Push Client - Application Interface

Transcription

1 Push Client - Applicatin Interface Apprved Versin Nv 2011 Open Mbile Alliance OMA-TS-PushCAI-V1_ A

2 OMA-TS-PushCAI-V1_ A Page 2 (16) Use f this dcument is subject t all f the terms and cnditins f the Use Agreement lcated at Unless this dcument is clearly designated as an apprved specificatin, this dcument is a wrk in prcess, is nt an apprved Open Mbile Alliance specificatin, and is subject t revisin r remval withut ntice. Yu may use this dcument r any part f the dcument fr internal r educatinal purpses nly, prvided yu d nt mdify, edit r take ut f cntext the infrmatin in this dcument in any manner. Infrmatin cntained in this dcument may be used, at yur sle risk, fr any purpses. Yu may nt use this dcument in any ther manner withut the prir written permissin f the Open Mbile Alliance. The Open Mbile Alliance authrizes yu t cpy this dcument, prvided that yu retain all cpyright and ther prprietary ntices cntained in the riginal materials n any cpies f the materials and that yu cmply strictly with these terms. This cpyright permissin des nt cnstitute an endrsement f the prducts r services. The Open Mbile Alliance assumes n respnsibility fr errrs r missins in this dcument. Each Open Mbile Alliance member has agreed t use reasnable endeavrs t infrm the Open Mbile Alliance in a timely manner f Essential IPR as it becmes aware that the Essential IPR is related t the prepared r published specificatin. Hwever, the members d nt have an bligatin t cnduct IPR searches. The declared Essential IPR is publicly available t members and nn-members f the Open Mbile Alliance and may be fund n the OMA IPR Declaratins list at The Open Mbile Alliance has nt cnducted an independent IPR review f this dcument and the infrmatin cntained herein, and makes n representatins r warranties regarding third party IPR, including withut limitatin patents, cpyrights r trade secret rights. This dcument may cntain inventins fr which yu must btain licenses frm third parties befre making, using r selling the inventins. Defined terms abve are set frth in the schedule t the Open Mbile Alliance Applicatin Frm. 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. Used with the permissin f the Open Mbile Alliance Ltd. under the terms set frth abve.

3 OMA-TS-PushCAI-V1_ A Page 3 (16) Cntents 1. SCOPE REFERENCES INFORMATIVE REFERENCES TERMINOLOGY AND CONVENTIONS CONVENTIONS DEFINITIONS ABBREVIATIONS INTRODUCTION VERSION VERSION PUSH CLIENT - APPLICATION INTERFACE (PUSH-CAI) PUSH APPLICATION REGISTRATION PUSH APPLICATION DEREGISTRATION PUSH EVENT DELIVERY SECURITY CONSIDERATIONS APPENDIX A. CHANGE HISTORY (INFORMATIVE) A.1 APPROVED VERSION HISTORY APPENDIX B. STATIC CONFORMANCE REQUIREMENTS (NORMATIVE) B.1 SCR FOR PUSH CLIENT... 16

4 OMA-TS-PushCAI-V1_ A Page 4 (16) 1. Scpe This specificatin defines the Push Applicatin Interface thrugh which Push Applicatins can access OMA Push enabler services. The interface specified in this dcument defines functins and data frmats supprting: registratin f Push Applicatins with an OMA Push Client the subsequent delivery f Push events t the Push Applicatin

5 OMA-TS-PushCAI-V1_ A Page 5 (16) 2. References [BCAST-SvcGuide] [PushMO] [PushMsg] [PushOTA] [RFC2119] [RFC2234] [SIPPush] [TS23.041] [TS26.346] [UAPROF] [UAPrfSchema] Service Guide fr Mbile Bradcast Services. Open Mbile Alliance. OMA-TS- BCAST_ServiceGuide-V1_0. URL: "Push Management Object". Open Mbile Alliance. OMA-TS-Push_MO-V1_1. URL: "Push Message Specificatin". Open Mbile Alliance. OMA-TS-Push_Message-V2_3. URL: "Push OTA Prtcl Specificatin". Open Mbile Alliance. OMA-WAP-TS-PushOTA-V2_3. URL: Key wrds fr use in RFCs t Indicate Requirement Levels. S. Bradner. March URL: "Augmented BNF fr Syntax Specificatins: ABNF". D. Crcker, Ed., P. Overell. Nvember URL: Push using SIP. Open Mbile Alliance. OMA-TS-SIP_Push-V1_0. URL: "Technical realizatin f Cell Bradcast Service (CBS)". 3rd Generatin Partnership Prject (3GPP). URL: 3GPP Technical Specificatin Grup Services and System Aspects; Multimedia Bradcast/Multicast Service (MBMS). URL: "Wireless Applicatin Grup User Agent Prfile Specificatin", Open Mbile Alliance, OMA-UAPrfv2_0. URL: URL: OMA User Agent Prfile Schema (latest), Open Mbile Alliance, Infrmative References [IANA] [OMADICT] [OMNA] "Internet Assigned Numbers Authrity", URL: Dictinary fr OMA Specificatins, Open Mbile Alliance, OMA-ORG-Dictinary, URL: "OMA Naming Authrity". Open Mbile Alliance. URL:

