hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.9.1 Enrolment control at the CTS-FP | Enrolment control at the CTS-FP can be controlled by the operator either:
• pre-populating the SIM of the CTS FP with IMSI ranges; or
• by the CTS-SN during signalling exchanges between the CTS-SN and CTS-FP.
In each of the above cases the CTS-FP is given information as to the range of IMSI values [16 ranges] that the CTS-FP can consider valid for enrolment. The stage 3 shall allow all IMSIs to be valid.
The validity period for each of these locally enrolled CTS-MS shall be controllable by CTS-FP subscriber.
For IMSIs that do not fall into these ranges the CTS operator can specify that the CTS-FP shall contact the CTS-SN for permission before enrolling these mobiles. In the case where the CTS operator doesn't specify that the CTS-SN should be contacted, then the CTS-MS with such IMSIs shall not be allowed to enrol.
The number of enrolled CTS-MS on a CTS-FP is controllable from the CTS-SN. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.9.2 Enrolment control at the CTS-SN | The CTS-SN can control initial enrolment and surveys enrolment for previously enrolled CTS-MS.
The enrolment process performed at the CTS-SN gives a CTS-MS the right to have CTS services on a CTS-FP for a certain period of time (determined by the CTS operator). This period of time shall not be capable of being altered by the CTS-FP subscriber. In order to have a continuous CTS service the enrolment process requires to be confirmed before this period expires. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.9.2.1 Initial enrolment at the CTS-SN | The CTS-FP may contact the CTS-SN via the access network to demand enrolment of a CTS-MS. In this case the IMSI of the CTS-MS is given to the CTS-SN.
In this case the CTS-SN shall perform range checking on the IMSI to verify roaming agreements and may interrogate (under operator control) the HLR of the CTS-MS in order to perform subscription checking.
Once the right to enrol has been established the CTS-SN confirms enrolment together with a validity period with which the CTS-FP supervises the subscription for CTS services. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.9.2.2 Subsequent enrolment at the CTS-SN | Subsequent enrolment is required to check that enrolled CTS-MSs still have the right of using CTS service. As part of the supervisory activities the CTS-FP requires to contact the CTS-SN at specific points in time either for reallocation of the GFL or other supervisory procedures. During these communications the CTS-SN can demand the CTS-FP to give information as to the enrolled CTS-MS on the CTS-FP. The CTS-SN can then check that the CTS subscription is still valid for these CTS-MS and either reconfirm the enrolment of the CTS-MS or withdraw the enrolment right (i.e. de-enrolment). |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.9.3 Agreement between the CTS FP Subscriber and CTS MS subscribers | The CTS FP subscriber chooses to give the right to a CTS MS subscribers to have access to his CTS FP.
This is performed by the CTS FP owner entering information into the CTS FP as defined by [4].
The CTS FP will only allow the CTS MS to have access once the CTS operator authorisation procedure has been successfully completed. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.9.4 CTS authorisation check of enrolment of a CTS MS onto a CTS FP | Enrolment of the CTS MS to a CTS FP involves:
• Optional Authentication of the CTS MS by the HPLMN via the CTS-SN;
• Optional Subscription check for the CTS MS by the HPLMN via the CTS-SN.
Confirmation of enrolment requires mutual authentication to taken place as described in [4]. The enrolment of a CTS-MS has an associated validity period. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.10 De-enrolment of CTS MS from a CTS-FP | The CTS FP can receive a command to remove the enrolment of a specific CTS MS at any time see [4].
If the validity period for a particular CTS MS expires then the specific CTS MS shall become de-enrolled.
De-enrolment can be commanded by either the CTS-FP subscriber or the CTS-SN. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.10.1 Mutual autentication | Mutual authentication is a concept whereby the CTS MS/CTS FP can check that the controlling network is a valid network. This protection mechanism is needed to ensure that both GSM and CTS operator can protect themselves from intrusion see ref [4]. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.11 CTS MM and CM layers | The message exchange on the Um* interface shall be (as close as possible) to the GSM 04.08 interface. The exceptions to this are the security procedures as specified in [4] which may be substituted in place of the normal GSM procedures. The CTS standard still allows the use of the normal GSM authentication and ciphering on the Um* interface. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.12 CTS MM and CM layers on the fixed network side | The CTS standard specifies the protocols on the CTS Um* interface only. The standard specifying the split between these layers on the fixed network side is left open to implementation. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.13 CTS Mobility services | CTS mobility services are to be specified for the CTS Um* interface only. Mobility in the fixed network (i.e. towards other nodes in the fixed network) is out of scope of this recommendation. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.13.1 CTS support in idle mode | Cell selection and reselection mechanisms are described in [5].
It should be possible for the CTS MS subscriber to choose preferences between either GSM or CTS coverage. When in CTS coverage, it should be possible that the user set preferences between different CTS coverage. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.13.2 CTS attach and detach | CTS mobility services offer the ability to attach an enrolled CTS-MS to a CTS-FP. The camping of a CTS-MS on a CTS-FP requires that the CTS-MS performs an attachment to the CTS FP.
In the case where a CTS-MS is disabled (i.e. turned off, etc) whilst attached to the CTS-FP, the CTS-MS can, under certain circumstances, inform the CTS-FP of this event. This procedure is known as detachment from a CTS-FP.
In the case where a CTS-MS is refused attachment to a CTS-FP due to the fact that it is not enrolled on the CTS-FP, the CTS-MS shall consider itself de-enrolled and should not re-attempt to attach to the same CTS-FP.
The attach and detach procedures shall be those specified in 04.08 with modifications in order to take into account the local CTS security procedures as specified in [4]. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.14 CTS CM layer | The CTS CM layer is specified for the local CTS system only. The CTS CM layer in the fixed network is out of scope of the present document.
The CTS CC layer is specified in GSM 04.08 section 5. The CTS CC layer is modified in order to introduce extra functions (eg Hook Flash) as specified in [4] |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.14.1 CTS service indication | Once attached to a CTS-FP the MS shall indicate that CTS service is available.
The CTS user can define a name (alphanumeric name, icon, etc) for each of the CTS cells to which it has access (i.e. attached). The MS will, when attached and in coverage of a CTS cell and if required by the user, indicate to the user the current CTS cell. The indication may be the name of the current CTS cell, as set by the user. The form of display and indication are left to the CTS-MS manufacturer's choice.
[NOTE: The CTS-FP owner could also define a name for his CTS-cell. This name could be transmitted to the MS, e.g. during attachment by using the NITZ procedure.] |
fcc930975597116eb21de958d20d3f3d | 03.56 | 4.15 Subscriber information for CTS | A CTS-MS subscriber may be enrolled on several CTS FPs. It shall be possible for the subscriber to establish an order of preference between the allowed CTS-FPs.
Subscriber specific CTS information can be stored and managed in the HLR.
In addition to subscriber details in the HLR, it is also necessary for subscriber specific CTS information to be stored and managed in the SIM of the CTS MS. This is required because the MS shall prioritise CTS cells in the cell (re)selection process and also for presenting the current CTS cell to the user.
The management of CTS data on SIM may be performed manually. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 5 Transmission | No specific requirements are identified. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 6 Information storage | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 6.1 Information managed per CTS-MS subscriber | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 6.1.1 Stored in the CTS-MS SIM | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 6.1.2 Stored in the HLR | CTS MS subscriber CTS subscription may be stored in the HLR. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 6.1.3 Stored in the MSC/VLR | CTS MS subscriber CTS subscription may be stored in the MSC/VLR. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 6.2 Information managed per CTS-FP subscriber | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 6.2.1 Stored in the CTS-FP SIM | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 6.2.2 Stored in the CTS-FPE | CTS-SN Telephone Number is stored in non volatile memory in the CTS-FPE. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 6.2.3 Stored in the CTS-SN | CTS-FP subscriber's subscription information may be stored in the CTS-SN. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 6.2.4 Stored in the CTS-HLR | CTS-FP subscriber's subscription information may be stored in the CTS-HLR. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7 Identities | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.1 Identification of the CTS-FP | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.1.1 IFPSI | A CTS specific identity is assigned to a CTS FP subscriber of a CTS service. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.1.2 IFPEI | Each CTS-FP is assigned by the manufacturer a unique IFPEI number see GSM 03.03 [3].
The coding rules of the IFPEI and the rules for changing the IFPEI shall be equal to the rules defined for the IMEI in GSM 03.03 [3]. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.1.3 FPBI | The CTS-FP broadcasts (after CTS-FP initialisation has been performed) a beacon which carries information conveying the Fixed Part Beacon Identity which identifies the CTS-FP. The FPBI need not be unique due to the capacity of signalling on the beacon. The FPBI is defined in GSM 03.03 [3]. The use of the beacon and the FPBI related procedures are defined in [5]. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.2 Addressing parameters | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.2.1 Addressing the CTS-FP | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.2.1.1 CTS-FP Fixed Network dialling number | This is the fixed network dialling number (PSTN/ISDN) to which the CTS-FP is connected. A single CTS-FP may have several fixed network dialling numbers. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.2.1.2 CTS FP name | It shall be possible to assign a subscriber-defined identifier to each CTS FP. The CTS FP name can e.g. be an icon or an alphanumeric text up to 10 characters. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.2.2 Addressing the CTS-MS subscriber | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.2.2.1 MSISDN | The MSISDN is the dialling number at which the CTS-MS can be reached in the cellular network. It may also be used for CTS applications.
In order to address a CTS-MS by its MSISDN, this number has to be known by the CTS-FP and the CTS-MS. The MSISDN may be submitted to the CTS-FP either:
• from the CTS-HLR at CTS-MS enrolment; or
• by means of user input; or
• by the CTS-MS |
fcc930975597116eb21de958d20d3f3d | 03.56 | 7.2.2.2 CTS-MS Subscriber Identity(CTS-MSI) | The CTS-MSI is an CTS-MS identity which has only local significance between a CTS-MS and CTS-FP pair, its purpose is to maintain the anonymity of the users of the CTS service as specified in [4].
The CTS-MSI is assigned and maintained by the CTS-FP during CTS-MS enrolment, and is reallocated by the CTS-FP during CTS attachment and as part of each Mobile originated and Mobile terminated signalling exchange. It is unique for each CTS-MS enrolled at the CTS-FP. The CTS-MSI allocation procedure and CTS-MSI reallocation procedure data flows are specified in [4].
In order to maintain anonymity of the subscriber the CTS-MSI shall be used in all signalling procedures by both CTS-MS and CTS-FP.
The protocols shall ensure that the CTS-FP can detect any CTS-MSI conflicts (e.g. duplicated CTS-MSI). In case of CTS-MSI conflicts, it is up to the CTS-FP to resolve the situation by the appropriate security checks (i.e. by obtaining the IMSI of the CTS-MS, performing local security procedures (see [4]) and verifying the enrolment rights). |
fcc930975597116eb21de958d20d3f3d | 03.56 | 8 Operation and maintenance aspects | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9 Function and information flows | The following functional flows deal with the initial phase of CTS where roaming is not supported. In this case the DPLMN, HPLMN and the CTS operator need to be the same. If they are the same then this allows the CTS reference model to be simplified as the CTS FRA can be integrated in to the CTS SN thus simplifying the signalling model. The CTS specifications shall provide means to ensure that DPLMN, HPLMN and CTS operator are the same entity.
When there is no indication on the status of the CTS frequencies (i.e. licensed or licensed exempt), the following recommendations are applicable to all cases. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.1 CTS FP management | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.1.1 CTS FP Initialisation | CTS FP initialisation can be envisaged in two phases.
The data flow diagram below shows the flows required for CTS FP initialisation.
Figure 9: CTS FP initialisation
1 The CTS-FP subscriber wants to initialise a CTS-FP. He triggers an MMI procedure. The CTS-SN telephone number is used by the CTS-FP to contact the CTS-SN. The IFPSI is given to the CTS-SN.
The CTS-SN authenticates the CTS-FP by addressing the CTS-HLR using the IFPSI.
2 In absence of location information the CTS-FRA allocates a temporary GFL.
The CTS-FP is temporarily initialised. Confirmation of the initialisation is performed in future signalling when location information can be provided and a correct GFL allocated. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.1.2 Update of CTS FP frequencies | The data flow diagrams below shows the flows required for gathering the DPLMN surrounding cells and the updating the CTS FP GFL.
Figure 10: CTS MS Home cell reporting
1 The CTS MS remembers the cells it last camped on from the DPLMN and the time it left each cell.
2 This cell information is given to the CTS FP during signalling exchanges during attachment for example.
In addition if the MS has received a CTS-SN Telephone Number (see 9.2 CTS management for CTS MS) from the DPLMN then this will also be given.
Figure 11: CTS FP update
1 The CTS-FP calls the CTS-SN.
If a CTS-SN Tel No has been received from the DPLMN, then this number is used. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 2 Authentication of the CTS FP is made by the CTS SN and HLR | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 3 DPLMN information is given by the CTS FP for location purposes | 4 GFL is updated and the CTS-FP authenticates the CTS-SN.
This procedure also forms part of the CTS-FP initialisation procedure where the Temporary GFL (allocated during the first initialisation) is replaced by the GFL based on location information. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.2 CTS management for CTS MS | The GSM PLMN controls the MS as to whether it can operate CTS. When the CTS-MS access the GSM PLMN it will receive signalling which informs the CTS-MS whether it can perform CTS operations.
Figure 12
1 The MS performs a location update in the DPLMN.
2 Authentication is performed.
3 If CTS is allowed in the PLMN, or this particular MS has the CTS subscription then the MSC sends CTS info to the MS. The CTS-SN Tel No is optional and indicates the telephone number for this LA/Cell to which The CTS-FP should contact.
4 The location update is accepted. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.3 CTS integration to Fixed Mobile Convergence applications | In order to use CTS for FMC applications it is suggested that a hook be provided in order to facilitate FMC applications. To this end it is envisaged to allocate a FMC Telephone Number, for instance on the CTS-FP SIM. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.4 Functions related to MS in idle mode for support of CTS | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.4.1 Cell selection and reselection | The definition of a "suitable cell", as defined in GSM 03.22, is extended with the following criterion:
An CTS-MS with SIM indicating CTS subscription shall always try to select the cell with the highest CTS FP priority according to the information stored on the SIM. The CTS selection parameters last received from the CTS FP shall be used to calculate the selection criteria for the corresponding CTS cell. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.4.2 DPLMN Cell information gathering | As the CTS-MS roams through the DPLMN it shall gather information as to the cells it has passed through. This cell information is stamped with the time that the MS either left the cell or lost GSM coverage with the cell. The figure below shows the required functional behaviour.
When the CTS-MS gives this information to the CTS-FP the time information is presented by using the relative time (for example: Cell X was last camped on 5 minutes ago).
Figure 13: DPLMN cell information gathering
In this figure the cells reported to the CTS FP are as follows:
• Cell D left at T-td
• Cell C left at T-tc
• Cell B left at T-tb
• Cell A left at T-ta |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.4.3 CTS local mobility | The presence and absence of a CTS-MS needs to be determined by the CTS-FP as part of the local CTS mobility procedures. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.4.3.1 CTS attachment | CTS attachment is a procedure by which a CTS-MSs presence is made known to the CTS-FP. The attachment to a CTS-FP is made by the CTS-MS when the CTS-MS comes within coverage of the CTS-FP.
The CTS Attach procedure shall replicate the protocol as expected as in GSM, with the exceptions to the local security procedures defined in [4].
Figure 14: CTS Attachment
1 The CTS-MS comes within coverage of the CTS-FP and initiates attachment.
2 Local authentication is performed see ([4]).
3 The CTS attachment is accepted. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.4.3.2 CTS detachment | CTS detachment is a procedure by which a CTS-MSs non presence is made known to the CTS-FP. When a CTS-MS is attached the CTS-FP shall regularly ensure that the CTS-MS is within CTS-FP coverage, if the CTS-MS is found to be out of coverage the CTS-FP will mark the CTS-MS as detached. If the MCTS-MS is powered down within coverage of the CTS-FP the CTS-MS shall perform the CTS detach procedure.
Figure 15: CTS MS detachment
1 The CTS-MS when powered down within coverage of the CTS-FP indicates that it no longer is attached.
Figure 16: CTS-FP detected detachment of CTS-MS
1) The CTS-FP pages and finds that the MS is not present. The CTS-MS is marked as detached. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.5 Functions related to active mode support of CTS | 9.5.1 MS connection establishment for MT and MO calls.
When calls are established the CTS FP shall perform Authentication and Ciphering as specified in 03.20. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.5.2 Handover | Handover between instances of CTS radio interfaces shall be supported by the CTS MS when the same CTS FP controls these CTS radio interfaces. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 9.6 Overview of signalling | Security procedures such as authentication, ciphering and key distribution are defined in order to protect the GSM network and the user communication. CTS operation is initialised by downloading operation control information into the CTS-FP. The operator can change and de-activate CTS operation via the GSM Radio Interface or via the access network. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10 CTS Architecture | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.1 CTS Elements | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.1.1 CTS Fixed Part | CTS Fixed Part (CTS-FP) is the logical and physical element, which provides the link to the access network. For this purpose it controls on the one side one or more CTS Radio Interface and on the other side one or more access network interface. The interworking between both interfaces is implemented in the CTS-FP interworking Function.
Figure 17: The CTS-FP and its main functional entities
Figure 17bis: The CTS-FP connected to GSM |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.1.2 CTS Mobile Station | The CTS Mobile Station (CTS-MS) is the logical and physical element which provides to the user cordless access to the fixed network or the GSM network. The CTS-MS consists of GSM Mobile Equipment and a GSM-SIM, both with additional CTS capabilities.
Figure 18: The CTS-MS and its main functional entities |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.1.3 CTS controlling and supporting network entities | In order to control and support the CTS, the following functional entities are situated in the GSM network:
• the CTS-AuC is the functional entity for performing authentication of the CTS-FP SIM;
• the CTS-HLR is the functional entity which contains the data base of the CTS-FP subscribers of the CTS operator. This data base is related to subscription management (including related security control). It may contain additional information, e.g. subscriber specific CTS operation information;
• the CTS-SN is mainly a routing functionality. It provides the interface to the CTS-FP(s) via the access network. The CTS SN also provides the security functions for secure signalling of CTS specific operation information on the CTS access network interface;
• the CTS FRA is considered to be the location of frequency allocation for the CTS operation.
Figure 19: CTS supporting functional entities |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2 CTS Interfaces | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.1 CTS Radio Interface (Um*) | The CTS Radio Interface is used for local communication between CTS MS and the CTS FP. It provides a cordless connection between these two elements. This interface is referred to as Um* in the CTS specifications.
According to GSM 02.56 [2], the CTS Radio Interface is a modified GSM Radio Interface. CTS is to operate in the GSM frequency spectrum of the DPLMN operator or in an license exempt frequency band.
The physical characteristics of the CTS Radio Interface are similar to those of the GSM Radio Interface. The aspects of the radio interface are described in [5].
The Um* interface shall be future proof to support services to be implemented in later phases such as data and fax services etc. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.2 GSM Radio Interface (Um) | On the GSM Radio Interface the CTS-MS shall behave according to the GSM standards. As required in GSM 02.56 [2], means of the GSM Radio Interface shall be used to exchange information relevant for operation control of the CTS. User communication via the GSM Radio Interface is covered by the GSM specifications and not considered in the CTS specifications. The GSM Radio Interface is referred to as Um in the CTS specifications. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.3 CTS Access Network Interface | The Access Network Interface is the connection of the CTS-FP to the Fixed or mobile Network for user communication. According to GSM 02.56 [2], this interface shall also be used to transport information which is relevant for operation control. The Fixed Network Interface is referred to as Cf in the CTS specifications. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.3.1 Physical characteristics of the CTS Fixed Network Interface | The physical characteristics of the Fixed Network Interface, e.g. signal levels, shall correspond to national standards. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.3.2 Physical characteristics of the CTS GSM Network Interface | In the case of a CTS-FP connected to GSM, the physical characteristics of the GSM Network Interface, e.g. signal levels, shall correspond to GSM standards. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.4 Network internal interfaces | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.4.1 Interface CTS SN/CTS HLR (Cd) | The Cd interface between the CTSSN and the HLR may use existing MAP procedures to receive challenge/response pairs to be used for the authentication of the CTS FP SIM when communication is performed via the access network. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.4.2 Interface CTS SN/CTS HLR (Cd') | Cd' interface between CTS SN and CTS HLR. The interface is used for CTS FP subscription control. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.4.3 Interface CTS SN/CTS FRA | This interface is used when download of radio parameters shall be performed to the CTS-FP via application signalling. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.2.4.4 Interface CTS FRA/BSC | This interface is used when download of radio parameters shall be performed to the CTS-FP via GSM layer 3 signalling. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.3 CTS sub-systems | The CTS can be split in two subsystems, the local CTS and the supervising CTS:
• the local CTS consists of a CTS-FP and one or several CTS-MS, which are enrolled at the CTS-FP.
The main aspect of the local CTS is that the user communication is provided via the CTS Radio interface and the CTS Access Network Interface;
• the supervising CTS consists of the functional entities to control CTS operation. The main aspect of the supervising CTS is the control of the operation of the local CTS such as:
• control of the frequencies used by the CTS-FP on the CTS Radio Interface;
• control of the CTS FP subscription (of the SIM) of the CTS FP;
• control of the CTS MS subscription (of the SIM) of the CTS MS.
Figure 20: CTS Subsystems |
fcc930975597116eb21de958d20d3f3d | 03.56 | 10.4 Network Access | As the purpose of the CTS, the Access Network is accessed by the CTS-MS via the CTS-FP for user communication.
A CTS-MS can, depending on services subscribed, access the GSM network for user communication. This case is covered by the GSM specifications and not considered in the CTS specifications.
According to GSM 02.56 [2], control of the CTS operation can be carried out either via the GSM Network or via the Access Network. In the latter case the Access Network is as a transit network CTS operation control.
A co-ordination between the GSM Network and the Access Networks is not required. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 11 CTS main parameters | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 11.1 Radio Resource Management parameters | The Radio Resource Management specific parameters are defined in [5]. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 11.2 Identification parameters | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 11.3 Security specific parameters | The security related parameters such as authentication and ciphering keys are defined in [4]. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 12 The local CTS | The following elements are part of the local CTS:
• CTS-FP;
• One or several CTS-MS.
The following interfaces have relevance for the local CTS:
• the CTS Radio Interface Um* for signalling and user communication;
• the CTS Access Network Interface Cf or Um for user communication.
Aspects of the local CTS are the following:
• services provided on the CTS radio interface as defined in [2] (e.g. MT and MO calls);
• transmission mechanisms related to these services;
• signalling mechanisms related to these services;
• protocol stacks on the CTS radio interface;
• functions and procedures on the CTS radio interface. |
fcc930975597116eb21de958d20d3f3d | 03.56 | 12.1 Transmission and Signalling Planes | |
fcc930975597116eb21de958d20d3f3d | 03.56 | 12.1.1 Transmission Plane | According to GSM 02.56 [2] user communication is restricted to speech in the first phase of CTS specification. The transmission plane is segmented in two parts, the transmission on the CTS Radio Interface and the transmission on the CTS Access Network Interface.
The transmission of speech on the CTS Radio Interface Um* follows the GSM standard.
The transmission on the CTS Fixed Network Interface follows national standards for the fixed network access and is out of the scope of CTS specifications.
History
Document history
V7.0.1
May 1999
Public Enquiry PE 9943: 1999-05-26 to 1999-10-22
(as EN 301 405)
V7.1.0
May 2000
Vote V 20000721: 2000-05-22 to 2000-07-21
V7.1.1
August 2000
Publication |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 1 Scope | No mandatory protocol between the Service Centre (SC) and the Mobile Switching Centre (MSC) below the transfer layer is specified by GSM; this is a matter of agreement between SC and PLMN operators.
The present document specifies three approaches to the specification of protocol stacks of communication protocols for the purpose of relaying short messages and alerts between Short Message Service Centres and Gateway/Interworking MSCs (GMSC) for the Short Message Service (SMS). One approach is based upon use of the complete OSI reference model (see X.200), another approach is based upon the use of only the lower three OSI layers, and another approach is based upon the use of CCITT Signalling System No. 7 (see Q.700).
Alternative protocol stacks are specified via ASN.1 encoding rules (see X.208 and X.209). These alternative protocol stacks are examples for the implementation of the Short Message Relay Layer (SM‑RL). The requirements placed upon the Short Message Relay Layer are briefly described in clause 9 of GSM 03.40.
Specifications are based upon individual contributions. Any judgement concerning functionality, completeness and advantages/disadvantages of implementation is intentionally omitted. |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 1.2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.
• For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
[1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms".
[2] GSM 03.40: "Digital cellular telecommunications system (Phase 2+); Technical realization of the Short Message Service (SMS) Point-to-Point (PP)".
[3] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification".
[4] GSM 12.20: "Digital cellular telecommunication system (Phase 2); Network Management (NM) procedures and messages".
[5] CCITT Recommendation E.164: "Numbering plan for the ISDN era".
[6] CCITT Recommendation Q.700: "Introduction to CCITT Signalling System No.7".
[7] CCITT Recommendation Q.931: Integrated services digital network.(ISDN) User-Network interface layer 3 specification for basic control".
[8] CCITT Recommendation Q.932: "Generic procedures for the control of ISDN supplementary services".
[9] CCITT Recommendation Q.941: "ISDN user-network interface protocol profile for management".
[10] CCITT Recommendation Q.1400: "Architecture framework for the development of signalling and organisation, administration and maintenance protocols using OSI concepts".
[11] CCITT Recommendation X.2 (1988): "International data transmission services and optional user facilities in public data networks and ISDNs".
[12] CCITT Recommendation X.200: "Reference Model of Open Systems Interconnection for CCITT Applications".
[13] CCITT Recommendation X.208: "Specification of basic encoding rules for Abstract Syntax Notation One (ASN.1)".
[14] CCITT Recommendation X.209: "Specification of Abstract Syntax Notation One (ASN.1)".
[15] CCITT Recommendation X.215: "Session service definition for open systems interconnection for CCITT applications".
[16] CCITT Recommendation X.216: "Presentation service definition for open systems interconnection for CCITT applications".
[17] CCITT Recommendation X.217: "Association control service definition for open systems interconnection for CCITT applications".
[18] CCITT Recommendation X.219: " Remote operations: model, notation and service definition".
[19] CCITT Recommendation X.223: "Use of X.25 to provide the OSI connection-mode network service for CCITT Applications".
[20] CCITT Recommendation X.224: "Transport protocol specification for Open Systems Interconnection for CCITT Applications".
[21] CCITT Recommendation X.225: "Session protocol specification for Open Systems Interconnection for CCITT Applications".
[22] CCITT Recommendation X.226: "Presentation protocol specification for Open Systems Interconnection for CCITT Applications".
[23] CCITT Recommendation X.227: "Information technology - Open Systems Interconnection - protocol specification for the association".
[24] CCITT Recommendation X.229: "Remote operations Protocol specification". |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 1.3 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04. |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 2 An OSI Protocol Stack For Interconnecting SCs and MSCs | This clause specifies a stack of communication protocols in terms of the OSI Reference Model (see X.200) and therefore makes use of all seven layers for the purpose of relaying short messages and alerts between SC and MSC for the Short Message Service. The SMS application layer (layer 7) is mapped to the Presentation Layer via ACSE (see X.217 and X.227) and ROSE (see X.219 and X.229). Only the Kernel functional unit of the Presentation Layer is used. Only Kernel and Duplex functional units are used in the Session Layer (see X.215 and X.225). |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 2.1 Service elements on the application layer | An association (class 3) between SMRSEs is formed via ACSE and ROSE operations (class 2 and 5) are used to implement the Short Message Relay Layer described in clause 9 of GSM 03.40. This results into a asynchronous symmetric situation where both (the application entity in) the SC and (the application entity in) the MSC can invoke a SMRSE operation at any time.
The new SMRSE service element is first defined in this section, and then specified in ASN.1 notation in section 2.2.
SMRSE definition
This service element defines the following services:
SMR-BIND This operation must be invoked by that party which established the application association; only after that may the remaining SMRSE services be used. This operation reports either success or failure (result or error).
SMR-MO-DATA This operation may be invoked by the application entity in the MSC; it is used to relay one SMS transfer layer PDU from the IWMSC to the SC. This operation reports either success or failure.
SMR-MT-DATA This operation may be invoked by the application entity in the SC; it is used to relay one SMS transfer layer PDU from the SC to the GMSC, to be further relayed to the MS addressed. This operation reports either success or failure, after the full relay attempt to the MS.
SMR-ALERT This operation may be invoked by the application entity in the MSC. It is used as the GMSC-to-SC indication of the fact that an MS which was previously unattainable has recovered operation. This operation does not report any outcome.
SMR-UNBIND This operation must be invoked by that party which invoked the SMR-BIND operation, as the last SMRSE operation before releasing the application association. This operation reports success only.
Of the services defined above, SMR-MO-DATA and SMR-MT-DATA semantically mean the relay of short messages across the SC-MSC-connection; SMR-ALERT similarly implements the alerting operation. The SMR-BIND service is used to exchange identifications, passwords, etc., and in order to negotiate the usage of the other services. The SMR-UNBIND service prepares for the release of the application association. |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 2.2 Detailed specification of the SMRSE services | On the following pages, the new SMRSE service element is specified with the ASN.1 notation, together with the entire SM-RL protocol.
The Abstract Syntax Notation of
the Short Message Relay Service Element
SMRSE
NOTE: The first two arcs of the object identifier are arbitrarily allocated, the name "etsi" is adopted from GSM 12.20 but the value 040 is arbitrary, and the last three arcs are allocated in this module.
1st module of 3:
SMS-UsefulDefinitions
SMS-usefulDefinitions { iso identified-organization etsi(040) mobile-domain(0) gsm-messaging(4) gsm-sms1(10) usefulDefinitions(0) }
DEFINITIONS
IMPLICIT TAGS
::=
BEGIN
EXPORTS id-ot-SC, id-ot-MSC, id-port, id-ac-so, id-ac-st, id-SMRSE, id-as-SMRSE;
IMPORTS
ID ::= OBJECT IDENTIFIER
-- root for all sms allocations
mobile-domain ID ::= {iso identified-organization etsi(40) mobile-domain(0) }
gsm-messaging ID ::= { mobile-domain gsm-messaging(4) }
gsm-sms1 ID ::= { gsm-messaging gsm-sms1(10)}
-- categories
id-mod ID ::= { gsm-messaging 1 } -- modules
id-ot ID ::= { gsm-messaging 2 } -- object type
id-pt ID ::= { gsm-messaging 3 } -- port types
id-ac ID ::= { gsm-messaging 4 } -- appl. contexts
id-ase ID ::= { gsm-messaging 5 } -- ASEs
id-as ID ::= { gsm-messaging 6 } -- abstract syntaxes
-- modules
usefulDefinitions ID ::= { gsm-sms1 0 }
relayProtocol ID ::= { gsm-sms1 1 }
relayAbstractService ID ::= { gsm-sms1 2 }
-- object types
id-ot-SC ID ::= { id-ot 0 }
id-ot-MSC ID ::= { id-ot 1 }
-- port types
id-port ID ::= { id-pt 0 }
-- application contexts
id-ac-so ID ::= { id-ac 0 } -- SC does BIND
id-ac-st ID ::= { id-ac 1 } -- MSC does BIND
-- application service elements
id-SMRSE ID ::= { id-ase 0 }
-- abstract syntaxes
id-as-SMRSE ID ::= { id-as 0 }
END
2nd module of 3
RelayAbstractService
RelayAbstractService { iso identified-organization etsi(040) mobile-domain(0) gsm-messaging(4) gsm-sms1(10) relayAbstractService(2) }
DEFINITIONS
IMPLICIT TAGS
::=
BEGIN
-- EXPORTS everything
IMPORTS
BIND, UNBIND
FROM Remote-Operations-Notation
{ joint-iso-ccitt remote-operations(4) notation(0) }
OBJECT, PORT, ABSTRACT-BIND, ABSTRACT-UNBIND,
ABSTRACT-OPERATION, ABSTRACT-ERROR
FROM AbstractServiceNotation
{ joint-iso-ccitt mhs-motis(6) asdc(2) modules(0) notation(1) }
id-ot-SC, id-ot-MSC, id-port
FROM SMS-UsefulDefinitions
{ iso identified-organization etsi(040) mobile-domain(0) gsm-messaging(4) gsm-sms1(10) usefulDefinitions(0) } ;
-- upper bound settings
ub-operator-name-length INTEGER ::= 20
ub-agreem-name-length INTEGER ::= 20
ub-X121Address-length INTEGER ::= 15
ub-password-length INTEGER ::= 20
-- Objects
-- The SC and the MSC are modelled as atomic objects, sC-Object and MSC-Object. Each object
-- has one port for the interconnection. ([S] and [C] indicate supply and consumption of services,
-- respectively).
sC-Object OBJECT
PORTS { sMR-port [C] }
::= id-ot-SC
mSC-Object OBJECT
PORTS { sMR-port [S] }
::= id-ot-MSC
-- Port
sMR-port PORT
CONSUMER INVOKES { Forward-MS-Terminated-Short-Message }
SUPPLIER INVOKES { Forward-MS-Originated-Short-Message, Alert- SC }
::= id-port
-- Bind
SMR-Bind ::=
ABSTRACT-BIND
TO { sMR-port }
BIND
ARGUMENT SMR-Bind-Parameters
RESULT SMR-Bind-confirm
BIND-ERROR SMR-Bind-failure
-- Unbind
-- The UNBIND is a harsh release of the association: all outstanding operations are aborted, and
-- SMR-ALERT requests may be lost if they collide with the SMR-UNBIND request. The SC and
-- the MSC should negotiate (during SMR-BIND) the use of services on the association (the
-- operations parameter - list of operation types for the association) in such a way that no harmful
-- losses of operations occur.
SMR-Unbind ::= ABSTRACT-UNBIND
FROM { sMR-port }
UNBIND
ARGUMENT Time-when-connected
RESULT Time-when-disconnected
-- Association control parameters
SMR-Bind-Parameters ::= SEQUENCE {
initiatorID [0] Name,
password [1] Password OPTIONAL,
pswNeeded [2] BOOLEAN,
iniType [3] Telecom-System-Type,
operations [4] List-of-Operations
}
-- Above and in SMR-Bind-confirm
-- initiatorID/respID: identify the initiating/responding telecommunication subsystem
-- password: may assist in authentication
-- pswNeeded (BIND only): requests password into SMR-Bind SMR-Bind-confirm
-- iniType/respType: identify the types of the systems
-- operations: lists the SM relay operations requested and supported on the association:
-- operations listed in both the BIND and the CONFIRM may be used (i.e. this is a negotiation
-- between SC and MSC)
-- transient (CONFIRM only): forces the association (and the underlying connections) transient: it
-- must be UNBouND as soon as there are no operations to be performed
Name ::= SEQUENCE {
operator [0] Operator OPTIONAL,
bilateralAgreem [1] BilateralAgreem OPTIONAL,
dataNetworkAddress [2] X121Address OPTIONAL,
iSDNAddress SMS-Address OPTIONAL
}
-- operator is a text string containing the name of the SC/PLMN operator. bilateralAgreem is a
-- text string identifying the bilateral agreement between the SC and the PLMN operators which
-- allows for this association to be established.
-- dataNetworkAddress is the PSPDN X.121 address of the SC/MSC issuing the BIND or
-- CONFIRM, occurring only if a PSPDN is used.
-- iSDNAddress is the PLMN address of the SC as seen by the MSs (same datum in both BIND
-- and CONFIRM).
-- Any pair of subsets of these parameters may be used to identify the SC and the MSC to one
-- another.
Operator ::= PrintableString (SIZE(0..ub-operator-name-length))
BilateralAgreem ::= PrintableString (SIZE(0..ub-agreem-name-length))
X121Address ::= NumericString (SIZE(0..ub-X121Address-length))
- SMS-Address is specified later in this module.
Password ::= PrintableString (SIZE(0..ub-password-length))
Telecom-System-Type ::= INTEGER {
short-Message-Service-Centre (0),
public-Land-Mobile-Network (1)
-- Extensions are possible: additional
-- telecommunication subsystems might adopt this
-- service element for their interconnection.
}
List-of-Operations ::=
BIT STRING {
sMR-MO-Data-by-MSC (0),
sMR-MT-Data-by-SC (1),
sMR-Alert-by-MSC (2)
-- Extensions are possible: additional operations may be defined within this service
-- element. Existing systems should tolerate unknown values, but negotiate not to
-- perform unknown operations.
}
SMR-Bind-confirm ::= SEQUENCE {
respId [0] Name,
password [1] Password OPTIONAL,
respType [3] Telecom-System-Type,
operations [4] List-of-Operations,
transient [5] BOOLEAN,
connectTime [6] Time-when-connected
}
SMR-Bind-failure ::= SEQUENCE {
connect-failure-reason [0] Connect-failure,
alternative-system [1] Name OPTIONAL
}
-- connect-failure-reason contains one of the error indications given in the following table.
-- alternative-system is included when the SC/PLMN operator wishes to indicate that the MSC/SC
-- might try to establish an association with another SC/MSC.
Error indications
Reason
not-entitled
The responder is not entitled to accept a request for an association between itself and the initiator.
temporary-overload
The responder is not capable of establishing an association due to temporary overload.
temporary-failure
The responder is not capable of establishing an association due to a temporary failure (having impact on an entity at SM-RL or at layers above).
incorrect-ID-or-password
The responder will not accept the request to establish an association between itself and the initiator due to incorrect identity or password.
not-supported
The responder does not recognize the telecommunication subsystem type of the initiator, or cannot support any of the operations suggested on the association.
Connect-failure ::= INTEGER
{ not-entitled (0),
temporary-overload (1),
temporary-failure (2),
incorrect-ID-or-password (3),
not-supported (4)
}
Time-when-disconnected ::= UTCTime
Time-when-connected ::= UTCTime
-- The SMR-MT-DATA operation
-- SMR-MT-DATA
Forward-MS-Terminated-Short-Message ::=
ABSTRACT-OPERATION
ARGUMENT RPDataMT
RESULT RPAck
ERRORS { Unknown-subscriber,
Teleservice-not-provisioned,
Call-barred,
Facility-not-supported,
Memory-capacity-exceeded,
Absent-subscriber,
MS-busy-for-MT-SMS
SMS-lower-layer-capabilities-not-prov,
Error-in-MS,
Illegal-subscriber,
Illegal-equipment,
System-failure
}
-- SMR-MT-DATA error alternatives listed below
Unknown-subscriber ::=
ABSTRACT-ERROR
PARAMETER RPError
Teleservice-not-provisioned ::=
ABSTRACT-ERROR
PARAMETER RPError
Call-barred ::=
ABSTRACT-ERROR
PARAMETER RPError
Illegal-subscriber ::=
ABSTRACT-ERROR
PARAMETER RPError
Illegal-equipment ::=
ABSTRACT-ERROR
PARAMETER RPError
System-failure ::=
ABSTRACT-ERROR
PARAMETER RPError
Facility-not-supported ::=
ABSTRACT-ERROR
PARAMETER RPError
Memory-capacity-exceeded ::=
ABSTRACT-ERROR
PARAMETER RPError
Absent-subscriber ::=
ABSTRACT-ERROR
PARAMETER RPError
MS-busy-for-MT-SMS ::=
ABSTRACT-ERROR
PARAMETER RPError
SMS-lower-layer-capabilities-not-prov ::=
ABSTRACT-ERROR
PARAMETER RPError
Error-in-MS ::=
ABSTRACT-ERROR
PARAMETER RPError
-- SMR-MT-DATA parameters
-- SMR-MT-DATA parameters
RPDataMT ::= SEQUENCE {
mt-priority-request [0] BOOLEAN,
mt-more-messages-to-send [1] BOOLEAN OPTIONAL,
mt-message-reference RP-MR,
-- if more messages to send mechanism is used, the mt-message-reference value
-- must remain unchanged until all the messages to the same destination
-- have been sent.
mt-originating-address SMS-Address,
mt-destination-address SMS-Address,
mt-user-data RP-UD
}
-- SMR-MT-DATA acknowledgement
RPAck ::= SEQUENCE {
message-reference RP-MR
}
RPError ::= SEQUENCE {
msg-waiting-set [1] BOOLEAN,
message-reference RP-MR,
rp-msidsn SMS-Address OPTIONAL
-- must be an international ISDN address
rp-user-data RP-UD OPTIONAL
}
RP-MR ::= [APPLICATION 2] INTEGER (0..255)
RP-UD ::= [APPLICATION 3] OCTET STRING (SIZE (1..164))
-- Definition of Short Message Service address
SMS-Address ::= [APPLICATION 0] SEQUENCE {
address-type INTEGER { unknown-type(0),
international-number(1),
national-number(2),
network-specific-number(3),
short-number(4),
alphanumeric-number(5),
abbreviated-number(6) },
numbering-plan INTEGER { unknown-numbering(0),
iSDN-numbering(1),
data-network-numbering(3),
telex-numbering(4),
national-numbering(8),
private-numbering(9),
ERMES-numbering(10) },
address-value CHOICE {
octet-format
SemiOctetString
-- other formats are for further study
}
}
SemiOctetString ::= OCTET STRING (SIZE(1..10)) -- each octet contains
-- two binary coded
-- decimal digits
-- The SMR-MO-DATA and SMR-ALERT operations
-- SMR-MO-DATA
Forward-MS-Originated-Short-Message ::=
ABSTRACT-OPERATION
ARGUMENT RPDataMO
RESULT RPAck
ERRORS { SC-congestion,
MS-not-SC-Subscriber,
Invalid-Sme-address,
System-failure
}
-- SMR-ALERT
Alert-SC ::=
ABSTRACT-OPERATION
ARGUMENT RPAlertSC
-- SMR-MO-DATA error alternatives
SC-congestion ::=
ABSTRACT-ERROR
PARAMETER RPError
MS-not-SC-Subscriber ::=
ABSTRACT-ERROR
PARAMETER RPError
Invalid-Sme-address ::=
ABSTRACT-ERROR
PARAMETER RPError
System-failure ::=
ABSTRACT-ERROR
PARAMETER RPError
-- Parameters
-- SMR-MO-DATA parameters
RPDataMO ::= SEQUENCE {
mo-message-reference RP-MR,
mo-originating-address SMS-Address,
mo-user-data RP-UD
}
-- SMR-ALERT parameters
RPAlertSC ::= SMS-Address
-- must be an international ISDN address
END
3rd module of 3
RelayProtocol
RelayProtocol { iso identified-organization etsi(040) mobile-domain(0) gsm-messaging(4) gsm-sms1(10) relayProtocol(1) }
DEFINITIONS
IMPLICIT TAGS
::=
BEGIN
-- EXPORTS everything
IMPORTS
-- application service elements and application contexts
aCSE, APPLICATION-SERVICE-ELEMENT, APPLICATION-CONTEXT
FROM Remote-Operations-Notation-extension
{ joint-iso-ccitt remote-operations(4)
notation-extension(2) }
rOSE FROM Remote-Operations-APDUs
{ joint-iso-ccitt remote-operations(4) apdus(1) }
-- object identifiers
id-ac-so, id-ac-st, id-SMRSE, id-as-SMRSE
FROM SMS-UsefulDefinitions
{ iso identified-organization etsi(040) mobile-domain(0) gsm-messaging(4) gsm-sms1(10) usefulDefinitions(0) }
-- abstract service parameters
Forward-MS-Terminated-Short-Message,
Forward-MS-Originated-Short-Message, Alert-SC,
SMR-Bind, SMR-Unbind,
Unknown-subscriber, Teleservice-not-provisioned,
Call-barred, Facility-not-supported, Absent-subscriber,
MS-busy-for-MT-SMS
Invalid-Sme-address, Memory-Capacity-Exceeded,
SMS-lower-layer-capabilities-not-prov, Error-in-MS,
Illegal-subscriber, Illegal-equipment,
System-failure, SC-congestion, MS-not-SC-Subscriber
FROM RelayAbstractService
{ iso identified-organization etsi(040) mobile-domain(0) gsm-messaging(4) gsm-sms1(10) relayAbstractService(2) } ;
aS-ACSE OBJECT IDENTIFIER ::=
{joint-iso-ccitt association-control(2)
abstractSyntax(1) apdus(0) version (1) }
-- Application contexts
-- Two different application contexts are specified:
-- one for the case when the SC BINDs (and UNBINDs),
-- and the other for the case when the MSC BINDs (and UNBINDs).
-- There is only one application service element, however (see "Application service elements" below.)
sC-BINDs-and-UNBINDs
APPLICATION-CONTEXT
APPLICATION-SERVICE-ELEMENTS { aCSE }
BIND SMR-Bind
UNBIND SMR-Unbind
REMOTE OPERATIONS { rOSE }
INITIATOR CONSUMER OF { sMRSE }
ABSTRACT SYNTAXES { id-as-SMRSE , aS-ACSE }
::= id-ac-so
mSC-BINDs-and-UNBINDs
APPLICATION-CONTEXT
APPLICATION-SERVICE-ELEMENTS { aCSE }
BIND SMR-Bind
UNBIND SMR-Unbind
REMOTE OPERATIONS { rOSE }
RESPONDER CONSUMER OF { sMRSE }
ABSTRACT SYNTAXES { id-as-SMRSE , aS-ACSE }
::= id-ac-st
-- Application service elements
sMRSE APPLICATION-SERVICE-ELEMENT
CONSUMER INVOKES { forward-MS-Terminated-Short-Message}
SUPPLIER INVOKES { forward-MS-Originated-Short-Message,
alert-SC }
::= id-SMRSE
-- Remote operations
forward-MS-Terminated-Short-Message
Forward-MS-Terminated-Short-Message
::= 1
-- Note: localValue-words omitted, since they are typically not used, and likely to be removed
-- from the OPERATION and ERROR macros in ROSE.
forward-MS-Originated-Short-Message
Forward-MS-Originated-Short-Message
::= 2
alert-SC Alert-SC
::= 3
-- Remote errors
unknown-subscriber
Unknown-subscriber
::= 1
teleservice-not-provisioned
Teleservice-not-provisioned
::= 11
call-barred Call-barred
::= 13
illegal-subscriber
Illegal-subscriber
::= 9
illegal-equipment
Illegal-equipment
::= 44
system-failure
System-failure
::= 36
facility-not-supported
Facility-not-supported
::= 21
memory-capacity-exceeded
Memory-capacity-exceeded
::= 22
absent-subscriber
Absent-subscriber
::= 29
mS-busy-for-MT-SMS
mS-busy-for-MT-SMS
::= 30
sMS-lower-layers-capabilities-not-prov
SMS-lower-layer-capabilities-not-prov
::= 19
error-in-MS
Error-in-MS
::= 20
sC-congestion
SC-congestion
::= 101
mS-not-SC-Subscriber
MS-not-SC-Subscriber
::= 103
invalid-sme-address
Invalid-sme-address
::=104
END |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 2.3 Application rules for avoiding collisions between SMR-UNBIND and the other SMRSE operations | There may be a collision between the SMR-UNBIND operation and another operation. This may cause the unwanted abortion of SMR-MO-DATA or SMR-MT-DATA operations, and/or the loss of SMR-ALERT operations.
(In order to guarantee the completion of all the SMRSE operations, the Session negotiated release functional unit might have been specified on the session layer and the SMR-UNBIND mapped on that negotiated release. However, the Session negotiated release functional unit requires also the Session half duplex functional unit. The negotiated release functional unit is not used anywhere else in the GSM specifications, hence it was not adopted here either.)
The proper completion of all the SMRSE operations is guarantied by avoiding collisions between SMR‑UNBIND and other operations. This is achieved by following application rules which restrict the invocation of different operations on the association. Two alternative sets of application rules are given in 2.3.1 and 2.3.2 in the sequel; additional sets are possible. |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 2.3.1 Application rule set 1 Semi-permanent symmetric connection | This set of application rules is to be used in situations where the connection (on all the protocol layers) between the SC and the MSC is maintained for ever.
Within the SMR-BIND service, all operations are allowed on the association; semi-permanent connection is accepted (by not forcing the connection transient). This is negotiated within the SMR-BIND service as follows:
name of parameter value in request and report
operations {sMR-MO-Data-by-MSC,sMR-MT-Data-by-SC, sMR-Alert-by-MSC}
transient FALSE (in report only)
The association is used fully asymmetrically, the parties invoke SMR-MO-DATA, SMR-MT-DATA, and SMR-ALERT operations as needed.
The SMR-UNBIND operation is not normally invoked on the association. |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 2.3.2 Application rule set 2 Transient asymmetric connection | This set of application rules is to be used e.g. in situations where one SC has connections with many MSCs or vice versa, and there is a switched data network connecting them. A data network connection (and the higher layer connections on top of it) is maintained for the duration of the relay or alert operations only.
Within the SMR-BIND service, only one type of operations is negotiated for use on the association. (As an exception, an association for both SMR-MO-DATA and SMR-ALERT is allowed below.) The operations of that type must be invoked by the initiator of the SMR-BIND. The responder of the SMR-BIND accepts the one type of operations and forces the association transient.
The following is an example of negotiating this within the SMR-BIND service; here, the SMR-MT-DATA operations are to be initiated by the SC.
name of parameter value
iniType short-Message-Service-Centre
respType public-Land-Mobile-Network
operations { sMR-MT-Data-by-SC }
transient TRUE
The association for SMR-MO-DATA or SMR-ALERT is negotiated according to the same principle, the MSC being the initiator of the SMR-BIND.
As an exception to the single type of operations rule, the following SMR-BIND negotiation for both SMR-MO-DATA and SMR-ALERT is allowed in this application rule set:
name of parameter value
iniType public-Land-Mobile-Network
respType short-Message-Service-Centre
operations { sMR-MO-Data-by-MSC, sMR-Alert-by-MSC }
transient TRUE
The association may be used for invoking operations of the negotiated type(s) as long as there are such operations to be invoked. (In other words, until all short messages or/and alerts to that direction have been relayed.)
If SMR-ALERT is not allowed on the association, the SMR-UN-BIND operation may be invoked on the association as soon as all operations on the association have been completed (by REPORT or ERROR). If SMR-ALERT is allowed, a guard time since the last SMR-ALERT invocation (if any) must have elapsed also (to guarantee that the SMR-ALERTs have been processed - there will be no responses).
This set of application rules effectively makes the association asymmetric: all operations are invoked by the same party, hence collisions are not possible. |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 2.4 Timing terminology | The overall delay of a short message relay operation between an SC and an MS may be affected i.e. by the following delays:
a) transport connection establishment time between an SC and an MSC (including the time spent establishing a new network connection, if needed);
b) the time needed to establish the higher layer protocol connections on top of the transport connection (including the SMR-BIND operation); and
c) the time needed (request to result) for the actual remote operation (SMR-MO-DATA or SMR-MT-DATA) relaying the SM.
If semi-permanent connections are used, only the delay (c) is likely to occur.
As an aid to the organizations discussing these delays in actual implementations, the following time/count-valued constants are defined in the remainder of this section:
T-failure-delay
A/tr-typical-delay
A/tr-failure-delay
A/pe-typical-delay
A/pe-failure-delay
R/MO/1-typical-delay
R/MO/n-typical-delay
R/MO-failure-delay
R/MT-typical-delay
R/MT-failure-delay
R-OK-load
R-error-load
R/MO-OK-outstanding
R/MT-OK-outstanding
The delay (a) is dependent on the network being used. A delay exceeding T-failure-delay when establishing a transient transport connection should be treated as a failure, despite the worst-case delay specification of the network used.
The delay (b) for transient connections is typically A/tr-typical-delay, and a delay exceeding A/tr-failure-delay should be treated as a failure.
The delay (b) for semi-permanent connections is typically A/pe-typical-delay, and a delay exceeding A/pe-failure-delay should be treated as a failure.
The delay (c) for the SMR-MO-DATA service is typically R/MO/1-typical-delay if no other SMR-MO-DATAs are outstanding, and R/MO/n-typical-delay if there are other SMR-MO-DATAs outstanding. In either case, a delay exceeding R/MO-failure-delay should be treated as a failure.
The delay (c) is typically R/MT-typical-delay for the SMR-MT-DATA service (PLMN delays involved), and a delay exceeding R/MT-failure-delay should be treated as a failure.
Concerning throughput and overloading, a SMRSE responder is capable of processing R-OK-load SMRSE operations per minute and properly rejects (via error) up to R-error-load operations per minute if the actual processing throughput is exceeded. (Failing SMR-ALERTs do not cause any response, though.) The maximum number of outstanding SMR-MO-DATA operations on an application association must not exceed R/MO-OK-outstanding, if all operations are to be properly processed. The corresponding limitation for SMR-MT-DATAs is R/MT-OK-outstanding. |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 2.5 Error Cause Mapping | MAP to SC - MSC
IllegalSubscriber illegal-subscriber
IllegalEquipment illegal-equipment
TeleServiceNotProvisioned teleservice-not-provisioned
SM-DeliveryFailure (#0) memory-capacity-exceeded
SM-DeliveryFailure (#1) error-in-MS
SM-DeliveryFailure (#2) sms-not-provisioned
CallBarred call-barred
DataMissing system-failure
FacilityNotSupported facility-not-supported
SystemFailure system-failure
UnexpectedDataValue system-failure
UnidentifiedSubscriber unknown-subscriber
UnkwownSubscriber unknown-subscriber
AbsentSubscriber absent-subscriber
SubscriberBusyForMT-SMS MS-busy-for-MT-SMS
SC - GMSC to MAP
sc-Congestion SM-Delivery-Failure (#4)
invalid-sme-address SM-Delivery-Failure (#5)
ms-not-sc-subscriber SM-Delivery-Failure (#6)
system failure SystemFailure
#0 memory capacity exceeded (MT only)
#1 equipment protocol error (MT only)
#2 equipment not SM equipped (MT only)
#4 SC-Congestion (MO only)
#5 invalid Sme address (MO only)
#6 Subscriber not SC Subscriber (MO only) |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 3 A Protocol Stack which utilises an Application-Network Layer convergence function for interconnecting SCs and MSCs | A convergence function (see Draft CCITT Recommendation Q.941 - Report R 22 May 1990) which maps an application entity protocol directly to the Network Layer service defined by X.213 can provide a practical alternative to ACSE, ROSE and OSI layers 6, 5 and 4 specified in Section 2.
Draft CCITT Recommendation Q.941 proposes to map application layer protocols ACSE and ROSE via a convergence function to network layers defined by CCITT Recommendations Q.931 and Q.932.
The complexity of dealing with the many different network layer protocols is avoided by mapping the application protocols to the Network Layer Service defined by X.213. ACSE and ROSE are specifically defined in terms of the full OSI stack. The use of ACSE and ROSE is avoided by incorporating the functionality provided by ACSE and ROSE into SMS protocols. The convergence function is therefore embedded in SMS protocols just as the use of ACSE and ROSE is embedded into SMS protocols defined by Section 2. |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 3.1 SMRSE Definition | The Short Message Service Relay Element (SMRSE) is defined in terms of the following service :
SMR - BIND:
This operation must be involved by the party which is responsible for establishing the application association ; only after the application association has been established may be remaining SMRSE services be used. This operation reports either success (via SMR-Bind-Confirm) or failure (via SMR-Bind-Failure).
SMR-BIND will be mapped to/from N-CONNECT request/indication with SMR-Bind parameters carried in NS-user-data (if the network layer does not support NS-user-data of 128 octets the SMR-Bind parameters may be carried by the first N-DATA request/indication following establishment of the network layer connection - see Section 3.4).
SMR-BIND-CONFIRM:
This operation must be invoked by a party to accept an application association.
SMR-BIND-CONFIRM will be mapped to/from N-CONNECT confirm/response with SMR-BIND-CONFIRM parameters carried in NS-user-data (if the network layer does not support NS-user-data of 128 octets then SMR-BIND-CONFIRM may be carried as the second N-DATA request/indication following establishment of the network layer connection - see Section 3.4).
SMR-BIND-FAILURE:
This operation must be invoked by a party to reject an attempted application association.
SMR-BIND-FAILURE will be mapped to/from N-DISCONNECT request/indication with SMR‑BIND‑FAILURE parameters carried in NS-user-data (if the network layer does not support NS‑user‑data of 128 octets then SMR-BIND-FAILURE parameters will not be carried by the network layer - i.e. NS‑user‑data will be discarded).
SMR-UNBIND:
This operation must be invoked by a party to release the application association.
SMR-UNBIND will be mapped to/from N-DISCONNECT request/indication with SMR-UNBIND parameters be carried in NS-user-data (if the network layer does not support NS-user-data of 128 octets then SMR-UNBIND parameters may be carried by the N-DATA request/indication preceding N-DISCONNECT - see Section 3.4).
SMR-MO-DATA:
This operation may be invoked by the application entity in the GMSC ; it is used to relay one SMS transfer layer PDU from the GMSC to the SC. This operation reports success (via RPAck) or failure (via RPError).
SMR-MO-DATA will be mapped to/from N-DATA request/indication.
SMR-MT-DATA:
This operation may be invoked by the application entity in the SC ; it is used to relay one SMS transfer layer PDU from the SC to the GMSC. This operation reports success (via RPAck) or failure (via RPError) after the full relay attempt to the MS.
SMR-MT-DATA will be mapped to/from N-DATA request/indication.
SMR-ALERT:
This operation may be invoked by the application entity in the GMSC. It is used as the GMSC-to-SC indication of the fact that an MS which was previously unattainable has recovered operation. This operation does not report any outcome.
SMR-ALERT will be mapped to/from N-DATA request/indication.
RPAck:
This operation is invoked by the application entity in the GMSC or the SC ; it is used as the GMSC-to-SC indication that a particular short message has been received by an MS and as the SC-to-GMSC indication that a short message has been received by the SC.
RPAck will be mapped to/from N-DATA request/indication.
RPError:
This operation is invoked by the application entity in the GMSC or the SC ; it is used as the GMSC-to-SC indication that a particular short message has not been successfully received by an MS and is needed as the SC-to-GMSC indication that a short message has not been successfully received by the SC.
RPError will be mapped to/from N-DATA request/indication. |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 3.2 ASN1 Specification | The Abstract Syntax Notation of
the Short Message Relay Service Element
SMRSE
NOTE: The first two arcs of the object identifier are arbitrarily allocated, the name "etsi" is adopted from GSM 12.20 but the value 040 is arbitrary, and the last three arcs are allocated in this module.
1st module of 2:
SMS-UsefulDefinitions
SMS-usefulDefinitions { iso identified-organization etsi(040)
mobile-domain(0) gsm-messaging(4)
gsm-sms2(11) usefullDefinitions(0) }
DEFINITIONS
IMPLICIT TAGS
::=
BEGIN
IMPORTS
ID ::= OBJECT IDENTIFIER
-- root for all sms allocations
mobile-domain ID ::= {iso identified-organization etsi(40) mobile-domain(0) }
gsm-messaging
ID ::= { mobile-domain gsm-messaging(4) }
-- categories
gsm-sms2 ID ::= { gsm-messaging 11}
-- modules
usefullDefinitions ID::= {gsm-sms2 0}
relayProtocol ID::= {gsm-sms2 1}
END
2nd module of 2
RelayProtocol
RelayProtocol { iso identified-organization etsi(040)
mobile-domain(0) gsm-messaging(4) gsm-sms2(11)
relayprotocol(1) }
DEFINITIONS
IMPLICIT TAGS
::=
BEGIN
-- EXPORTS everything
-- The SMR-Bind-Parameters will be the User Data field in the N-CONNECT request/indication
-- message.
SMR-Bind-Parameters ::= SEQUENCE {
initiatorID [0] Name,
password [1] Password OPTIONAL,
pswNeeded [2] BOOLEAN,
iniType [3] Telecom-System-Type
}
-- Above and in SMR-Bind-confirm
-- initiatorID/respID identify the initiating/responding telecommunication subsystem
-- password may assist in authentification
-- pswneeded (BIND only) requests password into SMR-Bind SMR-Bind-confirm
-- initype/resptype identify the types of the systems
-- transient (CONFIRM only) forces the association (and the underlying connections) transient : it must be UNBouND as soon as there are no operations to be performed
Name ::= SEQUENCE {
operator [0] Operator OPTIONAL,
bilateralAgreem [1] BilateralAgreem OPTIONAL,
dataNetworkAddress [2] X121Address OPTIONAL,
iSDN Address SMS-Address OPTIONAL
}
-- operator is a text string containing the name of the SC/PLMN operator. bilateralagreem is a text
-- string identifying the bilateral agreement between the SC and the PLMN operators which allows
-- for this association to be established.
-- dataNetworkAddress is the PSPDN X.121 address of the SC/MSC issuing the BIND or
-- CONFIRM, occurring only if a PSPDN is used.
-- iSDNAddress is the PLMN address of the SC as seen by the MSs (same datum in both BIND
-- and CONFIRM).
-- Any pair of subsets of theses parameters may be used to identify the SC and the MSC to one
-- another.
-- upper bound settings
ub-operator-name-length INTEGER ::= 20
ub-agreem-name-length INTEGER ::= 20
ub-X121Address-length INTEGER ::= 15
ub-password-length INTEGER ::= 20
Operator ::= PrintableString (SIZE (0..ub-operator-name-length))
BilateralAgreem ::= PrintableString (SIZE (0..ub-agreem-name-length))
X121Address ::= NumericString (SIZE (0..ub-X121Address-length))
-- Definition of Short Message Service address
SMS-Address ::= [APPLICATION 0] SEQUENCE {
adress-type INTEGER { unknown-type (0),
international-number (1),
national-number (2),
network-specific-number (3),
short-number (4) },
numbering-plan INTEGER {unknown-numbering (0),
iSDN-numbering (1),
data-network-numbering (3),
telex-numbering (4),
national-numbering (8),
private-numbering (9) },
address-value CHOICE {
octet-format
SemiOctetString
-- other formats are for further study
}
}
-- each octet contains two binary coded decimal digits
SemiOctetString ::= OCTET STRING (SIZE (1..10))
Password ::= PrintableString(SIZE(0..ub-password-length))
Telecom-System-Type ::= INTEGER {
short-Message-Service-Centre (0),
public-Land-Mobile-Network (1)
-- Extensions are possible: additional telecommunication subsystems
-- might adopt this service element for their interconnection.
}
-- SMR-Bind-confirm will be the User Data in the N-CONNECT response/confirm message
SMR-Bind-confirm ::= SEQUENCE {
respID [0] Name,
password [1] Password OPTIONAL,
respType [3] Telecom-System-Type,
transient [5] BOOLEAN,
connectTime [6] Time-when-connected
}
-- The following defines the choices and tags for the N-DISCONNECT request/indication User Data.
RELAYdiscs ::= CHOICE {
bindfail [1] SMR-Bind-failure,
unbindreq [2] SMR-Unbind
}
SMR-Bind-failure ::= SEQUENCE {
connect-failure-reason
[0] Connect-failure,
alternative-system
[1] Name OPTIONAL
}
-- connect-failure-reason contains one of the error given in the following table. alternative-system
-- is included when the SC/PLMN operator wishes to indicate that the MSC/SC might try to
-- establish an association with another SC/MSC.
-- Connection Failure Reason
-- not-entitled: The responder is not entitled to accept a request for an association between itself
-- and the initiator.
-- temporary-overload: The responder is not capable of establishing an association due to
-- temporary overload.
-- temporary-failure: The responder is not capable of establishing an association due to a
-- temporary failure (having impact on an entity at SM-RL or at layers above).
-- incorrect-ID-or-password: The responder will not accept the request to establish an association
-- between itself and the initiator due to incorrect identity or password.
-- not-supported: The responder does not recognize the telecommunication subsystem type of the
-- initiator, or cannot support any of the operations suggested on the association.
Connect-failure ::= INTEGER {
not-entitled (0),
temporary-overload (1),
temporary-failure (2),
incorrect-ID-or-password (3),
not-supported (4)
}
SMR-Unbind ::= Time-when-connected
Time-when-connected ::= UTCTime
-- The following defines the choices and tags for the N-DATA request/indication User Data
RELAYapdus ::= CHOICE {
rpdatamt [1] RPDataMT,
rpdatamo [2] RPDataMO,
rpalertsc [3] RPAlertSC,
rpack [4] RPAck,
rperror [5] RPError
}
RPDataMT ::= SEQUENCE {
mt-priority-request [0] BOOLEAN,
mt-more-messages-to-send [1] BOOLEAN OPTIONAL,
mt-message-reference RP-MR,
mt-originating-address SMS-Address,
mt-destination-address SMS-Address,
mt-user-data RP-UD
}
RPDataMO ::= SEQUENCE {
mo-message-reference RP-MR,
mo-originating-address SMS-Address,
mo-user-data RP-UD
}
RP-MR ::= [APPLICATION 2] INTEGER (0..255)
RP-UD ::= [APPLICATION 3] OCTET STRING (SIZE (1..164))
RPAck ::= SEQUENCE {
message-reference RP-MR
}
Error-reason ::= INTEGER {
unknown-subscriber (1),
teleservice-not-provisioned (11),
call-barred (13),
sMS-lower-layer-capabilities-not-prov (19),
error-in-MS (20),
facility-not-supported (21),
memory-capacity-exceeded (22),
absent-subscriber (29),
illegal-subscriber (9),
illegal-equipment (44),
system-failure (36),
sC-congestion (101),
mS-not-SC-Subscriber (103),
invalid-sme-address (104)
}
RPError ::= SEQUENCE {
error-reason Error-reason,
msg-waiting-set BOOLEAN,
message-reference RP-MR
}
RPAlertSC ::= SMS-Address
-- must be an international ISDN address
END |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 3.3 Application Rules for Avoidance of Collision of SMRSE Operations | For the purpose of establishing the association between SMRSEs in MSC and SC then either the MSC or the SC shall be designated as the entity responsible for initiating the association by the operation SMR‑Bind.
Following premature release of the association by N-DISCONNECT then either the MSC or the SC shall be designated as the entity responsible for re-establishing the association.
Following receipt of N-RESET any unacknowledged SMR-MT-DATA or SMR-MO-DATA will be retransmitted. |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 3.3.1 Semi-permanent Connections | On a semi-permanent connection the SMR-UNBIND operation is not normally invoked following an application association. |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 3.3.2 Transient Connection | In a situation where an SC has several connections to an MSC, or an MSC has several connections to MSCs, and a public data network connection may be maintained for the duration of the relay and/or alert operations the association may be ended via SMR-UNBIND as soon as all operations on the association have been completed via RPAck or RPError and by some guard timer being applied following SMR‑ALERT. |
91e934a3a02c6481be36d5ef0f1f6c4b | 03.47 | 3.4 Non Support of 128 bytes of NS-user-data in Network Connection and Network Connection Release phases | It is generally intended to make the support of 128 bytes of NS-user-data mandatory (see Sections 12.2.8 and 13.2.3 of X.213). CCITT Recommendation X.2 regards provision of Fast Select as essential, thereby ensuring support of 128 bytes of NS-user-data in network connection and network connection release phases will remain a provider option. The following figures are therefore provided in order to indicate how SMR-BIND, SMR-BIND-CONFIRM and SMR-UNBIND should be mapped to/from an OSI Network Service definition which support 128 bytes of NS-user-data in network connection and network connection release phases.
NOTE 1: SMR-BIND parameters are carried as NS-user-data
NOTE 2: SMR-BIND-CONFIRM is carried in NS-user-data
NOTE 3: SMR-UNBIND parameters are carried as NS-user-data |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.