1、 TIA-664.518-B (Revision of TIA-664.518-A) October 2007Wireless Features Description: Remote Feature Control (RFC) ANSI/TIA-664.518-B-2007 APPROVED: OCTOBER 12, 2007 REAFFIRMED: JANUARY 28, 2013 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through elimi
2、nating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall n
3、ot in any respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally.
4、 Standards and Publications are adopted by TIA in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This St
5、andard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its
6、 use. (From Project No. SP-3-4652.518-RV2-RF1, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no assurance that the Document will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the
7、standards development or any editing process. The use or practice of contents of this Document may involve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consist
8、ing of patents and published pending patent applications are claimed and called to TIAs attention, a statement from the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or v
9、alidity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or conditions, which are instead left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or repr
10、esent that procedures or practices suggested or provided in the Manual have been complied with as respects the Document or its contents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or
11、publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA disclaims any duty or obligation to search or inve
12、stigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Info
13、rmation as to claims of IPR in the records or publications of the other SSO shall not constitute identification to TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspe
14、ct, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATEN
15、ESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH A
16、NY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY U
17、SE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGEN
18、CE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-664.518-B 1 2 3 4 5 6 7 8 9 10 11 12 1
19、3 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 518-i Contents Wireless Features Description: Remote Feature Control Contents List of Tables.ii Revision Historyii 1 Remote Feature Control (RFC).1 1.1 Norma
20、l Procedures with Successful Outcome1 1.2 Exception Procedures or Unsuccessful Outcome .4 1.3 Alternative Procedures .5 1.4 Interactions with Other Wireless Services5 TIA-664.518-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43
21、 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 List of Tables 518-ii List of Tables Table 1: RFC Idle State2 Table 2: RFC Collect DN State2 Table 3: RFC Collect PIN State.3 Table 4: RFC Collect Feature Code State3 Table 5: RFC Collect DN State4 Table 6: RFC Collect PIN State.5 Table 7: RFC Coll
22、ect Feature Code State5 Revision History Revision Date Remarks IS-53, Revision 0 August 1991 Initial publication IS-53, Revision A May 1995 Updated publication ANSI/TIA/EIA-664, Revision 0 June 1996 Initial ANSI publication ANSI/TIA/EIA/664-518-A July 2000 Updated ANSI publication TIA-664.518-B Sept
23、ember 2007 Updated publication TIA-664.518-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 518-1 Remote Feature Control (RFC) 1 Remote Feature Control (RFC) Remote Feature Con
24、trol (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
25、 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 deactivation. RFC may be used to affect a subscribers ability to originate or receive
26、 calls through the manipulation of various features. Applicability to Telecommunications Services RFC is applicable to voice telecommunication features. 1.1 Normal Procedures with Successful Outcome Authorization RFC may be generally available or may be provided after prearrangement with the service
27、 provider. The features and operations accessible through RFC may be restricted on a per subscriber or on a per system basis. Deauthorization RFC may be withdrawn at the subscribers request or for administrative reasons. Registration The subscriber Directory Number (DN) and RFC Personal Identificati
28、on Number (PIN) are registered during authorization. The registered DN is the normal DN used to reach the subscriber (usually the subscribers MIN). The RFC PIN may be changed by the service provider at any time. Deregistration None identified. Activation RFC is activated upon authorization. TIA-664.
29、518-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Remote Feature Control (RFC) 518-2 Deactivation RFC shall be deactivated upon deauthorization. Invocation RFC is invoked wh
30、en the RFC subscriber calls the RFC access number from any mobile or landline telephone. Normal Operation with Successful Outcome RFC should prompt the subscriber through the following possible interactions: Table 1: RFC Idle State State RFC Idle The RFC is idle Condition XID Call Party Action Syste
31、m Reaction 50I An incoming call arrives for the RFC ervice. The RFC prompts the user to enter his or her N. Go to the RFC Collect DN state. s DTable 2: RFC Collect DN State State RFC Collect DN The RFC is waiting for the DN Condition XID Call Party Action System Reaction 51G 1 The calling party ente
32、rs a DN and the # digit. If the DN is accepted, optionally apply feature confirmation treatment. (For security reasons, the DN should be accepted if it at least looks like a valid DN.) The RFC prompts the user to enter his or her RFC PIN. Go to the RFC Collect PIN state. 51G 2 The calling party ente
33、rs a star or asterisk digit “ .” Clear the current number field. Go to the RFC Collect DN State *51D The calling party disconnects. Release the RFC channel. Go to the RFC Idle State. 51P The calling party exceeds a threshold ased upon the time to enter the DN. Release the RFC channel. Go to the RFC
34、Idle tate. b STIA-664.518-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 518-3 Remote Feature Control (RFC) Table 3: RFC Collect PIN State State RFC Collect PIN The RFC is wa
35、iting for the RFC PIN. Condition XID Call Party Action System Reaction 52G 1 The calling party enters his or her RFC PIN and the # digit. If the RFC PIN is accepted (in the context of the DN), optionally apply feature confirmation treatment. The RFC prompts the user to enter a feature code string. G
36、o to the RFC Collect FC state. Clear the current number field. Go to the RFC Collect PIN State 52G 2 The calling party enters a star or asterisk digit “ .” *52D The calling party disconnects. Release the RFC channel. Go to the RFC Idle State. Release the RFC channel. Go to the RFC Idle State. 52P Th
37、e calling party exceeds a threshold based upon the maximum number of RFC requests, total access time, or the ime to enter the RFC PIN. tTable 4: RFC Collect Feature Code State The RFC is waiting for a feature code. State RFC Collect FC Condition XID Call Party Action System Reaction 53G The calling
38、party enters a feature code string delimited by the # digit. If the RFC is accepted, apply feature confirmation treatment. The RFC prompts the user to enter a feature code string. Go to the RFC Collect FC state. 53D The calling party disconnects. Release the RFC channel. Go to the RFC Idle State. Re
39、lease the RFC channel. Go to the RFC Idle State. 53P The calling party exceeds a threshold based upon the maximum number of RFC requests, total amount of access ime, or time to enter a single number. tCall Detail Record The system should record call detail information for the following: a. A RFC ter
40、minating call leg to record the RFC usage. b. The feature activation call leg for each feature access attempt by the RFC. c. The affected feature registration, deregistration, activation, deactivation, invocation events, including an RFC indication. See DMH for the specific information to be include
41、d for each element. TIA-664.518-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Remote Feature Control (RFC) 518-4 1.2 Exception Procedures or Unsuccessful Outcome Registratio
42、n None identified. Deregistration None identified. Activation None identified. Deactivation None identified. Invocation The following call party action and system reactions are possible for exception processing: Table 5: RFC Collect DN State State RFC Collect DN Condition The RFC is waiting for the
43、DN XID Call Party Action System Reaction 51GX 1 The calling party enters his or her DN and the # digit. If the DN is refused, apply denial treatment. Prompt the user to reenter the DN. Go to the RFC Collect DN state. 51GX 2 The calling party enters his or her DN and the # digit. If the DN is refused
44、 too many times, apply denial treatment. Release the RFC channel. o to the RFC Idle state. GTIA-664.518-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 518-5 Remote Feature Co
45、ntrol (RFC) Table 6: RFC Collect PIN State State RFC Collect PIN Condition The RFC is waiting for the RFC PIN. XID Call Party Action System Reaction 52GX 1 The calling party enters his or her RFC PIN and the # digit. If the RFC PIN is refused, apply denial treatment. Prompt the user to reenter the R
46、FC PIN. Go to the RFC Collect PIN state. 52GX 2 The calling party enters his or her RFC PIN and the # digit. If the RFC PIN is refused too many times, apply denial treatment. Release the RFC hannel. Go to the RFC Idle state. cTable 7: RFC Collect Feature Code State State RFC Collect FC Condition The
47、 RFC is waiting for a feature code. XID Call Party Action System Reaction 53GX 1 The calling party enters a feature code string delimited by the # digit. If the dialed feature code is refused, apply denial treatment. Go to the RFC Collect FC state. 53GX 2 The calling party enters a feature code stri
48、ng delimited by the # digit. If the dialed feature codes are refused too many times, apply denial treatment. Release he RFC channel. Go to the RFC Idle state. tExceptions While Roaming None identified. Exceptions During Intersystem Handoff None identified. 1.3 Alternative Procedures None identified.
49、 1.4 Interactions with Other Wireless Services Asynchronous Data Service (ADS) Voice prompt for additional information is not supported. RFC may be used to get *FC control for the features CD, CFB, CFD, CFNA, CFU, CNIR, FA, MAH, PL, PACA, SCA, and SPINA. TIA-664.518-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Remote Feature Control (RFC) 518-6 Call Delivery (CD) None identified. Call ForwardingBusy (CFB) CFB Registration should not be allowed via RFC, as this
