3GPP2 X.

S0004-700-E
Version 1.0.0
Date: March 2004

Wireless Intelligent Networks

COPYRIGHT
3GPP2 and its Organizational Partners claim copyright in this document and individual
Organizational Partners may copyright and issue documents or standards publications in
individual Organizational Partner's name based on this document. Requests for
reproduction of this document should be directed to the 3GPP2 Secretariat at
secretariat@3gpp2.org. Requests to reproduce individual Organizational Partner's
documents should be directed to that Organizational Partner. See www.3gpp2.org for more
information.
Revision History

Revision Date
Rev. 0 Initial Publication March 2004
 X.S0004-700-E v1.0

1
2 PART 700
3
4
5
6 1 INTRODUCTION
7
8
The Wireless Intelligent Network (WIN) is a network which supports the use of intelligent network
9
capabilities to provide seamless terminal services, personal mobility services, and advanced network
10
services in the mobile environment. 700 Intelligent network capabilities are all those functional
11
12
capabilities which support creation and execution of service logic programs which reside outside of
13
switching equipment, but work in collaboration with the switching equipment based upon a common
14 definition of call models and protocols. These service logic programs may utilize data resources and
15 physical resources which also reside outside of the switching equipment.
16
17
Terminal mobility services are services created using intelligent network capabilities to serve
18 customers with mobile terminals. A set of these services will be associated with each mobile
19 terminal based on the capabilities of the terminal and subscription selections. Some prerequisites of
20 providing these services are the abilities to identify and authenticate the terminal and to provide
21 seamless operations capabilities between wireless and wireline networks.
22
23 Personal mobility services are services created using intelligent network capabilities to serve
24 customers who are mobile. A set of these services will be associated with each customer based on
25 personal subscription selections. The customer may utilize a variety of mobile and fixed terminals
26 at different locations. Some prerequisites of providing these services are the abilities to:
27
28
29
• identify and authenticate the person (subscriber) who has been provisioned for the service
30
• provide seamless operations capabilities among the wireless, fixed and other networks
31
32
(e.g., broadband, internet, data networks)
33
• provide a unique set of services to the subscriber based on the subscriber’s access point to the
34
WIN service
35
36
Advanced network service has the functionality to identify the capability of the serving network, to
37
provide service based on the network and terminal capability, and to provide seamless service
38
mobility between wireless and wireline networks.
39
40
The basic difference between terminal mobility service, personal mobility service, and advanced
41
network service is as follows:
42
43 • Terminal mobility services: services based on the terminal capability irrespective of the
44
terminal user.
45
46 • Personal mobility services: services based on personal needs or business entity needs
47 irrespective of terminals or networks.
48
49 • Advanced network services: customized services which can be provided ubiquitously in home
50 or roaming networks (wireless or wireline).
51
52 Service management functionality is used to provision and manage the service control functionality,
53 the service data functionality, and the specialized resource functionality in the network. Service
54 creation functionality is used to create services. Service management and service creation
55 functionality may use standardized interfaces. However, the ability of a service subscriber to interact
56
directly with subscriber-specific service management information will not be excluded or
57
constrained for WIN.
58
59
60

700-1 INTRODUCTION
X.S0004-700-E v1.0

Initial WIN standards describe a distributed functional plane (DFP) architecture, call models, and 1
2
advanced network services such as calling name presentation capabilities, voice controlled services,
3
and incoming call screening services. Future WIN standards will add additional WIN capabilities
4
and functionality.
5
6
7
1.1 OBJECTIVE 8
9
10
The DFP defines the WIN architecture in terms of functional entities (FEs), each of which performs
11
distinct actions in the network. A grouping of actions across one or more FEs, when coordinated by
12
communication flows, provides the required WIN service execution.
13
14
The WIN DFP provides a different view of the network than is provided by the wireless network
15
reference model (NRM). The NRM defines network entities and the associated interface reference
16
points that may logically comprise a wireless network. The WIN DFP identifies FEs that perform
17
distinct actions in the network. Multiple FEs can be included in a single network entity. 18
19
20

1.2 SCOPE 21
22
23
This part of TIA-41 defines the distributed functional plane (DFP) for the Wireless Intelligent
24
Network (WIN).
25
26
Specifically, the scope of this part of the Standard is:
27

1. To define the WIN functional entities and the relationships applicable to WIN. 28
29
2. To specify a high level model description of call control function (CCF) activities required 30
to establish and maintain communication paths for users. 31
32
3. To specify a high level model description of service switching function (SSF) activities 33
required for interaction between the CCF and a service control function (SCF). 34
35
4. To specify WIN triggers and provide a high level model description of detection point 36
processing. 37
38
5. To describe mobility management and radio access control functions in the context of 39
WIN. 40
41
6. To illustrate how the WIN basic call state models interact with TIA-41 signaling. 42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

OBJECTIVE 700-2
 X.S0004-700-E v1.0

