hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 4.6 Recommended WTM specific data service | |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 4.6.1 General | These services allow WTM users to set up or receive Circuit switched and Packet switched data calls via mobile terminals. Calls may originate either in the home PISN or in another network(s) including calls between terminals visiting another network(s). Handover may be suppressed for Data calls, e.g., by an analysis of... |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 4.6.2 Circuit Switched Data | WTM circuit switched data services features are characterized by a set of attributes. A telecommunication service attribute is a specific characteristic of that service whose values distinguish it from other telecommunication services. Particular values are assigned in the relevant standards to each attribute when a gi... |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 4.6.3 Point-to-Point Protocol (PPP) datagram transport | The purpose of the PPP Inter-working Service is to allow dial-up Internet access and general multi-protocol datagram transport. PPP packet transfers on the air interfaces are specified by the relevant radio packet transmission protocols. Inter-working to the PISN or public ISDN networks may be via a number of bearer se... |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 4.6.4 WTM Point-to-Point Short Message Service | The WTM Point-to-Point Short Message Service (SMS) provides a mean for sending messages of limited size to and from mobile terminals as well as fixed terminals. It is anticipated that the SMS makes use of a Service Centre, that acts as a store and forward centre for the short messages. The location of the PISN Service ... |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 4.6.5 Other standards related to WTM | Ideally the users of the WTM service should not see any differences in the behaviour of the service just because of a change of location. It may, however, be a problem for the visited network to identify the WTM user and to determine the correct PISN from the WTM identity provided by the cordless terminal. This problem... |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 5 Packaging of WTM services | In order to help organizations implementing a WTM service of a specific ambition level, it is recommended to develop "profile standards" that specifies which standards that need to be implemented as well as the available options within the standards. |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 5.1 Roaming within a single PISN | |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 5.1.1 Basic call | This feature package provides a minimum service level and supports only in and outgoing call to/from a roaming Wireless Terminal that roams within the boundaries of a single PISN. Profile standards should be written for Basic Call with at least the following combinations. |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 5.1.1.1 Basic call with support of Home PINX supplementary services | Support of home PINX supplementary services may be achieved in many ways. At least the following options should be available. However, it is not recommended that more than one option be used at a time in a single PISN: a) Remote access; b) Signalling enquiry; c) Transport of Service Profile to visitor PINX; d) Predefin... |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 5.1.1.2 Handover between PINXs | Handover between PINXs within a single PISN is a service option that can be offered as an enhancement to service package Basic call with or without the support of supplementary services. |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 5.1.2 Data calls | Data calls are call unrelated services. Support of voice calls may therefore not be required in Data Terminals. However, it is expected that a voice service may be enhanced with Data calls. Handover may be offered for Data calls, but due to the possibility of breaks in the connection between the terminals and the netwo... |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 5.1.3 Short Message Service (SMS) | The Short Message Service is a call unrelated services that may be combined with voice terminals as well as Data call terminals. Handover is not considered relevant to this service as the reception of a short message always should be acknowledged by the wireless terminal. If the message is not confirmed it should be re... |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 5.2 Roaming between networks | |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 5.2.1 Basic call | This service package allows for roaming between two PISNs or between a PISN and a public network. The networks may either be directly connected or interconnected via another network (PISN or public network). Roaming into public CTM networks may imply development of inter-working functions between the identification, au... |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 5.2.1.1 Basic call with support of Home PISN supplementary services | Support of supplementary services may be achieved in many ways. At least the following options should be available: a) Remote access; b) Signalling enquiry; c) Transport of Service Profile to visitor PINX; d) Predefined service profiles. |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 5.2.1.2 Handover between PISNs | Handover between networks is a service option that can be offered as an enhancement to service package Basic call with or without the support of supplementary services. However, this service should not be given high priority. |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 5.2.2 Short Message Service (SMS) | The Short Message Service (SMS) is a call unrelated services that may be combined with voice terminals as well as Data call terminals. Handover is not considered relevant to this service as the reception of a short message always should be acknowledged by the wireless terminal. If the message is not confirmed it should... |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 5.2.3 Data calls | Data calls are call unrelated services. Support of voice may therefore not be required in Data Terminals. However, it is expected that a voice service may be enhanced with Data calls.. Handover may be offered for Data calls, but due to the possibility of breaks in the connection between the terminals and the network a ... |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 7 Interaction with ISDN supplementary services | Possible interactions with public ISDN supplementary services should be included in the relevant WTM inter networking WTM standard. |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 8 Roadmap for the development of WTM standards | WTM standards for PISNs already exist in ETSI, ECMA and ISO/IEC versions. These standards are, from a technical point of view, partly identical but not exact copies of each other. As the goal should be to have only one set of common international standards for WTM, it is suggested to adopt a new procedure for making WT... |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 8.1 Development of new WTM standards | Figure 3: Proposed workflow for new WTM standards Start Write new ECMA standard Publish ECMA standard Fast track accepted ? Issue ISO/IEC standard Update fast tracked ECMA standard End Publish revised ECMA standard. Withdraw old version Issue ETSI standard No Modifications needed ? Fast track to ISO/IEC-JTC1? ETSI stan... |
db2cdb5dce32777910df5b2264c2eca0 | 101 794 | 8.2 Proposed handling of old standards | Table 47: Handling of ETSI ‘s WTM standards on Location Registration/De-registration Standard Title Date issued Proposed action ETS 300 691 [9] ed.1 Private Integrated Services Network (PISN); Cordless Terminal Mobility (CTM); Location handling services; Service description 1996-03 To be withdrawn and replaced by endor... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 1 Scope | The present document considers the inter-operator/service provider processes required to support Number Portability, in particular, the information transfer requirements. Processes include: - service establishment (including initial contact, planning, implementation & testing); - impact upon number administration; - cu... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 3 Definitions and abbreviations | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Relinquishing Network: Network from which the number is being ported. Directory Enquiry Service Provider: Service Provider that provides alternate Directory Services to end customers. Wholesale Billing: Billing process where the 'custo... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: DIS Directory Information Systems DQ Directory Enquiry ESE Emergency Services Enterprise ISS Information Support Systems LEA Law Enforcement Agencies NO Network Operator NP Number Portability NPA Numbering Plan Administration NRA National Regu... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 4 Assumptions | Interconnect agreements are in place between involved operators, including agreed points of contact. There is an agreed timescale against which involved operators will deliver Number Portability. Each operator is responsible for ensuring that their network, and Information Support Systems, are suitably prepared to hand... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 5 Entities involved in the Porting Process | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 5.1 Distribution Chain for Porting Service | The distribution chain of the porting service contains the following roles: • customer; • Service Provider (SP); • Network Operator (NO). The assumption is made that generically speaking these roles can always be identified although these roles may not be fulfilled by separate legal entities (in practical situations so... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 5.1.1 Service Provider (SP) | Service provider is defined in [1]. Examples of service provider include a service operator/reseller in the case of Service numbers. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 5.1.2 Network Operator | Network Operator is defined in [1]. Within the NP process three "different" networks can be identified: relinquishing, recipient, and donor network. Definitions of relinquishing, recipient, and donor network can be found in [1]. The relationships between relinquishing, recipient, and donor network are also visualized i... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 5.1.3 Transit network | The transit network is defined in [1]. ETSI ETSI TR 101 698 V1.1.1 (1999-07) 10 |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 5.2 'One-stop Shop' Model | Number portability means that a customer resigns their subscription with a service provider and contracts another subscription with another service provider without changing their number. With the one-stop shop model, the customer contacts a SP of the recipient network operator. The recipient SP takes care of the porti... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6 Processes | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.1 Convention | For each process, the present document identifies what it is, why it is required, what are the information flows, and what are the escalation procedures. Note that the involved entities are considered from a functional perspective; for example, in an "Onward Routeing" implementation, the donor Service Provider would ac... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.2 Number Portability Establishment Processes | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.2.1 Number Portability Establishment Process Description | This is the process by which the Number Portability capability is implemented in the participating operators' networks and Operational Support Systems. This involves implementation of the Serving Network functionality, and of the ability to route based upon the Routeing Number. It is recommended that Verification and V... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.2.2 Rationale for the Establishment of Number Portability | This process is required because prior to Number Portability, Serving Network functionality was not required. Also there was not a requirement for use of Routeing Numbers. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.2.3 Information Flows | RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows Operator Contact Details Implementation Methodology RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows Routeing Number Plan Figure 5 Figure 6 RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows Test Numbers RECIPIENT SERVING TRANSIT DONOR ENTITIE... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.2.4 Escalation Procedures | This process is the basis upon which operators will perform Number Portability. Therefore any failure to reach agreement during this process will necessitate escalation to an appropriate regulatory, or arbitration, body. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.3 Number Portability Maintenance Processes | This subclause defines the processes required to maintain the Number Portability capability between Service Providers following completion of the Establishment process. It details new procedures and identifies links to existing interconnect procedures which should be operating as business as usual, i.e. forecasting, ro... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.3.1 Network Changes | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.3.1.1 Network Changes Process Description | This process is used when operators make changes to their networks (either internal or to Points of Interconnect) which affect the Routeing plan agreed during the Establishment process. ETSI ETSI TR 101 698 V1.1.1 (1999-07) 12 |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.3.1.2 Rationale for the Network Change Process | As operators evolve their networks to meet the ever-growing demand, network changes need to be reflected in the Number Portability Routeing plan. Examples of when such changes can occur, dependent upon the architectural solution, are: a) introduction of new numbering resource; b) movement of numbering resources within ... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.3.1.3 Information Flows | RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows Nature of Change Impact upon Routeing Plan Timing Impanct upon Capacity Forecast Figure 9 |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.3.1.4 Escalation Procedures | As these processes occur at an operational level, failure to resolve issues by operational staff will result in escalation to already identified Higher Level Interconnect Managers for resolution. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.3.2 Capacity Planning | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.3.2.1 Description of the Capacity Planning Process. | This is the process by which operators exchange information as to forecast capacity requirements between (and in certain circumstances within) networks. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.3.2.2 Rationale for the Capacity Planning Process | In certain scenarios, for example, All Call Query, this incremental process is not required above "business as usual" processes. However for implementations where the Donor Network performs some, or all of, the Serving Network functionality, these processes are required in order that the Donor Network (and Transit Netw... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.3.2.3 Information Flows | RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows Quantiity of Numbers to Be Ported RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows Volume of Calls to Ported Numbers Figure 10 Figure 11 |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.3.2.4 Escalation Procedures | As these processes occur at an operational level, failure to resolve issues by operational staff will result in escalation to already identified Higher Level Interconnect Managers for resolution. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.3.3 Customer Changes | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.3.3.1 Description of the Customer Changes Process | This is the process by which a change to the Routeing Number used to complete calls to a particular customer is registered. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.3.3.2 Rationale for the Customer Changes Process | This process is required to allow movement of customers within the recipient network. NOTE: If the implementation adopted is such that the routeing number identifies only the recipient network, or Routeing Numbers are not passed across network boundaries, this process is not required. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.3.3.3 Information Flows | RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows Nature of Change Timing of Change Figure 12 |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.3.3.4 Escalation Procedures | As these processes occur at an operational level, failure to resolve issues by operational staff will result in escalation to already identified Higher Level Interconnect Managers for resolution. ETSI ETSI TR 101 698 V1.1.1 (1999-07) 14 |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4 Number Portability Porting Processes | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.1 Sequence of Events During Porting Processes | The porting processes must be designed to minimize disruption for the customer. Therefore, the sequence of events is very important, especially for directly involved entities. In this clause, the sequence of events is explained. The flow is applicable to the Porting Process, to the Return to Donor process, and to the S... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.1.1 Administrative Phase | This phase is initiated by a customer obtaining service from the recipient service provider requesting that they retain their existing number. During this phase, the recipient service provider will have to ensure that there are no issues which will prevent the number from being ported, by co-ordinating with the relinqu... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.1.2 Preparation Phase | This phase involves the preparation of the affected networks to carry out the port of the number. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.1.3 Porting Phase | This phase is when the port of the number actually takes place. Typically, the changes in the recipient network will be activated, then the serving, donor and/or relinquishing networks will activate the relevant changes to implement the port of the number. The order of activating network changes is determined by the us... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.1.4 Case 1 | A serving network supplies a routeing number for routeing the call to the recipient exchange, or to the network termination point in the recipient network. In this case the order of notification is first recipient network then serving networks. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.1.5 Case 2 | A serving network supplies a routeing number for routeing the call to the recipient network, or a point of interconnect of the recipient network, or supplies a routeing number for routeing internal in the serving network only. In this case the order is first recipient network, then relinquishing network and finally ser... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.1.6 Information Phase | This phase informs other affected parties that the port has taken place. Typically, this will include: • organizations responsible for directory enquiry services, see subclause 6.6.1; • administrators of billing systems, see subclause 6.6.2; • regulatory bodies (e.g. Numbering Plan Administration (NPA)) where regulatio... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2 Porting Processes | There are four main types of Number Porting. These are: a) initial porting; b) subsequent porting; c) return to donor; d) customer cessation. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.1 Initial Porting Process | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.1.1 Geographic Numbers | Single Line Porting Process. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.1.2 Description of the Single Line Porting Process | This is the process by which an individual customer (single line) ports from a Donor Network to a Recipient Network. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.1.3 Rationale for the Single Line Porting Process | In order to allow customers to change their service provider whilst retaining the same ITU-T Recommendation E.164 [2] Public Telecommunication Number. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.1.4 Information flows | RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows Evidence of Customer Validation Numbers to Be Ported Timing of Port RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows Routeing Information NOTE: In certain implementations, which do not use routeing numbers, the exchange of this information may not be ... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.1.5 Non-Geographic Numbers Porting Process | Void. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.1.6 Description of the Non-Geographic Number Porting Process | This is the process by which an individual customer, with a non-geographic number, ports from a Donor Network to a Recipient Network. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.1.7 Rationale for the Non-Geographic Number Porting Process | In order to allow customers to change their non-geographic service provider whilst retaining the same ITU-T Recommendation E.164 [2] Public Telecommunication Number(s). |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.1.8 Information Flows | Where non-geographic numbers are allocated on an individual basis by a central administrative authority, there is no "donor" network, so information flows to/from donor network operators in the diagrams below should be treated as being from the relinquishing network. RECIPIENT SERVING TRANSIT DONOR ENTITIES Information... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.1.9 Escalation Procedures | As these processes occur at an operational level, failure to resolve issues by operational staff will result in escalation to already identified Higher Level Interconnect Managers for resolution. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.1.10 Subsequent Portability Process | Void. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.1.11 Description of a Subsequent Portability Process | This is the process by which an individual customer ports from a one Recipient Network to another. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.1.12 Rationale for the Subsequent Portability Process | In order to allow customers to change their service provider whilst retaining the same ITU-T Recommendation E.164 [2] Public Telecommunication Number. ETSI ETSI TR 101 698 V1.1.1 (1999-07) 19 |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.1.13 Information Flows | RELIN- QUISHING NETWORK TRANSIT DONOR RECIPIENT ENTITIES Information Flows SERVING ENTITIES Information Flows Routeing Information RELIN- QUISHING NETWORK TRANSIT DONOR RECIPIENT SERVING Evidence of Customer Validation Numbers to be Ported Timing of Port Figure 24 Figure 25 RELIN- QUISHING NETWORK SERVING TRANSIT DONOR... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.1.14 Escalation Procedure | As these processes occur at an operational level, failure to resolve issues by operational staff will result in escalation to already identified Higher Level Interconnect Managers for resolution. Note on Initial porting vs. Subsequent Portability Process. The only difference between the Initial Porting Process and the ... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.2 Void | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.3 Return to Donor Process | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.3.1 Description of the return to Donor Process | This is the process by which an individual customer returns to the Donor Network that originally served them. NOTE: This is only relevant where numbers are assigned in ranges to operators. ETSI ETSI TR 101 698 V1.1.1 (1999-07) 20 |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.3.2 Rationale for the return to Donor Process | In order to allow customers to change their service provider whilst retaining the same ITU-T Recommendation E.164 [2] Public Telecommunication Number. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.3.3 Information Flows | RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows Evidence of Customer Validation Numbers to be Ported Timing of Return RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows Confirmation of Readiness to Port Figure 27 Figure 28 |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.3.4 Escalation Procedures | As these processes occur at an operational level, failure to resolve issues by operational staff will result in escalation to already identified Higher Level Interconnect Managers for resolution. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.4 Customer Cessation Process | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.4.1 Description of the Customer Cessation Process | This is the process by which a number is returned to the Donor network following a ported customer ceasing service. NOTE: This is only relevant where numbers are assigned in ranges to operators. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.4.2 Rationale for the Customer Cessation Process | In many regulatory environments, a condition is placed that ported numbers should revert to the Donor if the customer ceases to take service. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.4.3 Information Flows | RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows Evidence of Customer Validation Numbers to be Ported Timing of Return RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows Confirmation of Readiness to Port Figure 29 Figure 30 ETSI ETSI TR 101 698 V1.1.1 (1999-07) 21 |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.4.2.4.4 Escalation Procedures | As these processes occur at an operational level, failure to resolve issues by operational staff will result in escalation to already identified Higher Level Interconnect Managers for resolution. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.5 Number Portability Fault Handling Processes | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.5.1 Fault Identified During Porting | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.5.1.1 Description of the "Fault Identified During Porting" Processes | These processes encapsulate the fault handling procedures to be used if a port is unsuccessful. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.5.1.2 Rationale for the "Fault Identified During Porting" Processes | These processes are required to assure that a seamless service is provided to customers. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.5.1.3 Information Flows | SCENARIO DIALOGUE TO ENABLE PROGRESSION OF FAULT-HANDLING BETWEEN OPERATORS Recipient Network identifies port has failed Recipient notifies donor, attempt made to rectify fault. If unsuccessful, is put on hold until fault is rectified, or cancelled by recipient. Donor or Serving Network identifies Port has failed Donor... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.5.2 Fault identified after porting | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.5.2.1 Description of the 'Fault Identified After Porting' process | These processes encapsulate the fault handling procedures to be used if a fault subsequently develops on the routeing of calls to a ported number. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.