hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.5.2.2 Rationale for the 'Fault Identified After Porting' Process | These processes are required to assure that a seamless service is maintained for customers. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.5.2.3 Information Flows | SCENARIO DIALOGUE TO ENABLE PROGRESSION OF FAULT-HANDLING BETWEEN OPERATORS Imported Customer making outgoing call Recipient - Called customer's operator Incoming call to imported number: From a recipient customer Recipient – Serving Incoming call to imported number: From a donor customer Donor - Recipient – Donor (Don... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.5.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.6 Number Portability Ancillary Processes | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.1 Directory Enquiry | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.1.1 Description of the Directory Enquiry Process | This is the process by which it is ensured that a customer continues to have an appropriate entry in Directory Information Systems. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.1.2 Rationale for the Directory Enquiry Process | These processes are required to ensure that customers who have ported maintain a comparable DQ service as those who have not, irrespective of serving operator and DQ supplier. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.1.3 Information Flows | RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows Number/ Customer Information DQ Appropriate Service Level DQSP Figure 31 |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.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. NOTE: In some regulatory environments this process may not apply. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.2 Billing | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.2.1 Description for the Billing Process | These processes encapsulate wholesale billing for the porting of customers and, if applicable, for routeing of calls to ported customers. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.2.2 Rationale for the Billing Process | The Regulatory regime may allow donor operators to make a charge to recipient operators for the porting process, and additionally may allow operators providing serving network functionality to make a per-call charge (and possible per-call attempt charge) for the provision thereof. Processes may therefore be required to... |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.2.3 Information Flows | RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows NumbeR if Customers Port Traffic to Ported customersl Figure 32 |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.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.6.3 Numbering Plan Administration | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.3.1 Description of the Numbering Plan Administration process | This is the process which ensures that the NPA continues to have correct information about the numbering plan after introduction of number portability. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.3.2 Rationale for the Numbering Plan Administration process | These processes are required so that the NPA always has the correct status of the numbering plan. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.3.3 Information flows | RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows NPA ported number, donor and recipient operator and time for porting. Figure 33 |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.3.4 Escalation procedures | In some countries this requirement is required by regulation from the NRA. ETSI ETSI TR 101 698 V1.1.1 (1999-07) 24 |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.4 Public Emergency Services | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.4.1 Description of the process for the public emergency services | This is the process which ensures that the ESE continues to have correct information about ported number for the purpose of emergency calls after introduction of number portability. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.4.2 Rationale for the public emergency services process | These processes are required so that the ESE always has the correct status of subscribers (ported and non-ported) that use the public emergency services. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.4.3 Information flows | RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows ESE ported number, donor and recipient operator and time for porting. Figure 34 |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.4.4 Escalation procedures | In some countries this requirement is required by law or regulation. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.5 Law Enforcement Agencies | |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.5.1 Description of the process for the Law Enforcement Agencies | This is the process which ensures that the LEA continues to have correct information about ported number that for the moment is under lawful interception after introduction of number portability. |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.5.2 Rationale for the Law Enforcement Agencies Process | These processes are required so that the LEA always has the correct status of subscribers (ported and non-ported) that for the time being is under lawful interception. ETSI ETSI TR 101 698 V1.1.1 (1999-07) 25 |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.5.3 Information flows | RECIPIENT SERVING TRANSIT DONOR ENTITIES Information Flows LEA ported number, donor and recipient operator and time for porting. Figure 35 |
6fe43eb2c1f7a376d19b813f41bcfd8a | 101 698 | 6.6.5.4 Escalation procedures | In some countries this requirement is required by law or regulation. ETSI ETSI TR 101 698 V1.1.1 (1999-07) 26 History Document history V1.1.1 July 1999 Publication ISBN 2-7437-3214-8 Dépôt légal : Juillet 1999 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 1 Scope | ........................................................................................................................................................5 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 2 References | ................................................................................................................................................5 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 3 Abbreviations | ...........................................................................................................................................5 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 4 Introduction | ..............................................................................................................................................6 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 5 Services | ....................................................................................................................................................7 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 5.1 Broadband Multimedia Services | ..............................................................................................................................8 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 5.1.1 Video On demand | ...............................................................................................................................................9 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 5.1.2 Broad Band TV | ..................................................................................................................................................9 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 5.1.3 Video Conference | .............................................................................................................................................10 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 5.1.3.1 Communication configuration | ..........................................................................................................................10 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 5.1.3.2 Examples of Applications | .................................................................................................................................10 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 5.2 Internet based services | ...........................................................................................................................................10 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 5.2.1 Web based services | ..........................................................................................................................................11 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 5.3 Other Services | ........................................................................................................................................................11 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 5.3.1 Voice Calling Card service | ...............................................................................................................................11 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 6 Resources | ...............................................................................................................................................11 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 6.1 Speaker Verification | ..............................................................................................................................................12 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 7 The SRF model | ......................................................................................................................................12 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 7.1 Data Manipulation in the SRF | ................................................................................................................................12 |
7e3a927a278d83981acfcd06d9fd6888 | 101 779 | 8 The SRF Service Creation Environment | ................................................................................................13 Bibliography.....................................................................................................................................................15 History..................................................... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 1 Scope | The scope of the present document is to provide information for the design of the system architecture of a "third generation" Universal Mobile Telecommunication System (UMTS) evolving from fixed networks. The present document focuses on the evolved fixed network and considers cordless access systems, wire-line access s... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 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... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ABR Available Bit Rate AC Authentication Center ADDS Application Data Delivery Service AMF Authentication Management Function AMSC Anchor Mobile Switching Center API Application Programming Interface ARF Access link Relay Function BC Bearer Co... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 4 Introduction to ISDN-UMTS Framework | The term "ISDN-UMTS" indicates a variant of UMTS that evolves from (B-)ISDN based networks for support of UMTS service capabilities. It includes the UMTS core network, UMTS application servers, the UMTS radio subsystem and second generation radio subsystems. All these subsystems form part of the GMM standardization fra... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 5 Overall requirements | |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 5.1 Service requirements | Most telecom services (teleservices, bearer and supplementary services and also applications) that the user will wish to employ will initially be those he has already used on fixed networks, either at home or in the office. However, there will be some services which have specific relevance to mobility (such as location... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 5.2 System and business requirements | UMTS is planned to be provided on the basis of service capabilities (tools) rather than detailed specified service definitions (as previously within digital cellular and ISDN). These would be supported by the Virtual Home Environment (VHE) which allows the user his own service profiles (based on these tools) and his ow... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 5.3 Architecture and protocol requirements | Architecture and protocol requirements need to be developed to support the service requirements. It is expected that separate specificationswill be developed for Call Control from and for Location/Mobility management and Service Control. Interfaces between these should be open. These functions will be required not only... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 5.4 Network infrastructures | A requirement for UMTS support over differing access and core infrastructure implies that the interconnection and service compatibility of supporting infrastructure is to be considered. This requires a common control mechanism and a set of functions to support services to allow network-independent interworking. Access ... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 5.5 Roaming and handover between mobile systems | The future set of mobile systems may include both UMTS systems and non UMTS systems. Such a system, figure 5-2, might include UMTS cellular, UMTS satellite, GSM, ISDN cordless (e.g. CTM), packet data networks, Internet services and B-ISDN high bit rate networks. Even, within the same mobile system, different base stati... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 5.6 UMTS system capabilities | Table 5-2: UMTS system capabilities System Capability UMTS Target System Location management Support for automatic location management for single and multiple registrations on a single terminal. Support of multi-mode terminals. Roaming Roaming between UMTS and other 2nd and 3rd generation systems. Support of mobility s... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 6 Service perspectives | |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 6.1 UMTS role models | GSM operator requirements for third generation trading relations are contained in GSM MoU TG.25 and are reproduced below. Such role model issues fall outside of the scope of the UMTS Task Force and therefore this model is reproduced for information and does not necessarily reflect the views of the UMTS Task Force as a ... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 6.1.1 Home Mobility Provider | The Home Mobility Provider is that with wich the subscriber has a contractual relationship. A Home Mobility Provider can contract with one or several Service Providers for service provision to his subscribers. Note that the roles of Home Mobility Provider and Service Provider may be combined in one organization, but UM... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 6.1.2 Serving Network Mobility Provider | A Mobility Provider may have a contractual relationship with one or more Serving Networks, to provide mobility support to all subscribers in the serving network. It may also offer service support to subscribers in the serving network, by acting as a proxy for one or more Service Providers. |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 6.1.3 Service Provider | This is the role which can have a contractual relationship with the Home Mobility Provider for the service support of the Home Mobility Provider's subscribers. Alternatively, a contractual relationship may exist directly with a subscriber, to provide services to the subscriber. For example, this could occur if the subs... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 6.1.4 Roaming Broker | This is the role having a roaming contract with many Mobility Providers, which acts as a broker between any two Mobility Providers. The term "broker" implies signalling support for support of mobility and charging information. |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 6.1.5 Serving Network | This is the role having a contractual relationship with one or more Mobility Providers, which provides access to UMTS services. |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 6.2 Generic VHE scenarios | The scope of IMT2000 Global Roaming includes the following: - Personal Mobility: the ability of a user to access communications services anywhere, in accordance with his/her service profile, within and between IMT2000 networks; - Personal Routeing/Addressing: the ability of the network to address and route communicatio... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 7 Identification of the ISDN-UMTS Sub-Systems | The most well developed set of network functionalities and capabilities for future mobile systems is described in Q.FNA for IMT-2000. This should be considered as a basis for the development of the cross functional requirements between the core network, service provider and the UTRAN. Some functions might be supported ... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 7.1 UMTS Domains in SMG12 | The SMG12 draft 23.01 (v0.6.0) [6] identifies UMTS domains and reference points and is reproduced in figure 7-3. ETSI ETSI TR 101 695 V3.1.1 (1999-10) 21 User Equipment Domain Access Network Domain Core Network Domain Infrastructure Domain Cu Mobile Equipment Domain USIM Domain Home Network Domain Transit Network Domai... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8 Serving Network Domain | It is widely recognized that one of the most important requirements for UMTS is its capability to support mobile access to multimedia services and applications. Also an important driver for UMTS is to provide a platform for convergence and integration of fixed, computer and mobile networks for the provision of multimed... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.1 Transport network | UMTS should provide a wide range of transport services for the support of mobile multimedia services and applications. Future mobile networks should provide the integration of fixed, computer and mobile networks for the provision of multimedia applications and services to users whilst on the move. An aim of UMTS should... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.1.1 Transport of services | The target is the support of user services and applications on any serving network independent of specific transport used in the underlying network. It is appreciated that certain network implementations in terms of transport and control may place constraints on the applications and services which can be supported. Neg... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.1.1.1 Multimedia applications | A target for future mobile systems is to support a wide range of mobile multimedia applications for many years into the future. Whilst users today may accept the appalling quality of service offered by the internet there will undoubtedly be a future requirement for much higher QoS. Users will for instance expect sub-10... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.1.1.2 Internet services | The rapid growth of the internet (including Intranet and Extranet) is leading to the development of networks based on IP addressing and routeing. For this purpose IPv4 is being used for access to internet capabilities. The IETF is now developing IPv6 to include a number of enhanced capabilities including the support of... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.1.1.3 Multimedia services | The development of B-ISDN will provide the support of a wide range of user services based on ATM transport. This will enable a range of service types to be supported such as Constant Bit Rate (CBR), Variable Bit Rate (VBR) and Available Bit Rate (ABR) services both real time an non-real-time. A wide range of QoS requir... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.1.1.4 Connection types | The task of UMTS is to extend the support of multimedia services to users whilst on the move. This will imply the support of end to end user information flow including transport over one or more radio interfaces. Various connection types, connection orientated and/or connectionless, could be setup for end to end transf... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.1.1.5 Resource allocation | UMTS (as well as B-ISDN) will need to support a mixture of services with different QoS requirements and traffic characteristics on the same network including delay critical and delay tolerant services as well as VBR services with very high peak to mean bit rate. The efficient use of network resources will be essential ... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.1.1.6 Transport over Radio | UMTS will evolve from the provision of the UMTS radio interface that will offer greater capacity and a wider range of services. The basic bearer services over the radio interface will enable UMTS to support a wide range of user QoS requirements, connection types and traffic profiles whilst providing efficient use of ne... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.1.2 Circuit switched transport networks | This subclause outlines an evolution scenario for the UMTS core network. Thus various cases in this subclause are not intended to describe a phased deployment but rather a number of options, some of which may be combined depending on the operator requirements and the complexity of implementation. One key feature might ... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2 Control network | |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.1 UMTS procedures | The following classes of UMTS Procedures are distinguished: - Attach/Detach; - Registration, Roaming, Paging; - Call Control; - Bearer Control, Handover. The classes of UMTS procedures are specified independently from each other in terms of state machines. Each state machine could be seen as a plane in the user side an... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.1.1 Location management procedures | |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.1.1.1 Considerations on location management | There will not be a network based Terminal Profile to manage a terminal identifier. The terminal identifier will not be used, or required as permanent network data, in the location management procedures including: Location Registration (including a user status update), Location Updating, and Collecting Routeing Informa... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.1.1.2 Introduction to the procedures | This State Model covers the following mobility procedures: User Registration This procedure is initiated by the user to notify the network of the presence of the user at a terminal. If this is the first User registered on the terminal, then location registration is invoked. If multiple subscriptions are allocated to a ... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.1.1.3 Information model for location management | The information model reflects the organization of the data needed for location management. The attributes store the relevant values for the location management and they are grouped in data entities (or data object classes). Each data entity contains a number of instances which are distinguished by a key or identifier.... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.1.2 Attach/Detach procedures | The attach/detach procedure is intended to notify the network about the status of the terminal on which the user has registered, i.e. whether the users registered on that terminal are reachable or not. In the case of incoming calls to a not reachable (detached) terminal the requests can be rejected at an early stage. T... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.1.3 Handover control | Handover cases may vary from a simple change of radio channel at the same mobile-base station link, through to a complete change of point of attachment to include a re-direction and re-routeing of the network side of the connection. In the following subclause only connection-oriented services and their signalling are i... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.1.3.1 Functional and procedural requirements for handover | This subclause identifies some key requirements put on handover from a functional and procedural point of view. These are derived from analysing the different handover conceptual phases which are: a) Monitoring and collecting of data; b) Decision; c) Path creation and switching; d) Completion and route optimization. Th... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.2 Functional model for UMTS | |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.2.1 Requirements for the UMTS functional model | Figure 8-3 shows the functional model for IMT2000 enhanced with functions for UMTS. It reflects the basic concepts of UMTS and commonalties with other network-concepts (such as e.g. IN, B-ISDN), namely: - the separation of switching, service control and service data functionality; - the support of call and connection c... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.2.2 The IMT2000 functional models | In the IMT-2000 functional models, the functions required for IMT-2000 service support have been grouped into Functional Entities (FE) and the functional relationships between these FEs have been indicated. Since there are two possible approaches to the allocation of call control and connection control related function... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.3 IN enhancements to support UMTS | |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.3.1 Impact of handover on IN | Handover is a means of rerouteing a connection in-call or out of call. I.e. handover does not alter the call state or the service but only replaces one or several consecutive connection elements with one or several other consecutive connection elements. Many handovers can be dealt with in access networks. In this subcl... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.3.2 Triggering of IN control functions for handover | For the triggering of IN functions on the SCF-HO, three alternatives are considered: a) Triggering from SSF (BCSM) to SCF-HO The existing CS triggering mechanism is used. This means that for handover triggering, the trigger from the radio part of the network must be notified to the SSF via the BCSM. The impact is that ... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.3.3 Execution of intra-switch handover | For the requirements for the execution of handover, different cases are distinguished, from a simple handover where only a connection towards a new base station has to be established to the most complex handover (between different domains), where not just a new connection has to be established but also the call control... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.3.4 Execution of inter-switch handover | Inter-switch handover implies that a call control entity should be initiated in the new switch. Optimization requires that all associations are transferred to this new entity. Another issue arises if the established connection, at a given node, is already under the control of an IN service logic e.g. a UPT call, when a... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.3.5 State modelling for handover | |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.3.5.1 Introduction | In this subclause a state model for handover control and one for bearer control are presented in order to define the actions taken in the switch during handover. For the time being only inter-RACF, intra-switch handover is considered for simplicity. This kind of handover does not require Control Point Transfer in the c... |
53397ed2bc1ce258883e3de36a112124 | 101 695 | 8.2.3.5.2 Evolution of IN for the integration with B-ISDN | The concept of separation of Call Control (CC) and Bearer Control (BC) functions has an impact on IN, especially for the Service Switching Function (SSF) and the Basic Call State Model (BCSM). The separation of CC and BC is also very attractive for the support of mobility services like handover, where is needed the dir... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.