S tandard ECMA-241
4th Edition - February 2002
Standardizing Information
and
Communication
Systems
Private Integrated Services Network (PISN) Specification, Functional Model and Information Flows Message Waiting Indication Supplementary Service
Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: [email protected]
.
S tandard ECMA-241
4th Edition - February 2002
Standardizing Information
and
Communication
Systems
Private Integrated Services Network (PISN) Specification, Functional Model and Information Flows Message Waiting Indication Supplementary Service (MWISD)
Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: [email protected] IW
Ecma-241.doc
07-02-02 14,46
.
Brief History
This Standard is one of a series of ECMA Standards defining services and signalling protocols applicable to Private Integrated Services Networks (PISNs). The series uses ISDN concepts as developed by ITU-T and conforms to the framework of International Standards for Open Systems Interconnection as defined by ISO/IEC. This particular Standard specifies the Message Waiting Indication supplementary service. This Standard is based upon the practical experience of ECMA member companies and the results of their active and continuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and other international and national standardization bodies. It represents a pragmatic and widely based consensus. Compared to the 2nd Edition of Standard ECMA-241 (published by ECMA in September 1997), the 3rd Edition incorporated changes to allow indication of multimedia messages.
Adopted as 4th Edition of Standard ECMA-241 by the General Assembly in February 2002.
.
- i -
Table of contents 1
Scope
1
2
Conformance
1
3
References (normative)
1
4
Definitions 4 . 1 E x te r n a l d e f in itio n s 4 . 2 O th e r d e f in itio n s 4.2.1 Served User 4.2.2 Me s s a g e Ce n tr e 4.2.3 Me s s a g e W a itin g I n d ic a tio n
1 1 2 2 2 2
5 6
List of acronyms SS-MWI stage 1 specification 6 . 1 D e s c r ip tio n 6.1.1 G e n e r a l d e s c r ip tio n 6.1.2 Q u a l i f i c a t i o n s o n a p p l i c a b i l i t y t o t e l e c o mmu n ic a t i o n s e r v i c e s 6.2 Procedures 6.2.1 P r o v is io n / w ith d r a w a l 6.2.2 N o r ma l p r o c e d u r e s 6.2.3 E x c e p tio n a l p r o c e d u r e s 6 . 3 I n t e r a c t i o n s w i t h o t h e r S u p p l e me n t a r y S er v i c e s / A d d i t i o n a l N e t w o r k F e a t u r e s 6.3.1 A d v ic e o f Ch a r g e ( A O C) 6.3.2 Call Deflection (CD) 6.3.3 Ca ll F o r w a r d in g U n c o n d itio n a l ( CF U ) 6.3.4 Call Forwarding Busy (CFB) 6.3.5 Ca ll F o r w a r d in g N o Re p ly ( CF N R) 6.3.6 Call Interception (CINT) 6.3.7 Call Intrusion (CI) 6.3.8 Call Offer (CO) 6.3.9 Call Transfer (CT) 6.3.10 Ca llin g /Co n n e c te d L in e I d e n tif ic a tio n Re s tr ic tio n ( CL I R) 6.3.11 Ca llin g /Co n n e c te d N a me I d e n tif ic a tio n Re s tr ic tio n ( CN I R) 6.3.12 Calling Line Identification Presentation (CLIP) 6.3.13 C a l l i n g N a me I d e n t i f i c a t i o n P r e s e n t a t i o n ( C N I P ) 6.3.14 C o n n e c t e d L i n e I d e n t i f i c at i o n P r e s e n t a t i o n ( C O L P ) 6.3.15 C o n n e c t e d N a me I d e n t i f i c at i o n P r e s e n t a t i o n ( C O N P ) 6.3.16 C o mp l e t i o n o f C a l l s t o B u s y S u b s c r i b e r s ( C C B S ) 6.3.17 C o mp l e t i o n o f C a l l s o n N o R e p ly ( C C N R ) 6.3.18 Do Not Disturb (DND) 6.3.19 Do Not Disturb Override (DNDO) 6.3.20 P a t h R e p l a c e me n t ( P R ) 6.3.21 Recall (RE)
2 2 2 2 2 3 3 3 3 3 3 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
- ii -
7
6.3.22 R o u te R e s t r i c t i o n C l a s s ( R R C ) 6.3.23 W ir e l e s s T e r mi n a l L o c a t io n Re g is tr a tio n ( W T L R) 6.3.24 W ir e l e s s T e r mi n a l M o b i l i t y I n c o min g C a l l ( W T M I ) 6.3.25 W ir e l e s s T e r mi n a l M o b i l i t y O u t g o in g C a l l ( W T M O ) 6.3.26 Authentication of a WTM user (WTAT) 6.3.27 Authentication of the PISN (WTAN) 6 . 4 I n te r w o r k in g c o n s id e r a tio n s 6.5 Overall SDL
4 5 5 5 5 5 5 5
SS-MWI stage 2 specification 7 . 1 F u n c tio n a l mo d e l 7.1.1 F u n c tio n a l mo d e l d e s c r ip tio n 7.1.2 Description of Functional Entities 7.1.3 Re la tio n s h ip o f f u n c tio n a l mo d e l to Ba s ic Ca ll f u n c tio n a l mo d e l 7 . 2 I n f o r ma t i o n f l o w s 7.2.1 D e f in itio n o f in f o r ma tio n f lo w s 7.2.2 Re la tio n s h ip o f in f o r ma tio n f lo w s to Ba s ic Ca ll in f o r ma tio n f lo w s 7.2.3 I n f o r ma tio n f lo w s e q u e n c e s 7.3 Functional Entity actions 7.3.1 Functional Entity actions of FE1 7.3.2 Functional Entity actions of FE2 7 . 4 F u n c t i o n a l E n t i t y b e h a v io u r 7.4.1 Be h a v io u r o f F E 1 7.4.2 Be h a v io u r o f F E 2 7 . 5 A l l o c a t i o n o f F u n c t i o n a l E n t i t i e s t o p h ys i c a l e q u ip me n t 7 . 6 I n te r w o r k in g c o n s id e r a tio n s
9 9 9 9 9 9 9 12 13 15 15 15 16 16 17 18 18
1
Scope This Standard specifies supplementary service Message Waiting Indication (SS-MWI), which is related, but not limited, to various basic services supported by Private Integrated Services Networks (PISNs). Basic services are specified in ECMA-142. This supplementary service MWI enables a Served User to be sent a Message Waiting Indication and also enables this Message Waiting Indication to be cancelled. Service specifications are produced in three stages, according to the method described in ETS 300 387. This Standard contains the stage 1 and stage 2 specifications of SS-MWI. The stage 1 specification (clause 6) specifies the supplementary service as seen by users of PISNs. The stage 2 specification (clause 7) specifies the functional entities involved in the supplementary service and the information flows between them.
2
Conformance In order to conform to this Standard, a stage 3 standard shall specify signalling protocols and equipment behaviour that are capable of being used in a PISN which supports the supplementary service specified in this Standard. This means that, to claim conformance, a stage 3 standard is required to be adequate for the support of those aspects of clause 6 (stage 1) and clause 7 (stage 2) which are relevant to the interface or equipment to which the stage 3 standard applies.
3
References (normative) The following standards contain provisions which, through reference in this text, constitute provisions of this Standard. All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. In the case of references to ECMA Standards that are aligned with ISO/IEC International Standards, the number of the appropriate ISO/IEC International Standard is given in brackets after the ECMA reference. ECMA-133
Private Integrated Services Network (PISN) - Reference Configuration for PISN Exchanges (PINX) (International Standard ISO/IEC 11579-1)
ECMA-142
Private Integrated Services Network (PISN) - Circuit Mode 64kbit/s Bearer Services Service Description, Functional Capabilities and Information Flows (International Standard ISO/IEC 11574)
ETS 300 387
Private Telecommunication Network (PTN); Method for the specification of basic and supplementary services (1994)
ITU-T Rec. I.112
Vocabulary of terms for ISDNs (1993)
ITU-T Rec. I.210
Principles of telecommunication services supported by an ISDN and the means to describe them (1993)
ITU-T Rec. Z.100 Specification and description language (1999)
4
Definitions For the purposes of this Standard, the following definitions apply:
4.1
External definitions This Standard uses the following terms defined in other documents: − Basic Service
(ITU-T Rec. I.210)
− Private Integrated services Network eXchange (PINX)
(ECMA-133)
− Private Integrated Services Network (PISN)
(ECMA-133)
− Service
(ITU-T Rec. I.112)
- 2 -
4.2
− Signalling
(ITU-T Rec. I.112)
− Supplementary Service
(ITU-T Rec. I.210)
− User
(ECMA-142)
Other definitions
4.2.1
Served User The user to whom the Message Waiting Indication is sent on initiative of the Message Centre.
4.2.2
Message Centre The entity which activates or deactivates the Message Waiting Indication as a result of the storage or retrieval of messages.
4.2.3
M e s s a g e W a it in g I n d ic a t io n An indication to the Served User when messages are waiting for the Served User. NOTE The indication may be a lamp, special tone, display etc. This is outside the scope of this Standard.
5
List of acronyms
6
ANF
Additional Network Feature
FE
Functional Entity
ISDN
Integrated Services Digital Network
MWI
Message Waiting Indication
PINX
Private Integrated services Network eXchange
PISN
Private Integrated Services Network
SDL
Specification and Description Language
SS
Supplementary Service
SS-MWI stage 1 specification
6.1 6.1.1
Description General description The supplementary service MWI enables a Served User to be sent a Message Waiting Indication and also enables this Message Waiting Indication to be cancelled. NOTE The Message Waiting Indication is sent on activation by the Message Centre. NOTE The Message Waiting Indication is cancelled on deactivation by the Message Centre. A Served User can receive separate MWIs for each of the services for which there is a message waiting. NOTE A service for which there is a message waiting would normally use the related basic service to retrieve that message.
6.1.2
Qualifications on applicability to telecommunication services This supplementary service does not apply directly to any basic telecommunication service. However, a MWI relates to a basic service for which there are messages waiting.
- 3 -
6.2
Procedures
6.2.1
P r o v is io n / wit h d r a wa l SS-MWI may be provided or withdrawn after pre-arrangement with the service provider or may be generally available to all users.
6.2.2 Normal procedures 6.2.2.1 A c t iv a t io n , d e a c t iv a t io n a n d in t e r r o g a t io n The PISN shall provide activation / deactivation by the Message Centre. In addition, the PISN may provide interrogation by the Served User. To activate SS-MWI, the Message Centre shall supply the PISN number and the service for which there is a message waiting and may, as an implementation option, add any combination of the following pieces of information: the identity of the Message Centre; the number of messages waiting for the Served User for that service; the address of the user that left a message; the time when a message was left; the priority of the highest priority message waiting for that service. After activation, SS-MWI may be activated again whenever the number of waiting messages changes. To deactivate SS-MWI, the Message Centre shall supply the PISN number and the service for which there is no longer a message waiting. As a result of activation, a MWI shall be sent to the Served User. The MWI may include information on messages waiting, if provided by the Message Centre. As a result of deactivation, the MWI at the Served User, for the service concerned, shall be cancelled. When the Message Centre activates or deactivates SS-MWI at the Served User, it shall be provided with an indication of acceptance. When the Served User interrogates SS-MWI for a particular service, the Message Centre shall provide the Served User with an indication of whether SS-MWI is activated for that service and may add, as an implementation option, any of the following information: • the identity of the Message Centre; • the number of messages waiting; • the address of the user that left a message; • the time when a message was left; • the priority of the highest priority message waiting. When the Served User interrogates SS-MWI for all services, the Message Centre shall provide the Served User with a list of services for which SS-MWI is active and, as an implementation option, for each service, any of the additional information listed above. 6.2.2.2
I n v o c a t io n a n d o p e r a t io n Not applicable.
6.2.3 Ex c e p t io n a l p r o c e d u r e s 6.2.3.1 A c t iv a t io n , d e a c t iv a t io n a n d in t e r r o g a t io n If the Served User cannot accept activation or deactivation, then the Message Centre shall be informed and may also be given the reason. If the PISN cannot accept interrogation, then the Served User shall be informed and may also be given a reason. 6.2.3.2
6.3
I n v o c a t io n a n d o p e r a t io n None.
Interactions with other Supplementary Services / Additional Network Features Interactions with other supplementary services and ANFs for which PISN standards were available at the time of publication of this Standard are specified below.
6.3.1
A d v ic e o f C h a r g e ( A O C ) No interaction.
- 4 -
6.3.2
Call Deflection (CD) No interaction.
6.3.3
C a ll F o r wa r d in g U n c o n d it io n a l ( C F U ) No interaction.
6.3.4
C a ll F o r wa r d in g Bu s y ( C F B) No interaction.
6.3.5
C a ll F o r wa r d in g N o R e p ly ( C F N R ) No interaction.
6.3.6
Call Interception (CINT) No interaction.
6.3.7
C a ll I n t r u s io n ( C I ) No interaction.
6.3.8
C a ll O f f e r ( C O ) No interaction.
6.3.9
C a ll Tr a n s f e r ( C T) No interaction.
6.3.10
C a l l i n g /C o n n e c t e d L i n e I d e n t i f i c a t i o n R e s t r i c t i o n ( C L I R ) No interaction.
6.3.11
C a l l i n g /C o n n e c t e d N a m e I d e n t i f i c a t i o n R e s t r i c t i o n ( C N I R ) No interaction.
6.3.12
Calling Line Identification Presentation (CLIP) No interaction.
6.3.13
Calling Name Identification Presentation (CNIP) No interaction.
6.3.14
C o n n e c t e d Lin e I d e n t if ic a t i o n P r e s e n t a t i o n ( C O L P ) No interaction.
6.3.15
Connected Name Identification Presentation (CONP) No interaction.
6.3.16
Completion of Calls to Busy Subscribers (CCBS) No interaction.
6.3.17
Completion of Calls on No Reply (CCNR) No interaction.
6.3.18
Do Not Disturb (DND) No interaction.
6.3.19
Do Not Disturb Override (DNDO) No interaction.
6.3.20
Path Replacement (PR) No interaction.
6.3.21
R e c a ll ( R E) No interaction.
6.3.22
Route Restriction Class (RRC) No interaction.
- 5 -
6.3.23
Wireless Terminal Location Registration (WTLR) No interaction. NOTE A MWI may be directed to the new location.
6.3.24
Wireless Terminal Mobility Incoming Call (WTMI) No interaction.
6.3.25
Wireless Terminal Mobility Outgoing Call (WTMO) No interaction.
6.3.26
A u t h e n t ic a t io n o f a W TM u s e r ( W TA T) No interaction.
6.3.27
A u t h e n t ic a t io n o f t h e P I S N ( W TA N ) No interaction.
6.4
Interworking considerations A PISN may be able to accept MWIs from a Message Centre in another network. In this case, the PISN may also be able to interrogate that Message Centre. A PISN may be able to send MWIs to a Served User in another network. In this case, the PISN may also be able to accept interrogation requests from that Served User.
6.5
Overall SDL Figure 1 contains the dynamic description of SS-MWI using the Specification and Description Language (SDL) defined in ITU-T Rec. Z.100 (1999). The SDL process represents the behaviour of the network in providing SS-MWI. Input signals from the left and output signals to the left represent primitives from and to the Message Centre. Input signals from the right and output signals to the right represent primitives from and to the Served User.
- 6 -
MWI-Idle
Activate MWI
Activation possible? Yes
No
Send MWI
Reject activation
Confirm activation
MWI-Idle
MWI-Idle Figure 1 (part 1) - SS-MWI Overall SDL
- 7 -
MWI-Idle
Deactivate MWI
Deactivation possible? Yes
No
Cancel MWI at Served User
Reject deactivation
Confirm deactivation
MWI-Idle
MWI-Idle Figure 1 (part 2) - SS-MWI Overall SDL
- 8 -
MWI-Idle
Interrogate MWI
Interrogation possible? Yes
No
Send MWI Status
Reject interrogation
MWI-Idle
MWI-Idle
Figure 1 (part 3) - SS-MWI Overall SDL
- 9 -
7
SS-MWI stage 2 specification
7.1
Functional model
7.1.1
Functional model description The functional model shall comprise the following Functional Entities (FEs): FE1
Message Centre's control entity;
FE2
Served User's control entity.
The following relationship shall exist between these FEs: ra
between FE1 and FE2.
Figure 2 shows these FEs and this relationship.
FE1
ra
FE2
Figure 2 - Functional model for SS-MWI 7.1.2 D e s c r ip t io n o f F u n c t io n a l En t it ie s 7.1.2.1 M e s s a g e C e n t r e c o n t r o l e n t it y , F E1 This Functional Entity:
7.1.2.2
7.1.3
7.2 7.2.1
-
sends an activation / deactivation request to FE2 on initiative of the Message Centre;
-
receives the result of the activation / deactivation request from FE2 and informs the Message Centre of the result;
-
receives the interrogation request from FE2;
-
checks if the interrogation request is allowed to be performed;
-
sends the status of the Message Waiting Indication to FE2, in the case of interrogation.
Served User's control entity, FE2 This Functional Entity: -
receives the activation / deactivation request from FE1;
-
checks if the activation / deactivation request is allowed to be performed;
-
sends the result of the activation / deactivation request to FE1;
-
sends the interrogation request to FE1;
-
receives the status of the Message Waiting Indication from FE1, in the case of interrogation;
-
sends/cancels MWIs to/at the Served User.
R e la t io n s h ip o f f u n c t io n a l m o d e l t o Ba s ic C a ll f u n c t io n a l m o d e l Not applicable.
Information flows D e f in it io n o f in f o r m a t io n f lo ws In the tables listing the elements in information flows, the column headed "Request" indicates which of these elements are mandatory (M) and which are optional (O) in a request/indication information flow, and the column headed "Confirm" (confirmed information flows only) indicates which of these elements are mandatory (M) and which are optional (O) in a response/confirmation information flow.
- 10 -
7.2.1.1
r a _ M W I _ A c t iv a t e ra_MWI_Activate is a confirmed information flow across ra from FE1 to FE2 used to activate SSMWI. Table 1 lists the elements within the ra_MWI_Activate information flow. Ta b le 1 - C o n t e n t o f r a _ M W I _ A c t iv a t e Element Served User's number Service Number of messages Priority Message Centre identity Originating number Timestamp Result
Request M M O O O O O
Confirm
M
NOTE 1 2 3 4 5 6 7 8
NOTE 1 This is the Served User's PISN number. NOTE 2 This indicates a particular service. NOTE 3 This indicates the number (non-zero) of messages waiting for the Served User. If this field is omitted, then there is one or more than one message waiting. NOTE 4 This indicates the priority of the highest priority message waiting. NOTE 5 This identifies the Message Centre at which messages are waiting. NOTE 6 This indicates the PISN number of the user that left a message. NOTE 7 This indicates the time when a message was left. NOTE 8 This indicates acceptance or the reason for rejection.
- 11 -
7.2.1.2
r a _ M W I _ D e a c t iv a t e ra_MWI_Deactivate is a confirmed information flow across ra from FE1 to FE2 used to deactivate SS-MWI. Table 2 lists the elements within the ra_MWI_Deactivate information flow. Ta b le 2 - C o n t e n t o f r a _ M W I _ D e a c t iv a t e Element Served User's number Service Message Centre identity Result
Request M M O
Confirm
M
NOTE 1 2 3 4
NOTE 1 This is the Served User's PISN number. NOTE 2 This indicates a particular service. NOTE 3 This identifies the Message Centre at which messages have been retrieved. This element is mandatory if included in a previous ra_MWI_Activate information flow. NOTE 4 This indicates acceptance or the reason for rejection.
- 12 -
7.2.1.3
ra_MWI_Interrogate ra_MWI_Interrogate is a confirmed information flow across ra from FE2 to FE1 used to interrogate SS-MWI. Table 3 lists the elements within the ra_MWI_Interrogate information flow. Ta b le 3 - C o n t e n t o f r a _ M W I _ I n t e r r o g a t e Element Served User's number Service Number of messages Priority Message Centre identity Originating number Timestamp Result
Request M M
O
Confirm M O O O O O M
NOTE 1 2 3 4 5 6 7 8
NOTE 1 This is the Served User's PISN number. NOTE 2 In the request, this indicates a particular service or all services. The confirmation shall provide a list of zero or more services for which SS-MWI is activated. NOTE 3 This indicates the number (non-zero) of messages waiting for the Served User. If provided, and the request was for all services, it shall be repeated for each service for which SS-MWI is active. NOTE 4 This indicates the priority of the highest priority message waiting. If provided, and the request was for all services, it shall be repeated for each service for which SS-MWI is active. NOTE 5 This identifies the Message Centre interrogated. NOTE 6 This indicates the PISN number of the user that left a message. NOTE 7 This indicates the time when a message was left. NOTE 8 This indicates acceptance or the reason for rejection. 7.2.2
R e la t io n s h ip o f in f o r m a t io n f lo ws t o Ba s ic C a ll in f o r m a t io n f lo ws ra_MWI_Activate, ra_MWI_Deactivate and ra_MWI_Interrogate are sent independently of basic call information flows.
- 13 -
7.2.3
I n f o r m a t io n f lo w s e q u e n c e s A stage 3 standard for SS-MWI shall provide signalling procedures in support of the information flow sequences specified in the figures. In addition, signalling procedures should be provided to cover other sequences arising from error situations, interactions with Basic Call, interactions with other supplementary services, different topologies, etc. Within a column representing an SS-MWI Functional Entity, the numbers refer to Functional Entity actions listed in 7.3.
7.2.3.1
A c t iv a t io n o f S S - M W I Figure 3 shows in generic form the information flow sequence for activation of SS-MWI.
FE1
101
ra
FE2
ra_MWI_Activate req/ind 201
102
ra_MWI_Activate con/res
F ig u r e 3 - I n f o r m a t io n f lo w s e q u e n c e f o r a c t iv a t io n o f S S - M W I
- 14 -
7.2.3.2
D e a c t iv a t io n o f S S - M W I Figure 4 shows in generic form the information flow sequence for deactivation of SS-MWI.
FE1
103
ra
FE2
ra_MWI_Deactivate req/ind 202
104
ra_MWI_Deactivate con/res
F ig u r e 4 - I n f o r m a t io n f lo w s e q u e n c e f o r d e a c t iv a t io n o f S S - M W I 7.2.3.3
I n t e r r o g a t io n o f S S - M W I Figure 5 shows in generic form the information flow sequence for interrogation of SS-MWI.
FE1
ra
ra_MWI_Interrogate
FE2
203
req/ind 105 ra_MWI_Interrogate
204
con/res
F ig u r e 5 - I n f o r m a t io n f lo w s e q u e n c e f o r in t e r r o g a t io n o f S S - M W I
- 15 -
7.3 7.3.1
7.3.2
Functional Entity actions F u n c t io n a l En t it y a c t io n s o f F E1 101 Send ra_MWI_Activate req/ind to FE2 in order to activate SS-MWI at the Served User. 102
Receive ra_MWI_Activate con/res from FE2.
103
Send ra_MWI_Deactivate req/ind to FE2 in order to deactivate SS-MWI at the Served User.
104
Receive ra_MWI_Deactivate con/res from FE2.
105
Process ra_MWI_Interrogate and if SS-MWI is allowed to be interrogated, obtain the current status of the Message Waiting Indication and send it back to FE2.
F u n c t io n a l En t it y a c t io n s o f F E2 201 Process ra_MWI_Activate and if SS-MWI is allowed to be activated at the Served User, activate SS-MWI at the Served User and send back a confirmation of the activation to FE1. 202
Process ra_MWI_Deactivate and if SS-MWI is allowed to be deactivated at the Served User, deactivate SS-MWI at the Served User and send back a confirmation of the deactivation to FE1.
203
Send ra_MWI_Interrogate req/ind to FE1 in order to interrogate SS-MWI.
204
Receive ra_MWI_Interrogate con/res from FE1.
- 16 -
7.4
Functional Entity behaviour The FE behaviours shown below are intended to illustrate typical FE behaviour in terms of information flows sent and received. The behaviour of each FE is shown using the Specification and Description Language (SDL) defined in ITU-T Rec. Z.100 (1999).
7.4.1
Be h a v io u r o f F E1 Figure 6 shows the normal behaviour of FE1. Output signals to the left and input signals from the left represent primitives to and from the Message Centre. Output signals to the right and input signals from the right represent information flows from and to FE2.
Figure 6 - SS-MWI, SDL for Functional Entity FE1
- 17 -
7.4.2
Be h a v io u r o f F E2 Figure 7 shows the normal behaviour of FE2. Output signals to the left and input signals from the left represent information flows to and from the Served User. Output signals to the right and input signals from the right represent primitives to and from FE1.
Figure 7 - SS-MWI, SDL for Functional Entity FE2
- 18 -
7.5
Allocation of Functional Entities to physical equipment The allocation of FEs to physical locations as shown in table 4 shall apply. T a b l e 4 - S c e n a r i o s f o r t h e a l l o c a t io n o f F E s t o p h y s i c a l e q u i p m e n t f o r a c t iv a t io n / d e a c t iv a t io n / in t e r r o g a t io n Scenario 1
7.6
FE1 Message Centre's PINX
FE2 Served User's PINX
Interworking considerations The allocation of FEs to physical locations in the case of interworking with other networks that support a compatible service, as shown in table 5, shall apply. T a b l e 5 - S c e n a r i o s f o r t h e a l l o c a t io n o f F E s t o p h y s i c a l e q u i p m e n t in the case of interworking with other networks Scenario 2 Scenario 3
FE1 Other network Message Centre's PINX
FE2 Served User's PINX Other network
.
.
Free printed copies can be ordered from: ECMA 114 Rue du Rhône CH-1204 Geneva Switzerland Fax: Email:
+41 22 849.60.01 [email protected]
Files of this Standard can be freely downloaded from the ECMA web site (www.ecma.ch). This site gives full information on ECMA, ECMA activities, ECMA Standards and Technical Reports.
ECMA 114 Rue du Rhône CH-1204 Geneva Switzerland See inside cover page for obtaining further soft or hard copies.