Disclaimer: This tr is an ad-hoc draft, and subject to modification. The Tr has yet to be presented to, or be accepted by, tsg-s1


Support of Release 99 supplementary services in PS Release 2000



старонка7/7
Дата25.04.2016
Памер274.37 Kb.
#29689
1   2   3   4   5   6   7

7.4 Support of Release 99 supplementary services in PS Release 2000


Having established the requirement for Release 99 supplementary services in Release 2000, it is required to clarify how these services are supported in.Release 2000. Release 2000 shall not specify in detail how Release 99 services are implemented in Release 2000, but solely identify the requirement for their support.

This requirement allows the Release 99 services requirements to be fulfilled using the VHE service capabilities of Release 2000.


8 Case study of realisation of some services


e.g. CFU

Editor's note: contributions invited


9 Evaluation of what does and does not need to be standardised by 3GPP


To promote this access independence for IP based services it is necessary for Release 2000 to support and follow main stream IP-based multimedia standards, such as H.323 and SIP. This also means that 3GPP shall not standardise any mobile specific extensions to these standards.

There are cases where today’s IP based standards have to be modified to suit the mobile environment of R2000. Such modifications shall then be done by enhancing those IP based standards themselves in their relevant standardisation fora. As users can be expected to require access independence to have their services available anywhere and anytime, and as mobile communications are becoming more and more important, such mobile specific modifications in main stream standards should be achievable.

To promote access independence for IP based services Release 2000 shall support and follow main stream IP-based multimedia standards, such as H.323 and SIP. No mobile specific extensions to such standards shall be standardised by 3GPP. Where today’s IP based standards have to be modified to suit the mobile environment of 3G, such modifications shall instead be done by enhancing those IP based standards themselves.

  1. Interoperability requirements


Editor's note: contribution expected from Telia

11 Release workplan


In order to clearly state the TSG-S1 Service Requirements to other TSG’s and WG’s in a timely fashion the following Work Plan is proposed.



S1

Dates

Actions

S1#7

Feb 9-11,2000

  • Work on TR22.976 so it is suitable for v1.0.0 at SA#7

  • Liase TR22.976 to S2#12.

S1#8


April 10-14, 2000

  • Prepare TR22.976 for approval at SA#8

  • Liase TR22.976 to S2#13.

  • Work on of any new Stage 1’s required so they are suitable for v1.0.0 at SA#8.

  • Produce initial CR’s to the existing 22-series

S1#9


July 17-21, 2000

  • Prepare any new Stage 1’s for approval at SA#9.

  • Complete CR’s to the 22-series.

S1#10

November 13-17, 2000

  • Revise Stage 1’s in line with feedback from other TSG’s and WG’s.

  • Begin TR on R2001.

Editor's note: need to also consider workplan for subsequent releases

Annex A PS Domain feature list evaluation for release 2000 (Normative)


Key to Table

E = Essential for release 00, launch of a commercial all-IP network is not viable with these missing or required in R00 terminal specifications to enable forward compatibility to future releases

D= Desirable for Release 2000, important features to enable a competitive and successful service launch, but could be slipped to Release 2001

R99 = Features already supported in Release 99, shall also be supported as part of Release 2000

R01+ = could wait for these features, but hooks are required in Release 2000 to enable them to be added later

No = Not needed in the PS domain

Note: Circuit switched domain services are not considered at this annex. S1 has agreed to maintain the existing Release 99 requirements in Release 2000, allowing full service continuity.

Note: All Release 99 features shifted by any reason to Release 2000 shall be included as E R’00 (to be verified feature by feature)



Feature Name

Short description

R99

E R00

D R00

R01+

No

Comments/Notes

DTAP CC

i.e. 04.08 based CC. Seamless support for existing GSM services

This set of requirements means 04.08/04.80 CC and SS in PS domain



Rel 99 CS terminal and circuit service support by circuit switched domain.

Support of R99 TS11, TS12, BS20, call offering SS, call completion SS, call restriction SS, CCBS SS, number identification SS etc.

