Network architectural components of the OMA MC Enabler involved in resolution of Indirect Codes and related addressing rules for such components are as follows:
a) Code Management Platform (CMP) and its variants where applicable (i.e., CMP-Split-Parent and CMP-Split-Child). Each CMP capable of resolving Indirect Codes is assigned with a globally unique Routing Prefix.
b) A CMP is typically associated with either a Mobile Code Registry (MCR) or Multi-lateral Arrangement (MLA). A CMP can also operate on its own without any association with other CMPs.
c) Within a community of CMPs associated with a MCR, the entity that operates the MCR shall apply for a 'Registry-ID' from the appropriate OMNA Registry. Within a MLA (i.e., a community of CMPs without any MCR), the designated lead CMP in the MLA shall apply for a 'Registry-ID' from the appropriate OMNA Registry.
d) If associated with either a MCR or MLA, a CMP shall obtain its Routing Prefix assignment from the holder of a Registry-ID (i.e., either the MCR entity or the designated lead CMP in the MLA).
e) If not associated with any MCR or MLA, a CMP shall obtain its Routing Prefix directly from the appropriate OMNA Registry.
Definitions and normative functional responsibilities of the above-mentioned network components of the MC Enabler, as well as the relationship between a Registry-ID and Routing Prefixes that stem from it, are specified in the OMA Mobile Codes V1.0 Enabler (Technical Specification Sections 3.2, 8.1 and 8.2). See OMA Mobile Codes V1.0
An entity who is responsible for the Mobile Code Registry (MCR) role within a community of CMPs or is the lead CMP in a multi-lateral arrangement (MLA), as specified in the OMA Mobile Codes V1.0 Enabler, can apply for a Registry-ID. An applicant will receive a fixed length 3-hexadecimal-digit Registry-ID value when approved.
A Routing Prefix comprises of three sub-parts as follows: Length Indicator, Registry-ID and the Remaining-Part-of-Routing-Prefix. (Ref: OMA MC Enabler V1.0 TS, Section 8.1.3)
| Field | Routing Prefix | ||
| Length-Indicator | Registry-ID | Remaining-Part-of-Routing-Prefix | |
| Length | 1 hex digit | 3 hex digits | Variable length (1 to 16 octets) |
| Description | Indicates the length of the 'Remaining Part of Routing Prefix' field in octets | Contains the Registry ID | Contains the remaining part of the Routing Prefix after excluding the first 2 octets. |
| Range of Assignable Mobile Codes Routing Prefixes | ||
| OMNA Database Record Sequence Number (for internal use only) | Assignable Range of Routing Prefixes | |
| [incrementing integer from 1 to .... | [x000100 to xF001FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF] |
|
Note: OMNA's Registry-ID has the value %x001; any octet value of '%x04' in the Remaining-Part-of-Routing-Prefix must not be assigned.
| Mobile Codes Routing Prefix | ||||
| OMNA Database Record Sequence Number (for internal use only) | Assigned Routing Prefix Value | Applying entity | Description of the Applying Entity | Contact details |
| (See legend above for the Range of Assignable Routing Prefixes) | Recipient of the Routing Prefix(es) |
Brief Description of the applying entity | Applying entity of primary contact information based on the application form (name, address, email addres, etc.) | |
| 1 | %x2001000001 (example) |
Open Mobile Naming Authority (OMNA) | Naming Authority of the Open Mobile Alliance | OMA-OMNA |
| 4 | %6001900107F52810D5 (example) |
ACME Inc | A shipping & tracking company using barcodes | IAM President 1-800-555-xxx iam.president@acme.com |
| continues... | ||||