Skip to content

Commit 7cea1ec

Browse files
committed
fixup! fixup! fixup! [feature] building up the schema again from scratch acording the section 11,4,1 in the bitag report
1 parent 08b6798 commit 7cea1ec

3 files changed

Lines changed: 29 additions & 8 deletions

File tree

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
date_published,regulator_name,regulator_version_number,connection_type,fcc_registration_number,unique_plan_identifier
2-
2025-01-15,FCC,1,fixed,0005937974,F0005937974TIER1
3-
2025-11-02,,1,mobile,0003768165,F0005937974ABCD12341234
4-
2025-06-06,FCC,99,satellite,0005937974,F0005937974ABCDEFGHIJ12345
5-
2025-06-06,FCC,,something,,
1+
date_published,regulator_name,regulator_version_number,connection_type,fcc_registration_number,unique_plan_identifier,network_technology_type
2+
2025-01-15,FCC,1,fixed,0005937974,F0005937974TIER1,50
3+
2025-11-02,,1,mobile,0003768165,F0005937974ABCD12341234,500
4+
2025-06-06,FCC,99,satellite,0005937974,F0005937974ABCDEFGHIJ12345,500
5+
2025-06-06,FCC,,something,,,0
Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,9 @@
11
version 1.1
2-
@totalColumns 6
2+
@totalColumns 7
33
date_published: xDate
44
regulator_name: empty or upperCase
55
regulator_version_number: empty or range(1, 99)
66
connection_type: notEmpty
77
fcc_registration_number: empty or range(0000000000, 9999999999)
8-
unique_plan_identifier: empty or regex("^[FM][0-9]{1,10}[A-Z0-9]{1,15}$")
8+
unique_plan_identifier: empty or regex("^[FM][0-9]{1,10}[A-Z0-9]{1,15}$")
9+
network_technology_type: range(0, 999)

src/main/resources/schemas/schema_specs

Lines changed: 21 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,4 +78,24 @@ US, it MAY be left empty.
7878
Name: unique_plan_identifier
7979
Type/Format: string, limited to a maximum of 26 characters, no special characters, no delimiters, all letters
8080
capitalized.
81-
Examples: F0005937974TIER1, F0005937974ABCD12341234, F0005937974ABCDEFGHIJ12345
81+
Examples: F0005937974TIER1, F0005937974ABCD12341234, F0005937974ABCDEFGHIJ12345
82+
83+
```
84+
unique_plan_identifier: empty or regex("^[FM][0-9]{1,10}[A-Z0-9]{1,15}$")
85+
```
86+
87+
7. Network Technology Type.
88+
This indicates the access network technology used for a given BIAS offering. This is a numeric field using
89+
FCC-defined technology codes, limited to no more than 3 digits length. (In the future, it may be better to
90+
register these codes with IANA and to maintain them globally, rather than on a regulator-specific basis.)
91+
• If a Fixed plan type, refer to the FCC’s Fixed Technology Codes [42]. For example, hybrid-fiber coaxial
92+
(HFC) is “40” and fiber to the premises (FTTP) is “50”.
93+
• If a Mobile plan type, refer to the FCC’s Mobile Technology Codes [43]. For example, 3G is “300” and
94+
5G is “500”. This field MUST be in the file and MUST be populated.
95+
Note that mobile networks (and possibly other network types) may support the newest technology type, such
96+
as 5G, while also remaining backward compatible with 4G and 3G. In such cases, the newest technology type
97+
should be listed, because that is the current version/type of network.
98+
This field MUST be in the file and MUST be populated.
99+
Name: network_technology_type
100+
Type/Format: numeric, range (0, 999)
101+
Examples: 40, 50, 500

0 commit comments

Comments
 (0)