X













How this requirement is supported (e.g. IP Transport, MSC servers, etc) in the circuit switched domain is out of S1 scope.

Rel 99 CS terminal and circuit service support by PS Domain.

Support of R99 TS11, TS12, BS20, call offering SS, call completion SS, call restriction SS, CCBS SS, number identification SS etc.
















This requirement means 04.08/04.80 CC and SS support by PS domain.




IP CC

e.g. H.323 / SIP related IP multimedia services.

IP multimedia services






















IP telephony


Single medium IP voice call (using H.323 or SIP) with end user perceived quality equal or better than 2G GSM voice call
















MMI must be identical to the standard telephony MMI (dialled digit, off hook, connection, on hook).

Including end to end QoS support.



Multimedia IP Call

Includes IP telephony, all real time calls single and multi-media, processed by IP CC
















Including end to end QoS support.

It is desirable to limit the standard to one protocol only. S2 should decide on the standard protocol. The usage of any additional protocol may be based on the network transport function (bearer service).



Emergency Voice Call

Basic emergency voice call over IP
















This must use the existing emergency numbering schemes (22.101).

Must be compliant with FCC mandates, European and other regulatory requirements.



Group calling

This requirement covers various group call services (e.g. PMR/ASCI type of services)
















Service requirements FFS

Short message service (CBS)

As specified by 23.041.

X













No additional standardisation work required for S1

Short message service (SMS PTP)

As specified by 23.040.

X













No additional standardisation work required for S1

Multimedia messages (MMS)


Support of multimedia messaging in PS domain

?













Currently supported in R99 for MS/MS. Need to consider messaging to and from other access.



Facsimile service






















Store and forward


Transfer of text or images from a MS to a store and forward unit for subsequent delivery to a fax machine. Faxes from PSTN/ISDN to mobile terminals are stored in a store-and-forward unit.
















Support of bearer service is, however, necessary to allow customised solutions to be implemented (based on T.37 and/or T.38).

End-to-end


End-to-end fax between a PSTN/ISDN fax machine and a mobile terminal.





















Services independence from transport technology


Possibility to operate in different transport environments (e.g. all IP or other different from IP)





















IP bearer services























Point-to-Point

As in 22.060

X













No additional standardisation work required for S1

Point-to-Multipoint

PTM services such as PTM-Multicast, PTM Group Call, IP Multicast, IP Distribution Services (MDS)
















Implementation of PTM services for example as defined within GPRS specifications



Asymmetric bearers


Separate parameters at the User Interface for the uplink and downlink data rate and QoS. This feature is already within R99 (e.g. TS 23.107)

X













No additional standardisation work required for S1



Support of QoS mechanisms for real time services





?













QoS is also part of R99, but the features for real time conversational services might be delayed



Multicall capability


Support of multiple active PS sessions (TS 22.060)

X













No additional standardisation work required for S1



Interworking




















Including end to end QoS support

IPv4 interworking




X













Same reqs as Rel 99 GPRS

IPv6 interworking




X













Same reqs as Rel 99 GPRS(?)

Speech to/from PSTN / ISDN / 2G CS mobile / 3G CS mobile

Full interoperability between corresponding services in PSTN/GSM environment and UMTS rel00 environment



















Multimedia to/from Internet-H.323

H.323 protocol interworking
















Incl. Intranet.

Multimedia to/from Internet –SIP

SIP protocol interworking
















Incl. Intranet.

Modem and ISDN interworking

Access to PSTN / ISDN dial up –data services
















Removed from R99 at SA1#6

Interworking with ISDN multimedia applications

Service compatibility between real time single/multimedia N-ISDN applications and single/multimedia UMTS rel 00 applications including H.324



















Interworking with other access networks (e.g. cable)






















Interworking with intranets (including VPNs)

VPN functionality (firewall bypass) shall be supported
















May possibly be supported at the application layer.




Roaming

