<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>

<!--
    FILE INFORMATION

    Description
       Guidelines for the handling for the GBA Protocol Identifier registry

    Version: 1.0
    Date:    14 APR 2010

    OMA Permanent Document
       File: OMA-INF-HTM_OMNA_PushAppID-20100414-I
       Type: Text

    Private Reachable Information
       Path: http://www.openmobilealliance.org/ftp/REL/P-n-G
       Name: OMNA_PushAppID.htm

    NORMATIVE INFORMATION

    Description of the handling and usage for OMNA Registry for
    Push Application Identifier
	
    LEGAL DISCLAIMER

    Use of this document is subject to all of the terms and conditions
    of the Use Agreement located at
	http://www.openmobilealliance.org/UseAgreement.html

    You may use this document or any part of the document for internal
    or educational purposes only, provided you do not modify, edit or
    take out of context the information in this document in any manner.
    Information contained in this document may be used, at your sole
    risk, for any purposes.

    You may not use this document in any other manner without the prior
    written permission of the Open Mobile Alliance.  The Open Mobile
    Alliance authorizes you to copy this document, provided that you
    retain all copyright and other proprietary notices contained in the
    original materials on any copies of the materials and that you
    comply strictly with these terms.  This copyright permission does
    not constitute an endorsement of the products or services.  The
    Open Mobile Alliance assumes no responsibility for errors or
    omissions in this document.

    Each Open Mobile Alliance member has agreed to use reasonable
    endeavors to inform the Open Mobile Alliance in a timely manner of
    Essential IPR as it becomes aware that the Essential IPR is related
    to the prepared or published specification.  However, the members
    do not have an obligation to conduct IPR searches.  The declared
    Essential IPR is publicly available to members and non-members of
    the Open Mobile Alliance and may be found on the "OMA IPR
    Declarations" list at http://www.openmobilealliance.org/ipr.html.
    The Open Mobile Alliance has not conducted an independent IPR review
    of this document and the information contained herein, and makes no
    representations or warranties regarding third party IPR, including
    without limitation patents, copyrights or trade secret rights.  This
    document may contain inventions for which you must obtain licenses
    from third parties before making, using or selling the inventions.
    Defined terms above are set forth in the schedule to the Open Mobile
    Alliance Application Form.

    NO REPRESENTATIONS OR WARRANTIES (WHETHER EXPRESS OR IMPLIED) ARE
    MADE BY THE OPEN MOBILE ALLIANCE OR ANY OPEN MOBILE ALLIANCE MEMBER
    OR ITS AFFILIATES REGARDING ANY OF THE IPR'S REPRESENTED ON THE "OMA
    IPR DECLARATIONS" LIST, INCLUDING, BUT NOT LIMITED TO THE ACCURACY,
    COMPLETENESS, VALIDITY OR RELEVANCE OF THE INFORMATION OR WHETHER OR
    NOT SUCH RIGHTS ARE ESSENTIAL OR NON-ESSENTIAL.

    THE OPEN MOBILE ALLIANCE IS NOT LIABLE FOR AND HEREBY DISCLAIMS ANY
    DIRECT, INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR
    EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF
    DOCUMENTS AND THE INFORMATION CONTAINED IN THE DOCUMENTS.

    Copyright 2010 Open Mobile Alliance Ltd.  All Rights Reserved.
    Used with the permission of the Open Mobile Alliance Ltd. under the
    terms set forth above.
-->

<head>
	<title>OMNA Guidelines - Push Application ID</title>
	<meta name="description" content="OMNA Guidelines - Push Application ID">
	<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
	<link rel="stylesheet" href="../../GI_template/accessible_StaticPages.css" type="text/css">
	<link rel="stylesheet" href="ProcStyle.css" type="text/css">
</head>

<body>

<!--  Document Header  -->

<table border=0 width=100% cellspacing=0 cellpadding=0>
<tr>
<td align=left><img src="imgOMAlogo.gif"></td>
<td align=right>
<p class=dochead>OMNA Guidelines - PUSH Application ID</p>
<p class=docfile>OMA-INF-HTM_OMNA_PushAppID-20100414-I</p>
</td>
</tr></table>