6 OMA-TS-PushCAI-V1_ A Page 6 (16) 3. Terminlgy and Cnventins 3.1 Cnventins The key wrds MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this dcument are t be interpreted as described in [RFC2119]. All sectins and appendixes, except Scpe and Intrductin, are nrmative, unless they are explicitly indicated t be infrmative. 3.2 Definitins Applicatin Applicatin-Level Addressing Bearer Netwrk Client Cntact Pint Cntent Cntent Encding Cntent Frmat Device End-user Multicast Message Pint-t-Multipint Push Push Access Prtcl Push Client Applicatin Interface Push Framewrk Push Initiatr Push OTA Prtcl Push Prxy Gateway Push Sessin An implementatin f a related set f functins that perfrm useful wrk, ften enabling ne r mre services [OMADICT] the ability t address push cntent between a particular user agent n a client and push initiatr n a server a netwrk used t carry the messages f a transprt-layer prtcl between physical devices. Multiple bearer netwrks may be used ver the life f a single push sessin. A device, user agent, r ther entity that acts as the receiver f a service [OMADICT] address infrmatin that describes hw t reach a push prxy gateway, including transprt prtcl address and prt f the push prxy gateway. Digitized wrk that is prcessed, stred, r transmitted. It includes such things as text, presentatin, audi, images, vide, executable files, etc. Cntent may have prperties such as media type, mime type, etc [OMADICT] when used as a verb, cntent encding indicates the act f cnverting a data bject frm ne frmat t anther. Typically the resulting frmat requires less physical space than the riginal, is easier t prcess r stre, and/r is encrypted. When used as a nun, cntent encding specifies a particular frmat r encding standard r prcess. actual representatin f cntent. Equipment which is nrmally used by users fr cmmunicatins and related activities. The definitin can be extended t cver remte mnitring applicatins where there is n user present, but the cmmunicatins t and frm the remte mnitr use the same cmmunicatins channels as when used by users [OMADICT] see "user" a push message cntaining a single address which implicitly specifies mre than ne OTA client address. Push cntent delivery t a grup f users thrugh the OTA-PTM Push-OTA prtcl variant. a prtcl used fr cnveying cntent that shuld be pushed t a client, and push related cntrl infrmatin, between a Push Initiatr and a Push Prxy/Gateway. A device-internal interface prvided by Push Clients, via which Push applicatins can register fr Push services with applicatin-specified ptins, and receive ntificatins f Push events. the entire push system. The push framewrk encmpasses the prtcls, service interfaces, and sftware entities that prvide the means t push data t user agents in the client. An entity r service that initiates Push cntent delivery t Push clients [OMADICT] a prtcl used fr cnveying cntent between a Push Prxy/Gateway and a certain user agent n a client. a prxy gateway that prvides push prxy services An active pint-t-pint transprt prtcl sessin ver which push peratins can be executed.

