Tech-invite3GPPspaceIETF RFCsSIP

Content for  TR 22.800  Word version:  6.0.0

Top   Top   None   None   Next
1…   4…


1  Scopep. 8

This document studies scenarios between subscribers and operators, mainly from IMS subscriptions point of view and verifies the compatibility of the possible scenarios within 3GPP Scope. Release 6 includes several work items like IMS enhancements, WLAN interworking that needs to be better understood so that clear requirement can be agreed and relevant technical specifications can be developed in time.
The document will identify the requirements arising from the following issues:
  • Identification of requirements for 3GPP operators to implement only some of 3GPP system domains? (For example an IMS system separated from the PS domain and access network. What is the relationship between the AN/CN/IMS networks in this case? Are there conflicts in privacy issues due to several subscriptions?)
  • Operator control of networks used to access / provide IMS services. For example operator may want to limit the subscriber to access the IMS via a specific 3GPP access network.
  • Non-3GPP access network implications.
  • Simultaneously access to IMS by one user with multiple devices. .
  • UE functionality split (if any implications).
  • Deployment of UICC with several USIM and ISIM applications from different parties.
  • Analyse aspects of user interaction when activating USIM and ISIM applications on the UICC (e.g. manually, automatically, PIN, NON-PIN).
Below issues need to be described in scenarios :
  • Generic issues
  • Security
  • Charging
  • Privacy
  • Roaming
  • Regulatory (e.g lawful interception) etc.
  • Quality of service
  • User experience
Further TR needs to translate the scenarios, which fit in the scope of the 3GPP system to 3GPP service requirements.
Criteria for requirements to be included:
  1. In scope with 3GPP access (UTRAN, GERAN) or access that 3GPP has specified interworking with (WLAN).
  2. In scope with 3GPP core network(s).
  3. In scope with 3GPP enabling technologies.
  4. Scope of this work is limited to identify service requirements derived from scenarios capturing various business requirements. No architectural solutions will be considered in this TR.

2  Referencesp. 9

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
TR 21.905: "Vocabulary for 3GPP specifications"
TS 22.101: "Service principles"
TS 22.228: "IP multimedia (IM) CN subsystem, stage 1"
TS 22.115: "Charging and Billing"

3  Definitions, symbols and abbreviationsp. 9

3.1  Definitionsp. 9

For the purposes of the present document, the following terms and definitions apply.
3GPP Access Operator:
an operator offering access network over 3GPP specified radio access form (e.g. GERAN/UTRAN).
3GPP Access Domain:
Domain administrated by 3GPP Access Operator.
Access independence:
the ability for the subscribers to access their IP Multimedia services over any access network capable of providing IP-connectivity, e.g. via:
  • Non 3GPP accesses with specified interworking (e.g. WLAN with 3GPP interworking)
  • Other non 3GPP accesses (e.g. xDSL, PSTN, satellite, WLAN without 3GPP interworking)
Business Agreement:
a relation between two or more parties, it may include one or more of the following elements: roaming agreement, charging agreement, authentication agreement and settlement agreement.
Unless specifically stated otherwise, the word "domain" is used to denote an administrative domain. An administrative domain is under the control of an actor (e.g. company). Some domains used in the present document may (roughly) correspond to technical domains specified by 3GPP. The technical details regarding such relationships are not covered by the document.
IMS Operator:
The operator of 3GPP compliant IP multimedia CN subsystem (IMS). IMS operator provides the users of its IMS domain with identity/identities by which the users are known.
IMS domain:
Domain administrated by IMS operator
IMS Roaming:
IMS roaming refers to the possibility for subscribers of one IMS to obtain IMS services from an IMS the users have not subscribed to, due to a business agreement between the two IMS service providers.
Non-3GPP Access Operator:
an operator offering IP-connectivity over an access form not being conformant to 3GPP specifications (e.g. WLAN, xDSL).
PS Roaming:
PS roaming refers to the possibility for subscribers of one 3GPP operator to obtain GPRS service from an other 3GPP operators that users have not subscribed to, due to a business agreement between the operators.
Further definitions are given in 3G TR 21.905.

3.2  Abbreviationsp. 10

For the purposes of the present document, the following abbreviations apply:
Personal Digital Assistant
Universal Integrated Circuit Card
x Digital Subscriber Line
Further abbreviations are given in 3G TR 21.905.

Up   Top   ToC