Zone Normalizer

The Zone Normalizer flow is used to normalize an incoming field on the Diameter Ro message and determine the pricing zone that should be applied.

POST /objects/Normalizer/Zone shows how to create a new zone normalizer.
Table 1. POST /objects/Normalizer/Zone
URL
POST http://localhost:8080/matrixx/data/objects/Normalizer/Zone
Input 
<?xml version="1.0" encoding="UTF-8"?>
<ZoneNormalizer name="Zone Determination (MCC/MNC)">
    <EffectiveDate>2012-10-22T00:00:00</EffectiveDate>
    <ValueList default="5">
        <value color="#ff00ff" description="Not Present" id="0" index="0" name="Not Present"/>
        <value color="#ff00" description="Zone A" id="1" index="1" name="Zone A"/>
        <value color="#99cc" description="Zone B" id="2" index="2" name="Zone B"/>
        <value color="#996633" description="Zone C" id="3" index="3" name="Zone C"/>
        <value color="#ffff00" description="Zone D" id="4" index="4" name="Zone D"/>
        <value color="#ff0000" description="Unknown" id="5" index="5" name="Unknown"/>
        <value color="#99cc" description="Unknown IP Address" id="6" index="6" name="Unknown IP Address"/>
    </ValueList>
    <ResultList>
        <result index="0" value="0"/>
        <result index="6" value="6"/>
        <result index="1" value="10"/>
        <result index="4" value="497"/>
        <result index="4" value="498"/>
        <result index="4" value="499"/>
    </ResultList>
</ZoneNormalizer>
Response 
<CreateResponse>
    <type>Normalizer</type>
    <DomainId>1</DomainId>
    <Result>0</Result>
    <ResultText>Success</ResultText>
    <ObjectId>1066</ObjectId>
    <Revision>0</Revision>
</CreateResponse>
GET /objects/Normalizer/Zone/{id} shows how to retrieve a zone normalizer from the in-memory pricing database.
Table 2. GET /objects/Normalizer/Zone/{id}
URL
GET http://localhost:8080/matrixx/data/objects/Normalizer/Zone/1066
Response 
<?xml version="1.0" encoding="UTF-8"?>
<ZoneNormalizer name="Zone Determination (MCC/MNC)">
    <EffectiveDate>2012-10-22T00:00:00</EffectiveDate>
    <ValueList default="5">
        <value color="#ff00ff" description="Not Present" id="0" index="0" name="Not Present"/>
        <value color="#ff00" description="Zone A" id="1" index="1" name="Zone A"/>
        <value color="#99cc" description="Zone B" id="2" index="2" name="Zone B"/>
        <value color="#996633" description="Zone C" id="3" index="3" name="Zone C"/>
        <value color="#ffff00" description="Zone D" id="4" index="4" name="Zone D"/>
        <value color="#ff0000" description="Unknown" id="5" index="5" name="Unknown"/>
        <value color="#99cc" description="Unknown IP Address" id="6" index="6" name="Unknown IP Address"/>
    </ValueList>
    <ResultList>
        <result index="0" value="0"/>
        <result index="6" value="6"/>
        <result index="1" value="10"/>
        <result index="4" value="497"/>
        <result index="4" value="498"/>
        <result index="4" value="499"/>
    </ResultList>
</ZoneNormalizer>
PUT /objects/Normalizer/Zone/{id} shows how to update an existing zone normalizer.
Table 3. PUT /objects/Normalizer/Zone/{id}
URL
PUT http://localhost:8080/matrixx/data/objects/Normalizer/Zone/1066
Input 
<?xml version="1.0" encoding="UTF-8"?>
<ZoneNormalizer name="Zone Determination (MCC/MNC)">
    <EffectiveDate>2012-11-22T00:00:00</EffectiveDate>
    <ResultList>
        <result index="0" value="0"/>
        <result index="6" value="6"/>
        <result index="1" value="10"/>
        <result index="1" value="11"/>
        <result index="1" value="12"/>
        <result index="4" value="497"/>
        <result index="4" value="498"/>
        <result index="4" value="499"/>
    </ResultList>
</ZoneNormalizer>
Response 
<UpdateResponse>
    <type>Normalizer</type>
    <Result>0</Result>
    <ResultText>Success</ResultText>
    <ObjectId>1066</ObjectId>
    <Revision>1</Revision>
</UpdateResponse>