00034649.00 Nokia PoC Rel. 1.5, Product...

PoC Overview

dn03505268Issue 9 en

# Nokia CorporationNokia Proprietary and Confidential

1 (74)

00034649.00Nokia PoC Rel. 1.5, Product Documentation

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is intended for the useof Nokia's customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be reproduced or transmitted in any form or means without theprior written permission of Nokia. The document has been prepared to be used by professionaland properly trained personnel, and the customer assumes full responsibility when using it.Nokia welcomes customer comments as part of the process of continuous development andimprovement of the documentation.

The information or statements given in this document concerning the suitability, capacity, orperformance of the mentioned hardware or software products cannot be considered binding butshall be defined in the agreement made between Nokia and the customer. However, Nokia hasmade all reasonable efforts to ensure that the instructions contained in the document areadequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the document.

Nokia's liability for any errors in the document is limited to the documentary correction of errors.NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENTOR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARYLOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright according tothe applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

Other product names mentioned in this document may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright © Nokia Corporation 2005. All rights reserved.

2 (74) # Nokia CorporationNokia Proprietary and Confidential


PoC Overview

Contents

Contents 3

1 About PoC Overview 5

2 Introduction to PoC 72.1 PoC concept 72.2 PoC functionality 12

3 End-user features 153.1 End-user features overview 153.2 Basic communication features 163.2.1 Registration to PoC service 163.2.2 Session control 163.2.3 Floor control 173.2.4 Indicators 173.2.5 User identification 193.2.6 MSISDN dialling 203.3 One-to-one communication features 203.3.1 One-to-one call 203.3.2 Answering mode 213.4 Group communication features 223.4.1 Open join-in groups 223.4.2 Closed join-in groups 223.4.3 Temporary dial-out groups 243.5 Control features 243.5.1 Access control lists 243.5.2 Group member lists 253.5.3 Multisession support 253.5.4 Group advertisement 263.5.5 Anonymous communication 263.6 Supporting features 273.6.1 Callback request 273.6.2 Do not Disturb 273.6.3 Group participant info 273.6.4 PoC Presence 28

4 Operator features 294.1 Communication reliability 294.1.1 Acknowledged one-to-one call start 294.1.2 Service recovery 294.2 Provisioning 304.2.1 PoC Register element 304.2.2 Folder structure 324.2.2.1 Load balancing based on folders 334.2.2.2 Folder redeployment 334.2.3 Provisioning APIs 344.2.4 Management User Client tool 344.2.5 Subscriber provisioning 37



3 (74)

Contents

4.2.6 Terminal settings 374.2.7 Autoprovisioning 374.2.8 Advanced service plans with folders 384.3 Administering corporate fleets 394.3.1 Organising corporate usage 394.3.2 Administration by corporate management user 414.3.3 Communication rights management 424.4 Charging 434.5 Operation and Maintenance in PoC system 454.5.1 Cabinet switch 504.5.2 Nokia NetAct 514.6 Security 514.6.1 PoC call security 514.6.2 PoC administration security 524.7 Redundancy and scalability 53

5 PoC system architecture 555.1 Client-server architecture 585.2 Logical planes of PoC system 605.3 Architecture of the main elements 64

6 PoC system interfaces 656.1 Terminal interface: Nokia PoC client interface 676.2 Presence interfaces 676.3 Provisioning interface 686.4 Register - Call Processor interface 686.5 Group and access control list management interface 686.6 Access Control List (ACL) management interface 686.7 Charging interfaces 686.8 Operation and maintenance interfaces 696.9 Intercollegiate interface 706.10 Nokia Network-to-Network Interface (NNI) 706.11 Authorization interface 716.12 Autoprovisioning interface 71

7 Glossary 73



PoC Overview

1 About PoC OverviewAudience

This document is aimed at readers who have general knowledge abouttelecommunications and who need to gain a general understanding about theNokia Push to talk over Cellular (PoC) service and the Nokia Push to talk system.

Scope

This document is an introduction to the Nokia Push to talk over Cellular Release1.5 system.

Changes between issues 7 and 9

Section Temporary dial-out groups has been updated.

PoC customer document issues are by default release-specific. Issue 8 has beenused for PoC Release 1.0.

Changes in the document

The document issue 7 is the first for the Nokia PoC Rel. 1.5.

PoC customer document issues are by default release-specific. Issues 1 to 6 havebeen used for PoC Release 1.0.

The title of the document has been changed from PoC System Overview to PoCOverview. The document has also been restructured.

New features introduced:

. Tel URL support within domain: MSISDN dialling

. Dial-out groups

. Group member lists

. Group participant info



5 (74)

About PoC Overview

. PoC presence

. Nokia Network-to-Network Interface (NNI)

Descriptions for the new features have been added and the names and concepts ofthe old features have been revised.

For more information on changes between PoC releases, see Nokia Push to talkover Cellular, Release Note.

References to related documents

PoC Register Product Description and PoC Call Processor Product Descriptionprovide further information on the functionality of PoC.

We welcome any suggestions for further improvement of this document. Also,should you find any errors or omissions in this document, please forward yourcomments to the local Nokia representative or send them to the e-mail [email protected].



PoC Overview

2 Introduction to PoC

2.1 PoC concept

Nokia Push to talk over Cellular (PoC) enables real-time one-to-one and one-to-many voice communication service in a cellular network.

The service, which has proved popular among two-way radio users, is enabledthrough GPRS cellular phones. It enhances the cellular services and brings newbusiness opportunities into the domain of real-time voice communications. NokiaPoC is a Voice over IP (VoIP) application running over (E)GPRS/WCDMAnetworks. The system itself is access-independent.

PoC system elements

The PoC system consists of

. (E)GPRS/WCDMA packet switched network

. PoC Call Processor(s)

- that implements most of the end-user features and provides featuresfor the operators to operate and maintain the PoC functionality andservices.

. PoC Register

- that handles all provisioning tasks.

. Nokia Presence Server

- that stores and distributes presence information.

. Cabinet Switch (two Cisco 6509 or 3750)

- that connects the PoC network elements to each other and toexternal networks.

. workstations for O&M and provisioning clients

. DNS servers



7 (74)

Introduction to PoC

. the operator's customer care and billing systems (for provisioning andcharging) which might include charging mediation devices and/or Nokiacharging gateway

. Nokia NetAct

. possibly an additional network management system, for example to collectalarms and performance reports from the entire network

. IP Backbone and all related equipment, such as site LAN switches, siterouters, possibly some security equipment like firewalls, VPN gatewaysand so on.



PoC Overview

Figure 1. PoC system in the GPRS/WCDMA packet switched environment

Terminals

One of the goals of PoC is to bring the push to talk facility into conventionalcellular phones. The concept offers terminal manufacturers an opportunity toimplement the push to talk facility across mobile phone categories, thus offeringend users more freedom to choose products that best meet their communicationneeds.

ProvisioningNetwork ManagementCustomer Care and

Billing

BTS BSC/RNC

GPRSbackbonenetwork

SGSN

ChargingGateway

GGSN

PoCRegister

PresenceServer

PoC CallProcessors



9 (74)

Introduction to PoC

Communication principle

The principle of communication in PoC is simple - just push to talk. Users canselect the person or talk group they wish to talk to and then press the push to talkkey or equivalent to start talking. The call is connected instantly. Figure Basicprinciples of push to talk illustrates the push to talk concept.

Push to talk calls are one-way communication: while one person speaks, the other(s) only listen. The turns to speak are requested by pressing the push to talk keyand granted on a first-come-first-served basis. Push to talk speech is connectedwithout the recipient(s) answering and heard through the phone's built-inloudspeaker. The basic idea is that the initiator of a call session is the first one totalk.

For one-to-many communication, users can create talk groups. This happenssimply by sending invitations to the desired group members to join the talk group.Talk groups can also be pre-configured, for example, by the operator for the useof a specific group of people.

Figure 2. Basic principles of push to talk

(E)GPRS/WCDMA PSnetwork

POCapplicationservers

Recipients hearthe speechwithoutanswering

Select target

Press Push to talk key and

Talk!



PoC Overview

Technology

One of the starting points of PoC is a virtual connection within a group of people.While setting up a traditional conference call requires the user to make severalphone calls, in PoC the members of an active talk group session can startconversing in real time at the press of a key. This virtual connection state within agroup session is created by using the Session Initiation Protocol (SIP).

An efficient implementation of push to talk service in the cellular network isenabled by IP technology. Based on Voice over IP technology, the push to talkservice uses cellular access and radio resources more efficiently than thetraditional conference calls, reserving network resources only when neededinstead of reserving the resources the whole duration of the call. Despite thegroup-inclined nature of the service, multicast support is not required for PoC,but a standard GPRS/WCDMA packet switched network is used.

PoC is an application running over the GPRS/WCDMA packet switched networkand all the other services of a cellular network can be made available also for thePoC users.

User

A user is a provisioned subscriber with associated attributes (identity, folder,rights and services). Users communicate through PoC enabled GPRS/WCDMApacket switched terminals.

End-user features

The main end-user features of PoC are one-to-one call and group call. Thesefeatures can be used with a terminal's push to talk facility. In addition, there areseveral features that enhance the functionality of these main features.

Operator features

The PoC solution provides interfaces to an operator's Customer Care and Billing(CC&B) systems, enabling the integration of existing billing and provisioningenvironments to the PoC system.

The management of PoC elements is based on locally or remotely accessibleelement managers and the centralised collection of fault management (FM) andperformance management (PM) data to the Nokia NetAct management system.An element manager can be launched from the Nokia NetAct. The ElementManager is also a standalone application. PoC management support is a NokiaNetAct release-dependent issue and described in the corresponding Nokia NetActrelease documentation.



11 (74)

Introduction to PoC

2.2 PoC functionality

The figure PoC features is an illustration of the features in the PoC system. PoCfeatures can be divided into two basic categories, operator features and end-userfeatures. Some of the end-user features are terminal dependent, although theyrequire support from the system.