Editor's note: Roaming section not reviewed



















CS/PS GSM/UMTS R99 to R00 PS



















(U)SIM and Multimode terminal Roaming.

Roaming should be possible for both R99 and pre R99 GSM/GPRS networks.

(Note: roaming to R00 CS is included but not within the scope)


R00 PS to GSM/GPRS



















(U)SIM and Multimode terminal roaming.

Roaming should be possible for both R99 and pre R99 GSM/GPRS networks.



ANSI-41 to R00 PS






















R00 PS to ANSI-41

























Handover

Editor's note: Handover section not reviewed



















Speech from PS Domain to CS-GSM /UMTS






















Speech from CS-GSM /UMTS to PS Domain






















Handover of parallel sessions/calls (with different QoS)






















Multimedia handover between R00 UTRAN and GERAN



















To include real-time services in addition to R99 “best effort”

Multimedia services to/from alternative access technologies (e.g. HIPERLAN/2)



















Alternative access technologies to include HIPERLAN/2



Supplementary Services (PS Domain)




















IP Multimedia / IP Telephony aware supplementary services to be considered only from end-user need view point. (Standardization, service capabilities and implementation FFS).

S2 choice of MM CC protocol may support some MM services implicitly. Some of the following services can be provided at the application level (i.e. no standardisation required).



The H.450 standards defines supplementary services for H.323, and SIP provides tools to build supplementary services.

Multimedia Call Barring

Enables mobile subscriber to have barring of certain categories of outgoing multimedia calls.
















Also includes incoming multimedia calls and barring when roaming.

Network Barring

Editor's note: Description and justification to be supplied by Horst Rauch (T-Mobil)
















FFS

Session Barring


Editor's note: Description and justification to be supplied by Horst Rauch (T-Mobil)
















FFS

Bearer Barring

Editor's note: Description and justification to be supplied by Horst Rauch (T-Mobil)
















FFS. Might be based on the QoS parameters.

Multimedia Call Forwarding

Forwarding of multimedia call (e.g. triggered by conditions of Unconditional, Busy, No Reply, Not Reachable etc). Triggers/activation will be different and more detailed in a MM environment for the different media components.
















Conditions require to be evaluated.

Multimedia Call Transfer

Enables served mobile subscriber who has a multimedia call, to connect the other parties in the multimedia call and release the served mobile subscriber’s own connection.



















Multimedia Call Deflection Service

Enables the served mobile subscriber to respond to an incoming multimedia call offered by the network by requesting redirection of this multimedia call to another address or location.



















Multimedia Call Holding

Allows served mobile subscriber to interrupt communication on an existing active multimedia call and then subsequently re-establish communication



















Multimedia Call Waiting

Permits mobile subscriber to be notified of an incoming multimedia call while the mobile subscriber is engaged in other multimedia call(s). Subscriber can either accept, reject, ignore, or deflect the incoming multimedia call.



















Advice of Charge

Supply user sufficient information to allow real time estimate of the call charge.



















Caller Identification and restriction

Similar to CLIP, CLIR, CNAP and CNAR.
Editor's note: add to abbreviations
















Could include additional IP related information such as IP address.

Need to support European, FCC and other regulatory requirements.



Connected Line Identification and restriction

Similar to COLP and COLR

Editor's note: add to abbreviations


















Could include additional IP related information such as IP address.

Need to support European, FCC and other regulatory requirements.



Multimedia conferencing

Similar to Multiparty but is applicable to multimedia calls.


















Multimedia call-back when free / CCBS


Editor's note: definition required in the MM case


















Closed user group (CUG) / community of interest


Editor's note: definition required in the MM case


















Precedence and Pre-emption service


Editor's note: definition required in the MM case






















Network Services






















Operator Determined Barring (ODB)

Allows service providers to regulate subscriber access to services by the barring of certain categories of outgoing or incoming multimedia calls and packet services. ODB could terminate ongoing multimedia calls and could bar future multimedia calls and packet services.

?
















