hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.6.1 Default references | Variables of default type can either be declared within an action symbol or within a default symbol as part of an activate statement. Clauses 11.3.1 and 11.3.4 illustrate how a variable called MyDefaultType is declared within GFT. |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.6.2 The activate operation | The activation of defaults shall be represented by the placement of the activate statement within a default symbol (see figure 39). MyDefaultVar := activate(MyTestStep()) MyDefaultVar := activate(MyAltStep ()) MyDefaultVar:=activate(MyAltStep()); GFT Core Figure 39: Default activation |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.6.3 The deactivate operation | The deactivation of defaults shall be represented by the placement of the deactivate statement within a default symbol (see figure 40). If no operands are given to the deactivate statement then all defaults are deactivated. deactivate(MyDefaultVar) deactivate(MyDefaultVar) deactivate(MyDefaultVar); GFT Core Figure 40: ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.7 Configuration operations | Configuration operations are used to set up and control test components. These operations shall only be used in GFT test case, function, and altstep diagrams. The mtc, self, and system operations have no graphical representation; they are textually denoted at the places of their use. GFT does not provide any graphical ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.7.1 The Create operation | The create operation shall be represented within the create symbol, which is attached to the test component instance which performs the create operation (see figure 41). The create symbol contains the create statement. MyComp:=MyCType.create MyComp:=MyCType.create; GFT Core Figure 41: Create operation |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.7.2 The Connect and Map operations | The connect and map operations shall be represented within an action box symbol, which is attached to the test component instance which performs the connect or map operation (see figure 42). The action box symbol contains the connect or map statement. connect(MyComp:PortA, mtc:PortM); map(MyComp:PortB, system:PortC) co... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.7.3 The Disconnect and Unmap operations | The disconnect and unmap operations shall be represented within an action box symbol, which is attached to the test component instance which performs the disconnect or unmap operation (see figure 43). The action box symbol contains the disconnect or unmap statement. disconnect(MyComp:PortA, mtc:PortM); unmap(MyComp:Por... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.7.4 The Start test component operation | The start test component operation shall be represented within the start symbol, which is attached to the test component instance that performs the start operation (see figure 44). The start symbol contains the start statement. MyComp.start(MyCompBehaviour()) MyComp.start(MyCompBehaviour()); GFT Core Figure 44: Start o... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.7.5 The Stop execution and Stop test component operations | TTCN-3 has two stop operations: The module control and test components may stop themselves by using a stop execution operations, or a test component can stop other test components by using stop test component operations. The stop execution operation shall be represented by a stop symbol, which is attached to the test c... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.7.6 The Done operation | The done operation shall be represented within a condition symbol, which is attached to the test component instance, which performs the done operation (see figure 48). The condition symbol contains the done statement. MyComp.done MyComp.done; GFT Core Figure 48: Done operation The any and all keywords can be used for t... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8 Communication operations | Communication operations are structured into two groups: 1) sending operations: a test component sends a message (send operation), calls a procedure (call operation), replies to an accepted call (reply operation) or raises an exception (raise operation). 2) receiving operations: a component receives a message (receive ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.1 General format of the sending operations | All sending operations use a message symbol that is drawn from the test component instance performing the sending operation to the port instance to which the information is transmitted (see figure 49). Sending operations consist of a send part and, in the case of a blocking procedure-based call operation, a response an... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.2 General format of the receiving operations | All receiving operations use a message symbol drawn from the port instance to the test component instance receiving the information (see figure 50). A receiving operation consists of a receive part and an optional assignment part. The receive part: 1) specifies the port at which the operation shall take place; 2) defin... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.3 Message-based communication | |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.3.1 The Send operation | The send operation shall be represented by an outgoing message symbol from the test component to the port instance. The optional type information shall be placed above the message arrow. The (inline) template shall be placed underneath the message arrow (see figures 52 and 53). MyTemplate(5,MyVar) MyType MyPort MyPort.... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.3.2 The Receive operation | The receive operation shall be represented by an incoming message arrow from the port instance to the test component. The optional type information shall be placed above the message arrow. The (inline) template shall be placed underneath the message arrow (see figures 54 and 55). MyPort MyTemplate(5,MyVar) MyType MyPor... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.3.2.1 Receive any message | The receive any message operation shall be represented by an incoming message arrow from the port instance to the test component without any further information attached to it (see figure 56). MyPort MyPort.receive; GFT Core Figure 56: Receive any message ETSI ETSI TR 101 873-3 V1.2.1 (2002-05) 43 |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.3.2.2 Receive on any port | The receive on any port operation shall be represented by a found symbol representing any port to the test component (see figure 57). MyMessage any port.receive(MyMessage); GFT Core Figure 57: Receive on any port |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.3.3 The Trigger operation | The trigger operation shall be represented by an incoming message arrow from the port instance to the test component and the keyword trigger above the message arrow preceding the type information if present. The optional type information is placed above the message arrow subsequent to the keyword trigger. The (inline) ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.3.3.1 Trigger on any message | The trigger on any message operation shall be represented by an incoming message arrow from the port instance to the test component and the keyword trigger above the message arrow without any further information attached to it (see figure 60). trigger MyPort MyPort.trigger; GFT Core Figure 60: Trigger on any message op... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.3.3.2 Trigger on any port | The trigger on any port operation shall be represented by a found symbol representing any port to the test component (see figure 61). MyMessage trigger any port.trigger(MyMessage); GFT Core Figure 61: Trigger on any port operation |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.4 Procedure-based communication | |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.4.1 The Call operation | |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.4.1.1 Calling blocking procedures | The blocking call operation is represented by an outgoing message symbol from the test component to the port instance with a subsequent suspension region on the test component and the keyword call above the message arrow preceding the signature if present. The (inline) template is placed underneath the message arrow (s... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.4.1.2 Calling non-blocking procedures | The non-blocking call operation shall be represented by an outgoing message symbol from the test component to the port and the keyword call above the message arrow preceding the signature. There shall be no suspension region symbol attached to the message symbol. The optional signature is represented above the message ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.4.2 The Getcall operation | The getcall operation shall be represented by an incoming message arrow from the port instance to the test component and the keyword getcall above the message arrow preceding the signature. The signature is placed above the message arrow subsequent to the keyword getcall. The (inline) template is placed underneath the ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.4.2.1 Accepting any call | The accepting any call operation shall be represented by an incoming message arrow from the port instance to the test component and the keyword getcall above the message arrow. No further information shall be attached to the message symbol (see figure 70). getcall MyPort MyPort.getcall; GFT Core Figure 70: Getcall on a... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.4.2.2 Getcall on any port | The getcall on any port operation is represented by a found symbol representing any port to the test component and the keyword getcall above the message arrow followed by the signature if present. The (inline) template if present shall be placed underneath the message arrow (see figure 71). getcall MyProc MyTemplateRef... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.4.3 The Reply operation | The reply operation shall be represented by an outgoing message symbol from the test component to the port instance and the keyword reply above the message arrow preceding the signature. The signature shall be placed above the message arrow subsequent to the keyword reply. The (inline) template shall be placed undernea... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.4.4 The Getreply operation | The getreply operation shall be represented by an incoming message arrow from the port instance to the test component and the keyword getreply above the message arrow preceding the signature. Within a call symbol, the message arrow head shall be attached to a preceding suspension region on the test component (see figur... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.4.4.1 Get any reply from any call | The get any reply from any call operation shall be represented by an incoming message arrow from the port instance to the test component and the keyword getreply above the message. No signature shall follow the getreply keyword. Within a call symbol, the message arrow head shall be attached to a preceding suspension re... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.4.4.2 Get a reply on any port | The get a reply on any port operation is represented by a found symbol representing any port to the test component. The keyword getreply shall be placed above the message arrow followed by the signature if present. Within a call symbol, the message arrow head shall be attached to a preceding suspension region on the te... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.4.5 The Raise operation | The raise operation shall be represented by an outgoing message symbol from the test component to the port instance. The keyword raise shall be placed above the message arrow preceding the signature and the exception type, which are separated by a comma. The (inline) template shall be placed underneath the message arro... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.4.6 The Catch operation | The catch operation shall be represented by an incoming message arrow from the port instance to the test component and the keyword catch above the message arrow preceding the signature and the exception type (if present). Within a call symbol, the message arrow head shall be attached to a preceding suspension region on... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.4.6.1 The Timeout exception | The timeout exception operation shall be represented by a timeout symbol with the arrow connected to the test component (see figure 88). No further information shall be attached to the timeout symbol. It shall be used within a call symbol only. The message arrow head shall be attached to a preceding suspension region o... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.4.6.2 Catch any exception | The catch any exception operation shall be represented by an incoming message arrow from the port instance to the test component and the keyword catch above the message arrow. Within a call symbol, the message arrow head shall be attached to a preceding suspension region on the test component (see figure 89). Outside a... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.4.6.3 Catch on any port | The catch on any port operation is represented by a found symbol representing any port to the test component and the keyword catch above the message arrow. Within a call symbol, the message arrow head shall be attached to a preceding suspension region on the test component (see figure 91). Outside a call symbol, the me... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.5 The Check operation | The check operation shall be represented by an incoming message arrow from the port instance to the test component. The keyword check shall be placed above the message arrow. The attachment of the information related to the receive (see figure 93), getcall, getreply (see figures 94 and 95) and catch follows the check k... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.5.1 The Check any operation | The check any operation shall be represented by an incoming message arrow from the port instance to the test component and the keyword check above the message arrow (see figure 96). It shall have no receiving operation keyword, type and template attached to it. Optionally, an address information and storing the sender ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.5.2 Check on any port | The check on any port operation is represented by a found symbol representing any port to the test component and the keyword check above the message arrow (see figure 97). The attachment of the information related to the receive, getcall, getreply and catch follows the check keyword and is according to the rules for re... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.6 Controlling communication ports | |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.6.1 The Clear port operation | The clear port operation shall be represented by a condition symbol with the keyword clear. It is attached to the test component instance, which performs the clear port operation, and to the port that is cleared (see figure 98). clear MyPort MyPort.clear; GFT Core Figure 98: Clear port operation ETSI ETSI TR 101 873-3 ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.6.2 The Start port operation | The start port operation shall be represented by a condition symbol with the keyword start. It is attached to the test component instance, which performs the start port operation, and to the port that is started (see figure 99). start MyPort MyPort.start; GFT Core Figure 99: Start port operation |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.6.3 The Stop port operation | The stop port operation shall be represented by a condition symbol with the keyword stop. It is attached to the test component instance, which performs the stop port operation, and to the port that is stopped (see figure 100). stop MyPort MyPort.stop; GFT Core Figure 100: Stop port operation |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.8.6.4 Use of any and all with ports | The GFT representation of the any keyword for ports together with the receive, trigger, getcall, getreply, catch, and check operations is explained in the respective subclauses of clause 11.8. The all keyword for ports together with the clear, start and stop operation is represented by attaching the condition symbol co... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.9 Timer operations | In GFT, there are two different timer symbols: one for identified timers and one for call timers (see figure 101). They differ in appearance as dashed timer symbols are used for call timers. The difference in syntax is that the identified timer shall have its name attached to its symbol, whereas the call timer does not... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.9.1 The Start timer operation | For the start timer operation, the start timer symbol shall be attached to the component instance. A timer name and an optional duration value (within parentheses) may be associated (see figure 102). MyTimer(10.0) MyTimer.start(10.0); GFT Core Figure 102: The start timer operation |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.9.2 The Stop timer operation | For the stop timer operation, the stop timer symbol shall be attached to the component instance. An optional timer name may be associated (see figure 103). MyTimer MyTimer.stop; GFT Core Figure 103: The stop timer operation The symbols for a start timer and a stop timer operation may be connected with a vertical line. ... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.9.3 The Timeout operation | For the timeout operation, the timeout symbol shall be attached to the component instance. An optional timer name may be associated (see figure 105). MyTimer MyTimer.timeout; GFT Core Figure 105: The timeout operation ETSI ETSI TR 101 873-3 V1.2.1 (2002-05) 58 The symbols for a start timer and a timeout operation may b... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.9.4 The Read timer operation | The read timer operation shall be put into an action box (see figure 107). MyVar := MyTimer.read; MyVar := MyTimer.read; GFT Core Figure 107: The read timer operation |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.9.5 Use of any and all with timers | The stop timer operation can be applied to all timers (see figure 108). all timer.stop; GFT Core Figure 108: Stopping all timers The timeout operation can be applied to any timer (see figure 109). any timer.timeout; GFT Core Figure 109: Timeout from any timer ETSI ETSI TR 101 873-3 V1.2.1 (2002-05) 59 |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.10 Test verdict operations | The verdict set operation setverdict is represented in GFT with a condition symbol within which the values pass, fail, inconc or none are denoted (see figure 110). NOTE: The rules for setting a new verdict follow the normal TTCN-3 overwriting rules for test verdicts. pass setverdict(pass); GFT Core Figure 110: Set loca... |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.11 External actions | External actions are represented within action box symbols (see figure 111). The syntax of the external action is placed within that symbol. action( "Send MyTemplate on lower PCO ") action("Send MyTemplate on lower PCO "); GFT Core Figure 111: External actions |
26cb0886e0a7c8ad09c5dd0dfd2e07c4 | 101 873-3 | 11.12 Specifying attributes | The attributes defined for the module control part, testcases, functions and altsteps are represented within the text symbol. The syntax of the with statement is placed within that symbol. An example is given in figure 112. testcase MyTestcase() extension “MySpecialLogging()" testcase MyTestcase() { : } with { extensio... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 1 Scope | The present document is a technical report keeping the state of the early development done on the transport of IP over DTM. It gives insight into how things can be done, but is not complete enough to become a standard, so the status is reported so that further work can make use of this knowledge. The present document d... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 2 References | For the purposes of this Technical Report (TR) the following references apply: [1] IETF RFC 791: "Internet Protocol". [2] IETF RFC 2328: "OSPF Version 2", J. Moy, April 1998. [3] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification". [4] IETF RFC 2543: "SIP Session Initiation Protocol". [5] ETSI ES 201 803... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 3 Definitions and abbreviations | |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: access node: a node that supports an external network interface, contains an interworking function for an external network and uses the DTM service channel: set of slots allocated from one source Access node to one or more destination ... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ARP Address Resolution Protocol CMI Channel Multiplexing Indentifier CMMI Channel Management Module Interface DCAP-1 DTM Channel Adaption Protocol 1 DCP DTM Channel Protocol DST DTM Service Type DSTI DTM Service Type Instance DTM Dynamic synch... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 4 Service overview | Two different methods for transporting IP traffic across a DTM network are specified in the present document. The DTM network may be used to provide a transmission layer between adjacent IP routers which provide a service based on traditional hop-by-hop forwarding. This method is normally used for best effort IP traffi... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 5 System overview | IP over DTM (IPOD) is designed for building large IP- networks overlaid on DTM networks. IPOD is designed to efficiently provide a best-effort service for bursty traffic, as well as transport of QoS demanding traffic. IPOD supports both types of traffic in the same infrastructure by treating them differently. Normally,... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 5.1 Topology based forwarding | The hop-by-hop forwarding technique traditionally used in IP-based networks has proved very effective at transporting best-effort traffic where traffic from many sources can be aggregated to efficiently use network resources (i.e. links and switches). With DTM, a flexible transport network is provided to build a hop-by... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 5.2 Flow based forwarding | DTM has inherent support for end-to-end transport with complete traffic isolation resulting in no data loss and predictable delay. This support is used by IPOD to establish direct channels across the DTM network to carry IP traffic, thus short cutting intermediate routers making the IP transport over the network one ho... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 5.3 IPOD interfaces | An IPOD interface represents an IP interface to the IPover DTM service. The IPOD interface provides access to a virtual multicast and broadcast capable IP subnet being specified as an IPOD segment. Configured base connections provide the basic connectivity within the IPOD segment while dynamic channels can be setup for... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 5.4 IPOD segments | An IPOD segment consists of a number of IPOD interfaces and thus forms an IP subnet emulating a broadcast medium. Each IPOD interface is located in a physical node. There can only be one IPOD interface for a specific IPOD segment in a single node, but one physical node can have several IPOD interfaces connected to diff... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 5.5 Channels in IPOD | All packets in IPOD are transmitted on channels using DCAP-1 encapsulation with its CRC-32 checking of the data content. The IPOD channels are used for sending both IP datagrams and IPOD control messages. The CMI is used to demultiplex the IP datagrams and IPOD control messages at the destination. The CMI value of the ... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 5.6 Base channel capacity | NOTE: This clause should be moved to another document since it is common to IPOD/DLE/DLT and it should also be re-written to allow for several different bitrate specification schemes. Agreed, will move when we have identified another location. We must have something concerning BW mgmt here since IPOD instructs the chan... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 5.7 Interaction with routing protocols | The IPOD base channel topology can be implemented using partly connected meshes that add requirements on the IP routing protocol. To obtain simple configuration and IP routing stability, the IP routing protocol should support multipoint interfaces as in for example OSPF. |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 5.7.1 OSPF | The base connection is used by OSPF RFC 2328 [2] to build a topology map of the network. The IPOD segment corresponds to an OSPF routing domain. As defined in RFC 2328 [2] clause 12.4.1.4, an IP interface should be identified in an OSPF router by its IP address. Each base connection from the OSPF router should be ident... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 6 Service Interface | This is structured as in the Ethernet over DTM standard in terms of Traffic interface and Control interface. IP IPOD interface DCAP-1 DCAI Figure 7: Transport view of IPOD To transport the IP packets over DTM, the Ethernet/DTM Interworking function uses the DCAI service interface of DCAP-1. IPOD Interworking function C... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 6.1 Service provided | The IPOD provide a management interface to the upper layers. The details of this interface are not part of the present document. |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 6.2 Service required | The Ethernet channels use the DTM Channel Management Interface (DCMI) to establish channel, modify capacity of channel and remove channel. The size of the channels is also defined through the DCMI. |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7 Detailed protocol description | This clause starts with a description of the entities involved in IPOD: interfaces and incoming and outgoing channels. It continues to describe the actions performed by an IPOD interface. Each node participating in an IPOD segment has one IPOD interface for that IPOD segment. Each IPOD interface is associated with a nu... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.1 IPOD interface parameters | The following parameters are associated with an IPOD interface. Table 1: IPOD interface parameters Parameter Description IP address The IP address of the IPOD interface. This should be unique, both within the node and within the IPOD segment that this interface is connected to. Segment IP address The IPOD segment has a... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.2 Incoming channel properties | Each incoming channel to an IPOD interface is associated with the following parameters. • Source DTM address. • The DTM address of the sending IPOD interface. • Source DSTI. • The DSTI of the sending IPOD interface. ETSI ETSI TR 101 803-10 V1.1.1 (2004-07) 17 |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.2.1 Channel type | This parameter identifies the type of the outgoing channel. It can have the following values: • CONFIGURED_BASE: This channel is part of a base connection that was established because of a local configuration. • AUTOMATIC_BASE: This channel is part of a base connection that was established because of a remote configura... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.2.2 Source IP address | The IP address of the sending IPOD interface. |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.2.3 Filter specifications | In RSVP (RFC 2205)[7] this is called "filter specification" or "filter spec" for short. I propose we use that terminology over "flow restriction" which in my mind has a bad ring to it. A filter specification can be associated with a dynamic channel. The filter specification has the following properties: • Source IP add... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.3 Outgoing channel parameters | Each outgoing channel has the following parameters associated with it. Table 2: Outgoing channel parameters Parameter Description Destination DTM address The DTM address of the destination IPOD interface. Destination DSTI The DSTI of the destination IPOD interface. Channel type This property identifies the type of the ... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.4 IPOD interface operation | |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.4.1 IPOD interface startup | When an IPOD interface is started, it should perform the following steps: 1) Start to accept channels on the configured DSTI. 2) Start to establish the channels for the base connection. The base connection are configured at one end of the bi-directional base connection, if configured in the node, the node starts to est... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.4.2 IPOD interface shutdown | When an IPOD interface is shut down, it should perform the following steps: 1) Deregister with the routing entity to avoid having more packets sent to it. 2) Stop accepting new channels. 3) Close all incoming and outgoing channels. ETSI ETSI TR 101 803-10 V1.1.1 (2004-07) 19 |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.4.3 Establishing an IPOD channel | To establish a channel from IPOD interface A to IPOD interface B, A must know the DTM address and destination DSTI of B. This information can be found either in the configuration of A or it can be obtained from the channel establishment message received from B if B has already established a channel to A. The establishm... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.4.4 Establishing base connection | A base connection consists of exactly two channels between two IPOD interfaces, one in each direction. Both channels are established as described in clause 7.4.3. Base channels should always be created with the base connection bit set in the IPOD_REGISTER message to signal to the receiver that a base connection is requ... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.4.5 Establishing dynamic channels | Dynamic channels are created either based on configuration of the IPOD interface or in response to a request from a function outside the IP/DTM interworking. This function can for example be an IP signalling protocol. Dynamic channels are always uni-directional and the sender creates them. The receiver must accept inco... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.4.6 Receiving a channel | When a new channel is received, the IPOD interface is issued a DMCI_ICHANNEL_RECEIVED primitive from the channel manager. The IPOD interface must accept the channel if it has enough resources to do so. It accepts the channel by issuing a DMCI_ICHANNEL_ACCEPT service primitive to the channel manager. When the channel ha... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.4.6.2 Receiving a dynamic channel | If the received channel is a dynamic channel, it should be accepted. |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.4.7 Remote teardown of an incoming channel for a base connection | If an incoming channel for a base connection is torn down by the sender or by a network failure, the receiver should signal to the routing entity that the base connection is no longer available. If the base connection is a configured base connection, the receiver should raise an alarm and wait for the other node to re-... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.4.8 Remote teardown of an outgoing channel for a base connection | If an outgoing channel of a base connection is torn down by the receiver or by a network failure, the sender should raise an alarm and signal to the routing entity that this base connection no longer exists. If the base connection has the configured bit set (which means that it was configured locally), the sender shoul... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.4.9 Remote teardown of an incoming dynamic channel | If an incoming dynamic channel is torn down, the receiving IPOD interface should do nothing except removing the entry for the channel. |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.4.10 Remote teardown of an outgoing dynamic channel | If an outgoing dynamic channel is torn down by a network failure or by the receiver, the transmitting IPOD interface should notify the entity that requested the dynamic channel. It is then up to that entity to request that the dynamic channel should be re-established. |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 7.4.11 Removal of a base channel because of re-configuration | If an IPOD interface is reconfigured so that a base connection is removed from the configuration, the corresponding channels should be closed and the base connection shall be removed. Note that the base connection can be re-established by the IPOD interface at the other end if that IPOD interface still has a configurat... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 8 Messages | This clause describes the different control messages that can be sent on an IPOD channel. All IPOD channels should be established to the DST for IPOD. IPOD control messages should be sent with CMI=1 and IP packets should be sent with CMI=2. |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 8.1 General message format | All IPOD messages have the following format: VER MT Data… Extension… Figure 9: General IPOD message format The VER field is 4 bits and identifies the version of IPOD used. The current version number is 0. The IPOD_MSG_TYPE (MT in figure 9) is 4 bits. The following values for IPOD_MSG_TYPE have been defined. Table 3: De... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 8.2 IPOD_Register | This message is used when establishing a channel from one IPOD interface to another IPOD interface. |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 8.2.1 Normal message format | IPOD_REG_ FLAGS 0 0 SOURCE_IP_ADDRESS Figure 11: IPOD_Register message format B C U U U U U U 0 1 2 3 4 5 6 7 Figure 12: IPOD_REGISTER_FLAGS |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 8.2.1.1 Source IP Address | The IP address of the IPOD interface that sent the message. |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 8.2.1.2 Base Connection | Bit 7 (marked with a B) of IPOD_REGISTER_FLAGS. This bit indicates the type of channel being established. 0 dynamic channel. 1 base connection ETSI ETSI TR 101 803-10 V1.1.1 (2004-07) 23 |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 8.2.1.3 Configured | Bit 6 (marked with a C) of IPOD_REGISTER_FLAGS. If this is a channel of a base connection (as indicated by the Base Connection bit above), this parameter tells whether the sender has this dynamic channel configured or not. 0 Not configured (i.e.the channel was established because a channel of a base connection was rece... |
f7c91eb1e354b2497af26e208311976f | 101 803-10 | 8.2.2 Flow Restriction Extension | The Flow Restriction Extension tells the receiver that only packets matching the specified flow specification will be sent on the channel. 0 PROTOCOL_SPECIFIC 14 DESTINATION_IP_ADDRESS SOURCE_IP_ADDRESS PROTOCOL Figure 13: Flow Restriction Extension general format 0 SOURCE_PORT DEST_PORT 14 DESTINATION_IP_ADDRESS SOURC... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.