1. QoS JEM Input from TSG-S All-IP ad-hoc AllIP-20010116-21

2. General direction The All-IP ad-hoc group believes that, whenever it is possible and makes sense (from a technical and time to market perspective), all changes to existing standards that are made to accommodate QoS shall be made in line with the 3GPP2 All-IP architecture.

3. Different levels of QoS support Basic/Static: Subscribers are assigned a priority (subscriber class). Packets are classified into priority classes and are prioritized over the air interface. Can be combined with e.g DiffServ in the network. No dynamical negotiation. Would from an All-IP perspective be needed in both domains Advanced/Dynamic: QoS is dynamically negotiated. Support for multiple concurrent logical channels with different characteristics. End-to-end negotiation (e.g RSVP). Negotiation for capacity, rather than static priorities. Would from an All-IP perspective fall into the IP multimedia domain

4. Basic/Static QoS Support Used to give certain types of traffic higher relative priority compared to other. Users may be given different relative priorities, using differentiated subscription types. Main purpose of this is to give better performance (e.g. response times) to different services and different subscribers Open issues: Is DiffServ etc. really necessary on the network side to achieve this ? Are any new service enabled by this that are not possible with best -effort ?

5. Advanced/Dynamic QoS support The main purpose of this is to enable new types of services (e.g. VoIP, real-time gaming etc.) and to provide a certain degree of guarantee/reliability to these From an All-IP perspective, this is one of the cornerstones of the IP Multimedia domain. Any support for this should be developed within the All-IP effort and with the All-IP NAM as a reference

6. What are the necessary changes to provide advanced/dynamic QoS support ? Is there adequate support in IS-2000 for the radio bearers needed for All-IP Multimedia Services ? Do the Service Options and multiplexing options provide all we need ? What are the necessary changes to registration procedures to support the All-IP architecture ? New messages or parameter indicating mobile station type ? What are the necessary changes to the call set up procedures to support the All-IP architecture ? Do we need a new IS-2000 call model to support multiple and concurrent Service Options ?

7. Recommendations from All-IP Basic/Static QoS functions shall be supported in both All-IP domains as well as in legacy systems. Therefore, migration towards All-IP must be taken into consideration. Advanced/Dynamic QoS functions are a part of the All-IP multimedia domain functions. Therefore, these functions shall be developed based on the All-IP NAM.