1
2 2 WIN DISTRIBUTED FUNCTIONAL PLANE
3
4 The distributed functional plane (DFP) for the Wireless Intelligent Network (WIN) is based on the
5
ITU-T Q.1224 recommendation for IN CS-2. The DFP defines the WIN architecture in terms of
6
functional entities (FEs), each of which performs distinct actions in the network. A grouping of
7
actions across one or more FEs, when coordinated by communication flows, provides the required
8
9
WIN service execution.
10
The WIN DFP provides a different view of the network than is provided by the wireless network
11
reference model (NRM). The NRM defines network entities and the associated interface reference
12
13
points that may logically comprise a wireless network. The WIN DFP identifies FEs that perform
14
distinct actions in the network. Multiple FEs can be included in a single network entity.
15
16
17 2.1 Scope of WIN Distributed Functional Plane
18
19
The scope of the DFP architecture for WIN is driven by the requirements of desired wireless services
20
21
and is constrained by the capabilities of the embedded base of evolvable network technology.
22
The functions required to support the desired wireless services include:
23
24 • end user access to call and service processing
25
26 • service invocation and control
27
28 • end user interaction with service control
29
30
• service management
31
The scope of each of these functions is described below.
32
33
34
35 2.1.1 End User Access
36
37 End user access to call and service processing will be provided via the following access
38 arrangements:
39
40 • line interfaces that are provided by radio access systems
41
42 • traditional trunk and SS7 interfaces
43
44
• other types of network access arrangements such as roamer ports
45
46
47 2.1.2 Service Invocation and Control
48
49 Call and service processing for WIN builds upon the call processing infrastructure of existing MSCs.
50 It does so by using a generic model of existing call control functionality to process basic two-party
51
calls, then adding service switching functionality to invoke and manage WIN service logic. Once
52
invoked, WIN service logic is executed under the control of service control functionality in
53
conjunction with service data functionality. With this distributed approach to call and service
54
55
processing, the existing call control functionality retains ultimate responsibility for the integrity of
56
calls, as well as for the control of call processing resources.
57
The following call and service processing constraints apply for WIN:
58
59
60

700-3 WIN DISTRIBUTED FUNCTIONAL PLANE

X.S0004-700-E v1.0

a. Call control and service switching functionality are tightly coupled in the MSC, thus the 1
2
relationship between SSF and CCF is not standardized.
3

b. A call is either between two or more end users that are external to the network and 4

addressable via a directory number or combination of directory number and bearer 5

6
capability, or a call is between one or more end users and the network itself.
7

c. A call may be initiated by an end user, or by an SCF within the network on behalf of an end 8

user. To supplement a call, WIN service logic may either be invoked by an end user served 9
10
by a WIN MSC, or by the network on behalf of an end user.
11

d. A call may span multiple MSCs. As such, each MSC only controls the portion of the call 12

in that MSC. Call processing is functionally separated between MSCs. WIN service logic 13
14
invoked on WIN MSCs in such an inter-MSC call are managed independently by each WIN
15
MSC.
16

e. MSCs can be viewed as having two functionally separate sets of call processing logic that 17
18
coordinate call processing activities to create and maintain a basic two-party call. This
19
functional separation is provided between the originating portion of the call and the
20
terminating portion of the call. This functional separation should be maintained in a WIN
21
MSC to allow WIN service logic invoked on the originating portion of the call (i.e. on 22
behalf of the calling party) to be managed independently of WIN service logic invoked on 23
the terminating portion of the call (i.e. on behalf of the called party). 24
25
f. It is desirable to allow multiple WIN-supported service logic instances to be 26
simultaneously active for a given end user. It is also recognized that non-WIN service logic 27
will continue to exist in the network. As such, service feature logic instances mechanisms 28
for WIN should: 29
30
» determine which service logic to invoke for a given service request. This mechanism 31
should select the appropriate WIN-supported service logic or non-WIN-supported 32
service logic, and block the invocation of any other service logic for that particular 33
service request; 34
35
» manage WIN- and non-WIN-supported service logic instances which are 36
simultaneously active (this may require limiting the service logic instances which are 37
active); 38
39
» ensure that simultaneously active WIN-supported service logic instances adhere to 40
single-ended, single point of control service processing. 41
42
g. The distributed approach and added complexity of call and service processing for WIN 43
requires mechanisms for fault detection and recovery, allowing graceful termination of 44
calls and appropriate treatments for end users. 45
46
47

2.1.3 End User Interaction 48

49
50
End user interaction with the network to send and receive information is provided by service
51
switching and call control resources, augmented by specialized resources. These specialized
52
resources are controlled by service control functionality, and are connected to end users via call 53
control and service switching functionality. 54
55
56
57
58
59
60

Scope of WIN Distributed Functional Plane 700-4

 X.S0004-700-E v1.0

1
2.1.4 Service Management
2
3
Service management functionality is used to provision and manage the service control functionality,
4
5
service data functionality, and specialized resource functionality in the network, outside of the
6
context of call and service processing. Standardized interfaces for this functionality are outside the
7 scope of WIN. However, the ability of a service subscriber to interact directly with subscriber-
8 specific service management information will not be excluded or constrained for WIN.
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

700-5 Scope of WIN Distributed Functional Plane

X.S0004-700-E v1.0

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

Scope of WIN Distributed Functional Plane 700-6