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




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

6.6 Conferencing


A solution for basic 3-way voice conferencing supported in the network is likely to be required, since this is the most likely service to be used with the greatest gains. Although, H.323 terminals (PCs) currently offer multimedia conferencing on the terminal, it requires one terminal to "anchor" the session and provide the mixing of sessions. A more sophisticated multimedia conferencing solution may be required, but this will be dependent on the codecs used etc. It may be more appropriate to provide this as a native IP service internal or external to the network.

Multicast and broadcast support may also be offered, using IP multicast. The benefits of this approach are most likely to occur where many users are receiving the same feed on the same cell, and the commercial benefits for this are yet to be fully understood. Any IP service should allow multicast connections to be made outside of the cellular part of the core network.


6.7 Number Portability


This category of services is one of many aspects of addressing and routing which must interwork with the existing fixed and mobile 2G network schemes already deployed. Essentially number portability can be implemented within the HLR, as part of the initial inbound call-processing query. More sophisticated schemes, which resolve one or more identities to actual routing codes may overlay these 2G schemes. Parallels may be seen in the e-mail world, where e-mail addresses appear to be portable between computers with different IP addresses, and where multiple e-mail addresses per user and per device are supported.

6.8 Service Provisioning


The range of new services created in 3G will require provisioning and configuration by users and service providers. Since the range of services and the services themselves are not standardised in 3G, the specific feature codes to provision, enable and configure them cannot be standardised either. Instead, it is expected that service capabilities, personalised Internet web pages or direct access to customer helpdesk by voice telephone will be used to allow (self)provisioning, configuration and enabling of VHE services.

6.9 Summary of required service primitives


In order to build a set of supplementary services (suitable for service provider differentiation) in the VHE, a basic set of service primitives is required which are available for access from the terminal, together with call handling for those cases where the terminal is offline or unreachable. These are:

  1. Authentication (as per GSM/GPRS via SIM Card)

  2. Basic Call (including implicit Mobile Number Portability, Lawful Intercept and Tandem Free Operation). Shall allow interworking as voice only call with legacy networks.

Editor's Note: need to restructure document to identify all the required services in one common subclause…

  1. Internet Access (i.e., standard GPRS service)

  2. Call Diversion Immediate Call Diversion on unreachable (i.e. when terminal does not respond to paging)

  3. Call manipulation primitives from the terminal:

  1. set-up outbound basic call

  2. notify/accept/answer incoming call

  3. hold

  4. transfer

  5. divert

  1. Call triggers (CAMEL) to monitor and manipulate multimedia calls from the home network:

  • incoming call arrival (similar to CAMEL in circuit switched domain)

The PS domain shall use the following minimum service capabilities to build and support all other services:-

  • HLR/CAMEL support in the serving network

  • SIM Toolkit (minimum terminal requirement, Class FFS)

  • MExE Classmark 1 (minimum terminal requirement)



7 Service continuity and new services

7.1 Service continuation


Service continuation from an end user perspective is understood to be an important driver for established users of 2nd generation mobile communications systems to stay with their existing operator while moving into the 3rd generation. It is therefore important to enable operators to offer such service continuation into Release 2000. Existing Release 99 services must as a principle be supported also in Release 2000, and that any exception explicitly identified.

Note: To enable service continuation, the existing Release 99 supplementary services (refer to [7]) shall be supported also in Release 2000 for circuit services.


7.2 No new standardised supplementary services


Operators and service providers are expected to offer new (supplementary) services to their users. If those new services would be standardised then they would have to be implemented also in all visited networks, as the existing way of implementing these services have been by downloading profiles and/or CAMEL triggers to the visited network. This creates dependencies to the visited networks which makes it more difficult to deploy new services, especially operator specific ones. We have seen in GSM that this can take time which would lead to inflexibility and delays in service offerings.

To avoid such limitations the Release 99 principle of not adding more 3GPP standardised supplementary services shall be kept. Operator specific services shall instead be implemented using VHE service capabilities, as stated for Release 99.

New supplementary services shall, as a principle, not be standardised, but instead be implemented using VHE.

7.3 Service compatibility with mainstream IP based services


It is important that Release 2000 supports evolving main stream IP based multimedia services and applications. The requirement for access independence implies that such multimedia services, e.g. an IP web based Call Forwarding service where a user could access a web page to manipulate her Call Forwarding settings based on any number of input parameters, also have to be compatible with the same IP web based service supported via other accesses such as, e.g., fixed lines. The end user shall thus experience the same service behaviour irrespective if the access is made via 3G networks or a fixed line.

Many similar (supplementary) services applicable for the evolving IP based multimedia services are as a principle different from the existing GSM standardised supplementary services, see the example of the web based Call Forwarding service above.

If a choice has to be made for the Release 2000 IP based multimedia services, between being compatible either with main stream IP based services or with existing GSM standardised supplementary services, the service compatibility with main stream IP based services must be a first priority.

Editor's note: should it be an operator or customer choice to choose "classic" service compatibility? The above paragraph may require to be revisited


1   2   3   4   5   6   7


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

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