D.1 Rules
32.1533GPPIntegration Reference Point (IRP) technology specific templates, rules and guidelinesRelease 17Telecommunication managementTS
D.1.1 XSD Use Cases
D.1.1.1 Background
3GPP defines a number of IOCs, say in Release-N. 3GPP also defines an XSD schema that can capture these IOCs, in Release-N.
Release-N+1 authors can/may also extend these Release-N IOCs to capture the newly agreed capabilities and publish them as Release-N+1 IOCs. Authors also define a Release-N+1 XSD schema.
The Use Cases here illustrate the capabilities of the Release-N+1 XSD schema.
The "?" in the Use Case tables are for further study.
D.1.1.2 Use Cases Set 1
Suppose the old-XSD has SubNetwork (SN) containing ManagedElement (ME).
Suppose the new-XSD has enhanced-SN containing enhanced-ME.
Suppose we want the XML-instance-documents (doc-1, doc-2, etc) to contain instances as identified below:
– Doc-1 has SN instance containing ME instances
– Doc-2 has SN instance containing enhanced-ME instances
– Doc-3 has SN instance containing ME instances and enhanced-ME instances
– Doc-4 has enhanced-SN containing enhanced-ME instances
– Doc-5 has enhanced-SN containing ME instances
– Doc-6 has enhanced-SN containing enhanced-ME instances and ME instances
Can a XML-instance-doc-creator (IRPAgent or IRPManager) produce the doc (column) using the XSD (row) identified?
|
Doc-1 |
Doc-2 |
Doc-3 |
Doc-4 |
Doc-5 |
Doc-6 |
|
|
Old-XSD |
? |
? |
? |
? |
? |
? |
|
New-XSD |
? |
? |
? |
? |
? |
? |
Can a XML-instance-doc-reader (IRPAgent or IRPManager) validate the doc (i.e. confirm that the document is well-formed) (column) using the XSD (row) identified?
|
Doc-1 |
Doc-2 |
Doc-3 |
Doc-4 |
Doc-5 |
Doc-6 |
|
|
Old-XSD |
? |
? |
? |
? |
? |
? |
|
New-XSD |
? |
? |
? |
? |
? |
? |
D.1.1.3 Use Cases Set 2
Suppose one old-XSD has SubNetwork (SN) containing ManagedElement (ME) that in turn, contained an RNCFunction (RNC) defined by the other Old-XSD.
Suppose the new-XSD has enhanced-SN containing enhanced-ME. Suppose also another new-XSD has enhanced-RNC.
– Doc-7 has ME instance containing RNC instances
– Doc-8 has ME instances containing enhanced-RNC instances
– Doc-9 has ME instances containing RNC instances and enhanced-RNC instances
– Doc-10 has enhanced-ME instances containing enhanced-RNC instances
– Doc-11 has enhanced-ME instances containing RNC instances
– Doc-12 has enhanced-ME instances containing RNC instances and enhanced-RNC instances
Can a XML-instance-doc creator (IRPAgent or IRPManager) produce the doc (column) using the XSD (row) identified?
|
Doc-7 |
Doc-8 |
Doc-9 |
Doc-10 |
Doc-11 |
Doc-12 |
|
|
Old-XSD |
? |
? |
? |
? |
? |
? |
|
New-XSD |
? |
? |
? |
? |
? |
? |
Can a reader (IRPAgent or IRPManager) validate the doc (i.e. confirm that the document is well-formed) (column) using the XSD (row) identified?
|
Doc-1 |
Doc-2 |
Doc-3 |
Doc-4 |
Doc-5 |
Doc-6 |
|
|
Old-XSD |
? |
? |
? |
? |
? |
? |
|
New-XSD |
? |
? |
? |
? |
? |
? |
D.1.2 Rules for NRM IRP XML specification extensions
Void
D.1.3 XML version encoding
The first line of each XML schema description file file shall indicate the XML version and encoding. The supported XML version is specified in the subject TS. The supported encoding is UTF-8 (refer to [16]).
Therefore, an example for xsd filei s:
<?xml version="1.0" encoding="UTF-8"?>