AGENDA ITEM: TITLE: CONTRIBUTORS: DOCUMENT FOR: ANSI-664 Features to be Supported in DS/ANSI-41 Systems Members of the 3GPP2 G3G Ad Hoc Ameritech Cellular Bell Atlantic Mobile Bell Mobility BellSouth China Mobile DENSO DDI Ericsson Fujitsu IDO IFR Systems KDD LG Infocomm Discussion LG Telecom Ltd. Lucent Technologies Inc. Motorola Nokia Nortel Networks Panasonic Philips QUALCOMM Samsung SK Telecom Sprint PCS US West Vodafone AirTouch Background: This document provides a summary of the services and features described in ANSI-664 in support of G3G. Page 1 of 24
0. Introduction This document provides a summary of the services and features described in ANSI-664 in support of G3G. 1. Background The following is an extract of an advance copy of the PMT meeting notes as recorded by the TSG-S Secretary, Clif Barber, for the PMT discussions of July 15, 1999. The results of the first G3G Ad Hoc meeting (3GPP2-S30-19990714-010) were presented as FYI. This correspondence included the Ad Hoc work plan (3GPP2-S30-19990714-010A) and terms of reference (3GPP2-S30-19990714-010B). Based on the G3G Ad Hoc work plan, the work schedule of the newly formed TSG-S OHG Requirements Ad Hoc was accelerated to complete the second draft by the Portland meeting for release at the G3G Ad Hoc face-to-face meeting. The high level requirements should be based on the requirements suggested from DDI, IDO, and KDD (3GPP2-SC-19990712-022.) The PMT determined that a list of 3GPP2 system capabilities is required for use by the G3G Ad Hoc in finalizing the design of the hooks and extensions. Assignments include: Clif Barber, Oki Telcom IS-2000 review John Visser, Nortel Networks ANSI-664 review TBD 3GPP2 Release A review The following text is an extract of the referenced DDI, IDO and KDD paper to the 3GPP2 SC. It provides an example of the style of text requested. 2.1 The capabilities/features defined in the 3GPP2 Work Plan shall be supported. The IMT-2000 system requirements have been discussed in 3GPP2 and have been described in the Work Plan. All the capabilities and features, such as QoS control, ISDN interworking and high speed packet, shall be supported. 2.2 The supplementary services provided by the cdmaone system shall be transparently supported for both circuit switched and packet modes. (The users can get the same service as available in the cdmaone system.) The supplementary services that have been supported by cdmaone system shall be maintained in the Harmonized DS + ANSI-41 system in addition to the 3G specific service features (refer to high level requirement in 2.1). Examples of the supplementary services supported by the cdmaone system are call waiting and three way calling. Page 2 of 24
2. Some Notes About ANSI-664 The version used is the V&V text, Revision 1, dated January 12, 1998. The following is an extract of ANSI-664: 1 Introduction This Standard presents a recommended plan for the implementation of Uniform Features for use in the Wireless Radiotelephone Service. Its intent is to describe services and features so that the manner in which a subscriber may place calls using such features and services may remain reasonably consistent from system to system. It is not intended to require that specific service offerings be required of all service providers. 1. 1 General This document describes a subset of wireless features which have been defined to enable a wireless subscriber to use these features in any system into which the subscriber roams. To accomplish this, the selected subset consists of features which are more likely to be used when roaming, and also features which are necessary to implement full inter-system operation. 1. 2 Objective The purpose of this document is to identify those wireless features which need to be standardized in all wireless systems, and to specify operation of those features such that a subscriber could use the feature in any system in a consistent manner. Page 3 of 24
3. Requirements Extracted from ANSI-664 and Related Documents The following services and capabilities shall be supported by 3GPP2 systems: 3.1 Advice of Charge Advice Of Charging (AOC) permits a wireless subscriber to receive charging information for telecommunication services. AOC information may be presented at the start of a call, during a call, or at the end of a call. AOC information is conveyed to the subscriber within five (5) seconds of the appropriate event (start of call, mid-call charging event, end of call). AOC information may be presented using visual display, or audible tone or announcement, or a combination of visual display and audible tone or announcement. AOC typically conveys the following types of information to the subscriber: Calling Rate; Change in Calling Rate; Accumulated Usage or Charge for the call just completed; Accumulated Usage or Charge for the billing period or calendar period; Usage Remaining in an Air Time Package. 3.2 Answer Hold (AH) Answer Hold (AH) provides a called subscriber the capability to answer the call, but selectively delay the conversation (e.g., calls in the alerting or Call Waiting state). The incoming call is provided an appropriate network announcement to notify the calling party to please hold. AH is also applicable to incoming calls being delivered to called AH authorized subscribers as Call Waiting (CW) calls. AH authorized subscribers, with AH active on an unanswered incoming call, shall resolve the call in the AH state prior to originating a new outgoing call or call leg. New incoming calls to AH authorized subscribers, with AH active on an unanswered incoming call, shall receive the appropriate busy treatment (e.g., busy tone, redirected to voice mail, etc.) for the called AH subscriber. As a result, only one incoming call shall be in the AH state per each AH called subscriber) 3.3 Asynchronous Data Service (ADS) This telecommunication service allows digital wireless subscribers to send and receive asynchronous data. ADS provides functionality similar to a wireline modem in that the data is modified to make it suitable for transporting over the appropriate medium. Both wireless and wireline media are accommodated to support interworking between the two networks in a way that is transparent to the terminal equipment. The subscriber's terminal equipment interfaces to a conventional DCE (Data Circuit-Terminating Equipment) data port. The far-end DCE interworks each end function as if connected to a compatible device. ADS procedures and interfaces are specified by appropriate air interface standards (e.g., TIA/EIA/IS-99 ortia/eia/is-135 and TIA/EIA/S-130). These TIA standards specify compliance with other common TIA data standards (e.g., EIA/TIA-602) and ITU recommendations (e.g.,.v.32 bis, V.42). Mobile originated service may be of two types: Data Only and Voice Then Data. Mobile terminated service may be of three types: One Number per Service, Two-Stage Dialing, or Voice Then Data. Page 4 of 24
3.4 Call Delivery (CD) Call Delivery (CD) permits a subscriber to receive calls to his or her Directory Number while roaming. CD does not impact a subscriber s ability to originate calls. CD does not impact a subscriber s ability to receive calls via a roamer port. 3.5 Call Forwarding Busy (CFB) Call Forwarding Busy (CFB) permits a called subscriber to have the system send incoming calls addressed to the called subscriber s Directory Number to another Directory Number (forward-to number) or to the called subscriber s designated voice mail box, when the subscriber is engaged in a call or service. 3.6 Call Forwarding Default (CFD) Call Forwarding Default (CFD) permits a called subscriber to send incoming calls addressed to the called subscriber s Directory Number to the subscriber s designated voice mail box or to another Directory Number (forward-to number), when the subscriber is engaged in a call, does not respond to paging, does not answer the call within a specified period after being alerted or is otherwise inaccessible (including no paging response, the subscriber s location is not known, the subscriber is reported as inactive, Call Delivery not active for a roaming subscriber, Do Not Disturb active, etc.). 3.7 Call Forwarding No Answer (CFNA) Call Forwarding No Answer (CFNA) permits a called subscriber to have the system send incoming calls addressed to the called subscriber s Directory Number to another Directory Number (forward-to number) or to the called subscriber s designated voice mail box, when the subscriber fails to answer, or is otherwise inaccessible (including no paging response, the subscriber s location is not known the subscriber is reported as inactive, Call Delivery not active for a roaming subscriber, Do Not Disturb active, etc.). CFNA does not apply when the subscriber is considered to be busy. 3.8 Call Forwarding Unconditional (CFU) Call Forwarding Unconditional (CFU) permits a called subscriber to send incoming calls addressed to the called subscriber s Directory Number to another Directory Number (forwardto number) or to the called subscriber s designated voice mail box. If this feature is active, calls are forwarded regardless of the condition of the termination. CFU does not impact a subscriber s ability to originate calls. 3.9 Call Transfer (CT) Call Transfer (CT) enables the subscriber to transfer an in-progress established call to a third party. The call to be transferred may be an incoming or outgoing call. 3.10 Call Waiting (CW) Call Waiting (CW) provides notification to a subscriber of an incoming call while the subscriber s call is in the 2-way state. Subsequently, the subscriber can either answer or ignore the incoming call. If the subscriber answers the second call, the subscriber may alternate between the two calls. Page 5 of 24
3.11 Calling Name Presentation (CNAP) Calling Name Presentation (CNAP) provides the name identification of the calling party (e.g., personal name, company name, restricted, not available ) to the called subscriber. The calling name identification (CNA) may be provided to the terminating network by the originating network or the terminating network may retrieve it or derive it using the calling number identification (CNI) which is generally provided to the terminating network from the originating network. The CNA is considered public when presentation of the calling name is allowed, and private when presentation of the calling name is restricted. Optionally, the date and time of the call may also be provided to the called subscriber. Redirecting Name Delivery (RND) is a CNAP subscription option. When CNAP with RND is active and a call has been forwarded, CNAP provides the CNA of the last redirecting party and the original calling party to the called subscriber. 3.12 Calling Name Restriction (CNAR) Calling Name Restriction (CNAR) restricts presentation of the calling subscriber s name to the called party. CNAR may restrict the presentation of the calling subscriber s name for all calls, or it may change the presentation status on a per-call basis. The terminating network may receive the calling name identification (CNA) as part of basic call setup or as a result of a database query. The portion of the CNA associated with the calling subscriber is considered public when presentation to the called party is allowed and private when presentation to the called party is restricted. 3.13 Calling Number Identification Presentation (CNIP) Calling Number Identification Presentation (CNIP) provides the number identification of the calling party to the called subscriber. One or two numbers may be presented to identify the calling party. The terminating network may receive the Calling Number Identification (CNI) as part of basic call setup. This CNI may include one or two Calling Party Numbers (CPNs), a Calling Party Subaddress (CPS), Redirecting Numbers (RNs), and a Redirecting Subaddress (RS). 3.14 Calling Number Identification Restriction (CNIR) Calling Number Identification Restriction (CNIR) restricts presentation of that subscriber s Calling Number Identification (CNI) to the called party. The terminating network may receive the Calling Number Identification (CNI) as part of basic call setup. This CNI may include one or two Calling Party Numbers (CPNs), a Calling Party Subaddress (CPS), Redirecting Numbers (RNs), and Redirecting Subaddresses (RSs). 3.15 Conference Calling (CC) Conference Calling (CC) provides a subscriber with the ability to have a multi-connection call, i.e., a simultaneous communication between three or more parties (conferees). If any of the conferees to a conference call disconnects, the remaining parties remain connected. If the controlling subscriber of a conference call disconnects, the conference circuit and all conferees are released. CC remains in effect until the controlling subscriber disconnects. The controlling party may drop the conferee connected the shortest time with the drop last party feature code. Any number of conferees may be dropped this way. The conference call terminates when no other conferee remains. Page 6 of 24
3.16 Data Privacy (DP) Data Privacy (DP) provides a degree of privacy for the subscriber over the radio link. A call requesting DP, while DP is not available, may be rejected by the system. 3.17 Do Not Disturb (DND) Do Not Disturb (DND) prevents a called subscriber from receiving calls. When this feature is active, no incoming calls shall be offered to the subscriber. DND also blocks other alerting, such as the Call Forwarding Unconditional abbreviated (or reminder) alerting and Message Waiting Notification alerting. DND makes the subscriber inaccessible for call delivery. 3.18 Emergency Services (9-1-1) Emergency Services ( 9-1-1) permits a subscriber to dial 9-1-1-SEND and be connected to a Public Safety Answering Point (PSAP) to request an emergency response from the appropriate agency (e.g., fire, police, ambulance, poison control center, or suicide prevention center). The PSAP shall be the PSAP appropriate to the calling subscriber s current location. A 9-1-1 call shall bypass any authorization restrictions or call origination restrictions features (e.g., Subscriber PIN Access (SPINA), Subscriber PIN Intercept (SPINI) features). The call shall automatically invoke Priority Access and Channel Assignment (PACA), and the call shall be given higher priority than normal calls. Once the call is answered, the subscriber shall be able to communicate the type of emergency over a normal voice connection with the PSAP. (Encryption may be used over the air interface, but it must be removed on the connection to the PSAP.) A 9-1-1 call does impact a subscriber s ability to originate or receive calls while the 9-1-1 call is in progress. Flash privileges (features controlled by activating the SEND key, such as, Call Waiting, Three-Way Calling, Conference Calling, and Call Transfer) are suspended during the 9-1-1 call, except to re-connect a call placed on hold to place the 9-1-1 call. When the 9-1-1 call is released, the subscriber s normal calling capabilities are restored. Release occurs when either the subscriber or PSAP disconnects. Special release controls may apply, as described in Emergency Services Reconnect ( 9-1-1RC). 3.19 Flexible Alerting (FA) Flexible Alerting (FA) causes a call to a Pilot Directory Number to branch the call into several legs to alert several termination addresses simultaneously. The mobile telephones in the group may be alerted using distinctive alerting. Additional calls may be delivered to the FA Pilot Directory Number at any time. The first leg to be answered is connected to the calling party. The other call legs are abandoned. The members of an FA group are described by a list of termination addresses. Each termination address may either be a Directory Number or a MIN or IMSI that uniquely identifies a mobile station. This allows MSs served by the same Home Location Register (HLR) as the FA pilot DN, MSs served by other HLRs (especially for serving multi-nam phones of multiple service providers) and landline telephone numbers to be included 1. 1 Interactions between FA and the features of FA members controlled by different systems are beyond the scope of this Interim Standard. Page 7 of 24
FA may be used for either a single user or multiple users. The difference between the two is in determining when the FA group is busy. In the single user case, the group is considered to be busy when one of the members is considered to be busy. In the multiple user case, the group is considered to be busy when all of the accessible members are considered to be busy. A member is considered to be busy when it cannot accept the presentation of another call. The busy condition of landline telephones cannot always be accurately determined. The FA Pilot Directory Number may have features to manage incoming calls. These features should take precedence over the corresponding features of individual members, however, these interactions, when occurring at the Home Location Register (HLR), are beyond the scope of ANSI-664. If an FA Pilot Directory Number is an FA member Directory Number, the FA member loses his or her individual incoming call features. The FA member s incoming call features are superseded by the incoming call features of the FA Pilot Directory Number. If an FA Pilot Directory Number is not an FA member Directory Number, the features of the FA Pilot Directory Number may be changed only through Remote Feature Control or service provider provisioning. If an FA member has only a single Directory Number that is the same as the FA Pilot Directory Number, the FA member may not receive calls except through the FA Pilot Directory Number. If an FA member has a Directory Number different than the FA Pilot Directory Number, the FA member may receive calls as an individual as well as calls through the FA Pilot Directory Number. Such an FA member may use revertive calling (i.e., a call to itself) for other features, such as Voice Mail Retrieval. 3.20 Global Emergency Call Origination (GECO) This section details the functionality of the GECO feature. The basic operations are indicated below: The MS shall provide a means, either by dialing the emergency access number (e.g., 911) or other vendor specific means (i.e., hot button(s) or other), for the user to initiate an emergency call. The actual user interface for the user to initiate a GECO call is vendor specific and not the subject of standardization. However, internally programmed call restrictions shall not prevent the user from initiating a GECO call. A special call origination message (defined as an Global Emergency Call Origination Message (GECO_MSG)) shall be issued by the MS in lieu of the standard call origination message to indicate that the call origination being requested is an emergency call origination. The GECO_MSG can be interpreted as follows: In those networks that support a single PSAP, the GECO_MSG can be interpreted by appropriate programming of the network for connection to the PSAP without regard to the dialed digits included in the GECO_MSG. Alternatively, in those networks that support multiple PSAPs, the network can be programmed to evaluate the dialed digits included in the GECO_MSG to determine more specific information regarding the type of emergency support requested and, therefore, the required routing of the call. Page 8 of 24
For those networks supporting GECO, GECO_MSGs may be accepted and the GECO call connected by the network from both subscribed and unsubscribed mobiles. For those networks supporting GECO, the GECO_MSG shall also be considered to be an implicit registration of the MS by the network to expedite the GECO call connection. That is to say that when the MS accesses a system for the purpose of initiating a GECO call, the GECO_MSG may be issued by the MS and shall be accepted by the network without an explicit registration by the MS on that system. Other actions by the network to prioritize and otherwise expedite the connection of a GECO call are vendor specific and not the subject of standardization. If the MS is currently registered on and accessing an operating network when the GECO call is initiated by the user, the MS shall use that system to initiate the GECO call. If the MS is not currently accessing a system, the MS shall attempt to access its preferred service as indicated by its internal system selection and system access restriction programming to maximize the probability that the GECO call will be accepted by the system. If no preferred system is available, the MS may override its internal system selection and system access restriction programming in an attempt to access any available system. Other actions by the MS to expedite the initiation and connection of a GECO call are vendor specific and not the subject of standardization. Initiation of a GECO call by the MS shall in no way degrade the user s access to any other feature/service which would normally be available to him from the accessed service provider s network 3.21 Group 3 Analog Facsimile Service (G3AFax) A standard Group 3 facsimile machine 2 uses a 2 wire loop interface (the RJ-11 in North America) to connect to the PSTN. Through this analog, voice band, connection, the machine communicates with another fax machine using the appropriate G3 fax protocols. Supporting the operation of such fax machines is necessary in a wireless telephone system where subscribers expect to use their standard fax machines to send and receive faxes through their wireless subscriber unit. The G3 AFax Service shall allow digital wireless subscribers to send and receive faxes using standard Group 3 fax machines and fax modems. The fax machine connects to the Wireless Access Subscriber Unit (WASU), sometimes called a Fixed Wireless Terminal (FWT), through the 2 wire loop interface as it would to the PSTN. The figure below shows one possible configuration. It should be noted that the WASU or FWT can be stationed either inside or outside the subscriber s premises. 2 The term fax machine is used to describe a standard fax machine, a fax modem connected to a computer, or any other fax device that operates according to the ITU-T T.30 Group 3 fax protocol. Page 9 of 24
G3 AFax service shall perform the necessary data and protocol conversions between the 2 wire loop interface, the wireless digital network, and the PSTN to allow the proper transmission of fax documents. This shall be done in a manner that is transparent to the G3 analog fax machines involved in the fax transaction. WASU originated service may be one of three types: Automatic G3 AFax, Dial-Prefix Selected Service, or G3 AFax Directory Number (DN). WASU terminated service may be one of four types: Automatic G3 AFax, G3 AFax DN, Two-Stage Dialing, or Pre-selection. 3.22 Group 3 Facsimile Service (G3 Fax) This telecommunication service allows digital wireless subscribers to send and receive faxes similar to the functionality in 4.21 but does not provide for use of a WASU and an analog fax machine. It does so by implementing over the Air Interface the Service Class 2.0 AT command set of TIA/EIA-592 and TIA/EIA-707A. The network then converts the AT command set and fax data into analogue G3 fax modem signals at the interface to the PSTN. This capability allows Mobile Station implementations to: 1. Provide fax service directly by supporting this command set and generation of fax data internally. 2. Provide fax service indirectly by passing on to the air interface AT commands and fax data received via a digital interface contained on the mobile station consistent as might be implemented in a laptop to fax modem connection. Mobile originated service may be of two types: G3 Fax Only and Voice Then G3 Fax. Mobile terminated service may be of three types: One Number per Service, Two-Stage Dialing, or Voice Then G3 Fax. 3.23 ISDN Interworking (ISDN IW) ISDN Interworking is permits a wireless subscriber to interconnect to ISDN and to communicate to ISDN subscriber directly in circuit switched mode. Followings are the items to be defined for the ISDN Interworking; (1) Quality of Services Quality of services is categorized by the error rate and the transmission delay. Category 1 Error rate: Not guaranteed. (Note 1) (i.e. no re-transmission required in 3G Mobile NW) Delay: Constant and minimum delay guaranteed. (i.e. only delay on air and internal processing delay) Other Categories (For Further Study Note 2) Page 10 of 24
(2) Data rate In ISDN interworking, guaranteed constant data rate is mandatory. 3G Mobile networks should support the Information Transfer Rate described in ITU-T DSS1 recommendations. Required data rates are as follows: 64k bit/s 128k bit/s (Note 3) Support of higher data rate (i.e., 384k bit/s, 1536k bit/s, and 1920k bit/s) and Multirate based on 64k bit/s base rate is for further study. (3) Basic Bearer 3G Mobile Network should support the Information Transfer Capability described in ITU-T DSS1 recommendations. Initial required basic bearer is as follows: Unrestricted Digital Information Support of other basic bearers described in DSS1 is for further study. (Note 1) (Note 2) (Note 3) (Note 4) Desired error rate is the order of 1 x 10-6 on the air. Other QoS categories, e.g., error rate guaranteed with appropriate delay for retransmission permitted, are for further study. Data rate is 128k bit/s at U m point, Ab and A interface and 64k bit/s X 2 at Interconnection point (i.e., POI) to ISDN. Bearer of the Restricted Digital Information should be supported if any of the networks concerned with the communications (e.g., transfer network, etc.) cannot transmit Unrestricted Digital data. Sub-address is not supported in ISDN Interworking. 3G Network should remove both callingparty sub-address and called-party sub-address if present. In this case, the Network screening indicator may be set as Subscriber inserted, network verification failure. 3.24 Message Waiting Notification (MWN) Message Waiting Notification (MWN) informs enrolled subscribers when a voice message is available for retrieval. MWN may use pip tone, an MS indication, or alert pip tone to inform a subscriber of an unretrieved voice message(s). 3.25 Mobile Access Hunting (MAH) Mobile Access Hunting (MAH) causes a call to a Pilot Directory Number to search a list of termination addresses sequentially for one that is idle and able to be alerted. If a particular termination address is busy, inactive, fails to respond to a paging request, or does not answer alerting before a time-out, then the next termination address in the list is tried. Only one termination address is alerted at a time. The mobile telephones in the group may be alerted using distinctive alerting. Additional calls may be delivered to the MAH Pilot Directory Number at any time. Page 11 of 24
The members of an MAH group are described by a list of termination addresses. Each termination address may either be a Directory Number or a MIN/IMSI that uniquely identifies a mobile station. This allows MSs served by the same Home Location Register (HLR) as the MAH pilot DN, MSs served by other HLRs (especially for serving multi-nam phones of multiple service providers) and landline telephone numbers to be included 3. MAH may be used for either a single user or multiple users. The difference between the two is in determining when the MAH group is busy. In the single user case, the group is considered to be busy when one of the members is considered to be busy. In the multiple user case, the group is considered to be busy when all of the accessible members are considered to be busy. A member is considered to be busy when it cannot accept the presentation of another call. The busy condition of landline telephones cannot always be accurately determined. The MAH Pilot Directory Number may have features to manage incoming calls. These features should take precedence over the corresponding features of individual members, however, these interactions, when occurring at the Home Location Register (HLR), are beyond the scope of ANSI-664. If an MAH Pilot Directory Number is an MAH member Directory Number, the MAH member loses his or her individual incoming call features. The MAH member s incoming call features are superseded by the incoming call features of the MAH Pilot Directory Number. If an MAH Pilot Directory Number is not an MAH member Directory Number, the features of the MAH Pilot Directory Number may be changed only through Remote Feature Control or service provider provisioning. MAH does not affect the ability of an MAH member to originate calls. MAH may affect the ability of an MAH member to receive calls. If an MAH member has only a single Directory Number that is the same as the MAH Pilot Directory Number, the MAH member may not receive calls except through the MAH Pilot Directory Number. If an MAH member has a Directory Number different than the MAH Pilot Directory Number, the MAH member may receive calls as an individual as well as calls through the MAH Pilot Directory Number. Such an MAH member may use revertive calling (i.e., a call to itself) for other features, such as Voice Mail Retrieval. 3.26 Network Directed System Selection (NDSS) The Network Directed System Selection (NDSS) feature is a network capability that provides a network based mechanism for a service provider, based on various customer and service provider specified criteria, to automatically direct a subscriber's Mobile Station (MS) to a desired serving system. The serving system could be any system available to the MS, regardless of frequency band (cellular A/B or PCS bands A/B/C/D/E/F) or technology (analog or digital). NDSS consists of procedures that allow wireless subscribers to register upon a preferred system while they are roaming (i.e., outside of their home system) without manual intervention by the subscriber. NDSS allows an MS to automatically register with a preferred serving system or to be automatically directed by their home system to a suggested system based on bilateral agreements between the serving system and home system. When an MS registers on a visited system, the network may direct the MS from that system to another system. The network may provide information which controls the status of the Enhanced Roaming Indicator in the MS. NDSS may override system selection procedures in the MS. The subscriber should have the ability, however, to suppress NDSS, and use the MS's system selection procedure. The status of NDSS (i.e., Active, Suppressed) is maintained in the home system, and may be changed upon request by the subscriber. 3 Interactions between MAH and the features of MAH members controlled by different systems are beyond the scope of this Interim Standard Page 12 of 24
3.27 Non-Public Mode Service (NP) Non-Public Service Mode (NP) permits a subscriber to access available wireless service on a business telephone system (or private system) or a residential telephone system. An application of Non-Public Mode Service is the User Zone (UZ). User Zones are defined as entities (geographic, logical, or both), specified primarily by the Private System Identifier (PSID), Residential System Identifier (RSID), System Identifier (SID), or Network Identifier (NID) associated with the zones. User Zones provide an optimization that allows for a mapping (maintained in the serving MSCs) to multiple PSID/RSID/SID/NIDs, so that network traffic related to PSID/RSID/SID/NID downloads is minimized A subscriber may obtain NP service via User Zones using the UZ Identifier. A UZ may consist of a coverage area as small as a cell sector or a group of cells that overlay the Public Wireless System, and may be a subset of a PSID/RSID/SID/NID. Alternatively, User Zones spanning many systems may be identified by a common User Zone Identifier in all these systems. UZ's or PSID/RSIDs can offer differentiating flavors of services beyond those offered by the Public System, based on criteria such as preferential charging areas, specific location identities, zone unique features, etc. An end user may receive an in-call indication via a tone or an MS display (icon) when a UZ or PSID/RSID is transitioned. 3.28 Over the Air Service Provisioning (OTASP) The Over the Air Service Provisioning (OTASP) feature allows a potential wireless service subscriber to activate (i.e., become authorized for) new wireless service, and allows an existing wireless subscriber to make changes in existing services without the intervention of a third party. OTASP typically includes the following: a. A call to the service provider customer service center. b. Over-The-Air programming of Number Assignment Modules (NAMs), and optionally, service provider or manufacturer specific parameters (e.g., lock code, call timer). c. An Authentication Key Generation procedure. The OTASP feature has the following objectives: 1. To support OTASP on digital systems. 2. To simplify the service provisioning process for both the user and the wireless service provider. 3. To increase efficiency of mobile station NAM programming and reduce the possibility of errors during initial service provisioning programming. 4. To enable a potential wireless user to easily choose a desired wireless service provider. 5. To minimize the ability to fraudulently use wireless service. 6. To keep the distribution of the Authentication Key (A-key) secure. 7. To safeguard user information. One of the primary objectives of OTASP is the ability to provide a secure authentication key to an MS to facilitate authentication. Authentication is the process by which information is exchanged between an MS and the network for the purpose of confirming and validating the identity of the MS. A successful outcome of the authentication process occurs only when it is demonstrated that the MS and the network possess identical sets of Shared Secret Data (SSD). The OTASP feature incorporates a cryptographic Authentication Key Generation procedure. This procedure allows the network to exchange Authentication Key parameters with an MS. These parameters are used to generate the A-key that is used to generate the SSD. The Authentication Key Generation procedure enhances security for the subscriber and reduces the potential for fraudulent use of wireless telecommunications service. Page 13 of 24
Any Authentication Key Generation algorithm chosen shall satisfy the following subscriber, system operator, and equipment manufacturer requirements for A-key delivery to the MS: 1. The subscriber should not be required to make any keypad entries in addition to those required to initiate OTASP. 2. The MS should not be required to contain secret information (e.g., Authentication Key) when it is initially delivered to the subscriber. 3. The MS shall be capable of normal operation, including full authentication, after the end of the service provisioning procedure. For MSs that contain more than one Number Assignment Module (NAM) 4, OTASP may be used to perform service provisioning for the NAM selected by the user. MSs may be reprogrammed after they have been initially programmed. Reprogramming is performed using the same procedures as initial programming. There may be some cases in which an MS shall be prohibited from being reprogrammed. It is left to the service provider to determine and control which MSs shall not be reprogrammed. 3.29 Password Call Acceptance (PCA) Password Call Acceptance (PCA) is a call screening feature that allows a subscriber to limit incoming calls to only those calling parties who are able to provide a valid PCA Password (i.e., a series of digits). Calls from parties who cannot provide a valid PCA Password shall be given call refusal treatment while PCA is active. PCA provides a method for screening incoming calls while providing access to the subscriber from a calling party using any terminal or phone. 5 When a call is placed to a PCA subscriber with PCA active, the call is routed to an announcement requesting the calling party to enter the PCA subscriber s PCA Password. The call shall be allowed to terminate to the subscriber only if the calling party enters the correct PCA Password. If an invalid PCA Password is entered, the system may chose to re-solicit the PCA password or give call refusal treatment. Calls so refused may, optionally, be logged. A subscriber may select a diversion number termination address when the subscriber registers the PCA. 3.30 Preferred Language (PL) Preferred Language (PL) provides the subscriber the ability to specify the language for network services. This service allows the subscriber to specify service in English, Spanish, French, Portuguese or Japanese. 6 Provision may be made for additional languages in the future. 4 Each NAM may be associated with a different service provider. 5 Enhanced capabilities, such as (a) the use of multiple passwords, (b) the automatic activation and de-activation of PCA based on time-of-day or day-ofweek schedules, are left as service provider options. 6 Korean? Page 14 of 24
Network services which could be offered in the subscriber s preferred language include: Recorded announcements Directory assistance Operator services Emergency services Help lines Message Waiting Notification CNIP number not available CNIP number restricted If the subscriber s preferred language is not available, service shall be provided in the default language, which shall be determined by the cellular wireless network operator. 3.31 Priority Access and Channel Assignment (PACA) Priority Access and Channel Assignment (PACA) allows a subscriber to have priority access to voice or traffic channels on call origination. This feature permits a subscriber to obtain priority access to voice or traffic channels by queuing these subscribers originating calls when channels are not available. When a channel becomes available, the queued subscriber is served on a first come first served and a priority basis. The subscriber is assigned one of n priority levels at subscription time (where n has a minimum of eight and a maximum of fifteen). Priority levels are defined as 1, 2, 3,,n, with 1 being the highest priority level and n being the lowest priority level. The invocation of PACA is determined by subscription to one of two options: Permanent or Demand. In the Permanent option the feature is always available and is used automatically whenever the subscriber attempts to originate a call. In the Demand option the feature is available only on request. For the Demand option, the subscriber requests PACA by using a feature code with an origination request. Call originations to priority access service codes or Directory Numbers (e.g., 9-1-1, fire, police medical) should invoke PACA using an independent priority level assigned to each number by the serving service provider. The priority used for the call shall be the higher of the dialed number s priority level or the subscriber s priority level. The subscriber is considered to be busy while it waits for a PACA channel to be assigned. 3.32 Rejection of Undesired Annoying Calls (RUAC) Rejection of Undesired Annoying Calls (RUAC) is defined as a service that the network rejects undesired annoying calls delivering to the called subscriber. Rejection service of Undesired Annoying Calls (UAC) is provided upon a subscriber's request to register a certain UAC number to the network. After the registration, the network rejects calls with a certain UAC number in place of the called subscriber. Even in the case that the calling subscriber activated CNIR(Calling Number Identification Restriction), however, the RUAC function is available. Rejection is notified to the UAC number subscriber by way of in-channel announces or outer-channel signaling by the network. However, the called subscriber does not receive the notification. Page 15 of 24
RUAC is based on ICS (Incoming Call Screening), but there are a few different points from ICS. a) The UAC caller is registered to the list after the call release. 7 The object of RUAC is to reject the call when the caller is not identified and calls a few times for the purpose of bothering or annoying the called subscriber. Therefore the called subscriber must reject even if the call with CNIR denying the number displayed. The way of registration to the RUAC list shall be to send not a specified calling number, but registration feature code when the UAC call is released. b) The de-registration request is used for deletion of the newest or all numbers from the RUAC list. The called subscriber may not identify each calling number in the RUAC list on account of as mentioned above. If the de-registration is needed, the called subscriber delete the newest or all number from the list. c) The system may charge the caller for a refused call by RUAC. When the UAC caller in the RUAC list calls, the system rejects it and plays the specified announcement, same as the ICS (Incoming Call Screening.) The rejected call by the RUAC is for the purpose of bothering or annoying the called subscriber, and it spend the network resource for the processing. In order to make the caller to stop, the system may charge the caller for the refused call. 3.33 Remote Feature Control (RFC) Remote Feature Control (RFC) permits a calling party to call a special RFC Directory Number, identify itself as an authorized subscriber with a mobile Directory Number and an RFC Personal Identification Number (PIN), and to specify one or more feature operations. This service is accessible from any mobile or landline station. To reduce fraudulent use, RFC is protected with a Personal Identification Number (PIN). Features accessible through RFC should be restricted, and the allowed operations should be limited to activation and de-activation. 3.34 Selective Call Acceptance (SCA) Selective Call Acceptance (SCA) is a call screening service that allows a subscriber to receive incoming calls only from parties whose Calling Party Numbers (CPNs) are in an SCA screening list of specified CPNs. Calls from CPNs not on the SCA screening list and calls without a CPN shall be given call refusal treatment while SCA is active. The SCA screening list is a set of CPNs that shall be permitted to terminate to the called subscriber. A subscriber may select a diversion number termination address when the subscriber registers the SCA. 7 Interaction with the TR45.2 WIN Task Group may add the capability of adding an undesired annoying caller to the RUAC list while the call is still active. Page 16 of 24
3.35 Service Negotiation (SN) SN provides a capability for the MS to choose a Service Configuration at the onset of a call or change a Service Configuration during a call. This may involve an iterative negotiation process to reach a service configuration mutually acceptable to the MS and the system prior to the negotiation process on the network. This includes voice and data service calls originating from and terminating to an MS. For each user, allowed service options are specified by the service provider at service authorization. Preferred service options may also be specified at service authorization. Optionally, these preferences may be controlled by the user of the MS. The system uses a service configuration which includes a currently available service option that is allowed for the user and chosen in accordance with the preferred service option information. As a result of a user initiation of a Service change, the system may initiate a change in the preferred Service Option information of the MS while a call is in progress. 3.36 Short Message Delivery Point-to-Point Bearer Service (SMD- PP) Short Message Delivery Point-to-Point (SMD-PP) provides bearer service mechanisms for delivering a short message as a packet of data between two service users, known as Short Message Entities (SMEs). SMEs are SMS endpoints capable of composing or disposing of a short message. One or both of the service users may be a mobile station. The data packets are transferred transparently between two service users. The network or destination application generates negative acknowledgments when it is unable to deliver the message as desired. The destination application may respond with an automatic acknowledgment and may include application generated or user provided information. The length of the Bearer Data may be up to 200 octets. Implementations and service providers may further restrict this length. SMD does not provide packet fragmentation or re-assembly services by the network. (Teleservices may support fragmentation and re-assembly using messages sent independently on the network.) Message integrity should be maintained over all interfaces including the Base Station to Mobile Station radio link (air or U m interface). The SMD-PP service attempts to deliver a message to an MS based SME whenever the MS is registered even when the MS is engaged in a voice or data call. Each SME has a network address. A SME may have multiple network addresses. MS based SMEs may roam throughout the network. Messages to an MS based SME are usually addressed to his or her Message Center (MC). This address is translated into a routing address for the purposes of message delivery. The SMD-PP message consists of a packet with the following attributes: Bearer Data The Bearer Data attribute is of variable length up to 200 octets in length. Implementations and service providers may further restrict this length. The Bearer Data attribute is conveyed transparently by the intervening network. This attribute includes a length indication. The Bearer Data is encoded and interpreted by the teleservice. Page 17 of 24
Message Type The Message Type attribute indicates the type of the message, and may be specified as: a. Request (an SMS message). b. Acknowledgment (a message sent to report errors or confirm delivery in response to an SMS message). Charge Indicator [optional] Message may indicate charging options for usage metering separation. Cause Code The Cause Code is used in acknowledgments to convey the reason for not being able to complete a particular message delivery. (See ANSI-41 for the code values.) Originating Address The Originating Address is the network address identifying the node sending the SMD message. It is used to deliver a return acknowledgment message. This may not be the original message sender, when store and forward services are provided. This attribute may be physically absent, if it can be derived from other attributes. The Originating Address allows E.164, X.121, internet IP, or MDN address formats. MSs are usually addressed by their E.164 mobile Directory Number, although mapping services may allow addresses on interconnected networks. Destination Address The Destination Address is the network address used for delivery of the message. This attribute may be physically absent, if it can be derived from other attributes. Mobile subscribers may be assigned a temporary routing address to allow delivery of messages while roaming anywhere in the network. This address is not generally known, accessible, or available. The Destination Address allows E.164, X.121, internet IP, or MDN address formats. MSs are normally addressed by their E.164 mobile Directory Number, although mapping services may allow aliased addresses on interconnected networks. Teleservice Identifier The Teleservice Identifier selects the application and teleservice that is to use the Bearer Data. Teleservice Identifiers should be standardized (or reserved by the standard). Carrier specific applications may be assigned a range of the identifiers. A Teleservice Identifier should be reserved for the general bearer service maintenance. This Teleservice Identifier may be used when reporting message routing problems. The Teleservice Identifier should be 16 bits. Original Originating Address The Original Originating Address is the network address initiating the message. This attribute need only be present if the Originating Address is different than the Original Originating Address. This attribute may be physically absent, if it can be derived from other attributes. Page 18 of 24
The Original Originating Address is in any allowable Originating Address format. Original Destination Address The Original Destination Address is the destination network address in the original message. This attribute may be physically absent, if it can be derived from other attributes. The Original Destination Address is in any allowable Destination Address format. Original Originating Subaddress [Optional] The Original Originating Subaddress is an address within an addressable message origination node to identify a particular SME. Original Destination Subaddress [Optional] The Original Destination Subaddress is an address within an addressable message destination node to identify a particular SME. Mobile Identification Number [Optional] The Mobile Identification Number is primarily used to address messages to MS-based SMEs. Electronic Serial Number [Optional] The Electronic Serial Number is primarily used to address messages to MS-based SMEs. 3.37 Subscriber PIN Access (SPINA) Subscriber PIN Access (SPINA) permits a subscriber to control whether his or her mobile station is allowed to access the network by using a SPINA Personal Identification Number (PIN) as a subscriber identity. This feature may be used by the subscriber to prevent unauthorized use of his or her own mobile station or fraudulent use by a clone. Note that the access restriction is network-based rather than a terminal-based lock-out feature. 3.38 Subscriber PIN Intercept (SPINI) The Subscriber PIN Intercept (SPINI) feature enables a subscriber to restrict outgoing call origination usage of their mobile. The subscriber is required to enter a SPINI Personal Identification Number (PIN) authorization code (i.e., a subscriber-specific string of digits) in order to originate calls meeting a specified criteria (e.g., local call type). If the correct SPINI PIN authorization code (or, simply, PIN) is entered, call originations are allowed. If an invalid SPINI PIN is entered, call originations shall be given denial treatment (e.g., an announcement indicating the reason for denial). Calls so denied may, optionally, be logged. This feature provides a level of security against cloning and fraud by requiring the subscriber to identify itself by entering a SPINI PIN for certain call originations. The service provider selects the call types requiring a SPINI PIN. That is, for each subscriber, the SPINI PIN may be required on certain classes of calls (e.g., local, international, long distance, feature registration attempts, or directory assistance with call completion, etc.). Page 19 of 24
SPINI PIN shall not be required on unrestricted call types (e.g., emergency). SPINI PIN may not be required for a list of frequently called numbers, regardless of their call type. The subscriber may be authorized to change the SPINI PIN at any time. The service provider has the ability to register or de-authorize the SPINI PIN for any subscriber at any time. 3.39 Three-Way Calling (3WC) Three-Way Calling (3WC) provides the subscriber the capability of adding a third party to an established two-party call, so that all three parties may communicate in a three-way call. If either of the two non-controlling parties to an established three-way call disconnects, the remaining party is re-connected to the controlling subscriber as a normal two-party call. If the controlling subscriber of a three-way call disconnects, the conference circuit and all other parties are released. 3.40 User Group (UG) User Group (UG) allows for a number of UG capable MSs to register for operation within a specific user group. This group of MSs can be alerted as a group (i.e., simultaneously) when a call is made to the directory number associated with the group. MSs registered in a User Group can receive distinctive alerting for incoming calls to the User Group. In other words, the service provider can establish different ringing patterns based on whether the call is to the MIN or to the User Group. MSs are allowed to be authorized in multiple User Groups, but can be active in only one User Group at a time. MSs may be active in both an FA/MAH group and a User Group at the same time. MSs can request to be activated on a particular User Group, or request to be activated without specifying a Group ID (in which case they will be assigned a default User Group). MSs can also request to be deactivated from the User Group in which they are currently active. The MS user shall be provided an indication of the result (success or failure) of a user group request. A user group can be associated with a geographical area known as the domain of the user group. When the MS roams into an area which lies outside the domain of the active user group, the MS user may be provided an indication that the MS is no longer active within the group. 3.41 User Selective Call Forwarding (USCF) User Selective Call Forwarding (USCF) provides a called subscriber the capability to selectively redirect incoming calls, in the alerting or Call Waiting state, to an alternate destination (e.g., to a voice mail system, to a network registered USCF DN, or to a DN stored in the Mobile Station (MS). USCF alternate destination DNs received over the radio link have precedence over USCF pre-registered network stored DNs. USCF called subscribers also authorized for calling party information presentation features (e.g., Calling Number Identification Presentation [CNIP], Calling Name Presentation [CNAP], etc.) may redirect incoming calls to different DNs based on the received calling party s identity. Page 20 of 24