WO2011155734A2 - 다른 장치와 통신 하는 방법 및 통신 기기 - Google Patents
다른 장치와 통신 하는 방법 및 통신 기기 Download PDFInfo
- Publication number
- WO2011155734A2 WO2011155734A2 PCT/KR2011/004100 KR2011004100W WO2011155734A2 WO 2011155734 A2 WO2011155734 A2 WO 2011155734A2 KR 2011004100 W KR2011004100 W KR 2011004100W WO 2011155734 A2 WO2011155734 A2 WO 2011155734A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mode
- pne
- cpns
- entity
- information
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
- H04W4/203—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel for converged personal network application service interworking, e.g. OMA converged personal network services [CPNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/005—Discovery of network devices, e.g. terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/16—Gateway arrangements
Definitions
- the present invention relates to a converged personal network service (CPNS).
- CPNS converged personal network service
- CPNS allows devices to receive various services belonging to a personal network (PN) (also called a personal area network (PAN)).
- PN personal network
- PAN personal area network
- the CPNS is implemented through a CPNS server, a CPNS gateway, and a device supporting CPNS. There may also be generic servers and generic devices.
- the CPNS is a PN based on a private network, and a bundle of devices is referred to as a PN, the CPNS gateway is placed in the PN, and through this, services of devices belonging to the PN are registered with the CPNS server, and then a predetermined service is provided.
- a device can be searched from the CPNS server, and an external entity can share a service provided by the device based on the search.
- the CPNS gateway serves as a PN (gateway (also referred to as 'GW')) to connect the PN to another network.
- the CPNS device is also referred to as a personal network entity (PNE), and becomes a member of the PN. Multiple devices may be grouped into a single PNE, or a single device may be a PNE.
- 1 is an exemplary view showing the concept of CPNS.
- a general server As shown in FIG. 1, a general server, a CPNS server, a CPNS gateway, a CPNS device, and a general device are shown.
- the CPNS server may communicate with one or more CPNS gateways (ie, PN gateways) and transmit and receive data.
- CPNS gateways ie, PN gateways
- Each CPNS server may exchange data by communicating with one or more CPNS devices in a PN (or PAN (or Personal Area Network)) via the CPNS gateway.
- Each of the CPNS devices may exchange data with one or more other CPNS devices or general devices through the CPNS gateway.
- the CPNS gateway may communicate with a CPNS server, a CPNS gateway belonging to another PN, or a CPNS device to transmit and receive data.
- Each CPNS server may transmit and receive data by communicating with a general server and a CPNS gateway.
- the CPNS server and the CPNS gateway may communicate with each other using a cellular network
- the CPNS gateway and the CPNS device may communicate with each other using short-range communication such as Bluetooth, NFC, Zigbee, Wi-Fi, and the like. have.
- the CPNS server manages and controls communication between the CPNS gateway and the CPNS device, thereby exchanging applications and information with each other, thereby enhancing a user experience.
- a user acquires location information from another CPNS device (eg, a GPS) using any CPNS device, transmits the location information to a CPNS server via the CPNS gateway, and from the CPNS server.
- Location-based services can be provided.
- the user may be provided with various services through various CPNS devices belonging to the PN.
- an object of the present specification is to present a detailed technology for implementing a CPNS service.
- an embodiment of the present invention provides a method for communicating with another apparatus performed by a communication device having a Converged Personal Network Service (CPNS) enabled entity.
- CPNS Converged Personal Network Service
- the communication method may further include: first discovery that a CPNS enable entity of the communication device set to a gateway mode is set from a first device to a mode of the first device to a personal network entity (PNE) and further discovery of the first device; And receiving a search response message that includes second information indicating whether to be hidden in the procedure.
- the CPNS enable entity may manage a first network, and there may be at least one personal network entity (PNE) capable of receiving a first service through a CPNS enable entity configured as the gateway in the first network.
- the communication method includes receiving a search request message from the second device that includes third information indicating a mode of the second device when the communication device moves into coverage of a second network managed by a second device.
- the mode of the CPNS enable entity is changed from the gateway mode to the combined mode. Can be determined.
- the combined mode may be a mode for simultaneously driving in the gateway mode and the PNE mode.
- the available PNE may be a PNE located within the coverage of the second network, supporting the communication scheme of the second network, and having sufficient power to receive a service of the second network.
- the determining may further include the CPNS enable entity confirming its mode information. As a result of confirming the own mode information, when the gateway mode and the PNE mode can be simultaneously driven, it may be changed to the combined mode.
- the mode of the CPNS enable entity may be determined to change from the gateway mode to the PNE mode, or may be determined not to perform a mode change.
- the communication method may further include transmitting a discovery response message to the second device in response to receiving the discovery request message.
- the discovery response message may include mode information indicating that the first device is operated in the combined mode.
- the discovery response message may include information on other PNEs other than the first device.
- the communication method further comprising: after changing to the combined mode, the CPNS enabled entity receiving service data of the second network from the second device as a PNE; Delivering, by the CPNS enabled entity, the service data to the entity as a gateway;
- an embodiment of the present invention also provides a communication device.
- the communication device may include a storage configured to store a Converged Personal Network Service (CPNS) enabled entity set to the gateway mode.
- CPNS Converged Personal Network Service
- the CPNS enable entity may manage a first network, and there may be at least one personal network entity (PNE) capable of receiving a first service through a CPNS enable entity configured as the gateway in the first network.
- PNE personal network entity
- first information indicating that the mode of the first device is set to a personal network entity (PNE) from the first device and the first device should be hidden in an additional discovery procedure.
- One embodiment of the present invention solves the problems of the prior art as described above. That is, an embodiment of the present invention provides a detailed technology for implementing a CPNS service.
- 1 is an exemplary view showing the concept of CPNS.
- 2 is an exemplary view showing the entire CPNS procedure.
- FIG. 3 shows the architecture of the first and second devices shown in FIG. 2.
- FIG. 4 is an exemplary view showing an initial CPNS procedure.
- 5 illustrates an example in which user A's PN overlaps with another PN as user A performs geographical movement.
- FIG. 6 is an exemplary diagram illustrating a signal flow of a physical connection procedure and a discovery procedure generated by the example illustrated in FIG. 5.
- FIG. 7 is an exemplary diagram illustrating a first embodiment for preventing a predetermined device from performing a pairing procedure.
- FIG. 8 is an exemplary view illustrating a second embodiment for hiding a given device in a mutual discovery procedure.
- FIG 9 is an exemplary view showing a third embodiment for hiding a predetermined device.
- FIG. 10 shows a signal flow diagram for changing a mode of a CPNS enable entity.
- 11 shows a process of changing a mode of a CPNS enable entity.
- FIG. 13 shows an example of adjusting a sync after a mode of a CPNS enable entity is changed.
- 15 is a configuration block diagram of a device according to embodiments of the present invention.
- the present invention relates to a converged personal network service (CPNS).
- CPNS converged personal network service
- the present invention is not limited thereto, and the present invention may be applied to all communication systems, methods, and other systems to which the technical spirit of the present invention may be applied.
- first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.
- first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component.
- the terminal may include a user equipment (UE), a mobile equipment (ME), a mobile station (MS), a user terminal (UT), a subscriber station (SS), a wireless device (Wireless Device), It may be called a handheld device or an access terminal (AT).
- the terminal may be a portable device having a communication function such as a mobile phone, a PDA, a smart phone, a wireless modem, a laptop, or the like, or a non-portable device such as a PC or a vehicle-mounted device.
- CPNS Converged Personal Network Service
- PN personal network
- PAN personal area network
- CPNS allows devices to receive various services belonging to a personal network (PN) (or also called a personal area network (PAN)).
- PN personal network
- PAN personal area network
- a tethering service is simply a device connected to the Internet assigns a private IP address to another device using NAT technology, so that the other device uses the private IP to connect to the Internet. It's a technology that lets you connect.
- CPNS allows the first device to integrate and manage various services that can be provided through a mobile communication network, instead of simply assigning a private IP address to another device of the user.
- the first device of the user is integrated and managed, so that the service can be seamlessly shared among the various devices of the user.
- video on demand may be used by a user's first device and seamlessly delivered to a second device. Therefore, the user's convenience can be increased.
- the user owns several devices, even if the external server does not request the user, if the user wants to deliver the service data, it is possible to determine which one of the various devices to transmit. For example, when the user has several devices capable of making a video call, when the user receives a video call request, the user can determine which of the various devices should forward the video call call.
- the ongoing video call can be transferred to the other device of the user without interruption.
- Such CPNS is achieved by a CPNS enable entity provided in the user's device.
- CPNS Enable Entity There are three types of CPNS Enable Entity as a logical entity entity. That is, there may be a PNE, PN GW, CPNS server. The CPNS server entity is located in the core network, and the PNE and PN GW are located in the CPNS device.
- CPNS device A device that can operate in multiple modes simultaneously in a private network.
- the CPNS device has a function of processing, storing and playing content, and the CPNS device may also have a communication interface that allows other CPNS devices to operate in different modes within a private network.
- CPNS Server A functional entity capable of providing resources to CPNS entities in response to a request or in a push manner. Receive registration of device and user related services, store relevant information, and provide registration of PN, which is a bundle of devices, and registration of service group covering PN and WAN. In addition, the CPNS server may communicate with external entities such as a content providing server.
- the CPNS server is a subject that sets a key for authenticating that the user has a device in order to perform a service on the CPNS framework. It also registers externally provided services and supports search and consumption / providing requests for consumption by devices.
- PN Personal Network
- All devices in the PN may be connected to the PN GW.
- PN may change over time.
- the PN may include at least a device operating in the GW mode and another device operating in the PNE.
- PNE Abbreviation for Personal Network Element, a member of the PN.
- the PNE may consume or provide a service or content. It is the subject that consumes the actual content, application, and service. It is the subject that becomes a member when creating a PN and creating a service group within the CPNS framework.
- PN GW An acronym for Personal Network Gateway, which is an entity existing in the PN and wide area networks, and can create a PN providing CPNS services. It also manages heterogeneous networks for devices that exist in the PN and cannot be externally connected, and registers and manages CPNS servers for connected devices.
- the PN GW in the device allows not only the PNEs present in the PN but also other devices to connect with the CPNS server.
- the PN GW present in the device uses a global network such as a mobile network.
- the PN GW manages services with PNEs, and manages communication and various other functional information.
- PN Inventory A list of PNs and devices belonging to a PN and several PNs.
- Service Group A collection of PNEs and PN GWs that share services, data and applications. It means a bundle of devices registered in the server through the generated PN. At this time, the devices that are members of the Service Group do not have to be subordinated in a single PN, and include all devices that belong to multiple PNs and cannot be connected to each other because they are located far apart from each other, and need not be devices owned by the same user. .
- Zone means a specific regional zone.
- Zone based service means CPNS server provided within the coverage of Zone based PN GW.
- Zone PN GW A PN GW that provides unique services or content within a zone.
- CPNS device may operate in PN GW, PNE mode.
- the mode may be identified between devices through CPNS entity discovery function.
- the PN must include a device operating with a minimum PN GW and a PNE operating with a PNE.
- the PNE and the PN GW must know each other's modes in order to create or join a PN.
- the PN GW must be able to identify the PNE in order to make a member of the PN.
- the PNE needs to know the PN GW in order to create a new PN or to join a previously created PN.
- the device If there is a device (eg MP3 player, smart meter) that supports only PNE mode, the device operates only in PNE mode. If a device can only operate with PN GW, the device operates with PN GW. However, when a device can operate in either PN GW or PNE, the mode of the device may operate in either one according to a pre-stored setting value, and may be changed according to a user's setting or an operator's setting.
- a device eg MP3 player, smart meter
- 2 is an exemplary view showing the entire CPNS procedure.
- the first device 110 the second device 120, the CPNS server 300, and the application server 400 are shown.
- the first and second devices 110 and 120 are devices owned by user A.
- the first device 110 is a cellular phone of user A, and may include a first transceiver for connecting to the CPNS server 300 through a mobile communication network.
- the first device 110 may include a second transceiver, such as a blue pitcher, WiFi, and Zigbee, to form a personal network.
- the second device 120 is a portable multimedia device of the user A, and does not have a first transceiver for communicating with a mobile communication network, but may have a second such as a blue pitcher, WiFi, Zigbee, etc. that can form the personal network. Only the transceiver may be provided.
- the first and second devices 110 and 120 may have a CPNS enable entity.
- Each CPNS enable entity may operate in a gateway mode or a personal network entity (PNE) mode.
- PNE personal network entity
- FIG. 2 shows that the second device 120 operates as a gateway since the second device 120 has a first transceiver that can be connected through the mobile communication network.
- the first device 110 and the second device 120 When the first device 110 and the second device 120 are located close to each other first, the first device 110 and the second device 120 perform a physical connection procedure through the second transceiver. Meanwhile, the application server 400 registers or advertises a service and content in the CPNS server 300. In addition, the CPNS server 300 performs a procedure for authenticating the second device 120 acting as the gateway.
- each CPNS enable entity performs a procedure of searching for each other.
- the devices When the search is completed, the devices set PN # 1. At this time, the information on the PN # 1 is registered in the CPNS server 300.
- the CPNS server 300 advertises its own service to devices in the PN # 1 or searches for a service that can be provided by the devices in the PN # 1.
- any device in the PN # 1 invokes any service or content among the advertised services, a procedure for checking the function of the arbitrary device is performed, and the service or content is delivered according to the checked function. do.
- the usage statistics are collected and reported to the CPNS server 300 or the application server 400.
- the PN # 1 may be released and information on the PN # 1 may be deregistered from the CPNS server 300.
- FIG. 3 shows the architecture of the first and second devices shown in FIG. 2.
- a physical layer, a MAC layer, a 3rd layer, a CPNS enable entity, and an application layer exist in the first and second devices 110 and 120.
- the CPNS enable entity of the second device 120 is driven in the PNE mode, and the CPNS enable entity of the first device 110 drives only the gateway entity.
- the CPNS enable entity of the first device 110 moves the gateway entity.
- the service data is delivered to the gateway entity in the CPNS enable entity through the physical layer, the MAC layer, and the 3rd layer of the first device 110.
- the gateway entity of the first device 110 receives the service data
- the service data is transmitted to the second device 120 via a CPNS enable entity, a 3rd layer, a MAC layer, and a physical layer.
- the second device 120 receives the PNE of the CPNS enabled entity through the physical layer, the MAC layer, and the 3rd layer.
- the PNE in the CPNS enable entity of the second device 120 transmits a control message such as a request message or a response message to the first device 110 through the 3rd layer, the MAC layer, and the physical layer.
- FIG. 4 is an exemplary view showing an initial CPNS procedure.
- a paring procedure (S11), an entity discovery procedure (S12), and a PN establishment procedure (S13) corresponding to a physical connection procedure are performed.
- the second device 120 starts a scan.
- the second device may transmit a scan message to the first device 110.
- the first device 110 transmits a scan response message to the second device 120 in response to the scan.
- a procedure for the physical connection is started between the first device and the second device, and information for the physical connection, for example, information such as an address and an IP address, is exchanged with each other.
- the second device sends a physical connection request message, such as a Paring Request message, to the first device.
- the first device receives a pin code from a user and includes the pin code in a connection request response message, for example, a Paring Answer message, to transmit the pin code to the second device. If the pin code is correct, the physical connection procedure is completed.
- CPNS-enabled entities in each device perform a procedure for searching each other, that is, an entity discovery procedure (S12).
- the CPNS enable entity of the second device 120 transmits a discovery request message, for example, an Entity Discovery Request message, to the first device 110.
- the discovery request message for example, an Entity Discovery Request message, includes information about a mode of a CPNS enable entity in the second device, and information about the CPNS enable entity and other devices discovered previously.
- the mode information may include information indicating that the gateway.
- the CPNS enable entity of the first device 110 also transmits a discovery request message, for example, an Entity Discovery Request message, to the second device 120.
- the discovery request message eg, an Entity Discovery Request message
- the mode information may include information indicating the PNE.
- the CPNS enable entity of the first device 110 transmits a discovery response message, for example, an Entity Discovery Response message, to the second device 120.
- the discovery response message for example, an Entity Discovery Response message, includes mode information, information on the CPNS enabled entity and other devices discovered previously, and information on a UI function.
- the CPNS enable entity of the second device 120 also transmits a discovery response message, eg, an Entity Discovery Response message, to the first device 110 in response to receiving the discovery request message from the first device.
- a discovery response message eg, an Entity Discovery Response message
- the PN setup request message for example, the PN Setup Request message
- the device eg, the first device 110
- the PN configuration request message may include information about the gateway, information about entities (eg, CPNS enable entity in the first device) that will belong to the PN to be generated.
- the CPNS enable entity of the first device transmits a PN setup response message, eg, a PN Setup Response message, to the second device
- a PN setup response message eg, a PN Setup Response message
- the CPNS server 300 When the CPNS server 300 receives the PN setup request message, the CPNS server 300 transmits an authentication request message and an Authenticate Request message to the first device through the second device 120 operating as the gateway. In response to the authentication request message, the first device transmits an authentication response message, for example, an Authenticate Response message, to the CPNS server 300 through a second device operating as the gateway.
- an authentication response message for example, an Authenticate Response message
- the CPNS server 300 transmits a PN setup response message to the second device 120 operating as the gateway.
- the CPNS enable entity of the second device 120 acting as the gateway transmits a PN establishment completion notification message, for example, a PN Establishment Notify message, to the first device.
- the application server 400 such as a content server sends a Service Description Advertisement message including information about its service through the CPNS server 300 to the second gateway. May be transferred to device 120. Then, the second device 120 as the gateway delivers the Service Description Advertisement message to devices belonging to the PN managed by the gateway.
- FIG. 5 illustrates an example in which user A's PN overlaps with another PN as user A moves geographically
- FIG. 6 illustrates an example of a signal flow of a physical connection procedure and a discovery procedure generated by the example illustrated in FIG. 5. It is also.
- FIG. 5A illustrates three PNs, a CPNS server, and an application server.
- PN # 1 of the three PNs is generated by user A.
- the PN # 1 is composed of devices of the user A.
- the PN # 1 may include the GW # 1 and the PNE # 1 as shown.
- GW # 1 is the user A's cellular phone
- PNE # 1 is the user A's portable multimedia device.
- PN # 2 includes GW # 2 and PNE # 2
- PN # 3 includes GW # 3 and PNE # 3.
- the application server may provide a service to PNEs in each PN through the CPNS server and the GW # 1, GW # 2, and GW # 3.
- PN # 1 and PN # 2 configured by GW # 1 and PNE # 1 of user A overlap. That is, GW # 1 and PNE # 1 belonging to PN # 1 of user A are included in the coverage of PN # 2.
- a first device of user A performs a pairing and discovery procedure with GW # 2
- a second device of user A performs a pairing and discovery procedure with GW # 2. do.
- user A needs to input the pin code several times, which is cumbersome.
- four signals are transmitted and received as shown in FIG. 2 for the discovery procedure. Considering that the discovery procedure is performed four times in total, as many as 16 messages are transmitted and received, it becomes very complicated.
- FIG. 7 is an exemplary diagram illustrating a first embodiment for preventing a predetermined device from performing a pairing procedure.
- the first embodiment allows a user to select or modify a preferred device and a device to be hidden in a later physical connection procedure.
- user A owns a second device 120 acting as a PNE and a first device 110 acting as a gateway.
- the second device 120 is a portable multimedia device
- the first device 110 is a cellular phone.
- a physical connection procedure is performed. Subsequently, a mutual search procedure is performed between the first device 110 and the second device 120, and a PN # 1 setting procedure is performed.
- the user A selects and inputs a preferred device for physical connection with another device from among devices belonging to the PN # 1 using the first device 110.
- the user A selects a device to be hidden when performing a procedure for physical connection with another device using the first device 110.
- the first device 110 stores the setting information by the user in a database and transmits the setting information to the second device 120.
- the second device 120 stores the configuration information in a database.
- the user A may change the setting by using the first device 110.
- the first device 110 may transmit the changed setting information to the second device 120.
- the user A uses the first device 110 to make and change the selection.
- the user A may perform the selection through the second device 120.
- the user A may access and set the CPNS server 300 using a device other than the first device and the second device.
- the CPNS server 300 may transmit the configuration information to the first device 110 and the second device 120.
- the third device 210 belonging to the PN # 2 may transmit a scan message to scan the first device 110 and the second device 120.
- each device may check its configuration and determine whether to respond to the scan message. If it is determined that the first device 110 is the preferred device according to the set value, the first device 110 transmits a scan response message, for example, an Answer Scan message, to the third device 210 and performs a physical connection procedure.
- the second device 120 may ignore the scan message and do not transmit a scan response message or transmit a message indicating rejection.
- the user can select a preferred device and a device to be hidden in the future physical connection procedure, thereby preventing unnecessary physical connection procedures from being performed.
- FIG. 8 is an exemplary view illustrating a second embodiment for hiding a given device in a mutual discovery procedure.
- the second embodiment allows a user to select or modify a device to hide in a later mutual search procedure.
- user A owns a second device 120 acting as a PNE and a first device 110 acting as a gateway.
- the second device 120 is a portable multimedia device
- the first device 110 is a cellular phone.
- the user A selects a device that the user wants to hide in a later mutual search procedure.
- the first device 110 and the second device 120 When the first device 110 and the second device 120 are located near each other, the first device 110 and the second device 120 perform a physical connection procedure.
- a mutual discovery procedure is performed between the first device 110 and the second device 120. Specifically, first, if the CPNS enable entity in the first device 110 is set to the gateway, immediately after the physical connection is completed, a discovery request message, for example, a discovery request message is transmitted. In this case, if the CPNS enable entity in the first device 110 transmits the second device 120 at the same time without first transmitting the information, the information may overlap.
- the first device 110 acting as a gateway immediately transmits a discovery request message immediately after the physical connection is completed.
- the discovery request message may include an element indicating whether information should be hidden according to a user setting, for example, a sharing element. That is, if the user chooses to share all PNEs in the gateway and PN, the Sharing element is set to a value indicating open or shared, and the user selects that only information about the gateway is shared. In this case, the sharing element may be set to a value indicating blocked or protected.
- the discovery request message may include the following elements.
- EntityInfo element Contains information about a CPNS enabled entity for transmitting a discovery request message.
- UserInfo element Contains information about a user of a CPNS enabled entity that sends a Discovery Request message.
- the information on the user may include a User ID sub element and a User Name sub element.
- PNEID element (or attribute): ID of the PNE if the CPNS-enabled entity that sends the Discovery Request message is a PNE.
- PN GW ID element (or attribute): ID of the GW if the CPNS enable entity that sends the Discovery Request message is a PN GW.
- PNE Name or PN GW Name element if the CPNS enable entity transmitting the Discovery Request message is a PNE, the name of the PNE or the name of the GW if the CPNS enable entity transmitting the Discovery Request message is a PN GW.
- Mode element information on an activated mode of a CPNS enable entity that transmits a Discovery Request message, and has a value indicating PNE or PN GW. If the activated mode of the CPNS enable entity is PNE, it has a value of 1. However, when the activated mode is PN GW, it has a value of two. In FIG. 10, since the CPNS enable entity of the third device is set to the gateway, two values are included.
- PN Info Req element A value of True or False
- a CPNS enable entity that transmits a Discovery Request message wants to obtain information about a PN stored by an entity that will receive the Discovery Request message. , Include the value True.
- UI Capabilities element If the PN GW should perform User Interaction on behalf of the PNE, it has a value of True. This is set by the PNE. For example, if the PNE does not have a user interface, it may be set to a value of True if the PN GW takes over the user interaction.
- Zone based service support element (or attribute): Set to "TRUE" if the PN GW can provide zone based services.
- the included element includes a PN ID subelement, a Description subelement, a Sharing subelement, and a PNE Info subelement.
- the PN ID lower element indicates an ID for the PN when there is a PN.
- the Sharing sub-element indicates whether to hide information of other PNEs belonging to the PN and to deliver only PN GW information according to the user setting.
- the value of the sharing subelement is set to 1
- information of PNEs may be included in the PNE Info subelement.
- the value of the Sharing subelement is set to 2
- information of PNEs may not be included in the PNE Info subelement.
- the PNE Info sub-element includes information on the PNE belonging to the PN, if there was a PN previously.
- the PNE info sub-element includes a PNE ID element and a PNE Name element.
- the discovery request message may be transmitted in a broadcast manner.
- the discovery request message described above may be as shown in Table 1 below.
- Table 1 Element Explanation User Info Include UserID and UserName.
- UserID ID of CPNS user UserName CPNS user's name EntityInfo
- entity information may include a PNEID, PNGWID, Name, Mode, PN Info Req, UI Capa, Zone based service support, and Broadcast group key delivery support elements.
- PNEID ID of the PNE PNGWID ID of PN GW Name Name of PNE or PN GW Mode The mode of the subject to be transmitted, which is 1 when the PNE transmits and has a value of 2 when the PN GW transmits. If it can operate simultaneously with PNE and GW, it has 3 values.
- PNInfoReq When the PNE sends a message, it requests the PN Info and sets it to Tree. UICapa Set to True if the device operating as a PNE does not have a user interface and the PN GW is to interact with the user. Zone based service support Set to True if the PN GW provides zone-based services.
- PN Info If the subject transmitting the discovery request message is a PN GW and has a PN, information about the PN is included to enable the PNE to join the PN. It may include the PN ID, Description, and PNE Info sub-elements.
- PNE Info Contains information about PNEs that are members of a PN.
- the lower element may include a PNEID and a PNE Name.
- the lower element may also include Device Info.
- the second device 120 checks the discovery request message. In addition, the second device 120 stores the elements in the Discovery Request message. In particular, the second device 120 generates and stores a PN inventory therein by using the PNE Info element.
- the second device 120 determines not to additionally transmit a discovery request message and generates a discovery response message.
- the discovery response message may include an element indicating whether to be hidden according to a user setting as described above, for example, a sharing element. That is, if the user chooses to share all PNEs in the gateway and PN, the Sharing element is set to a value indicating open or shared, and the user selects that only information about the gateway is shared. In this case, the sharing element may be set to a value indicating blocked or protected.
- the Discovery Response message may include the following elements.
- Entity Info element Information on a CPNS enabled entity that has received a discovery request, and includes a User ID subelement and a user Name subelement.
- PNE ID element When the CPNS enable entity that has received the discovery request is a PNE, it includes an ID of the PNE.
- PNE Name element When the CPNS enable entity that has received the discovery request is a PNE, includes a name of the PNE.
- Mode element Set to Both mode or Combined Mode.
- -UI Capa element If the PN GW performs User Interaction on behalf of PNE, it has True value. This is set by the PNE. For example, if the PNE does not have a user interface, it may be set to a value of True if the PN GW takes over the user interaction.
- the PN Info element This element is included when the value of the PN Info Req element is set to True in the received Discovery Request message.
- the PN Info element includes a PN ID subelement, a Description subelement, a Sharing subelement, a PNE Info subelement, and the like.
- the PN ID lower element indicates an ID for the PN when there is a PN.
- the Sharing sub-element indicates whether to hide information of other PNEs belonging to the PN and to deliver only PN GW information according to the user setting. When the value of the sharing subelement is set to 1, information of PNEs may be included in the PNE Info subelement.
- the PNE Info sub-element includes information on the PNE belonging to the PN, if there was a PN previously.
- the PNE info sub-element includes a PNE ID element and a PNE Name element.
- PNE Info element Contains information about the members of the PN.
- the discovery response message described above may be as shown in Table 2 below.
- UserID ID of the user UserName User's name EntityInfo
- entity information may include a PNEID, PNGWID, Name, Mode, PN Info Req, and UI Capa element.
- PNEID ID of the PNE PNGWID ID of PN GW Name Name of PNE or PN GW Mode A mode of a subject that transmits a Discovery Response message, which is 1 when a PNE is transmitted and has a value of 2 when a PN GW is transmitted. If it can operate simultaneously with PNE and GW, it has 3 values.
- PN Info If the subject transmitting the discovery response message is a PNE and already participates in another PN, the PN includes information about the PN. It may include the PN ID, Description, and PNE Info sub-elements.
- PNEInfo Contains information about PNEs that are members of a PN.
- the lower element may include a PNEID and a PNE Name.
- the lower element may also include Device Info.
- the first device 110 checks the discovery response message.
- the first device 110 stores the elements in the discovery response message.
- the first device 110 generates and stores a PN inventory therein by using the PNE Info element.
- the first device 110 and the second device 120 performs a PN setting procedure.
- the first device 110 operating in the gateway mode registers PN # 1 with the CPNS server 300.
- the CPNS server 300 stores the information on the PN # 1 in the PN inventory, and stores the PNE Info element.
- the PNE Info element includes a sharing sub-element.
- the first device 110 and the second device 120 performs a physical connection with the third device 210.
- a discovery request message for example, a discovery request message may be sent to the first entity. Transmission to the device 110 and the second device 120, respectively.
- the second device 120 When the second device 120 receives the discovery request message, for example, a Discovery Request message, the second device 120 confirms its user setting, for example, a Sharing element. If, in the user setting, for example, the sharing element, information of the PNE, for example, information of the second device 120 is set to be hidden, the second device 120 may respond to the discovery request message, for example.
- the discovery response message may not be transmitted. Alternatively, only the information on the first device, which is a gateway, may be included in the discovery response message and transmitted.
- the first device 110 when the first device 110 receives the discovery request message, for example, a Discovery Request message, the first device 110 confirms its user setting, for example, a Sharing element. If the user setting, for example, the sharing element, the information of the PNE, for example, the information of the second device 120 is set to be hidden, the first device 110 may optionally request confirmation from the user. That is, the first device 110 may receive an input regarding whether to share the information by releasing the hiding to the user. If it is determined that the information of the PNE, for example, the information of the second device 120 is hidden, the first device 110 is a gateway (GW), so that only the information about the PNE is included in the discovery response message and transmitted. Can be.
- GW gateway
- remote entity 500 wishes to provide a service to the user A's devices. However, since the remote entity 500 cannot know which devices the user A possesses, the remote entity 500 transmits an information request message for the user A's PN to the CPNS server 300.
- the CPNS server 300 checks the PN inventory and the PNE Info element stored as described above. Specifically, the CPNS server 300 checks a sharing element, and if the information of the PNE, for example, the information of the second device 120 is set to be hidden, only the information of the first device 110 that is the gateway is a PN. It can be included in the information response message and transmitted.
- the second embodiment allows a user to select or modify a device to be hidden in a mutual search procedure performed later.
- FIG 9 is an exemplary view showing a third embodiment for hiding a predetermined device.
- the third embodiment allows a user to select or modify a device to be hidden in a service search procedure performed later.
- user A owns a second device 120 acting as a PNE and a first device 110 acting as a gateway.
- the second device 120 is a portable multimedia device
- the first device 110 is a cellular phone.
- the user A selects a device which the user wants to hide in a service search procedure performed later.
- the first device 110 and the second device 120 When the first device 110 and the second device 120 are located near each other, the first device 110 and the second device 120 perform a physical connection procedure.
- the PN setting procedure is performed.
- the PN setting procedure may be started first by the second device 120 which is the PNE or by the first device 110 first.
- the second device 120 transmits a PN setup request message, for example, a PN Setup Request message, to the CPNS server 300 through the first device 110.
- a PN Setup Request message may include a sharing element. That is, if the user chooses to share all PNEs in the gateway and PN, the Sharing element is set to a value indicating open or shared, and the user selects that only information about the gateway is shared. In this case, the sharing element may be set to a value indicating blocked or protected.
- the first device 110 transmits a PN setup request message to the second device 120.
- the PN configuration request message may include information about the gateway, information about entities (eg, CPNS enable entity in the first device) that will belong to the PN to be generated.
- the PN setting request message may include the aforementioned Sharing element.
- the PN Setup Request message may be as shown in Table 3 below.
- Explanation Origin Entity ID ID of the CPNS-enabled entity for which you want to set a PN PN Setup Type Indicates how the PN should be set 1: Includes PN GW and PNE one-to-one 2: Allows PNE to configure PN with all devices connected to PN GW 3: Set PN only with specific PNEs that are invited. Invited PNE ID Contains the IDs of the PNEs to be invited during the PN setup process.
- PN Info Information of the PN to be registered and stored in the CPNS server may include a PNID, Description, Disclosure, Ownership Entity, PN GW Info, and PNE Info elements.
- PN inventory Information on the PN GW includes a PNGWID and a PN GW Name element.
- PNGWID ID of PN GW PN GW Name Name of PN GW PNE Info As information on the PNE, it may include a PNEID, PNE Name, Mode, Description, Device Capa, and Service Profile elements.
- PNE ID ID of the PNE PNE Name Name of the PNE Mode Information about the mode of the PNE Description Description of PN Device capa Information about the function of the device including the PNE.
- Service profile Information about the CPNS-enabled application or information that supports a particular service or state Auth IniData Information used to start the PNE authentication procedure may include AuthPNEID, rand_PNE, and LocalEUKeyAssignment.
- the Origin Entity ID element is checked to see who is trying to generate a PN. Then, the PN ID and Msg ID elements are extracted from the message.
- the CPNS enable entity of the second device 120 generates a PN configuration response message as a response message to the PN configuration request message.
- the CPNS enable entity of the second device 120 includes a response to the PN configuration request message in a Return element in the PN configuration response message.
- the response is 1 if successful and 2 if unsuccessful.
- the PN Setup Request message may include a sharing element.
- the generated PN setting response message may be as shown in Table 4 below.
- PN SETUP Request1 OK2: Failed, CPNS enable entity cannot process the request3: Not allowed PNInfo
- the information on the PN may include PNID, Description, PNGWInfo, and PNEInfo.
- PN GW Info As the information on the PN GW, it may include a PNGWID and a PN GW Name.
- the information on the PNE may include PNEID, PNEName, Mode, Description, DeviceCapa, and ServiceProfile.
- AuthPNEID ID of target PNE to be authenticated by CPNS server rand_PNE Random value generated by PNE LocalEUKeyAssignment Flag indicating need for LocalEUKey assignment TRUE: required, FALSE: not required Auth FinData Information used in a PNE to authenticate a CPNS server, including HASH.
- HASH Hash value calculated by the target PNE or PN GW
- the CPNS enable entity of the second device 120 transmits the generated message to the first device 110.
- the first device 110 When the PN setup response message is received from the second device 120, the first device 110 generates a PN setup request message based on the received PN setup response message, and transmits it to the CPNS server 300. do.
- an CPNS server 300 When the CPNS server 300 receives the PN Setup Request message from the first device 110, an CPNS server 300 generates an authentication request message, for example, an Authenticate Request message, and the second device 120 through the first device 110. To pass).
- an authentication request message for example, an Authenticate Request message
- the second device 120 transmits an authentication response message to the CPNS server 300 through the first device 110.
- the CPNS server 300 registers the PN information included in the PN Setup Request message, and stores the PN information in the PN inventory.
- the CPNS server 300 generates a PN Setup Response message and transmits it to the first device 110.
- the first device 110 When the first device 110 receives the PN Setup Response message from the CPNS server, the first device 110 stores PN information in a local PN inventory. The first device 110 generates a PN establishment notification message, for example, a PN establishment notify message, and transmits the generated PN establishment notification message to the second device 120.
- a PN establishment notification message for example, a PN establishment notify message
- the remote entity transmits a Service Discovery Request message to the CPNS server 300 to know the service provided in the generated PN # 1.
- the Service Discovery Request message may be as Table 5 below.
- Table 5 Element Explanation OriginEntityID Identifier of the subject sending the service discovery request message SG Info Service Group Information.
- Service ID Service identifier Keyword Service keyword, service group keyword, or member identifier Member req If set to "True", it means requesting information about the members of the service group.
- the CPNS server When the CPNS server receives the Service Discovery Request message, it checks the elements in the message.
- the CPNS server If there is a search rule information, for example a keyword element in the message, and no information on the operator policy, the CPNS server performs a search based on the request. However, if there is search rule information, for example, a keyword element in the message, and there is operator policy information, the CPNS server 300 performs a search based on the search rule and the operator policy information. However, if there is no search rule information, for example, a keyword element in the message, and only information about a provider policy, the CPNS server 300 searches for a service based on the provider policy. However, if there is no search rule information, such as a keyword element in the message, and no information about the operator policy, then the CPNS server 300 searches for all available services.
- search rule information for example, a keyword element in the message, and no information on the operator policy
- the CPNS server 300 checks a sharing element based on the stored information, for example, PN information in a local PN inventory. If the sharing element is set to hide information of the PNE, for example, information of the second device 120, and includes information on the second device 120 among the search results.
- the CPNS server 300 transmits a service discovery confirmation request message to the second device 120 through the first device 110.
- the second device 120 includes a result element including a value indicating permission or rejection in the service discovery confirmation response message and transmits the result element to the CPNS server 300 based on user input or configuration information.
- the CPNS server 300 includes a value indicating permission in the result element in the received service search acknowledgment message
- the CPNS server 300 includes a service discovery response message, for example, an SG info element including information of the second device 120. Included in the Service Discovery Responses message, and sent to the remote entity (500).
- the result element in the received service discovery confirmation response message includes a value indicating rejection
- an SG info element including information other than the information of the second device 120 is included in the discovery response message. To the remote entity 500.
- the service discovery response message for example, the service discovery response message may be as shown in Table 6 below.
- the third embodiment allows a user to select or modify a device to be hidden in a service search procedure performed later.
- the user A is configured to hide the first device 110 and the second device 120 from the pairing procedure, the mutual discovery procedure, and the service discovery procedure. It is assumed that the second device 120 is carried with the geographical location and moved to coverage of the PN # 2.
- PN # 1 and PN # 2 of user A overlap. That is, the first device 110 and the second device 120 of the user A are included in the coverage of the PN # 2.
- the second device 120 is located within the coverage of the PN # 2, the second device 120 is hidden from the pairing procedure, the mutual discovery procedure, and the service discovery procedure according to the first to third embodiments. Since it is set to, only the first device 110 may perform a pairing procedure, a mutual discovery procedure, and a service discovery procedure within the PN # 2. However, since the CPNS enable entity of the second device 120 operates as a gateway GW, in order to receive a service in the PN # 2, a mode of the CPNS enable entity of the second device 120 is changed. It is necessary to be able to change from gateway mode to another mode. This will be described below.
- FIG. 10 illustrates a signal flow diagram of changing a mode of a CPNS enable entity
- FIG. 11 illustrates a process of changing a mode of a CPNS enable entity.
- the first embodiment illustrates a process of changing a mode of a CPNS enable entity of the first device 120 from a gateway to another mode.
- user A owns a first device 110 acting as a gateway and a second device 120 acting as a PNE.
- the first device 110 is a cellular phone and the second device 120 is a portable multimedia device.
- the second device 120 is set to be hidden in the pairing procedure, the mutual discovery procedure, and the service discovery procedure according to the first to third embodiments described above.
- a physical connection procedure (eg, a physical pairing procedure) is performed.
- the CPNS enable entity in the first device 110 reads its mode setting value, activates the gateway entity according to the mode setting value, and deactivates the PNE.
- the CPNS enable entity in the second device 120 reads its mode setting value, activates the PNE according to the mode setting value, and deactivates the gateway entity.
- a mutual search procedure is performed between the first device 110 and the second device 120.
- the CPNS enable entity of the first device 110 performs a PN setting procedure to generate PN # 1.
- the second device 120 may be located within the coverage of the PN # 2 but may not perform a pairing procedure due to the hidden setting.
- the first device 110 performs a physical connection with the third device 210.
- the CPNS enable entity in the third device 210 transmits a discovery request message, for example, a discovery request message immediately after the physical connection is completed, if its mode is set to a gateway. do.
- a discovery request message for example, a discovery request message immediately after the physical connection is completed, if its mode is set to a gateway.
- the CPNS enable entity in the third device 210 transmits the first device 110 simultaneously without first transmitting, information may overlap.
- the third device 210 acting as a gateway immediately transmits a discovery request message immediately after the physical connection is completed.
- the discovery request message may include the following elements.
- EntityInfo element Contains information about a CPNS enabled entity for transmitting a discovery request message.
- UserInfo element Contains information about a user of a CPNS enabled entity that sends a Discovery Request message.
- the information on the user may include a User ID sub element and a User Name sub element.
- PNEID element (or attribute): ID of the PNE if the CPNS-enabled entity that sends the Discovery Request message is a PNE.
- PN GW ID element (or attribute): ID of the GW if the CPNS enable entity that sends the Discovery Request message is a PN GW.
- PNE Name or PN GW Name element if the CPNS enable entity transmitting the Discovery Request message is a PNE, the name of the PNE or the name of the GW if the CPNS enable entity transmitting the Discovery Request message is a PN GW.
- Mode element information on an activated mode of a CPNS enable entity that transmits a Discovery Request message, and has a value indicating PNE or PN GW. If the activated mode of the CPNS enable entity is PNE, it has a value of 1. However, when the activated mode is PN GW, it has a value of two. In FIG. 10, since the CPNS enable entity of the third device is set to the gateway, two values are included.
- PN Info Req element A value of True or False
- a CPNS enable entity that transmits a Discovery Request message wants to obtain information about a PN stored by an entity that will receive the Discovery Request message. , Include the value True.
- UI Capabilities element If the PN GW should perform User Interaction on behalf of the PNE, it has a value of True. This is set by the PNE. For example, if the PNE does not have a user interface, it may be set to a value of True if the PN GW takes over the user interaction.
- Zone based service support element (or attribute): Set to "TRUE" if the PN GW can provide zone based services.
- the included element includes a PN ID subelement, a PNE Info subelement, and the like.
- the PN ID sub-element indicates an ID for the PN when there is a PN previously, and the PNE Info sub-element includes information about a PNE belonging to the PN when there is a PN.
- the PNE info sub-element includes a PNE ID element and a PNE Name element.
- the gateway After generating the discovery request message as described above, the gateway transmits the message to the detected devices through the physical connection.
- the discovery request message may be transmitted in a broadcast manner.
- the CPNS enable entity of the first device 110 checks an element, such as Zone based service support, for a service in a received discovery request message, for example, a Discovery Request message. , To check the provided service (S111). If the service provided is what user A wishes, perform the following procedure.
- an element such as Zone based service support
- the CPNS enable entity in the first device 110 checks the mode of the counterpart that transmitted the message through the Mode element based on the received message, and identifies the counterpart's ID by using the Entity Info element. Check through.
- the CPNS enable entity of the first device 110 checks the states of PNEs belonging to the PN # 1 (S112). As a result of checking the states of the PNEs, if there is no PNE available to use the service provided by the PN # 2, it checks its own mode (S113). In this case, the absence of a PNE that can use the service provided by the PN # 2 may mean that all PNEs are located within the coverage of the PN # 1, but all of the PNEs are hidden. Alternatively, the absence of a PNE that can use the service provided by the PN # 2 means that all PNEs are located within the coverage of the PN # 1, but any PNE of all the PNEs also includes the coverage of the PN # 2.
- PNEs of all the PNEs are located in both the coverage of the PN # 1 and the coverage of the PN # 2, but communication is not performed in the PN # 2 due to a low battery, a power off, or a difference in a communication scheme. It may mean that there is no PNE available.
- the PNE is activated (S114).
- both the gateway mode and the PNE mode are activated. Both modes are activated simultaneously at this time. Alternatively, the two modes being activated at the same time is called a combined mode.
- the mode information is set to both mode or combined mode in a discovery response message, for example, an entity discovery response message, for the discovery request message.
- Entity Info element Information on a CPNS enabled entity that has received a discovery request, and includes a User ID subelement and a user Name subelement.
- PNE ID element When the CPNS enable entity that has received the discovery request is a PNE, it includes an ID of the PNE.
- PNE Name element When the CPNS enable entity that has received the discovery request is a PNE, includes a name of the PNE.
- Mode element Set to Both mode or Combined Mode.
- -UI Capa element If the PN GW performs User Interaction on behalf of PNE, it has True value. This is set by the PNE. For example, if the PNE does not have a user interface, it may be set to a value of True if the PN GW takes over the user interaction.
- PN Info element This element is included when the value of the PN Info Req element is set to True in the received Discovery Request message.
- the first device 110 operating as a PNE sends information about the PN # 1 that is already configured with the second device 120. Include it.
- the PN Info element may include a PN ID element, a Description element, and the like below.
- PNE Info element Contains information about the members of the PN.
- the discovery response message described above may be as described in Table 2 above.
- the third device 210 confirming that the CPNS-enabled entity of the first device 110 is operated in both mode or combined mode operating in a PNE as well as a gateway. 1
- the PN # 2 setup procedure is started. Specifically, it is as follows.
- the CPNS enable entity of the third device 210 transmits a PN setup request message, for example, a PN Setup Request message, to the first device 110.
- the PN configuration request message may include information about the gateway, information about entities (eg, CPNS enable entity in the first device) that will belong to the PN to be generated.
- the PNE When the PNE receives the PN Setup Request message at the CPNS enable entity of the first device 110, the PNE checks the Origin Entity ID element to know who is trying to generate the PN. Then, the PN ID and Msg ID elements are extracted from the message.
- the CPNS enable entity operating as a PNE in the first device 110 generates a PN configuration response message as follows.
- the CPNS enable entity operating as the PNE includes a response to the PN configuration request message in a Return element in the PN configuration response message.
- the response is 1 if successful and 2 if unsuccessful.
- a PN Info element for PN information included in the CPNS enable entity of the first device 110 is included in the PN configuration response message.
- the PNE information included in the PN included in the CPNS enable entity of the first device 110 is included in the PNE Info element in the PN configuration response message.
- various elements are included in the PN configuration response message.
- the CPNS enable entity of the first device transmits the generated message to the third device 210.
- the CPNS enable entity of the third device 210 receives the PN setup response message, eg, a PN Setup Response message, to confirm whether the first device wants to join the PN, the received message in the received message.
- the PN setup response message eg, a PN Setup Response message
- the Return element When the value of the Return element is set to 1, information about a PN inventory for a corresponding PN is generated, and a routing table is generated and maintained based on the information from the received message.
- the CPNS enable entity of the third device 210 generates a PN setup request message, for example, a PN Setup Request message for transmission to the CPNS server.
- the CPNS enable entity of the third device 210 includes the ID of the PN GW in the OriginEntityID element. Then, the information on the PN to be generated is included in the PN Info element of the PN Setup Request message.
- the PN Info element includes a PN ID element including the ID of the PN generated by the PN GW, a Description element including the description of the generated PN.
- the CPNS enable entity of the third device 210 includes a PN GW Info element in the PN Setup Request message.
- the PN GW Info element includes a PN GW ID element representing the ID of the PN GW and a PN GW Name element representing the name of the PN GW.
- the CPNS enable entity of the third device 210 includes a PNE Info element and an Auth Ini Data element in the PN Setup Request message.
- the CPNS enable entity of the third device 210 transmits the generated PN Setup Request message to the CPNS server 300.
- the CPNS server 300 When the CPNS server 300 receives the PN Setup Request message from the third device 210, generates an authentication request message, for example, an Authenticate Request message, and the first device via the third device 210. Forward to 110.
- an authentication request message for example, an Authenticate Request message
- the first device 110 transmits an authentication response message to the CPNS server 300 through the third device (210).
- the CPNS server 300 registers the PN information included in the PN Setup Request message, and stores the PN information in the PN inventory.
- the CPNS server 300 generates a PN Setup Response message and transmits it to the third device 210.
- the third device 210 When the third device 210 receives the PN Setup Response message from the CPNS server, the third device 210 stores PN information in a local PN inventory. The third device 210 generates a PN establishment notification message, for example, a PN establishment notify message, and transmits the generated PN establishment notification message to the first device 110.
- a PN establishment notification message for example, a PN establishment notify message
- the application server 400 may obtain information about the PN # 2 from the CPNS server 300, and if there is service data, the obtained information
- the first device 110 or the second device 120 may be determined as a destination of the service data through.
- the application server 400 transmits the service data to a third device 210 that operates as the gateway, and the third device serves as a PNE. Transfer to the first device 110 to operate.
- the CPNS enable entity operating as a PNE in the first device 110 receives the service data
- the CPNS enable entity transmits the service data to an internal gateway
- the gateway transmits the service data to the second device 120. Can be delivered to.
- the CPNS enable entity in the first device 110 When the CPNS enable entity in the first device 110 operates in both modes, as can be seen with reference to FIG. 12, a gateway and a PNE in the CPNS enable entity of the first device 110 are present. Are driven simultaneously, and a communication channel is established between the gateway and the PNE. Accordingly, the CPNS enable entity in the first device 110 receives service data from the third device 210 acting as a gateway in the PN # 2 as a PNE, and the CPNS enable in the first device 110. The enable entity is capable of delivering the service data to a second device 120 operating as a PNE in the PN # 1 as a gateway.
- the physical layer, MAC layer, 3rd layer, and CPNS enable entity, and application are included in the first, second, and third devices 110, 120, and 130.
- the CPNS enable entity of the second device 120 drives only the PNE
- the CPNS enable entity of the third device 210 drives only the gateway entity.
- both the PNE and the gateway entity are driven.
- a communication link is created between the PNE and the gateway entity within the CPNS enable entity of the first device 110.
- the service data is transmitted to the first device 110 through the CPNS enable entity, the 3rd layer, the MAC layer, and the physical layer of the third device 210.
- the service data is received by a PNE of a CPNS enable entity through a physical layer, a MAC layer, and a 3rd layer, and the PNE transmits the service data to the generated communication.
- the gateway entity in the CPNS enable entity of the first device 110 transmits the service data to the second device 120 through the 3rd layer, the MAC layer, and the physical layer.
- the CPNS enable entity in the first device 110 communicates with the third device 210 that operates as the gateway as a PNE, and simultaneously operates with the second device 120 that operates as the PNE as a gateway.
- the sink needs to be adjusted.
- the CPNS enable entity in the first device 110 must communicate with two devices, that is, the third device 210 and the second device 120 at the same time. Communication with may interfere with communication of other devices. For example, a signal transmitted from the third device 210 to the first device 110 may act as interference to the second device 120. Similarly, a signal transmitted from the second device 120 to the first device 110 may act as interference to the third device 210.
- the sink of the communication link between the first device 110 and the second device 120 is a sink of the communication link between the third device 210 and the first device 110. It needs to be readjusted accordingly.
- FIG. 13 shows an example of adjusting a sync after a mode of a CPNS enable entity is changed.
- FIG. 13 (a) shows the cycle of transmission (Tx) and reception (Rx) in PN # 1 composed of the first device 110 and the second device 120, and the lower part of FIG. 13 (a). Shows a cycle of transmission (Tx) and reception (Rx) in PN # 2 composed of the first device 110 and the third device 130. 13 (a), the idle time T2 in PN # 2 may be longer than the idle time T1 in PN # 1.
- a signal transmitted from the third device 210 to the first device 110 in the PN # 2 may act as an interference to the second device 120 in the PN # 1.
- the first device 110 may measure the starting point T0 in the link with the third device 210.
- one or more of a period of transmission (Tx), a period of reception (Rx), and an idle time between transmission (Tx) and reception (Rx) of the third device 210 may be measured.
- the first device 110 may transmit a control signal for adjusting the sync with the second device 120 to the second device based on one or more of the measurement results.
- the control signal may include one or more of the measurement results.
- the second device 120 may readjust the sync with the first device 110 based on the control signal.
- the idle times T1 and T2 may have the same length.
- each of the transmission periods Tx and the reception periods Rx may coincide with each other.
- an operation of receiving data from the third device 210 by the first device 110 is shown in the upper portion, and the first device 110 is displayed in the second portion in the lower portion.
- the operation of receiving data from device 120 is shown.
- the first device 110 in order to receive power of the beacon signal from the third device 210, the first device 110 is shown as a wakeup time 1.
- the time for applying power to the internal receiver in order for the first device 110 to receive the beacon signal from the second device 120 is represented by wakeup time2.
- the first device 110 must apply power to the receiver during wakeup time 1 and wakeup time 2 in order to receive the beacon messages.
- the power can be used more efficiently.
- the first device 110 compares the Wakeup time 1 with an offset between the time point at which the beacon signal is received from the third device 210 and the time point at which the beacon signal is received from the second device 210. If the offset is greater than the wakeup time1, the offset can be reduced. In order to reduce the offset, the first device 110 may transmit a control signal to the second device 120.
- the first device 110 in order to receive the beacon signal from the third device 210, the first device 110 is referred to as wakeup time 1, and the power is applied to the internal receiver.
- wakeup time 1 a1 time before receiving the beacon message during wakeup time1 and a2 time after receiving the beacon message.
- the time for applying power to the internal receiver is called wakeup time 2, and until the device 110 receives the beacon message during the wakeup time 2.
- b1 time, after receiving the beacon message is b2 time.
- K be the time offset between the wakeup time 1 and the wakeup time 2.
- the first device 110 compares the a2 + b1 time with the k time value, and if a2 + b1 ⁇ k, the first device 110 decreases k. In order to reduce the k, the first device 110 may transmit a control signal to the second device 120.
- Embodiments described above may be combined. Accordingly, the embodiments may not be implemented alone, but may be implemented in combination as necessary. Such a combination can be easily implemented by those skilled in the art after reading the present specification, and the combination will not be described in detail below. However, even if not described, it is not to be excluded from the present invention, it should be construed as being included in the scope of the present invention.
- Embodiments and modifications described above may be implemented through various means.
- embodiments of the present invention may be implemented by hardware, firmware, software, or a combination thereof.
- the method according to embodiments of the present invention may include one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs). Field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, and the like.
- ASICs application specific integrated circuits
- DSPs digital signal processors
- DSPDs digital signal processing devices
- PLDs programmable logic devices
- FPGAs Field programmable gate arrays
- processors controllers, microcontrollers, microprocessors, and the like.
- the method according to the embodiments of the present invention may be implemented in the form of a module, procedure, or function that performs the functions or operations described above.
- the software code may be stored in a memory unit and driven by a processor.
- the memory unit may be located inside or outside the processor, and may exchange data with the processor by various known means.
- the method according to the present invention may be stored in a storage medium (eg, internal memory, flash memory, hard disk, etc.) and may be executed by a processor (eg a microprocessor). It can be implemented as codes or instructions within a program. This will be described with reference to FIG. 15.
- a storage medium eg, internal memory, flash memory, hard disk, etc.
- a processor eg a microprocessor
- 15 is a configuration block diagram of a device according to embodiments of the present invention.
- the first device 110 includes a storage means 111, a controller 112, and a transceiver 113.
- the storage means 111 stores the method shown in FIGS. 2 to 14.
- the controller 112 controls the storage means 111 and the transceiver 113. Specifically, the controller 112 executes the methods stored in the storage means 111, respectively. The controller 112 transmits the above-mentioned signals through the transceiver 113.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
엘리먼트 | 설명 | |||
User Info | UserID와 UserName를 포함한다. | |||
UserID | CPNS 사용자의ID | |||
UserName | CPNS 사용자의 이름 | |||
EntityInfo | Entity information의 약자로서, PNEID, PNGWID, Name, Mode, PN Info Req, UI Capa, Zone based service support, Broadcast group key delivery support 엘리먼트를 포함할 수 있다. | |||
PNEID | PNE의 ID | |||
PNGWID | PN GW의 ID | |||
Name | PNE 또는 PN GW의 이름 | |||
Mode | 전송하는 주체의 모드로서, PNE가 전송하는 경우, 1이고, PN GW가 전송하는 경우 2 값을 갖는다. PNE와 GW로 동시에 동작할 수 있는 경우, 3값을 갖는다. | |||
PNInfoReq | PNE가 메시지를 전송하는 경우에, PN Info를 요청하면 Tree로 설정된다. | |||
UICapa | PNE로 동작하는 디바이스가 사용자 인터페이스를 갖지 않은 경우, PN GW가 사용자와의 상호 작용을 하도록 할 경우 True로 설정된다. | |||
Zone based service support | PN GW가 존 기반 서비스를 제공하는 경우 True로 설정된다. | |||
PN Info | Discovery Request 메시지를 전송하는 주체가 PN GW이고, PN을 가지고 있는 경우, PNE가 PN에 가입할 수 있도록 하기 위해 PN에 대한 정보를 포함한다. PN ID, Description, PNE Info 하위 엘리먼트를 포함할 수 있다. | |||
PNID | PN의 ID | |||
Description | PN에 대한 설명 | |||
Sharing | PN 인벤토리의 공유 여부 1: Shared(공유)됨을 나타낸다. 즉, PN GW의 정보와 PNE 정보가 모두 공유됨 2: Protected(숨김)됨을 나타낸다. 즉, PN GW의 정보만이 공유되고, PNE 정보는 공유되지 않는다. | |||
PNE Info | PN의 멤버인 PNE들에 대한 정보를 포함한다. 하위 엘리먼트로서, PNEID, PNE Name을 포함할 수 있다.또한, 하위 엘리먼트로서 Device Info를 포함할 수 있다. | |||
PNEID | PNE의 ID | |||
PNEName | PNE의 이름 | |||
Device Info | 디바이스에 대한 정보이다. Mode 엘리먼트와, InactiveMode를 포함할 수 있다. | |||
Mode | 현재 활성화된 Mode에 대한 정보를 포함할 수 있다. | |||
Inactive Mode | 비활성화된 Mode에 대한 정보를 포함한다. |
엘리먼트 | 설명 | ||
User Info | UserID와 UserName를 포함한다. | ||
UserID | 사용자의 ID | ||
UserName | 사용자의 이름 | ||
EntityInfo | Entity information의 약자로서, PNEID, PNGWID, Name, Mode, PN Info Req, UI Capa엘리먼트를 포함할 수 있다. | ||
PNEID | PNE의 ID | ||
PNGWID | PN GW의 ID | ||
Name | PNE 또는 PN GW의 이름 | ||
Mode | Discovery Response 메시지를 전송하는 주체의 모드로서, PNE가 전송하는 경우, 1이고, PN GW가 전송하는 경우 2 값을 갖는다. PNE와 GW로 동시에 동작할 수 있는 경우, 3값을 갖는다. | ||
UICapa | PNE로 동작하는 디바이스가 사용자 인터페이스를 갖지 않은 경우, PN GW가 사용자와의 상호 작용을 하도록 할 경우 True로 설정된다. | ||
PN Info | Discovery Response 메시지를 전송하는 주체가 PNE 이고, 이미 다른 PN에 참가하고 있는 경우,상기 PN에 대한 정보를 포함한다. PN ID, Description, PNE Info 하위 엘리먼트를 포함할 수 있다. | ||
PNID | PN의 ID | ||
Description | PN에 대한 설명 | ||
Sharing | PN 인벤토리의 공유 여부 1: Shared(공유)됨을 나타낸다. 즉, PN GW의 정보와 PNE 정보가 모두 공유됨 2: Protected(숨김)됨을 나타낸다. 즉, PN GW의 정보만이 공유되고, PNE 정보는 공유되지 않는다. | ||
PNEInfo | PN의 멤버인 PNE들에 대한 정보를 포함한다. 하위 엘리먼트로서, PNEID, PNE Name을 포함할 수 있다.또한, 하위 엘리먼트로서 Device Info를 포함할 수 있다. | ||
PNEID | PNE의 ID | ||
PNEName | PNE의 이름 | ||
DeviceInfo | 디바이스에 대한 정보이다. Mode 엘리먼트와, InactiveMode를 포함할 수 있다. | ||
Mode | 현재 활성화된 Mode에 대한 정보를 포함할 수 있다. | ||
InactiveMode | 비활성화된 Mode에 대한 정보를 포함한다. |
엘리먼트 | 설명 | ||
Origin Entity ID | PN을 설정하려는 CPNS 인에이블 엔티티의 ID | ||
PN Setup Type | PN이 어떻게 설정되어야 하는지를 나타낸다.1: PN GW와 PNE가 일대일로 포함된다.2: PNE가 PN GW와 연결된 모든 디바이스들과 PN을 설정할 수 있도록 한다. 3: 초대되는 특정 PNE들하고만 PN을 설정한다. | ||
Invited PNE ID | PN 설정과정동안 초대될 PNE들의 ID를 포함한다. | ||
PN Info | CPNS 서버에 등록되고 저장될 PN의 정보로서, PNID, Description, Disclosure, Ownership Entity, PN GW Info, PNE Info 엘리먼트를 포함할 수 있다. | ||
PN ID | PN의 ID를 나타낸다. | ||
Description | PN에 대한 설명 (예 Home, Office) | ||
Sharing | PN 인벤토리의 공유 여부 1: Shared(공유)됨을 나타낸다. 즉, PN GW의 정보와 PNE 정보가 모두 공유됨 2: Protected(숨김)됨을 나타낸다. 즉, PN GW의 정보만이 공유되고, PNE 정보는 공유되지 않는다. | ||
PN GW Info | PN GW에 대한 정보로서, PNGWID와, PN GW Name엘리먼트를 포함한다. | ||
PNGWID | PN GW의 ID | ||
PN GW Name | PN GW의 이름 | ||
PNE Info | PNE에 대한 정보로서, PNEID, PNE Name, Mode, Description, Device Capa, Service Profile 엘리먼트를 포함할 수 있다. | ||
PNE ID | PNE의 ID | ||
PNE Name | PNE의 이름 | ||
Mode | PNE의 모드에 대한 정보 | ||
Description | PN에 대한 설명 | ||
Device Capa | PNE를 포함하는 디바이스의 기능에 대한 정보이다. | ||
Service Profile | CPNS 인에이블 애플리케이션에 대한 정보 또는 특정 서비스 또는 상태를 지원하는 컨텐츠에 대한 정보 | ||
Auth IniData | PNE 인증 절차를 시작하기 위해서 사용되는 정보로서, AuthPNEID, rand_PNE, LocalEUKeyAssignment를 포함할 수 있다. | ||
AuthPNEID | CPNS 서버에 의해서 인증되어야 할 타겟 PNE의ID | ||
rand_PNE | PNE에 의해서 생성된 랜덤 값 | ||
LocalEUKeyAssignment | LocalEUKey 할당의 필요성을 나타내는 플래그TRUE: 필요함, FALSE: 불필요함 |
엘리먼트 | 설명 | ||
Return | PN SETUP Request에 대한 성공 여부1: OK2: 실패, CPNS 인에이블 엔티티가 상기 요청을 처리할 수 없음3: 허락되지 않음 | ||
PNInfo | PN에 대한 정보로서, PNID, Description, PNGWInfo, PNEInfo를 포함할 수 있다. | ||
PN ID | PN의 아이디 | ||
Description | PN에 대한 설명 | ||
Sharing | PN 인벤토리의 공유 여부 1: Shared(공유)됨을 나타낸다. 즉, PN GW의 정보와 PNE 정보가 모두 공유됨 2: Protected(숨김)됨을 나타낸다. 즉, PN GW의 정보만이 공유되고, PNE 정보는 공유되지 않는다. | ||
PN GW Info | PN GW에 대한 정보로서, PNGWID, PN GW Name를 포함할 수 있다. | ||
PNGWID | PN GW의 ID | ||
PNGW Name | PN GW의 이름 | ||
PNE Info | PNE에 대한 정보로서, PNEID, PNEName, Mode, Description, DeviceCapa, ServiceProfile를 포함할 수 있다. | ||
PNEID | PNE의 ID | ||
PNEName | PNE의 이름 | ||
Mode | 디바이스의 모드에 대한 정보 | ||
Description | PN에 대한 설명 | ||
Device Capa | PNE가 포함된 디바이스의 기능에 대한 정보 | ||
Service Profile | CPNS 인에이블 애플리케이션에 대한 정보 또는 특정 서비스 또는 상태를 지원하는 컨텐츠에 대한 정보 | ||
AuthIniData | PNE 인증 절차를 시작하기 위해서 사용되는 정보로서, AuthPNEID, rand_PNE, LocalEUKeyAssignment를 포함할 수 있다 | ||
AuthPNEID | CPNS 서버에 의해서 인증되어야 할 타겟 PNE의ID | ||
rand_PNE | PNE에 의해서 생성된 랜덤 값 | ||
LocalEUKeyAssignment | LocalEUKey 할당의 필요성을 나타내는 플래그TRUE: 필요함, FALSE: 불필요함 | ||
Auth FinData | CPNS 서버를 인증하기 위해 PNE에서 사용되는 정보로서, HASH를 포함한다. | ||
HASH | 타겟 PNE 또는 PN GW에 의해서 계산된 해쉬 값 |
엘리먼트 | 설명 | |
OriginEntityID | 서비스 탐색 요청 메시지를 전송하는 주체의 식별자 | |
SG Info | 서비스 그룹 정보Service Group Information. | |
Service ID | 서비스 식별자 | |
Keyword | 서비스 키워드, 서비스 그룹 키워드 또는 멤버 식별자 | |
Member Req | “True”로 설정될 경우, 서비스 그룹의 멤버에 대한 정보를 요청한다는 의미이다. |
이름 | Description | |
SG Info | 서비스 그룹 정보 | |
SGID | 서비스 그룹 식별자 | |
SG Description | 서비스 그룹에 대한 설명 | |
SGOwner | 서비스 그룹의 엔티티 식별 정보 | |
ServiceInfo | 서비스 그룹에 대한 서비스 정보 | |
ServiceID | 서비스 식별자 | |
ServiceName | 서비스 키워드 또는 태그 | |
Member Info | 서비스 그룹 멤버의 정보 | |
PNE ID | PNE 이름 | |
Name | PNE 이름 |
PN#1의 커버리지 및 PN#2의 커버리지의 중첩 영역에 존재 | PN#1의 커버리지 내이지만, PN#2의 커버리지의 밖 | 결정의 결과 |
이용가능한 PNE가 존재 | PNE가 존재 | 모드 변경 필요 함 |
이용가능한 PNE가 존재 | PNE이 없음 | 변경 필요 없음 |
이용가능한 PNE가 없음 | PNE가 있음 | 모드 변경 필요 함 |
이용가능한 PNE가 없음 | PNE가 없음 | 변경 필요 없음 |
Claims (15)
- CPNS(Converged Personal Network Service) 인에이블 엔티티(enabled entity)를 구비하는 통신 기기에 의해 수행되는 다른 장치와 통신하는 방법으로서,게이트웨이 모드로 설정된 상기 통신 기기의 CPNS 인이에블 엔티티가 제1 장치로부터 상기 제1 장치의 모드가 PNE(Personal Network Entity)로 설정됨을 나타내는 제1 정보와 상기 제1 장치가 추가적인 탐색 절차에서 숨겨져야 하는지를 나타내는 제2 정보를 포함하는 탐색 응답 메시지를 수신하는 단계와,여기서 상기 CPNS 인에이블 엔티티는 제1 네트워크를 관리하고, 상기 제1 네트워크 내에는 상기 게이트웨이로 설정된 CPNS 인에이블 엔티티를 통해 제1 서비스를 수신할 수 있는 하나 이상의 PNE(Personal Network Entity)가 존재하고;상기 통신 기기가 제2 장치에 의해 관리되는 제2 네트워크의 커버리지 내로 이동한 경우, 상기 제2 장치의 모드를 나타내는 제3 정보를 포함하는 탐색 요청 메시지를 상기 제2 장치로부터 수신하는 단계와;상기 하나 이상의 PNE 중 이용 가능한 PNE의 존재 여부 및 상기 제2 장치의 모드, 및 상기 제2 정보 중 하나 이상에 기초하여, 상기 통신 기기의 CPNS 인에이블 엔티티의 모드를 변경해야 할지 결정하는 단계를 포함하고,여기서 상기 제2 네트워크의 커버리지 밖에 존재하는 PNE는 없으나, 상기 제1 장치가 상기 추가적인 탐색 절차에서 숨겨지는 것으로 설정되어 있는 경우, 상기 CPNS 인에이블 엔티티의 모드는 상기 게이트웨이 모드에서 결합 모드로 변경되는 것으로 결정되는 것을 특징으로 하는 통신 방법.
- 제1항에 있어서, 상기 결합 모드는상기 게이트웨이 모드와 PNE 모드로 동시에 구동하는 모드인 것을 특징으로 하는 통신 방법.
- 제1항에 있어서, 상기 이용가능한 PNE는상기 제2 네트워크의 커버리지 내에 위치하면서, 상기 제2 네트워크의 통신 방식을 지원하고, 상기 제2 네트워크의 서비스를 수신하는데 충분한 전력을 가지고 있는 PNE인 것을 특징으로 하는 통신 방법.
- 제1항에 있어서, 상기 결정 단계는상기 CPNS 인에이블 엔티티가 자신의 모드 정보를 확인하는 단계를 더 포함하는 것을 특징으로 하는 통신 방법.
- 제4항에 있어서,상기 자신의 모드 정보를 확인한 결과 상기 게이트웨이 모드와 PNE 모드로 동시에 구동가능한 경우, 상기 결합 모드로 변경되는 것을 특징으로 하는 통신 방법.
- 제1항에 있어서,상기 제2 네트워크의 커버리지 내에 모든 PNE가 존재하는 경우, 상기 CPNS 인에이블 엔티티의 모드는 상기 게이트웨이 모드에서 PNE 모드로 변경되되도록 것으로 결정되거나, 모드 변경이 수행되지 않도록 결정되는 것을 특징으로 하는 통신 방법.
- 제1항에 있어서,상기 탐색 요청 메시지의 수신에 응답하여, 탐색 응답 메시지를 상기 제2 장치로 전송하는 단계를 더 포함하는 것을 특징으로 하는 통신 방법.
- 제7항에 있어서, 상기 탐색 응답 메시지 에는상기 제1 장치가 상기 결합 모드로 동작됨을 나타내는 모드 정보를 포함하는 것을 특징으로 하는 통신 방법.
- 제7항에 있어서,상기 제2 정보에 의해 상기 제1 장치가 추가적인 탐색 절차에서 숨겨져야 하는 것으로 확인되는 경우,상기 탐색 응답 메시지에는 상기 제1 장치를 제외한 다른 PNE들에 대한 정보가 포함되는 것을 특징으로 하는 통신 방법.
- 제1항에 있어서,상기 결합 모드로 변경 후, 상기 CPNS 인에이블 엔티티가 PNE로서 상기 제2 장치로부터 상기 제2 네트워크의 서비스 데이터를 수신하는 단계와;상기 서비스 데이터를 상기 CPNS 인에이블 엔티티가 게이트웨이로서 상기 엔티티에게 전달하는 단계를 더 포함하는 것을 특징으로 하는 통신 방법.
- 게이트웨이 모드로 설정된 CPNS(Converged Personal Network Service) 인에이블 엔티티(enabled entity)를 저장하는 저장부와, 여기서 상기 CPNS 인에이블 엔티티는 제1 네트워크를 관리하고, 상기 제1 네트워크 내에는 상기 게이트웨이로 설정된 CPNS 인에이블 엔티티를 통해 제1 서비스를 수신할 수 있는 하나 이상의 PNE(Personal Network Entity)가 존재하고;상기 통신 기기가 상기 제1 네트워크 내에 위치할 때에는 제1 장치로부터 상기 제1 장치의 모드가 PNE(Personal Network Entity)로 설정됨을 나타내는 제1 정보와 상기 제1 장치가 추가적인 탐색 절차에서 숨겨져야 하는지를 나타내는 제2 정보를 포함하는 탐색 응답 메시지를 수신하고, 상기 통신 기기가 제2 장치에 의해 관리되는 제2 네트워크의 커버리지 내로 이동한 후에는 상기 제2 장치의 모드를 나타내는 제3 정보를 포함하는 탐색 요청 메시지를 상기 제2 장치로부터 수신하는 수신부와; 그리고상기 하나 이상의 PNE 중 이용 가능한 PNE의 존재 여부 및 상기 제2 장치의 모드, 및 상기 제2 정보 중 하나 이상에 기초하여, 상기 통신 기기의 CPNS 인에이블 엔티티의 모드를 변경해야 할지 결정하는 제어부를 포함하고,여기서 상기 제2 네트워크의 커버리지 밖에 존재하는 PNE는 없으나, 상기 제1 장치가 상기 추가적인 탐색 절차에서 숨겨지는 것으로 설정되어 있는 경우, 상기 CPNS 인에이블 엔티티의 모드는 상기 게이트웨이 모드에서 결합 모드로 변경되는 것으로 결정되는 것을 특징으로 하는 통신 기기.
- 제11항에 있어서, 상기 결합 모드는상기 게이트웨이 모드와 PNE 모드로 동시에 구동하는 모드인 것을 특징으로 하는 통신 기기.
- 제11항에 있어서, 상기 결합 모드는상기 게이트웨이 모드와 PNE 모드로 동시에 구동하는 모드인 것을 특징으로 하는 통신기기.
- 제11항에 있어서, 상기 송수신부는상기 탐색 요청 메시지의 수신에 응답하여, 탐색 응답 메시지를 상기 제2 장치로 전송하는 것을 특징으로 하는 통신 기기.
- 제14항에 있어서,상기 제2 정보에 의해 상기 제1 장치가 추가적인 탐색 절차에서 숨겨져야 하는 것으로 확인되는 경우,상기 탐색 응답 메시지에는 상기 제1 장치를 제외한 다른 PNE들에 대한 정보가 포함되는 것을 특징으로 하는 통신 기기.
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP11792645.1A EP2579679A4 (en) | 2010-06-06 | 2011-06-03 | METHOD AND COMMUNICATION DEVICE FOR COMMUNICATING WITH OTHER DEVICES |
CN201180033233.6A CN102972091B (zh) | 2010-06-06 | 2011-06-03 | 与其它设备通信的方法和通信设备 |
KR1020127031698A KR101404383B1 (ko) | 2010-06-06 | 2011-06-03 | 다른 장치와 통신 하는 방법 및 통신 기기 |
US13/702,391 US20130086246A1 (en) | 2010-06-06 | 2011-06-03 | Method and Communication Device for Communicating with Other Devices |
Applications Claiming Priority (18)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US35191810P | 2010-06-06 | 2010-06-06 | |
US61/351,918 | 2010-06-06 | ||
US35280010P | 2010-06-08 | 2010-06-08 | |
US61/352,800 | 2010-06-08 | ||
US35363410P | 2010-06-10 | 2010-06-10 | |
US61/353,634 | 2010-06-10 | ||
US35425610P | 2010-06-14 | 2010-06-14 | |
US61/354,256 | 2010-06-14 | ||
US37708110P | 2010-08-25 | 2010-08-25 | |
US61/377,081 | 2010-08-25 | ||
US37799010P | 2010-08-30 | 2010-08-30 | |
US61/377,990 | 2010-08-30 | ||
US38695410P | 2010-09-27 | 2010-09-27 | |
US61/386,954 | 2010-09-27 | ||
US41672510P | 2010-11-23 | 2010-11-23 | |
US61/416,725 | 2010-11-23 | ||
US41987710P | 2010-12-06 | 2010-12-06 | |
US61/419,877 | 2010-12-06 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2011155734A2 true WO2011155734A2 (ko) | 2011-12-15 |
WO2011155734A3 WO2011155734A3 (ko) | 2012-04-19 |
Family
ID=45098507
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2011/004100 WO2011155734A2 (ko) | 2010-06-06 | 2011-06-03 | 다른 장치와 통신 하는 방법 및 통신 기기 |
Country Status (5)
Country | Link |
---|---|
US (1) | US20130086246A1 (ko) |
EP (1) | EP2579679A4 (ko) |
KR (1) | KR101404383B1 (ko) |
CN (1) | CN102972091B (ko) |
WO (1) | WO2011155734A2 (ko) |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR101680715B1 (ko) * | 2010-06-15 | 2016-11-30 | 삼성전자주식회사 | 개인 네트워크 등록을 위한 장치 및 방법 |
KR101683292B1 (ko) * | 2010-06-18 | 2016-12-07 | 삼성전자주식회사 | Pn 라우팅 테이블을 이용한 개인 네트워크의 구성 장치 및 방법 |
US9131360B2 (en) * | 2010-12-10 | 2015-09-08 | Htc Corporation | Apparatus and method of open mobile alliance |
US9836177B2 (en) | 2011-12-30 | 2017-12-05 | Next IT Innovation Labs, LLC | Providing variable responses in a virtual-assistant environment |
US9672822B2 (en) | 2013-02-22 | 2017-06-06 | Next It Corporation | Interaction with a portion of a content item through a virtual assistant |
US20140245140A1 (en) * | 2013-02-22 | 2014-08-28 | Next It Corporation | Virtual Assistant Transfer between Smart Devices |
US9706585B2 (en) * | 2013-03-11 | 2017-07-11 | Lg Electronics Inc. | Method and apparatus for performing device to device service in wireless communication system |
CN104349401B (zh) * | 2013-09-03 | 2018-10-16 | 广州三星通信技术研究有限公司 | 用于在终端中调整数据策略的设备和方法 |
US9485708B2 (en) * | 2013-09-10 | 2016-11-01 | Qualcomm Incorporated | Systems and methods for concurrent service discovery and minimum spanning tree formation for service delivery |
CN104065659B (zh) * | 2014-06-27 | 2019-08-16 | 努比亚技术有限公司 | 一种dlna设备隐身的方法及主、从dlna设备 |
CN105916015A (zh) * | 2015-12-15 | 2016-08-31 | 乐视致新电子科技(天津)有限公司 | 一种车载多设备共享音视频数据的方法、装置及系统 |
Family Cites Families (47)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6347339B1 (en) * | 1998-12-01 | 2002-02-12 | Cisco Technology, Inc. | Detecting an active network node using a login attempt |
US6707811B2 (en) * | 1999-03-19 | 2004-03-16 | Estara, Inc. | Internet telephony for ecommerce |
WO2000057621A1 (en) * | 1999-03-19 | 2000-09-28 | Estara, Inc. | Public web phone system |
US8798251B2 (en) * | 2001-02-27 | 2014-08-05 | Verizon Data Services Llc | Methods and systems for computer enhanced conference calling |
US20020136226A1 (en) * | 2001-03-26 | 2002-09-26 | Bluesocket, Inc. | Methods and systems for enabling seamless roaming of mobile devices among wireless networks |
US6981263B1 (en) * | 2001-06-29 | 2005-12-27 | Bellsouth Intellectual Property Corp. | Methods and systems for converged service creation and execution environment applications |
US7042988B2 (en) * | 2001-09-28 | 2006-05-09 | Bluesocket, Inc. | Method and system for managing data traffic in wireless networks |
EP1563671A1 (en) * | 2002-11-08 | 2005-08-17 | Koninklijke Philips Electronics N.V. | Method and apparatus allowing remote access in data networks |
US7366159B1 (en) * | 2002-11-14 | 2008-04-29 | At&T Corp. | Mix protocol multi-media provider system incorporating a session initiation protocol based media server adapted to form preliminary communication with calling communication devices |
US7852837B1 (en) * | 2003-12-24 | 2010-12-14 | At&T Intellectual Property Ii, L.P. | Wi-Fi/BPL dual mode repeaters for power line networks |
US7395085B1 (en) * | 2005-03-11 | 2008-07-01 | Sprint Spectrum L.P. | Method and system for notifying a multi-mode mobile station of an incoming call |
KR20080109078A (ko) * | 2006-04-10 | 2008-12-16 | 야후! 인크. | 미디어 자산의 화제 고유 생성 및 편집 |
WO2007140834A1 (en) * | 2006-06-02 | 2007-12-13 | Telefonaktiebolaget L M Ericsson (Publ) | Ims service proxy in higa |
US20080117850A1 (en) * | 2006-10-30 | 2008-05-22 | Agrawal Dharma P | Dual Mode Wireless Personal Area Network and Wireless Local Area Network Architecture |
US7983407B2 (en) * | 2007-03-28 | 2011-07-19 | Verizon Patent And Licensing Inc. | Calling party number override for emergency services |
US8013734B2 (en) * | 2007-05-14 | 2011-09-06 | Autocart Llc | Personal safety mobile notification system |
US7924747B2 (en) * | 2007-11-29 | 2011-04-12 | Bae Systems Information And Electronic Systems Integration Inc. | Enhancement of node connectivity in a wireless communications network with changing topology via adaptive role changing |
US20090147702A1 (en) * | 2007-12-10 | 2009-06-11 | Buddhikot Milind M | Method and Apparatus for Forming and Configuring a Dynamic Network of Mobile Network Nodes |
US8462728B2 (en) * | 2007-12-24 | 2013-06-11 | Apple Inc. | Method and wireless system for achieving local anchoring of a mobile node |
US8503460B2 (en) * | 2008-03-24 | 2013-08-06 | Qualcomm Incorporated | Dynamic home network assignment |
US8335508B2 (en) * | 2008-08-07 | 2012-12-18 | General Motors Llc | System and method for monitoring and reporting telematics unit communication network system acquisition and scanning performance |
KR20100020925A (ko) * | 2008-08-13 | 2010-02-23 | 한국전자통신연구원 | 개인 무선 통신 네트워크(wpan)에서의 피코넷 간 멀티 홉 메쉬 통신 장치 및 그 방법 |
EP2166790A1 (en) * | 2008-09-19 | 2010-03-24 | NEC Corporation | Method for personal network service configuration |
KR101242440B1 (ko) * | 2008-10-23 | 2013-03-12 | 에스케이플래닛 주식회사 | Cpns 환경에서 팀플레이 게임 시 데이터를 효과적으로 전송하기 위한 시스템 및 방법과 이를 위한 cpns 서버,이동통신 단말기 및 종단 단말기 |
KR101268838B1 (ko) * | 2008-11-06 | 2013-05-29 | 에스케이플래닛 주식회사 | Cpns 환경에서 원거리의 종단 단말기를 제어하기 위한 시스템 및 방법과 이를 위한 cpns 서버, 이동통신 단말기 |
US8693316B2 (en) * | 2009-02-10 | 2014-04-08 | Qualcomm Incorporated | Access point resource negotiation and allocation over a wireless interface |
CN101489300A (zh) * | 2009-02-11 | 2009-07-22 | 深圳华为通信技术有限公司 | 一种个人网中业务通知的方法及设备 |
KR101291654B1 (ko) * | 2009-02-24 | 2013-08-01 | 에스케이플래닛 주식회사 | Cpns 환경에서 종단 단말기가 다수의 이동통신 단말기에 연결되어 서비스를 제공받기 위한 방법 및 시스템과 이를 위한 cpns 서버 및 종단 단말기 |
WO2010131860A2 (en) * | 2009-05-14 | 2010-11-18 | Lg Electronics Inc. | Method and system for optimizing cpns enabler |
US8527659B2 (en) * | 2009-05-17 | 2013-09-03 | Lg Electronics Inc. | Method and system for optimizing CPNS enabler |
CN102461076B (zh) * | 2009-06-04 | 2014-06-18 | 瑞典爱立信有限公司 | 用于针对本地网络中的设备获得媒体对象的方法和装置 |
US8335854B2 (en) * | 2009-07-21 | 2012-12-18 | Empire Technology Development Llc | Performing services on behalf of low-power devices |
US20110022620A1 (en) * | 2009-07-27 | 2011-01-27 | Gemstar Development Corporation | Methods and systems for associating and providing media content of different types which share atrributes |
US8640204B2 (en) * | 2009-08-28 | 2014-01-28 | Broadcom Corporation | Wireless device for group access and management |
KR101679428B1 (ko) * | 2009-10-16 | 2016-11-25 | 삼성전자주식회사 | Cpns 서비스 제공을 위한 개인망 형성 장치 및 방법 |
KR101674903B1 (ko) * | 2009-10-20 | 2016-11-11 | 삼성전자주식회사 | 개인 네트워크를 이용한 서비스 제공 방법 및 장치 |
US10455275B2 (en) * | 2010-02-16 | 2019-10-22 | Comcast Cable Communications, Llc | Disposition of video alerts and integration of a mobile device into a local service domain |
US20110231547A1 (en) * | 2010-03-18 | 2011-09-22 | Yang Ju-Ting | Search methods applied to a personal network gateway in converged personal network service systems and related converged personal network service systems and mobile devices |
US20110246605A1 (en) * | 2010-03-31 | 2011-10-06 | Yang Ju-Ting | Method for Handling Information Delivery in Personal Network and Related Communication Device |
US8583811B2 (en) * | 2010-04-23 | 2013-11-12 | Qualcomm Incorporated | Gateway device for multimedia content |
WO2011152687A2 (ko) * | 2010-06-04 | 2011-12-08 | 엘지전자 주식회사 | 장치가 다른 장치를 검출하는 방법 |
US9001762B2 (en) * | 2010-06-06 | 2015-04-07 | Lg Electronics Inc. | Communication method between a device and another device |
US8744860B2 (en) * | 2010-08-02 | 2014-06-03 | At&T Intellectual Property I, L.P. | Apparatus and method for providing messages in a social network |
US8762487B2 (en) * | 2010-10-29 | 2014-06-24 | Htc Corporation | Method of performing a service group discovery procedure in a communication system and related communication device |
US9131360B2 (en) * | 2010-12-10 | 2015-09-08 | Htc Corporation | Apparatus and method of open mobile alliance |
US8510398B2 (en) * | 2010-12-10 | 2013-08-13 | At&T Intellectual Property I, Lp | Apparatus and method for managing message communication |
US20140157300A1 (en) * | 2012-11-30 | 2014-06-05 | Lenovo (Singapore) Pte. Ltd. | Multiple device media playback |
-
2011
- 2011-06-03 WO PCT/KR2011/004100 patent/WO2011155734A2/ko active Application Filing
- 2011-06-03 CN CN201180033233.6A patent/CN102972091B/zh not_active Expired - Fee Related
- 2011-06-03 EP EP11792645.1A patent/EP2579679A4/en not_active Withdrawn
- 2011-06-03 KR KR1020127031698A patent/KR101404383B1/ko not_active IP Right Cessation
- 2011-06-03 US US13/702,391 patent/US20130086246A1/en not_active Abandoned
Non-Patent Citations (2)
Title |
---|
None |
See also references of EP2579679A4 |
Also Published As
Publication number | Publication date |
---|---|
KR101404383B1 (ko) | 2014-06-09 |
CN102972091B (zh) | 2016-05-18 |
WO2011155734A3 (ko) | 2012-04-19 |
KR20130040902A (ko) | 2013-04-24 |
EP2579679A4 (en) | 2016-03-30 |
US20130086246A1 (en) | 2013-04-04 |
CN102972091A (zh) | 2013-03-13 |
EP2579679A2 (en) | 2013-04-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2011155734A2 (ko) | 다른 장치와 통신 하는 방법 및 통신 기기 | |
WO2011155762A2 (ko) | 다른 장치와 통신 하는 방법 및 통신 기기 | |
WO2020204474A1 (ko) | 무선 통신 시스템에서 에지 컴퓨팅 서비스를 제공하기 위한 장치 및 방법 | |
WO2011155733A2 (ko) | 장치가 다른 장치와 통신 하는 방법 | |
WO2016024695A1 (en) | Method and apparatus for profile download of group devices | |
WO2020231120A1 (ko) | 에지 컴퓨팅 서비스에서 단말의 식별자 관리 방법 및 장치 | |
WO2020197221A1 (ko) | 통신 방법 및 통신 디바이스 | |
WO2011152687A2 (ko) | 장치가 다른 장치를 검출하는 방법 | |
WO2018222024A1 (ko) | 블루투스 le 기술을 이용하여 디바이스를 연결하기 위한 방법 및 장치 | |
WO2020204505A1 (ko) | 엣지 컴퓨팅 서비스를 위한 방법 및 그의 전자 장치 | |
WO2017030232A1 (ko) | 데이터 송수신 방법 및 이를 위한 디바이스 | |
WO2013073869A1 (en) | Method and apparatus for managing security keys for communication authentication with mobile station in wireless communication system | |
WO2021167277A1 (ko) | 에지 컴퓨팅 시스템에서 무선 통신 네트워크 타입에 따른 서비스 제공 장치 및 방법 | |
WO2010120026A1 (en) | Method for performing uncontrolled handover | |
WO2015133865A1 (en) | Method and system for establishing a service session between seeker device and advertiser device | |
WO2013058423A1 (ko) | 전자기기 및 전자기기의 동작 방법 | |
WO2013048008A1 (en) | Methods and apparatus for registering a device to server | |
WO2021194163A1 (ko) | Upf 서비스 기반 packet delay status event exposure service 방법 및 장치 | |
WO2015137637A1 (en) | Method for supporting proximity-based service configuring for ue | |
WO2014189323A1 (en) | Apparatus and method for performing wireless docking operation in communication system supporting universal plug and play protocol | |
WO2015037909A1 (ko) | 통신 시스템에서 푸쉬 서비스 제공을 위한 방법 및 장치 | |
WO2016013846A1 (ko) | 무선 통신 시스템에서 요청 메시지를 처리하기 위한 방법 및 이를 위한 장치 | |
WO2018048230A1 (en) | Method for managing short data service (sds) in mission critical data (mc data) communication system | |
WO2016036056A1 (ko) | 무선 통신 시스템에서 단말이 서비스 연결을 유지하는 장치 및 방법 | |
WO2022265123A1 (ko) | 초광대역 통신을 수행하기 위한 방법 및 장치 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201180033233.6 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11792645 Country of ref document: EP Kind code of ref document: A2 |
|
ENP | Entry into the national phase |
Ref document number: 20127031698 Country of ref document: KR Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13702391 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011792645 Country of ref document: EP |