7 OMA-TS-PushCAI-V1_ A Page 7 (16) Push Whitelist Registratin Registratin Cntext Server Terminal Terminal-ID User User agent WAP Push XML 3.3 Abbreviatins a list stred in the Terminal f PPG addresses and/r SMSC addresses that are authrised t push Cntent t the Terminal. refers t a prcedure where the PPG becmes aware f the terminal s current capabilities and preferences. a state where the PPG is aware f at least the last capabilities and preferences cnveyed frm the terminal. An entity that prvides resurces t clients in respnse t requests [OMADICT] see "client". an identifier that is used by a PPG t uniquely identify a terminal. An entity which uses services. Example: a persn using a device as a prtable telephne [OMADICT] Any sftware r device that acts n behalf f a user, interacting with ther entities and prcessing resurces [OMADICT] Push cntent delivery t a specific user via the WAP1 (OTA-WSP) r WAP2 (OTA-HTTP) Push-OTA prtcl variants. The Extensible Markup Language is a Wrld Wide Web Cnsrtium (W3C) standard fr Internet markup language, f which WML is ne such language [OMADICT] ABNF BCAST CPI CBS CSD DNS GPRS HTTP IANA IP MBMS MSISDN OMA OTA OTA-HTTP OTA-SIP OTA-HTTP-TLS OTA-PTM OTA-SIP OTA-WSP Augmented Backus-Naur Frm OMA Bradcast Services Capability and Preference Infrmatin Cell Bradcast Service Circuit Switched Data Dmain Name Server General Packet Radi Service Hypertext Transfer Prtcl Internet Assigned Numbers Authrity Internet Prtcl Multimedia Bradcast/Multicast Service Mbile Statin Internatinal Subscriber Directry Number Open Mbile Alliance Over The Air (Push) OTA ver HTTP (Push) OTA ver SIP OTA-HTTP ver TLS (Push) OTA ver Pint-t-Multipint (Push) OTA ver SIP (Push) OTA ver WSP

8 OMA-TS-PushCAI-V1_ A Page 8 (16) PDP Packet Data Prtcl PDU Prtcl Data Unit PI Push Initiatr PO-TCP PPG Originated TCP cnnectin establishment methd PPG Push Prxy Gateway PTM Pint-t-Multipint QS Quality f Service RADIUS Remte Authenticatin Dial-In User Service RFC Request Fr Cmments SHA-1 Secure Hash Algrithm 1 SIA Sessin Initiatin Applicatin SIP Sessin Initiatin Prtcl SIR Sessin Initiatin Request SMS Shrt Message Service SMSC Shrt Message Service Centre TCP Transmissin Cntrl Prtcl TLS Transprt Layer Security TO-TCP Terminal Originated TCP cnnectin establishment methd UDP User Datagram Prtcl URI Unifrm Resurce Identifier URL Unifrm Resurce Lcatr WAP Wireless Applicatin Prtcl WDP Wireless Datagram Prtcl WSP Wireless Sessin Prtcl WTLS Wireless Transprt Layer Security

9 OMA-TS-PushCAI-V1_ A Page 9 (16) 4. Intrductin The OMA Push architecture enables a Push Client t register fr Push-based services n behalf f Push applicatins, and t subsequently deliver Push events t the Push applicatin. The Push Client may use varius ver-the-air (OTA) prtcls and data bearers in prviding Push service. Histrically, Push Clients have been implemented as embedded sftware functins in mbile devices, with pre-defined supprt fr specific Push applicatins, e.g. brwsers, Multimedia Messaging clients, Instant Messaging clients, etc. The Push Client typically registers as needed n behalf f these pre-defined Push applicatins, and includes its capabilities n their behalf in the vendr-published User Agent Prfile fr the device. While this apprach has supprted well the grwth f Pushbased services fr typical embedded Push applicatins, it des nt supprt the dynamic enhancement f devices fr new Push applicatins and services, e.g. thrugh installatin f dwnladable applicatins and OMA service enabler clients. This specificatin enables Push Clients t ptinally ffer a means fr Push applicatins t register fr Push services with applicatin-specified ptins fr the Push service, including: Prviding an applicatin name, which can be a unique identifier usable by OMA Push entities in service matching A Push Applicatin ID, which assciates the applicatin with an OMNA-registered Push service type r an unregistered (prprietary) Push service type A specified applicatin event handler fr receptin f Push events A selectin f Push Servers (e.g. Push Prxy Gateways r Push Applicatin Servers) frm which the Push Client shuld request service and expect Push events Push prtcls and data bearers t use fr Push Client registratin and Push event receptin Push event addressing at the Push Client, via which the Push Client can be directed t receive Push events at standard r alternate prts fr specific bearers A set f cntent types which the Push applicatin is cmpatible with, which may be used by the Push Client t negtiate capabilities with a Push Server This registratin and event receptin interface enables the dynamic extensin f the OMA Push enabler t new applicatins and OMA service enablers as described abve. 4.1 Versin 1.0 Versin 1.0 includes all f the functinality described in sectin Versin 1.1 Versin 1.1 includes functinality supprting Pint-t-Multipint Push, and supprt fr the Push Service Registratin prcedure defined in [PushOTA].