Figure 3. PoC features

PoC features

Operator featuresEnd-user features

Provisioning- Folder structure

- Load balancing

- Folder redeployment

- Provisioning APIs

- Management user client tool

- Autoprovisioning solution

- Organising corporate usage

- Communication rights management

- Cross fleeting

Security- PoC user authentication

- Authorization interface

- PoC management user authentication

- Secure group communication

- Provisioning rights

- Technical management rights

Redundancy and scalability

Networking between PoC Call Processors

NNI interface

NOKIA client interface

Charging- Charging records

- Charging configuration settings

- User id for billing

- Charging acknowledgements

Operation and Maintenance- Element managers

- Fault management

- Performance management

- Configuration management

- Security management

- Backup and restore

Basic communication features- Registration to PoC service

- Session control

- Floor control

- Indicators

- User Identification

- MSISDN dialling

One-to-one communication features- One-to-one call

- Answering mode

Group communication features- Open join-in group

- Closed join-in group

- Temporary dial-out group

Control features- Access control lists

- Group member lists

- Multi-session support

- Group advertisement

- Anonymous communication

Supporting features- Callback request

- Do not Disturb

- Group participant info

- PoC presence



PoC Overview

For more information, see the descriptions of the features.

PoC functions are implemented with the PoC Call Processor and PoC Register.For details of the functions, see PoC Call Processor Product Description, PoCRegister Product Description and Presence Server Product Description.



13 (74)

Introduction to PoC



PoC Overview

3 End-user features

3.1 End-user features overview

The main end-user features supported by the PoC system are one-to-one call andgroup call. These features are supported by several enhancements. The end-userfeatures are dependent on the terminal implementation.

For feature availability for Nokia PoC Rel. 1.0 and Rel. 1.5, see the followingtable:

Table 1. End-user features for Nokia PoC terminal users

Feature Rel. 1.0 Rel. 1.5

One-to-one call X X

Closed join-in group X

Ac hoc pro/Provisioned

group

X

Open join-in group X

Ad hoc group

X

Group advertisement X X

Temporary dial-out group - X

Callback request X X

Do not Disturb X X

Multisession support X X

Group participant info X X



15 (74)

End-user features

Table 1. End-user features for Nokia PoC terminal users (cont.)

Feature Rel. 1.0 Rel. 1.5

Anonymous communication X X

