3GPP IMS and UMTS Specifications -- 22 Series:
Service Aspects - Stage 1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 22.071 |
SA1 |
|
Location Services (LCS) -
Service Description - Stage 1 |
This TS provides core requirements to an extent sufficient to derive a complete definition of location
services at the service level. However, the present document also provides additional requirements which
may suggest in a non-normative manner certain ways the system may be implemented to support location services.
LCS can be offered without subscription to basic telecommunication services.
LCS is available to the following categories of LCS clients:
|
| - |
Value Added Services LCS Clients --
use LCS to support various value added services;
these clients can include UE subscribers as well as non-subscribers to other services.
| |
| - |
PLMN Operator LCS Clients --
use LCS to enhance or support certain O&M related tasks,
supplementary services, IN related services and bearer services and teleservices.
| |
| - |
Emergency Services LCS Clients --
use LCS to enhance support for emergency calls from subscribers.
| |
| - |
Lawful Intercept LCS Clients --
use LCS to support various legally required or sanctioned services.
|
LCS is applicable to any target UE whether or not the UE supports LCS, but with restrictions on choice
of positioning method or notification of a location request to the UE user when LCS or individual
positioning methods, respectively, are not supported by the UE.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 22.078 |
SA1 |
|
CAMEL - Service description - Stage 1 |
|
This TS specifies the stage 1 description for the CAMEL feature (Customised Applications
for Mobile network Enhanced Logic) which provides the mechanisms to support services consistently
independently of the serving network. The CAMEL features shall facilitate service control of
operator specific services external from the serving PLMN. The CAMEL feature is a network
feature and not a supplementary service. It is a tool to help the network operator to provide
the subscribers with the operator specific services even when roaming outside the HPLMN.
|
|
|
| |
| Up |
Rapporteur: Michel Grech |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 22.101 |
SA1 |
|
Service Principles |
This TS describes the Service Principles for PLMNs specified by 3GPP.
Principles and requirements for interworking with WLAN are covered in
3GPP TS 22.234.
3GPP specifications provide integrated personal communications services.
The system will support different applications ranging from narrow-band to wide-band communications
capability with integrated personal and terminal mobility to meet the user and service requirements
of the 21st century.
3GPP specifications allow the realisation of a new generation of mobile communications technology for a world in which personal communications services should allow person-to-person calling, independent of location, the terminal used, the means of transmission (wired or wireless) and the choice of technology. Personal communication services should be based on a combination of fixed and wireless/mobile services to form a seamless end-to-end service for the user.
3GPP specifications should be in compliance with the following objectives:
|
| a) |
to provide a single integrated system in which the user can access services in an easy to use and uniform way in all environments;
| |
| b) |
to allow differentiation between service offerings of various serving networks and home environments;
| |
| c) |
to provide a wide range of telecommunications services including those provided by fixed networks and requiring user bit rates of up to 100 Mbits/s as well as services special to mobile communications. These services should be supported in residential, public and office environments and in areas of diverse population densities. These services are provided with a quality comparable with that provided by fixed networks such as ISDN and fixed broadband Internet access;
| |
| d) |
to provide services via hand held, portable, vehicular mounted, movable and fixed terminals (including those which normally operate connected to fixed networks), in all environments (in different service environments - residential, private domestic and different radio environments) provided that the terminal has the necessary capabilities;
| |
| e) |
to provide support of roaming users by enabling users to access services provided by their home environment in the same way even when roaming;
| |
| f) |
to provide audio, data, video and particularly multimedia services;
| |
| g) |
to provide for the flexible introduction of telecommunication services;
| |
| h) |
to provide within the residential environment the capability to enable a pedestrian user to access all services normally provided by fixed networks;
| |
| i) |
to provide within the office environment the capability to enable a pedestrian user to access all services normally provided by PBXs and LANs;
| |
| j) |
to provide a substitute for fixed networks in areas of diverse population densities, under conditions approved by the appropriate national or regional regulatory authority;
| |
| k) |
to provide support for interfaces which allow the use of terminals normally connected to fixed networks.
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 22.105 |
SA1 |
|
Services and Service Capabilities |
Existing systems have largely standardised the complete sets of bearer services, teleservices and supplementary services which they provide. 3GPP specifications specify service capabilities rather than services, allowing service differentiation and system continuity.
This TS describes how and what kind of services the user has access to.
|
|
|
| |
| Up |
Rapporteur: Michele Zarri |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 22.115 |
SA1 |
|
Service Aspects -
Charging and Billing |
|
This TS describes the Service Aspects of charging and billing of the 3GPP System.
It is not intended to duplicate existing standards or standards being developed by other groups
on these topics, and will reference these where appropriate. The present document will elaborate
on the charging requirements described in the Charging Principles in
3GPP TS 22.101
Service Principles. It will allow the generation of accurate charging information to be used
in the commercial and contractual relationships between the parties concerned.
|
|
|
| |
| Up |
Rapporteur: Enrico Scarrone |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 22.127 |
SA1 |
|
Service Requirement for the Open Service Access (OSA) - Stage 1 |
|
This TS specifies the stage 1 requirements for realisation of an Open Service Access (OSA).
OSA enables applications to make use of network functionality through an open standardised interface
(the OSA API). OSA provides the glue between applications and network functionality.
In this way applications implementing the services become independent from the underlying network technology.
Applications which make use of network functionality offered through the OSA interface
are not standardised by 3GPP.
|
|
|
| |
| Up |
Rapporteur: Joerg Swetina |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 22.140 |
SA1 |
|
Multimedia Messaging Service (MMS) - Stage 1 |
This TS defines the stage one description of the non real-time Multimedia Messaging Service, MMS. Stage one is the set of requirements which shall be supported for the provision of non real-time multimedia messaging service, seen primarily from the subscriber's and service providers' points of view.
This TS defines the requirements for MMS to be understood as a framework to enable non real-time transmissions for different types of media including such functionality as:
|
| - |
multiple media elements per single message
| |
| - |
individual handling of message elements
| |
| - |
different delivery methods for each message element
| |
| - |
negotiate different terminal and network MM capabilities
| |
| - |
notification and acknowledgement of MM related events (e.g. delivery, deletion, ...)
| |
| - |
handling of undeliverable MM
| |
| - |
personalised MMS configuration
| |
| - |
flexible charging
|
The above list is not exhaustive.
Thus the MMS enables a unified application which integrates the composition, storage, access, and delivery of different kinds of media, e.g. text, voice, image or video in combination with additional mobile requirements.
|
|
|
| |
| Up |
Rapporteur: Juergen Meyer |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 22.141 |
SA1 |
|
Presence Service - Stage 1 |
|
This TS defines the requirements for the support of the presence service.
The presence service results in presence information of a user and information on a user's devices,
services and services components being managed by the wireless network.
Together, user, these devices, services and services components are termed presentity (presence entity).
This TS makes extensive use of internet terminology to ensure alignment with the presence service
description and behaviour in internet recommendations.
The presence service provides access to presence information to be made available to other users or services.
Exploitation of this service will enable the creation of wireless-enhanced rich multimedia services along
the lines of those currently present in the internet world.
Presence is an attribute related to, but quite different from mobility information,
and is a service that can be exploited to create additional services.
|
|
|
| |
| Up |
Rapporteur: Randolph Wohlert |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 22.146 |
SA1 |
|
Multimedia Broadcast/Multicast Service - Stage 1 |
This TS
defines the stage one description of the Broadcast and Multicast Services for the 3GPP System (UTRAN and GERAN). Stage one is the set of requirements which shall be supported for the provision of Broadcast and Multicast services, seen primarily from the subscriber's and service providers' points of view.
This TS includes information applicable to network operators, content providers, and terminal and network manufacturers.
This TS contains the core requirements for Multicast and Broadcast Services, which are sufficient to provide a complete service.
|
|
|
| |
| Up |
Rapporteur: Andre Jarvis |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 22.173 |
SA1 |
|
IMS Multimedia Telephony service and Supplementary Services |
The IMS Multimedia Telephony Service should allow multimedia conversational communications between two or more users. It provides real time bidirectional conversational transfer of speech, video or optionally other types of data.
The IMS Multimedia Telephony communication is point to point between terminals communicating , or a terminal and a network entity. This communication is usually symmetrical, but in special cases the media components present in each direction may be different, or they may be the same but with different bit rates and Quality of Service.
An IMS Multimedia Telephony communication can start with only one type of media and additional types of media may or may not be added by the users as the communication progress. Therefore a particular IMS Multimedia Telephony communication may consist of only one type of media, e.g. speech.
IMS Multimedia Telephony service is different from other IMS based services, such as Push to Talk over Cellular (PoC).
Its characteristics includes the following:
|
| - |
IMS Multimedia Telephony is a service where speech, and speech combined with other media components, is the typical usage but the service is not limited to always include speech, it also caters for other media or combinations of media (e.g. text and video).
| |
| - |
The IMS multimedia telephony service includes supplementary services. The behaviour of these services is almost identical to supplementary services for CS voice (TS 11) and PSTN/ISDN.
Note: most supplementary services are active in the set-up phase. Mid session supplementary services such as session transfer and session hold exist.
| |
| - |
The anticipated usage model is that of traditional telephony: one user connecting to any other user, regardless of operator and access technology.
| |
| - |
When a supplementary service is invoked it applies to all media components of an IMS Multimedia Telephony communication. A supplementary service can be activated by the user for one or more types of media components. If one or more of these media components are present in the IMS Multimedia Telephony communication then the supplementary service is invoked.
|
This TS defines the IMS Multimedia Telephony service and the minimum set of capabilities required to secure multi-vendor and multi-operator inter-operability for Multimedia Telephony and related Supplementary Services.
|
|
|
| |
| Up |
Rapporteur: Joerg Swetina |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 22.228 |
SA1 |
|
Service Requirements for the IP
Multimedia Core Network (IM CN) Subsystem - Stage 1 |
This TS defines the service requirements from users' and operators' perspective for the support of IP multimedia applications through the IMS.
IP multimedia applications are supported by IP multimedia sessions in the IM CN Subsystem. IP multimedia sessions use IP connectivity bearers (e.g. GPRS as a bearer). Examples of IP multimedia applications include speech communication, real time multimedia applications, shared online whiteboards etc.
This TS, in general, does not standardise usage of IP multimedia applications, but instead identifies the requirements to enable their support.
In order to align IP multimedia applications wherever possible with non-3GPP IP applications, the general approach is to adopt non-3GPP IP based solutions.
The existing legacy tele- and supplementary services shall not be re-standardised as IP multimedia applications, and multimedia equivalent applications may be created with toolkits.
|
|
|
| |
| Up |
Rapporteur: Mark Cataldo |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: Michael Boote |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 22.246 |
SA1 |
|
Multimedia Broadcast/Multicast Service user services - Stage 1 |
3GPP TS 22.146
specifies the multimedia broadcast and multicast service (MBMS) application independent transport service and includes some guidance on application services and bit rates. The present specification defines MBMS User Services that use the capabilities of MBMS. Service related information is defined in this specification to specify requirements in terms of data rates, quality of service requirements, typical volumes of data etc.
MBMS User Services may be delivered to a user at different bit rates and quality of service depending on radio networks and conditions. This technical specification describes service scenarios for MBMS User Services.
In addition scenarios related to security and charging are described providing information for detailed MBMS User Services security and charging mechanisms to be specified. The service scenarios described in this specification are not exhaustive, it is possible that MBMS may be used for services that are not included in this specification. The present specification describes the minimal requirements for interoperability for MBMS based services. This specification establishes a basis which can also be used for future services.
This TS
describes MBMS User Services that use the capabilities of MBMS. Application scenarios including charging, QoS aspects and related service requirements derived from them are described. These scenarios and service requirements can be used as guidance for the design of codecs and bearers.
|
|
|
| |
| Up |
Rapporteur: Igor Curcio |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 22.250 |
SA1 |
|
IP Multimedia Subsystem (IMS) Group Management
- Stage 1 |
|
This TS defines the requirements for the support of IP Multimedia Subsystem (IMS) group
management capability. IMS group management capability provides a possibility to manage network based groups.
IMS group management allows defining different roles and rights to the members of a group, defining group level
information and properties, etc.
|
|
|
| |
| Up |
Rapporteur: Juho Laatu |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 22.259 |
SA1 |
|
Service Requirements for
Personal Network Management (PNM) - Stage 1 |
Traditionally a single integrated device with integrated radio access means formed the User Equipment (UE) for access to mobile communication services. Now, however, many subscribers possess more than one device for running mobile communication services, which may be connected to form a Personal Network (PN). The devices differ in their capabilities and these capabilities qualify the devices more or less for specific end-to-end applications or particular media like audio, video and pictures. A part of the devices offers own network access means for accessing the PLMN via UTRA, W-LAN, or other access technologies. The other devices are Terminal Equipments without radio access capabilities.
Personal Network Management (PNM) allows the users to manage their devices and PN's. This TS specifies requirements for allowing the users to manage their devices. The considered management functions of Personal Network Management comprise the setup and configuration of Personal Networks, the personalization for the termination of services within the Personal Network as well as the enabling of secure connections between the Personal Network Elements. This includes the management of Personal Area Networks with their local device connections and their available radio access means.
Two different scenarios are distinguished for Personal Network Management:
|
| 1 |
Personal UE Networks: This addresses the management of multiple UEs belonging to a single user. It contains the UE Redirecting Service that provides a service to redirect terminating services to selected UEs and Private Network services that provide a service to maintain privacy and enable restricted access to a PN.
| |
| 2 |
PNE Networks: This extends the scope of considered managed objects from UEs to physically separated UE components and to attached MEs. It does not only extend the UE Redirecting Service and Private Network services by PAN-specific aspects but addresses the PAN Management with interactions of TEs and MEs required for applicable AIPN features.
|
These two scenarios are handled separately within the TS as the requirements of Personal UE Networks and PNE Networks are focussed on different types of services. Personal UE Networks aim at an easy-to-use UE management whereas PNE Networks enable complex scenarios of local networks with alternative network access means and AIPN-based requirements.
This TS describes the service requirements for the Personal Network Management (PNM). Aspects of data synchronisation and management of user data are out of scope.
|
|
|
| |
| Up |
Rapporteur: Armin Toepfer |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 22.278 |
SA1 |
|
Service Requirements for the Evolved Packet System (EPS) |
To ensure competitiveness in a longer time frame an evolution of the overall 3GPP system needs to be considered.
This document compiles requirements to ensure that an Evolved Packet System can cope with the rapid growth in IP data traffic and demanding requirements for new multimedia type of applications in terms of performance and quality, delivered to the user, whilst at the same time enabling cost effective deployment and operation.
The Evolved Packet System is characterised by:
|
| - |
Reduced latency
| |
| - |
Higher user data rates equating to broadband performance
| |
| - |
Improved system capacity and coverage
| |
| - |
Lower operational costs
|
This TS describes the service requirements for the Evolved Packet System.
|
|
|
| |
| Up |
Rapporteur: Michael Kurz |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 22.279 |
SA1 |
|
Combined CS and IMS Sessions - Stage 1 |
This TS specifies service requirements for Combining CS (Circuit Switched) and IMS services using a CS speech or CS
multimedia call in association with an IMS session. The IMS session may consist of one or more IMS services.
Requirements for the following capabilities are included:
|
| - |
Radio capability exchange
| |
| - |
Terminal capability exchange
| |
| - |
E.164 number exchange
| |
| - |
Adding IMS session to an ongoing CS call
| |
| - |
Adding a CS call to an ongoing IMS session
| |
| - |
Supplementary services as they relate to CSICS (Circuit Switched IMS Combinational Service).
|
It is intended that the capabilities defined herein for CSICS shall support interoperability between different operator networks, and roaming.
|
|
|
| |
| Up |
Rapporteur: John Watson |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: Juho Laatu |
|
|
|
|
|
|
|
|
|
|
