CSTA Standard Enhancements in 8 th edition

1. Ecma/TC32-TG11/2012/004 CSTA Standard Enhancements in 8th edition

2. Highlights of enhancements in the 8th edition • New features that enable the establishment and control of advanced types of conferencing • Meet me conferencing • Conference reservation, etc. • Set of dedicated location-based features that enable location-aware applications • Tracking of location changes of users and devices • Call Control enhancements: • enable applications to deflect calls to multiple destinations • provide location information with CSTA call events (independent of location-based dedicated services) • Enhanced deviceID formats • indicate when a number and/ or a name associated with in a deviceID in a CSTA message should be treated as private (e.g. restrict presentation) • New features that allow applications to synchronize with a CSTA implementation • Query for active monitors & registrations after system events

3. Conferencing Enhancements • Specifies a Conferencing model for the life cycle of a conference • A new Make Connection service – to reserve conference resources for future use • Detailed scenarios (TR/82) that illustrate: • Creating a conference • Reserving a conference (scheduled conferences) • Enabling a conference • Inviting one or a set of participants to a conference • Populating a conference • conference participant added to conference after calling into a conference (meet me) • conference participant is added to conference after being called by conference (outbound) • Mixed use of inbound (meet me) and outbound for same conference • Automatically added after answer or after participant validation • Removing participants from a conference • Suspending a conference for future use • Releasing a conference • Etc. • Improves the existing conference after consultation and single step conferencing model

4. Conference Life Cycle • Creating a Conference • A conference involving a Conferencing Device may be created via the Make Connection service. The Make Connection service creates a conference call with one connection at the Conferencing Device. A conference can be created that is either reserved or enabled. • A reserved conference • refers to a call involving a Conferencing Device that allocates resources at a Conferencing Device for future use. A reserved conference is modeled with a Conference Device connection in an initiated connection state. • An enabled conference • refers to a call involving a Conferencing Device that is ready to process media between participants that will be added to the call or are already part of the call. • The Answer Call service may be used to enable a reserved conference by transiting the Conference Device connection state from initiated to connected (e.g. when a reserved conference is ready to start). • Once the conference is enabled participants may be added to the call via services like Conference Call and Single Step Conference Call. The participants may be authenticated (via speech, DTMF, etc.) prior to being added to the conference. • Removing participants • Participants may be removed from the call via the Clear Connection service. • Suspending a Conference • A conference may be suspended (e.g. no media exchanged between participants in the call) via the Park Call service to place the connection at the Conferencing Device in the queued connection state. When a conference is suspended, resources at the Conferencing Device may be reused for other purposes. • Releasing a conference • A conference is released when all resources involving the conference are stopped. This is modeled with a Conference Device connection state of null. This may happen as a result of the Clear Connection service.

5. Implicit conferencing features • Changes in the conference may also occur implicitly (i.e. without being invoked by a CSTA service). For example: • a conference may be implicitly created and enabled whenever a conference participant becomes part of a call involving a Conferencing Device. • a participant may be implicitly added to the conference when: • a participant calls a Conferencing Device and the participant is added to the conference (no participant authentication is required). • the participant answers a call that was initiated on behalf of the Conferencing Device. Once the participant answers the participant is added to the conference. • a conference may be implicitly suspended when the last participant leaves the conference and the conference is maintained for future use. • a conference may be implicitly released when the last participant leaves the conference (and there is no need to maintain the conference) or after an amount of time when no participants are involved with the conference.

6. Conference Model

7. New Location-based Features • new services to allow applications to obtain and manage location information for users and devices such as: • Setting location information – used by application when it wants to specify a location of a user and/or a device (e.g, client solicits mobile user for location information at application start up) • Polling location information – used to obtain the latest location information associated with a user and/or a device • Starting a location tracking session to be notified when location information changes via Location Information Reports • Suspending and Resuming a location tracking session • Services to get the capabilities location tracking capabilities • etc.

