43GPP2 Work Items Descriptions V1.4
Phone: +1 408 330 9113
Fax: +1 408 330 9140
13Work Item Descriptions for Version 23 of the Workplan.
18Review and Approve
24The contributor grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable
25material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in
26Organizational Partner's name any Organizational Partner's standards publication even though it may include portions of the contribution;
27and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contributions or the resulting
28Organizational Partner's standards publication. The contributor must also be willing to grant licenses under such contributor copyrights to
29third parties on reasonable, non-discriminatory terms and conditions, as appropriate.
32Permission is granted to 3GPP2 participants to copy any portion of this contribution for the legitimate purpose of the 3GPP2.
33Copying this contribution for monetary gain or other non-3GPP2 purpose is prohibited.
Date: January 31, 2001
1Work Item Descriptions
3GPP2 and its Organizational Partners claim copyright in this document and individual
Organizational Partners may copyright and issue documents or standards publications in
individual Organizational Partner's name based on this document. Requests for reproduction
of this document should be directed to the 3GPP2 Secretariat at firstname.lastname@example.org.
Requests to reproduce individual Organizational Partner's documents should be directed to
that Organizational Partner. See www.3gpp2.org for more information.
11. Network Capabilities
2 1.1- 1.3 Intentionally Left Blank
3 Completed work item. See System Capabilities Guide.
5 1.4 Authentication - Incorporation of 3GPP AKA
6 This work item is to incorporate the 3GPP AKA algorithms into the system taking into
7 account any specific requirements of an ANSI-41 evolved network. This will provide
9 1.4.1 Enhancements:
10 The 3G system will provide users with a common authentication and key
11 management algorithm for use in all 3G TIA/EIA-41 mapped networks. Enhanced
12 Subscriber Authentication (ESA) will provide the capability for mutual
13 authentication between UIM and network. Key management will ensure that keys
14 for authentication and ciphering are sufficiently independent that compromise of
15 one key does not compromise the other.
17 1.4.2 Exportability:
18 The 3G authentication and key management algorithm will meet the requirements
19 of U.S. export laws and regulations.
21 1.4.3 Internationalization:
22 This is the ability to permit the use of specific algorithms as may be required on a
23 national or regional basis. It would also provide for the co-existence of multiple
24 algorithms in a mobile station and/or infrastructure to facilitate backward
25 compatibility and roaming capabilities. This capability implies that a mobile station
26 and infrastructure will negotiate the specific algorithms to be used.
27 1.5 Ciphering (circuit switched)
28 1.5.1 Enhancements:
29 Enhanced Subscriber Privacy (ESP) by means of encryption across the air interface
30 protects subscriber traffic (bearer data and signaling) from unauthorized disclosure.
32 1.5.2 Exportability:
33 At least one 3G ciphering algorithms will be developed which shall be capable of
34 being used globally. This implies that the algorithm meets U.S. export laws and
35 regulations. This does not preclude the development of algorithms to be used on a
36 national or regional basis.
38 1.5.3 Internationalization:
39 Due to restrictions on the use and export or encryption algorithms, it is required that
40 a mechanism be developed to permit the use of specific algorithms as may be
41 required on a national or regional basis. This provides for the co-existence of
42 multiple algorithms in a mobile station and/or infrastructure to facilitate backward
1 compatibility and roaming capabilities. This capability implies that a mobile station
2 and infrastructure will negotiate the specific algorithms to be used.
3 1.6 Intentionally Left Blank
4 Completed work item. See System Capabilities Guide.
6 1.7 3G Mobile Equipment Identifier
7 Expanding the ESN field beyond 32 bits.
8 When the length of the ESN is extended, the unique country information should be
9 included in the ESN field. The ESN numbering space should be appropriately divided
10 into a number of subspaces and each subspace is administered by each country. This
11 capability differs from the Expanded ESN effort previously addressed within the TR-45
12 ESN Ad Hoc.
13 1.8 TMSI Support
14 This capability provides for Temporary Mobile Station Identity (TMSI) support in order
15 to mask or hide a mobile station’s subscriber identity from unwanted eavesdropping. The
16 use of TMSI also permits a shortened mobile station address to reduce the size of the
17 messages sent over the air.
18 1.9 Data Field Encoding for Multiple Character Set
20 This capability provides the ability to deliver and receive messages from the mobile
21 station in a variety of character sets. Support includes both Short Message Service and
22 other messaging (e.g., Calling Name Presentation) where the information may be
23 presented on the mobile station’s display. The ability to support different character sets
24 includes the ability to assign character sets on a message by message basis as well as the
25 ability to mix character sets within a message. The choice of character set a message is to
26 be encoded in may be driven either by the source information or by the Preferred
27 Language Indicator as the application demands.
28 1.10 Out- of-band Feature Activation/Deactivation
30 Feature activation and de-activation messages provide an out of band mobile station to
31 network signaling procedure for the activation/de-activation, registration and de-
32 registration, and invocation and de-invocation of features. They also provide network
33 level confirmation of a change in a feature back to the mobile station and provide for the
34 capability of a mobile station to query the network as to the status of a feature.
35 1.11 Location - Position Technology Enhanced
36 This capability adds common channel support for position assist parameters passed from
37 the network to the mobile station. This reduces the capacity impact of delivering
38 common parameters to multiple mobile stations.
1 1.12 Intentionally Left Blank
2 Completed work item. See System Capabilities Guide.
4 1.13 Automatic Roaming Agreements
5 In the environment where the automatic roaming agreement is supported even if the
6 operator A doesn't have a roaming agreement with the operator B, a user subscribing the
7 operator A can enjoy the operator B's cellular service. This feature may be realized by
8 information transaction other than TIA/EIA-41.
9 Upon registration, the home HLR will be queried and parameter loaded in the visited
10 switch, however it is a business issue to enable the feature where there are no roaming
12 No additional requirements have been identified.
13 1.14 Intentionally Left Blank
14 Completed work item. See System Capabilities Guide.
16 1.15 Backwards Compatibility
17 This standing requirement requires each new version of the specifications to be backward
18 compatible with previous versions, providing for the capability of new mobile stations to
19 work on older systems and for older mobiles to operate on new systems with as
20 consistent set of features as is possible.
21 1.16 Location - Support Services
22 1.16.1 Calling Party Cell/Sector:
23 The ability to transport calling party cell/sector information through the network.
24 1.16.2 Called Party Cell/Sector:
25 The ability to transport called party cell/sector information through the network.
26 1.16.3 Calling Party Latitude/Longitude:
27 The ability to transport calling party cell/sector information through the network.
28 1.16.4 Called Party Latitude/Longitude:
29 The ability to transport called party cell/sector information through the network.
30 1.16.5 Mid Call Location Update
31 The ability to obtain location information for either party while a call is in progress.
32 1.17 Location - Tiered Services
33 Tiered Services provides the ability to identify to the network that a mobile station is
34 within a User Zone (geographical area) and to identify to the mobile station user the
35 name of the User Zone where the mobile station is active via the mobile station display.
36 This allows the Location Based Services capability to provide services such as
37 differential billing, wireless PBX emulation, and residential base station emulation to
38 individuals or groups of subscribers.
1 1.18 Automatic Code Gapping
2 This features allows elements in an ANSI-41 to shed excessive load by instructing the
3 source of incoming requests to suspend messaging for a period of time.
5 1.19 All IP Network
6 This project is the development of a network that uses IP based packet data as its primary
7 mechanism for transport and switching. The actual scope of the activity is being defined
8 in a Steering Committee Ad Hoc.
102. UIM Capabilities and Services
11 2.1 User Identification Module (UIM) Support –
12 Integrated and Removable
13 The User Identity Module (UIM) contains information specific to an individual
14 subscriber as well as elements required for authentication such as secret keys and
15 algorithms. The UIM functionality can be implemented directly in the MS or via a
16 separate, removable, hardware token. The UIM capability provides for terminal
17 portability within a single subscription based on a single air interface. Combined with
18 the Personal Mobility capability, a UIM should provide portability of services across
19 different MSs and/or different networks (i.e., dual mode international roaming).
20 2.2 Intentionally Left Blank
21 Completed work item. See System Capabilities Guide.
23 2.3 Personal Mobility
24 This capability allows a subscriber to roam between different 3G family members (e.g.,
25 from cdma2000 to UWC-136, TIA/EIA-41 to GSM MAP) based on either the integrated
26 or removable UIM capability. It provides for the provisioning of all parameters to access
27 the air and network interfaces when moving between families.
283 Data - Circuit Switched Capabilities
29 3.1 V.90 Interworking
30 This capability supports a user’s ability to attach a data terminal device (e.g., laptop
31 computer) to a mobile station and use the wireless network as if it were a V.90 modem.
32 Aspects of this capability include the user’s ability to specify a modem and the airlink’s
33 support of the selected modem’s command set and the sustained bandwidth requirements.
34 3.2 Intentionally Left Blank
35 Completed work item. See System Capabilities Guide.
1 3.3 Analog Async Data to V.90 Speeds
2 This capability allows the transport, over the air interface, of V.90 data signals that are
3 presented to the mobile station as analog signals. The analog signals may be
4 encapsulated/translated as required for transmission over the air interface. An
5 interworking function in the network provides conversion back to the native analog
7 3.4 ISDN Interworking
8 ISDN networking is required to achieve the interconnection to ISDN and support 3G
9 mobile station users to communicate to ISDN subscriber directly in circuit switched
11 Required data rates are as follows:
12 1. 64 kbps.
13 2. 128 kbps
154. Data - Packet Capabilities
16 4.1 Packet Data Rates
17 The system standards shall support high-speed packet based communications. The bearer
18 capabilities for packet mode are as follows:
19 Packet mode bearers to at least 384 kbps.
20 4.2- 4.5 Intentionally Left Blank
21 Completed work item. See System Capabilities Guide.
23 4.6 Multiprotocol support (e.g. X.25)
24 Support for multiple protocols for packet data.(e.g. X.25).
25 4.7 Internet Protocol Version 6 (IPv6) Support
26 Support of IPv6 as per RFC 1883..
27 4.8 IP Broadcast and IP Multicast Services
28 This is a bearer capability that the network provides single originator - multi terminator
29 communication for packet data communications. Standard IETF multicast/broadcast
30 protocols should be taken into account.
31 Broadcast Services:
32 For broadcast services, the communication terminates to all subscribers on a PDSN
33 or in a particular area.
1 Multicast Services:
2 For multicast services, the communication terminates to all users subscribed to a
3 specific group.
4 These services may be provided via the air interface and/or the packet network per the
6 4.8.1 IP Broadcast and Multicast Support at the PDSN:
7 This capability translates IP Broadcast and Multicast messages received at the
8 PDSN into individual mobile specific messages for transport to the targeted mobile
10 4.8.2 IP Broadcast and Multicast Support Over the Air Interface:
11 For broadcast and multicast support the information should be sent over-the-air
12 using common channels to avoid message replication and thereby reduce traffic.
13 When a mobile station is otherwise engaged in a transmission and does not have
14 immediate access to the common channel, it may be required that the message be
15 replicated to reach one or more specific mobile stations. If no multicast member is
16 in a particular cell or sector, the information should not be sent.
17 4.9- 4.10 Intentionally Left Blank
18 Completed work item. See System Capabilities Guide.
20 4.11 Optimal Packet Routing
21 Optimal Packet Routing minimizes the number of nodes an IP packet traverses between
22 the mobile and host. This can be supported via the assignment of a Home Agent in a
23 local network.
24 4.12 Prepaid Support
25 This item will extend support for prepaid into packet based services.
275. Subscriber Services
28 5.1 Intentionally Left Blank
29 Completed work item. See System Capabilities Guide.
31 5.2 User Selective Call Forwarding
32 This feature permits a user to manually redirect, on a per call basis, incoming calls in the
33 alert or call waiting notification states to a network based voice mail system, to a network
34 pre-registered phone number, or to a phone number stored in the mobile station.
35 5.3- 5.4 Intentionally Left Blank
36 Completed work item. See System Capabilities Guide.
1 5.5 Emergency Services
2 Enhanced Emergency Services (ES) permits a subscriber to be connected to a Public
3 Safety Answering Point (PSAP) to request an emergency response from the appropriate
4 agency (e.g., fire, police, ambulance, poison control center, suicide prevention center).
5 The PSAP shall be the PSAP appropriate to the calling subscriber’s current location. An
6 ES call shall bypass any authorization restrictions or call origination restriction features
7 (e.g., Subscriber PIN Access (SPINA), Subscriber PIN Intercept (SPINI) features). ES
8 calls from uninitialized mobile stations shall also be supported. This call may
9 automatically invoke Priority Access and Channel Assignment (PACA) and the call may
10 be given a higher priority than normal calls. Once the ES call is answered, the subscriber
11 shall be able to communicate the type of emergency over a normal voice connection with
12 the PSAP. Air interface encryptions may be used, but the signal at the PSAP must be
13 unencrypted. A subscriber’s ability to activate flash privileges (features controlled by
14 activating the SEND key such as Call Waiting, Three-Way Calling, Conference Calling
15 and Call Transfer) is suspended during an ES call. The only flash privilege exception is
16 in the case where another call was placed on hold to originate the ES call, the mobile
17 station will be allowed to return to the held call while the ES call is still in progress.
18 When the ES call is released, the subscriber’s normal calling capabilities are restored.
19 Release occurs when either the subscriber or PSAP disconnects or when the ES call is
21 5.5.1 Calling Party Cell/Sector:
22 See 1.16.1.
23 5.5.3 Calling Party Latitude/Longitude:
24 See 1.16.3.
25 5.5.5 Mid Call Location Update
26 See 1.16.5.
27 The Stage-1 for this service is in ANSI-664-A.
28 5.6- 5.10 Intentionally Left Blank
29 Completed work item. See System Capabilities Guide.
30 5.11 Calling Party Pays
31 Calling Party Pays (CPP) permits a wireless subscriber to have some or all air time
32 charges for received calls applied to the calling party. The calling party may be calling
33 from the wireline or the wireless network.
34 The calling party will be given an opportunity to decline the charges. In cases when it is
35 not possible to charge the calling party, an alternative action may be taken (e.g., diverting
36 the call, denying the call, alternate billing, presenting the call to the user with an
37 indication, such as distinctive ringing, that the caller will not be paying for the call).
38 CPP does not impact a subscriber’s ability to originate calls.
1 5.12 Location Based Services
2 Location based services are services that provide different functional features,
3 capabilities, or attributes based on the geographic position or location area of the mobile
4 subscriber using the service. Location based services may be implemented in an
5 IMT-2000 network by using Position Location Technologies or zone determining
6 technologies (e.g., Tiered Services, Non-Public Mode).
7 Location based services allow service providers the opportunity to offer differential
8 billing an selective services based on the subscriber's geographic location when accessing
9 these services. They also allow service providers the opportunity to offer individual
10 subscribers, groups of subscribers, or businesses the ability to utilize private equipment to
11 offer location based services and the ability to restrict access to that equipment to the
12 users of the network. Service providers may also offer subscribers a residential service
13 which is a private system limit to a subscriber's home or a small area surrounding the
14 home. Examples of location based services include such services as Location Based
15 Charging, Fleet and Asset Management, Enhanced Call Routing, and Location Based
16 Information services.
17 See 1.16 for specific location based service support capabilities.
18 5.13 Intentionally Left Blank
19 Completed work item. See System Capabilities Guide.
20 5.14 Rejection of Undesired Annoying Calls
21 This service allows a subscriber to register a directory number of an incoming call as
22 undesirable and annoying after the call ends. Based on this registration, future calls from
23 the same calling party directory number will be denied.
24 5.15- 5.18 Intentionally Left Blank
25 Completed work item. See System Capabilities Guide.
26 5.19 Air Chat
27 This capability allows the real-time transfer of limited amounts of data directly between
28 two subscribers involved in a call. Examples of such data might be a phone number or a
29 phone list.
30 5.20 Intentionally Left Blank
31 Completed work item. See System Capabilities Guide.
32 5.21 Third Party Charging
33 This capability allows all or part of a call to be charged to a third party.
34 If a user does not have credit to originate a voice call, the network will connect a live
35 operator during call origination. The operator may request a credit card number and
36 other information to validate the mobile station and authorize credit. Depending upon the
37 credit limit, the user may make/receive a single call or a series of voice/data calls. The
38 network may restrict services to a geographic area (e.g., city wide) or time duration (e.g.,
39 end of business day).
1 For a normal user or a pre-paid user with sufficient credit, the user can connect with a
2 human operator and request third-party billing to override the normal billing for the next
3 call or series of calls.
4 5.22 Intentionally Left Blank
5 Completed work item. See System Capabilities Guide.
6 5.23 Location Dependent Charging
7 Location Depending Charging permits a wireless subscriber to be charged based on the
8 mobile station location. The Location Depending Charging is different than the normal
9 rate charged to the wireless subscriber, it may be higher rate or a lower rate based on the
10 specified geographic areas or zones. When the subscriber is requesting service and is
11 located outside the zones, the service provider may deny access to the services, or
12 provide the services at a different rate.
13 See 1.16 for specific location based service support capabilities.
14 5.24- 5.27 Intentionally Left Blank
15 Completed work item. See System Capabilities Guide.
16 5.28 Calling Information Audio Presentation
17 This capability allow a subscriber upon receiving a call to first hear audio information
18 about the call such as calling party name or number prior to being connected to the
19 calling party.
21 5.29 Video Streaming
22 Video streaming services are services in which continuous one way video and audio data
23 are delivered to an end user.
25 5.30 Video Conferencing
27 5.30.1 Video Conferencing – Two-Party
29 Two-party video conferencing services are the services that provide two-way
30 transmission of real-time video, audio and other contents through the wireless
31 communication systems between two parties.
33 5.30.2 Video Conferencing – Multi-Party
35 Multi-party video conferencing services are the services that provide two-way
36 transmission of real-time video, audio and other contents through the wireless
37 communication systems between two or more parties.
16. Wireless Intelligent Networking
3 6.1- 6.4 Intentionally Left Blank
4 Completed work item. See System Capabilities Guide.
5 6.5 Location Registration Based IN Services
6 This is a state model for interaction between Location Registration events and IN services
7 in the style of the Originating and Terminating Basic Call Models.
8 6.6 Authentication Based IN Services
9 This is a state model for interaction between Authentication events and IN services in the
10 style of the Originating and Terminating Basic Call Models.
117. Charging Capabilities
12 7.1 Packet Charging Information - Enhanced
13 This capability will expand upon present packet charging capabilities to provide for the
14 recording of information such as:
15 1. Information type
16 2. Source and destination information
17 3. Billing designators (eg. source vs. destination).
18 The exact designation of what parameters will be developed is the subject of stage 1
208. Air Interface Capabilities
21 8.1 Soft Handoff
22 8.1.2 Inter-MSC Soft Handoff:
23 A handoff in which the cells or sectors involved are under control of different
24 MSCs. This capability would provide for reconnecting the call through the serving
25 switch after one or more inter-BSC soft handoffs.
26 8.1.3 Inter-generation Soft Handoff:
27 A handoff in which the new cell or sector is 2G while all existing cells or sectors
28 are 3G (generation down) or in which the new cell or sector is 3G while all existing
29 cells or sectors are 2G (generation up). Data service should be maintained in a
30 generation up scenario though re-negotiation may be required. Data service should
31 be maintain in a generation down scenario; however, the service may be
32 discontinued or downgraded.
1 8.2 Intentionally Left Blank
2 Completed work item. See System Capabilities Guide.
3 8.3 Time Division Duplex (TDD) Physical Layer
4 A Time Division Duplex Physical Layer at the air interface allows a system to operate in
5 a single continuous frequency block. It does so by alternating in time between the
6 forward and reverse directions to make use of a single frequency block. The rate of
7 switching between forward and reverse directions is fast enough to be transparent to most
8 typical applications.
9 Note: As per the OHG agreement this is the responsibility of 3GPP.
11 8.4- 8.9 Intentionally Left Blank
12 Completed work item. See System Capabilities Guide.
13 8.10 Support for Handoff Between Different Carrier
14 Sizes and Structures
15 This work will involve the development for the support of various types of hand-off.
16 This will include support for both soft and hard handoff. Specific requirements include:
18 • Hard handoff is required between TIA/EIA-95 based systems and Harmonized
19 Direct Spread
20 • Handoff is required between TIA/EIA-95 based systems and Multi-Carrier (1X
21 and 3X).
22 • Hard handoff is required between 1X and harmonized Direct Spread
23 • Handoff is required between 1X and 3X Multi-Carrier
25 Other handoff scenarios may also be required.
27 8.11- 8.14 Intentionally Left Blank
28 Completed work item. See System Capabilities Guide.
29 8.15 Support for Common Channel Only Capable Devices
30 (eg. Telemetry/ Paging services)
31 This will permit the designation and operation of devices capable of operating only on the
32 cdma2000 common channels. Such devices reduce the complexity of delivering paging
33 and telemetry services in a cdma2000 system.
35 8.16 High Speed Data Enhancements
36 Provide enhancements to the cdma2000 family of standards to increase the speed and
37 efficiencies for data within the cdma2000 1x RF channel.
39 8.16.1 Data Only
40 A packet data only solution on a separate cdma2000 1x RF channel.
2 8.16.2 Integrated Data and Voice
4 A solution that integrates enhanced high speed packet data and voice on a
5 cdma2000 1x RF channel.
7 8.17 Access Overload Class by Service Option
8 This feature permits the Access Overload Class to be applied uniquely by service option.
9 This could for example limit the use of Packet Data Services to a select group of users while
10 permitting voice access to continue to operate normally.
129. Multi- call, Multi- media
13 9.1 Intentionally Left Blank
14 Completed work item. See System Capabilities Guide.
15 9.2 Voice and Packet Data Concurrent Support
16 This capability provides support for two concurrent services, one being voice and one
17 being packet data. This includes the ability to independently establish and terminate each
19 9.3 Multimedia Call Model
20 This capability supports multiple simultaneous connections of the same or different
21 traffic types including voice, circuit switched data, and packet data.
2310. Radio Access Interface
24 10.1 Open Radio Access Interfaces
25 This plurality of interfaces exists between the BS, MSC and PDSN in the Wireless
26 Network Reference Model. The capability provides for interoperability between different
27 BSs, MSCs, PDSNs and their associated equipment across these boundaries.
28 10.2 Open Abis Interface
29 This interface is between the BTS and the BSC in the Wireless Network Reference
30 Model. The capability provides for interoperability between different BTSs and BSCs
31 and their associated equipment across this interface.
3210.3 Support for 3x Multi- Carrier
33 This will add support to the A-Interface for the 3x Multi-carrier physical layer of the Air
110.4 Inter- Generation Handoff - Packet
2 This capability provides for handoff between a TIA/EIA-95B packet service and an
3 IS-2000 packet service.
410.5 IP Based RAN Architecture Study
5 TSG-A will explore alternate cdma2000 RAN architectures made possible by the
6 utilization of Internet based concepts and protocols. Evaluation of various characteristics
7 such as performance and complexity will be done in an attempt to identify a single
8 proposal for subsequent specification work. The target architecture will respect the high
9 level requirements as specified in the requirements and network architecture documents
10 of the Steering Committee All-IP Ad Hoc Group.
1111. Mobile Station Capabilities
12 11.1 Increased Battery Life
13 This standing requirement identifies the ongoing desire to improve both the standby and
14 talk times of mobile stations through whatever techniques may be suitable.
15 11.2 MS Adapter Interfaces
16 11.2.1 Voice:
17 This is a standardized interface supporting external voice connections to a mobile
18 station . Examples of such connections may be a handsfree car kit or a headset
20 11.2.2 TDD/TTY:
21 This is a standardized interface supporting TDD/TTY connections to a mobile
22 station .
23 11.2.3 Data:
24 This is a standardized interface supporting packet and circuit switched data
25 connections to the mobile station.
2612. Fixed Wireless
27 12.1 Wireless Local Loop
28 Wireless Local Loop extends the existing Air Interface to support Wireless Local Loop
29 Terminals and Network Interface Units by adding the following capabilities to the Air
32 1. The ability to specify a number of Wireless Local Loop Terminal Types.
33 2. The ability to identify Hook Status to the network from the Terminal.
34 3. The ability to generate Dial Tone by the network and/or the Terminal.
35 4. The ability to specify an Autonomous Message Interval.
36 5. The ability to signal Call Waiting Notification to the Terminal.
1 12.2 Multiple Simultaneous Call (single media)
2 12.2.1 Voice:
3 This capability permits more than one simultaneous voice call from a single mobile
4 station . Each call is independently controllable both in addressing and in call
6 12.2.2 Circuit Switched Data:
7 This capability permits more than one simultaneous circuit switched data call from
8 a single mobile station . Each call is independently controllable both in addressing
9 and in call control.
10 12.3 Wireless Payphone
12 This feature will provide for payphones based on prepaid cards. There is no specific
13 network/air interface support for coin based payphones in this feature. The feature uses
14 existing air interface metering signaling to allow the payphone to debit the card based on
15 network generated metering pulses. The feature does not provide for any network based
16 validation of the prepaid cards.
1813. Over the Air Service Provisioning and
19 Administration (OTASPA)
20 13.1 Mobile Initiated
21 This capability extends the OTASPA capabilities to permit a mobile station to initiate a
22 parameter update. The update may be application or user initiated, for example, to receive
23 an updated Preferred Roaming List after returning from a trip where roaming problems
25 13.2 User Data
26 This capability extends OTASPA to support user data contained within a mobile station.
27 Examples of user data would be a phone list or stored short messages. This capability
28 permits user data to be uploaded to the network for backup purposes and to be subsequently
29 downloaded to the mobile station for purposes of activation a new mobile station or
30 replacing a damaged unit. The data models for this capability shall support both generic
31 concepts such as a phone list to permit transfers between different mobile station models and
32 manufacturers and vendor specific data that may be unique to a particular mobile station
34 13.3 UIM Support
35 This capability extends OTASPA to support both integrated and removable UIM.
36 13.4 Tiered Services
37 This provides support for the Preferred User Zone List (PUZL) in OTASPA.
1 13.5 International Band Support
2 This capability will expand the supported bands to include the IMT-2000 band amongst
3 others. It will resolve potential problems where frequency blocks are no longer being
4 assigned consistently on an international basis.
6 13.6 Card Application Toolkit
7 The Card Application Toolkit (CAT) provides mechanisms that allow applications, existing
8 on the R-UIM, to interact and operate with any CAT capable ME irrespective of access
9 technology that the ME supports.
1114. Data - Support
12 14.1 Data Compression
13 Data compression support in the packet data network includes transparent support of IP
14 network layer compression between the mobile station and the host, compression at the
15 link layer, and TCP/IP header compression (e.g., RFC-1144 Compressing TCP/IP
16 headers for Low-Speed Links by Van Jacobson). This standing requirement exists to
17 insure maximum efficiency over the Air Interface.
18 14.2 Intentionally Left Blank
20 14.3 QoS – End to End
21 This activity is to provide an overall architectural and requirements model for the
22 provisioning and delivery of Quality of Service on an end-to-end basis, taking into
23 account the unique characteristics of each of the networks and transports involved.
25 14.4 Packet Data QoS Negotiation
26 The access network must support QoS negotiation per connection based on radio
27 resources and mobile station capabilities.
28 14.5 Packet Data QoS Parameters
29 QoS parameters allow differentiated services, whether the parameters are in the air
30 interface or system wide.
31 Initial - The initial set of parameters allow different priorities to be established between
32 applications and subscribers for basic IP transport.
33 Enhanced - The enhanced set of parameters support services such as video streaming and
35 14.6 Quality of Service Negotiation - During a Call
36 This capability would provide for dynamic provisioning of Quality of Service Parameters
37 as determined by either the application or the mobile station subscriber.
2 14.7 Quality of Service - User Selection
3 This capability permits a user to select Quality of Service Parameters from the mobile
6 15.1 Vocoder Tandem Free Operation (VTFO)
7 VTFO permits the bypass of speech encoding and decoding in the network for mobile
8 station to mobile station calls when the same digital codec type is used over the radio
9 interfaces serving the calling and called party. Vocoder bypass reduces throughput delay
10 produced by the tandeming of vocoders and may improve audio quality. This capability
11 includes both inter-BSC (intra-MSC) and inter-MSC operation.
12 Description needed for enhancements.
13 15.2 Selectable Mode Vocoder
14 This vocoder will provide for equivalent and/or improved voice quality when compared
15 against EVRC at a reduced average bit rate. It will provide for operator selection of
16 operating modes to trade off average bit rate vs. voice quality.
17 15.3 High Quality Audio Codec
18 A high quality audio codec would provide a quality level for audio transmission that far
19 exceeds current codecs that are tailored for voice. Such a codec would have increased
20 input bandwidth capability, wider dynamic range and may have multi-channel
21 capabilities such as stereo and/or surround sound.
23 15.4 Intentionally Left Blank