Skip to content

Commit 3acdaca

Browse files
authored
Add comments to update questions in PR#5
Add comments to update questions in PR#5
1 parent 6d45da6 commit 3acdaca

File tree

1 file changed

+16
-23
lines changed

1 file changed

+16
-23
lines changed

10308.xml

+16-23
Original file line numberDiff line numberDiff line change
@@ -25,35 +25,32 @@ DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
2525
<Operations>R</Operations>
2626
<MultipleInstances>Single</MultipleInstances>
2727
<Mandatory>Mandatory</Mandatory>
28-
<Type>Integer</Type>
28+
<Type>String</Type>
2929
<RangeEnumeration>
3030
</RangeEnumeration>
31-
<Units>
32-
</Units>
33-
<Description><![CDATA[The ICCID resource is used to identify the UICC used by the IoT device or module for authentication by the network.]]></Description>
31+
<Units></Units>
32+
<Description><![CDATA[T he ICCID resource is used to identify the UICC used by the IoT device or module for authentication by the network. Reference ITU-T recommendation E.118]]></Description>
3433
</Item>
3534
<Item ID="2">
3635
<Name>IMSI</Name>
3736
<Operations>R</Operations>
3837
<MultipleInstances>Single</MultipleInstances>
3938
<Mandatory>Mandatory</Mandatory>
40-
<Type>Integer</Type>
39+
<Type>String</Type>
4140
<RangeEnumeration>
4241
</RangeEnumeration>
43-
<Units>
44-
</Units>
42+
<Units></Units>
4543
<Description><![CDATA[The IMSI resource is used to log the IMSI used by the UE to identify itself to the network. The IMSI is defined in 3GPP TS 23.003 and is a combination of MCC (Mobile Country Code), MNC (Mobile Network Code), and MSIN (Mobile Subscriber Identification Number).]]></Description>
4644
</Item>
4745
<Item ID="3">
4846
<Name>MSISDN</Name>
4947
<Operations>RW</Operations>
5048
<MultipleInstances>Single</MultipleInstances>
5149
<Mandatory>Mandatory</Mandatory>
52-
<Type>Integer</Type>
50+
<Type>String</Type>
5351
<RangeEnumeration>
5452
</RangeEnumeration>
55-
<Units>
56-
</Units>
53+
<Units></Units>
5754
<Description><![CDATA[The MSISDN resource will indicate the MSISDN as assigned, if any, to the SIM card. In the case that no MSISDN is assigned to the SIM card the response should be zero.]]></Description>
5855
</Item>
5956
<Item ID="4">
@@ -64,8 +61,7 @@ DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
6461
<Type>Integer</Type>
6562
<RangeEnumeration>
6663
</RangeEnumeration>
67-
<Units>
68-
</Units>
64+
<Units></Units>
6965
<Description><![CDATA[The APN Retry multi instance resource will maintain the number of retries the device can attempt to activate a context on a particular APN. This resource should be defaulted to 2 retries. Should a device integrator wish to manipulate this the integrator should be able to do so.]]></Description>
7066
</Item>
7167
<Item ID="5">
@@ -76,7 +72,7 @@ DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
7672
<Type>Integer</Type>
7773
<RangeEnumeration>
7874
</RangeEnumeration>
79-
<Units>seconds</Units>
75+
<Units>s</Units>
8076
<Description><![CDATA[The APN retry period multi instance resource is the time in seconds between attempting a context activation on the APN. This should be defaulted to 0. Note that the IoT Module will be limited by the number retries and the periodicity of the retries by the DAM requirements in Chapter 28 of the AT&T 13340. The resource is multi-instance to accommodate different periods of retries on different APNs.]]></Description>
8177
</Item>
8278
<Item ID="6">
@@ -87,7 +83,7 @@ DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
8783
<Type>Integer</Type>
8884
<RangeEnumeration>
8985
</RangeEnumeration>
90-
<Units>seconds</Units>
86+
<Units>s</Units>
9187
<Description><![CDATA[The APN Retry Back-Off Period is the period between a burst of attempts to activate a context on a particular APN. This resource is intended to be a longer period than the APN retry period to account for limitations on the numbers of times an authentication request can be made with the network. This should be defaulted to 86400 seconds (1 Day). This resource is also a multiple instance resource to accommodate different retry periods amongst different APNs.]]></Description>
9288
</Item>
9389
<Item ID="7">
@@ -96,10 +92,9 @@ DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
9692
<MultipleInstances>Single</MultipleInstances>
9793
<Mandatory>Mandatory</Mandatory>
9894
<Type>Integer</Type>
99-
<RangeEnumeration></RangeEnumeration>
100-
<Units>
101-
</Units>
102-
<Description><![CDATA[This is the signal to noise ratio resource. This measurement should be measured over 10 sampled at a 400ms sample rate. Once the 10 samples are averaged the measurement should be reflected in the Signal to Noise Ratio resource.]]></Description>
95+
<RangeEnumeration>&#60;7 to &#62;12.5</RangeEnumeration>
96+
<Units></Units>
97+
<Description><![CDATA[This is the signal to noise ratio resource. This measurement should be measured over 10 sampled at a 400ms sample rate. Once the 10 samples are averaged the measurement should be reflected in the Signal to Noise Ratio resource. Reference: 3GPP TS 38.215, clause 5.1.]]></Description>
10398
</Item>
10499
<Item ID="8">
105100
<Name>SRXLEV</Name>
@@ -109,8 +104,7 @@ DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
109104
<Type>Integer</Type>
110105
<RangeEnumeration>
111106
</RangeEnumeration>
112-
<Units>
113-
</Units>
107+
<Units></Units>
114108
<Description><![CDATA[This resource indicates the cell selection receive value. See definition in 3GPP TS 36.304.]]></Description>
115109
</Item>
116110
<Item ID="9">
@@ -121,9 +115,8 @@ DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
121115
<Type>String</Type>
122116
<RangeEnumeration>
123117
</RangeEnumeration>
124-
<Units>
125-
</Units>
126-
<Description><![CDATA[This resource indicates the CE Mode the IoT module is currently in.]]></Description>
118+
<Units></Units>
119+
<Description><![CDATA[This resource indicates the CE Mode the IoT module is currently in. Potential values: Mode A, Mode B.]]></Description>
127120
</Item>
128121
</Resources>
129122
<Description2 />

0 commit comments

Comments
 (0)