《ISO-14845-1996.pdf》由会员分享，可在线阅读，更多相关《ISO-14845-1996.pdf（79页珍藏版）》请在三一文库上搜索。
1、INTERNATIONAL STANDARD ISO/IEC 14845 First edition 1996-09-I 5 Information technology - Telecommunications and information exchange between systems - Private Integrated Services Network - Specification, functional model and information flows - Call intrusion supplementary service Technologies de /in
2、formation - T l Isolation, allowing the served user, if a conference type connection has been established, to isolate user C; l Wait on busy, allowing the served user to cause a transition from the intrusion state to the wait on busy state. 6.1.2 Qualifications on applicabiiity to telecommunication
3、services SS-CI is applicable to all basic services defined in ISO/IEC 11574. 6.2 Procedures 6.2.1 Provision/withdrawal SS-CI shall be provided or withdrawn after prearrangement with the service provider. SS-CI shall be provided on a per PISN number basis. For each PISN number, the supplementary serv
4、ice may be provided for those basic services for which it is considered meaningful (see 6.1.2) provided at that PISN number or for only some of these basic services provided at that PISN number. A Call Intrusion Capability Level (CICL) shall be allocated to the served user. Call Intrusion Protection
5、 Levels (CIPLs) shall be allocated to potential individual users B and C within the PISN and to gateways to other networks (for use on behalf of users outside the PISN). The procedure by which CICL and CIPL are allocated is outside the scope of this International Standard. CICL shall have a value in
6、 the range 1 (lowest capability) to 3 (highest capability). At least one of the CICL values shall be offered. CIPL shall have a value in the range 0 (no protection) to 3 (total protection). CIPL values 0 and 3 shall be offered, and values 1 and 2 may, as an implementation option, be offered. Note -
7、It is not precluded that CIPL values can be variable, e.g. a user may have the possibility to change the CIPL value with a user procedure. CIPL values assigned to gateways may also be variable. e.g. depending on whether the gateway is used for an incoming or outgoing call to the PISN. The details of
8、 such capabilities are outside the scope of this International Standard. At least one of the methods of invoking SS-CI (see 6.2.2.2.1) shall be supported. If both methods given in 6.2.2.2.1 are supported, then a user may be provided with one or both methods. A number of implementation options concer
9、n features available to the served user during call intrusion. The served user may, at time of provision of SS-CI, be given the choice of being provided with some, all or none of these or the options may be generally available. These implementation options are: forced release, isolation, and wait on
10、 busy. When these options are selectable on a per served user basis, they may be selectable separately for each basic service for which SS-CI is provided, or selectable only for all basic services for which SS-CI is provided. 6.2.2 Normal procedures 6.2.2.1 Activatiouldeactivatiouh-egistrationhnterr
11、ogation SS-CI shall be activated by the service provider upon provision, and deactivated upon withdrawal. Registration and interrogation shall not apply. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bern
12、ie Not for Resale, 04/04/2007 08:59:11 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IRC 148451996 (E) OISO/IEC 6.2.2.2 Invocation and operation 6.2.2.2.1 Methods of invoking SS-CI There are two different ways to invoke SS-CI. A PISN shall offer one or both of these w
13、ays. These ways are: i) Consultation: the served user, on being informed that a call has failed because of busy at the destination, shall be able, within a defined period (consultation timer), to request SS-CI. ii) Immediate invocation: the served user shall be able to request SS-CI as part of the i
14、nitial call set up. 6.2.2.2.2 Verification and selection of compatible call If the consultation method is provided to the served user, the following procedure shall apply. If a call fails due to busy at the called user B and the PISN is not aware that intrusion is not allowed (e.g. because of insuff
15、icient CICL), the PISN shall notify the served user that the call has failed because of busy at the called user B and that intrusion may be possible. The served user may then request SS-CI. If the immediate invocation method is provided to the served user, the served user may request SS-CI with the
16、initial call set up. For both invocation alternatives the following shall apply. Upon receiving an intrusion invocation request from the served user, the PISN shall check that the user Bs number used by the served user, when requesting the service, is also a number involved in a compatible call in t
17、he active state. A called users subaddress supplied by the served user shall not be taken into account when selecting a call to intrude on. Further, the PISN checks that the CIPL values of the users in the active call are lower than the CICL value of the served user. If user Bs CIPL value is lower t
18、han the CICL value and user B has several compatible calls in the active state, the CIPL values of the other users in the calls shall be checked, in any order, until a CIPL value lower than the CICL value is found. A call that passes these checks shall be selected as the established call. When the e
19、stablished call has been selected, the users in the established call may as an option be provided with an Impending intrusion warning notification and a short delay (not exceeding 10s) before the connection between the served user and user B is formed. If this notification is provided, it shall be s
20、ent to both users in the established call and optionally to the served user and the impending intrusion state shall be entered. Note - The Impending intrusion warning notification can be accompanied by an in-band tone or announcement to user B and user C. An in-band tone or announcement can be given
21、 to the served user. If no Impending intrusion warning notification is provided, the procedures of 6.2.2.2.4 for setting up the connection between the served user and user B shall apply immediately. 6.2.2.2.3 Actions during impending intrusion state 6.2.2.2.3.1 Impending intrusion state ends A time
22、period, time to intrusion (l-10 seconds, implementation option), after the Impending intrusion warning notification has been provided the impending intrusion state shall be terminated and the procedures of 6.2.2.2.4 for setting up the connection between the served user and user B shall apply. 6.2.2.
23、2.3.2 Release of intruding caii If the served user releases the intruding call during the impending intrusion state, user B and user C shall each be notified that intrusion has terminated. SS-CI shall be terminated. 6.2.2.2.3.3 Release of established tail If user B or user C releases the established
24、 call, the served user shall be notified that intrusion is no longer applicable. SS-CI shall be terminated and the network shall attempt to present the call from the served user to user B and continue in accordance with basic call procedure. 6.2.2.2.4 Setting up the connection between served user, u
25、ser B and user C There are two different ways (implementation options) for the served user to be connected to user B. Either the network shall form a conference type connection between user B, user C and the served user, or the network shall isolate user C and connect the served user only to user B.
26、 In either case, when the connection has been established, the intrusion state shall be entered. If the first option is implemented, the users in the established call shall be provided with an Intruding call connected notification when the served user is connected. The served user shall receive conf
27、irmation that the intrusion request has been accepted and that a conference type connection has been formed. Note - The three users can also receive a superimposed in-band indication (e.g. a repeated tone) while the conference type connection exists. 6 Copyright International Organization for Standa
28、rdization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/04/2007 08:59:11 MDTNo reproduction or networking permitted without license from IHS -,-,- OISOKIEC ISO/IEC 14845: 1996 (El If the latter option is implemented, user C shall be gi
29、ven a notification that isolation has occurred and user B shall be informed that user C has been isolated and that an intrusion has occurred. The served user shall receive confirmation that the intrusion request has been accepted and that isolation has occurred. The served user and user B shall be c
30、onnected and no conference type connection shall be formed. The established call shall remain in progress but with the user information connection to user C broken. Note - User C can also receive an in-band tone or announcement while isolated. Note - The option selected can depend on the particular
31、basic service being used. 6.2.2.2.5 Actions during intrusion state 6.2.2.2.5.1 Release of intruding call If the served user releases the intruding call, the established call shall revert to the state that existed before the intrusion state, and the intrusion state shall be terminated. User B and use
32、r C shall be notified that the intrusion state has been terminated. If user B releases the intruding call, the established call shall revert to the state that existed before the intrusion state, and the intrusion state shall be terminated. User C shall be notified that the intrusion state has termin
33、ated. 6.2.2.2.5.2 Release of the established call If user B or user C releases the established call, the served user shall be notified that call intrusion has terminated. If user C releases the established call, user B shall be notified that intrusion has terminated. The intruding call shall become
34、an ordinary call between user B and the served user. 6.2.2.2.5.3 Forced release As an implementation option the served user may, during the intrusion state, request a forced release of user C. User C may be isolated or in a conference type connection when the request is made. A successful forced rel
35、ease shall be notified to the served user, to user B and to user C. The intruding call shall continue as an ordinary call between the served user and user B, the established call shall be released, and the intrusion state shall be terminated. 6.2.2.2.5.4 Isolation on request from served user If a co
36、nference type connection is used, user C may (implementation option) be isolated from the conference type connection on request from the served user. If the request is accepted the served user shall receive confirmation and the established call shall be disconnected from user B, but not released. Th
37、e served user shall be connected only to user B. The intrusion state shall continue and the ensuing situation shall be identical to the situation where isolation occurred when the intrusion state was entered. User C and user B shall be notified that user C has been isolated. 6.2.2.2.5.5 Transition f
38、rom intrusion state to wait on busy state As an implementation option it may be possible for the served user to request transition from the intrusion state to the wait on busy state. On acceptance of such a request, the served user shall receive a confirmation, the established call shall revert back
39、 to the state that existed before intrusion, user B shall be reconnected to user C if isolated, the intruding call shall be disconnected from user B and the intrusion state shall be terminated. The intruding call shall not be released but shall enter the wait on busy state. User B shall be notified
40、that the intrusion has terminated and wait on busy has been invoked. User C shall be notified that the intrusion has terminated. 6.2.2.2.6 Actions during wait on busy state 6.2.2.2.6.1 Served user releases If the served user releases during the wait on busy state, user B shall be notified and SS-CI
41、terminated. 6.2.2.2.6.2 User B answers the waiting call If user B answers the waiting call, SS-CI shall be terminated, and the served user shall be notified and connected to user B. The call shall become an ordinary call between user B and the served user. 6.2.2.2.6.3 Re-intrusion request When the n
42、etwork receives a request for re-intrusion, the network shall verify the request and select an established call in accordance with 6.2.2.2.2 and set up the connection in accordance with 6.2.2.2.3 (if applicable) and 6.2.2.2.4. 6.2.2.2.6.4 User B becomes not busy If the PISN detects that the necessar
43、y resources have become available, it shall transfer an incoming call indication to user B. If user B starts alerting, the served user shall receive an appropriate indication. 7 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/111
44、1111001, User=Wing, Bernie Not for Resale, 04/04/2007 08:59:11 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 14845:1996 Q OISO/IEC 6.2.3 Exceptional procedures 6.2.3.1 Activationfdeactivationhegistrationfinterrogation Not applicable. 6.2.3.2 Invocation and operati
45、on If the served user requests invocation of SS-CI as part of the initial call request, and immediate invocation is not provided to the served user, then the request shall be ignored and the call shall proceed as if the request had not been made. If a SS-CI or re-intrusion request is rejected, the s
46、erved user shall be informed, and may be given an indication of the reason for the rejection. Possible reasons to reject a SS-CI or re-intrusion request are e.g.: - served user has a lower or equal CICL compared with user Bs and/or user Cs CIPL value; - user B is busy but not involved in a compatibl
47、e call in the active state; - temporary lack of resources; - the established call is already being intruded upon; - the established call is intruding on another call. If SS-CI is requested and user B is found to be not busy, the call shall be treated as a normal incoming call to user B. If a forced
48、release, isolate or wait on busy request from the served user is denied by the PISN, the served user shall be notified and may be given an indication for the reason of the denial. The intrusion state shall remain. If an intrusion request from the wait on busy state is rejected, the wait on busy stat
49、e shall remain. If consultation applies to the call, the call shall be released either if the served user does not request invocation within the defined time period (consultation timer) or if the served user requests invocation within the defined time period (consultation timer) and this request is rejected. Consultation shall not apply if the called user is busy and the PISN is aware that intrusion is not allowed. Basic call procedures shall apply. 6.3 Inte