<!--  Navigation Bar  -->

<table width=100% cellspacing=0 cellpadding=0>
<tr><td colspan=2><img height=5 width=100% src="imgBitWht.gif"></tr>
<tr><td colspan=2><img height=5 width=100% src="imgBitSep.gif"></tr>
<tr>
<td class=navbar>
<a href="Procs-n-Guides.htm">Procs-n-Guides</a>&nbsp;>>
<a href="OMNA.htm">OMNA</a>&nbsp;>>
<b>PushAppID</b>
</td>
<td class=navbar align=right>Updated: 14 Apr 2010</td>
</tr>
<tr><td colspan=2><img height=5 width=100% src="imgBitSep.gif"></tr>
<tr><td colspan=2><img height=5 width=100% src="imgBitWht.gif"></tr>
</table>

<!--  Start of Document  -->

<h1>OMNA Guidelines - PUSH Application ID</h1>


<h3>Contents</h3>
<ul>
<li><a href="#acc">Accessing the Registry</a></li>
<li><a href="#purp">Purpose of the Registry</a></li>
<li><a href="#data">Data Model for the Registry</a></li>
<li><a href="#how">How to Get a Registration</a></li>
</ul>

<hr class=1>
<a name="acc"><h2>Accessing the Registry</h2></a>

The <a target="OMNAreg" href="http://www.openmobilealliance.org/tech/omna/omna-push-app-id.aspx">PUSH Application ID Registry</a> is available from <a target="OMNAmain" href="http://www.openmobilealliance.org/tech/OMNA.aspx">Open Mobile Naming Authority (OMNA)</a> which is a registry service provided by the Open Mobile Alliance.
<p>

<hr class=1>
<a name="purp"><h2>Purpose of Registry</h2></a>

<p>
This registry records assignments of Application IDs as utilized by the PUSH enabler.
The application identifier codes provides a mapping to possible applications on a device.
<p>
The use of Application Identifiers for PUSH operations originated in the WAP Forum where the registrations were performed by the WAP Interim Naming Authority (WINA).  These were carried forward to OMA and is covered in the OMA Push Enabler with the registry moving to OMNA.
<p>

<hr class=1>
<a name="data"><h2>Data Model for the Registry</h2></a>

<p>
The PUSH documentation (WAP-189-PushOTA, WAP-235-PushOTA, OMA-TS-PushOTA) sets the Application-ID value as a <b><i>uintvar</i></b> and assignments as set in the registry.
To facilitate logical assignments, and to reserve shorter codes to common uses the following allocation scheme has been established.
<p>
The Application label is a unique string that describes the entity to receive the PUSH message.  It is translated to the assigned code for transmission over the air to shorten the message length.  The usable values for this code are divided into three zones based on the entity defining the application.  The following table describes the code ranges. 
<p>

<center>
<table border=1 width=80%>
<tr class=title>
  <th>Application Values</th>
  <th>Classes</th>
  <th>Description</th>
</tr>

<tr>
  <td class=code><nobr>0x00000000 - 0x00007FFF</nobr></td>
  <td>OMA Defined Application IDs</td>
  <td>These values are reserved for application IDs defined by OMA Enablers.  The domain will be "x-oma-application" for new assignments.  This section includes the "x-wap-application" labels assigned by the former WAP Forum.</td>
</tr>
<tr>
  <td class=code>0x00008000 - 0xFEFFFFFF</td>
  <td><nobr>External Entity Application IDs</nobr></td>
  <td>The values are available for registration by entities external to OMA</td>
</tr>
<tr>
  <td class=code>0xFF000000 - 0xFFFFFFFF</td>
  <td>Test/Experimental</td>
  <td>These values may be used for test or private use.  They are not recorded by OMNA</td>
</tr>
</table>
</center>
<p>

<hr class=1>
<a name="how"><h2>How to get a Registration</h2></a>

<p>
The method to acquire a registration is different depending upon whether the request is coming from an OMA Working Group to associate with an enabler in development or whether the request is coming from external entities.  Each of these are described below.