8. Location Tracking Session • Used for the continuous reporting of changes in user and/or device location information • Started with a Start Location Tracking Session service that passes back a session identifier that is used with all services for the session. • Specifies criteria for collecting location information, including filtering. In order to control the rate in which location information is collected, the application specifies a set of collection criteria on how the location information should be collected. For example the Start Location Tracking Session service may specify that location information should be collected every minute. • The criteria for the reporting location information. In order to reduce the frequency of CSTA Location Information Report(s), an application specifies a set of reporting criteria that specifies how to buffer collected location information before sending it to the application. For example the Start Location Tracking Session service may specify that collected location information should be sent every 5 minutes.

9. Location Tracking Session

10. Format of Location Information in CSTA- based upon IETF Standards • The CSTA LocationInfo parameter type contains a PIDF-LO element: • Presence Information Data Format - Location Object for carrying location information as defined in IETF RFC-4119 as updated by IETF RFC-5139. • Location information in a PIDF-LO element is contained in a GEOPRIV element. The GEOPRIV element consists of elements including: • location-info - consisting of one or more chunks - each chunk can be either in Geospacial format or civic address format as discussed. Note that when two chunks are provided in a location-info element that corresponds to the same place, this is referred to as a compound location. • A GEOPRIV element can be associated with a person or a device (or a generic tuple) element using the data model in RFC-4479. There can be multiple GEOPRIV elements in a single PIDF-LO. For example: • For a CSTA user with 2 devices, location information in a single PIFDF-LO may be in three GEOPRIV elements: one contained in a person element, one contained in a device element (for a cell phone), and one contained in another device element (for an office phone). • For a CSTA device such as an office phone, location information may be in a single GEOPRIV element contained in device element. The GEOPRIV location-info element contains two chunks of location information - one that specifies a location using Geospatial format and one that contains an office number as a civic address type that augments the Geospatial information. • For a CSTA group-device consisting of 3 member devices, location information may be in three GEOPRIV elements each contained in separate device elements. • The construction and interpretation of the location information in a PIDF-LO is based upon the latest draft of the IETF PIDF-LO Profile.

11. Call Control Enhancements • Option to deflect a call to multiple destinations • Application specifies (e.g. based upon rules) a set of device that all alert at the same time • Caller connected to first one that answers, other alerting devices are cleared • Parameters/features added to existing call control services: • callCharacteristics added to Deflect and Single Step Transfer so an application can change the characteristics when it moves a call. • Parameters added to existing call control events: • locationInfo on all call control events so that location information can be presented with other information about the calling party on call arrival. • calledDevice on Service Initiated event so that application knows who will be called when a prompt is answered • Enhanced deviceID formats • indicate when a number and/ or a name associated with in a deviceID in a CSTA message should be treated as private (e.g. restrict presentation)

12. Synchronization Enhancements • Services that an application can use to synchronize with a switch: • Get Monitors service to obtain the list of active monitors • Get Registrations service to obtain the list of registrations • Get Location Tracking services to obtain the list of location tracking services • Typically used after system events like switchovers when there is a possibility of lost CSTA messages.

13. Background Slides