10 OMA-TS-PushCAI-V1_ A Page 10 (16) 5. Push Client - Applicatin Interface (Push-CAI) The term Push-CAI is used in this specificatin t refer t a generic interface defined as a set f functins and related data frmats enabling the high-level capabilities described in sectin 4, which cmprise verall: Push applicatin registratin with the Push Client, and subsequent deregistratin if required Push Client delivery f Push events t the Push applicatin The Push-CAI is defined in an implementatin-agnstic manner, since the implementatin f the Push-CAI in specific devices will depend upn the applicatin prgramming envirnments and runtime envirnments supprted by the devices. Thus definitin f a specific applicatin prgramming interface (API) is ut f scpe fr this specificatin. Hwever t supprt the basic set f interface functinality called fr in this specificatin, the Push-CAI makes the fllwing assumptins abut the interactin capabilities f the Push Client and Push applicatins: The Push Client supprts sme means f being invked fr registratin f the Push applicatin. This can be fr example thrugh a callable functin r a service access pint t which interface messages can be directed. The Push applicatin, thrugh the executin envirnment, supprts sme means f being invked fr Push event delivery frm the Push Client. Similar t the Push Client registratin functin, the Push applicatin may prvide this thrugh a callback functin r a service access pint t which interface messages can be directed. 5.1 Push Applicatin Registratin Push applicatins register with the Push Client thrugh delivery f an Applicatin Registratin request t the Push Client, and receiving an Applicatin Registratin respnse. The Applicatin Registratin may be successful r unsuccessful depending upn the Push Client s ability t handle the Push applicatin s specified ptins. Nte: interface parameter data types given belw are the recmmended types fr supprt by specific API implementatins. Where n data type is given, the type is expected t be API implementatin-specific. The Push applicatin must include the fllwing parameters in the Applicatin Registratin request: pushapplicatinid (string): an [OMNA] registered r unregistered (prprietary) Push Applicatin ID t be assciated with the Push applicatin. The Push applicatin may include the fllwing parameters as ptins in the Applicatin Registratin request: Applicatin ID (anyuri): name f the applicatin, recmmended as a unique identifier in the frm f a URI registered by the Push applicatin develper. Event Handler: handler fr incming Push events, defined per the capabilities f the device executin envirnment and Push applicatin preferences. May be unspecified if the device executin envirnment prvides default mechanisms fr Push event delivery t the Push applicatin. Whitelist (structure): set f addresses frm which Push events shuld be accepted per [PushMO]. If unspecified, the Push Client default whitelist (if any) is assumed t be cmpatible with the Push applicatin. ne f: Push Service Registratin URI (anyuri): the address where the Push Client shuld execute the Push Service Registratin prcedure [PushOTA], t receive applicable cnnectin prfile(s) fr the Push service Cnnectin Prfile (structure): ne r mre set f ptins fr Push event delivery, including

