hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 6.8.4.1 Continuous Rate Assignment | Continuous Rate Assignment (CRA) is recommended implemented as follows: • It is allocated as a static rate, hence it is not subject to the dynamic requests as defined in [i.2]. • It is allocated in full every superframe, whether the RCST has traffic to transmit or not. • The indicated rate is in given in burst payload ... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 6.8.4.2 Rate-Based Dynamic Capacity | Rate Based Dynamic Capacity (RBDC) is recommended implemented as follows: • Requests are made in units of 2 or 32 kbit/s depending on the applied scaling factor as defined in [i.2]. It is similar to CRA, but dynamic in nature (based on requests). • The requested rate is given in burst payload bit/s (considering ATM and... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 6.8.4.3 Volume-Based Dynamic Capacity | Volume Based Dynamic Capacity (VBDC) is recommended implemented as follows: • VBDC requests are made in units of a single-payload-unit (one ATM cell or one MPEG PES packet) or units of 16-payload-units units depending on the scaling factor, as defined in [i.2]. • VBDC requests are cumulative per RC ("Cumulative" means ... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 6.8.4.4 Absolute Volume Based Dynamic Capacity | Absolute VBDC (AVBDC) is recommended implemented as follows: • AVBDC requests are absolute and, when received at NCC, invalidate previous A/VBDC requests issued by the RCST for the same RC, as defined in [i.2]. • AVBDC requested volume relates to the VBDC component of the buffer of the respective RC at the RCST. RCST m... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 6.9 Queuing and packet dispatching strategy | The RCST will be capable of buffering traffic arriving from the user interface before submission to the satellite link. An RCST may support QoS differentiation in order to provide high quality for simultaneous heterogeneous services. One option is then to implement DS-compliant QoS differentiation according to the IETF... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 6.9.1 Guidelines for DS-compliant queueing and dispatching | The RCST will be capable of recognizing BA's by the applied DSCP value. A BA may also exclusively apply internally for a DVB-RCS network without any externally visible DSCP tagging of the associated IP packets, depending on the classification capabilites of the RCST, and by this the specific DVB-RCS system appears itse... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 6.9.2 A two-stage traffic queueing DS architecture | An RCST QoS architecture, based on the DS framework, is illustrated in figure 6.11. ETSI ETSI TR 101 790 V1.4.1 (2009-07) 54 Capacity Requests Capacity Assignment (TBTP) Transmit data AF Scheduler MAC (ATM) Layer Service Layer IP Traffic Classifier/Conditioner & Router & Queue Manager IP Queues MAC Request Class Buffer... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 6.10 Guidelines for the requesting strategy | Implementation specific request strategies apply. It is system dependent which capacity categories that apply fore each RC. RBDC might be useful e.g. for delay jitter sensitive traffic (like VoIP) and A/VBDC might be useful e.g. for more efficiency sensitive traffic (like best effort). An NCC BoD controller may allow b... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 6.10.1 BoD queue synchronization method | This clause proposes a specific technique for using AVBDC capacity requests to maintain BoD queue synchronization between RCST and hub in the presence of transmission losses in forward and return MAC signalling. An AVBDC request transmitted in an arbitrary superframe S, AVBDCS, can for example be calculated as: AVBDCS ... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 6.11 Assignment/allocation | The NCC may relate a request for resources for a specific RC aggregate to an associated appropriate assignment/allocation policy, through the association with a specific Channel_ID. The NCC may also utilise the different capacity categories through differentiated authorization and application of capacity category speci... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 6.12 Procedure for contention resolution | When capacity requests (CR) are sent in contention slots (CS), there is a definite chance of a collision, which typically results in the capacity request being lost. In such situations, the RCST will want to reissue its capacity request. Mini-slot contention resolution by retransmission based on feedback is not recomme... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 7 Synchronization procedures | |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 7.1 Overall events sequencing | Terminals should know what the initial power level is that they can use when entering the network. The knowledge about this power level should be gathered during the installation procedure. Terminals will keep the information about this power level. In the typical RCST design, the IDU will use the corresponding IF leve... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 7.2 Initial synchronization procedure | The corresponding clause in the normative document [i.2] contains a description of the initial synchronization procedure. |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 7.3 Logon procedure | The normative document [i.2] defines the logon procedure by a flow chart. Parameters for the procedure are given by the Contention Control descriptor. The flow chart given in figure 7.1 is copied from the one of the normative document [i.2], but expresses parameters by the field names of the descriptor. ETSI ETSI TR 10... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 7.3.1 Multiple correction message descriptors in TIM | An NCC may provide multiple CM descriptors with timing corrections in a single unicast TIM, in order to achieve both the required acquisition range and the required precision by use of a single TIM. The RCST is then expected to perform all the given timing corrections. Each timing correction is to be scaled with its co... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 7.4 Coarse synchronization procedure (optional) | The corresponding clause in the normative document [i.2] contains a description of the coarse synchronization procedure. An RCST that indicates in the CSC burst that it does not require to send an ACQ burst should not be expected to send the ACQ burst. An RCST that indicates it requires to send an ACQ burst may or may ... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 7.5 Fine synchronization procedure (optional) | The corresponding clause in the normative document [i.2] contains a description of the fine synchronization procedure. The fine synch procedure is considered mandatory for the RCST and optional for the NCC. The burst _time_scaling value of the Correction Message descriptor should be applied for the SYNC Assign descript... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 7.6 Synchronization maintenance procedure | The corresponding clause in the normative document [i.2] contains a description of the synchronization maintenance procedure. The RCST should scale the burst_time_correction value given in CMT according to the burst_time_ scaling value related to the RCST by the same CMT. Despite what is indicated in [i.2] for the thre... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 7.7 Logoff procedure | Typical values for the triggers of abnormal log-off as defined in the corresponding clause of [i.2] may be: • NCR not received for a period of 6 seconds. • CMT burst correction not received for 3 consecutive SYNCs. |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8 Control and management | For optional Type B RCSTs, if capacity request mechanisms can be in conflict with ATM features, then these mechanisms can be disabled by the NCC and not used on the satellite network. |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.1 Protocol stack | |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.1.1 Transparent system | The protocol stack for a transparent system is described in [i.2]. |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.1.2 Regenerative system | In case of fully-regenerative RSMS (OBP with/without on board switching), the on board processor will provide data de-capsulation of the uplink streams, followed by encapsulation and frame formatting into downlink transport streams, which are identical to DVB-RCS forward link streams (see also table 4.1). |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.2 RCST addressing | The Group_ID is probably the same on two consecutive sessions. ETSI ETSI TR 101 790 V1.4.1 (2009-07) 59 Group_ID: The Group_ID was introduced to reduce the signalling load on the forward link. A unique TBTP is applicable to a group of terminals. The network operator may perform Group_ID grouping based on the subscriber... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.3 Forward link signalling | Note that if the NCC calculates time offset due to RCST-to-satellite range the SPT need not be transmitted. The accessing of the forward link signalling is described in clause 8.5.5.11 in EN 301 790 [i.2]. It is recommended to refer to figure 35 of EN 301 790 [i.2] when reading the extra explanations that are provided ... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.3.1 Repetition rates | The normative document [i.2] indicated that the TBTP will be updated every superframe, or equivalently, for each increment of the "superframe_count" parameter. When the superframe duration is long (its definition allows superframes to be as long as 93,2 s), an update rate of once per superframe would lead to unacceptab... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.3.2 DVB RCS SI table updates | An update of the RCS SI tables is indicated by the use of the current_next_indicator and version_number fields of the SI section header. The Table Update Descriptor may be used to inform the RCST that there is an upcoming change to one of these tables. For the SI tables used for frame composition, SCT, FCT and TCT, the... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.3.3 Logon response TIM | The logon response TIM will contain at least a Correction_message_descriptor, a Logon_initialize_descriptor, a SYNC_assign_descriptor and a Satellite_return_link_descriptor, according to [i.2]. It is recommended that this TIM provides also the Correction_control_descriptor, so that the coarse sync control loop and the ... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.3.4 Multicast Mapping Table | Implementations may support IP multicast in the TS by providing the identification of the elementary streams for different multicast groups through a custom table broadcasted by the NCC, called the Multicast Mapping Table. |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.3.4.1 MMT for MPE | A format for the MMT has been recommended by SatLabs in [i.52], and the recommended format is included here. The Multicast Mapping Table identifies the elementary streams used to transport specific multicast traffic. It uses the same SI table format as other RCS tables specified in [i.2]. The Multicast PID Mapping Tabl... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.3.4.2 MMT for VC-MUX | Implementations may support IP multicast on links using ATM formatting by providing the identification of the VCC for different multicast groups through a custom table broadcasted by the NCC, called the Multicast Mapping Table. The Multicast Mapping Table identifies the elementary streams used to transport specific mul... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.3.5 Other FL messages for network management (optional) | A design that provides additional functionality with SNMP can be found in clause 8.6. |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.4 Return Link Signalling | The return link signalling specified in [i.2] serves these four functional groups: • System logon and burst synch acquisition. • Maintenance of burst synchronisation. • Unit control and management. • Resource control. |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.4.1 Typically use of Return Link Signalling | It is highly recommended that both the RCST and the GW supports signaling in the regularly assigned dedicated synch slots that are allocated for synch maintenance. It is highly recommended that both the RCST and the GW supports signalling in TRF slots, for the ATM mode as well as the MPEG mode as applicable, as this is... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.4.2 On board processing of Return Link Signalling | In fully regenerative RSMS (OBP with/without on board switching), the onboard processor will provide some functions which would be otherwise provided by the NCC. Therefore, the OBP has an active role in the return link synchronization procedure and link control and monitoring. In particular the following control and ma... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.4.3 Other RL messages for network management (optional) | A design that provides additional functionality with SNMP can be found in clause 8.6. An RCST may support signalling of a Route_ID as specified in [i.2]. The use of the Route_ID is considered optional and system dependent. ETSI ETSI TR 101 790 V1.4.1 (2009-07) 64 |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.5 Coding of SI for forward link signalling | |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.5.1 Table definition | The TBTP should be transmitted in the proper order (consecutive frames are sent one after each other). TBTP should not be sent fragmented (for example a part of frame n, then a part of frame m, then again a part of frame n and so on). |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.5.1.1 Timeslot Composition Table (TCT) | Preamble_Length: For the CSC, SYNC and TRF bursts, this parameter is used to communicate unambiguously the length of the preamble sequence that precedes the encoded information bits. When used with the ACQ burst, however, this parameter indicates the combined length in symbols of both the preamble and the special frequ... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.5.1.2 Terminal Burst Time Plan (TBTP) | The assignment_type field is used to specify the type of allocation which is granted to the RCST. In most networks, RCSTs transmit in all assigned time slots, even when they have no actual traffic to send. Some networks may prefer that RCST's generally do not transmit in this case. In these systems, the reserved value ... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.5.2 DSM-CC Private Section Header | The DSM-CC section is specified in [i.51]. A DSM-CC section can contain private data, and [i.34] specifies that this private data can be used to transport MPE, using a specific header extension. TIM is specified in [i.2] as a specialized type of the private sections specified in [i.50], and a header extension is specif... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 8.6 SNMP (optional) | It is recommended that the RCST supports SNMP/UDP/IP on its Satellite and Ethernet interfaces and act as an SNMP agent/client. The RCST should support SNMPv2c as specified in [i.25] and [i.19]. ETSI ETSI TR 101 790 V1.4.1 (2009-07) 65 It is recommended that the following MIB modules are implemented: 1) MIB-II [i.56]. 2... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 9 Security, identity and encryption | Clause 9.4 of the normative document [i.2] describes an optional security mechanism, which provides link layer security. An example for a security and authentication concept, which takes into account the common practice in the Internet environment, can be found in annex G. An example of end user authentication using RA... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10 RCST implementation guidelines | |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10.1 Architecture | The RCST does typically comply with the architecture outlined in figure 10.1. An RCST may conceptually consist of the Outdoor Unit (ODU), the Interfacility-Link (IFL), and the Indoor Unit (IDU). The ODU is composed of the following subsystems: Antenna Subsystem (ANT), Transceiver (TRx), and Mechanical Subsystem (MECH).... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10.2 System performance | |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10.2.1 RF/IF performance | The RF parameters have been selected to comply with the conditions identified in the ERC decisions related to Exemption from Individual Licensing of Satellite User Terminals (SUTs), Satellite Interactive Terminals (SIT) and Very Small Aperture Terminal (VSAT). These ERC decisions make reference to the Harmonized Standa... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10.2.2 Code performance in an AWGN channel | The code performance given here below is related to the case where the coder and decoder simulation models are placed back to back (in baseband) together with an additive white Gaussian noise (AWGN) channel. Neither the satellite channel nor the RF impairments are considered. The indicated values do not include any all... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10.2.2.1 Concatenated coding performance | Table 10.2 provides examples of indicative values of the performance achievable with the concatenated coding. The values are applicable to a system that employs soft-in/hard-out Viterbi decoding of the inner code, with 3-bit input soft decisions, and an algebraic decoder of the outer code. The term Eb/N0 refers to the ... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10.2.2.2 Turbo code performance | The performance given below can be achieved with 4-bit quantization, 6 iterations and a SUB-MAP decoding algorithm. Further gain can be achieved by increasing the number of iterations at the expense of reduced information bit rate, at constant system clock. For the 16 bytes case, the performance is given without applyi... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10.3 Interfaces | This clause describes bi-directional communications used in the IDU/ODU Inter-Facility Link (IFL). Other ways of implementing this interface than described here are possible. Performance figures in this clause are not necessarily optimized in terms of the requirements of the normative document [i.2] for all potential i... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10.3.1 RX IFL | The RX IF system interfaces between LNB and IDU. The definition is directly derived from the ETS 300 784 [i.59] and EN 61319-1 for "Universal" DBS/DTH terminals [i.12]. Table 10.5 shows the IFL parameters. ETSI ETSI TR 101 790 V1.4.1 (2009-07) 70 Table 10.5: IFL parameters Parameter Value Unit Note Frequency scheme no ... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10.3.2 TX IFL | The TX IFL system interfaces between IDU and BUC. A single coaxial cable typically carries: • The TX IF signal in L-band. • The TX LO frequency reference signal. • A low frequency sub-carrier for DiSEqC™ signaling. • The DC power supplying the BUC. In general L-band is recommended for all RCS terminals according to fol... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10.3.3 ODU control signal | DiSEqCTM IFL signalling between IDU and BUC enables a number of advanced applications and features. The signalling from IDU to ODU can be implemented by on/off voltage modulation, shown in table 10.10. Table 10.10: IFL signals Parameter Value Unit Note Carrier frequency 22 ± 4 kHz acc. EN 61319-1 [i.12] Modulation type... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10.3.3.1 Concept of the 22 kHz Pulse Width Keying (PWK) Bus | The low data rate communication between the IDU and the ODU is based on a 22 kHz PWK signal as used by DiSEqCTM [i.18]. The impedance of the bus at 22 kHz should be 15 Ω. A parallel inductor of 270 μH can be used to support a DC. power supply current. In this case a capacitor to ground should be supplied to shape the 2... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10.3.4 Control functions from the IDU | The following functions should be available: • SSPA ON/OFF (relates to disabled state as described in EN 301 459 [i.8]). • Tx Unit power off. The following functions may be available: • Frequency tuning within the wide frequency range of the slow frequency agility (if applicable). • Software update of the ODU. • Tx Fre... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10.3.5 Monitoring functions (from ODU on request) | The following functions should be available: • SSPA ON/OFF status. • Phase lock oscillator status. • Power supply status. • Device status. • EUI-64 of the ODU. ETSI ETSI TR 101 790 V1.4.1 (2009-07) 75 NOTE: EUI-64 is a trademark of IEEE, it is intended to identify a single unique device independent of its functionality... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10.3.6 Control and Monitoring protocol description | The protocol description is provided in annex B. |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10.4 ODU environmental conditions | |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10.4.1 Operational environment | There should be no significant degradation of the specified system and subsystem performance when operating under the following environmental conditions: • Temperature: -30 °C to +50 °C. • Solar Radiation: 500 W/m2 max. • Humidity: 0 % to 100 % (condensing). • Rain: up to 40 mm/h. • Wind: up to 45 km/h. The ODU mechani... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 10.4.2 Survival conditions | The ODU is allowed to degrade in performance, but should maintain pointing accuracy and suffer no permanent degradation under the following environmental conditions: • Temperature: -40 °C to +60 °C. • Solar Radiation: 1 000 W/m2. • Humidity: 0 % to 100 % (condensing). • Precipitation: up to 100 mm/h of rain or 12 mm/h ... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 11 User network guidelines | |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 11.1 RCST interaction with cable and non-transparent SMATV | This clause describes a possible design for the interaction of the RCST with cable networks or non-transparent SMATV installations. Figure11.1 depicts an example of such an interaction. An RCST is connected to the head-end of a cable system via an IP network (typically Ethernet). At the end-user's premises, the cable n... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 11.2 Transparent SMATV | This clause describes the implementation of very cost effective solutions matched to the SMATV interactive networks. Transparent SMATV means: no transmodulation for the forward signals, nor for the return signals; the same modulation is carried through the whole SMATV network. ETSI ETSI TR 101 790 V1.4.1 (2009-07) 77 T... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 11.2.1 Interactive "one cable" SMATV-IF installation | This type of installation is shown schematically in figure 11.2. Most of those installations are already installed with passive components (splitter and tap-off) working from 5 MHz to 2 150 MHz. To up-grade such an installation for satellite interactivity, it suffices to replace the existing dish by an ODU and to add a... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 11.2.2 Interactive "multiswitches equipped" SMATV-IF installation | Two main types of multiswitches are used for those installations: with and without built-in 5 MHz to 65 MHz return path. The installation using the first type (built-in return path) is shown in figure 11.4. To up-grade such an installation for satellite interactivity, the existing dish could be replaced by an ODU, and ... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 11.3 RCST interaction with local area networks | This clause describes the interworking between a RCST and a Local Area Network (LAN). An RCST has to include an interface to the user network. The complexity of this interface depends on what kind of technology is used in the LAN. Figure 11.5 shows the general system. RCST ODU RCST IDU/LAN Interface Generic computer Ge... |
d1b2bee55ecd2d18f12cc06899493bcb | 101 790 | 11.4 RCST interaction with In-Home Digital Network | The DVB Home Local Network specification [i.17] defines how to implement an IEEE 1394 [i.63] based home network in conjunction with DVB distribution and interaction networks. In conjunction with DVB-RCS the RCST is part of a residential gateway. ETSI ETSI TR 101 790 V1.4.1 (2009-07) 85 Annex A: Examples of incorporatio... |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 1 Scope | The present document is to analyse the interrelationships of the various technical components involved in providing service provider number portability and provide guidance on use in Europe between networks. NOTE: For the purpose of the present document, the term "Service Provider Number Portability" is used to describ... |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 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... |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACQ All Call Query Ccat Concatenated DB DropBack Exch Recipient exchange IN Intelligent Network NA Network Aspects NPTF Number Portability Task Force NTP Network Termination Point None No routeing number used OR Onward Routeing POI-NNet Point ... |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 4 Possible Number Portability Solutions | Contained within the three technical reports detailed in clause 2, there are three technical components that are to be included in any solution (application) for service provider number portability: 1) the architecture being used; 2) the method of transporting a routeing number; 3) the entity addressed by the routeing ... |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 5 Appropriateness of Number Portability solutions | Although the previous clause identified a number of options for choice of architecture, transportation of the routeing number and entity to be addressed by the routeing number, there are a number of these possibilities which are either completely inappropriate, or appropriate only under certain circumstances. This clau... |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 5.1 Architecture | None of the architectures identified are impracticable; however, the options could be viewed as more or less appropriate dependant upon whether a short or long term solution is being devised. Onward Routeing is best considered as a short to medium term solution, as it can be implemented relatively quickly using existin... |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 5.2 Transportation of the Routeing Number | Four options have been identified, including not transporting any routeing number. Concatenating the routeing number with the destination number is seen as a good short term solution, as it may require little or no development to signalling systems. Some form of indication that the contents of the signalling field is a... |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 5.3 Entity addressed by Routeing Number | Six options have been identified for the entity to be addressed by the routeing number, including not actually having a routeing number. In carrying out this analysis, it is important to recognize that what is being considered is the Routeing Number used at network interfaces, not that used internally to a network. Add... |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 5.4 Further Considerations | Based on the above discussion, several of the possible technical parameters are not recommended. Removing these options from consideration leaves a matrix of: - four architectures (OR, ACQ, QoR, & DB); - three means of transporting routeing numbers (Ccat, Sep, & None); - four entities to be addressed by routeing number... |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 6 Number portability options that should not be used | TR 101 119 [1] pointed out that there are many parameters to be considered in the selection of the best solution for implementing number portability. These factors include technical, service, cost, efficiency and administrative issues. The present document is unable to look at all of these issues, but does focus on the... |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 6.1 Routeing Number identifies something when it is not carried | If the routeing number is said to identify something, but is not being carried, then the implementation cannot exist. It therefore follows that some options are not possible; 3, 6, 9, 15 18, 21, 27, 30, 33, 39, 42, 45. |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 6.2 Routeing Number doesn't identify anything but is carried | If the routeing number is said not to identify anything, there is no point in carrying it. It therefore means that the following options are implausible; 10, 11, 22, 23, 34, 35, 46, 47. ETSI 9 ETSI TR 101 697 V1.1.1 (1999-07) |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 6.3 Information sent back by Donor network is to be consistent | It would not be practicable for the donor network utilizing dropback type techniques to return a different value of Routeing Number dependent upon the originating exchange. It therefore follows that the combination of drop back with PoI is not valid, ruling out the options; 40, 41. Similarly, as drop back sends a route... |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 6.5 Donor exchange (network) should only respond once - QoR | It is our view that the donor network should only need to respond once during a call set up to indicate that a number is ported. All addressing options that involve additional QoR set up sequences to the donor network should be eliminated from further consideration when QoR is the method used. This would eliminate Reci... |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 7 Combined Number Portability solutions | While clause 6 deals with options where only one type of architecture is used, it is also possible to combine different architectures. The number of possible options is quite large, hence we have not attempted to list them all, only the combined solutions that are considered plausible. |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 7.1 Explanation of combined solutions | In the cases where the routeing number addresses the recipient network, or the routeing number is only used for network-internal routeing (the routeing number is not passed across the network boundary), multiple networks carry out a database query to route a call to a ported number. NOTE 1: If the routeing number ident... |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 7.2 Plausible combined Number Portability solutions | As a variant of a two or multi-stage ACQ solution, the first stage could be replaced by a query on release. This means a combined solution where the first stage uses query on release. As for all two-stage and multi-stage solutions subsequent stage(s) use ACQ. NOTE: This ACQ can be performed network internal using QoR t... |
dbe44a9b2b444bf2ca0d464a46baa0e1 | 101 697 | 8 Conclusion | It has been shown that a multitude of solutions can be implemented for service provider number portability, based around the architecture for deriving the routeing number, the carriage of the routeing number, and the entity that the routeing number addresses. However, where a single architecture is used, only thirteen ... |
a34988f69711a1482d1521f3ced6fd66 | 101 665 | 1 Scope | The present document is a first study on service capability modelling for IN CS-4. Clause 4 identifies the requirements for IN service modelling. Clause 5 lists some shortcomings of using IN CS-2 SIBs for IN service modelling. Clause 6 explains the rationale for applying object oriented techniques, followed by the intr... |
a34988f69711a1482d1521f3ced6fd66 | 101 665 | 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... |
a34988f69711a1482d1521f3ced6fd66 | 101 665 | 3 Definitions and abbreviations | |
a34988f69711a1482d1521f3ced6fd66 | 101 665 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply. methodology: systematic working procedure consisting of a set of clearly defined steps and their relation. In each step of the methodology one or more modelling techniques can be used to carry out the activities described by that step ... |
a34988f69711a1482d1521f3ced6fd66 | 101 665 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AccCOs Accounting Computational Objects API ApplicationProgramming Interface ASN.1 Abstract Syntax Notation No.1 BCSM Basic Call State Model B-ISDN Broadband ISDN CM Connection Management CNPs & ANPs Core and Access NPs ConS Connectivity Servi... |
a34988f69711a1482d1521f3ced6fd66 | 101 665 | 4 Requirements for IN CS-4 Service Modelling | Requirements that have been identified as important for modelling techniques and methodologies used for IN service modelling are: - stepwise refinement from service (features) to protocol level should be supported; - support for various mechanisms of transparency. These include: - technology transparency: - the modelli... |
a34988f69711a1482d1521f3ced6fd66 | 101 665 | 5 Shortcomings of IN CS-2 SIB approach | This clause describes the major shortcomings that have been identified for the IN CS-2 SIB approach (see ITU–T Recommendation Q.1223 [3]): - the Service Independent Building blocks (SIBs) at Global Functional Plane (GFP) is hard to refine to a Distributed Functional Plane (DFP) level; - the refinement of the Service Pl... |
a34988f69711a1482d1521f3ced6fd66 | 101 665 | 7 Methodologies and modelling techniques | Subclauses 7.1 and 7.2 introduce ODP and UML as general methodologies/modelling techniques for service modelling. Subclause 7.3 introduces TINA as a possible approach for service modelling based on ODP and UML principles. |
a34988f69711a1482d1521f3ced6fd66 | 101 665 | 7.1 Open Distributed Processing (ODP) | |
a34988f69711a1482d1521f3ced6fd66 | 101 665 | 7.1.1 Introduction to ODP | The reference model of ODP is a generic distributed object-oriented methodology that is suitable for both traditional telecommunications applications (such as IN) and information processing applications. It is based on two powerful trends in software technology: - object-oriented specification techniques provided at di... |
a34988f69711a1482d1521f3ced6fd66 | 101 665 | 7.1.2 Evaluation of ODP | The benefits of ODP for IN service modelling include: - stepwise refinement of specifications: shows some possible scenarios of specification refinement in ODP. Note that specification refinement and transformations can be made in an iterative manner; enterprise specification technology specification engineering specif... |
a34988f69711a1482d1521f3ced6fd66 | 101 665 | 7.2 Unified Modelling Language | |
a34988f69711a1482d1521f3ced6fd66 | 101 665 | 7.2.1 Introduction to UML | The Unified Modeling Language (UML) (see UML, www.omg.org), a de facto standard from OMG, is a further development and merging of Booch, OMT, and OOSE. The result is a single, widely recognized modelling language for users of these and other methods. UML provides a standard modelling language, not a standard process. E... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.