Group communication method, communication device and management device
Granted 1 Nov 2011 · 6 office actions
Assignee: Fujitsu Limited
Law firm: Law firm · Log in to unlock
Attorney: Attorney · Log in to unlock
Inventors: Yuji Matsumoto · Examiner: Kwasi Karikari · AU 2617 · TC 2600
Life of the application
18 dated eventsAbstract
A group communication method capable of performing group communication without additional functions provided on a network and with preventing excessive network traffic. Each communication device first transmits an enrollment message. A providing device groups the communication devices, creates a group key specifying the communication devices that are identified as a same subgroup, and transmits the group key to the communication devices. The communication devices receive and store the group key. To transmit distribution data to a subgroup, the providing device transmits the data together with data corresponding to the group key to a selected communication device of the subgroup. When the communication devices recognize the distribution data, the communication devices determine whether to receive the distribution data, based on the distribution data and the stored group key.
Description
9 parts›CROSS-REFERENCE TO RELATED APPLICATIONS
This application is based upon and claims the benefits of priority from the prior Japanese Patent Application No. 2005-286369, filed on Sep. 30, 2005, the entire contents of which are incorporated herein by reference.
›BACKGROUND OF THE INVENTION
(1) Field of the Invention
This invention relates to a group communication method, a communication device and a management device, and more particularly, to a group communication method, a communication device and a management device for group communication.
(2) Description of the Related Art
IP multicast communication has been widely known as a technique to simultaneously transmit the same data to a plurality of receiving ends.
For the IP multicast communication, a method where a server selects a multicast group comprising member terminals and transmits data to the group has been proposed (for example, Japanese Patent Application Laid-open No. 2003-134161).
As another technique to simultaneously transmit the same data to a plurality of receiving ends, Push-to-Talk communication has been known, which realizes group communication by half duplex communication.
In the IP multicast communication, a multicast distribution tree is constructed and then multicast data is transmitted. As to the multicast distribution tree, multicast routers are used as routers and connected by unicast between them.
In the Push-to-Talk communication, data is transmitted to the member terminals of a group by unicast.
The above IP multicast service, however, has a drawback in that a network is not easily built because special routers and a unique protocol should be provided on the network.
The Push-to-Talk communication, on the other hand, can realize the service, irrespective of network. However, the unicast communication may cause excessive network traffic when the number of member terminals increases in the group.
›SUMMARY OF THE INVENTION
This invention has been made in view of foregoing and intends to provide a group communication method, a communication device and a management device capable of realizing group communication without special functions provided on a network and with preventing excess network traffic.
To accomplish the above objects, there provided is a group communication method for performing broadcast communication in a group comprising communication devices by using a management device that manages the group. According to this group communication method, each communication device first transmits an enrollment message to join the group. Then the management device groups the communication devices transmitting the enrollment message, creates a group key specifying the communication devices that are identified as a same subgroup, transmits the group key to the communication devices of the same subgroup. Then the communication devices receive and store the group key. To transmit distribution data to a subgroup, the management device selects at least one communication device of the subgroup and transmits the distribution data together with data corresponding to the group key to the selected communication device(s) of the subgroup. When the communication devices recognize the distribution data, the devices determine based on the distribution data and the group key being stored whether to receive the distribution data.
The above and other objects, features and advantages of the present invention will become apparent from the following description when taken in conjunction with the accompanying drawings which illustrate preferred embodiments of the present invention by way of example.
›BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a principle view of a group communication system according to this invention.
FIG. 2 shows a group communication system according to the first embodiment.
FIG. 3 is a block diagram of a providing device.
FIG. 4 is a block diagram of a communication device.
FIGS. 5 and 6 are a flowchart showing operation of the providing device.
FIG. 7 is a flowchart of a packet reception process of the communication device.
FIG. 8 shows an example of operation of the group communication system.
FIG. 9 shows a multicast logical group key for the group communication system of FIG. 8 .
FIG. 10 shows a group communication system according to the second embodiment.
›DESCRIPTION OF THE PREFERRED EMBODIMENTS · 1 of 5
Preferred embodiments of this invention will be described with reference to the accompanying drawings.
The present invention that is implemented to the embodiments will be first summarized and then the specific embodiments will be described.
FIG. 1 is a principle view of a group communication system of this invention.
A group communication system 100 has communication devices 1 and 2 , a providing device 3 , an access point (AP) 4 , and an access network 5 .
The communication devices 1 and 2 communicate with the providing device 3 via the AP 4 and the access network 5 .
To join a group, the communication devices 1 and 2 first transmit enrollment messages Msg 1 and Msg 2 to the providing device 3 .
The providing device 3 has a management table Tbl 1 for managing communication devices 1 and 2 , the management table Tbl 1 containing information included in enrollment messages. Referring to this figure, the management table Tbl 1 contains group information and subgroup (logical group) information regarding the communication devices 1 and 2 . When the communication devices 1 and 2 join the same group and their IP addresses indicate the same AP (AP 4 in FIG. 1 ), the providing device 3 identifies them as belonging to the same subgroup (logical group), and creates (defines) a group key so that the communication devices 1 and 2 can receive the same data. Then, the providing device 3 transmits (makes a notice of) a multicast logical group keys K 1 and K 2 each including the group key to the communication devices 1 and 2 , respectively. This multicast logical group key will be described later.
The communication devices 1 and 2 have management tables Tbl 2 and Tbl 3 to store the received multicast logical group keys K 1 and K 2 .
Under this condition, assume that the providing device 3 selects the communication device 1 of the subgroup (comprising the communication devices 1 and 2 ) as a destination and transmits distribution data D 1 to the communication device 1 . The communication device 1 recognizes the distribution data D 1 , and receives the data after confirming the destination. The communication device 2 also recognizes the distribution data D 1 , and determines based on the group key whether to receive the distribution data D 1 . When it is recognized that the distribution data D 1 is logically-created multicast distribution data, the communication device 2 receives this data. At this time, the communication device 2 performs address conversion (rewriting) based on the multicast logical group key K 2 being stored in the management table Tbl 3 .
The group communication system 100 works as follows.
First the communication devices 1 and 2 transmit enrollment messages Msg 1 and Msg 2 to the providing device 3 (steps S 1 and S 2 ).
When it is detected that the communication devices 1 and 2 join the same group and their IP addresses indicate the same AP 4 , the providing device 3 identifies the communication devices 1 and 2 as belonging to the same subgroup (logical group) (step S 3 ), and creates (defines) a group key for the communication devices 1 and 2 (step S 4 ). The providing device 3 transmits (makes a notice of) multicast logical group keys K 1 and K 2 each including the group key to the communication devices 1 and 2 , respectively (steps S 5 and S 6 ).
The communication devices 1 and 2 receive and store the multicast logical group keys K 1 and K 2 into the management tables Tbl 2 and Tbl 3 (step S 7 , S 8 ).
Then, the providing device 3 selects the communication device 1 as a destination and transmits distribution data D 1 (step S 9 ). The communication device 1 recognizes the distribution data D 1 , and receives this data D 1 after confirming the destination. At this time, the communication device 2 also recognizes the distribution data D 1 and determines based on the group key whether the distribution data D 1 is logically-created multicast distribution data. When this determination results in Yes, the communication device 2 receives this distribution data D 1 (step S 10 ). At this time, the communication device 2 performs the address conversion based on the multicast logical group key K 2 being stored in the management table Tbl 3 .
Specific embodiments of this invention will be hereinafter described in detail.
FIG. 2 shows a group communication system according to the first embodiment.
Referring to this figure, a group communication system 200 has a group including subgroups A and B, the subgroup A comprising a providing device 10 , communication devices 20 and 20 a , an AP 40 , and an access network 60 , the subgroup B comprising the providing device 10 , communication devices 30 and 30 a , an AP 40 a , and an access network 60 a.
The providing device 10 manages both the subgroups A and B. In a case of broadcast communication in the group, the providing device 10 transmits data together with information equivalent to a multicast address, to a main device, for example, the communication device 20 , 30 of each subgroup. At this time, the communication device 20 a , 30 a also recognizes this data, and receives the data when detecting that this data is broadcast data.
By the way, in the group communication system 200 , the communication devices 20 , 20 a , 30 , 30 a are grouped into the subgroups A and B by an initial operation. This initial operation will be described later.
Next explanation is about how to realize such the group communication system 200 . The following explanation uses the subgroup A as an example. The subgroup B has the same configuration as the subgroup A.
FIG. 3 is a block diagram of the providing device.
The providing device 10 has a management unit 11 , a receiver 12 , a conversion unit 13 , a transmitter 14 , and a physical interface section 15 for data input/output.
The management unit 11 processes data which are input/output via the physical interface section 15 . Further, the management unit 11 has a management table 111 for storing (registering) information on the communication devices 20 and 20 a transmitting enrollment messages. Furthermore, the management unit 11 manages the stored information on the communication devices 20 and 20 a . When detecting that the communication devices 20 and 20 a can be grouped, the management unit 11 creates a logical key (group key) and then a multicast logical group key including the logical key, and gives it to the transmitter 14 .
›DESCRIPTION OF THE PREFERRED EMBODIMENTS · 2 of 5
The receiver 12 receives enrollment messages and packets from communication devices via the physical interface section 15 .
When the receiver 12 receives from the communication device 20 a data delivery request to another communication device of the subgroup A, or the communication device 20 a , the conversion unit 13 converts the data based on the logical key and the information on the communication device 20 a being stored in the management table 111 , and gives the converted data to the transmitter 14 (the same process is performed on a data delivery request to the communication device 20 , from the communication device 20 a ).
The transmitter 14 transmits the received data via the physical interface section 15 .
FIG. 4 is a block diagram of a communication device.
The communication device 20 will be described as an example. It should be noted that the communication device 20 a has the same configuration. This figure shows the reference numbers of the both devices.
The communication device 20 has a management unit 21 , a transmitter 22 , a receiver 23 , a deletion unit 24 , a physical interface section 25 , and an application section 26 .
The management unit 21 has a management table 211 for storing a multicast logical group key and an enrollment processor 212 for transmitting an enrollment message to the providing device 10 . To transmit an enrollment message, the enrollment processor 212 instructs the transmitter 22 , which then transmits the enrollment message to the providing device 10 via the physical interface section 25 in response to the instruction.
The receiver 23 has functions to receive and process data via the physical interface section 25 . Specifically, the receiver 23 has a detector 231 , a determination unit 232 and a conversion unit 233 . The detector 231 detects data coming via the physical interface section 25 . The determination unit 232 determines based on information being stored in the management table 211 whether to receive data detected by the detector 231 . The conversion unit 233 converts the data to be received according to a mode specified in the management table 211 and gives the converted data to the management unit 21 .
The deletion unit 24 deletes data that the determination unit 232 identifies as unnecessary to receive.
The operation of the group communication system 200 will be now described. FIGS. 5 and 6 show the operation of the providing device.
<Initial Operation>
In this initial operation, the communication devices are grouped into the subgroups. As an example, a case where the communication device 20 is grouped into the subgroup A will be described. FIGS. 5 and 6 are a flowchart showing the operation of the providing device.
At first, the communication device 20 transmits an enrollment message to the providing device 10 to join a group.
The providing device 10 determines whether a received message is an enrollment message (step S 11 ). When this determination in step S 11 results in Yes, the providing device 10 starts this operation. Specifically, the providing device 10 receives and registers this message in the management table 111 (step S 12 ). Then the providing device 10 determines whether some communication devices exist in the group and some IP addresses have the same prefix as the IP address of the communication device 20 (step S 13 ). When this determination in step S 13 results in No, the providing device 10 ends this operation. When the determination in step S 13 results in Yes, on the contrary, the management unit 11 creates a logical key (step S 14 ), transmits this key to the communication device 20 (step S 15 ), and ends this initial operation. The communication device 20 stores this logical key in the management table 111 .
When the determination in step S 11 results in No, the providing device 10 determines whether the message came from another communication device (hereinafter, referred to as joining communication device) belonging to the group (step S 16 ). When this determination in step S 16 results in No, the providing device 10 then determines whether the received data is addressed to the communication device 20 or 20 a (step S 17 ). When this determination in step S 17 results in Yes, the providing device 10 transmits the data (step S 18 ) and ends this operation. When the determination in step S 17 results in No, the providing device 10 ends this operation without receiving the message.
When the determination in step S 16 results in Yes, the providing device 10 determines whether the message is addressed to the subgroup A (step S 20 ). When this determination in step S 20 results in No, the providing device 10 transmits the message to the designated destination (step S 21 ) and ends this operation. When the determination in step S 20 results in Yes, the providing device 10 searches for a communication device with a unique prefix (step S 22 ). When a communication device with a unique prefix exists (Yes of step S 22 ), the providing device 10 transmits the message to the found communication device (step S 23 ). Then it is determined whether transmission to all communication devices each having a unique prefix is done (step S 24 ). When this determination in step S 24 results in No, the providing device 10 goes back to step S 23 to continue the transmission. When the determination in step S 24 results in Yes, the process goes on to step S 25 .
When a communication device having a unique prefix is not detected in step S 22 (No of step S 22 ), the providing device 10 determines whether some IP addresses have the same prefix (step S 25 ). When this determination in step S 25 results in No, the providing device 10 ends this operation. When the determination in step S 25 results in Yes, the providing device 10 determines whether a multicast logical group key has been distributed (step S 26 ). When this determination in step S 26 results in No, the providing device 10 distributes the key to the intended devices (step S 27 ) and ends this operation. When the determination in step S 26 results in Yes, the providing device 10 operates for group communication.
›DESCRIPTION OF THE PREFERRED EMBODIMENTS · 3 of 5
<Group Communication Operation>
In the group communication operation, the providing device 10 determines a main prefix address (step S 28 ). Then the providing device 10 creates a packet (distribution data) that is addressed to the main prefix address (step S 29 ), and transmits the created packet to the main prefix address (step S 30 ). Then, it is determined whether there is a different prefix to which the packet is not transmitted (step S 31 ). When this determination in step S 31 results in Yes, the process goes back to step S 28 . When the determination in step S 31 results in No, the providing device 10 ends this operation.
The operation of the communication device to receive a packet will be now described with reference to the flowchart of FIG. 7 .
When the communication device 20 , 20 a detects (recognizes) a packet, it determines whether the packet is addressed to the own device (step S 41 ). When this determination in step S 41 results in Yes, the communication device 20 , 20 a receives the packet (step S 42 ). Then, it is determined whether the received packet is a notification of a multicast logical group key (step S 43 ). When this determination in step S 43 results in Yes, it is determined whether the own device has applied for a group (step S 44 ). When this determination in step S 44 results in Yes, the communication device 20 , 20 a registers the multicast logical group key in the own management table (step S 45 ). Then this packet reception process ends. When the determination in step S 44 results in No, the communication device 20 , 20 a ends this process without any action. When the determination in step S 43 results in No, the communication device 20 , 20 a receives the packet (step S 46 ) and ends this packet reception process.
When the determination in step S 41 results in No, the communication device 20 , 20 a determines whether to receive the packet (step S 47 ). When this determination in step S 47 results in No, the communication device deletes the detected packet (step S 48 ), and ends this packet reception process. When the determination in step S 47 results in Yes, the communication device proceeds to receive the packet (step S 49 ). Then the mode of the packet is confirmed (step S 50 ). The mode is a raw data mode (a of step S 50 ), the process goes on to step S 53 . When the mode is a unicast mode (β of step S 50 ), the destination address of the packet is overwritten to the own address (step S 51 ). When the mode is a multicast mode (γ of step S 50 ), the destination address of the packet is overwritten to a multicast address (step S 52 ).
Then the communication device 20 , 20 a determines whether the received packet includes an encryption code (step S 53 ). When this determination in step S 53 results in Yes, the communication device decrypts the encrypted part of the data with the encryption code (step S 54 ), and ends this message reception process. When the determination in step S 53 results in No, the communication device ends this message reception process.
A specific operation of the group communication system will be described with reference to FIG. 8 .
This figure shows a case where the communication devices 20 and 20 a join a group G 1 of the providing device 10 and perform group communication in this group G 1 .
Assume now that the IP address and the MAC address of the communication device 20 are IP_adr 1 and MAC 1 :11 22 33 44 55 66, respectively. The IP address and the MAC address of the communication device 20 a are IP_adr 2 and MAC 2 :aa bb cc dd ee ff, respectively. The MAC address of the providing device 10 is MAC 3 .
The communication device 20 transmits a packet P 1 to the providing device 10 for enrollment of the group G 1 (step S 61 ).
Similarly, the communication device 20 a transmits a packet P 2 to the providing device 10 for enrollment of the group G 1 (step S 62 ).
As shown in FIG. 8 , each packet P 1 , P 2 comprises a destination MAC address, a source MAC address, a source IP address, a destination IP address, and a group for enrollment in order.
When the providing device 10 recognizes that the communication devices 20 and 20 a have the same prefix (AP 40 ), based on the IP addresses IP_adr 1 and IP_adr 2 of the communication devices 20 and 20 a and the G 1 information, the providing device 10 extracts the IP_adr 1 , MAC 1 and G 1 from the packet P 1 and registers them in the management table 111 as table information T 1 in association with one another. Similarly, the providing device 10 extracts the IP_adr 2 , MAC 2 and G 1 from the packet P 2 and registers them in the management table 111 as table information T 2 in association with one another.
Then the providing device 10 associates the table information T 1 with the table information T 2 as the same subgroup (logical group) M 1 allowing mergeable (broadcast) communication (step S 63 ).
Then the providing device 10 adds the logical key (hereinafter, referred to as LJKEY) to each of the table information T 1 and T 2 associated as M 1 (step S 64 ).
Then the providing device 10 creates packets P 3 and P 4 each including the multicast logical group key (shown by * 1 in FIG. 8 ) having LJKEY, and sends them to the communication devices 20 and 20 a (steps S 65 and S 66 ).
As shown in FIG. 8 , each packet P 3 , P 4 comprises a destination MAC address, a source MAC address, a source IP address, a destination IP address, and a multicast logical group key.
FIG. 9 shows the multicast logical group key of the group communication system of FIG. 8 .
The multicast logical group key comprises fields for LJKEY, Field 1 for transmission of distribution data, Field 2 containing a value resulted from the exclusive OR operation of LJKEY and Field 1 , Mode specifying how to rewrite the destination of the distribution data when LJKEY is satisfied, and an encryption code that is information to decrypt the encryption of data when LKEY is satisfied.
In this embodiment, as an example, a packet-length of 6 bytes (FF FF FF FE FD FC) is set in the LJKEY field. In the Field 1 , a length of 6 bytes (11 22 33 44 55 66) is set from the first zeroth byte of the data. In the Field 2 , a length of 6 bytes (ee dd cc ba a8 98) is set from the sixth byte from the beginning of the data. In the Mode field, “1” (unicast mode) is set. In the encryption code field, “NO” is set. In this connection, in a case of a multicasting mode, “2” is set in this Mode field.
›DESCRIPTION OF THE PREFERRED EMBODIMENTS · 4 of 5
Referring back to FIG. 8 , the communication device 20 receives the packet P 3 , and registers the multicast logical group key in the management table 211 . Similarly, the communication device 20 a receives the packet P 4 and registers the multicast logical group key in to the management table 211 a.
When the communication device 20 a performs broadcast communication of a message Msg 3 to the group G 1 , this device transmits the packet P 5 to the providing device 10 .
As shown in FIG. 8 , the packet P 5 comprises a destination MAC address, a source MAC address, a source IP address, a destination IP address, a group for the broadcast communication, and a message in order.
When the providing device 10 receives the packet P 5 , this device sets a destination communication device (main prefix address) with reference to the management table 111 . This setting method is preferably a fixed-priority method or the Round-Robin method but is not limited to them. In the Round-Robin method, even when the main communication device leaves a group, a next destination can be determined easily.
FIG. 8 shows a case of setting the communication device 20 as a destination.
When the providing device 10 receives the packet P 5 , this device performs the exclusive OR operation of Field 1 and LKEY, the Field 1 sent to the communication device 20 in the packet P 3 and being stored in the management table 211 of the communication device 20 . Then the providing device 10 sends a packet P 6 (distribution data) with CKEY resulted from the operation contained in the Field 2 , to the communication device 20 (step S 68 ).
The communication device 20 recognizes the packet P 6 , confirms the destination and receives this packet (step S 69 ). Then the communication device 20 gives the message Msg 3 to the application section 26 .
The communication device 20 a also recognizes the packet P 6 , and determines whether to receive the packet P 6 (step S 70 ). Specifically, when the exclusive OR operation of Field 1 and CKEY results in LJKEY or when the exclusive OR operation of Field 1 and LJKEY results in CKEY, the packet P 6 is identified as being addressed to the group G 1 . Therefore the communication device 20 a receives the packet P 6 (step S 71 ). Then, in a case of mode 1 (unicast), the communication device 20 a gives the message Msg 3 to the application section 26 a with the destination MAC address of the packet P 6 rewritten to the own MAC address MAC 2 (step S 72 ) and the destination IP address rewritten to the own IP address.
This example shows the case of the unicast mode. In a case of the multicast mode, after reception of the packet P 6 , the communication device 20 rewrites the destination MAC address and the destination IP address of the packet P 6 to the address of the group G 1 and the multicast IP address, respectively.
According to the group communication system of this embodiment as described above, when the communication device 20 , 20 a transmits an enrollment message, the providing device 10 groups the communication devices belonging to the same network (router or access point) based on the connection formation of the network or the network prefix address information (into subgroup A), and after sending LJKEY as management data to the communication device sending the enrollment message, transmits to each subgroup a packet P 6 together with information equivalent to a multicast address, so that the communication devices 20 and 20 a can both receive the packet, like multicast communication. This technique can reduce the traffic volume by 1/n (½ in this embodiment), thus transmitting information to each subgroup with preventing excess network traffic.
Further, effective communication can be realized without additional functions provided on a network.
Still further, full duplex group communication can be realized since private information is not treated as broadcast information.
Still further, since data indicating an unreceivable condition can be set in Field 2 , general communication where data is sent to a specified communication device only can be realized.
Still further, this embodiment uses the communication device 20 as a destination. However, since a result of the exclusive OR operation of LJKEY and information in Field 1 is set in Field 2 , data can be transmitted to any main address. That is, as shown in FIG. 8 , since only CKEY is changed, a wide-area group communication can be performed, even for wireless LAN where a prefix varies, via some access points and networks.
Still further, this embodiment has described a case where the providing device 10 is provided, independently from the communication devices 20 and 20 a via the access network 60 . This embodiment, however, is not limited to this and one communication device 20 , 20 a can operate as the providing device 10 to manage the group G 1 . This can offer effective distribution even in an ad-hoc network. The ad-hoc network can perform half duplex distribution in such a manner that a communication device itself can transmit information to members. In addition, the communication device can receive information from the own device by transmitting the information to a deputy device.
Still further, an encryption mode is not specifically limited. A well-known encryption method of encrypting an entire packet P 6 with an encryption code can be used.
Still further, although the packet P 5 is data that is transmitted from the communication device 20 a , this invention also can be applied to data traveling through the access network 60 from the providing device 20 to a group.
It should be noted that communication devices that belong to the same database, the same network address, or the same domain can be grouped into the same subgroup (logical group) M 1 .
The second embodiment of a group communication system will be now described with reference to FIG. 10 .
Here only different configuration from the above-described first embodiment, that is the configuration of a communication device, will be described.
›DESCRIPTION OF THE PREFERRED EMBODIMENTS · 5 of 5
Referring to FIG. 10 , a terminal device 20 b has some (two in this embodiment) physical circuits 50 and 50 a . The physical circuits 50 and 50 a correspond to the communication devices 20 and 20 a of the group communication system 200 .
At the time of group communication, table information on each physical circuit 50 , 50 a is stored in a management table 111 of a providing device 10 .
This group communication system 200 a of this second embodiment can obtain the same effects as the group communication system 200 of the first embodiment.
In addition, according to the group communication system 200 a of the second embodiment, since a packet from the providing device 10 can be received via the physical circuits 50 and 50 a . Therefore, by providing each of the physical circuits 50 and 50 a with a memory unit to store the packet received via the physical circuits 50 and 50 a , the terminal device 20 b can operate as a backup device.
The group communication method, the communication device and the management device according to this invention have been described with reference to the accompanying drawings. This invention is not limited to them and they can have other equivalent functions. In addition, other configurations and processes can be applied. Two or more configurations (features) of the above-described embodiments can be combined. For example, a group communication method according to one of the embodiments can be used for the subgroup A while communication using a multicast address can be used for the subgroup B.
According to this invention, the communication devices previously store a group key received from the providing device and the providing device performs only one transmission for each subgroup, thereby realizing service like multicast service. Therefore, the data transmission to a plurality of communication devices does not cause excessive network traffic.
In addition, effective communication can be realized without additional functions provided on a network.
The foregoing is considered as illustrative only of the principle of the present invention. Further, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the invention to the exact construction and applications shown and described, and accordingly, all suitable modifications and equivalents may be regarded as falling within the scope of the invention in the appended claims and their equivalents.
Claims as granted
15 claimsLog in to read the claims of this application.
Log in to unlockClassifications
14 codes- H04L12/70
- H04H20/71
Claim changes
SoonSee which claims were amended, added or cancelled during examination, with every added and removed word marked.
The published claims of this application are not paired with the granted ones in what we hold.
File wrapper
See the full prosecution history — every USPTO and applicant action on this file, in order.
Log in to unlockDocuments
Log in to open the documents of this file: the application as filed, every office action and response, the notice of allowance.
Log in to unlockChain of title
See the full assignment history — every owner this patent has passed through, with recordation dates and reel/frame numbers.
Log in to unlock