CAMEL Support for Multimedia Services

Provides mechanisms to support multimedia services consistently & independently of the serving network.
















CAMEL enhancements, but additionally needs to support multimedia calls. Implementation is FFS.

Editor's note: DeWayne Sennet (AWS) to WIN support proposal



(U)SIM Toolkit

Feature provides a set of facilities which allow the (U)SIM to interact with external entities (e.g. the network, the Mobile Equipment, or the user) to enable value-added multimedia applications to exist in the (U)SIM.



















OSA for new elements

Provision of an API for controlled, secure and accountable access to multimedia service capability features by applications, based on the user profile
















E.g. H.323/SIP CSCF.

LCS for GPRS/PS domain

Support of LCS on the PS domain required to meet regulatory and commercial requirements (e.g., 3GPP 22.071)
















Exact work required is for FFS.

Need to support European, FCC and other regulatory requirements.



SoLSA

SoLSA shall facilitate user-dependent radio resource selection based on LSA (e.g. when user is located at his office, radio coverage provided with indoor radio solutions should be preferred).



















Lawful Surveillance / Intercept



















Need to support European, FCC and other regulatory requirements.

Number Portability

Ability for subscriber to change service providers while retaining the original directory number. Includes mobile to mobile, mobile to landline, & landline to mobile number portability scenarios.
















Need to support European, FCC and other regulatory requirements.

Mobile Station Application Execution Environment (MExE)

Provides standardized execution environment in an MS, and an ability to negotiate its supported capabilities with a MExE service provider, allowing applications to be developed independently of any MS platform.



















Personalization of Mobile Equipment (ME)

Storage of information in the ME which limits the SIMs which will operate with the ME.

X













No standardisation work required for R99

Advanced Addressing

Support of symbolic and advanced addressing
















Addressing depends on applications, e.g. e-mail addresses are used for e-mail, E.164 is used for telephony, ICQ uses IP addresses. This does not require standardisation by 3GPP.

System Selection

Ability for the mobile equipment to choose a preferred service provider, based upon geographic location, frequency band preferences, available operators, etc. Also the ability to force a mobile station to "disallow" service from a "forbidden" service provider, and to force a mobile station to use "home" services. Service provider lists must be downloadable over-the-air. The possibility for operators with multimode networks, e.g. with GSM and UMTS radio access networks, to control which RAN a user accesses.
















Similar to ANSI-136 Intelligent Roaming.

Over-the-Air Service Provisioning

Ability to download parameters to either the SIM or ME for provisioning of services. This includes both subscription parameters as well as operator-specific parameters.
















Similar to ANSI-136 OTASP and OTAPA.




Charging






















Implementation of on-line charging mechanisms for the support of Pre-paid services

Definition of charging mechanisms for the support of IP multimedia pre-paid services



















Event/transaction based charging mechanisms (e.g. content based)

Definition of charging mechanisms for the provisioning of IP based Value Added Services



















Charging aspects – need to charge for each PDP context (PS sessions) independently














































.

History


Document history

0.0.0

17/11/1999

Skeleton

0.1.0

14/1/2000

Editor's draft input to Rome, Italy R2000 ad-hoc 17-19/1/2000

0.2.0

18/1/2000

Produced during the Rome, Italy R2000 ad-hoc 17-19/1/2000

0.3.0

19/1/2000

Produced during the Rome, Italy R2000 ad-hoc 17-19/1/2000

0.4.0

19/1/2000

Produced during the Rome, Italy R2000 ad-hoc 17-19/1/2000

0.5.0

20/1/2000

Produced during the Rome, Italy R2000 ad-hoc 17-19/1/2000

Editor: Mark Cataldo, Motorola

E-mail: mcatald1@email.mot.com Telephone: +44 1793 566297








Поделитесь с Вашими друзьями:
1   2   3   4   5   6   7




База данных защищена авторским правом ©shkola.of.by 2022
звярнуцца да адміністрацыі

    Галоўная старонка