<h3>Request from an OMA Working Group</h3>
<p>
Requests from OMA Working Groups are expected to be associated with enablers that they are developing.
The OMA Defined Application ID number space is utilized to fulfill these requests.  The codes in this space are normally shorter to transmit.
<p>
Application descriptors for the OMA Defined IDs start with "<font class=code>x-oma-application</font>".  This continues the model value of "<font class=code>x-wap-application</font>" used when this registry was managed by the WAP Forum.
<p>
Requests by OMA Working Groups should be directed to the REL Committee via DSO.  The Working Group Should provide the following information:
<ul>
<li>Requested app label (e.g. the '<font class=code>xxx</font>' part of "<font class=code>x-oma-application:xxx</font>")</li>

The registrant submits 
an URI to OMNA for registration, together with the name and the description of 
the application, which the URI represents.
<p>
OMNA verifies that the URI is 
not registered
OMNA assigns an available code 
for the URI
MUST be rfc2396 compliant

URN SHOULD be used for location independent URI [rfc2141][rfc2611]
</ul>

<h3>Submitting a request</h3>

In order to register a PUSH Application identifier, a short 
description of its use must be provided. A form for submitting a request may be 
found at http://www.openmobilealliance.org/Technical/omna/omna-req-push-app-id.aspx

<p>
The information requested on the form is:

<ul>
	<li>Name </li>
	<li>Email Address</li>
	<li>Requested PUSH Application IDs URN</li>
	<li>Short Description</li>
	<li>Comments</li>
</ul>


<h3>Processing a request</h3>
<p>
The steps taken to validate and register a request are:</p>
<ol>
  <li>Check that the request seems valid and is not generated by a spam generator or someone testing the form.</li>
  <li>Determine if the request is for a Well Known Value, a Registered Value or a Private or Experimental Value (If in doubt check with ???.)
    <ul>
      <li>If the URN has NID&nbsp; 'x-wap-application' or x-oma-application and it is defined in any OMA specification then it will be assigned the next available value from and registered in the <b>Well Known Values</b> Table</li>
      <li><b>Registered Values</b> the URI can be registered with OMNA by any entity.  The registrant may choose any desirable URI except that the URN with NID 'x-wap-application' or x-oma-application cannot be used. Code in the code range must be assigned by OMNA.</li>
      <li><b>Private/Experimental: </b>Any URI can be used at will, but any registered URIs in Well-Known and Registered category SHOULD NOT be used. Registration is not required.  Any code in the code range can be selected as desirable.</li>
    </ul></li>
  <li>If the request is from an OMA group, then advise REL exploder lists</li>
  <li>Check that the mandatory information has been provided and is valid</li>
  <li>If the request seems reasonable and correct and then
    <ul>
      <li>Determine the next available value</li>
      <li>Assign the next available value</li>
      <li>Update the OMNA page
	<ul>
	  <li>Well Known Value Assigned:
            <ul>
              <li>Assigned Number (in the range 0x0000 to 0x7FFF)</li>
              <li>URN</li>
              <li>Description</li>
            </ul></li>
	  <li>Registered Value assigned:
            <ul>
              <li>Assigned Number (in the range 0x8000 to 0xFF000000)</li>
              <li>Registrant Name (with Mailto: link</li>
              <li>URN</li>
              <li>Description</li>
	    </ul></li>
          <li> Experimental Value requested:
            <ul>
              <li>no entry made - we do not record these</li>
            </ul></li>
        </ul></li>
      <li>Inform the requestor and the OMNA exploder list</li>
    </ul></li>
  <li>If the the request is incomplete or there are doubts
    <ul>
      <li>Contact the requestor and request clarification.</li>
    </ul></li>
</ol>

<p>

<!--  Document Footer  -->

<table width=100% cellspacing=0 cellpadding=0>
<tr><td colspan=2><img height=5 width=100% src="imgBitWht.gif"></tr>
<tr><td colspan=2><img height=5 width=100% src="imgBitSep.gif"></tr>
<tr>
<td class=footer align=left>&copy; 2010 Open Mobile Alliance, Ltd.<br>All Rights Reserved</td>
<td class=footer align=right>
<a href="http://www.openmobilealliance.org/AboutOMA/useterms.aspx">Website Terms of Use</a>
</td>
</tr>
</table>

</body>
</html>