Abstract:
A server is disclosed. A method of handling information delivery for the server comprises sending information to at least one personal network entity (PNE) of a first group, wherein the first group comprises a plurality of PNEs. Besides, a method of handling information delivery for the gateway which transfers signals between a server and a plurality of personal network entities (PNEs) is also disclosed. The method comprises maintaining a group list and one corresponding group ID, wherein the group list indicates all personal network entities (PNEs) in one group and the PNEs share the group ID.

Description:
CROSS REFERENCE TO RELATED APPLICATIONS 
       [0001]    This application claims the benefit of U.S. Provisional Application No. 61/319,278, filed on Mar. 31, 2010 and entitled “Method for Instant Information Delivery in Extended Personal Area Network”, the contents of which are incorporated herein. 
     
    
     BACKGROUND OF THE INVENTION 
       [0002]    1. Field of the Invention 
         [0003]    The application relates to a method used in a personal network and related communication device, and more particularly, to a method for handling information delivery in a personal network and related communication device. 
         [0004]    2. Description of the Prior Art 
         [0005]    Nowadays users are increasingly connecting their devices to short-range Personal Networks (PNs) such as home networks, in-car networks and body area networks. Connecting these PNs to other networks can greatly extend the accessibility of the devices, or personal network elements (PNE(s)), in the PNs, enabling a number of compelling Services, including access by PNE(s) to services outside the PN (e.g. a Bluetooth-connected Personal Media Player (PMP) uses your cell phone&#39;s WAN connection to receive a video streamed from the Internet). 
         [0006]    Open Mobile Alliance (OMA) is the focal point for the development of mobile service enabler specifications, which support the creation of interoperable end-to-end mobile services. OMA drives service enabler architectures and open enabler interfaces that are independent of the underlying wireless networks and platforms. OMA creates interoperable mobile data service enablers that work across devices, service providers, operators, networks, and geography. Toward that end, OMA will develop test specifications, encourage third party tool development, and conduct test activities that allow vendors to test their implementations. 
         [0007]    The goal of OMA Converged Personal Network Services (CPNS) enabler is to provide application-layer support for ubiquitous access to services in a converged network, which is a collection of individual networks that are interconnected by means of PN Gateway (PN-GW) devices (in the example above, the cell phone assumes the role of a PN-GW that converges the Bluetooth and cellular networks to enable video to be streamed to the PMP from a network server). In the basic architecture of CPNS, three main CPNS enabler entities are the CPNS server, the PN-GW, and the PNE(s). The CPNS server is an entity of CPNS enabler that replies to requests from the PN-GW and ensures that the appropriate application is selected and appropriate content is provided to the PNE(s). The PN-GW serves as an intermediary entity between the PNE (s) and other networks that forwards the requests from the PNE(s) to the other networks and the other way around. The PN-GW can be a mobile phone, or an IP-enabled set-top box. The PNE(s) are PN entities that are connected to the PN-GW and between each other and are used for rendering the content received from the PN-GW or from each other. The PNE can be a mobile phone, a PC, a music player, car navigation system or an IP-enabled set-top box. A CPNS user may own a number of devices such as a mobile phone, a PC, a music player, and an IP-enabled set-top box. These devices construct an “Extended Personal Area Network” which is mentioned in 
       OMA-RD-CPNS-V1 — 0-20091117-C. 
     SUMMARY OF THE INVENTION 
       [0008]    A server is provided for handling information delivery. 
         [0009]    A server is disclosed. The server comprises a memory unit and a processor. The memory unit is used for storing a program code corresponding to a process. The processor is coupled to the memory unit and used for processing the program code to execute the process. The process comprises establishing a first group according to a first request and sending information to at least one accessible personal network entities (PNEs) of the first group, wherein the first group comprises a plurality of PNEs. 
         [0010]    A method of handling information delivery for a server is disclosed. The method comprises establishing a first group according to a first request and sending information to at least one accessible personal network entities (PNEs) of the first group, wherein the first group comprises a plurality of PNEs. 
         [0011]    A gateway for transferring signals between a server and a plurality of personal network entities (PNEs) is disclosed. The gateway comprises a memory unit and a processor. The memory unit is used for storing a program code corresponding to a process. The processor is coupled to the memory unit and used for processing the program code to execute the process. The process comprises maintaining a group list and one corresponding group ID, wherein the group list indicates all personal network entities (PNEs) in one group and the PNEs share the group ID. 
         [0012]    A method of handling information delivery for a gateway is disclosed. The gateway is used for transferring signals between a server and a plurality of personal network entities (PNEs). The method comprises maintaining a group list and one corresponding group ID, wherein the group list indicates all personal network entities (PNEs) in one group and the PNEs share the group ID. 
         [0013]    These and other objectives of the present invention will no doubt become obvious to those of ordinary skill in the art after reading the following detailed description of the preferred embodiment that is illustrated in the various figures and drawings. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0014]      FIG. 1  is a schematic diagram of an exemplary personal network. 
           [0015]      FIG. 2  is a schematic diagram of an exemplary communication device. 
           [0016]      FIG. 3  is a flow chart of an exemplary process. 
           [0017]      FIG. 4  is a flow chart of an exemplary process. 
           [0018]      FIG. 5  is a schematic diagram of another exemplary personal network. 
           [0019]      FIG. 6  is a schematic diagram of another exemplary personal network. 
           [0020]      FIG. 7  is a schematic diagram of another exemplary personal network. 
       
    
    
     DETAILED DESCRIPTION 
       [0021]    Please refer to  FIG. 1 , which is a schematic diagram of an exemplary personal network  10 . The personal network  10  comprises an application server, a converged personal network services (CPNS) server, a personal network gateway (PN-GW) and personal network entities (PNEs) PNE 1 , and PNE 2  (for simplicity, only two PNEs are shown in  FIG. 1 , but not limited herein). The CPNS server replies to requests from the PN-GW and ensures that the appropriate application is selected and appropriate content is provided to the PNE 1  and PNE 2 . The PN-GW serves as an intermediary entity between the PNE 1  and PNE 2  and other networks that forwards the requests from the PNE 1  and PNE 2  to the other networks and the other way around. Preferably, the PN-GW may be referred to as a mobile device, or an IP-enabled set-top box. The PNE 1  and PNE 2  share a group identity ID 1 . The group identity ID 1  is assigned by the server (e.g. PNID) or based on an account or a password of each PNE. The group identity ID 1  is identified by the PN-GW. The PNE 1  and PNE 2  are connected to the PN-GW and between each other and are used for rendering the content received from the PN-GW or from each other. The PNE 1  and PNE 2  may be referred to as a mobile device, a PC, a music player, car navigation system or an IP-enabled set-top box. In other words, a mobile device functions as the PNE or the PN-GW, depending on user&#39;s demand. 
         [0022]      FIG. 2  is a schematic diagram of an exemplary communication device  20 . The communication device  20  can be the server, the PN-GW, PNE 1 , PNE 2 , PNE 3  or PNE 4  shown in  FIG. 6  and may include a processor  200  such as a microprocessor or ASIC, a memory unit  210 , and a communication interfacing unit  220 . The memory unit  210  may be any data storage device that can store program code  214 , for access by the processor  200 . Examples of the memory unit  210  include but are not limited to a subscriber identity module (SIM), read-only memory (ROM), random-access memory (RAM), CD-ROMs, magnetic tapes, hard disks, and optical data storage devices. The communication interfacing unit  220  is preferably a radio transceiver for wirelessly communicating with the network according to processing results of the processor  200 . 
         [0023]    Please refer to  FIG. 3 , which is a flow chart of an exemplary process  30 . The process  30  is used for handling information delivery for the CPNS server shown in  FIG. 1 . The process  30  can be compiled into the program code  214  and include the following steps: 
         [0024]    Step  300 : Start. 
         [0025]    Step  302 : The PNE 1  sends a request R 1  to the server to create an extended personal area network G 1 . 
         [0026]    Step  304 : The PNE 2  registers to the server and joins the extended personal area network G 1 . 
         [0027]    Step  306 : The CPNS server sends instant information to the PNE 1  and PNE 2 . 
         [0028]    Step  308 : End. 
         [0029]    According to the process  30 , the PNE 1  first sends the request R 1  to the CPNS server to create the extended personal area network G 1 . The request R 1  is a request sent from a PNE to create the extended personal area network G 1 . All PNEs within the extended personal network G 1  share the same unique group identity. The PNE 2  registers to the server and join the extended personal area network G 1 . Since the PNE 1  and PNE 2  belong to the extended personal area network G 1 , the PNE 1  and PNE 2  share the same group identity ID 1 . When the server has the information for delivery, the server sends the information to both of the PNE 1  and PNE 2 . In other words, the server sends the information to the all PNEs in the same extended personal area network, and it doesn&#39;t matter whether one PNE is accessible or not. 
         [0030]    Please refer to  FIG. 5 , which is a schematic diagram of another exemplary personal network  10 . In  FIG. 5 , the personal network  10  includes a PNE 3 , which has the same group identity ID 1  and belongs to the same extended personal area network G 1 . In this situation, the CPNS server sends the information to the PNE 1  and the PNE 2  when the CPNS server receives the request R 1  from the PNE 1  and is not able to access to the PNE 3 . 
         [0031]    Please refer to  FIG. 6 , which is a schematic diagram of another exemplary personal network  10 . The extended personal area network G 2  includes a PNE 4 , which has the group identity ID 2 . In this situation, the PN-GW maintains a group list of extended personal area networks (e.g. G 1  and G 2 ) and one or more group identities. Each of the one or more group identity (e.g. ID 1  and ID 2 ) corresponds to a group. When the PNE 2  registers to the server, the PNE 2  chooses an extended personal area network of interest (e.g. G 1  or G 2 ) to join. If the PNE 2  chooses the extended personal area network G 1 , the PNE 2  shares the same group identity ID 1  with the PNE 1 . The CPNS server receives a request R 2  from the extended personal area network G 2  for information delivery. The request R 2  is a request sent from the extended personal area network G 2  to deliver information to the PNEs. However, the PNE 1  is out of service and the CPNS server is not able to access to the PNE 1 . At this moment, the CPNS can send the information to the PNE 2  instead. 
         [0032]    Please refer to  FIG. 7 , which is a schematic diagram of another exemplary personal network  10 . In  FIG. 7 , the CPNS server connects to an external network. The CPNS server receives a request R 3  from the external network for information delivery. The request R 3  is a request sent from the external network to deliver information to the PNEs. The CPNS can send the information to the PNE 2  when the CPNS server is not able to access to the PNE 1 . 
         [0033]    According to aforementioned examples, the CPNS receives a request from the PNE 1 , the extended personal area network G 2  or the external network for information delivery. When the CPNS user can not get access to one of its PNE inside the extended personal area network (e.g. the laptop), any information from the CPNS server intended to send to this user can then be notified and delivered immediately to all PNEs inside the extended personal area network (e.g. the mobile phone, the PMP or the car navigation system). And, it doesn&#39;t matter whether one PNE is accessible or not. 
         [0034]    In another example, the PNE 1  (e.g. PMP or mobile phone) sends the request R 1  to the CPNS server for downloanding the latest information (e.g. MP3 or maps). However, the application server is temporarily unavailable for the service. The CPNS user might switch off this PNE. With this information delivery mechanism, once the corresponding application server is ready, the CPNS server informs at least one PNE inside the extended personal area network (PNE 1  and/or PNE 2 ). If the application server is ready but the PNE 1  is still inaccessible, the CPNS server sends information to the PNE 2 . And it doesn&#39;t matter whether one PNE is accessible or not. 
         [0035]    Please refer to  FIG. 4 , which is a flow chart of an exemplary process  40 . The process  40  is used for handling information delivery for the PN-GW shown in  FIG. 1 . The process  40  can be compiled into the program code  214  and include the following steps: 
         [0036]    Step  400 : Start. 
         [0037]    Step  402 : Maintain the group list of extended personal area networks and the group IDs. 
         [0038]    Step  404 : End. 
         [0039]    According to the process  40 , the PN-GW maintains the group list of the extended personal area networks (e.g. G 1  and G 2 ) and the group IDs (ID 1  and ID 2 ). The detailed descriptions of the PN-GW can be found above, and thus is omitted herein. 
         [0040]    Please note that the abovementioned steps including suggested steps can be realized by means that could be hardware, firmware known as a combination of a hardware device and computer instructions and data that reside as read-only software on the hardware device, or an electronic system. Examples of hardware can include analog, digital and mixed circuits known as microcircuit, microchip, or silicon chip. Examples of the electronic system can include system on chip (SOC), system in package (Sip), computer on module (COM), and the communication device  20  in which the processor  200  processes the program code  214  related to the abovementioned processes and the processed results can handle information delivery in the personal network  10 . 
         [0041]    To sum up, a CPNS user can create an extended personal area network in which all of the devices in share the same group identity. When any information is issued from server to one of PNEs inside the extended personal area network, this information will be shared and delivered to all PNEs inside the extended personal area network sharing the same group identity. The present embodiment utilizes the information which might be important and urgent efficiently and instantly, especially benefits while any PNE inside the extended personal area network is inaccessible or while application server is not yet ready to provide requested service for the PNEs. And it doesn&#39;t matter whether one PNE is accessible or not. 
         [0042]    Those skilled in the art will readily observe that numerous modifications and alterations of the device and method may be made while retaining the teachings of the invention. Accordingly, the above disclosure should be construed as limited only by the metes and bounds of the appended claims.