11 OMA-TS-PushCAI-V1_ A Page 11 (16) Prtcl (string): ne f OTA-WSP, OTA-HTTP, OTA-SIP, OTA-PTM, r ther implementatin-specific value. If unspecified, the default supprted prtcls are assumed t be cmpatible with the Push applicatin. Bearer Type (string): ne f the Push-SupprtedBearers defined in [UAPrfSchema], r ther implementatin-specific value. If unspecified, the default supprted bearers are assumed t be cmpatible with the Push applicatin. Prt (string): a specific prt number apprpriate fr the prtcl and bearertype. If unspecified, the default/standard prt shuld be used. Nte that the mechanisms fr crdinatin f nnstandard prt usage are unspecified, e.g. are assumed t ccur at the applicatin layer. Cntact Pint (string): the expected surce address f Push messages as applicable t the prtcl, e.g. fr OTA-WSP, OTA-HTTP, OTA-SIP, r OTA-PTM, the IP address, hstname, r URI f the PPG Cell BradcastMessageId (string): fr OTA-PTM with CBS bearer, the Cell Bradcast Message Identifier assciated with Push messages [TS23.041] MBMS User Service Descriptin: fr OTA-PTM with MBMS bearer, a MBMS User Service Descriptin element [TS26.346] BCAST Access Inf: Fr OTA-PTM with BCAST bearer, a Bcast-Access-Inf element [BCAST- SvcGuide] Accept (string): a set f MIME types f Push events which the Push applicatin specifically requests subscriptin t. The Push Client MUST reject an Applicatin Registratin indicating an already-registered Push Applicatin ID, unless: the Applicatin Registratin is received frm the same Push applicatin, r the Push Client supprts a mechanism t ensure uniqueness in Push applicatin registratin with the Push Server, and delivery f Push events intended fr the specific Push applicatin, e.g. The OTA-SIP prtcl is used. OTA-SIP prvides a means t uniquely identify distinct Push applicatins supprting the same Push Applicatin ID, via a media feature tag indentifying the specific applicatin instance, e.g. in IMS, via the IMS Applicatin Reference Identifier (IARI), as described in [Push-OTA]. in nn-ims SIP netwrks, using the same feature tag name The Push applicatin is registered fr event receptin at a unique bearer prt, by request f the Push applicatin. The Push applicatin s registratin is assciated with a specific binding t a Push bearer, e.g. a unique Push Service Registratin address, r OTA-PTM ver MBMS binding via a unique MBMS User Service Descriptin element The Push Client MUST reject an Applicatin Registratin with an ptin that is nt supprted r nt currently available. If it accepts the Applicatin Registratin request: The Push Client MUST respnd t the Push applicatin with an Applicatin Registratin respnse indicating registratin was accepted (pending further prcessing, e.g. registratin with a PPG), and If the Push applicatin prvided a Push Service Registratin URI, the Push Client MUST initiate the Push Service Registratin prcedure [PushOTA]. By default, the Push Client MAY initiate the Push Service Registratin prcedure using a pre-cnfigured Push Service Registratin address.

12 OMA-TS-PushCAI-V1_ A Page 12 (16) If the Push applicatin prvided a Cnnectin Prfile, the Push Client MUST initiate binding t the requested bearer as applicable, e.g. register with the Push Server (e.g. Push Prxy Gateway, Push Applicatin Server, r BM-SC) fr the Push applicatin, as applicable fr the prtcl and bearer, if supprted directly by the Push Client. By default, the Push Client MAY register with a Push Server using a pre-cnfigured cnnectin prfile. directly bind t the bearer, if the cnnectin prfile indicates a bearer which the Push Client directly supprts and fr which binding can be cmpleted by device-lcal actin nly. bind via a bearer-specific client (e.g. CBS receiver, MBMS receiver, r BCAST client) In registering with the Push Server, the Push Client MUST fllw the prcedures defined in [PushOTA] fr the prtcl and bearer, e.g.: use the applicable bearer fr the Applicatin Registratin indicate the new Push Applicatin ID fr OTA-HTTP, via the X-Wap-Push-Accept-AppID header prvided in the terminal's CPI fr OTA-SIP, via inclusin as a Push Resurce Identifier in a SIP REGISTER request sent t update the registratin with the SIP/IP Cre a SIP OPTIONS request sent t update the capabilities requested frm the Push Server indicate the specified MIME types, if any, via inclusin in fr OTA-HTTP, the X-Wap-Push-Accept header prvided in the terminal's CPI fr OTA-SIP, the SIP OPTIONS request sent t update the capabilities requested frm the Push Server If the lcal binding r registratin fails fr any reasn, the Push Client MUST respnd t the Push applicatin with an Applicatin Registratin respnse indicating an applicable failure reasn. Upn successful cmpletin f Applicatin Registratin, including actins taken a Push Server if required, the Push Client MUST respnd t the Push applicatin with an Applicatin Registratin respnse indicating registratin was successful. If it accepts an Applicatin Registratin cntaining a whitelist parameter, the Push Client MUST add the specified Push Servers t its current whitelist, fr the specific Push applicatin. The Push Client MUST retain the details f the registratin request fr future reference in a deregistratin prcess if required. 5.2 Push Applicatin Deregistratin Push applicatins deregister with the Push Client thrugh delivery f an Applicatin Deregistratin request t the Push Client, and receiving an Applicatin Deregistratin respnse. The Applicatin Deregistratin may be successful r unsuccessful depending upn validatin f the request by the Push Client. Nte: interface parameter data types given belw are the recmmended types fr supprt by specific API implementatins. Where n data type is given, the type is expected t be API implementatin-specific. The Push applicatin must include the fllwing parameters in the Applicatin Deregistratin request: pushapplicatinid (string): an [OMNA] registered Push Applicatin ID that is assciated with the Push applicatin. Nte that fr API implementatins, the Push Applicatin ID may be implicit in the way that the deregistratin is requested, e.g. call f a deregister methd n a registratin bject can implicitly refer t the Push Applicatin ID used when the registratin bject was created.

