THOMSON TR-069 - Page 94

E-DOC-CTC-20071119-0003 v1.0
88
6| Service Provisionin
g
Message flow
Following illustration shows a possible message flow for the configuration of the NAT application list:
Example: parameter values
For example, following parameter values can be used:
 Creating an application: the AddObject RPC (message 1 in preceding illustration) contains for the
ObjectName argument the value
“InternetGatewayDevice.Services.X_000E50_NATApplicationList.Application.”.
The AddObjectResponse (message 3 in preceding illustration) contains for the InstanceNumber
argument for example value “130“.
 Configuring the application: the SetParameterValues RPC (message 4 in preceding illustration) contains
following name-value pair in its ParameterList argument:
 Creating a rule: the AddObject RPC (message 7 in preceding illustration) contains for the ObjectName
argument the value
“InternetGatewayDevice.Services.X_000E50_NATApplicationList.Application.130.Rule.”.
The AddObjectResponse (message 9 in preceding illustration) contains for the InstanceNumber
argument for example value “1“.
ACSCPE
Transaction session
...
5) Apply changes
Configure the Application
4) SetParameterValues
6) SetParameterValuesResponse
Create an Application
1) AddObject
3) AddObjectResponse
2) Apply changes
Create a Rule (Port Mapping)
7) AddObject
9) AddObjectResponse
8) Apply changes
11) Apply changes
Configure the Rule (Port Mapping)
10) SetParameterValues
12) SetParameterValuesResponse
...
14) Apply changes
Assign a Host to an Application
13) SetParameterValues
15) SetParameterValuesResponse
Name Value
InternetGatewayDevice.Services.X_000E50_NATApplicationList.
Application.130.Name
<Name>
The parameter Name is mandatory. This means that the parameter must be set before the
Application object is internally created.