draft-ietf-spirits-architecture-00.txt   draft-ietf-spirits-architecture-01.txt 
Network Working Group L. Slutsman (Ed.) Network Working Group L. Slutsman (Ed.)
Internet Draft AT&T Labs Internet Draft AT&T Labs
<draft-ietf-spirits-architecture-00.txt> I. Faynberg <draft-ietf-spirits-architecture-01.txt> I. Faynberg
Expires April 2001 H. Lu Expires August 2001 H. Lu
M. Weissman M. Weissman
Lucent Technologies Lucent Technologies
The SPIRITS Architecture The SPIRITS Architecture
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance wit all This document is an Internet-Draft and is in full conformance wit all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
skipping to change at page 2, line ? skipping to change at page 2, line ?
services, which are those originating in the PSTN and necessitating the services, which are those originating in the PSTN and necessitating the
interactions between the PSTN and the Internet. (Internet Call Waiting, interactions between the PSTN and the Internet. (Internet Call Waiting,
Internet Caller-ID Delivery, and Internet Call Forwarding are examples Internet Caller-ID Delivery, and Internet Call Forwarding are examples
of SPIRIT services.) Specifically, it defines the components of SPIRIT services.) Specifically, it defines the components
constituting the architecture and the interfaces between the constituting the architecture and the interfaces between the
components. components.
The rest of the document is organized as follows: The rest of the document is organized as follows:
+ Section 2 describes example SPIRITS services from the end-user point + Section 2 describes example SPIRITS services from the end-user point
of view; of view;
+ Section 3 describes the SPIRITS architecture;
<draft-slutsman-spirits-architecture-01.txt> April 2001 <draft-ietf-spirits-architecture-01.txt> August 2001
+ Section 3 describes the SPIRITS architecture;
+ Section 4 contains security consideration; + Section 4 contains security consideration;
+ Section 5 contains acknowledgments; + Section 5 contains acknowledgments;
+ Section 6 contains references; and + Section 6 contains references; and
+ Appendix contains the figure. + Appendix contains the figure.
2. Brief Description of Example SPIRITS Services 2. Brief Description of Example SPIRITS Services
To illustrate the motivation for the overall SPIRIT architecture, To illustrate the motivation for the overall SPIRIT architecture,
this section provides a brief description of the example SPIRITS this section provides a brief description of the example SPIRITS
services: services:
skipping to change at page 3, line 38 skipping to change at page 3, line 37
addresses of the SPIRITS servers] for realizing the SPIRITS services. addresses of the SPIRITS servers] for realizing the SPIRITS services.
The software may be sent by postal mail or downloaded from the Web. The software may be sent by postal mail or downloaded from the Web.
+ The subscriber activates a SPIRITS service by an act of service + The subscriber activates a SPIRITS service by an act of service
session registration, which can take place anytime after he (or she) session registration, which can take place anytime after he (or she)
is connected to the Internet. The subscriber may specify the life is connected to the Internet. The subscriber may specify the life
span of the session. As soon as the session ends, the SPIRITS service span of the session. As soon as the session ends, the SPIRITS service
is deactivated. Naturally, the subscriber should also be able to is deactivated. Naturally, the subscriber should also be able to
deactivate a SPIRITS service anytime during the service session. deactivate a SPIRITS service anytime during the service session.
For certain services (such as ICW or Caller-ID Delivery) the
assumption is that the service subscriber has a single telephone line
and a PC, which is connected to the Internet via this telephone.
(Only under this assumption these services make sense.) Nevertheless,
in other services (such as Web-based Call Center, in which a call
center assistant could re-direct or reject a call presented in a
pop-up window) this assumption may be unnecessary or even
inapplicable.
2.1 Internet Call Waiting (ICW) 2.1 Internet Call Waiting (ICW)
The Internet call waiting service enables a subscriber engaged in an The Internet call waiting service enables a subscriber engaged in an
Internet dial-up session to Internet dial-up session to
o be notified of an incoming call to the very same telephone line o be notified of an incoming call to the very same telephone line
that is being used for the Internet connection; that is being used for the Internet connection;
o specify the desirable treatment of the call; and o specify the desirable treatment of the call; and
o have the call handled as specified. o have the call handled as specified.
<draft-ietf-spirits-architecture-01.txt> August 2001
The details of the ICW service lie in the ways that a waiting call The details of the ICW service lie in the ways that a waiting call
can be treated [1]. Typical ways for handling a call include: can be treated [1]. Typical ways for handling a call include:
+ Accept the incoming call over the PSTN by terminating the Internet + Accept the incoming call over the PSTN by terminating the Internet
connection. (As switching cannot be done immediately, the caller may connection. (As switching cannot be done immediately, the caller may
hear an opening announcement followed by the "ringing" tone.) hear an opening announcement followed by the "ringing" tone.)
+ Forward the incoming call to another telephone number. The + Forward the incoming call to another telephone number. The
<draft-slutsman-spirits-architecture-01.txt> April 2001
subscriber will remain connected to the Internet, while the caller subscriber will remain connected to the Internet, while the caller
will hear an announcement indicating the call is being forwarded and will hear an announcement indicating the call is being forwarded and
eventually be connected to the new destination number. eventually be connected to the new destination number.
+ Accept the incoming call by voice over IP. The subscriber will + Accept the incoming call by voice over IP. The subscriber will
answer the incoming call via the already established Internet answer the incoming call via the already established Internet
connection. (The proposed SPIRITS architecture, however, does not connection. (The proposed SPIRITS architecture, however, does not
reflect this feature.) reflect this feature.)
+ Redirect the incoming call to voice mail. The subscriber will + Redirect the incoming call to voice mail. The subscriber will
skipping to change at page 4, line 51 skipping to change at page 4, line 59
connection, the service is a subset of the ICW service and follows connection, the service is a subset of the ICW service and follows
the relevant description in Section 2.1. Otherwise, the subscriber's the relevant description in Section 2.1. Otherwise, the subscriber's
IP host serves as an auxiliary device of the telephone to which the IP host serves as an auxiliary device of the telephone to which the
call is first sent. call is first sent.
2.3 Internet Call Forwarding 2.3 Internet Call Forwarding
The Internet call forwarding service allows a service subscriber to The Internet call forwarding service allows a service subscriber to
forward an incoming call to another telephone number while being forward an incoming call to another telephone number while being
connected to the Internet. If the subscriber has only one telephone connected to the Internet. If the subscriber has only one telephone
<draft-ietf-spirits-architecture-01.txt> August 2001
line and is using the very line for the Internet connection, the line and is using the very line for the Internet connection, the
service is a subset of the ICW service and follows the relevant service is a subset of the ICW service and follows the relevant
description in Section 2.1. Otherwise, the subscriber's IP host description in Section 2.1. Otherwise, the subscriber's IP host
serves as an auxiliary device of the telephone to which the call is serves as an auxiliary device of the telephone to which the call is
first sent. first sent.
3. SPIRITS Architecture 3. SPIRITS Architecture
<draft-slutsman-spirits-architecture-01.txt> April 2001
Figure 1 of the Appendix depicts the SPIRITS architecture, which Figure 1 of the Appendix depicts the SPIRITS architecture, which
includes the following entities: includes the following entities:
1. Service Control Function (SCF) [2], which executes service logic, 1. Service Control Function (SCF) [2], which executes service logic,
interacts with the entities in the IP domain (e.g., the SPIRITS Proxy interacts with the entities in the IP domain (e.g., the SPIRITS
and PINT Server) through the SPIRITS Client, and instructs the Gateway and PINT Server) through the SPIRITS Client, and instructs
switches on how to complete a call. Physically, the SCF may be the switches on how to complete a call. Physically, the SCF may be
located in either stand-alone general-purpose computers called located in either stand-alone general-purpose computers called
Service Control Points (SCPs) or specialized pieces of equipment Service Control Points (SCPs) or specialized pieces of equipment
called Service Nodes (SNs) [2]. called Service Nodes (SNs) [2].
2. Service Switching Function (SSF) [2], which normally resides in a 2. Service Switching Function (SSF) [2], which normally resides in a
switch and is responsible for the recognition of Intelligent Network switch and is responsible for the recognition of Intelligent Network
(IN) triggers and interactions with the SCF. (IN) triggers and interactions with the SCF.
3. SPIRITS Client, which is responsible for receiving PSTN requests 3. SPIRITS Client, which is responsible for receiving PSTN requests
from the SCF as well as sending responses back. It may be co-located from the SCF as well as sending responses back. It may be co-located
with the SCF. If not, it communicates with the SCF over the D with the SCF. If not, it communicates with the SCF over the D
interface. interface.
4. PINT Server, which receives PINT requests from the PINT Client and 4. PINT Server, which receives PINT requests from the PINT Client and
relays them to the PSTN for execution over the E interface. relays them to the PSTN for execution over the E interface.
5. SPIRITS Proxy, which is co-located with the PINT Server and serves 5. SPIRITS Gateway, which is co-located with the PINT Server or
as an intermediary between the SPIRITS Server and SPRITS Client via PINT Gateway (or both when they are co-located as assumed here
the B and C interfaces, respectively. for simplicity) and serves as an intermediary between the SPIRITS
Server and SPRITS Client via the B and C interfaces, respectively.
6. PINT Client, which resides in the subscriber's IP host and is 6. PINT Client, which resides in the subscriber's IP host and is
responsible for initiating PINT requests, which are sent to the PINT responsible for initiating PINT requests, which are sent to the PINT
server over the A interface. server over the A interface.
7. SPIRITS Server, which terminates PSTN requests and is responsible 7. SPIRITS Server, which terminates PSTN requests and is responsible
for all interactions (e.g., incoming call notification and relaying for all interactions (e.g., incoming call notification and relaying
the call treatment) between the subscriber and the SPIRITS proxy. the call treatment) between the subscriber and the SPIRITS Gateway.
The rest of the Section describes the interfaces between the entities The rest of the Section describes the interfaces between the entities
in detail. in detail.
3.1 Interface A 3.1 Interface A
This interface is used for sending PINT request to PINT Server. Its This interface is used for sending PINT requests to PINT Server. Its
principal use is for service session registration and as a result principal use is for service session registration and as a result
activation of a SPIRITS service (see Section 2). In addition, this activation of a SPIRITS service (see Section 2). In addition, this
interface may be used for service subscription. interface may be used for service subscription.
<draft-ietf-spirits-architecture-01.txt> August 2001
3.2 Interface B 3.2 Interface B
This interface serves two main purposes: 1) to notify the subscriber This interface serves two main purposes: 1) to notify the subscriber
of incoming calls together with the calling number and name, if of incoming calls together with the calling number and name, if
available; and 2) to send to the SPRITS Proxy the subscriber's choice available; and 2) to send to the SPRITS Gateway the subscriber's
of call disposition specified on the fly. choice of call disposition specified on the fly.
3.3 Interface C 3.3 Interface C
<draft-slutsman-spirits-architecture-01.txt> April 2001
This interface is used for communications between the SPIRITS Client This interface is used for communications between the SPIRITS Client
and SPIRITS Proxy. The SPIRITS Proxy may in turn communicate with and SPIRITS Gateway. The SPIRITS Gateway may in turn communicate
the SPRITS Server, or may act as a virtual server, terminating the with the SPIRITS Server, or may act as a virtual server, terminating
requests without sending them down to the SPIRITS Server. the requests without sending them down to the SPIRITS Server.
3.4 Interface D 3.4 Interface D
This interface is for communications between the SPIRITS Client and This interface is for communications between the SPIRITS Client and
the SCF. Specifically, from the SCF to the SPIRITS Client, the the SCF. Specifically, from the SCF to the SPIRITS Client, the
parameters associated with the applicable IN triggers are sent. From parameters associated with the applicable IN triggers are sent. From
the SPIRITS Client to SCF, the subscriber's call disposition is sent. the SPIRITS Client to SCF, the subscriber's call disposition is sent.
The SCF "transforms" the user's disposition into appropriate actions, The SCF "transforms" the user's disposition into appropriate actions,
such as playing an announcement to the caller, and resuming the such as playing an announcement to the caller, and resuming the
suspended call processing in the SSP. suspended call processing in the SSP.
skipping to change at page 6, line 33 skipping to change at page 6, line 42
4. Security Considerations 4. Security Considerations
It is assumed that the interface C is between trusting entities. In It is assumed that the interface C is between trusting entities. In
addition, the assumption that the PINT Client and SPIRITS Server are addition, the assumption that the PINT Client and SPIRITS Server are
collocated dictates that the security considerations for the A and B collocated dictates that the security considerations for the A and B
interfaces are exactly the same. interfaces are exactly the same.
5. Acknowledgments 5. Acknowledgments
We would like to thank Alec Brusilovsky and David Shraider for their We would like to thank Alec Brusilovsky, Jorgen Bjorkner, Jim Buller,
comments and input. The authors would like to extend their thanks to Lawrence Conroy, Jorge Gato, Dave Hewins, Naoto Makinae, and Dave
Jorgen Bjorkner and Naoto Makinae, for there email discussion on the Shrader for their comments and input.
joined PINT-SPIRITS architecture.
6. References 6. References
[1] Lu, H. (Editor), I. Faynberg, J. Voelker, M. Weissman, W. Zhang, [1] Lu, H. (Editor), I. Faynberg, J. Voelker, M. Weissman, W. Zhang,
S. Rhim, J. Hwang, S. Ago, S. Moeenuddin, S. Hadvani, S. Nyckelgard, S. Rhim, J. Hwang, S. Ago, S. Moeenuddin, S. Hadvani, S. Nyckelgard,
J. Yoakum, and L. Robart, "Pre-SPIRITS Implementations of PSTN- J. Yoakum, and L. Robart, "Pre-SPIRITS Implementations of PSTN-
Initiated Services ", IETF Draft, work in progress. Initiated Services ", RFC 2995.
[2] Faynberg, I., L. Gabuzda, M. Kaplan, and N.Shah, "The Intelligent [2] Faynberg, I., L. Gabuzda, M. Kaplan, and N.Shah, "The Intelligent
Network Standards: Their Application to Services", McGraw-Hill, 1997. Network Standards: Their Application to Services", McGraw-Hill, 1997.
<draft-slutsman-spirits-architecture-01.txt> April 2001 <draft-ietf-spirits-architecture-01.txt> August 2001
Appendix Appendix
Subscriber's IP Network ......................
IP Host +----------------+ . .
| +------------+ | . +------------+ .
_______________ .................... | | | | A . | | .
| _____________ | A . ________________ . | | PINT Client|********************|PINT Server/|********
| |PINT Client|*******| PINT Server |******** | | | | . Gateway | *
| |___________| | : |______________| : * | +------------+ | . +------------+ . *
| ____________ | : * : * | | . . *
| | SPIRITS | | B . _______*________ : * | Subscriber's | . . *
| | Server |*******|SPIRITS Proxy | : * | | . . *
| |___________| | : |______________| : * | IP Host | . . *
|_______________| .........*.......... * | | . +------------+ . *
*C * | +------------+ | . | SPIRITS | . *
_________________ ______*________ * | | SPIRITS | | B . | Gateway | . *
| Subscriber | |SPIRITS Client | * | | Server |********************| | . * E
| Telephone | | | * | | | | . +------------+ . *
|_________________| |_______________| * | +------------+ | . * . *
* * * E +----------------+ . * . *
* Line * D * ...........*.......... *
++++++++++*+++++++++++ PSTN +++*+++++++++++++++*++ //-------\\ * *
/// \\\ * *
| Subscriber's | * C *
| Telephone | * *
\\\ /// * *
\\ -------// * *
* * * * * *
+-------------------+ +-----------------+ * * *
| Service Switching |*****| Service Control | ++++++++++++++++++++++++++ PSTN ++++++++++++++++++++++++++
| Function | SS7 | Function | * * *
+-------------------+ +-----------------+ * * *
* +------------------+ *
* Line | SPIRITS Client | *
* | | *
+--------------------+ +---+----- D ---------+-*+
| | INAP/SS7 | |
|Service Switching ************Service Control Function |
| Function | | |
| | +-------------------------+
| |
| |
+--------------------+
Figure 1: SPIRITS Architecture Figure 1: SPIRITS Architecture
Author's Addresses Author's Addresses
Igor Faynberg Igor Faynberg
Lucent Technologies Lucent Technologies
Room 4D-601A Room 4D-601A
101 Crawfords Corner Road 101 Crawfords Corner Road
Holmdel, NJ 07733-3030 US Holmdel, NJ 07733-3030 US
E-mail: faynberg@lucent.com E-mail: faynberg@lucent.com
<draft-ietf-spirits-architecture-01.txt> August 2001
Telephone: +1 732 949 0137 Telephone: +1 732 949 0137
Hui-Lan Lu Hui-Lan Lu
Lucent Technologies Room 4C-607A Lucent Technologies Room 4C-607A
101 Crawfords Corner Road 101 Crawfords Corner Road
Holmdel, NJ 07733-3030 US Holmdel, NJ 07733-3030 US
E-mail: huilanlu@lucent.com E-mail: huilanlu@lucent.com
Telephone: +1 732 949 0321 Telephone: +1 732 949 0321
Mark Weissman Mark Weissman
Lucent Technologies Lucent Technologies
Room NE406B Room NE406B
200 Lucent Lane 200 Lucent Lane
Cary, NC 27511 Cary, NC 27511
<draft-slutsman-spirits-architecture-01.txt> April 2001
E-mail: maw1@lucent.com E-mail: maw1@lucent.com
Telephone: +1 919 463 3258 Telephone: +1 919 463 3258
Lev Slutsman Lev Slutsman
AT&T Labs AT&T Labs
Room D5-3D26 Room D5-3D26
200 Laurel Avenue 200 Laurel Avenue
Middletown, NJ 07748 Middletown, NJ 07748
E-mail: slutsman@att.com E-mail: slutsman@att.com
Telephone: 732-420-3756 Telephone: 732-420-3756
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (1998). All Rights Reserved. Copyright (C) The Internet Society (1998). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However, this are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing the document itself may not be modified in any way, such as by removing
copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. The limited permissions granted above are perpetual and will English. The limited permissions granted above are perpetual and
not be revoked by the Internet Society or its successors or assigns. will not be revoked by the Internet Society or its successors or
This document and the information contained herein is provided on an assigns. This document and the information contained herein is
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
<draft-slutsman-spirits-architecture-01.txt> April 2001 <draft-ietf-spirits-architecture-01.txt> August 2001
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/