hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.2 Summary | This profile supports the control of the following functionality in IP-to-IP Media Gateways: • opening and closing gates (i.e. packets filtering depending on "IP address/port"); • allocation and translation of IP addresses and port numbers (NAPT): - IP realm/domain indication (via H.248.41 amendment 1); - RTCP handling; • interworking between IPv4 and IPv6 networks (NAPT-PT); • topology hiding; • hosted NAT traversal; • packet marking for outgoing traffic; • resource allocation and bandwidth reservation: - one and two-stage BGF resource reservation; • policing of incoming traffic; • QoS and usage metering: - conditional statistics reporting; • transcoding; • detection of inactive bearer connections; • specific call-independent procedures: - detection of hanging H.248 terminations; and • BGF overload control (at H.248 interface). |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.3 Gateway Control Protocol Version | ITU-T Recommendation H.248.1 [1] Version 3. NOTE: Version 3 of the H.248 protocol is needed, due to the possible usage of stream statistics. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.4 Connection model | Table 2: Connection model Maximum number of contexts: Provisioned Maximum number of terminations per context: 2 Allowed terminations type combinations: (IP,IP) ETSI ETSI TS 183 018 V3.5.2 (2010-01) 17 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.5 Context attributes | Table 3: Context attributes Context attribute Supported Values supported Topology No Not Applicable Priority Indicator Yes 0 to15 Emergency Indicator Yes ON/OFF IEPS Indicator No Not Applicable ContextAttribute Descriptor No Not Applicable ContextIdList Parameter No Not Applicable AND/OR Context Attribute No Not Applicable |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.6 Terminations | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.6.1 Termination names | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.6.1.1 IP Termination | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.6.1.1.1 Overview and prose specification | The Termination ID structure shall follow the guidelines of H.248 and shall be based on four fields: • "ip/<group>/<interface>/<id>". The individual fields are described and defined in table 4. Table 4: IP Termination Fields Name Description Values CHOOSE Wildcard ALL Wildcard ip "ip" is a fixed prefix identifying the termination. "ip" No No group Group of Interface and Id. Integer (0 to 65 535) (see note 6) No Yes interface Logical or physical interface to a network to/from which the termination will be sending/receiving media. (See notes 1 and 2). String of max 51 alphanumeric characters Yes (see note 5) Yes id Termination specific identifier (See note 3). Non-zero 32 bit integer Yes (see note 4) Yes NOTE 1: A specific <Interface> may be used together with different groups. NOTE 2: The generic field <Interface> may relate specifically to an "IP interface", "protocol layer 2 interface" or others. NOTE 3: The combination of Interface and Id is unique. NOTE 4: In version 1 of this profile, there was a tacit assumption that the MGC used a CHOOSE wildcard in an ADD request command. In this version, the MGC shall always use CHOOSE in an ADD request command. If not, the MG shall reply with an error descriptor using error code #501 "Not Implemented". See also clause 5.6.1.1.1.3. NOTE 5: The MGC shall always use CHOOSE in an ADD request command. If not, the MG shall reply with an error descriptor using error code #501 "Not Implemented". NOTE 6: The actual used range of Group ID is fully under MGC control. NOTE: The SPDF has the ability to choose the address space in which the BGF will allocate an IP address for the termination by using the ipdc/realm property defined in the H.248.41 IP domain connection package. H.248 wildcarding may be applied on IP Termination Identifiers. Wildcarding is limited according the two columns on the right hand side. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 18 5.6.1.1.1.1 Combined usage of fields Group and Interface There are two potential relationships between <group> and <interface> within the TerminationID structure: • strictly hierarchical: a single "interface" is completely associated to a dedicated "group". EXAMPLE 1: May be driven for instance by hardware architecture or addressing schemes with the goal of minimizing ServiceChange command load by using wildcards such as ip/<group>/* for potential HW failures that may lead to issuing a single ServiceChange command rather than multiple ServiceChange commands. • partially hierarchical: an "interface" is distributed over multiple "groups". EXAMPLE 2: A logical partition concept may be driven for instance for selective auditing with the goal of minimizing the AuditReply to be of a manageable size by having the MGC allocate an adequate number of terminations within a <group>. Therefore Audits could be paced for example: ip/1/*, ip/2/*, .., ip/n/*. ip/<group>/<interface>/<id> IP Group ID Interface IP Groups ID Interface (A) Strict hierarchical structure (B) Partial hierarchical structure Figure 2: Group/Interface relationships for the structure of terminationIDs Potential use cases The following examples depict the advantages that each group/interface relationship may facilitate. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 19 Table 5: Examples of Group/interface relationship in ServiceChange Semantic of Termination Name ServiceChange Command (e.g. due to a HW Failure) Strictly hierarchical Upon a HW failure the command issued is (by MG): ServiceChange=ip/1/*{Services{ Method=Forced, Reason="906" }}}, ...a single wildcarded command is possible (facilitated by a strict hierarchical relationship). Partially hierarchical Upon a HW failure the command issued is (by MG): ServiceChange=ip/*/1/*{Services{ Method=Forced, Reason="906" }}}, ServiceChange=ip/*/2/*{Services{ Method=Forced, Reason="906" }}}, … ServiceChange=ip/*/x/*{Services{ Method=Forced, Reason="906" }}} ...a single wildcarded command is not always possible when not using a strict hierarchical relationship. Table 5a: Examples of Termination ID usage in AuditValue Usage of Termination ID structure AuditValue Command (e.g. Requesting a list of Context IDs present in the MG where n and N are number of contexts in the AuditValue Replie-s and n<<N) Neither group nor interface levels specified in request The command (from MGC): Context=*{AuditValue=Root{Audit{}}} Returns: Context=1{AuditValue=ip/1/11/101{},AuditValue=ip/1/12/102{}}, Context=2{AuditValue=ip/1/21/201{},AuditValue=ip/1/22/202{}}, Context=3{AuditValue=ip/1/31/301{},AuditValue=ip/1/32/302{}}, … Context=N{AuditValue=ip/256/11/504{},AuditValue=ip/256/12/534{}} … this could potentially return very large AuditValue Replies. Group level specified in request The command (by MGC): Context=*{AuditValue=ip/1/*{Audit{}}} Returns: Context=1{AuditValue=ip/1/11/101{},AuditValue=ip/1/12/102{}}, … Context=n{AuditValue=ip/1/51/121{},AuditValue=ip/1/52/122{}} … and this command would be repeated for each group. (facilitated by loose hierarchical relationship). ETSI ETSI TS 183 018 V3.5.2 (2010-01) 20 5.6.1.1.1.2 Optimization of call-independent procedures The CHOOSE wildcard for "Interface" is introduced by this version of the profile. The MGC may optimize (see note 1) call-independent procedures, e.g. based on the AuditValue command, by fully controlling the value allocation for field Group. NOTE 1: "Optimization" could e.g. mean a load shaping function concerning H.248 processing load. The MG may optimize (see note 2) call-independent procedures, e.g. based on the ServiceChange command, via full control over the value allocation for field Interface. NOTE 2: "Optimization" may allow single wildcarded commands, see discussion in table 5. 5.6.1.1.1.3 Field "Id": Usage of wildcard CHOOSE or not The CHOOSE wildcard for "Id" must be applied in the ADD.request command. It is the MGs responsibility for managing the value range of this logical resource. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.6.1.1.2 Syntactical Specification | 5.6.1.1.2.1 ABNF Grammar for H.248 Text Encoding Mode ABNF (RFC 5234 [6]) is used for the syntax specification. The ABNF for TerminationID and relation to pathNAME is defined in annex B.2 of ITU-T Recommendation H.248.1 [1]. ABNF coding: pathNAME = EphToken SLASH EPHsystem EphToken = "ip" ; prefix EPHsystem = WildcardALL / WildcardALL SLASH Interface / Group SLASH WildcardALL / Group SLASH (Interface / WildcardCHOOSE) SLASH (Identifier / WildcardALL / WildcardCHOOSE) Group = %d0-65535 ; data type: INT16 Interface = 1*51ALPHANUM Identifier = %d1-4294967295 ; data type: INT32 ALPHANUM = ALPHA / DIGIT WildcardCHOOSE = "$" WildcardALL = "*" |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.6.2 Multiplexed terminations | Table 6: Multiplexed terminations MultiplexTerminations Supported? No |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7 Descriptors | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.1 TerminationState descriptor | Table 7: ServiceState property ServiceState property used: No NOTE: All H.248 Terminations have a ServiceState property according to H.248.1, but explicit usage of the TerminationState Descriptor ServiceState property is not required by this Profile. ServiceState changes can still occur, however, and be indicated in ServiceChange Commands (i.e. this means that the value of the ServiceState property may be implicitly changed by ServiceChange procedures). ETSI ETSI TS 183 018 V3.5.2 (2010-01) 21 Table 8: EventBufferControl property EventBufferControl property used: No |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.2 Stream descriptor | Table 9: Stream descriptor Maximum number of streams per termination type: IP 5 Table 10: Stream configuration Stream Configuration: ALL configurations are allowed |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.2.1 LocalControl descriptor | Table 11: LocalControl descriptor If not generic list appropriate termination and stream types Termination Type Stream Type ReserveGroup used: No ReserveValue used: No Table 12: Termination type Termination Type Stream Type Allowed StreamMode Values IP RTP/AVP SendOnly, RecvOnly, SendRecv, Inactive tcp SendRecv, Inactive udptl SendRecv, Inactive udp SendOnly, RecvOnly, SendRecv, Inactive NOTE: Other stream types are for further study. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.3 Events descriptor | Table 13: Events descriptor Events settable on termination types and stream types Yes If yes Event ID Termination Type Stream Type See clause 5.14.2.1 • g/cause ALL except ROOT ANY See clause 5.14.2.3 • nt/netfail • nt/qualert ALL except ROOT ANY See clause 5.14.2.11 • it/ito only ROOT Not applicable See clause 5.14.2.14 • adid/ipstop ALL except ROOT ANY See clause 5.14.2.16 • ocp/mg_overload only ROOT Not applicable See clause 5.14.2.17 • hangterm/thb ALL except ROOT Not applicable See clause 5.14.2.18 • scr/cr ALL except ROOT Not applicable See clause 5.14.2.1 • ipra/arc only ROOT Not applicable ETSI ETSI TS 183 018 V3.5.2 (2010-01) 22 Table 14: EventBuffer control EventBuffer Control used: No Table 15: KeepActive KeepActive used on events: No Table 16: Embedded events and signals Embedded events in an Events Descriptor: No Embedded signals in an Events Descriptor: No Table 17: Regulated embedded events Regulated Embedded events are triggered on: None Table 18: ResetEventsDescriptor ResetEventsDescriptor used with events: None Table 19: NotifyImmediate, NotifyRegulated and NeverNotify NotifyImmediate: ALL events NotifyRegulated: None NeverNotify: None |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.4 EventBuffer descriptor | Table 20: EventBuffer descriptor EventBuffer Descriptor used: No |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.5 Signals descriptor | Table 21: Signals descriptor Signals settable dependant on termination or streams types Yes If yes Signal ID Termination Type Stream Type / ID ipnapt/* ALL except ROOT ANY Table 22: Signals lists Signals Lists supported: No Table 23: Signals type and duration Signal type and duration supported: No ETSI ETSI TS 183 018 V3.5.2 (2010-01) 23 Table 24: Signals direction Signal Direction supported: No Table 25: NotifyCompletion and RequestID NotifyCompletion supported: No RequestID Parameter Supported: No Table 26: Simultaneously played signals Signals played simultaneously: No Table 27: KeepActive KeepActive used on signals: No |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.6 DigitMap descriptor | Table 28: DigitMap descriptor DigitMaps supported: No |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.7 Statistics descriptor | Table 29: Statistics Descriptor Statistics supported on: Stream Table 30: Statistics Reported On Subtract Statistics reported on Subtract: Yes If yes Statistic IDs reported: ALL (See clause 5.14 for details) |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.8 ObservedEvents descriptor | Table 31: ObservedEvents descriptor Event detection time supported: No |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.9 Topology descriptor | Table 32: Topology descriptor Allowed triples: Not Applicable ETSI ETSI TS 183 018 V3.5.2 (2010-01) 24 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.7.10 Error descriptor | Table 33: Error Codes sent by MGC Supported H.248.8 [30] Error Codes: ALL Supported Error Codes defined in packages: All error codes defined in supported packages need to be supported Table 34: Error Codes sent by MG Supported H.248.8 [30] Error Codes: ALL with exception of #514 "Media Gateway cannot send the specified announcement" #518 "Event buffer full" #519 "Out of space to store digit map" #520 "Digit Map undefined in the MG" #522 "Functionality Requested in Topology Triple Not Supported" Supported Error Codes defined in packages: All error codes defined in supported packages need to be supported |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8 Command API | Table 35 shows in which direction commands are sent, which terminations they can be associated with, and which wildcard options are supported for the specific command. Table 35: Commands and terminations Command Sent By Used on Termination Type Wildcard Support IP ROOT W- O- Add SPDF Yes No No No AuditCapabilities - - - - - AuditValue SPDF Yes Yes No Yes Modify SPDF Yes Yes No No Move - - - - - Notify BGF Yes Yes No No ServiceChange BGF Yes Yes No No Subtract SPDF Yes No Yes No Table 35 shows for which termination types a specific descriptor can be applied, and tables 36 and 37 show with which commands and replies the descriptor can be used respectively. Table 36: Descriptors and requests Descriptor type (see note 1) Termination type Root IP Audit Yes Yes Error Events Yes Yes Local Yes LocalControl Yes Media Yes (see note 2) Yes ObservedEvents Yes Yes Packages Yes ServiceChange Yes Yes Signals Yes Statistics Yes Stream Yes TerminationState Yes (see note 2) NOTE 1: Only H.248 descriptors supported within this H.248 profile specification are shown. NOTE 2: E.g. Base Root package properties. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 25 Table 37: Descriptors and replies Descriptor type (see note 1) Termination type Root IP Audit Error Yes Yes Events Yes Yes Local LocalControl (see note 2) Yes Media Yes Yes ObservedEvents Packages Yes Remote ServiceChange Yes Yes Signals (see note 3) Statistics Yes Stream Yes TerminationState Yes NOTE 1: Only H.248 descriptors supported within this H.248 profile specification are shown. NOTE 2: According to section 5.8.5, auditing of mgcinfo/db H.248 property in LocalControl is required. NOTE 3: According to section 5.8.5, auditing of H.248 signals descriptors is not required. It is seen that an Error Descriptor may be returned in any command reply and thus the Error Descriptor is not included in any subsequent command reply tables. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.1 Add | Table 38: Descriptors used by Add Request Descriptors used by Add request: Media (Stream(LocalControl, Statistics, Local, Remote)), Event, Signals NOTE: Statistics are enabled as default. The MGC may explicitly request or suppress statistics generation for individual streams by inclusion of the Statistics descriptor in the Add request command (see section 7.1.15, ITU-T Rec. H.248.1 [1]). Table 39: Descriptors used by Add Reply Descriptors used by Add reply: Media (Stream (Local)) |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.2 Modify | Table 40: Descriptors used by Modify Request Descriptors used by Modify request: Media (TerminationState, Stream (LocalControl, Statistics, Local, Remote)), Audit (Media (Stream (Statistics)), Signals, Event Table 41: Descriptors used by Modify Reply Descriptors used by Modify reply: Media (Stream(Local, Statistics)) ETSI ETSI TS 183 018 V3.5.2 (2010-01) 26 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.3 Subtract | Table 42: Descriptors used by Subtract Request Descriptors used by Subtract request: Audit() OR NONE NOTE: This profile version supports reporting of statistics on all streams or none of the streams. Reporting and disabling of statistics from a subset of the streams in case of multiple streams is not supported by this profile version. Termination level statistics are not supported. Table 43: Descriptors used by Subtract Reply Descriptors used by Subtract reply: Media(Stream(Statistics)) OR NONE |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.4 Move | Table 44: Descriptors used by Move Command Move command used: No |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.5 AuditValue | Table 45: AuditValue Audited Properties: Media(TerminationState) (see note 1) Media(Stream(LocalControl)) (see note 2) Audited Statistics: ALL Audited Signals: None Audited Events: None Packages Audit possible: Yes NOTE 1: These are the root/*, seg/* and ipra/* properties. NOTE 2: This is the mgcinfo/db property. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.6 AuditCapabilities | Table 46: Descriptors used by AuditCapabilities Command AuditCapabilities command used: No |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.7 Notify | Table 47: Descriptors used by Notify Request Descriptors used by Notify Request: ObservedEvents Table 47a: Descriptors used by Notify Reply Descriptors used by Notify Reply: None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 27 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.8 ServiceChange | Table 48: ServiceChangeMethods and ServiceChangeReasons sent by MGC Service Change Methods Supported ServiceChange Reasons supported Restart 900, 901 Handoff 903 Table 49: ServiceChangeMethods and ServiceChangeReasons sent by MG Service Change Methods Supported ServiceChange Reasons supported Disconnected 900 Forced 904, 905, 906, 915 Restart 900, 901, 902 Graceful 905, 908 Failover 909 Handoff 903 Table 50: ServiceChangeAddress ServiceChangeAddress used: No Table 51: ServiceChangeDelay ServiceChangeDelay used: Yes If yes Valid time period: Provisioned Table 52: ServiceChange Incomplete Flag ServiceChange Incomplete Flag used: No Table 53: ServiceChangeVersion Version used in ServiceChangeVersion: 3 Table 54: Profile Negotiation Profile negotiation as per H.248.18 [i.7]: No Table 54a: ServiceChangeMGCId ServiceChangeMGCId used: Yes |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.8.9 Manipulating and auditing context attributes | Table 55: Context Attributes Manipulation and Auditing Context Attributes Manipulated: Emergency, Priority Context Attributes Audited: None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 28 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.9 Generic command syntax and encoding | Table 56: Command Encoding Supported Encodings: Text (see notes 1 and 2) NOTE 1: The receiver shall be capable of receiving both Short Token Notation and Long Token Notation on an H.248 control association. NOTE 2: The transmitter may select between long and short token forms per H.248 control association. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.10 Transactions | Table 57: Maximum number of Transaction Requests/Replies/TransResponseAcks/Segment Maximum number of Transaction Requests/Replies/TransResponseAcks/Segment Replies per message: 1 Table 58: Maximum number of Commands per Transaction Request Maximum number of commands per Transaction request: 2 Table 59: Maximum number of Commands per Transaction Reply Maximum number of commands per Transaction reply: 2 Table 60: Optional Commands Commands able to be marked "Optional": AuditValue Table 61: Wildcarded Commands Commands able to be marked "Wildcarded": Subtract Table 62: Transaction Timer Transaction Timer: Value normalMGExecutionTime Provisioned, changeable with Base Root Package (see clause 5.14.2) normalMGCExecutionTime Provisioned, changeable with Base Root Package (see clause 5.14.2) MGOriginatedPendingLimit Provisioned, changeable with Base Root Package (see clause 5.14.2) MGCOriginatedPendingLimit Provisioned, changeable with Base Root Package (see clause 5.14.2) MGProvisionalResponseTimerValue Provisioned, changeable with Base Root Package (see clause 5.14.2) MGCProvisionalResponseTimerValue Provisioned, changeable with Base Root Package (see clause 5.14.2) ETSI ETSI TS 183 018 V3.5.2 (2010-01) 29 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.11 Messages | It is recommended that MGC and MG names are in the form of fully qualified domain names. For example the domain name of the MGC may be of the form mgc1.whatever.net and the name of the MG may be of the form mg1.whatever.net. The fully qualified domain name will be used by the MGC and MG as part of the "Message Identifier" in the H.248 messages which identifies the originator of the message. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.12 Transport | Table 63: Transport Supported Transports: SCTP (Recommended) UDP (Optional) Table 64: Segmentation Segmentation Supported: SCTP: Inherent in Transport UDP: Optional (dependent on support of Segmentation Package, see clause 5.14.2.12) Table 65: Control Association Control Association Monitoring Supported: Monitoring mechanism is dependent on used H.248 transport (see above table 63): SCTP: inherent capability of SCTP. UDP: H.248.14 (MG-driven monitoring). Empty AuditValue on ROOT (MGC-driven monitoring). |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.13 Security | Table 66: Security Supported Security: None |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14 Packages | This clause includes details of the mandatory and optional H.248 packages that are included in this profile. The meaning of mandatory and optional packages and their properties, signals, events, and statistics is defined in ITU-T Recommendation H.248 Sub-series Implementers' Guide [33]. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 30 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.1 Overview | Table 67: Mandatory Packages Mandatory Packages Package Name Package ID Version Generic (ITU-T Rec. H.248.1 [1], annex E.1) g 2 Base root (ITU-T Rec. H.248.1 [1], annex E.2) root 2 Network (ITU-T Rec. H.248.1 [1], annex E.11) nt 1 Diffserv (ITU-T Rec. H.248.52 [17]) ds 2 Gate management (ITU-T Rec. H.248.43 [18], Appendix 1) gm 1 Traffic management (ITU-T Rec. H.248.53 [19]) tman 1 IP NAPT traversal (ITU-T Rec. H.248.37 [9]) ipnapt 1 IP Domain Connection (ITU-T Rec. H.248.41 [16]) ipdc 1 Table 68: Optional Packages Optional Packages Package Name Package ID Version Support dependent on MPLS (ITU-T Rec. H.248.54 [10]) mpls 1 Support of MPLS label stacks - i.e. Label Switched Paths terminated by the MG and related to the H.248 termination. VLAN (ITU-T Rec. H.248.56 [11]) vlan 1 Support of VLAN tags and/or Ethernet priorities. MGC Information (ITU-T Rec. H.248.45 [4]) mgcinfo 1 Support of MGC related recovery. Inactivity Timer (ITU-T Rec. H.248.14 [13]) it 1 Only applicable for UDP transport. Segmentation (ITU-T Rec. H.248.1 [1], annex E.14) seg 1 Applicable for UDP transport where sufficiently large messages are required to be supported. RTP (ITU-T Rec. H.248.1 [1], annex E.12) rtp 1 Support of usage metering and statistics reporting. Particular package capabilities are only applicable for "media-aware" bearer connections. Application Data Inactivity Detection ITU-T Rec. H.248.40 [12]) adid 1 MGC requires to be explicitly informed of a cessation of an application data flow. Media Gateway Overload Control (ITU-T Rec. H.248.11 [15]) ocp 1 Support of message throttling, based on rate limitation, from MGC towards MG. Hanging Termination Detection (ITU-T Rec. H.248.36 [24]) hangterm 1 Support of Hanging Termination Detection. Statistics Conditional Reporting (ITU-T Rec. H.248.47 Revision 1 [25]) scr 2 Support of real time reporting of specific statistics based on a particular condition. This package may be supported as an operator option. Gate management (ITU-T Rec. H.248.43 [18]) gm 2 Support of filtering based on source port range. IP realm availability (ITU-T Rec. H.248.41 Amendment 1) [16] ipra 1 Support of a mechanism allowing the MGC to discover the IP realms that are available at the MG at a certain time and on a mechanism allowing the MG to inform the MGC about change of availability of realms. RTP Application Data Package (H.248.58 [34]) rtpad 1 Support of usage metering and statistics reporting. Scope on traffic-volume based measurement of RTP application data (i.e. the media stream). Latch Statistics (ITU-T Rec. H.248.37 Revision 1 [9]) lstat 1 Complements the IP NAPT Traversal package to enable the recording of discarded packets due to implicit filtering by the latching function. Traffic Policing Statistics (ITU-T Rec. H.248.53 Revision 1 [19]) tmanr 2 Complements the Traffic Management package, allowing the recording of the number of packets and octets that did not conform to the traffic parameters, and the number of packets that were dropped due to such violations. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 31 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2 Package usage information | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.1 Generic (g) | Table 69: Generic package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command Cause (g/cause) M ADD, NOTIFY Event Parameters Mandatory/Optional Supported Values Provisioned Value None ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value General cause (Generalcause) M ALL Not Applicable Failure cause (Failurecause) M ALL Not Applicable Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 32 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.2 Base root (root) | Table 70: Base root package Properties Mandatory/Optional Used in command Supported Values Provisioned Value MaxNrOfContexts (root/maxNumberOfContexts) O AUDITVALUE ALL YES MaxTerminationsPerContext (root/maxTerminationPerContext) O AUDITVALUE ALL YES normalMGExecutionTime (root/normalMGExecutionTime) O MODIFY, AUDITVALUE ALL YES normalMGCExecutionTime (root/normalMGCExecutionTime) O MODIFY, AUDITVALUE ALL YES MGProvisionalResponseTimer Value (root/MGProvisionalResponse TimerValue) O MODIFY, AUDITVALUE ALL YES MGCProvisionalResponseTimer Value (root/MGCProvisionalResponse TimerValue) O MODIFY, AUDITVALUE ALL YES MGCOriginatedPendingLimit (root/MGCOriginatedPending Limit) O MODIFY, AUDITVALUE ALL YES MGOriginatedPendingLimit (root/MGOriginatedPendingLimit) O MODIFY, AUDITVALUE ALL YES Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command None Event Parameters Mandatory/Optional Supported Values Provisioned Value ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 33 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.3 Network (nt) | Table 71: Network package Properties Mandatory/Optional Used in command Supported Values Provisioned Value Maximum jitter buffer (nt/jit) O ADD, MODIFY ALL YES Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command Network failure (nt/netfail) O ADD, MODIFY, NOTIFY Event Parameters Mandatory/Optional Supported Values Provisioned Value None - - - ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Cause (cs) O For further studies. For further studies (see note) Quality alert (nt/qualert) O ADD, MODIFY, NOTIFY Event Parameters Mandatory/Optional Supported Values Provisioned Value Threshold (th) O ALL Not Applicable ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Threshold (th) O ALL Not Applicable Statistics Mandatory/Optional Used in command Supported Values Duration (nt/dur) O ADD, SUBTRACT, MODIFY, AUDITVALUE ALL Octets sent (nt/os) M ADD, SUBTRACT ALL O MODIFY, AUDITVALUE ALL Octets received (nt/or) M ADD, SUBTRACT ALL O MODIFY, AUDITVALUE ALL Error Codes Mandatory/Optional None NOTE: This event may be overloaded in order to address multiple failure causes (see ITU-T Rec. H.248.1 [1] Version 3, section E.11.5.1.2). An unambiguous distinction on MGC and MG side implies mutually agreed cause codepoints. This is a provisioning activity. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 34 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.4 Differentiated Services (ds) | Table 72: Differentiated Services package Properties Mandatory/Optional Used in command Supported Values Provisioned Value Differentiated Services Code Point (ds/dscp) M ADD, MODIFY ALL Yes Tagging Behaviour (ds/tb) O ADD, MODIFY ALL Yes Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command None Event Parameters Mandatory/Optional Supported Values Provisioned Value ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 35 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.5 Gate Management (gm) | Table 73: Gate Management Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value Remote Source Address Filtering (gm/saf) M ADD, MODIFY ALL Not Applicable (see note 1) Remote Source Address Mask (gm/sam) O ADD, MODIFY ALL Not Applicable Remote Source Port Filtering (gm/spf) M ADD, MODIFY ALL Not Applicable (see note 1) Remote Source Port (gm/spr) O ADD, MODIFY ALL Not Applicable Remote Source Port Range (gm/sprr) (see note 3) O ADD, MODIFY ALL Not Applicable Explicit Source Address Setting (gm/esas) O ADD, MODIFY ALL See note 1 Local Source Address (gm/lsa) O ADD, MODIFY ALL Not Applicable Explicit Source Port Setting (gm/esps) O ADD, MODIFY ALL See note 1 Local Source Port (gm/lsp) O ADD, MODIFY ALL Not Applicable RTP Specific Behaviour (gm/rsb) (see note 4) M ADD, MODIFY ALL OFF (see note 2) Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/ Optional Supported Values Duration Provisioned Value - - - - Events Mandatory/Optional Used in command None - - Event Parameters Mandatory/ Optional Supported Values Provisioned Value - - - - ObservedEvent Parameters Mandatory/ Optional Supported Values Provisioned Value - - - - Statistics Mandatory/Optional Used in command Supported Values Discarded Packets gm/dp O ADD, MODIFY, SUBTRACT, AUDITVALUE ALL Error Codes Mandatory/Optional None NOTE 1: Default value is 'OFF' in gm/1 (see ITU- Rec. H.248.43 [18]). NOTE 2: Default value must be provisioned in gm/1 (see ITU- Rec. H.248.43 [18]). The provisioned value in this profile shall be OFF. NOTE 3: This property is defined in gm/2 while all other properties exist in gm/1. NOTE 4: The gm/rsb property is identical to the rtcph/rsb property (see Figure II.1 in H.248.43) and defined by ITU-T Rec. H.248.57 [i.19]. The rtcph package defines rsb property semantics for the SDP attribute according RFC 3605 [31] (see in particular clause 6.6.1.4.1 in H.248.57). There are following package usage details for this profile specification: the SDP attribute "a=rtcp:" may be used in the H.248 RD and shall be not used in the H.248 LD (see clauses 5.16 and 5.17.1.7 for more information). ETSI ETSI TS 183 018 V3.5.2 (2010-01) 36 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.6 Traffic management (tman) | Table 74: Traffic Management Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value tman/pol M ADD, MODIFY ALL Yes tman/pdr M ADD, MODIFY ALL Not Applicable tman/dvt M ADD, MODIFY ALL Yes tman/sdr M ADD, MODIFY ALL Not Applicable tman/mbs M ADD, MODIFY ALL Yes Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command None Event Parameters Mandatory/Optional Supported Values Provisioned Value ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.7 IP NAPT Traversal (ipnapt) | Table 75: IP NAPT Traversal Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None Signals Mandatory/Optional Used in command Duration Provisioned Value Latching (ipnapt/latch) M ADD, MODIFY Not Applicable Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value NAPT Traversal Processing (napt) M ALL Not Applicable Events Mandatory/Optional Used in command None Event Parameters Mandatory/Optional Supported Values Provisioned Value ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 37 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.8 MPLS (mpls) | Table 76: MPLS Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value mpls/stack M ADD, MODIFY ALL Not Applicable (see note) Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command None Event Parameters Mandatory/Optional Supported Values Provisioned Value ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None NOTE: "Not applicable" means that in case the mpls/stack property is absent, the MG shall not apply any MPLS label to the given termination/stream. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.9 VLAN (vlan) | Table 77: VLAN Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value VLAN tags (vlan/tags) O ADD, MODIFY ALL (see note) Yes Ethernet priority (vlan/pri) O ADD, MODIFY ALL Yes Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command None Event Parameters Mandatory/Optional Supported Values Provisioned Value ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None NOTE: "ALL" means: • value range "0 to 4 095" of property VLAN tags used for VLAN tagging; • value "4 096" of property VLAN tags defines the semantic for "no VLAN tagging". ETSI ETSI TS 183 018 V3.5.2 (2010-01) 38 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.10 MGC Information (mgcinfo) | Table 78: MGC Information Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value ALL M ADD, MODIFY, AUDITVALUE ALL Not Applicable Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command None Event Parameters Mandatory/Optional Supported Values Provisioned Value ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.11 Inactivity Timer (it) | Table 79: Inactivity Timer Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command Inactivity Timeout (it/ito) M MODIFY, NOTIFY Event Parameters Mandatory/Optional Supported Values Provisioned Value Maximum Inactivity Time (mit) O ALL Yes ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value None Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 39 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.12 Segmentation (seg) | Table 80: Segmentation Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value MGSegmentation TimerValue (seg/ MGSegmentationTimerValue) M AUDITVALUE, MODIFY ALL YES MGCSegmentation TimerValue (seg/ MGCSegmentationTimerValue) M AUDITVALUE, MODIFY ALL YES MGMaxPDUSize (seg/ MGMaxPDUSize) M AUDITVALUE, MODIFY ALL YES MGCMaxPDUSize (seg/ MGCMaxPDUSize) M AUDITVALUE, MODIFY ALL YES Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command None Event Parameters Mandatory/Optional Supported Values Provisioned Value ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional 459 M ETSI ETSI TS 183 018 V3.5.2 (2010-01) 40 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.13 RTP (rtp) | Table 81: RTP Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None - - - - Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value - - - - Events Mandatory/Optional Used in command None Statistics Mandatory/Optional Used in command Supported Values Packets Sent (rtp/ps) M ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Packets Received (rtp/pr) M ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Packet Loss (rtp/pl) M ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Jitter (rtp/jit) O ADD, AUDITVALUE, SUBTRACT, MODIFY ALL Delay (rtp/delay) O ADD, AUDITVALUE, SUBTRACT, MODIFY ALL Octets sent (rtp/os) (see note 1) O ADD, AUDITVALUE, SUBTRACT, MODIFY ALL Octets received (rtp/or) (see note 2) O ADD, AUDITVALUE, SUBTRACT, MODIFY ALL Error Codes Mandatory/Optional None - NOTE 1: Inherited statistic from nt package. Value of rtp/os must be identical to nt/os (see clause E.12.5.2, ITU-T Rec. H.248.1 [1]). NOTE 2: Inherited statistic from nt package. Value of rtp/or must be identical to nt/or (see clause E.12.5.2, ITU-T Rec. H.248.1 [1]). |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.14 Application Data Inactivity Detection (adid) | Table 82: Application Data Inactivity Detection Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None Signals Mandatory/Optional Used in command Duration Provisioned Value None Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value Events Mandatory/Optional Used in command IP Flow Stop Detection (adid/ipstop) M ADD, MODIFY, NOTIFY Event Parameters Mandatory/Optional Supported Values Provisioned Value Detection Time (dt) O ALL Yes Direction (dir) O ALL Yes ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value None Statistics Mandatory/Optional Used in command Supported Values None Error Codes Mandatory/Optional None ETSI ETSI TS 183 018 V3.5.2 (2010-01) 41 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.15 IP Domain Connection (ipdc) | Table 83: IP domain connection package Properties Mandatory/Optional Used in command Supported Values Provisioned Value IP Realm Identifier (iIpdc/realm) M ADD, MODIFY ALL Yes Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value - - - - Events Mandatory/Optional Used in command None - - Event Parameters Mandatory/Optional Supported Values Provisioned Value - - - - ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value - - - - Statistics Mandatory/Optional Used in command Supported Values None - - - Error Codes Mandatory/Optional No - NOTE: The ITU-T Rec. H.248.41 [16] package definition does not specify a length limit for the ipdc/realm string. The maximum length is given by RFC 1123 [29] in case of a domain name format used for the property. If it is not a domain name format, then the maximum size should be up to 255. In case the MGC uses an ipdc/realm property exceeding the above defined length limitation, the MG shall reply with an error descriptor using error code #410: "Incorrect identifier". |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.16 Media Gateway Overload Control (ocp) | Table 84: Media Gateway Overload Control Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None - - - - Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value - - - - Events Mandatory/Optional Used in command MG_Overload (ocp/mg_overload) (see note) M MODIFY, NOTIFY (see note) Event Parameters Mandatory/Optional Supported Values Provisioned Value None - - - ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value None - - - Statistics Mandatory/Optional Used in command Supported Values None - - - Error Codes Mandatory/Optional None - NOTE: When the MG is overloaded, overload Events may be sent either only following the first ADD.request which creates a new Context, or following all ADD.request commands (see ITU-T Rec. H.248.11 [15] Corrigendum 1). These two options result in different normalisations of the overload event rate as an indicator of the level of MG overload (see clause 5.17.2.3). ETSI ETSI TS 183 018 V3.5.2 (2010-01) 42 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.17 Hanging Termination Detection (hangterm) | Table 85: Hanging Termination Detection Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None - - - - Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value - - - - Events Mandatory/Optional Used in command Termination Heartbeat (hangterm/thb) M ADD, MODIFY, NOTIFY Event Parameters Mandatory/Optional Supported Values Provisioned Value Timerx (timerx) O 0,1 up Yes ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value - - - - Statistics Mandatory/Optional Used in command Supported Values None - - - Error Codes Mandatory/Optional No - |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.18 Statistic Conditional Reporting (scr) | Table 86: Statistic Conditional Reporting Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value None - - - - Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value - - - - Events Mandatory/Optional Used in command Conditional Reporting, (scr/cr) M ADD, MODIFY, NOTIFY Event Parameters Mandatory/Optional Supported Values: Provisioned Value Statistic Identifier (si) M ALL YES Duration (dur) O ALL YES Period (per) O ALL YES Maximum (max) O ALL YES Minimum (min) O ALL YES Normal (nor) O ALL YES Request timestamp (rt) O ALL YES Value Type (typ) O ALL YES Target Value (val) O ALL YES Deviation (dev) O ALL YES Compliance (com) O ALL YES Direction (dir) O ALL YES ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Statistic Identifier (si) M ALL - Value (val) M ALL - Statistics Mandatory/Optional Used in command Supported Values None - - - Error Codes Mandatory/Optional None - ETSI ETSI TS 183 018 V3.5.2 (2010-01) 43 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.19 IP Realm Availability (ipra) | Table 86a: IP Realm Availability Package Properties Mandatory/Optional Used in command Supported Values Provisioned Value Available Realms, (ipra/ar) M AUDITVALUE ALL Not Applicable Signals Mandatory/Optional Used in command Duration Provisioned Value None - - - Signal Parameters Mandatory/Optional Supported Values Duration Provisioned Value - - - - Events Mandatory/Optional Used in command Available Realms Changed, (ipra/arc) M MODIFY, NOTIFY Event Parameters Mandatory/Optional Supported Values: Provisioned Value - - - - ObservedEvent Parameters Mandatory/Optional Supported Values Provisioned Value Newly Available Realms (nar) O (see note) ALL Not applicable Newly Unavailable Realms (nur) O (see note) ALL Not applicable Statistics Mandatory/Optional Used in command Supported Values None - - - Error Codes Mandatory/Optional None - NOTE: Although the ObservedEvent Parameters ipr/nar and ipra/nur are optional as such, at least one parameter must be included in a ipra/arc notification command. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.20 RTP Application Data (rtpad) | Table 86b: RTP Application Data Package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: None - - - Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - - Events Mandatory/ Optional Used in command: None Statistics Mandatory/ Optional Used in command: Supported Values: RTP payload octets sent, (rtpad/payloados) M ADD, AUDITVALUE, SUBTRACT ALL O MODIFY RTP payload octets received, (rtpad/payloador) M ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Error Codes Mandatory/Optional None - ETSI ETSI TS 183 018 V3.5.2 (2010-01) 44 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.21 Latch Statistics (lstat) | Table 86c: Latch Statistics Package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: None - - - Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - - Events Mandatory/ Optional Used in command: None Statistics Mandatory/ Optional Used in command: Supported Values: Discarded packets, (lstat/dp) M ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Error Codes Mandatory/Optional None - |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.22 Void | Table 86d: Void |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.14.2.23 Traffic Policing Statistics (tmanr) | Table 86e: Traffic Policing Statistics Package Properties Mandatory/ Optional Used in command: Supported Values: Provisioned Value: None - - - - Signals Mandatory/ Optional Used in command: Duration Provisioned Value: None - - - Signal Parameters Mandatory/ Optional Supported Values: Duration Provisioned Value: - - - - Events Mandatory/ Optional Used in command: None Statistics Mandatory/ Optional Used in command: Supported Values: Discarded packets, (tmanr/dp) M ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Peak-rate violating packets, (tmanr/pvp) O ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Peak-rate violating octets, (tmanr/pvo) O ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Sustained-rate violating packets, (tmanr/svp) O ADD, AUDITVALUE, SUBTRACT ALL O MODIFY Sustained-rate violating octets, (tmanr/svo) O ADD, AUDITVALUE, SUBTRACT ALL O MODIFY ETSI ETSI TS 183 018 V3.5.2 (2010-01) 45 Error Codes Mandatory/Optional None - NOTE: The statistic tmanr/dp is mandatory because independent of the applied policing mechanism. The other four statistics are optional because dependent on peak- or sustained-rate policing. 5.15 Mandatory support of SDP and annex C information elements Elements listed as mandatory shall be supported by MGC and MG but does not have to be present in all commands containing SDP. Details of which elements are included in each command are provided in clause 5.18. Table 87: Supported SDP Information Elements SDP Information Element Mandatory/optional Description Protocol version "v=" line Mandatory The value must always be equal to zero: v=0 Connection "c=" line Mandatory The network type must always be "IN". The address type value must be "IP4" or "IP6". The connection address value may be underspecified with CHOOSE wildcard ("$"). Media "m=" line Mandatory There are four fields (or SDP values) <media>, <port>, <proto> and <fmt> in the "m=" line (see RFC 4566 [28]; note 3). The "m=" line may be omitted from SDP (see note 6). Media type <media> Mandatory if "m=" line included "Media-type agnostic" mode: "-" may be used for the media value (see also clause G.2.2 of [i.18]). In case MG is media agnostic and MGC specifies any other media type than "-", the MG shall reject the command with error code 515. "Media-type aware" mode: The media value shall be specified in case of media-aware interworking (see note 2). In case MG is media aware but does not support the requested media type the MG shall reject the command with error code 515. Transport port <port> Mandatory if "m=" line included L4-port aware mode: The port value may be underspecified with CHOOSE wildcard ("$"). L4-port agnostic mode: Not supported. Transport protocol <proto> Mandatory if "m=" line included "Transport-protocol agnostic" mode: "-" may be used for the proto value. "Transport-protocol aware" mode: udp Allow only L4 protocol = UDP (see note 8). tcp or TCP Allow only L4 protocol = TCP µ (see note 9). TCP/MSRP Message service using RFC 4975 [36]. RTP/AVP RTP profile according RFC 3551 [38] Allow only L4 protocol = UDP (see note 1). udptl Allow only L4 protocol = UDP. - No transport protocol specific behaviour is required by the MG. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 46 SDP Information Element Mandatory/optional Description Mode misalignments: In case MG is transport aware (i.e. "transport-protocol aware" and "L4-port aware") but does not support the requested transport protocol the MG shall reject the command with error code 449. In case MG is transport agnostic and MGC specifies any other transport protocol than "-", the MG shall reject the command with error code 449. If MG supports both transport protocol agnostic and transport protocol aware behaviours, then it shall accept "-" or a valid value in the transport protocol field. A transport protocol aware MG may not support transport agnostic behaviour and may reject a request with a transport protocol value"-", with error code 449 (see also clause G.3 of [i.18]). Media format <fmt> Mandatory if "m=" line included. "Media format aware" mode: Various values may be used for media-format aware interworking (e.g. transcoding; see clause 5.17.1.14) (see note 2). In case MG is media-format aware but does not support the requested media format the MG shall reject the command with error code 449. "Media format agnostic" mode: "-" may be used for the format list value. Mode misalignments: In case MG is media format aware but does not support the requested format list value the MG shall reject the command with error code 449. In case MG is media format agnostic and MGC specifies any other media format than "-", the MG shall reject the command with error code 449. If MG supports both media format agnostic and media format aware behaviours, then it shall accept "-" or a valid value in the format list value field. A media format aware MG may not support media format agnostic behaviour and may reject a request with a media format list value"-", with error code 449 (see also clause G.3 of [i.18]). Bandwidth "b=" line Mandatory MUST not be used without a "m=" line. The modifier value must always be "AS". This implies that the bandwidth-value represents the ""maximum bandwidth" (see clause 5.8 in RFC 4566 [28]). The bandwidth-value relates therefore to the peak bitrate (see note 7). The bandwidth-value value defines the IP layer bandwidth for the specific H.248 Stream (see notes 4 and 5). For RTP flows, where RTCP resources are reserved together with the RTP resources using the "RTP Specific Behaviour" property of the Gate Management package (gm) property, the bandwidth value will include the bandwidth used by RTP and RTCP together. NOTE 1: Even if the transport value is RTP, the "RTP Specific Behaviour" property of the Gate Management package (gm) shall be used to indicate whether RTCP resource reservation is also requested. NOTE 2: For Ia profile versions 2 and higher RFC 4566 [28] shall be used as basis. RFC 4566 [28] enables "-" as a valid character (Ia profile version 1 uses RFC 2327 [i.3], which does not allow the "-" in place of media type, transport and media format fields. However in the scope of Ia profile version 1 this was considered as an admitted SDP extension). NOTE 3: RFC 4566 [28] obsoleted RFC 2327 [i.3], but the ABNF grammar did slightly change for the "m=" line: a) RFC 2327 [i.3]: m=<media> <port> <transport> <fmt list>. b) RFC 4566 [28]: m=<media> <port> <proto> <fmt> ... There is a syntactical change for the last two fields, but the semantical meaning is unchanged. See also ITU-T Rec. H.248.49 [23], appendix I "Comparison of SDP variants between RFC 4566 [28] and RFC 2327 [i.3]" and in particular: table I.7/H.248.49 "RFC 4566 [28] versus RFC 2327 [i.3] - SDP specification - "m=" line". ETSI ETSI TS 183 018 V3.5.2 (2010-01) 47 SDP Information Element Mandatory/optional Description NOTE 4: This semantic is consistent for RTP traffic (see clause 6.2 of RFC 3550 [i.8]) and non-RTP traffic (see clause 5.8 of RFC 4566 [28]). NOTE 5: It has to be noted that Ia profile version 1 defines a different semantic (see table 81 in ES 283 018 [22]) defined, which incorporates also layer 2 bitrate. A transformation between both "b=" line usages (in case of IP-over-L2) is not straightforward because the transformation parameters are based on L2-PCI and the IP packet rate. The L2-PCI is typically constant for a dedicated L2 technology (like IP-over-IEEE 802.3 [i.9]), but the packet rate is application-specific. E.g. the IP packet rate is usually unknown at Ia for media-agnostic IP-to-IP interworking. NOTE 6: The "m=" and "b=" lines may be omitted in certain procedures, which are further described in clause 5.17.1.11. NOTE 7: The unit for the bandwidth-value (peak bitrate) is "kbit/s". The unit for the peak data rate (tman/pdr) is "byte/s". The "b=" line is not providing any information about the traffic characteristic, i.e. whether the traffic flow has a Constant BitRate (CBR) or Variable BitRate (VBR). The bandwidth-value is thus independent of the traffic characteristic and relates to the peak bitrate for CBR and VBR traffic (see also clause 5.17.1.5). NOTE 8: Parameter "udp" is introduced by RFC 4566 [28] but not yet registered by IANA (see http://www.iana.org/assignments/sdp-parameters). NOTE 9: Upper case TCP is defined by RFC 4145 [i.21] and registered by IANA. Lower case tcp was introduced by Ia v1 and is allowed for backwards compatibility. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.16 Optional support of SDP and annex C information elements | NOTE: "Annex C" relates to H.248.1 annex C "Tags for Media Stream Properties". Annex C information elements are not required in H.248 text encoding mode. Table 88 summarizes the "optional" SDP information elements, according their specific usage according clause 7.1.8 of ITU-T Recommendation H.248.1 [1]. Their usage may depend on the direction from MGC towards MG or vice versa. Details of which elements are included in each command are provided in clause 5.18. Table 88: Optional SDP Information Elements SDP Information Element Optional/mandatory Description Origin "o=" line Optional for MGC, Mandatory for MG The origin line consists of six fields (<username>, <sess-id>, <sess-version>, <nettype>, <addrtype> and <unicast-address>). The MGC is not required to supply this line but shall accept it (see clause 7.1.8 of ITU-T Recommendation H.248.1 [1]). The MG should populate this line as follows, e.g. o=- 0 0 IN IP4 11.9.19.65; or use the value received from the MGC. Session Name "s=" line Optional for MGC, Mandatory for MG The session name "s=" line contains a single field (<session name>). The MGC is not required to supply this line but shall accept it (see clause 7.1.8 in ITU-T Recommendation H.248.1 [1]). The MG should populate this line as follows, e.g. s=-; or use the value received from the MGC. Timing "t=" line Optional for MGC, Mandatory for MG The time "t=" line consists of two fields (<start time> and <stop time>). The MGC is not required to supply this line but shall accept it (see clause 7.1.8 in ITU-T Recommendation H.248.1 [1]). The MG should populate this line as follows, e.g. t=0 0; or use the value received from the MGC. Attribute "a=" line Optional for MGC, Recommended for MG 1) Application "RTCP transport address control": The attribute "a=rtcp" line may either contain (a=rtcp: <port>) or (a=rtcp: <port> <network type> <address type> <connection address>) when the "a=" line is used for RTCP transport port and optionally network address transmission. The MGC shall supply the "a=rtcp" line in the RD when non-default RTCP network address or transport port values are used by the peer media entity. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 48 SDP Information Element Optional/mandatory Description Optional for MGC, optional for MG 2) Application "Media-aware interworking (transcoding)": The "a=" line provides the complementary information for the "m=" line (see table 87) with regards to a specified media type/format (e.g. an optional SDP "a=ptime" line for a particular media format). For a dynamic RTP payload type, for each media information on the codec type shall be provided in a separate SDP "a=rtpmap"line and possibly additional SDP "a=fmtp"-line(s). |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17 Overview of Procedures | Details of Session Dependent Procedures are provided in clauses 5.18. Details of Session Independent Procedures are provided in clauses 5.19 and 5.20. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1 Overview of Session Dependent Procedures | The general procedures are related to session-dependent (also known as H.248 call-dependent) procedures. There are procedures in following categories: • Address allocation and translation is in scope of clauses 5.17.1.2. The adaptation of addresses (latching) is the subject of clause 5.17.1.3. • Session-dependent policing is applicable to this profile. Different policing types are classified in Appendix I of ITU-T Recommendation Q.3303.2 [14]. The specific types of address policing and traffic policing are in scope of clauses 5.17.1.1 and 5.17.1.5 respectively. Media type policing is discussed in clause 5.17.1.8. • QoS support mechanisms are discussed in clause 5.17.1.4. • Measurement and reporting of statistics are discussed in clause 5.17.1.6. • RTCP handling (e.g. IP port allocation rules for RTCP) is discussed in clause 5.17.1.7. • Detection of inactive bearer connections is in scope of clause 5.17.1.9. • IP Realm/Domain Indication is discussed in clause 5.17.1.10. • Two-Stage BGF Resource Reservation is discussed in clause 5.17.1.11. • Detection of hanging H.248 Terminations is discussed in clause 5.17.1.12. • Real Time Statistics Reporting in clause 5.17.1.13. • Transcoding is discussed in clause 5.17.1.14. • Media-path coupled QoS signalling is discussed in clause 5.17.1.15. • VPN identification is discussed in clause 5.17.1.16. • Topology hiding is discussed in clause 5.17.1.17. NOTE: Annex D of [i.18] provides an example IP processing model for an H.248 (IP, IP) Context, indicating the IP packet processing functions behind above session-dependent procedures. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.1 Gate control | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.1.1 Streams, Terminations and Gates | The realization of a gate requires two ephemeral terminations. An ephemeral termination sources and/or sinks one or more media streams. Gates are direction and stream dependent. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 49 In this profile, RTP traffic shall be controlled through a single H.248 stream, representing both the RTP and RTCP flows, if the RTP Specific Behaviour property of the Gate Management package is set to ON. In such a case, when the MG is requested to allocate a port for an RTP flow, a consecutive port for the associated RTCP flow is automatically allocated (see also clause 5.17.1.7). In this case, monomedia sessions require one bidirectional H.248 stream on a termination, while a multi-media sessions (e.g. audio and video) would require multiple H.248 streams on a termination (one stream per media type). |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.1.2 Assignment of L3 address and L4 port values | The H.248 base protocol enables the MGC to choose the IP address and port on which a termination will receive media flows. In addition, the Gate Management package enables the MGC to explicitly provide the following information: 1) expected IP source address and port of received packets; 2) IP source address and port of sent packets. The relationship between H.248 descriptors in this Profile and the addresses used in packets sent and received by the gate is indicated in table 89. Figure 2a illustrates the used naming conventions for the IP transport connection endpoints in the BGF and remote IP node. Table 89: Relation between Packet Direction, IP Address/Port and H.248 Descriptor/Information Packet direction IP Address/ L4 Port Source of Information for Transport Address values Received by termination Source: • RS(A) • RS(P) The source of information for the expected remote source transport address RS(A,P) value is dependent on the usage of remote source filtering and hosted NAP(T) traversal as per table 89a. Destination: • LD(A) • LD(P) Local destination transport address LD(A,P): Local Descriptor. Sent by termination Source: • LS(A) • LS(P) Local source transport address LS(A,P): 1. Availability of LS information due to explicit setting of local source transport address: LocalControl Descriptor/gate management/local source address + local source port; or, if not present: 2. Availability of LS information in H.248 Local Descriptor SDP: Source address not explicitly enforced/signalled via "gm" package. The source address is determined from the local SDP (which implies a symmetrical local network address, i.e. LD(A) = LS(A)). Destination: • RD(A) • RD(P) The source of information for the remote destination transport address RD(A,P) value is dependent on the usage of hosted NAP(T) traversal as per table 89b. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 50 Table 89a: Expected Remote Source Transport Address Expected remote source transport address RS(A,P): Hosted NA(P)T Traversal No Yes Filtering on Remote Source Address(es) No As no source filtering activated no specific RS(A,P) is expected. The BGF may determine actual RS(A) and RS(P) values by monitoring incoming IP packets. The expected remote source transport address is determined by the NAPT traversal process as described in [9]. Even if no filtering is ordered, the NAPT traversal process implies source filtering on the transport address after latching has occurred. Yes Alt 1. LocalControl Descriptor/gate management/remote source address mask AND/OR remote source port or remote source port range is used to determine the expected RS(A) and RS(P) values, which allows for the peer IP node to use asymmetric network address (RS(A) ≠ RD(A)). Alt 2. Combination of gate management and Remote Descriptor, which assumes symmetrical remote network address (RS(A) = RD(A)). 1st stage (before latching): Same as in cell to the left. 2nd stage (after latching): Same as in above cell. Table 89b: Source of Information for the Remote Destination Transport Address Remote destination transport address RD(A,P): Hosted NA(P)T Traversal No Yes Source of information The remote destination transport address is determined by the Remote Descriptor. The remote destination transport address is determined by the NAPT traversal process as described in [9]. This implies a symmetrical remote network address, i.e. RD(A) = RS(A). ETSI ETSI TS 183 018 V3.5.2 (2010-01) 51 Bidirectional IP Transport Connection H.248 Media Gateway Peer Entity (e.g. IP host, IP next hop, H.248 MGC) Perspective DA IP Header SA DP SP L4 Header LD(A) LD(P) LS(A) LS(P) IP Transport Connection Endpoint RS(A) RS(P) RD(A) RD(P) Local Source Remote Destination Local Destination Remote Source IP Transport Connection Endpoint SA DA SP DP L4 Header IP Header LS(P) LS(A) … … RD(P) L4 RD(A) L3 … L2 … L1 LD(P) LD(A) … … LD(P) LD(A) … … RS(P) L4 RS(A) L3 … L2 … L1 LS(P) LS(A) … … Stream S1 Stream S1 Context C1 b) Protocol Layering a) Endpoint Naming Convention Legend for Names: LD Local Destination LS Local Source RD Remote Destination RS Remote Source Legend for Addresses: DA Destination Address DP Destination Port SA Source Address SP Source Port L3 Address L4 Port … Figure 2a: Naming conventions for IP transport connection endpoints (from BGF perspective; in line with H.248.1 conventions) NOTE: H.248.1 may in the future provide a general overview of IP transport connection endpoints similar to figure 2a. Figure 2a will be then replaced by a reference to H.248.1. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.1.3 Opening and closing of gates | Opening and closing gates is achieved by setting the Stream mode parameter of the associated termination(s) to the appropriate values. Subtracting a termination from a context also closes the gate for all H.248 streams in the termination. In the context of conversational services, an active session requires that the gates in both directions be opened (terminations in bi-directional mode). |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.1.4 Filtering due to conditions on L3 address and/or L4 port values | Filtering on the IP source address and/or port might be implemented using the Gate Management package, or using the SDP information in the Remote Descriptor. In case the filtering is done based on the Remote Descriptor, the activation/deactivation of the filtering is configured in the MG. If the Gate Management package is used, it shall override the configured value in the MG. NOTE: It should be noticed that the IP source address and port may not always be available to the MGC. When SIP signalling is used, the session description does not contain this information (i.e. according to RFC 3264 [7], the IP address and port present in an SDP offer indicate nothing about the source IP address and source port of RTP and RTCP packets that will be sent by the offerer). Any other protocol that uses SDP as a session description mechanism (e.g. RTSP) has the same constraints. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 52 In such configurations, the Gate Management Package may be used as follows: • in an IPv6 environment, the Source Address Mask property contains the 64 bits prefix of the IP address that is set in the termination's Remote Descriptor; • in an IPv4 environment, the Source Address Mask property contains the IP address that is set in the termination's Remote Descriptor, except that a number of trailing digits may be wildcarded; • in both cases, Source Port Filtering should not be activated. The gate concept, together with H.248 Stream/Termination handling, is further illustrated in annex A of [i.18]. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.2 Allocation and translation of IP addresses, ports and versions (NAPT-PT) | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.2.1 Allocation methods | The procedures of this clause support the following NAPT-PT functionality: • NAPT-PT functionality with "double" addresses and ports translation (both source and destination addresses and ports are translated; example see clause 5.17.1.2.2); • or optional NAPT-PT functionality with "single" address and port translation (either source or destination address and port translation; (see also clause 5.17.1.2.3)) - applicable if the BGF has router functionality, or direct L2 connectivity with user terminals. The H.248 base protocol enables the MGC to either choose the addresses and ports associated with a termination or to request the MG to allocate these IP addresses and ports. NAPT control on destination addresses and ports is achieved by setting the Local and Remote Descriptors according to the following principles: • The IP and port address in the Remote Descriptors are set by the MGC according to the information received in call/session signalling (e.g. SDP in SIP INVITE and 200 OK). • The address and port in the Local Descriptor are selected by the MG within the indicated IP address realm from MGC side (see also below). If the BGF has router functionality, or direct L2 connectivity with the user terminals, the address and port of the Local Descriptor towards the private network may optionally be set according to the following principles: • The IP and port address in the Local Descriptor towards the private network is provided by the MGC (instead of being selected by the MG). The MGC shall copy the Remote Descriptor of the public network into the Local Descriptor towards the private network (see also clause 5.17.1.2.4.1). The MGC has the ability to choose the address space in which the MG allocates an IP address. This is achieved by setting the IP realm identifier in the IP Domain Connection package to the appropriate value (see clause 5.17.1.10). The association of dedicated "IP address spaces" (also known as "IP address realms" or briefly "IP realms", see RFC 2663 [8]) with the IP realm identifier requires a mutual agreement between MGC and MG. This is realized via provisioning, thus beyond the scope of this Profile. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.2.2 "Double" NA(P)T | The term "double" NA(P)T relates to the translation of source and destination address information: • "double" NAT = translation of 2-tuple (DA, SA) is not supported by this profile (because it would require the L4-port agnostic mode); • "double" NAPT = translation of 4-tuple (DA, SA, DP, SP), i.e. L4-port aware mode. EXAMPLE: (here "double" NAPT): Figure 3 provides an example of "double" network address and port translation, where a session is to be established between IPv4 addresses 10.140.120.10 (private address) and 156.106.192.33 (public address). ETSI ETSI TS 183 018 V3.5.2 (2010-01) 53 H.248 IP-to-IP Context C1 T1(S1) T2(S1) Stream Descriptor for T1 LS(P) LS(A) … … RD(P) L4 RD(A) L3 … L2 … L1 LD(P) LD(A) … … RS(P) RS(A) … … LD(P) LD(A) … … RS(P) L4 RS(A) L3 … L2 … L1 LS(P) LS(A) … … RD(P) RD(A) … … Stream S1 Stream S1 Context C1 a) H.248 Context model Local Descriptor: LD(A) = 10.200.30.20 LD(P) = 334 Remote Descriptor: RD(A) = 10.140.120.10 RD(P) = 222 c) Protocol Layering Stream Descriptor for T2 Local Descriptor: LD(A) = 139.100.0.121 LD(P) = 334 Remote Descriptor: RD(A) = 156.106.192.33 RD(P) = 556 b) Stream Descriptors NOTE: There is only one H.248 Stream (S1) per Termination in this example. Figure 3: Network Address and Port Translation (NAPT) - Example for bidirectional ("double") translation |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.2.3 "Single" NA(P)T | The term "single" NA(P)T relates to the translation of either source-only or destination-only address information: • "single" NAT = translation of 1-tuple (SA) or (DA) is not supported by this profile (because it would require the L4-port agnostic mode); • "single" NAPT = translation of 2-tuple (SA, SP) or (DA, DP), i.e. L4-port aware mode. Example (here "single" NAPT on (DA, DP)-tuple elements): For "single" network address and port translation applications, the T1 Local Descriptor address and port in figure 3 has to be changed to 156.106.192.33:556 (equal to the T2 Remote Descriptor address and port). T1-to-T2 IP flow direction: • The (DA, DP)-tuple values will be then not changed (called "destination NAPT-less"), whereas the (SA, SP)-tuple values are translated ("source NAPT-full" mode). = single NAPT. T2-to-T1 IP flow direction: • The (DA, DP)-tuple values and the (SA, SP)-tuple values are both translated ("source and destination NAPT-full" mode). = double NAPT. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 54 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.2.4 NA(P)T-less case | See also clause H.3 of [i.18]. 5.17.1.2.4.1 NA(P)T-less B2BIH mode For NA(P)T-less applications, the T1 Local Descriptor address and port in figure 3 has to be changed to 156.106.192.33: 556 (equal to the T2 Remote Descriptor address and port) and the T2 Local Descriptor address and port in figure 3 has to be changed to 10.140.120.10: 222 (equal to the T1 Remote Descriptor address and port). Further aspects from H.248 control perspective: • There is either a "source and destination NAT-less" mode (briefly NAT-less). • Or a "source and destination NAPT-less" mode (briefly NAPT-less). • All other combinations may be mapped on NA(P)T-full scenarios (e.g. L3 NAT-less but L4 port translation). • The NAT-less B2BIH and NAPT-less B2BIH mode using both the same H.248 control method, i.e. the RD(A,P) address value from the H.248 RD is copied by the MGC in the LD(A,P) value of the H.248 LD of the other H.248 IP Termination. This can only be done once the RD of both terminations are known to the MGC and the profile thus allows for a LD to be absent in the ADD request command. 5.17.1.2.4.2 NA(P)T-less IPR mode See annex H of [i.18], not supported by this profile. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.2.5 NA(P)T and explicit Local Source Transport Address settings | NAPT control on source addresses and ports (i.e. source NAPT) is achieved by setting the local source address and local source port properties defined in the Gate Management package to a value that differs from the actual source address of the packets received from the remote entity. The gm package capabilities may be also used for source NAT control only, i.e. without explicit L4 port settings. The explicit local source setting capabilities will lead to an overall: • "single NA(P)T" mode in case of a destination NA(P)T-less mode; or • "double NA(P)T" mode in case of a destination NA(P)T-full mode. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.2.6 Protocol Translation (V4 to V6) | Protocol Translation (NAPT-PT) can be controlled by the MGC by adding to the same H.248 context, two terminations whose media descriptors have different address-type values in the "c=" line. NOTE: It is recommended that the MGC takes precaution if setting up streams with both fully specified and under specified address and/or port towards the same realm in a MG, as this could otherwise lead to conflicting address or port assignments. The exact mechanism for how clashes is avoided is beyond the scope of this profile. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 55 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.3 Support of Hosted NAT Traversal | "Hosted NAT Traversal" relates to "assisting remote NAT/NAPT traversal" for the remote (peer) IP connection endpoints from BGF/SPDF point of view. This relates to an interim NA(P)T device from BGW perspective. The remote IP address information cannot be retrieved from the Remote Descriptor. The "Hosted NAT Traversal" function is controlled by the MGC using the IP NAPT Traversal package (ipnapt). Using the napt package, the MG is requested to perform media latching, i.e. listen for incoming media and latch to the remote address information of that media. When Hosted NAT Traversal is applied to a stream associated with multiple flows (for example RTP and RTCP), the MG shall perform individual latching and/or re-latching on the various flows. This means that an RTP and an RTCP flow of a single stream can be latched to different remote addresses and/or ports. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.4 QoS marking | The Differentiated Services package enables the MGC to control the setting of the DSCP value for all packets leaving the MG. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.4.1 Copying DSCP/ToS values from the ingress to egress | The copy mechanism is specified in Amendment 1 to H.248.52 [17]. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.4.2 Auditing the "Per-Hop Behaviour" | The Per-Hop Behaviour (PHB) concerning "MGC-signalled QoS marking" versus "copying of QoS values" may be explicitly controlled (and audited) using Differentiated Services package version 2, see Amendment 1 to H.248.52 [17]. The Differentiated Services package version 1 does not allow to audit the behaviour, see the note at the end of clause 7.6.1.3 in Amendment 1 to H.248.52 [17]. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.5 Bandwidth control - Reservation, Allocation and Policing | Resources are reserved independently per gate. For each gate, reservation of local resources for handling incoming and outgoing traffic is achieved by setting the appropriate properties in the Local and Remote Descriptors. Only one session description shall be included in each Stream Descriptor. Hence, the ReserveValue and ReserveGroup properties should not be used. The function of bandwidth control (which relates to bit- and byterate control in this profile) is structured in following clauses: • admission control (AC; clause 5.17.1.5.1); • traffic descriptor (clause 5.17.1.5.2); • traffic reservation and allocation (clause 5.17.1.5.3); and • traffic policing (clause 5.17.1.5.4). |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.5.1 Admission Control | Admission Control is defined in RACS for the BGF (MG role) level. There is no concept of a call in H.248 MGs due to the separation of call and bearers in the H.248 model, which means that AC translates in a Context Admission Control (CoAC; see also ITU-T H.Sup6) and Stream Admission Control (StAC) on MG side. The StAC and CoAC is triggered with the first incoming ADD.request Command. At that point a decision is taken whether the new context can be established or not. The StAC is triggered whenever a modification of an existing H.248 context, e.g. in terms of traffic descriptor, is requested. At that point a decision is taken whether the context modification can be accepted or not. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 56 5.17.1.5.1.1 Admission Control in this Profile The BGF AC is based on the requested H.248 stream level usage parameters and already established Contexts. The stream level usage parameters are given by the H.248 Media Descriptor in the ADD.request (and MODIFY.request) commands. The "usage parameters" as input for the AC of this Profile are mainly related to "bandwidth" information (see next clause on "traffic descriptor"). Specific AC algorithms could principally follow a deterministically or a statistically based multiplexing model. Concrete algorithms are implementation specific, thus out of scope of this profile. The result of an admission control (here CoAC or StAC) is either an accept or reject decision. NOTE: Step 2 in figure 4 shows an accept decision, which is implicitly given by the command reply on the ADD.request for the IP termination. A reject decision would be indicated by an appropriate H.248.8 [30] error code in the reply. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.5.2 Traffic Descriptor | A traffic descriptor is the set of traffic parameters that is used to capture the traffic characteristics of an IP flow (see clause 3.2.10/ITU-T Recommendation Y.1221 [i.10]). The traffic parameters for an H.248 Stream of an H.248 IP Termination are direction-independent and given by either: 1) an explicit specification via: - the "b=" line in the SDP description of the Local Descriptor and Remote Descriptor; or - the properties of the Traffic Management package; or 2) an implicit specification via: - the "m=" line in the SDP description of the Local Descriptor and Remote Descriptor (e.g. traffic usage estimate based on SDP media type and further mode of operation information). NOTE: There is no concept of a traffic contract explicitly used in the scope of this Profile version, because specific QoS classes (see ITU-T Recommendation Y.1541 [i.11]) are not signalled per termination. Nevertheless, the "QoS marking" information (see clause 5.17.1.4) could be used for QoS class indications, but such concepts are orthogonal to profile specifications, therefore out of scope of the present document. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.5.3 Bandwidth reservation and allocation | 5.17.1.5.3.1 SDP "b=" line for constant bitrate traffic The amount of required bandwidth for sending packets is expressed using the "b=" line of the SDP description contained in the Remote Descriptors. The amount of required bandwidth for receiving packets is expressed using the "b=" line of SDP description contained in the Local Descriptors or using one of the properties (tman/pdr or tman/sdr) of the traffic management package. 5.17.1.5.3.2 Properties of the Traffic Management package for variable bitrate traffic The Traffic Management package (tman) should be used in case of variable bit rate traffic. There are then two semantics for some tman properties. All properties may be applied for bandwidth policing. The two properties tman/pdr and tman/sdr would be used additionally for bandwidth reservation (see note). NOTE: The property tman/pol indicates whether just reservation is applied ('OFF'), or whether both semantics are in use ('ON'). The semantic for 'OFF' is going beyond the property definition in tman version 1 package. This should be non-controversial because these tman properties may be considered as elements of a traffic descriptor, i.e. information elements used for admission control (besides policing). 5.17.1.5.3.3 Examples for bandwidth reservation See informative annex F of [i.18]. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 57 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.5.4 Bandwidth policing | Policing of incoming traffic can be enabled using the Traffic Management package. Policing on incoming traffic can be set independently for each gate. The properties of the Traffic Management package shall be set to values that are compatible (see note) with the "b=" line value of the Local Descriptor. NOTE: The term "compatible" means that the b-line and the traffic management represent identical bandwidth value with respect to the protocol layer they are defined upon: - Constant bit rate: "b=" line = tman/pdr = tman/sdr. - Variable bit rate: "b=" line = tman/pdr. 5.17.1.5.4.1 Statistics for bandwidth policing Policing of incoming traffic is related to policy rules based on the following: • policy conditions on: - "IP byte-rate" parameter(s) (peak-rate and/or sustainable-rate); and/or - "IP packet size" parameter(s) (see H.248.53 [19]; signalling method not supported by this profile); and • policy actions: - accept conforming IP packet; or - silently discard non-conforming IP packet (in case that profile is not supporting the tmanr package); or - discard non-conforming IP packet and record event by tmanr statistics (see clause 5.17.1.6.3.3). The policy actions are executed per IP packet. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.5.5 Non-specification of tman properties | If no properties of the Traffic Management package are provided, the MG will not perform traffic policing. If only the tman/pol property set to ON is present, traffic policing shall not be done based on the b-line value, i.e. the policing function cannot be activated at this stage. Summary on bandwidth control actions: Table 89ba: Bandwidth control actions in relationship to tman version 1 properties H.248 property usage Semantic tman/pol tman/pdr tman/dvt tman/sdr tman/mbs Bandwidth control actions ON Not sent Not sent (use default) Not sent Not sent (use default) No traffic management. OFF OR not sent (default=OFF) Not sent Sent OR not sent (use default) Not sent Sent OR not sent (use default) No traffic management. OFF OR not sent (default=OFF) Sent Sent OR not sent (use default) Not sent Sent OR not sent (use default) No traffic management The property tman/pdr may be used for bandwidth reservation and allocation in receiving direction in accordance to clause 5.17.1.5.3. OFF OR not sent (default=OFF) Not sent Sent OR not sent (use default) Sent Sent OR not sent (use default) No traffic management The property tman/sdr may be used for bandwidth reservation and allocation in receiving direction in accordance to clause 5.17.1.5.3. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 58 H.248 property usage Semantic tman/pol tman/pdr tman/dvt tman/sdr tman/mbs Bandwidth control actions OFF OR not sent (default=OFF) Sent Sent OR not sent (use default) Sent Sent OR not sent (use default) No traffic management The property tman/pdr or tman/sdr may be used for bandwidth reservation and allocation in receiving direction in accordance to clause 5.17.1.5.3. ON OR not sent (default=ON) Sent Sent OR not sent (use default) Not sent Sent OR not sent (use default) Single stage policer (pdr, dvt) The property tman/pdr may be used for bandwidth reservation and allocation in receiving direction in accordance to clause 5.17.1.5.3. ON OR not sent (default=ON) Not sent Sent OR not sent (use default) Sent Sent OR not sent (use default) Single stage policer (sdr, mbs) The property tman/sdr may be used for bandwidth reservation and allocation in receiving direction in accordance to clause 5.17.1.5.3. ON OR not sent (default=ON) Sent Sent OR not sent (use default) Sent Sent OR not sent (use default) Dual stage policer ((pdr, dvt); (sdr, mbs)) The property tman/pdr or tman/sdr may be used for bandwidth reservation and allocation in receiving direction in accordance to clause 5.17.1.5.3. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.6 Usage metering and statistics reporting | Usage metering is supported by the statistics defined in the network and other packages. Such statistics may be notified to MGC when a stream is removed (and stats explicitly requested by the MGC) or a termination is subtracted from a context (e.g. at the end of a session). They provide information about: 1) information about resource usage, e.g.: - the duration of the time a termination has been in a context; - the traffic volume, e.g. number of octets sent and received; 2) information about Grade of Service (GoS)/Quality of Service (QoS), e.g.: - the packet delay variation or packet transfer delay. The "number of octets" for the case of nt package based measurement is calculated as defined in clause E.11.4 in ITU-T Recommendation H.248.1 [1]). The number of discarded packets due to H.248.43-based, explicit source filtering may be reported on basis of the gm/dp statistic. The number of discarded packets due to H.248.37-based, implicit source filtering may be reported on basis of the lstat/dp statistic. The number of discarded packets and octets due to H.248.53-based, explicit traffic filtering may be reported on basis by the tmanr statistics. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.6.1 Statistics for Media/Transport-agnostic IP packets | The available statistics for the IP streams and terminations of a dedicated context are dependent of the IP-to-IP interworking mode (see clause 3.1). |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.6.2 Traffic Volume related Statistics | Figure 3a provides an overview of different traffic volume related statistics, which might be useful for the various IP-to-IP interworking modes (e.g. media-agnostic, media-aware, transport-protocol agnostic). ETSI ETSI TS 183 018 V3.5.2 (2010-01) 59 5.17.1.6.2.1 General Case The general case relates to Ia profile version 1, i.e. media-agnostic IP-to-IP interworking. Traffic volume related statistics are only accessible by the nt package in profile version 1, and by the nt and rtp package in profile version 2. Profile version 3 provides additional metrics. Application Level Framing Protocol RTP, UDPTL, … L3: IP L2 L4: UDP, TCP, … L1 e.g. audio codec Transport Protocol Network Protocol Application Data Principle protocol stack for H.248 IP Terminations transport overhead reported traffic volume b c d a e rtpad nt & rtp ipocs Figure 3a: Overview of supported statistics - Traffic volume related statistics on different protocol layers 5.17.1.6.2.2 RTP Case (general) "Media-aware" IP terminations with RTP as application level framing protocol may use traffic volume based statistics via the RTP package: • packet granularity: RTP packets sent and/or received. NOTE: Packet level statistics could already provide useful volume measurements in case of RTP packets with constant length. • octet granularity: RTP octets send/received statistics are coupled with nt package statistics, i.e. these statistics are also including RTP padding, RTP header information and UDP transport overheads. Such overhead is excluded in the RTP application data specific statistics (see clause 5.17.1.6.2.3). 5.17.1.6.2.3 RTP Case: application data The RTP Application Data package provides support for explicit octet count statistics concerning media traffic, i.e. the RTP payload volume.5.17.1.6.2.4 IP Case: network layer data The IP layer octets count statistics package provides traffic volume statistics on IP layer for IP version 4 or 6. The H.248 ipocs package (see indication in above Figure 3a) is not supported by this profile version. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 60 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.6.3 Statistics for packet filtering | 5.17.1.6.3.1 Address policing: explicit remote source transport address filtering Filter conditions based on source transport address information for remote IP endpoints may be enabled with Gate Management properties (see also clause 5.17.1.1). The number of discarded packets due to remote source filtering may be reported on basis of the gm/dp statistic. 5.17.1.6.3.2 Address policing: implicit remote transport address filtering due to latching The lstat/dp statistic is used for recording the number of discard packets due to implicit filtering of the latching function. See also clauses 1.3 and 6.6.7.2 in ITU-T Recommendation H.248.37 [9]. 5.17.1.6.3.3 Traffic policing: byte-rate policing See clause 7.4 in ITU-T Recommendation H.248.53 [19]. 5.17.1.6.3.4 Traffic policing: packet-size policing Not supported by this profile specification. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.7 RTCP Handling | Handling of RTCP is already partially addressed by clause 5.17.1.1. This clause defines further procedures for RTCP. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.7.1 RTCP Transport Address Allocation | 5.17.1.7.1.1 Local RTCP IP Transport Address Allocation In line with the recommendations of RFC 3605 [31], separate address or non-contiguous RTCP port numbers (identified via the "a=rtcp" media attribute) shall not be used by the BGF in its LD. Local ports for RTCP are implicitly allocated by the MG whenever instructed to do so by the MGC via the gm/rsb=ON property. The MG must follow the port allocation rules as defined in clause 11 of RFC 3550 [i.8], which results in the allocation of a contiguous port pair for RTP and RTCP within a single stream. If the gm/rsb property is set to OFF, then no RTCP port is allocated in conjunction with an RTP stream. This behaviour is irrespective of the presence of the "a=rtcp" attribute in the related RD. 5.17.1.7.1.2 Remote RTCP Transport Address Representation/Usage, Implicit Allocation of IP Transport Addresses for RTCP RTCP ports are allocated either implicitly or explicitly when support of RTCP is required. RTCP support and RTCP address and port allocation is controlled as by the gm/rsb property and the "a=rtcp" media attribute line in the Remote Descriptor. If RTCP is sent within the same stream as RTP then RTCP port allocation is handled as follows: • gm/rsb=OFF or gm/rsb omitted. - RTCP support is not required. No pinhole is opened for received RTCP packets. No RTCP packets are sent and any received RTCP packets are silently discarded. This is irrespective of whether the "a=rtcp" attribute is present in the Remote Descriptor. • gm/rsb=ON and "a=rtcp" media attribute line not present. - RTCP support is required. A pinhole is opened for received RTCP packets. The MG must follow the port allocation rules as defined in clause 11 of RFC 3550 [i.8], which results in the allocation of a contiguous port pair for RTP and RTCP within a single stream in the Local Descriptor (see clause 5.17.1.7.1.1). RTCP packets are sent to the same address and contiguous port number to the RTP port as specified in the Remote Descriptor. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 61 • gm/rsb=ON and "a=rtcp" media attribute line present. - RTCP support is required. A pinhole is opened for received RTCP packets. The RTCP port and optionally address are explicitly identified by the included "a=rtcp" media attribute line. The MG must follow the port allocation rules as defined in clause 11 of RFC 3550 [i.8], which results in the allocation of a contiguous port pair for RTP and RTCP within a single stream in the Local Descriptor (see clause 5.17.1.7.1.1). If the "a=rtcp" media attribute line in the Remote Descriptor contains an address it is used as destination when sending RTCP packets. The destination port for RTCP packets is always explicitly identified via the "a=rtcp" media attribute line in the Remote Descriptor. 5.17.1.7.1.3 Unsuccessful transport address allocation In line with clause 5.17.1.7.1.1, neither a fully specified RTCP port nor RTCP address are ever used by the MGC in the Local Descriptor. Therefore, unsuccessful port/address allocation can only occur due to there being insufficient resources on the MG to allocate the (contiguous) RTCP port. Unsuccessful scenarios result in the MG responding with H.248 error code #510 ("Insufficient Resources"). |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.7.2 RTP/RTCP to-H.248 Stream Mapping | In line with clause 5.17.1.7.1.1, a single common H.248 stream is always used for RTP and its associated RTCP flow. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.8 RTCP Forwarding | Every RTP session may be accompanied by RTCP control flows. Blocking (by the BGF) of such RTCP packets may violate the end-to-end RTP/RTCP protocol and/or the served applications. However, security threats or specific RTCP reports types may request for dedicated RTCP packet policing rules. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.8.1 Conditions for RTCP packet policing | Conditions for RTCP packet policing are typically based on following n-tupel elements: • IP port for RTCP flow; • RTCP packet type codepoint; • RTCP SSRC codepoint; • RTCP source description information element (e.g. CNAME codepoint); or/and • RTCP block type codepoint in case of RTCP extension reports (XR, HR). |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.8.2 Forwarding of regular RTCP traffic | "Regular" RTCP packets shall be understood in the scope of the present document as packet units with a packet type value equal to a value from the range of {192, 193, 200 to 206}. Thus, regular traffic excludes XR and HR RTCP packets. Regular RTCP packets must be basically forwarded towards the RTP endpoint. Regular RTCP packets are be unambiguously identified by the 3-tupel of {packet type, SSRC, CNAME}. Thus, RTCP packets with e.g. an incorrect {SSRC, CNAME} combination may be blocked. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.8.3 Handling of RTCP XR/HR traffic | Extension reports (XR) and XR-based high resolution reports, - i.e. RTCP reports with a packet type value equal to 207 - carry measurement data from Measurement Points (MP) to Reporting Points (RP). Such measurement reports do not have necessarily an end-to-end significance, their scope may be e.g. limited to a single IP domain or "RTP network segment". The BGF may have to apply dedicated forwarding policy rules for such RTCP packets. Concrete policy rules are for further studies. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 62 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.17.1.9 Media Inactivity | Application data inactivity detection (also known as media inactivity detection) may have multiple, different use cases as cited in ITU-T Recommendation H.248.40 [12] e.g.: • detection of interrupted IP routes; • detection of released RTP endpoints; • detection of hanging SIP/RTP sessions (see note); or • detection of deadlocks in IP latching scenarios. NOTE: The notation of "SIP/RTP session" relates to a SIP-controlled RTP session, which implies a RTP session on MG level and a SIP session on MGC level. There might be a hanging RTP session (leg) or a SIP session (leg). The application of H.248.40 is able to address both failure scenarios. In all use cases, the adid v1 package (with possible different timing and/or direction configurations of the detection logic) is used to report the detected inactivity. The adid/ipstop event is enabled on a per H.248 IP termination basis, i.e. not on H.248 stream level. The BGF monitors all (IP) transport ports associated with the termination. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.