14. List of ECMA-269 Changes in the 8th edition • 6.1.1.4.14: Conference Device Category - added conference modeling (2009/003 & 2008/067 Clause 12). • 6.8: Location Features - added location services modeling clause (2008/041 & 2008/052 Clause 13). • 7.2: Typo - changed explicit association to implicit association (2008/067 Clause 9.2) • 10.2: DeviceID Tags - added deviceID tags privateNumber and a privateName (2008/044 & 2008/ 052 Clause 15). • 12.2.14.4: ErrorCode parameter type - added error codes for Make Connection parameters (2008/ 043 & 2002008/067 Clause 12) • 12.2.18 & 12.2.19: LocationInfo & LocationInfoList parameter types: • Added parameter type (2008/041 & 2008/052 Clause 13) • added PIDF Profile Options (2008/065-Rev1 & 2008/067 Clause 14) • 13.1.4.2.1: Get Switching Function Capabilities: • added maximum number of maxDestinationDevicesForDeflect parameter for Deflect Call service (2007/022 & 2007/026 Clause 13) • added privateNumber and privateName DeviceID Tags to deviceIDFormat parameter (2008/044 & 2008/052 Clause 15) • 14.2.5: Get Registrations service & 14.2.6: RegistrationInfo service - new services (2007/026 Clause 14) • 15.1.4: Get Monitors service & 15.1.5 MonitorInfo service - new services (2007/023 & 2007/026 Clause 14) • 16.1.1: Snapshot Call service - added optional locationInfo parameter to endpoint information in positive response (2008/020 Clause 3 & 2008/067) • 16.1.3: Snapshot Call Data service- added optional locationInfo parameter to endpoint information in service request (2008/020 Clause 3 & 2008/067) • 17.1.3: Answer Call service - added new Make Connection cause to Event Sequence tables (2008/ 058 & 2008/067 Clause 12).

15. List of ECMA-269 Changes in the 8th edition (continued) • 17.1.9: Conference Call service - clarified text allow two connected or two held calls to be conferenced (2008/058 & 2008/067 Clause 12) • 17.1.11: Deflect Call service - added Deflect to Multiple Destinations feature (2007/022 & 2007/026 Clause 13) • 17.1.11: Deflect Call service - added callCharacteristics parameter (2008/063 & 2008/057 Clause 16). • 17.1.19: Make Connection service - new service (2008/058, 2008/043, & 2008/067 Clause 12) • 17.1.25: Single Step Transfer Call service - added callCharacteristics parameter (2008/063 & 2008/ 057 Clause 16). • 17.2: all call control events - added optional LocationInfoList to call control events (2008/020 Clause 3 & 2008/035) • 17.2.17: Service Initiated event: • added calledDevice parameter (2007/021 & 2007/026 Clause 12) • added Make Connection to causes (2008/058 & 2008/067 Clause 12) • 17.2.4.2: Connection Cleared event - added Multiple Alerting cause code (2007/021 & 2007/026 Clause 12) • 17.2.14.2: Originated event - added Make Connection to causes (2008/058 & 2008/067 Clause 12) • 19.1.1: Typo - Media Attachment Device changed to Media Access Device (2007/040 Clause 4) • 24.1.1 - 24.1.11: Location Services - added service descriptions for location services (2008/041 & 2008/052 Clause 13) • 24.1.7: Start Location Tracking Service • added location collection filters (2008/064 and 2008/067 Clause 14) • added PIDF Profile Options in response (2008/065-Rev1 & 2008/067 Clause 14)

16. List of ECMA-269 Changes in the 8th edition (continued) • C.4.1: Capabilities for Snapshot Call service - added optional locationInfoList (2008/020 Clause 3 & 2008/067) • C.4.3: Capabilities for SnapshotCallData service - added optional locationInfoList (2008/020 Clause 3 & 2008/067) • C.5.11: Capabilities for Deflect Call service: • added multiple destination option (2007/022 & 2007/026 Clause 13) • added callCharacteristics parameter option (2008/063 & 2008/057) • C.5.19: Capabilities for Make Connection service (2008/058, 2008/043, & 2008/067 Clause 12) • C.5.26: Capabilities for Single Step Transfer Call service - added callCharacteristics parameter option (2008/063 & 2008/057) • C.6: Capabilities for Call Control Events - added locationInfoList as optional parameter for all call control events (2008/020 Clause 3 & 2008/035) • C.6.17: Capabilities for Service Initiated event - added calledDevice parameter option (2007/021 & 2007/026 Clause 12) • 10.2: Device Identifier Tags - added deviceID tags to indicate when a deviceID number is private number and when a deviceID name is private (2008/044 & 2008/052 Clause 15)