PoC presence (SIP/SIMPLE) - (* X

MSISDN dialling (Tel URL) - (** X

* OMA IMPSr1.1 used for PoC presence

** Only for MSISDN based SIP URIs within a single domain

3.2 Basic communication features

3.2.1 Registration to PoC service

Users have to register to PoC in order to use the PoC services. Registration canhappen either without any explicit actions by the end user or at the user�sinitiation. During registration, the user is authenticated.

3.2.2 Session control

Sessions

Basic PoC communication takes place in sessions. Sessions can be either one-to-one or group sessions and there are two different operator configurable sessionestablishment modes. In some situations the network can dynamically force theuse of late mode.

Terminals can use the early session establishment mode for one-to-one calls. Theearly session is established the moment the user logs on/registers and the sessionremains active the whole duration of the call.

Early mode

In the early session establishment mode a 'ready to speak' indication is given tothe A-party before the terminal of the B-party has been paged. This guarantees afast setup.



PoC Overview

Late mode

In the late session establishment mode the target terminal is paged before a 'readyto speak' indication is given to the originator. If the target user is using manualanswering, late establishment mode is automatically used. In other cases theoperator can select, which session establishment mode is used.

3.2.3 Floor control

Each session has its own floor control mechanism, which ensures that only oneparticipant can be heard at a time, meaning that the participant has the floor.

RTP-embedded signalling is used in floor control. The end user receives a 'readyto talk' indication in a successful case and a 'transmission failed' indication in anon-successful case. The system handles the requests on a first-come-first-servedbasis.

Floor granting, denial and releasing the floor

When the user presses the push to talk key to speak, a floor request is sent, whichis acknowledged by the system with a floor grant if the floor is free. If the floor isalready occupied, a floor denial is returned.

The system can forcibly end a transmission by a floor revoke. When the user endsthe transmission, the terminal sends a floor release indication to release the floor.Other participants will receive a floor taken indication when the floor is grantedto any other participant in the session, and a floor idle indication when anyterminal releases the floor. This way, the terminal can present accurate indicationsto the users concerning:

. whether the floor is currently free or occupied

. whether the user has the floor.

For example, when PoC user A presses the push to talk key, the terminal gives atone (ready to talk) to indicate that the floor was requested by A. If user B hasbeen granted the floor prior to user A, the terminal of user A gets a floor denysignal and can give the user a 'transmission failed' indication.

3.2.4 Indicators

PoC supports numerous indicators that give the end users vital information forusing the PoC services. The indicators can appear as, for example, tones orvisuals, depending on the terminal settings and implementation.



17 (74)

End-user features

Talking user id display

In a one-to-one call, identification (SIP URI, and/or mnemonic) of the individualuser whose voice is currently received is displayed. In a group call, it is displayedtogether with the group ID.

Talking group id display

Identification of the group (URI) where the voice is currently being received fromis displayed.

Callback request indicator

Callback request indicator informs the user about the received callback request ina terminal (see Callback request).

Incoming call notification

Incoming call notification indicator informs the user about an incomingnotification in a terminal (see Answering mode).

Notifying indicator

A notifying indicator informs the user who is trying to make a one-to-one call thatthe call attempt has been turned into a notification towards the target user (seeAnswering mode).

Call not allowed indicator

Call not allowed indicator informs the user who is trying to make a one-to-onecall that the call attempt to the target user is not allowed. The indicator is used insituations where the network does not authorise the call. The recipient is notnotified about the call attempt (see Answering mode).

Ready to talk indicator

Ready to talk indicator is an indication appearing after pressing the push to talkkey and telling that the user can start talking. It means that there is a highprobability for a successful connection.

End of talkburst indicator

End of talkburst indicator is an indication to the receiving user that the other userhas released the push to talk key, and the others can take turns. Also theoriginating user gets the indication.



PoC Overview

Time exceeded indicator

Time exceeded indicator is an indication signifying that the maximum talkbursttime has been exceeded and the talkburst is interrupted. In order to continue witha new talkburst, the user needs to release and press the push to talk key again.

Transmission failed indicator

Transmission failed is an indication signifying that the transmission attempt hasfailed. Reason for failure can be, for example, that the downlink connection to therecipient could not be established in one-to-one call or talkburst collision (seeAnswering mode).

Incoming call indicator

A new incoming call is preceded by an indicator. A new call means a voicetransmission after a period of inactivity in the communication. It can also mean achanged communication party in a call.

3.2.5 User identification

Uniform resource identifier (URI)

PoC users, groups and folders are uniquely identified by SIP URI. This identifieris used for the system and user management. It is also used for calling a user orjoining a group session and it can be used for identifying the calling or talkingparty.

The domain name part of the user and group URI has to uniquely identify theoperator. The user part of the URI can be used to contain relevant information toidentify the user (personal name, company, telephone number and so on) or thegroup. The URI for a user can be, for example, [email protected].

The URI for an open or a closed join-in group which has been created by the usercan be, for example, sales&[email protected], and the URI for aprovisioned open or closed join-in group could be [email protected].

The name of a temporary dial-out group is always 'adhocinstant', for example,[email protected].

Tel uniform resource locator (Tel URL)

In addition to SIP URI terminals can also use Tel URL. It is possible to mapMSISDN to a SIP URI using ENUM servers. The operator's ENUM server findsout the SIP URI corresponding to the particular MSISDN and forwards themessage further. A Tel URL could be, for example, tel:+1240555222.



19 (74)

End-user features

Mnemonic

The mnemonic can be used to identify the calling or talking party in addition to,or instead of, the user's SIP URI. A terminal may display the mnemonic as theuser identification. It is possible to use a different mnemonic in one-to-one callsand in different groups.

The end users may (depending on their rights) select a mnemonic for themselvesto be used in PoC communication. Mnemonic stands for the display name shownto the B-party. If the users are not allowed (by the operator) to change themnemonic themselves ('Right to define own mnemonic'), the mnemonic may bedefined by the operator. If the mnemonic field is not configured, the user part ofthe SIP URI may be shown to the B-party.

It is completely up to the terminal whether the mnemonic sent from the system isactually displayed or the name stored in the local phonebook is shown.

3.2.6 MSISDN dialling

Generally the routing of calls is done using SIP URIs but in addition to thatMSISDN can be used to make calls. The system extends this identification byadding an operator configurable default domain and forms a SIP URI that is usedin PoC session establishment.

In enhanced MSISDN dialling, the system makes a query to an external ENUM-DNS server using the MSISDN number as input and gets the corresponding SIPURI value in return.

3.3 One-to-one communication features

3.3.1 One-to-one call

One-to-one call is a feature where the target of push to talk communication is asingle user instead of a group. Users can select the person they wish to talk to andthen press the push to talk key to start talking.

The one-to-one call session starts when the call is initiated and will be releasedafter a period of inactivity.



PoC Overview

It is possible to restrict one-to-one calls between PoC users. Because the nature ofpush to talk traffic is such that there is no answer by the recipient, the usersthemselves may wish to restrict and filter push to talk calls they are willing toaccept immediately. For more information, see PoC Group and Access ControlList Management Interface and PoC Access Control List (ACL) ApplicationProgramming Interface (API). Normally enterprise and consumer users requiredifferent call authorisation models:

. In enterprise use, call authorisation is determined by predefined fleet andaccess right information. A fleet is a predefined set of users belonging tothe same company. A large company can also have a structure of severalfleets. Fleets are created using folders. Enterprise use usually entails thatthe company imposes communication restrictions and establishes cross-fleeting with other companies when needed.

. In consumer type of use, the calls between any users can be pre-authorised,or the user can enable and filter calls using personal access control lists(accept and reject lists).

Users that are currently active in the same group session can make one-to-onecalls to each other.

One-to-one call service in general can be set per user and, in addition, receivingcalls outside the closed user group can be prohibited in the PoC system on a userbasis. Joining a group session does not block incoming one-to-one calls or theinitiating one-to-one calls.

3.3.2 Answering mode

Depending on the terminal, the user may have the option of selecting whether theincoming calls are acknowledged automatically, in other words, the voice can beheard without answering, or whether the user gets an incoming call notificationand needs to manually accept the call.

With the access control list feature the user can filter which incoming calls arenotified/answered automatically and which completely ignored.



21 (74)

End-user features

wen

高亮

3.4 Group communication features

3.4.1 Open join-in groups

Open join-in groups are open groups which anyone who knows the groupidentification can join. The group identification can be found, for example, on aWeb site or chat room. However, an open talk group has to exist before any userscan join it.

Open join-in groups can be created by the end users themselves using terminals.Thus, a user does not have to have access to a provisioned group in order to havegroup communication within the PoC service. User-initiated groups aretemporary. However, a group may be stored in terminals for further use. Theoperator can also establish provisioned open join-in groups.

The creator of an open join-in group registers the open join-in group SIP URI intothe PoC Call Processor by activating the group for the first time and may deletethe group by removing the SIP URI registration from the PoC Call Processor. Thecreator can also determine whether the group members can re-distribute the groupdefinition to new members.

After the last member of an open join-in group has detached from the groupsession, it is deleted from the system. Also one-to-one calls are possible within anactive open join-in group session.

3.4.2 Closed join-in groups

Closed join-in groups are groups where access is limited to predefinedparticipants. For closed join-in groups different access control methods are used.The users need to know the group identification, but they also need to have theright to join the group session.

Access control for a group can be based on a group member list listing specificmembers or it can be based on folders defined in the provisioning level. The latteris an excellent method for enterprises where all users of a certain company areallowed to have group communication with each other.

There are three types of supported closed talk groups, differing in how the groupis created and how the allowed users are defined:



PoC Overview

. In the provisioned group the allowed users are defined by a managementuser using folder based definitions. This group has to exist before users canjoin it.

. In the ad hoc pro group the allowed users are defined by the members of anexisting base group. The base group has to exist before users can join thead hoc pro group. The base group must be a provisioned group.

. The list-based group is a closed talk group with member list based accesscontrol. Group member lists can be created by the operator using theprovisioning interface, or by end users using a web portal. A web portal isnot part of the PoC offering, it is up to the operator whether access to one isprovided.

Communication

The originator selects the group by any means available in the terminal (forexample, selection from the group list or manual URI entry) and joins the group.If the group exists, the user becomes a participant in a group session, and starts tohear traffic (if any) in the group. The right of the user to join the group is checkedthrough one of the following means, depending on the group:

. In a provisioned group access to the group is checked against folderdefinitions.

. In an ad hoc pro group access to the group is checked according to the basegroup, the identity of which is contained in the group id.

. In a list-based group access to the group is checked against the list.

While being in a group session, a user will receive traffic in the form of talkburstsaccompanied by a talking party identification. Whenever receiving traffic from agroup, the user also sees the group identification. The user can talk to the groupby pressing the push to talk key.

Users can leave the group session whenever they wish without affecting the restof the group session.

No explicit communications termination is required. Participants leave the groupwhen they desire and when there are no more participants, the group session isterminated by the server. As opposed to one-to-one and dial out group sessions,the system does not terminate the session based on inactivity, when no-one hastalked recently (the system may however terminate the session if unused for anexceptionally long period).



23 (74)

End-user features

3.4.3 Temporary dial-out groups

In dial-out group sessions, the calling party invites other participants to thesession. In a temporary dial-out group participants are selected temporarily by thegroup initiator. The calling party can select the participants from the PoC contactlist of the terminal.

Depending on the settings, the session is automatically or manually connected.Users may also use access control lists to allow or prohibit invitations fromcertain users.

A temporary dial-out group is used to establish a group session between a numberof users without the need to have an existing, predefined group.

Communication

The user selects the objects from the contacts list and initiates the establishmentof a temporary dial-out group session by pressing the push to talk key. The serverthen invites the required participants separately to the session. The invited userreceives the identifications of the group and the originating user. The invitedusers then accept the session manually, or automatically, each according to theirpredefined settings. The originating user will be given a notification of the resultper invited member (for example, accepted, rejected, not reachable).

When at least one invited participant has accepted, the group session enterscommunication phase, and any of the currently present participants can startcommunicating. During the communication phase, any user in the session cantalk to the group by pressing the push to talk key. The originator may add newparticipants to the session, if it is enabled by the terminal.

The session is terminated when the originator disconnects from the group orwhen the server disconnects the session because of an inactivity timeout.

3.5 Control features

3.5.1 Access control lists

Access Control Lists (ACLs) affect all incoming calls (either incoming dial-outgroup sessions or one-to-one calls). When there is a need to control which PoCcalls to accept, an accept list can be used. An accept list allows the user to specifyexactly which users may call directly to them.



PoC Overview

As a complement also a reject list is available. A reject list defines who are notallowed to call a user. The default way to use a reject list is that a user, inprinciple, accepts any authorised calls but wants to reject calls from specific usersthat are explicitly placed on the reject list.

This feature is particularly useful for consumer users; in this case, calls might bepre-authorised between any private users, and users could enable and filter callsusing their personal access control lists. Access control lists are also a usefulfeature for enterprise users, for example, to control one-to-one calls from theconsumers.

3.5.2 Group member lists

It is possible to establish a list-based group and list the allowed members of thatgroup.

All the members of that list can join the group. If a user who is not on the list triesto join the group session, PoC network elements reject the attachment.

3.5.3 Multisession support

The PoC system supports multisession operation and scanning.

Multisession operation allows a user to participate in more than one session at atime and to conduct one-to-one conversations while being in a group session. It isup to the operator to configure how many multisessions are possible.

Scanning allows a user to receive voice traffic from more than one simultaneoussession, for instance to monitor and participate multiple groups simultaneously.Only join-in type groups can be scanned. When scanning is not used, the user willonly receive traffic from the primary group session, and voice transmission willalso go to this group session.

When scanning is used, traffic from any active group session may be heard, oneat a time, but traffic from the primary group session will override. Note, however,that one-to-one traffic always overrides group traffic. No group traffic is receivedif there is an ongoing one-to-one session. For other groups a timeout mechanismis provided to ensure that a coherent discussion is heard. Normally the user'stalkbursts go to the primary group, but it is possible to respond to a talkburst in anactive group session that is other than the primary group session, during a periodafter which the terminal returns to the primary group session.



25 (74)

End-user features

The PoC system enables the selection in a terminal to switch scanning on or off.When 'on' has been selected, the groups to be scanned are the ones to which auser has joined. When there is no ongoing communication, the terminal resumesthe standby mode leaving the session still open.

3.5.4 Group advertisement

The users can advertise groups to desired members by using special SMSmessages generated by the PoC application (this requires that the SMS facilitiesare provided by the carrier). Group advertisement can also be used with bluetoothor infrared. Group advertisement compatible terminals can send SMSs withoutPoC involvement to advertise groups.

A user becomes a group member by receiving the group as group advertisementSMS and storing it into the terminal's group list. Other options (such as ignore oractivate session immediately) may also be available upon receiving a group-definition SMS. Creating special SMSs is not part of the PoC system but is theresponsibility of the terminal.

3.5.5 Anonymous communication

A user may be allowed to toggle anonymity on and off. In such a situation, theoriginating and talk user identities of this user are suppressed, or replaced by an'anonymous' identity. Anonymous operation suppresses the delivery and displayof the SIP URI. It does not affect the delivery and display of the mnemonic.

The mnemonic is also suppressed if

. anonymous communication is allowed and activated,

. users are not allowed to define their own mnemonics,

. the operator does not provision any mnemonic for the user.

In situations like this, the terminal may display an anonymous indication (forexample, a blank or question mark).



PoC Overview

3.6 Supporting features

3.6.1 Callback request

A callback request is intended for cases when a calling party fails to contact thedesired called party and wishes to leave an explicit message to request the calledparty to call back. The callback request is also used instead of a push to talk voicetransmission when a less obtrusive method of alerting is desired.

Whenever users want to leave a callback request at the terminal of another user,they select the target (for example, from the phonebook) and send the callbackrequest. When the target responds to the callback request by talking back, thisappears to the originator as a normal incoming push to talk call. Callback requestswill be delivered to the terminal regardless of the do not disturb state (see Do notDisturb).

Callback requests can be sent to any user that is registered and available, unlessthe sending party is on the reject list of the receiver. If the callback request doesnot succeed, the sending party receives information about the request not beingsuccessful. To respond to a callback request with a one-to-one call, a user canselect the target from the list of callback requests and place a call.

3.6.2 Do not Disturb

Do not Disturb (DnD) mode is intended for situations where immediate receptionof audio and incoming sessions is not desirable. When this mode is selected, therecipient user does not receive any push to talk voice communication. Theterminal in Do not Disturb mode does not hear the PoC traffic but may stillappear as a member of a group session.

The originating user receives a do not disturb indication from the PoC CallProcessor when trying to initiate a one-to-one call to a user who has selected theDo not Disturb mode.

3.6.3 Group participant info

A user who is currently in a group session can request a list of current participantsof that group session. A terminal in a session can also subscribe to notifications ofgroup members joining/leaving the session.



27 (74)

End-user features

3.6.4 PoC Presence

PoC Presence information can be used to enhance the Push to talk service. Theend user can see, before making a call, which users are online and available forthe call and which are not. With PoC Presence it is also possible to reduce thenumber of unsuccessful PoC calls due to the recipient's Do not Disturb mode orunavailability for PoC.

PoC Presence information, including also PoC availability, of individualsubscribers is held in the Presence Server. The PoC Call Processor, which isconnected to the Presence Server, updates the subscriber's PoC status changes tothe Presence Server. The Presence Server then distributes the availabilityinformation to the subscriber's terminal through the mobile network.

The PoC access control lists are used to define the users that can or cannot contacta particular user. Setting users to a reject list not only prevents them from makingPoC calls to that particular user, but it also prevents them from seeing the user'sPoC availability.

PoC Presence is an optional feature defined on the user level. PoC Presence canbe enabled/disabled by an individual subscriber.



PoC Overview

4 Operator features

4.1 Communication reliability

4.1.1 Acknowledged one-to-one call start

The system allows configuring how the �ready to talk� indication by the networkis generated to the calling party in a one-to-one call. The alternatives are:

. More reliable; the PoC system sends call signalling to the called party andwaits for an acknowledgement before giving a �ready to talk� tone to thecalling party. This can be conducted automatically by the terminal or it canbe a manual acceptance.

. Faster; the terminal gives the �ready to talk� tone to the calling userimmediately after it has checked all authorisation and related details fromthe PoC system.

This selection is intended for the purpose of selecting the wanted end-userexperience for the service in the operator�s network, not as a means for creatingdiffering service variants in a single system.

4.1.2 Service recovery

Automatic re-logon

Service recovery is a terminal implementation dependent functionality whichtakes care of the fact that the end user sees the PoC subscription always active (ortemporarily unavailable) in the user interface without any special actions. In otherwords, the user does not have to do anything to get the service back in case theterminal has lost it for some reason, if such a feature is supported by the terminal.



29 (74)

Operator features

Maintaining the group and session settings automatically

Group joining, scanning and other settings may be automatically restored by aterminal after temporary drop-out from the service, for example, because of acoverage problem or noise.

However, when the user inactivity timer expires, the user is considered logged offfrom PoC service in the network side. In such case, a terminal also needs to logon to restore the service. Log on is handled automatically with the servicerecovery functionality, if supported by the terminal.

4.2 Provisioning

4.2.1 PoC Register element

Provisioning is the essential step in deploying the PoC service. It does not onlymean adding new subscribers to the PoC system, but it also provides a way ofmanaging the subscribers and their access and service rights.

The PoC Register is a centralised provisioning element that handles theprovisioning-related tasks:

. provides an Application Programming Interface (API) towards theoperator's provisioning system

. provides a browser-based Management User Client (MUC) user interface

. provides a database for the provisioning data

. distributes the provisioning data to the PoC Call Processors

. provides troubleshooting and network management-related functionality.

Figure PoC provisioning model illustrates the elements and interfaces involved inPoC provisioning.



PoC Overview

Figure 4. PoC provisioning model

The PoC Register is the master database of all provisioned data (folders, users,and groups). It receives provisioning information through one of the APIs or thebrowser-based MUC interface, after which it distributes the provisioning data toall necessary PoC Call Processors in the PoC system. Once the data is stored inPoC Call Processors, all required authorisation and other data is available locally.Therefore, real-time requests from PoC Call Processors towards the PoC Registerare not necessary. This speeds up the service significantly.

Figure PoC provisioning information flow describes the information flow withinthe PoC system.

MUC interface

Provisioning usersand groups to folders

Provisioninginterface

Management UserClient (MUC)

Operator'sProvisioning System

Provisioning API

Resellers OperatorsWAP/webself-care

PoC system

GSM

SMSCNokia Terminal

Management Server



31 (74)

Operator features

Figure 5. PoC provisioning information flow

4.2.2 Folder structure

Before the service is started and users are provisioned to the system, a carefulplanning of the folder structure is needed. The folder concept is an essential partof the closed user groups of the PoC system. Folders are used for clustering users,groups and Management Users (MU). The concept of folders is similar to adirectory tree structure in common operating systems. Each folder can contain:

. subfolders

. users

. provisioned groups.

Folders are management tools for operators, and as such they are invisible to endusers.

PoC Call Processor

AuthorizationServer(s)

PoC Register

Provisioningdatabase

Distributing provisioning data

Provisioning data through Provisioning interface(Provisioning API and MUC interface)

PoC system



PoC Overview

wen

高亮

Figure 6. Folders and subfolders

4.2.2.1 Load balancing based on folders

Most of the communication between users occurs in the same geographical area.Users tend to communicate mostly with friends or colleagues in the same city orarea. This allows the planning of capacity usage. It is done in the following way:

. Each folder from a certain level in the folder structure (in the figure folders'Area1', 'Area2', and so on) is dedicated to a certain hardware resource.

. Each resource has its physical limitations in sending and receiving packets.By grouping users from the same geographical area into one folder it ispossible to minimise the hardware needs. One resource serves the users inthe same area, and inter-server traffic can be minimised.

4.2.2.2 Folder redeployment

When the service usage grows, adding new PoC Call Processors is very easy �

the operator just needs to allocate one or more existing folders to be served by thenew PoC Call Processors. All of the users, folders and groups that are provisionedunder the folder are automatically served by the new PoC Call Processor. Noaction is required from end users and they will not notice significant servicedowntime.

The User Control Server (UCS) is the only contact point for the terminal. When aNokia terminal logs in for the first time after the redeployment, the old UCSsends the host name of the correct UCS to the terminal using a Session InitiationProtocol (SIP) message (by means of a REDIRECT message). The terminal storesthe address of the new UCS after a SIP message has indicated that the UCS hasbeen permanently moved to the new address. This operation is invisible to usersand lasts only for around a second. It takes place only once for each subscriberthat has been assigned to the new UCS.

Consumers

Area 1 Area 2 Area N...



33 (74)

Operator features

wen

高亮

wen

高亮

wen

高亮

For more information on folders, see PoC Provisioning.

4.2.3 Provisioning APIs

Adding a new subscriber to the PoC system can be done via APIs. TheProvisioning API provides three different protocols that can be used forconnecting the PoC system to the operator's existing provisioning system. Theprotocols are:

. Java Application Programming Interface (Java API)

. Simple Object Access Protocol (SOAP)

. HTTP.

All three interfaces are secured with the Secure Sockets Layer (SSL). Theinterfaces are typically an integration point from the operator�s customer caresystem.

The same actions as with the Provisioning API can also be done with theManagement User Client (MUC) tool.

4.2.4 Management User Client tool

A browser-based graphical Management User Client (MUC) tool provides aninterface to perform provisioning actions. The operator can also use the MUC introubleshooting, to retrieve information available via this interface from thesystem, and for performing certain technical management actions. The MUC userinterface uses HTTP in the provisioning interface.

The provisioning actions that a management user can perform using MUCdepend on the rights granted to the management user.

Folder provisioning

The management user can perform the following folder provisioning actions viathe provisioning interface:

. creating folders

. modifying folders

. deleting folders

. listing folders

. querying folder attributes



PoC Overview

User provisioning

The management user can perform the following user provisioning actions via theprovisioning interface:

. creating users

. modifying users

. deleting users

. listing the users of a folder

. querying user attributes

Talkgroup provisioning

The management user can perform the following group provisioning actions viathe provisioning interface:

. creating groups

. modifying groups

. deleting groups

. listing the provisioned groups of one folder

. querying group attributes

The management user can also manipulate the user owned groups and relatedmember lists, if the management user has access to the folders of the usersowning the groups and member lists. The management user can perform thefollowing provisioning actions:

. creating user owned groups

. modifying user owned groups

. deleting user owned groups.

. listing user owned groups

Management user provisioning

The management user can perform the following management user provisioningactions via the provisioning interface:

. creating management users

. modifying management users



35 (74)

Operator features

. deleting management users

. listing management users

. querying management user attributes

A higher-level management user manages the management user's specific rightsto perform various provisioning actions. When management users are created,they are granted rights to various provisioning actions regarding folders, groups,users, and other management users. The higher-level management user can alsomodify other management users' rights to perform these provisioning actions.

User Access Control List (ACL) provisioning

The management user can manipulate user owned access control lists, providedthat the management user has access to the folders where the users are located.The management user can perform the following provisioning actions via theprovisioning interface:

. listing user ACLs

. modifying user ACLs

Dynamic reports

The management user may request the following dynamic data using the PoCRegister provisioning interface:

. attached members of a group

. logged-on users of one folder

. attached groups of one user

. active ad hoc pro groups of one base group

The actual dynamic information is fetched from the PoC Call Processor ControlPlane elements.

Folder, user, group and management user states

Each folder, user, group, and management user has an operational andadministrative state. The administrative state can be set as enabled or disabled.When the administrative state of a user, group, or folder is set as disabled, itmeans that the user, group, or folder in question cannot access the PoC service.The administrative state can be used to temporarily deny the PoC service, forexample, because of an unpaid bill.



PoC Overview

The operational state is set automatically by the system. The operational state iseither enabled, disabled, or deleted. When the operational state of a user, group,or folder is disabled or deleted, it is not possible to perform provisioning actions,in other words, modifications or deletions.

4.2.5 Subscriber provisioning

The operator can add a new subscriber to the PoC service by performing thefollowing steps:

1. provisioning the PoC system with the new user

2. provisioning the user's terminal with PoC settings.

The provisioned subscriber is put in one (and only one) folder. The subscriber isalso granted the access and service rights of that folder.

4.2.6 Terminal settings

PoC subscription data can be delivered to an end-user PoC terminal by using aspecial SMS. This is, however, not a built-in feature in the PoC Register. TheSMS is generated by the operator's provisioning system after a user has beencreated to the PoC system. The Nokia Terminal Management Server (NTMS) canbe used for this purpose. At least the following data must be delivered to theterminal:

. user URL

. host name of the PoC Server to be used when the user logs into the PoCsystem for the first time

. password

. default domain name

. Access Point Name (APN) for GPRS access

4.2.7 Autoprovisioning

To enable PoC service to all subscribers that have PoC-enabled terminals, theoperator can implement an autoprovisioning feature.

When a PoC user that has not yet been provisioned attempts to log into the PoCservice for the first time, it triggers the autoprovisioning process. The PoC CallProcessor recognises that the user is new to the system and sends information in aSOAP message to the operator's provisioning system. If it is possible to provision



37 (74)

Operator features

the user into the PoC system, the provisioning system provisions the user. It canalso send the user's specific PoC settings to the terminal and an SMS notificationto the user. Autoprovisioning of the terminal can also be triggered if the user isalready provisioned but uses a new terminal without service settings(unprovisioned terminal) for the first time.

The Nokia Profile Manager (NPM), or another external subscription managementsolution, is used to support autoprovisioning functions.

As in folder redeployment, (auto)provisioning of all terminals in the PoC systemwith the same User Control Server host name is enabled by the redirectfunctionality. This simplifies the operator's (auto)provisioning process. SeeFolder redeployment in Folder structure.

4.2.8 Advanced service plans with folders

When the operator wishes to introduce different levels of service for push to talksystems, it is made easy with the use of folders. The following example illustratesa case in which the operator grants different service levels to different consumergroups to reflect different pricing plans. The different service levels are grantedby defining different folder attributes to the 'Platinum', 'Silver', and 'Gold' folders.

Example 1. Service levels

Figure 7. Different service levels

In this example, users in the 'Platinum' folders can create open join-in groups andtemporary dial-out groups with a maximum of 20 simultaneous participants. Theusers in the 'Platinum' folders have a 'platinum' service plan.

Consumers

Area 1 Area 2 Area N...

Platinum 2 Gold 2 Silver 2

Platinum 1Gold 1

Silver 1

Platinum NGold N

Silver N



PoC Overview

Users in the 'Gold' folders can create open join-in groups and temporary dial-outgroups with a maximum of six simultaneous participants. The users in the 'Gold'folders have a 'gold' service plan.

Users in the 'Silver' folders can create open join-in groups and temporary dial-outgroups with a maximum of three simultaneous participants. The users in the'Silver' folders have a 'silver' service plan.

Using a solution like this, it is easy for the operator to define different serviceplans and to deploy them all at the same time. The restriction of rights is checkedautomatically based on the folder in which the subscriber is located. If asubscriber wishes to change the service plan, the operator only needs to changethe subscriber's folder. The subscriber�s terminal does not have to bereprovisioned.

4.3 Administering corporate fleets

In a corporate environment push to talk can be used for instant and easycommunication between colleagues or groups, for example, for announcementsor collaboration in the field. Typical users include mobile workforce, such as:

. service and repair personnel

. couriers

. taxi, limousine services

. car rental

. public transportation

. airlines, airports

. harbours

. distribution

. construction companies

. entrepreneurs.

4.3.1 Organising corporate usage

In business use, call authorisation is normally determined by predefined fleet andaccess right information. A fleet is a predefined set of users belonging to the samecompany. A large company can also have a structure of several fleets. In PoC,fleets are created by using folders. Business use usually entails that the company



39 (74)

Operator features

imposes communication restrictions and establishes cross-fleeting with othercompanies when needed. This feature enables cross-fleeting, in other words,closed user groups extended between different companies with preconfiguredsettings.

Folder external access rights of one-to-one calls and joining in group sessions canbe defined in a flexible manner for each folder. It is possible to carry out differentuse cases between two or more cooperative companies. The following rights canbe defined separately:

. one-to-one speech communication

. one-to-group speech communication.

This feature is a combination of source folder and source user rights and folderhierarchy features.

In Push to talk the usage of communication can be organised according to tasks.For example, it may be important to be able to organise the communicationbetween different departments in a clearly defined manner. The Nokia PoCsystem allows various corporate usage scenarios, access control and usagevisibility, explained in the following example.

Example 2. SPA Inn

The hotel chain SPA Inn wants to use the push to talk service. TheSPA_Inn_Main folder is created in the PoC system. After that, several subfoldersare created. The SPA_Inn_Main folder contains the following subfolders:

. SPA_Inn_HQ

. SPA_Inn_Reception

. SPA_Inn_Drivers

. SPA_Inn_Cleaners

. Etc.



PoC Overview

Figure 8. Organising corporate usage

The users are placed in the corresponding subfolders depending on their role inthe hotel. For example, drivers are put into the SPA_Inn_Drivers folder.

The folders may also contain provisioned groups. For example, theSPA_Inn_Reception folder has a provisioned group named Reception_Group. Inthis example, the administrator of the push to talk service is able to manage andassign different access rights. By restricting access rights to the SPA_Inn_Driversfolder, it is assured that only the drivers and perhaps the receptionists are able toattach to that group (if the receptionists need to call the drivers, or if the driversneed to talk to each other). Similarly, the drivers are not able to listen to thegroups provisioned in the HQ (Headquarters) folder.

4.3.2 Administration by corporate management user

As explained in the example, a folder is dedicated to each corporate that wishes touse the push to talk service. The corporate may have one or more managementusers. Management users are able to create new subfolders, add new users to thefolders, create and modify communication rights.

SPA_Inn

HQ

Cleaners

Drivers

Reception

[email protected]

This is a provisioned groupwith the address:[email protected]

[email protected]

[email protected]

[email protected]

These are users of thePoC service. The users areprovisioned to the "reception"folder so their access rightsare limited by the folderparameters.



41 (74)

Operator features

The management users typically access the PoC Register through the operator'sportals connected to the provisioning APIs or the web interface using theManagement User Client tool. Management user rights are restricted, in otherwords, the management user of SPA_Inn hotels can only see or modify folders,users and groups in the SPA_Inn folder and its subfolders.

Corporate end users access the service using their terminals and cannot see thefolder structure. They only see if they are allowed to make a one-to-one call,attach to a group, and so on.

4.3.3 Communication rights management

The concept of defining access control rights on folder level simplifies theadministrator (management user) role significantly.

Example 3. Defining access control rights on folder level

If there are, for example, two departments in the same company, each havinghundreds of users, allowing one-to-one communication but not groupcommunication between the departments for the users is done as follows:

1. Create users from one department in one folder, and users from the otherdepartment in another folder (for example Reception and Drivers folders,respectively).

2. Allow the users from the Reception folder to access the Drivers folder forone-to-one calls only.

3. Allow the users from the Drivers folder to access the Reception folder forone-to-one calls only.

If a user changes department (move from Drivers to Reception), the new rightswill apply automatically when the user's 'account' is moved to the new folder.

If the access rights were defined individually per subscriber, the maintenancecould become laborious. With folder-based access control the access control canbe easily mapped in the corporate organisation structure as each department hasits own folder and each unit its own subfolder. Communication between the unitscan be restricted or allowed depending on the unit and the company�s preferences.

Access rights can be applied to one-to-one calls as well as to group calls, callbackrequests, and so on. The system is fully flexible in granting or restrictingcommunication rights.

For more information on management users and access rights, see PoCProvisioning.



PoC Overview

4.4 Charging

The PoC solution provides interfaces to an operator's Customer Care and Billing(CC&B) systems, enabling the integration of existing billing and provisioningenvironments to the PoC system. The most suitable method depends on theoperator�s existing billing system, and the convenience of the charging method inquestion for the operator�s requirements.

Charging Records

Charging is based on charging records (CDRs). CDRs are charging records thatidentify the customer to be charged and contain information about the usedservices. Services that can be charged in the PoC system are

. logon to PoC services

. one-to-one communication

. different types of group communications.

Both usage-based and event-based CDR types are produced by the PoC system.

Charging configuration settings

The PoC charging functionality is highly configurable. For example, thefollowing can be configured:

. The CDR types to be generated can be selected from the supported ones bythe operator, based on the charging model used by the operator.

. For push to talk bursts, the CDR generation can be configured either sothat each push to talk burst triggers separate CDR(s) or the speech volumesare collected for a period.

The charging method can be

. off-line charging with PoC Call Processor, for post-paid subscribers

. on-line charging with Nokia Intelligent Content Delivery (ICD), forprepaid subscribers. This is not a PoC Call Processor feature but availableonly if the operator has Nokia Intelligent Content Delivery (ICD).

The charging features allow the operator to implement a charging model based on

. time-based rate (duration of the service)

. flat rate (for example, monthly fee � no CDRs needed)



43 (74)

Operator features

. single fee rate (number of events counted)

. volume rate (seconds of voice).

Figure 9. PoC system charging

User id for billing

A user id of maximum 20 characters can be included to the CDR. It isprovisioned to a user and can be used, instead of URI, as a user id for billing (forexample, IMSI). Its intention is to help the adaptation of the PoC service to thebilling system.

The user id for billing is an additional name for the PoC user identity that isprovisioned to correspond to the URI of the user. For example, if the internationalmobile subscriber identity (IMSI) is used here, the PoC system does not check thereal IMSI from which the PoC information session was created.

CG

Customer Care &Billing System

CDR

PaCo

OSC

SGSN

CDR

CDR

On-line creditsynchronisation

PoC

GGSN

TA

ICD

IN orPrepaid

Service access

PoC CallProcessors



PoC Overview

Charging acknowledgements

An operator can enable the charging acknowledgement feature which means thata talkburst generates charging only if it has been acknowledged by the receivingterminal. Thus, a user does not need to be charged for unsuccessfulcommunication. The feature works as follows:

. A terminal acknowledges the talkburst after the talkbust has ended.

. The duration information is added to the CDR from the acknowledgement(based on the total duration of speech).

This feature increases charging accuracy but consumes some uplink capacity inthe radio interface.

For more information, see PoC Charging.

4.5 Operation and Maintenance in PoC system

PoC operation and maintenance (O&M) provides the tools for you to successfullyset up, maintain and tune PoC elements and services as easily as possible. PoCoperation and maintenance can be done at three levels: local and remote elementmanager level, the Nokia NetAct system level and higher level O&M systems.

When centralised network management is required, Nokia NetAct" provides apowerful solution. It enables the handling of not only PoC elements, but also allother elements in the network (for example, GPRS, radio network and IP networkelements). NetAct can also provide a northbound interface to third party O&Msystems.

Figure Operation and Maintenance architecture in PoC depicts the different levelsof the O&M in the PoC system.



45 (74)

Operator features

Figure 10. Operation and Maintenance architecture in PoC

Figure Operation and Maintenance interfaces in PoC illustrates the O&M systeminterfaces.

PoCCallProcessors

PoCCabinetSwitch

FEWS

EMCPoCRegister

Site routers

PoCCallProcessors

FEWS

EMC

Site routers

PoC system

O&M and CCBsite

NetAct

MUC

Traffica

DNS/CN

Chargingmediator

MasterDNS

RemoteEMC

SGSN

GPRSIP

BackboneGGSN

BTS BSC

O&M network

PoCCabinetSwitch

PoC Site 1 PoC Site 2

O&M data fromother network

element

DNS/T

Bearer network



PoC Overview

Figure 11. Operation and Maintenance interfaces in PoC

The main O&M functions offered by the PoC system are:

Element management

The PoC Call Processor and PoC Register both have their own element managers.They consist of a user interface on a workstation computer and elementmanagement applications that manage the different PoC and platformapplications.

PoC Call Processors

Northboundinterfaces

(ASCII, CORBA, XML)

Trafficamonitoringand analysis

EM Client

NetAct framework for fault, performanceand element management

ChargingGateway

Java RMICORBAFTPTelnet

EM Client

PoCSystem

CabinetSwitch

NWI3(CORBA)

SNMP

SNMP(NE3S) Telnet

Telnet

PoC RegisterGTP'

EM Client

Java RMICORBAFTPTelnet

NMS

SNMP

EM Client



47 (74)

Operator features

Most of the O&M functions in PoC Call Processor are handled using the ElementManager (EM). The Element Manager offers a graphical user interface (GUI) anda command line interface (CLI) for performing element management tasks, suchas monitoring alarms, setting performance measurements and handlingparameters.

The PoC Register element management is handled via the Element ManagerClient (EMC) that consists mainly of simple UNIX commands and shell scripts.The PoC Register uses the Sun Management Center enterprise edition forenhanced operation and maintenance. Fault management is done by contactingthe Sun Management Center via the network management system. Performancemanagement is done by contacting the Sun Management Center directly.

Fault management

PoC Call Processor fault management solutions include a network element levelalarm system and Alarm Browser, a tool for monitoring alarms, and on the otherhand, an NWI3 interface towards NetAct as well as an SNMP interface towardsany network management system (NMS) in use. The SNMP fault managementinterface is an optional feature for sending SNMP messages. The SNMP interfacesends traps of active PoC Call Processor alarms to the NMS. The alarms can bemanaged using the EM GUI application Alarm Browser or Nokia NetAct, or theycan be forwarded to other network management systems via the SNMP interface.

The PoC Register collects the application and platform level alarms and clearnotifications. They can be handled through the Sun Management Center. Afterthis the PoC Register passes the alarms and notifications to a networkmanagement system, such as the Nokia NetAct, using the Simple NetworkManagement Protocol (SNMP) interface. Alarms can be managed with EMCshell scripts.

Performance management

The PoC Call Processor provides a performance management framework thatprovides mechanisms to generate, collect, and process performance managementdata. Measurements can be set using the Performance Management GUI, and themeasurement results can be accessed either via Nokia NetAct or locally via KPIuser interface. The Element Manager also offers tools for monitoring real-timepeak values and the number of active users and groups in the PoC system. PoCCharging Records (CDRs) also give statistical information on usage trends ofdifferent services in the PoC Call Processor.

The PoC Register monitoring is implemented with the Sun Management Center(SunMC). Additional components are added to the SunMC to achieve moredetailed level system monitoring, performance reporting and configurationtracking.



PoC Overview

Parameter management

Parameter management provides PoC Call Processor applications with acentralised, replicated, abstract data storage accessible remotely from anywherevia the LDAP. Parameter management also provides the users with a genericgraphical user interface, Parameter Tool, and a command line interface thatenable access to the data stored in the LDAP directory. Parameter managementuses a standard LDAP Data Interchange Format (LDIF) which can be used for thecommissioning, mass configuration changes, and conversions. The ParameterTool is used for configuring and managing parameters in the PoC system.

The PoC Register network topology and element related parameters are definedin network configuration files that are maintained by the PMF application.

Software configuration management

PoC Call Processor software management provides tools for software versionmanagement. The main functionality provided is the downloading of software ondisk, the installation and uninstallation of software on disk and the activation ofsoftware in the cluster. Also, the inquiry of software versions on disk as well asthe verification of the installed software on disk are supported.

Backup and restore

PoC Call Processor backup and restore services provide means to back up andrestore the file system, the LDAP directory, and all the databases in the cluster.Backups are made by connecting to the CLM node and running a shell script. Toprevent failures, backups can be scheduled to take place automatically. As anadditional safety precaution, backups can be transferred to an external serverusing, for example, Secure Copy (SCP).

The PoC Register EMC provides scripts for taking database backups. Automaticbackups can be scheduled.

Hardware configuration management

The hardware configuration of the PoC Call Processor defines the location of thehardware elements (for example, CPU blades and hard disk blades) in thedifferent chassis of the cabinet. Hardware configuration offers the linkagebetween the logical cluster nodes and the actual hardware. Hardwareconfiguration description data can be modified and interrogated to some extent.

The hardware configuration of a factory-installed PoC Register system is alwaysthe same.



49 (74)

Operator features

User and security management

PoC Call Processor user and security management allows you to give differentuser and access rights to personnel performing element management tasks withEM GUI and CLI applications. Security logs contain information on session startand end times, unauthorised login attempts, and changing parameters in LDAPthat may be needed for security-related analysis.

The PoC Register EMC has no separate user management system, usermanagement is handled at OS level. One main user owns the scripts and hasrights for all operations in the EMC. In addition, there can be users that haverights to execute commands and scripts. The Sun Management Center contains 3(+1) user categories that include rights for different management operations.

Time management

Time management provides a wall clock time for reporting different events likefailures, statistical reports and charging. Network Time Protocol (NTP) is usedfor timing the cluster and its nodes.

Time management used in the PoC Register is used to provide exact time to allthe logs and events that are recorded in the application. The PoC Register usesNTP protocol to adjust its internal clock with the network-provided time source.

4.5.1 Cabinet switch

The cabinet switch provides layer 3 interfaces towards the operator's site network.The management of the cabinet switch is handled via tools provided by thevendor of the cabinet switch. The Nokia solution for the cabinet switch is CiscoCatalyst 6509 or 3750. They support CiscoWorks network management platformand SNMP versions 1, 2 and 3.

The cabinet switch is required in the PoC site to route traffic between the PoCRegister, PoC Call Processors, the operator's site and the O&M network.

For more information about the cabinet switch, see Cisco's O&M documentation.



PoC Overview

4.5.2 Nokia NetAct

Nokia NetAct provides centralised network management for PoC. It includescentralised fault management and performance management (for the PoC CallProcessor). Nokia NetAct also offers PoC Call Processor and PoC Registerelement manager launch, which contains local configuration management,software management with local element managers as well as user managementwith local element managers. All alarm handling and performance managementreporting applications are available for PoC.

Nokia provides an open OSS environment. Nokia NetAct offers open northboundinterfaces to forward the data from NetAct to 3rd party systems.

Nokia NetAct Traffica

Nokia NetAct Traffica enables operators to view and analyse traffic data. PoCCall Detail Records (CDRs) received via the Charging Gateway can providetraffic data for Traffica.

Traffica data can also be used as partial input in NetAct applications such asNetwork Monitor, Reporter and Service Quality Monitor (SQM).

4.6 Security

4.6.1 PoC call security

The connection from the PoC user to the PoC system services is built withstandard GPRS/WCDMA packet switched network functions, using Um/Uu airinterface and the underlying GPRS/WCDMA packet switched networkinfrastructure. Standard GPRS security functions are in use.

Confidentiality in PoC communication is based on physical IP networkingsecurity, ciphering of the GPRS/WCDMA packet switched network and VPNsolutions.

PoC user authentication

PoC application-level user authentication is based on the HTTP Authenticationspecification (RFC 2617), which is a challenge-response authentication method.PoC users use the HTTP Digest authentication method.



51 (74)

Operator features

The PoC system authenticates the users using the user name and push to talkpassword. This information is sent to the terminal over the air or typed inmanually. The password is not readable from the terminal. The password isencrypted information in the terminal, so copying the push to talk authenticationsettings from one terminal to another is not possible.

Authorization interface

With the authorization interface it is possible to implement an external MSISDNauthorization solution. In this solution the user's MSISDN is verified whenauthorizing the PoC user.

The Nokia Profile Manager (NPM), as a subscription management solution, canbe used for end-user autoprovisioning and authentication functions.

Secure group communication

Closed talk groups, predefined either using folders or group member lists, controlthe access to participate group talk, thus making the communication in groupssecured.

4.6.2 PoC administration security

PoC management user authentication

For management users using the provisioning interface, the basic username andpassword method is used.

Provisioning rights

The access rights of a management user can be defined flexibly, from rightslimited to one folder up to unlimited rights to all provisioned data.

Technical management rights

Authentication method for the element manager users of the PoC Call Processorand PoC Register is the basic username/password method.

Secure protocols

PoC supports SSH to enable secure management access to the PoC elements.Additionally, PoC Register supports secured provisioning interfaces usingHTTPS.



PoC Overview

4.7 Redundancy and scalability

Redundancy

The PoC product solution provides redundancy mechanisms, which are intendedfor failure situations like malfunction in hardware. The external connections tothe operator's system are also fully redundant. For more information, seeRedundancy and reliability of PoC Register in PoC Register Product Descriptionand Redundancy and reliability of PoC Call Processor in PoC Call ProcessorProduct Description.

Scalability

The architecture of the PoC system has been designed to provide technicallyunlimited scalability. The basic setup provides high capacity and it is easy to addcapacity to the PoC system. PoC Call Processors have two configuration options:basic and large. Due to the extreme scalability architecture of the PoC system, itis easy to add new PoC Call Processors to the live network.



53 (74)

Operator features



PoC Overview

5 PoC system architecture

In a nutshell, the PoC technology solution is as follows:

. PoC one-to-one and group calls are running over (E)GPRS/WCDMAnetworks.

. Logon to PoC service means SIP registration.

. Join-in group sessions are created by sending SIP INVITEs from theterminals towards the group in the server. The group can be preconfiguredor it may be created automatically in the session initiation.

. Dial-out group sessions are created by sending SIP INVITEs from theserver towards the terminals listed in the call initiation. The list of memberscan come from the initiating terminal or can be preconfigured in the server.

. Voice is relayed by the user plane of the PoC Call Processor as RTPpackets.

. Group connection is created by multiplying voice packets to the membersof a group session.

. In (E)GPRS/WCDMA packet switched network, PoC speech is transferredas normal data packets. Appropriate QoS differentiation, for examplebetween PoC and WAP can be made either with Release 97/98 priority orRelease 99 QoS mechanisms. More detailed information on (E)GPRSfeatures and QoS settings can be found in PoC Radio Access and CoreNetwork Recommendations.

The PoC solution in an operator's network can be centralised to only a few centraloffice sites consisting of one or more PoC Call Processors. The location andnumber of the PoC Call Processor sites can be based on traffic engineering.Typically, the sites would be close to the network's GGSNs.

Network-level scaling is based on the number of PoC Call Processors in thesystem, providing a highly scalable architecture.



55 (74)

PoC system architecture

The PoC solution provides interfaces to an operator's Customer Care and Billing(CC&B) systems, thus enabling the integration of existing Customer Care andBilling (CC&B) environments to the PoC system (see Figure PoC networkarchitecture).

The IP addresses for PoC terminals will be allocated using conventionalmechanisms that are used in the GPRS network.

PoC terminals and the elements of the PoC system make DNS queries in the PoCsystem. Slave DNS servers of the network-level DNS are an integral part of thePoC Call Processors. DNS for PoC terminals is implemented separately.



PoC Overview

Figure 12. PoC network architecture

PoCCallProcessors

PoCCabinetSwitch

PoCRegister

PoC system

PoC Site

SGSN

GPRSIP

Backbone

GGSN

FEWS

EMC

Bearer network

Presence Server

DNS/T

BTS BSC



57 (74)


QoS procedures

Because PoC data is transferred as normal data packets among other data, someQoS differentiation has to be used. Possible ways to differentiate real time andnon real time services are either to use Release 97/98 based priority QoS orRelease 99 based QoS procedures with streaming traffic class, depending onnetworks capabilities.

In case priority QoS concept is used, both the signalling (Control) and RTP media(Speech) shares a PDP context that is corresponding to interactive traffic class.With this approach only one PDP context is used by the PoC application.

In case streaming traffic class is supported by the network and terminal,streaming may be used to carry the RTP media (speech). In this case thesignalling is conveyed in PDP context corresponding to interactive while speechitems are transferred using streaming traffic class PDP context. This latterapproach uses two PDP contexts for PoC.

More detailed information on QoS procedures can be found in PoC (E)GPRS andWCDMA Recommendations.

5.1 Client-server architecture

PoC service is an application over the (E)GPRS/WCDMA PS network. On theterminal side, a terminal with a PoC client can be used. The used speech codec isthe AMR (Adaptive Multi Rate Speech) codec, used in 5.15 kbit/s mode.



PoC Overview

Figure 13. PoC client-server architecture

Figure PoC client-server architecture illustrates the PoC client-server model. Inthe client-server model, PoC Call Processors comprise the server part and PoC-enabled terminals comprise the client part of the PoC service. The clientscommunicate with the speech transfer and signalling functions.

(E)GPRS/WCDMA PSnetwork

POCapplicationservers

Session set-up: SIP protocol

Speech packets:STP/RTP



59 (74)


Figure 14. PoC protocol stack in the client-server interface

5.2 Logical planes of PoC system

The PoC system implements typical IP-based architecture. Figure PoC systemfunctional planes describes the plane division in the PoC system.

The User plane, Control plane, Management plane and Provisioning plane areseparate from each other. The main elements in the PoC system are the PoCRegister and the PoC Call Processors. The Provisioning plane is physicallylocated in the PoC Register. The User, Control and Management planes arephysically located in the PoC Call Processors. The planes are connected to eachother and to the end-user terminals via several IP technologies, such as

. Real-time Transport Protocol (RTP) and Streaming Transport Protocol(STP) in the User plane

. Session Initiation Protocol (SIP) in the Control plane signalling

. Media Gateway Control protocol (MEGACO) between the Control andUser planes

. Simple Object Access Protocol (SOAP) between the Control andManagement planes, between the Management and Provisioning planesand also within the Management plane.



PoC Overview

Figure 15. PoC system functional planes

PoC Register

PoC Call Processor

IP

Provisioning plane

Managementplane

User plane

Control planeSIP

SOAP/ XML

MEGACO

ProvsioningFunctions

MEGACO

User Group

ManagementFunctions

SOAP/ XML

UserFunctions

GroupFunctions

UserFunctions

GroupFunctions

SIP

RTPRTP/STP



61 (74)


User plane

Speech (Real-time Transport Protocol, RTP) packet handling and multiplying isperformed in the user plane of the PoC Call Processor (see Figure PoC systemplanes). The user plane takes care of the user-specific speech transfer. Each userbelongs to a specific user plane unit, which is informed to the terminal via thecontrol plane at the log-on phase. It is used regardless of the user's physicallocation. Each user and group also resides in a specific user plane unit. Theterminals send their RTP traffic to the assigned unit.

The user plane supports both the IETF RTP (based on RFC1889) and (Nokia)Streaming Transport Protocol (STP). The STP has a shorter RTP header part. Dueto spectral efficiency requirements, STP is used in the GPRS air interface. Themain task of the PoC Call Processor user planes is to forward the RTP packets toterminals via the GPRS network. The RTP packets carry embedded signals andvoice. The user plane is a two-tier system of user and group functions.

The user plane also acts as a centralised authority when deciding which terminalhas the rights to talk within a group session and one-to-one call session. This isdone by floor control signalling.

Control plane

The control plane (see Figure PoC system functional planes) of the PoC CallProcessor resides between the management plane and the user plane.

The control plane uses services provided by the management plane to check theuser rights, for example, call rights.

The control plane controls the SIP signalling with the terminal and within thePoC system. It manages the PoC service log-on/log-off, which refers to SIPregistration/de-registration, and the group and one-to-one call sessions, whichrefer to SIP sessions and group attachments and detachments. It alsocommunicates with the user plane using the MEGACO protocol, to create thenecessary group and user connections to allow communication. Sessions of theuser and group reside in a specific control plane unit of a specific PoC CallProcessor.

The control plane is a two-tier system of user and group functions.



PoC Overview

Management plane

The management plane (see Figure PoC system functional planes) includes thestatic user and group data. The management plane scales within one PoC CallProcessor. Folders, containing the groups and users, are distributed according toseparate units in the management plane. The user and group information residesin a specific management plane unit of a specific PoC Call Processor. User andgroup data is distributed to the units on folder basis.

Network-wide scalability is achieved so that the management planes of theseparate PoC Call Processors and the individual management plane units within aPoC Call Processor communicate with each other.

Users and groups are identified by SIP URIs. Subscriber, group and folder SIPURIs are mapped to the specific management plane unit, which contains theneeded folder data. The SIP URIs are independent from the networkconfiguration.

The management plane serves the control plane in the real-time rights checking.

The management plane provides the PoC user authentication services. Theauthentication data of the users is entered into the database of the managementplane via the provisioning plane.

Provisioning plane

The PoC system is connected to the operator's provisioning system through theProvisioning plane (see Figure PoC system functional planes). The Provisioningplane functionality is implemented with the PoC Register. There is onecentralised PoC Register per one PoC system.

The PoC Register replicates the information to the needed management planeunits of the PoC Call Processors. The PoC Register is also the centralised masterdatabase of the provisioned data, thus providing network-wide back up storagefor the static user and group data. The PoC Register is used for provisioningpurposes, and is not serving control plane real time requests. In the PoC Register,an operator's provisioning system is treated as a management user client andauthenticated in the same way as a management user, which connects directly tothe PoC Register through the Web interface.



63 (74)


5.3 Architecture of the main elements

Architecture of PoC Call Processor

The PoC Call Processor is based on the Nokia FlexiServer platform that usesNokia Blade Hardware. External network connections from the PoC CallProcessor are routed via the Cabinet Switch. The Cabinet Switch also connectsthe PoC Call Processor and PoC Register to each other. For more information, seeHardware architecture of PoC Call Processor in PoC Call Processor ProductDescription.

The software architecture consists of eleven different servers that function on theUser, Control, and Management planes of the PoC system. For more information,see Software architecture of PoC Call Processor in PoC Call Processor ProductDescription.

Architecture of PoC Register

The PoC Register is based on Sun NETRA hardware platform used in SunCluster configuration. For more information, see Hardware architecture of PoCRegister in PoC Register Product Description.

PoC Register functions on the Provisioning plane. For more information, seeSoftware architecture of PoC Register in PoC Register Product Description.

Architecture of Nokia Presence Server

See Nokia Presence Server Product Description for details.

PoC network dimensioning

The system consists of a single Register element and the scalability of thenetwork is based on adding more PoC Call Processors as needed. PoC Registersupports at least 10 million subscribers. The subscriber space (provisionedsubscribers) in the PoC Call Processor configuration is 400 000 (Basicconfiguration) and 800 000 (Large configuration) subscribers, but the space thatcan be practically used depends on the actual traffic profiles.



PoC Overview

6 PoC system interfaces

The following figure displays the interfaces in the PoC system.

For more details on the interfaces, see Interfaces of PoC Call Processor in PoCCall Processor Product Description and Interfaces of PoC Register in PoCRegister Product Description.



65 (74)

PoC system interfaces

Figure 16. PoC product interfaces

Other PoCnetwork

PC Client

Chargingmediator

Nokia PS

ACL management

PoCRegister

Managementworkstations

Backup system

Nokia NetAct

Nokia NetActTrafficaNokia CG

Nokia NPM orother subscriptionmanagement system

Nokia NNI (SIP, RTP)

Auth/autoprov. (SOAP)

Presence WSI (SOAP)

ACL mgmt (SOAP)

Nokia client (SIP, RTP/STP)DNS, NTP, etc

O&M (CORBA,Java, Telnet, FTP)

Intercollegiate(SOAP, SIP, RTP)

PoC CallProcessors

R/CP(SOAP)

O&M (Telnet, FTP)

Nokia NPM orAuth/autoprov. proxy

Backup(Telnet, FTP)

O&M (SNMP)

O&M (NWI3)Provisioning(SOAP, Java,HTTP, GUI)

Charging (GTP')

Charging (FTP)

Basic IPservices

Packet Core,ICD

SIP/SIMPLE

Web portal

Group and ACL mgmt



PoC Overview

6.1 Terminal interface: Nokia PoC client interface

Operators using the Nokia PoC network solution can provide PoC services tousers using Nokia client interface compatible terminals. PoC Release 1.5 iscompatible with Release 1.0; Release 1.0 terminals are fully supported.

SIP protocol is used for control signalling and RTP is used for transmitting thespeech packets.

The SIP/SIMPLE client interface support enables an option to configure the PoCCall Processor to proxy SIP/SIMPLE based Presence communication between theterminal and the Nokia Presence Server. This kind of configuration setup enablesthe usage of one APN for both PoC and Presence and provides the terminal with asingle contact point. The required settings in the terminals are the same for PoCand Presence. The SIP/SIMPLE client interface uses SIP for control signallingand Presence information delivery.

6.2 Presence interfaces

SIP/SIMPLE PoC Presence Update interface (WSI)

With the SIP/SIMPLE PoC Presence Update interface it is possible to implementthe PoC Presence solution that makes it possible for a PoC user to see theavailability of other PoC users. The PoC Call Processor acts as a proxy for thePresence Server.

When a PoC user is logged on, logged off or chooses the Do not Disturb mode,PoC Call Processor sends this status information to the Presence Server, which inturn distributes the information to other PoC users. After this, the terminal clientcan show directly in the contact list who is available for PoC communication.

It is possible to connect one Presence Server to several PoC Call Processors.

Wireless Village Presence Update Interface (WSI)

The Wireless Village Presence Update Interface is used for exchanging presencedata between the PoC Call Processor and the Presence Server. The interface isimplemented with SOAP.



67 (74)


6.3 Provisioning interface

The Provisioning interface provides an Application Programming Interface (API)which can be connected to the operator's provisioning system. The interfacesupports Java API, HTTP API and Simple Object Access Protocol (SOAP) 1.1API. All these three interfaces can be secured by Secure Socket Layer (SSL). TheProvisioning interface also provides a browser-based Management User Client(MUC) interface.

6.4 Register - Call Processor interface

The Register - Call Processor interface is used by the PoC Register to distributethe provisioning data to the applicable PoC Call Processors and configuremapping information in one or more PoC Call Processors.

6.5 Group and access control list managementinterface

Group and access control list (ACL) management interface is an interfacebetween the PoC Register and a web portal.

The ACL management interface is an open Application Programming Interface(API) towards the operator's customer care functions. Depending on theoperator's preferences, these functions may include a web and WAP portal for theend-user self-management purposes.

6.6 Access Control List (ACL) management interface

The PoC Call Processor provides an Access Control List (ACL) managementinterface which is used by the gateway of the self-management portal. Forinformation on the functionality of the interface, see Group and access control listmanagement interface.

6.7 Charging interfaces

The PoC Call Processor provides charging interfaces which are used fortransferring charging data.



PoC Overview

Enhanced GPRS Tunnelling Protocol (GTP') is used for transferring ChargingRecords (CDR) to the Nokia Charging Gateway. One GTP' message may containone or more CDRs.

File Transfer Protocol (FTP) is used for transferring large files containing severalCDRs to a charging mediator.

6.8 Operation and maintenance interfaces

PoC Call Processor O&M interface

The PoC Call Processor provides an Operation and Maintenance (O&M)interface for operation and maintenance activities. The IP-based O&M interface iscomposed of several technologies:

Network Interface for 3rd generation networks (NWI3)This interface is used between the Nokia NetAct and the PoCCall Processor, for example. Also several other Nokianetwork elements provide an NWI3 interface towards theNetAct. The Element Manager Client (EMC) uses thisinterface for session establishment within the ElementManager. The EMC runs in a local or remote PC/laptop. TheElement Manager runs inside the PoC Call Processor.

SNMP fault management interfacePoC SNMP fault management interface enables integratingPoC Call Processor alarms into an existing NMS. With theSNMP protocol it is possible to send alarms generated in thePoC Call Processor to any standard NMS server that supportsSNMP.

Common IP protocolsThe FlexiServer platform provides services and protocols fordebugging, diagnostics and configuration of the IPfunctionality and several client/server IP applications.Examples of these are FTP server and client, Telnet, netstat,dig, ping, and traceroute.



69 (74)


PoC Register O&M and alarm interface

The PoC Register O&M and alarm interface is the PoC Register ElementManager interface. It consists of an Element Manager Client interface and anO&M interface. The EMC interface is used for maintenance and managementpurposes. The O&M interface uses the Nokia Enhanced Simple NetworkManagement Protocol (SNMP) to deliver alarms to an external networkmanagement system.

PoC Call Processor Backup interface

The PoC Call Processor Backup interface can be used to make backups of thesoftware and databases of the PoC Call Processor.

PoC Register Backup interface

The PoC Register Backup interface can be used to make backups of theprovisioning database.

6.9 Intercollegiate interface

The PoC Call Processor provides an intercollegiate interface for transferringauthorization information, control signalling, and speech packets between PoCCall Processors. The intercollegiate interface is used when the information onsubscribers and groups is located in different PoC Call Processors.

The intercollegiate interface uses SOAP for transferring authorization queries andresponses and also for transferring queries and responses related to the correlationinformation about users and groups. SIP is used for transferring controlsignalling, such as one-to-one call establishment, user attachments to a group, anduser detachments from a group. RTP is used for transferring one-to-one call andgroup call speech packets.

6.10 Nokia Network-to-Network Interface (NNI)

PoC network element architecture provides the Network-to-Network Interface(NNI) between two compatible PoC networks. With the NNI, different operatorsthat have compatible PoC systems can provide PoC services between end usershaving subscriptions from the different operators. This enables a wider usercontact basis.

The NNI interface supports all end-user to end-user services. The interface usesthe SIP and RTP protocols.



PoC Overview

Addressing in NNI is based on assigning specific domain names for differentoperators.

6.11 Authorization interface

With the authorization interface it is possible to implement an external MSISDNauthorization solution. In this solution user's MSISDN is verified whenauthorizing the PoC user.

When a user tries to use PoC services, a SOAP request may be sent from theAuthorization Server (AuS) to an external auto-provisioning element to requestMSISDN authorization. The external auto-provisioning proxy will perform theMSISDN authorization operation.

6.12 Autoprovisioning interface

With the autoprovisioning interface it is possible to implement an externalautoprovisioning solution. This solution makes automatic provisioning possiblefor PoC users.

When a PoC user that has not yet been provisioned attempts to log in to the PoCservice for the first time, it triggers the autoprovisioning process. In this processthe PoC Call Processor sends information in a SOAP message to the operator'sprovisioning system. Based on this information, provided that provisioning ispossible for the user, the provisioning system can provision the user and sends thePoC settings to the terminal and a notification to the user.



71 (74)




PoC Overview

7 Glossary

ACL Access Control List

AMR Adaptive Multi-Rate Speech Codec

API Application Programming Interface

APN Access Point Name

BSC Base Station Controller

BTS Base Transceiver Station

CC&B Customer Care and Billing System

CDR Charging Record (Call Detail Record)

CG Charging Gateway

CORBA Common Object Request Broker Architecture

CPU Central Processing Unit

DNS Domain Name System

(E)GPRS (Enhanced) General Packet Radio Service

EMC Element Manager Client

GGSN Gateway GPRS Support Node

GPRS General Packet Radio Service

GTP' Enhanced GPRS Tunnelling Protocol

IETF The Internet Engineering Task Force

LDAP Lightweight Directory Access Protocol

LDIF LDAP Data Interchange Format

MEGACO Media Gateway Control



73 (74)

Glossary

NTP Network Time Protocol

NWI3 Network Interface for 3rd generation networks

PM Performance Management

PMF Provisioning and Management Function

QoS Quality of Service

RMI Remote Method Invocation

RTP Real-time Transport Protocol

SGSN Serving GPRS Support Node

SIP Session Initiation Protocol

SOAP Simple Object Access Protocol

STP Streaming Transport Protocol

TCP Transmission Control Protocol

URI Uniform Resource Identifier

VoIP Voice over IP



PoC Overview

Date post:	30-Jan-2018
Category:	Documents
Upload:	truongduong
View:	225 times
Download:	0 times

00034649.00 Nokia PoC Rel. 1.5, Product...

Documents