1. Inventin Title. Light Transprt and Data Serializatin fr TR-069 Prtcl 2. Inventin Summary. This inventin defines a light prtcl stack fr TR-069. Even thugh TR-069 is widely deplyed, its prtcl infrastructure is heavy cmpared t web standards used tday. Alternative prtcls and data representatin will be beneficial fr easier adptin in new breed f devices that fill the netwrk. 3. Inventin Descriptin. a. Describe the inventin in detail. Claims 1. Imprve Device/ACS cmmunicatin by using in additin t the TR-069 Ntificatin and Cnnectin Request messaging a websckets mdel fr the request/respnse messaging used t manage the device, eliminating the TR-069 reverse HTTP dialg. Use the existing TR-069 Ntificatin mechanism t cmmunicate the use f Websckets. Advertise WebScket Supprt (Infrm Request) Reference WebScket URL (Infrm Respnse) This effectively separates Device Registratin (Infrm & Cnnectin Request) frm CPE/ACS management dialg. 2. Usage f WebSckets Encapsulate Request Types as WebScket Tkens. This eliminates the need fr SOAP as the encapsulatin mechanism. Furthermre, instead f Webscket Tkens, e.g., a STOMP client as a cnsumer can be used as a layer n tp f the Webscket t handle transactins, much mre simpler and pwerful than the SOAP. Hwever, it is still pssible t keep the SOAP layer n tp f the Webscket e.g., t make a minimal change in an existing implementatin. Encapsulate Data Request/Respnse in JSON frmat r current TR-069 XML. Defines private and public channels in rder t better scale data distributin Private Channels used fr Cnfiguratin and Mnitring Public Channels used fr ACS t cmmunicate cmmn plicies t a grup f devices. WebSckets can be seen as a suthbund adapter t a general bus architecture fr device access The WebSckets can be seen as a suthbund adapter t a general bus architecture fr device access Claims Discussin Page 1
Claim 1: TR-069 prtcl cnversatin is dne in tw ways: CPE Initiated Dialg (Ntificatin Request Respnse) See figure 1 ACS Initiated Dialg (Cnnectin Request) See Figure 2 The CPE Initiated dialg ccurs at bt time and at a scheduled r peridic interval if cnfigured. During the Ntificatin time the ACS has the pprtunity t request infrmatin t the device and perfrms ther management peratins. The ACS Initiated Dialg cnsist f an ACS HTTP GET send t the device that triggers the Ntificatin prcess, falling back t the previusly described prcedure Figure 1 Device Initializatin/Scheduled/Peridic Infrm Cnnectin Figure 2 ACS initiated Cnnectin By Using Websckets, the Device/ACS cmmunicatin stays ver a lighter cnnectin (WebSckets have much less verhead than HTTP) and fixes the TR-069 reverse HTTP mdel), being able t use regular websckets framewrks (including RPC request/respnse patterns). Tday Implementers need t adapt HTTP framewrks t supprt the TR-069 Page 2
reverse dialg mdel. The aggregate effect is faster cnnectins, less resurces and cmparatively similar scalability as the current HTTP mdel. In Figure 3 The device initiates a HTTP cnnectin, the regular TR-069 infrm messaging exchange. After authenticatin, The WebScket Infrmatin is made available t the device. The device pens the WebScket Cnnectin and maintains it alive. The HTTP sessin can remain pen r clsed and the Webscket nw handles the exchange f infrmatin. This will nrmally happen at bt time r at peridic/scheduled infrm, preserving the TR-069 state mdel. Figure 3 Device Initiated WebScket In figure 4 the same TR-069 Cnnectin Request is used t trigger the WebScket Cnnectin (in case the webscket cnnectin is clsed). This mde f peratin is als cmpatible with the existing mde f peratin. Figure 4 ACS initiated webscket Claim 2: TR-069, prvides a pint-t-multi-pint cmmunicatin mdel (ACS t ne r mre devices). A nrthbund interface is needed t cmmunicate frm external systems thugh the ACS. The SNMP Mdel used in Cable is mre flexible as it is multipint-t-multipint fashin but lacks f cntrl besides read/write access is pssible Using websckets channels sme interesting cnfiguratins can be achieved. Supprt either pint-t-multipint as traditinal TR-069 des, but als prvide multipint-t-pint with cncrete plicies t manage public and private channels channels. Page 3
Decentralizatin f peratins by allwing adhc managers t temprarily interact with ne r mre devices. Fr example, trubleshting sessins. Share infrmatin with ther management systems and applicatins using the enterprise bus. Figure 5 shws the current TR-069 mdel. The ACS acts as a brker fr the managed devices. The interactins frm a separate entity (ther NMSs, Management cnsles) use prprietary means. Figure 5 TR-069 Management Mdel Figure 6 shws the separatin f management and cntrl functins f the ACS f the prpsed mdel. The Device Registratin (i.e., Infrm, Cnnectin Request), and device management (request/respnse messaging) via websckets. The architecture is further enhanced by decupling the lgic and state machine f the ACS int a distributed system by using an enterprise bus. There are many available slutins that cnnect websckets t enterprise buses. Figure 6 Prpsed TR-069 Prtcl Infrastructure Management entities dmains. The lightweight aspects f this inventin expand the TR-069 capabilities beynd netwrk devices and target the management f mbile devices and even applicatins and Web Page 4
applicatins. Applicatin framewrks such as ios, Andrid, Linux packaging, OSGi and thers can be brught t the management plane. This allw targeting the fllwing managed clients Netwrk, appliances and mbile devices. Standalne applicatins using a cmmn management API at the OS level r each applicatin embedding the prper management stack. Web applicatins (ephemeral sessins). The web applicatin lads the management client entity and infrmatin cntext (instead f the TR-069 ntificatin schema) during the web page dwnlad. In the security side, web applicatins will be restricted t same t same rigin plicy as any web brwser fr the WebScket creatin. But this restrictin des nt apply t all ther mdels b. Why was the inventin develped? What prblem(s) des the inventin slve? Hw is it better? TR-069 is well psitined in the telecmmunicatin industry fr CPE management. Hwever, its implementatin is nt trivial. A new set f devices (E-Health, Electrical Grid) culd take advantage f the TR-069 infrastructure if the cmmunicatin prtcls are light and simpler. c. Briefly utline the ptential cmmercial value and custmers f the inventin. Currently millins f devices supprt TR-069. This inventin can prvide a faster path fr fast implementatin and brader adptin fr the benefit f Service Prviders and users alike. 4. HOW is this inventin different frm existing prducts, prcesses, systems? This inventin disclsure is intended t extend the TR-069 prtcl and dcuments the IPR aspects f this inventin and hw t integrate int the current prtcl. Page 5