hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK ACKnowledgement CD Communication Deflection CDIV Communication DIVersion CFB Communication Forwarding Busy CFNL Communication Forwarding on No Logged-in CFNR Communication Forwarding No Reply CFU Communication Forwarding Unconditional HOLD... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4 Communications Diversion (CDIV) | |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.1 Introduction | The Communications Diversion (CDIV) services enables diverting user, to divert the communications addressed to diverting user to an other destination. ETSI ETSI TS 183 004 V1.1.1 (2006-04) 8 |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.2 Description | |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.2.1 General description | The service description of the following Communication Services CFU, CFB, CFNR and CD are based on the PSTN/ISDN Supplementary Services. Generally the following requirements should be fulfilled: • It shall be possible for the user or the network to identify an alternative destination for an IP multimedia session or ind... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.3 Operational requirements | |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.3.1 Provision/withdrawal | The CDIV services (Communication forwarding unconditional, Communication forwarding busy, Communication forwarding no reply, Communication forwarding not logged-in and Communication deflection) shall be provided after prior arrangement with the service provider. The CDIV services shall be withdrawn at the served user's... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.3.2 Requirements on the originating network side | No specific requirements are needed in the network. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.3.3 Requirements in the network | No specific requirements are needed in the network. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.4 Coding requirements | ES 283 003 [2] defines the messages and parameters for this simulation service. The following messages and parameters are used to support the Communication diversion service due to fulfil the requirements. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.4.1 SIP-Messages | The following SIP messages are used due to the coding rules in ES 283 003 [2]. Table 4.4.1.1: SIP Header information for redirection SIP Message Ref. SIP Header INVITE [3] [8] see Draft-jennings-sip-voicemail-uri-05 in Bibliography History-Info-Header Privacy header cause-parameter in the uri-parameter 180 (Ringing) [3... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.4.2 Parameters | The Privacy header is described in ES 283 003 [2]. The present document refers for the History header to RFC 4244 [3], for the Privacy header and P.-Asserted-Identity to RFC 3325 [8] and for the Cause-Code to draft-jennings-sip-voicemail-uri-05 (see Bibliography). ETSI ETSI TS 183 004 V1.1.1 (2006-04) 12 |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5 Signalling requirements | |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.1 Activation/deactivation/registration | For provisioning of the CDIV the Ut interface could be used. More detail is described in clause 4.9. Other possibilities for provisioning could be used too like web based provisioning or pre-provisioning by the operator. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2 Invocation and operation | |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.1 Actions at the originating UA | When communication diversion has occurred on the served user side and the network option "notification procedure" is used, the originating UA may receive a 181 (Call is being forwarded) response according to the procedures described in ES 283 003 [2]. The Information given by the History header could be displayed by th... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.2 Actions at the originating P-CSCF | Procedures according to ES 283 003 [2] shall apply. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.3 Actions at the originating S-CSCF | Procedures according to ES 283 003 [2] shall apply. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.4 Actions at the diverting S-CSCF | Procedures according to ES 283 003 [2] shall apply. Based on the Initial Filter Criteria (IFC) Rules a communication indicating that UE:B the served user is subscribed to the CDIV simulation services the communication is be forwarded to the AS. NOTE: An example of the use of IFC is shown in annex B. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.5 Actions at the diverted to S-CSCF | Procedures according to ES 283 003 [2] shall apply. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.6 Actions at the AS of the diverting User | |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.6.1 Checking of the diversion limits | When receiving an INVITE request and the AS determines that it must divert a communication: 1) The AS shall check if diverting the communication exceeds the number of diversions allowed within the network. The number of diversions shall be calculated by the entries including a Cause parameter given by the History-Info ... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.6.2 Setting of the diversion parameters by the AS | 4.5.2.6.2.1 Overview After checking the limit of diversions the following settings of the INVITE request shall be performed. 4.5.2.6.2.2 First diversion; no History header received When this is the first diversion the communication has undergone, the following information is to be set in the retargeted request: - the d... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.6.3 Diversion procedures at the diverting AS | The diverting AS shall continue the communication depending on the service that is causing the diversion: 1) Communication Forwarding Unconditional or Communication Forwarding Busy network determined user busy or Communication forwarding on Not Logged in The AS shall continue in the following manner: - If the notificat... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.6.4 Notification procedures of the originating user (Network Option) | When Communication Diversion occurs and if the notification procedures of the originating user is supported then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user. The 181 (Call Is Being Forwarded) response contains the P-Asserted-Identity header field and Privacy header field. The P-A... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.6.5 Indication of communication diversion to the diverting user (network option) | One or combination of the following procedures are possible: 1) When the diverting user is registering the AS send a MESSAGE request including the information where the call is diverted too. As an Option the MESSAGE request that is be sent due to an timer value that can be provided by the user. 2) A diverting user will... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.7 Actions at the AS of the diverted to User | The AS shall store the History Header of an incoming Request. If a 180, 181 or 200 response does not contain a History header field, the AS shall include the stored History header field and if diverted to user is subscribed to the TIR service the Privacy header field of all responses the priv-value of the last entry in... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.8 Void | |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.9 Actions at the incoming I-CSCF | Procedures according to ES 283 003 [2] shall apply. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.10 Actions at the outgoing IBCF | Procedures according to ES 283 003 [2] shall apply. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.11 Actions at the incoming IBCF | Procedures according to ES 283 003 [2] shall apply. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.12 Actions at the BGCF | Basic call procedures according to ES 283 003 [2] shall apply. The interworking with other NGN is described in clauses 4.7.3 and 4.7.4. ETSI ETSI TS 183 004 V1.1.1 (2006-04) 18 |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.13 Actions at the MGCF | Procedures according to ES 283 003 [2] shall apply. The interworking is described in clause 4.7.1. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.14 Actions at the destination P-CSCF | Procedures according to ES 283 003 [2] shall apply. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.15 Actions at the diverted to UA | Procedures according to ES 283 003 [2] shall apply. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.5.2.16 Actions at the diverting UA | Procedures according to ES 283 003 [2] shall apply. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.6 Interaction with other services | |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.6.1 Communication Hold (HOLD) | No impact, i.e. neither service shall affect the operation of the other service. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.6.2 Terminating Identification Presentation (TIP) | A P-Asserted-Identity and History header field received in the diverting AS is passed unmodified to the originating entity. The originating S-CSCF is responsible of the interpretation of the privacy header field. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.6.3 Terminating Identification Restriction (TIR) | A P-Asserted-Identity and History header field received in the diverting AS is passed unmodified to the originating entity. The originating CSCF is responsible of the interpretation of the privacy header field. If the served (diverting) user selects the option that the originating user is notified, but without the dive... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.6.4 Originating Identification Presentation (OIP) | When a communication has been diverted and the diverted-to user has been provided with the originating identification presentation simulation service, the S-CSCF of the diverted-to user shall sent the number of the original originating user, if this originating user has not subscribed to or invoked the originating iden... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.6.5 Originating Identification Restriction (OIR) | When the originating identification restriction simulation service has been invoked, the originating user's address shall not be presented to the diverted-to user unless the diverted-to user has an override capability. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.6.6 Conference calling (CONF) | No impact, i.e. neither service shall affect the operation of the other service. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.6.7 Communication Diversion Services (CDIV) | No impact, i.e. neither service shall affect the operation of the other service. ETSI ETSI TS 183 004 V1.1.1 (2006-04) 19 |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.6.8 Malicious Communication Identification (MCID) | No impact, i.e. neither service shall affect the operation of the other service. 4.6.9 Anonymous Communication Rejection and Communication Barring (ACR/CB) If the user where the communication is forwarded to has subscribed to a call barring service "inhibition of incoming forwarded communication" the procedures describ... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.6.10 Explicit Communication Transfer (ECT) | No impact, i.e. neither service shall affect the operation of the other service. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.7 Interactions with other networks | |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.7.1 Interaction with PSTN/ISDN | In case of interaction with networks which do not provide any notification of the communication diversion or communication redirection information (e.g. redirection counter) in the signalling system, the communication continues according to the basic call procedures. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.7.1.1 Interworking at the O-MGCF | For the mapping of IAM to the INVITE Message no additional procedures beyond the basic call and interworking procedures are needed. With regard to the backward messages the following mapping is valid. Table 4.7.1.1.1: Mapping of SIP messages to ISUP messages ←Message sent to ISUP ←Message Received from SIP ACM indicati... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.7.1.1.1 Void | |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.7.1.1.2 Call forwarding within the ISUP Network appeared | The following Scenario shows if a Call Forwarding appears in the ISUP/PSTN Network and the redirected Number is within the SIP Network. Table 4.7.1.1.2.1 should be seen as example. For the mapping of 180 (Ringing) and 200 (OK) response OK to the regarding ISUP messages and parameters no additional procedures beyond the... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.7.1.2 Interworking at the I-MGCF | Table 4.7.1.2.1: Mapping of ISUP to SIP Massages Message sent to SIP Message Received from BICC/ISUP INVITE IAM Table 4.7.1.2.2: Mapping of History-Info Header to ISUP Redirecting number Source SIP header field and component Source Component value Redirecting number Derived value of parameter field CC Nature of addre... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.7.2 Interaction with PSTN/ISDN Emulation | The Interaction with PSTN/ISDN Emulation is for further study. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.7.3 Interaction with external IP networks | ES 283 003 [2] specifies the procedures used by a UE compliant to the TISPAN SIP profile to communicate with an external SIP device possibly lacking TISPAN SIP profile capabilities. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.8 Parameter values (timers) | |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.8.1 No reply timer | No reply timer: 20 to 40 sec. |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.9 Service Configuration | |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.9.1 Structure of the XML Document | Communication Diversion documents are subtrees of the simservs document specified in TS 183 023 [4]. As such, Communication Diversion documents use the XCAP application usage in TS 183 023 [4]. In addition to the considerations and constraints defined by the simservs document TS 183 023 [4], we define the additional co... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.9.1.1 Communication Diversion Element | The communication diversion configuration is contains a ruleset. The rule set reuses the syntax as specified by the common policy draft (see IETF draft-ietf-geoprive-common-policy-06.txt in Bibliography). <communication-diversion active="true"> <cp:ruleset> rule1 rule2 </cp:ruleset> </communication-diversion> In genera... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.9.1.2 Communication Diversion Rules | The Communication Diversion service is configured with an ordered set of forwarding rules. The XML Schema reuses the rule syntax as specified by the common policy draft (see IETF draft-ietf-geoprive-common-policy-06.txt in Bibliography). The rules take the following form: <cp:rule id="rule66"> <cp:conditions> condition... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.9.1.3 Communication Diversion Rule Conditions | The following conditions are allowed by the XML Schema for the communication diversion service: busy: This condition evaluates to true when the called user is busy. In all other cases the condition evaluates to false. Rules with this condition are evaluated when a busy indication is received from the called party. not-... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.9.1.4 Communication Diversion Rule Actions | The action supported by the communication service can is forwarding of calls. For this the forward-to action has been defined. The forward-to action takes the following elements: target: Specifies the address of the forwarding rule. It should be a valid SIP URI (RFC 3261 [6]) or TEL URL (RFC 3966 [7]). notify-caller: A... |
f5fdbdda5b3ff4a9fc4c165c487f8e4e | 183 004 | 4.9.2 XML Schema | <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/200 (OK) response1/XMLSchema" xmlns:ss="urn:org:etsi:ngn:params:xml:ns:simservs" xmlns:cp="urn:ietf:params:xml:ns:common-policy" xmlns:ocp="urn:oma:params:xml:ns:common-policy" targetNamespace="urn:org:etsi:ngn:params:xml:ns:simservs" element... |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 1 Scope | The present document describes the specific TISPAN requirements for controls to manage overload of processing resources in NGNs. In particular, it addresses overload control between nearest neighbours. |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ITU-T recommendation E.412: "Network management contr... |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: IMS IP Multimedia Subsystem ISDN Integrated Service Digital Network NGN Next Generation Network ETSI ETSI TS 182 018 V2.0.0 (2008-01) 6 PSTN Public Switched Telecommunication Network QoS Quality of Service RACS Resource Admission Subsystem SCF... |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 4 TISPAN NGN overload control requirements | |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 4.1 High level overload control requirements | In TS 181 005 [4] we have the following requirements for overload control. The NGN shall have mechanisms available to control overload that: 1) automatically maximize effective throughput (i.e. admitted service requests/sec) at an overloaded resource; 2) achieve this throughout the duration of an overload event, and ir... |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 4.2 General requirements for Nearest Neighbour load control | These requirements are general, and any overload control should address these requirements. REQ 1 A control shall automatically reduce the load that is sent to an overloaded host. REQ 2 A control shall aim to maximize the number of fully processed service requests at an overloaded host, subject to meeting any QoS const... |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 4.3 Deployment specific requirements | The following requirements relate to different deployment options of the protected host and its traffic sources. Particular controls will need to address these deployments, so any overload control architecture must support or enable these requirements. REQ 17 Controls are required for scenarios where hosts receive serv... |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 4.4 Application specific requirements | The general requirements above relate to overload controls that act between hosts that are nearest neighbours, i.e. host load control. Application specific requirements arise from the need for some applications to perform functions closely related to host load control. Many of these requirements are not naturally part ... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 1 Scope | The present document describes an IMS-based functional architecture for the PSTN/ISDN Emulation Subsystem (PES) of the ETSI TISPAN NGN overall architecture. The IMS-based PSTN/ISDN Emulation Subsystem described herein supports the emulation of PSTN services for analog terminals and ISDN services for ISDN terminals and ... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI ES 282 001: "Telecommunications and Internet con... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 2.2 Informative references | Not Applicable. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 3 Definitions and abbreviations | |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Access Gateway (AG): gateway device that interworks a significant number of analogue lines/ISDN accesses (directly or via an V5 Access Network) to a packet network and is located at the operator's premises NOTE: An AG can take the form... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AF Application Function AG Access Gateway AGCF Access Gateway Control Function A-MGF Access Media Gateway Function A-MGW Access Media GateWay AN Access Node AS Application Server ASF Application Server Function ATA Analogue Terminal Adaptor A-... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 4 Overview | |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 4.1 PSTN/ISDN Emulation subsystem environment | Figure 1 shows the PSTN/ISDN Emulation Subsystem and its relationships with other TISPAN NGN subsystem. Applications/ User Profiles Resource and Admission Control Subsystem Residential and Access MGW TISPAN PSTN/ISDN Emulation Subsystem Core IMS PSTN/ISDN (TDM based) Network Attachment Subsystem Charging functions Netw... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 4.2 Signalling configurations | Figure 2 illustrates the signalling configurations supported by the PSTN/ISDN Emulation Subsystem (PES) described in the present document. PSTN/ISDN Emulation Subsystem ISDN/PSTN ISDN/PSTN Trunk Trunk T-MGF T-MGF V5.x AN analog access ISDN access V5.x AN analog access ISDN access MGW/ VGW MGW/ VGW Figure 2: Signalling ... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 4.3 Constraints on services | The range of services that can be emulated in TISPAN NGN Release 1 is constrained by the functional architecture and the IMS SIP profile defined in ES 283 003 [4] on the Mw/Mx and ISC reference points, and of the Gm reference points in case of VGW. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 4.4 Overlap signalling | Overlap sending is a mechanism that is used for dialling over analogue and ISDN accesses, and is inbuilt in the inter- exchange signalling systems of the PSTN/ISDN networks. As such, it is a mechanism that the IMS-based PSTN/ISDN emulation subsystem architecture shall support, in a similar manner as for the PSTN. To su... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5 Functional architecture | |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.1 Overview | The functional architecture described in the preent document is one of the possible architectural options for structuring the TISPAN PSTN/ISDN Emulation Subsystem (PES) identified in the TISPAN NGN overall architecture ES 282 001 [1]. This functional architecture uses the same architecture as the IMS defined in ES 282 ... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.2 Overview of Functional entities of the PES | |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.2.1 Access Gateway Control Function (AGCF) | This functional entity is the first point of contact for Residential Media Gateway (R-MGW) and Access Media Gateways (A-MGW). This entity is specific to the PSTN/ISDN emulation subsystem. It performs the following functions: • Act as an MGC for controlling media gateways functions (R-MGF and A-MGF) located in residenti... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.2.2 Multimedia Resource Function Controller (MRFC) | The behaviour of the MRFC is identical in the PSTN/ISDN Emulation Subsystem and in the IMS subsystem ES 282 007 [2]. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.2.3 Media Gateway Control Function (MGCF) | The role of the MGCF is identical in the PSTN/ISDN Emulation Subsystem and in the IMS subsystem ES 282 007 [2]. Signalling procedures for interworking with ISUP signalling are slightly different due to the presence of encapsulated ISUP information inside the PES and the need to ensure full ISDN transparency in case of ... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.2.4 Proxy Call Session Control Function (P-CSCF) | The behaviour of the P-CSCF is identical in the PSTN/ISDN Emulation Subsystem and in the IMS subsystem ES 282 007 [2]. However, the P-CSCF is not used in configurations where an AGCF is required to control residential or access media gateways. In such cases, all functions normally provided by the P-CSCF will be provide... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.2.5 Service Call Session Control Function (S-CSCF) | The behaviour of the S-CSCF is identical in the PSTN/ISDN Emulation Subsystem and in the IMS subsystem ES 282 007 [2]. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.2.6 Interrogating Call Session Control Function (I-CSCF) | The behaviour of the I-CSCF is identical in the PSTN/ISDN Emulation Subsystem and in the IMS subsystem ES 282 007 [2]. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.2.7 Breakout Gateway Control Function (BGCF) | The behaviour of the BGCF is identical in the PSTN/ISDN Emulation Subsystem and in the IMS subsystem ES 282 007 [2]. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.3 Internal Reference Points | |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.3.1 Reference Point MGCF - CSCF (Mg Reference Point) | The Mg reference point allows the MGCF to forward incoming session signalling (from the PSTN) to the CSCF for the purpose of interworking with PSTN networks. The protocol used for the Mg reference point is SIP. SIP messages may contain encapsulated ISUP information. The role of this reference point is identical in the ... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.3.2 Reference Point CSCF - MRFC (Mr Reference Point) | The Mr reference point allows the S-CSCF to relay signalling messages between an application server function and an MRFC. The protocol used for the Mr reference point is SIP. The role of this reference point is identical in the PES and IMS subsystems ES 282 007 [2]. Details are described in TS 182 006 [3]. 5.3.3 Refere... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.3.4 Reference Point CSCF - BGCF (Mi reference point) | This reference point allows the Serving CSCF to forward the session signalling to the Breakout Gateway Control Function for the purpose of interworking to the PSTN networks. The protocol used for the Mi reference point is SIP. SIP messages exchanged over the Mi reference point may contain encapsulated ISUP information.... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.3.5 Reference Point BGCF - MGCF (Mj reference point) | This reference point allows the Breakout Gateway Control Function to forward the session signalling to the Media Gateway Control Function (and vice-versa) for the purpose of interworking to the PSTN networks. This reference point may also be used by an MGCF to forward session signalling to the BGCF in case of transit s... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.3.6 Reference Point BGCF - BGCF (Mk reference point) | This reference point allows the Breakout Gateway Control Function to forward the session signalling to another Breakout Gateway Control Function. The Mk reference point is SIP, possibly with encapsulated ISUP information. The role of this reference point is identical in the PES and IMS subsystems. Details are described... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.