13 OMA-TS-PushCAI-V1_ A Page 13 (16) The Push Client MUST reject an Applicatin Deregistratin request if it determines that the requesting Push applicatin is nt currently registered fr events related t the Push Applicatin ID. If it accepts the Applicatin Deregistratin request, the Push Client MUST deregister with the Push Server (e.g. Push Prxy Gateway r Push Applicatin Server) fr the Push applicatin if the applicable Push prtcl supprts explicit deregistratin. In deregistering with the Push Server, the Push Client MUST: use the applicable bearer fr the Applicatin Registratin deliver an updated set f supprted Push Applicatin ID s, remving the Push Applicatin ID assciated with the deregistered Push applicatin fr OTA-HTTP, via exclusin in the X-Wap-Push-Accept-AppID header prvided in the terminal's CPI fr OTA-SIP, via exclusin as a Push Resurce Identifier in a SIP REGISTER request sent t update the registratin with the SIP/IP Cre a SIP OPTIONS request sent t update the capabilities requested frm the Push Server deliver an updated set f supprted MIME types, if any, remving any MIME types that were slely assciated with the deregistered Push applicatin fr OTA-HTTP, in the X-Wap-Push-Accept header prvided in the terminal's CPI fr OTA-SIP, in a SIP OPTIONS request sent t update the capabilities requested frm the Push Server Deregistratin with the Push Server MUST NOT affect current registratins f ther applicatins. Thus the actins abve will be taken nly if the deregistering applicatin is the sle registered applicatin f the type (by Push Applicatin ID), r the sle registered applicatin fr specific MIME types. If the registratin had included an update t the Push whitelist, the Push Client MUST remve frm the Push whitelist any Push Servers that were slely assciated with the deregistered Push applicatin. If the Push Client accepts the Applicatin Deregistratin request and successfully deregisters with the Push Server (if required), the Push Client MUST respnd t the Push applicatin with an Applicatin Deregistratin respnse indicating deregistratin success, If the deregistratin fails fr any reasn, the Push Client MUST respnd t the Push applicatin with an Applicatin Deregistratin respnse indicating an applicable failure reasn, 5.3 Push Event Delivery Push Clients deliver Push events t Push applicatins upn receptin f the Push event frm Push Server. The Push Client MUST include the fllwing parameters in the Push event: cntent: the Push cntent received in the Push event frm the Push Server cntent-type: the MIME type f the Push cntent applicatin-specific r standard HTTP headers, as received.

14 OMA-TS-PushCAI-V1_ A Page 14 (16) 6. Security Cnsideratins Push Clients r the device runtime envirnment in which they execute MAY enfrce unspecified security plicies n Push registratin requests. Unless such security plicies are enfrced, the Push Client MUST assume that the Push applicatin is trusted and authrized t request registratin with the OMA Push enabler. Nte that further security plicies may be applied by the netwrk, e.g. Push Server.

15 OMA-TS-PushCAI-V1_ A Page 15 (16) Appendix A. Change Histry (Infrmative) A.1 Apprved Versin Histry Reference Date Descriptin OMA-TS-PushCAI-V1_1 22 Nv 2011 Status changed t Apprved by TP: OMA-TP INP_Push_V2_3_ERP_fr_Final_Apprval

16 OMA-TS-PushCAI-V1_ A Page 16 (16) Appendix B. Static Cnfrmance Requirements (Nrmative) The ntatin used in this appendix is specified in [SCRRULES]. B.1 SCR fr Push Client Item Functin Reference Requirement CAI-C-001-M Push Applicatin 5.1 Registratin CAI-C-002-M Push Applicatin 5.2 Deregistratin CAI-C-003-M Push Event Delivery 5.3 CAI-C-004-O Security Cnsideratins 6