US20080168566A1 - Group access management system - Google Patents
Group access management system Download PDFInfo
- Publication number
- US20080168566A1 US20080168566A1 US12/050,673 US5067308A US2008168566A1 US 20080168566 A1 US20080168566 A1 US 20080168566A1 US 5067308 A US5067308 A US 5067308A US 2008168566 A1 US2008168566 A1 US 2008168566A1
- Authority
- US
- United States
- Prior art keywords
- group
- service
- user
- class
- rule
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/105—Multiple levels of security
Definitions
- the present invention is generally related to telecommunications and more particularly to services provided to clients via instant messaging applications.
- IM instant messaging
- a representative system includes a group access management system operable to store a plurality of resource lists, the resource lists comprising at least one contact and at least one group comprising at least one member and further comprising a group class of service marker associated with the at least one group.
- the system further comprises a service router coupled to the group access management system and being operable to route a service request, if the service request includes an adequate class of service marker with respect to the group class of service marker.
- a method, among others, for managing group access includes: creating a group comprising at least one member; storing the group in a group access management system; and assigning a class of service level to the group.
- a method, among others, for adding a group to a user resource list includes: sending a request to add a group to a user resource list; providing a class of service marker; and adding the group to the user resource list if the class of service marker allows the group to be added.
- FIG. 1A is a block diagram illustrating an interoperability architecture for instant messaging used in one embodiment, among others, of the present invention.
- FIG. 1B is a block diagram illustrating an alternative embodiment, among others of an interoperability architecture for instant messaging used in one embodiment, among others, of the present invention.
- FIG. 2 is a block diagram of the interoperability architecture used in one embodiment, among others, of the present invention.
- FIG. 3 is a block diagram of a one embodiment, among others, of a system of the present invention for managing group.
- FIG. 4 is an embodiment, among others, of a data structure for storing a group and facilitating the use of the system of FIG. 3 .
- FIG. 5 is a flowchart illustrating operation of the system of FIG. 3 .
- FIG. 1A shown is a block diagram illustrating an interoperability architecture for instant messaging used in one embodiment, among others, of the present invention.
- Each of a plurality of remote computers 100 a - i access a network 110 through a local internet service provider (ISP) server 120 a , 120 b , 140 .
- the local ISP 120 a , 120 b , 140 can offer network 110 access through myriad connection types, including a digital subscriber line (DSL) service, an integrated services digital network (ISDN) service, an analog dial-up service, ethernet, T-1, or any other service for transmitting data through a network 110 .
- DSL digital subscriber line
- ISDN integrated services digital network
- T-1 any other service for transmitting data through a network 110 .
- Universal servers 130 a - c are located between the internet and each of local ISP servers 120 a , 120 b , and located inside local ISP 140 . These universal servers 130 a - c provide interoperability between a plurality of proprietary instant messaging clients 100 a - i. Of course, the scope of the presentation includes networks other than those with universal servers or instant messaging.
- FIG. 1B shown is an illustration of an alternative embodiment, among others, of a universal architecture. Greater detail regarding this interoperability architecture may be found in U.S. patent application Ser. No. 10/135,929, entitled “Instant Messaging Architecture and System for Interoperability and Presence Management,” which is hereby incorporated by reference.
- the universal architecture uses a universal protocol, such as the extensible markup language (XML) protocol to allow users of different ISPs 120 a , 140 that use proprietary protocols to communicate with one another.
- Universal servers 130 a , 130 c located at each of the ISPs 120 a , 140 are the key feature of the universal architecture.
- FIG. 1B illustrates two separate ISP networks 120 a , 140 . The discussion of the ISP 120 a , 140 will be limited to the components that provide the universal service.
- XML extensible markup language
- the ISP 120 a contains a local IM server 150 a , and is connected to the universal server 130 sa.
- the local IM server 150 a provides the standard IM function for the ISP 140 a .
- the universal server 130 a provides the universal function that allows the first user 160 a , who is registered with the first ISP 120 a , to communicate with a second user 160 b registered with the second ISP 140 .
- the first ISP 120 a provides connections to a plurality of clients 170 a , 170 b on computers 100 a , 100 b , which allows users 160 a , 160 b to access the proprietary IM and universal functions of the ISP 120 a .
- the first ISP 120 a is “bimodal,” in that it uses both a proprietary and universal format to provide a proprietary IM function that only allows the users who are registered with the ISP 120 a to send and receive instant messages. For example, if only one user has registered with the universal server 130 a , then the local IM server 150 a will transfer instant messages between the first and second users 160 a , 160 b using the proprietary protocol. However, if both the first and second users 160 a , 160 b are registered with the universal server 130 a , then the first ISP 120 a can transfer instant messages between them using the universal protocol. By supporting both formats at the first ISP 120 a , users can migrate to the universal format over time. When all users 160 a , 160 b have migrated the proprietary format can be discontinued.
- the universal server 130 a removes the restrictions associated with proprietary IM functions associated with the ISP 120 a .
- the universal server 130 a uses a universal format, such as XML, or any other suitable format, that allows users 160 a , 160 b registered with an ISP 140 a , such as BellSouth DotNet, to send and receive instant messages from other users 160 c , 160 d registered with another ISP 140 b , such as America Online (AOL).
- AOL America Online
- the user 160 a accesses the local IM server 150 a of the ISP 120 a through the IM client 170 a located on the user's computer 100 a .
- the IM client 170 a typically includes a proprietary software program that is capable of opening communications sockets that allow the IM client 170 a to communicate with the local IM server 150 a using either the proprietary or universal protocols.
- the software program is capable of formatting an instant message sent from the IM client 170 a to the appropriate format used by the IM function of the ISP 120 a . In this manner, the user 170 a is capable of communicating with any other user 160 b registered with the ISP 120 a .
- the local IM server 150 a on a first ISP 120 a is also connected to a first universal server 130 a .
- the first universal server 130 a is in turn, connected to a second universal server 130 b on the second ISP 140 b via a distributed network, such as the internet 110 .
- This allows the user 160 a to communicate not only with the user 160 b who is registered with the first ISP 120 a , but also with users 160 c who are registered with the second ISP 140 that uses a different proprietary IM protocol to send and receive instant messages within the network of the second ISP 140 .
- the IM client 170 a In order for the first user 160 a to be able to send and receive messages with a third user 160 c on the second ISP 140 , the IM client 170 a must be able to identify the IP address and presence information associated with the third user 160 c .
- the presence information for the third user 160 c is stored on the universal server 130 a connected to the first ISP 120 a .
- the universal server 130 a on the first ISP 120 a stores the IP address and presence information for the third user 160 c . Therefore, the first user 160 a , who is registered with the universal server 130 a on the first ISP 120 a has access to the IP address and presence information of the third user 160 c.
- the second local ISP 140 is an alternative embodiment that includes within the ISP 140 both the universal server 130 c and a local IM server 150 b .
- the local IM server 150 b does not communicate with the universal server 130 c .
- the first user 160 a will not be able to communicate with a fourth user 160 d if the fourth user 160 d is not registered with the universal server 130 b , but instead is only registered with a local IM server 150 b .
- the fourth user 160 d is able to send and receive instant messages using only the proprietary format over local IM server 150 b . Therefore, the user 160 d is limited to communicating via instant messages with users of the second ISP 140 b , such as the third user 160 c.
- An advantageous feature of the universal architecture is that it is designed to be easily integrated within existing ISPs 120 a , 140 , such as AOL and Microsoft Network (MSN) without disrupting the current IM function of these ISPs 120 a , 140 .
- Each ISP 120 a , 140 that adopts the universal architecture requires only a slight modification to the existing network.
- the ISP 120 a , 140 either adds a universal server 130 a between the local IM server 150 a and the internet 110 , or adds an additional server to function as the universal server 130 b and can install a universal application program on the local IM server 150 a , 150 b and each IM client 170 a - d attached to the network.
- the universal application program that is installed at each ISP 120 a , 140 converts the ISP 120 a , 140 to function as “bimodal.” That is, the ISP 120 a , 140 is capable of using the proprietary IM protocol of the local IM server 150 a , 150 b and the universal protocol of the universal architecture.
- the bimodal nature of the universal architecture allows the universal server 130 a , 130 b to be implemented into existing ISPs 120 a , 140 such as AOL and MSN without disrupting the current proprietary IM functions of those services. This allows the current users 160 a - d to continue using the proprietary IM function of their particular ISP 120 a , 140 until every user 160 a - d can be converted to the universal protocol.
- the client 170 includes at least three layers of functionality in one embodiment, among others, to communicate with the universal server 130 .
- the first layer is the presentation layer 205 .
- the presentation layer 205 includes the logic that is used to present the instant messenger or another application to a user.
- the second layer is a middleware layer 210 .
- the middleware layer 210 includes logic used to handle the message routing of the instant messaging application between the presentation layer and the service layer.
- the third layer is the service layer 215 .
- the service layer 215 handles both the applications management and communications management of the client.
- the service layer 215 communicates with the communications layer 220 on the universal server 130 .
- the first layer is the communications manager (CCM) 220 .
- the communications manager 220 manages the connections between the client communications manager 215 and the universal server 130 .
- communications between the client service layer 215 and the universal server 130 communications manager 220 occur in extensible markup language (XML).
- XML extensible markup language
- the communications may be secure socket layer (SSL) encrypted for security.
- the communications can be compressed by a compression/decompression algorithm implemented on a compression-decompression module, more commonly referred to as a CODEC, to provide faster data transfer.
- the communications manager 220 includes a number of connection sockets between the communications manager 220 and a plurality of users.
- the communications manager 220 can further include a load balancer (not shown) to balance the connections over a number of different communications managers.
- the load balancer can maintain a connection to the same connection socket during the period while the user is logged on and connected to an operable communications manager 220 , and can automatically connect the user to an alternate connection socket when a communications manager might fail. Thus, a continuous connection can be maintained during an active session despite hardware failures.
- the load balancer can also protect the server against denial of service attacks, which have become increasingly prevalent on the internet.
- a standard communications manager 220 will typically attempt to recover and reallocate a connection socket after a period of time with no activity from the client 170 . In this situation the communications manager 220 assumes that the client is no longer present on the system. However, because presence is an important piece of the instant messaging architecture, the communications layer 215 on the client-side sends a signal to the universal server 130 to keep the connection socket active on the communications manager 220 .
- the second layer is the service router 225 , with one example known as a JabberD in the Jabber architecture, such as that available from Jabber, Inc. of Denver, Colo., which performs a similar function to the message router 210 on the client side of the network.
- a number of different service managers 230 can be coupled to the service router 225 , each of which can provide a different service to the client 170 over the internet.
- the service router 225 routes the request to the requested service manager 230 .
- the service manager 230 is a Jabber service manager (JSM) which allows text communication between parties.
- JSM Jabber service manager
- the JSM 230 also keeps track of presence and roster information 235 , 240 , respectively, for a particular user on the network who has logged into the instant messaging system. Presence 235 typically refers to the user's status on the network, while roster 240 typically refers to the status on the network of those on the user's resource list.
- the service router 225 can utilize a self-similar architecture using the CODEC (not shown) and load balancer (not shown) to optimize the connection between the communications manager 220 and the service router 225 .
- Use of the CODEC enables high speed data transmission between the communications manager 220 and the service router 225 .
- the load balancer provides a robustness that allows the client to maintain contact with a selected service manager 230 during a session.
- the database containing the non-persistent data can be severed from the service manager 230 .
- the presence information 235 typically includes a list of all users who are registered with the universal server 130 , while the roster list includes a non-persistent list of those resource which are present on the network.
- the non-persistent data can be maintained and updated at a single database, and the plurality of service routers 225 can connect to the same presence information 235 .
- the service manager 230 can be equipped, as described above, with a CODEC (not shown) and load balancer (not shown), again utilizing a self-similar architecture to provide quality of service and communication efficiencies.
- the service router 225 is further coupled, in one embodiment, among others, to an XML database (XDB) library 245 .
- the XDB library 245 is used as a translator such that the service router 225 can communicate with a database system 250 that includes persistent data relating to a plurality of clients.
- the database system 250 which contains most of the persistent data for the services on the network, such as resource lists, preferences, etc.
- the database system 250 can be an Oracle 9i database.
- the XDB library 245 can be further coupled to an authentication server, such as a username and password database 255 . Thus a username and password can be required before the user is authenticated and allowed to access the database system 250 for any profile information.
- the user After registering with the database system 250 , the user is provided with a resource list.
- the client 170 can then contact the service manager 230 to find out which of the resources on the resource list is present and/or available on the network.
- presence refers to the registration state of a client 170 . If a client 170 is logged-in to the network, the client 170 is present on the network.
- availability refers to the status of a user at the client computer. A user can be made unavailable by the network if there has been no activity on the client computer 170 for a period of time. Otherwise, a client 170 can be made unavailable by user choice, if the user does not wish to be disturbed.
- the resource list only comprises a list of other users for which the client 170 wishes to know the status.
- the resource list of some embodiments of the present invention could include access to a plurality of applications, and there could be multiple service managers that include managers for the plurality of applications coupled to the service router 225 . These service managers could provide access to a multitude of different applications and resources, such as Microsoft Word and/or Visio, provided by Microsoft Corp. of Redmond, Wash., and/or billing entry applications, etc.
- the Jabber service manager 230 could keep track of the presence of these other applications and other resources on the network.
- the Jabber service manager 230 could alert the user that the server was down.
- the client 170 would not waste resources searching and waiting for e-mail from a server that is off-line.
- the Jabber instant messenger can be used similarly to an operating system.
- the resource(s) associated with that resource server can be displayed as an icon on the client computer display, and when a resource server is down, the resource(s) can be removed from the client computer 170 display.
- icons for example, could appear and disappear from a client computer 170 display as they become present and available, and not present or unavailable. Selecting the icon while it is displayed will cause a routing request to be sent to the service router 225 . Upon receiving the routing request, the service router 225 will determine the correct routing of the routing request and deliver the proper service to the client computer 170 .
- FIG. 3 shown is an embodiment, among others, of the universal server including an embodiment of a group access management system 300 for creating and editing groups.
- This group access management system 300 allows an administrator to create group lists 305 , and push the group lists 305 into a client profile or class of service to be displayed on the client 200 .
- a group 305 can be created to be displayed on every client 170 with a certain class of service level or every client 170 to whom a database 250 ′ administrator desires the group 305 to be shown.
- This system would help the database 250 ′ administrator in the creation of newsgroups, for example.
- the administrator creating the group 305 would be allowed to set extra field markers such as attribute 310 or class of service 320 that allow only members 330 of the group 305 or members of a certain class of service level to access the group.
- extra field markers such as attribute 310 or class of service 320 that allow only members 330 of the group 305 or members of a certain class of service level to access the group.
- the administrator can designate certain groups to be public groups according to the attribute field.
- a group When a group is designated a public group, all users of the system will be allowed to view the public group and add a number of these public groups to their resource list, regardless of the user's respective class of service level.
- a user could request that the universal server 130 provide a list of all public groups.
- the universal server 130 could then mask off all of the private group lists (filtering out all of the private groups), such that the user would be allowed to view only the public groups.
- a user could search all groups and be allowed to view the public groups in addition to those groups to which the user's class of service level allows access.
- this administrative application tool can override the class of service accessibility discussed in the provisional application above with respect to the service router 225 .
- an administrator can mask a group 305 from a user who may technically have access to two different service center groups by providing that only one of the service center groups be available to that user.
- the persistent database 250 ′′ has a plurality of records 400 that are associated with various users of the universal server 130 ( FIG. 3 ). Each of these records 400 contain a plurality of fields, including, but not limited to preferences 405 and resource lists 410 .
- the resource list 410 comprises a plurality of contacts 415 , 420 , 425 , 430 . Each of these contacts 415 , 420 , 425 , 430 includes a link to a unique identifier identifying a user associated with the each of the contacts 415 , 420 , 425 , 430 .
- a group contact 430 may be added to the resource list.
- the group contact 430 can in one embodiment, among others, contain a link to a public or private group 430 , that may be created centrally by a database 250 ′′ administrator, or an individual user.
- the database 250 in one embodiment, among others, could store the group 450 centrally, without requiring each user to separately store the group list 450 .
- the phone service group listing 430 could further include a rule 440 for the group.
- the rule could be used to indicate presence of the group 430 when a particular member 460 or subset of the group is present and available.
- the rule could be set by the user, but could also be set automatically by the universal server 130 upon addition of the group 430 to the resource list 410 .
- the group list 450 can include a plurality of users 460 , such as, for example, but not limited to, operators. Each of the individual users 460 would be linked to a unique identifier, which would allow two users to use the same “handle,” being differentiated by a unique identifier. Further, the group list 450 could include other fields such as, for example, but not limited to, attributes 470 , class of service 480 , and rules 490 .
- the attributes field 470 could consist of a marker which indicates the viewability of the group 450 with respect to the users of the universal server 130 .
- the attributes 470 can be set such that every user of the universal server 130 can view the group 450 , or so that it is not viewable to every user. This field 470 can be useful in creating private groups, such that only certain users or that no users may view the group 450 .
- the class of service field 480 can be used to create a group 450 which cannot be added to the resource list 410 of users without the required class of service marker. Thus, for example, if the group 450 is classified as class of service 1 , and the user has class of service 2 , the user would not be able to add the group 450 to the user's resource list 410 .
- This class of service marker 480 provides a tool by which the database 250 ′′ administrator can control access of the user to any particular group 450 .
- the universal server 130 in one embodiment, among others, may prompt the user to upgrade the user's respective class of service marker to add the group 450 to their resource list 410 . In one embodiment, among others, this upgrade may be facilitated by a charge to the user's account.
- the rules field 490 may be used to provide an alternative way to control access to the group list 450 .
- the database 250 ′′ administrator may use this field to add various users of the universal server 130 to a list of those permitted to access the group list 450 .
- it can be used to further defined other fields of the group list 450 .
- a rule may be written whereby one of the attributes of the group could be to show the group to a certain subgroup of users.
- the first step 500 is for an administrator to create a group list using the administrative application tool, adding attributes and class of service requirements under the group.
- the group is stored in the persistent database.
- the database receives a request to add the group to a resource list corresponding to a user.
- the database 250 checks to see that the class of service marker associated with the particular using wishing to add the group is sufficient in step 530 . If the class of service marker is sufficient, the next step 540 is to add the group 430 to the resource list 410 .
- the next step 550 can be to send a request to the database 250 administrator to request that the user be allowed to add the group 430 to their resource list 410 .
- the administrator may, in the next step 560 , add the user to the rules 490 allowing the user to add the group 430 to their resource list 410 .
- the administrator may decline the user, in which case the user is refused permission, according to step 570 , to allow the group 430 to their resource list 410 .
- Process and function descriptions and blocks in flow charts can be understood as representing, in some embodiments, modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process, and alternate implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.
- functional elements can be implemented as logic embodied in hardware, software, firmware, or a combination thereof, among others.
- such software comprises an ordered listing of executable instructions for implementing logical functions and can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions.
- a computer-readable medium can be any means that can contain, store, communicate, propagate, or transport the software for use by or in connection with the instruction execution system, apparatus, or device.
Abstract
Description
- This application is a continuation of U.S. patent application entitled, “GROUP ACCESS MANAGEMENT SYSTEM,” which is entirely incorporated herein by reference, having Ser. No. 10/217,916, filed Aug. 13, 2002, which claims priority to copending U.S. provisional application entitled, “INTEGRATION OF INSTANT MESSAGING AND COMPUTER OPERATING SYSTEMS,” having Ser. No. 60/382,106, filed May 21, 2002, which are entirely incorporated herein by reference.
- The present invention is generally related to telecommunications and more particularly to services provided to clients via instant messaging applications.
- The development of the internet has driven vast technological developments, particularly in the areas of networking hardware and software. Networking hardware developments have enabled networks to transfer large files in fractions of a second. Software developments, such as the world-wide-web (web) and e-mail, have facilitated communications over these networks that have allowed users to remain in almost constant contact with work. These types of communications have become of utmost importance in the business setting, where response time has become a key survival factor for many companies. Other networking software has allowed users to access and run applications from remote locations, thus enabling a businessperson to remain more productive, even on a business trip.
- Moreover, the internet has changed the way people communicate. E-mail has become the dominant means of communications in many settings, being preferred over traditional mail, and even telephones in some cases. Almost instantaneous communication with little charge has driven much of the popularity of e-mail. Once used only in university and military settings, e-mail has gained widespread public acceptance.
- In a world economy based largely upon communication, the relative speed of e-mail in comparison to traditional mail is often not fast enough or as effective. Demand for faster access to more information has resulted in the development of a number of instant messaging (IM) services. IM brings presence information into the communications arena, and it allows users to have real-time chat sessions with other users who are present on the system. The real-time nature of IM has led to quick acceptance by many in the business community of IM as an invaluable tool for communication. However, current IM systems often have administration and management problems.
- Therefore, there is a need for systems and method that address these and/or other perceived shortcomings of the prior art.
- One embodiment, among others, of the present invention provides systems and methods for a limiting group access. A representative system includes a group access management system operable to store a plurality of resource lists, the resource lists comprising at least one contact and at least one group comprising at least one member and further comprising a group class of service marker associated with the at least one group. The system further comprises a service router coupled to the group access management system and being operable to route a service request, if the service request includes an adequate class of service marker with respect to the group class of service marker.
- A method, among others, for managing group access includes: creating a group comprising at least one member; storing the group in a group access management system; and assigning a class of service level to the group.
- A method, among others, for adding a group to a user resource list includes: sending a request to add a group to a user resource list; providing a class of service marker; and adding the group to the user resource list if the class of service marker allows the group to be added.
- Other systems, methods, features, and advantages of the present invention will be or become apparent to one with skill in the art upon examination of the following drawings and detailed description. It is intended that all such additional systems, methods, features, and advantages included within this description and within the scope of the present invention.
- The invention can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.
-
FIG. 1A is a block diagram illustrating an interoperability architecture for instant messaging used in one embodiment, among others, of the present invention. -
FIG. 1B is a block diagram illustrating an alternative embodiment, among others of an interoperability architecture for instant messaging used in one embodiment, among others, of the present invention. -
FIG. 2 is a block diagram of the interoperability architecture used in one embodiment, among others, of the present invention. -
FIG. 3 is a block diagram of a one embodiment, among others, of a system of the present invention for managing group. -
FIG. 4 is an embodiment, among others, of a data structure for storing a group and facilitating the use of the system ofFIG. 3 . -
FIG. 5 is a flowchart illustrating operation of the system ofFIG. 3 . - The preferred embodiments of the present invention now will be described more fully with reference to the accompanying drawings. The invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are intended to convey the scope of the invention to those skilled in the art. Furthermore, all “examples” given herein are intended to be non-limiting.
- Referring now to
FIG. 1A , shown is a block diagram illustrating an interoperability architecture for instant messaging used in one embodiment, among others, of the present invention. Each of a plurality ofremote computers 100 a-i access anetwork 110 through a local internet service provider (ISP)server local ISP network 110 access through myriad connection types, including a digital subscriber line (DSL) service, an integrated services digital network (ISDN) service, an analog dial-up service, ethernet, T-1, or any other service for transmitting data through anetwork 110.Universal servers 130 a-c are located between the internet and each oflocal ISP servers local ISP 140. Theseuniversal servers 130 a-c provide interoperability between a plurality of proprietaryinstant messaging clients 100 a-i. Of course, the scope of the presentation includes networks other than those with universal servers or instant messaging. - Referring now to
FIG. 1B , shown is an illustration of an alternative embodiment, among others, of a universal architecture. Greater detail regarding this interoperability architecture may be found in U.S. patent application Ser. No. 10/135,929, entitled “Instant Messaging Architecture and System for Interoperability and Presence Management,” which is hereby incorporated by reference. The universal architecture uses a universal protocol, such as the extensible markup language (XML) protocol to allow users ofdifferent ISPs Universal servers ISPs FIG. 1B illustrates twoseparate ISP networks ISP - The ISP 120 a contains a
local IM server 150 a, and is connected to theuniversal server 130 sa. Thelocal IM server 150 a provides the standard IM function for the ISP 140 a. Theuniversal server 130 a provides the universal function that allows thefirst user 160 a, who is registered with thefirst ISP 120 a, to communicate with asecond user 160 b registered with thesecond ISP 140. Thefirst ISP 120 a provides connections to a plurality ofclients computers users ISP 120 a. Thefirst ISP 120 a is “bimodal,” in that it uses both a proprietary and universal format to provide a proprietary IM function that only allows the users who are registered with theISP 120 a to send and receive instant messages. For example, if only one user has registered with theuniversal server 130 a, then thelocal IM server 150 a will transfer instant messages between the first andsecond users second users universal server 130 a, then thefirst ISP 120 a can transfer instant messages between them using the universal protocol. By supporting both formats at thefirst ISP 120 a, users can migrate to the universal format over time. When allusers - The
universal server 130 a removes the restrictions associated with proprietary IM functions associated with theISP 120 a. Theuniversal server 130 a uses a universal format, such as XML, or any other suitable format, that allowsusers other users - The
user 160 a accesses thelocal IM server 150 a of theISP 120 a through theIM client 170 a located on the user'scomputer 100 a. TheIM client 170 a typically includes a proprietary software program that is capable of opening communications sockets that allow theIM client 170 a to communicate with thelocal IM server 150 a using either the proprietary or universal protocols. The software program is capable of formatting an instant message sent from theIM client 170 a to the appropriate format used by the IM function of theISP 120 a. In this manner, theuser 170 a is capable of communicating with anyother user 160 b registered with theISP 120 a. However, thelocal IM server 150 a on afirst ISP 120 a is also connected to a firstuniversal server 130 a. The firstuniversal server 130 a is in turn, connected to a seconduniversal server 130 b on the second ISP 140 b via a distributed network, such as theinternet 110. This allows theuser 160 a to communicate not only with theuser 160 b who is registered with thefirst ISP 120 a, but also withusers 160 c who are registered with thesecond ISP 140 that uses a different proprietary IM protocol to send and receive instant messages within the network of thesecond ISP 140. - In order for the
first user 160 a to be able to send and receive messages with athird user 160 c on thesecond ISP 140, theIM client 170 a must be able to identify the IP address and presence information associated with thethird user 160 c. The presence information for thethird user 160 c is stored on theuniversal server 130 a connected to thefirst ISP 120 a. Theuniversal server 130 a on thefirst ISP 120 a stores the IP address and presence information for thethird user 160 c. Therefore, thefirst user 160 a, who is registered with theuniversal server 130 a on thefirst ISP 120 a has access to the IP address and presence information of thethird user 160 c. - One skilled in the art will recognize the difference between the first
local ISP 120 a and thesecond ISP 140. The secondlocal ISP 140 is an alternative embodiment that includes within theISP 140 both theuniversal server 130 c and alocal IM server 150 b. Here, thelocal IM server 150 b does not communicate with theuniversal server 130 c. Thus, thefirst user 160 a will not be able to communicate with afourth user 160 d if thefourth user 160 d is not registered with theuniversal server 130 b, but instead is only registered with alocal IM server 150 b. As a result, thefourth user 160 d is able to send and receive instant messages using only the proprietary format overlocal IM server 150 b. Therefore, theuser 160 d is limited to communicating via instant messages with users of the second ISP 140 b, such as thethird user 160 c. - An advantageous feature of the universal architecture is that it is designed to be easily integrated within existing
ISPs ISPs ISP ISP universal server 130 a between thelocal IM server 150 a and theinternet 110, or adds an additional server to function as theuniversal server 130 b and can install a universal application program on thelocal IM server IM client 170 a-d attached to the network. The universal application program that is installed at eachISP ISP ISP local IM server universal server ISPs particular ISP - Referring now to
FIG. 2 , shown is a block diagram illustrating an embodiment, among others, of theuniversal server 130 ofFIG. 1A & B, which is used in conjunction with an embodiment, among others, of the present invention. Theclient 170 includes at least three layers of functionality in one embodiment, among others, to communicate with theuniversal server 130. The first layer is thepresentation layer 205. Thepresentation layer 205 includes the logic that is used to present the instant messenger or another application to a user. The second layer is amiddleware layer 210. Themiddleware layer 210 includes logic used to handle the message routing of the instant messaging application between the presentation layer and the service layer. The third layer is theservice layer 215. Theservice layer 215 handles both the applications management and communications management of the client. Theservice layer 215 communicates with thecommunications layer 220 on theuniversal server 130. - Preferably, there are three basic layers to the instant messaging service. The first layer is the communications manager (CCM) 220. The
communications manager 220 manages the connections between theclient communications manager 215 and theuniversal server 130. In one embodiment, among others, of theuniversal server 130, communications between theclient service layer 215 and theuniversal server 130communications manager 220 occur in extensible markup language (XML). Further, the communications may be secure socket layer (SSL) encrypted for security. Moreover, the communications can be compressed by a compression/decompression algorithm implemented on a compression-decompression module, more commonly referred to as a CODEC, to provide faster data transfer. - The
communications manager 220 includes a number of connection sockets between thecommunications manager 220 and a plurality of users. Thecommunications manager 220 can further include a load balancer (not shown) to balance the connections over a number of different communications managers. The load balancer can maintain a connection to the same connection socket during the period while the user is logged on and connected to anoperable communications manager 220, and can automatically connect the user to an alternate connection socket when a communications manager might fail. Thus, a continuous connection can be maintained during an active session despite hardware failures. The load balancer can also protect the server against denial of service attacks, which have become increasingly prevalent on the internet. - A
standard communications manager 220 will typically attempt to recover and reallocate a connection socket after a period of time with no activity from theclient 170. In this situation thecommunications manager 220 assumes that the client is no longer present on the system. However, because presence is an important piece of the instant messaging architecture, thecommunications layer 215 on the client-side sends a signal to theuniversal server 130 to keep the connection socket active on thecommunications manager 220. - The second layer is the
service router 225, with one example known as a JabberD in the Jabber architecture, such as that available from Jabber, Inc. of Denver, Colo., which performs a similar function to themessage router 210 on the client side of the network. A number ofdifferent service managers 230 can be coupled to theservice router 225, each of which can provide a different service to theclient 170 over the internet. Thus when a service is requested, theservice router 225 routes the request to the requestedservice manager 230. In the instant messaging architecture theservice manager 230 is a Jabber service manager (JSM) which allows text communication between parties. TheJSM 230 also keeps track of presence androster information Presence 235 typically refers to the user's status on the network, whileroster 240 typically refers to the status on the network of those on the user's resource list. - Similarly to the
communications manager 220, theservice router 225 can utilize a self-similar architecture using the CODEC (not shown) and load balancer (not shown) to optimize the connection between thecommunications manager 220 and theservice router 225. Use of the CODEC enables high speed data transmission between thecommunications manager 220 and theservice router 225. The load balancer provides a robustness that allows the client to maintain contact with a selectedservice manager 230 during a session. - In one embodiment, among others, of the
universal server 130, the database containing the non-persistent data, such as presence androster information service manager 230. Thepresence information 235 typically includes a list of all users who are registered with theuniversal server 130, while the roster list includes a non-persistent list of those resource which are present on the network. Thus, the non-persistent data can be maintained and updated at a single database, and the plurality ofservice routers 225 can connect to thesame presence information 235. After severing this database from theservice manager 230 theservice manager 230 can be equipped, as described above, with a CODEC (not shown) and load balancer (not shown), again utilizing a self-similar architecture to provide quality of service and communication efficiencies. - The
service router 225 is further coupled, in one embodiment, among others, to an XML database (XDB)library 245. TheXDB library 245 is used as a translator such that theservice router 225 can communicate with adatabase system 250 that includes persistent data relating to a plurality of clients. Thedatabase system 250 which contains most of the persistent data for the services on the network, such as resource lists, preferences, etc. In one embodiment, among others, of theuniversal server 130 thedatabase system 250 can be anOracle 9i database. TheXDB library 245 can be further coupled to an authentication server, such as a username andpassword database 255. Thus a username and password can be required before the user is authenticated and allowed to access thedatabase system 250 for any profile information. - After registering with the
database system 250, the user is provided with a resource list. Theclient 170 can then contact theservice manager 230 to find out which of the resources on the resource list is present and/or available on the network. Typically, presence refers to the registration state of aclient 170. If aclient 170 is logged-in to the network, theclient 170 is present on the network. Typically, availability refers to the status of a user at the client computer. A user can be made unavailable by the network if there has been no activity on theclient computer 170 for a period of time. Otherwise, aclient 170 can be made unavailable by user choice, if the user does not wish to be disturbed. One skilled in the art will recognize that these are merely definitions of various states that can be defined according to any specific implementation of the presence androster databases databases service manager 230. - Typically with respect to other instant messaging systems, the resource list only comprises a list of other users for which the
client 170 wishes to know the status. However, the resource list of some embodiments of the present invention could include access to a plurality of applications, and there could be multiple service managers that include managers for the plurality of applications coupled to theservice router 225. These service managers could provide access to a multitude of different applications and resources, such as Microsoft Word and/or Visio, provided by Microsoft Corp. of Redmond, Wash., and/or billing entry applications, etc. Moreover, theJabber service manager 230 could keep track of the presence of these other applications and other resources on the network. For example, if a client wished to access an e-mail account from a remote location and the system was down, theJabber service manager 230 could alert the user that the server was down. Thus theclient 170 would not waste resources searching and waiting for e-mail from a server that is off-line. - Thus, the Jabber instant messenger can be used similarly to an operating system. When a
resource server 260 is present on the network, the resource(s) associated with that resource server can be displayed as an icon on the client computer display, and when a resource server is down, the resource(s) can be removed from theclient computer 170 display. Thus, icons, for example, could appear and disappear from aclient computer 170 display as they become present and available, and not present or unavailable. Selecting the icon while it is displayed will cause a routing request to be sent to theservice router 225. Upon receiving the routing request, theservice router 225 will determine the correct routing of the routing request and deliver the proper service to theclient computer 170. - Referring now to
FIG. 3 , shown is an embodiment, among others, of the universal server including an embodiment of a groupaccess management system 300 for creating and editing groups. This groupaccess management system 300 allows an administrator to create group lists 305, and push the group lists 305 into a client profile or class of service to be displayed on the client 200. Thus agroup 305 can be created to be displayed on everyclient 170 with a certain class of service level or everyclient 170 to whom adatabase 250′ administrator desires thegroup 305 to be shown. This system would help thedatabase 250′ administrator in the creation of newsgroups, for example. - The administrator creating the
group 305 would be allowed to set extra field markers such asattribute 310 or class ofservice 320 that allow onlymembers 330 of thegroup 305 or members of a certain class of service level to access the group. Thus when a user that is not included on the list ofmembers 330 and does not have a class ofservice marker 320 that allows the user to add thegroup 305, the user will have to wait for authorization before thegroup 305 is posted to the user's resource list. - Further, the administrator can designate certain groups to be public groups according to the attribute field. When a group is designated a public group, all users of the system will be allowed to view the public group and add a number of these public groups to their resource list, regardless of the user's respective class of service level. Using this attribute field, a user could request that the
universal server 130 provide a list of all public groups. Theuniversal server 130 could then mask off all of the private group lists (filtering out all of the private groups), such that the user would be allowed to view only the public groups. Moreover, a user could search all groups and be allowed to view the public groups in addition to those groups to which the user's class of service level allows access. - One skilled in the art will recognize that this administrative application tool can override the class of service accessibility discussed in the provisional application above with respect to the
service router 225. Thus, an administrator can mask agroup 305 from a user who may technically have access to two different service center groups by providing that only one of the service center groups be available to that user. - Referring now to
FIG. 4 , shown is a data structure, illustrating the organization of the group fromFIG. 3 within a particular user's profile. Thepersistent database 250″ has a plurality ofrecords 400 that are associated with various users of the universal server 130 (FIG. 3 ). Each of theserecords 400 contain a plurality of fields, including, but not limited topreferences 405 and resource lists 410. In turn, theresource list 410 comprises a plurality ofcontacts contacts contacts - However, in the present invention, a
group contact 430 may be added to the resource list. Thegroup contact 430 can in one embodiment, among others, contain a link to a public orprivate group 430, that may be created centrally by adatabase 250″ administrator, or an individual user. In turn thedatabase 250, in one embodiment, among others, could store thegroup 450 centrally, without requiring each user to separately store thegroup list 450. Referring back to the user's resource list, the phone service group listing 430 could further include arule 440 for the group. The rule could be used to indicate presence of thegroup 430 when aparticular member 460 or subset of the group is present and available. The rule could be set by the user, but could also be set automatically by theuniversal server 130 upon addition of thegroup 430 to theresource list 410. - Now referring back to the
centralized group list 450, thegroup list 450 can include a plurality ofusers 460, such as, for example, but not limited to, operators. Each of theindividual users 460 would be linked to a unique identifier, which would allow two users to use the same “handle,” being differentiated by a unique identifier. Further, thegroup list 450 could include other fields such as, for example, but not limited to, attributes 470, class ofservice 480, and rules 490. - The attributes field 470 could consist of a marker which indicates the viewability of the
group 450 with respect to the users of theuniversal server 130. Theattributes 470 can be set such that every user of theuniversal server 130 can view thegroup 450, or so that it is not viewable to every user. Thisfield 470 can be useful in creating private groups, such that only certain users or that no users may view thegroup 450. - The class of
service field 480 can be used to create agroup 450 which cannot be added to theresource list 410 of users without the required class of service marker. Thus, for example, if thegroup 450 is classified as class ofservice 1, and the user has class ofservice 2, the user would not be able to add thegroup 450 to the user'sresource list 410. This class ofservice marker 480 provides a tool by which thedatabase 250″ administrator can control access of the user to anyparticular group 450. Alternatively, theuniversal server 130 in one embodiment, among others, may prompt the user to upgrade the user's respective class of service marker to add thegroup 450 to theirresource list 410. In one embodiment, among others, this upgrade may be facilitated by a charge to the user's account. - Finally, the rules field 490 may be used to provide an alternative way to control access to the
group list 450. Thedatabase 250″ administrator may use this field to add various users of theuniversal server 130 to a list of those permitted to access thegroup list 450. Moreover, it can be used to further defined other fields of thegroup list 450. For example, a rule may be written whereby one of the attributes of the group could be to show the group to a certain subgroup of users. - Referring now to
FIG. 5 , shown is one embodiment, among others, of a flowchart illustrating operation of the system ofFIG. 3 . Thefirst step 500 is for an administrator to create a group list using the administrative application tool, adding attributes and class of service requirements under the group. After the group has been created, in thenext step 510, the group is stored in the persistent database. In accordance with thenext step 520, the database receives a request to add the group to a resource list corresponding to a user. Thedatabase 250 then checks to see that the class of service marker associated with the particular using wishing to add the group is sufficient instep 530. If the class of service marker is sufficient, thenext step 540 is to add thegroup 430 to theresource list 410. - If the class of service marker is insufficient to add the
group 430 to theresource list 410 of the user, thenext step 550 can be to send a request to thedatabase 250 administrator to request that the user be allowed to add thegroup 430 to theirresource list 410. The administrator may, in thenext step 560, add the user to therules 490 allowing the user to add thegroup 430 to theirresource list 410. Alternatively, the administrator may decline the user, in which case the user is refused permission, according tostep 570, to allow thegroup 430 to theirresource list 410. - Process and function descriptions and blocks in flow charts can be understood as representing, in some embodiments, modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process, and alternate implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention. In addition, such functional elements can be implemented as logic embodied in hardware, software, firmware, or a combination thereof, among others. In some embodiments involving software implementations, such software comprises an ordered listing of executable instructions for implementing logical functions and can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a computer-readable medium can be any means that can contain, store, communicate, propagate, or transport the software for use by or in connection with the instruction execution system, apparatus, or device.
- It should be emphasized that the above-described embodiments of the present invention are merely possible examples of implementations set forth for a clear understanding of the principles of the invention. Many variations and modifications may be made to the above-described embodiment(s) of the invention without departing substantially from the principles of the invention. All such modifications and variations are intended to be included herein within the scope of this disclosure and the present invention and protected by the following claims.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/050,673 US20080168566A1 (en) | 2002-05-21 | 2008-03-18 | Group access management system |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US38210602P | 2002-05-21 | 2002-05-21 | |
US10/217,916 US7346696B2 (en) | 2002-05-21 | 2002-08-13 | Group access management system |
US12/050,673 US20080168566A1 (en) | 2002-05-21 | 2008-03-18 | Group access management system |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/217,916 Continuation US7346696B2 (en) | 2002-05-21 | 2002-08-13 | Group access management system |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080168566A1 true US20080168566A1 (en) | 2008-07-10 |
Family
ID=29552854
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/217,916 Expired - Fee Related US7346696B2 (en) | 2002-05-21 | 2002-08-13 | Group access management system |
US12/050,673 Abandoned US20080168566A1 (en) | 2002-05-21 | 2008-03-18 | Group access management system |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/217,916 Expired - Fee Related US7346696B2 (en) | 2002-05-21 | 2002-08-13 | Group access management system |
Country Status (3)
Country | Link |
---|---|
US (2) | US7346696B2 (en) |
AU (1) | AU2003243291A1 (en) |
WO (1) | WO2003100646A1 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040003084A1 (en) * | 2002-05-21 | 2004-01-01 | Malik Dale W. | Network resource management system |
US20070088759A1 (en) * | 2002-05-21 | 2007-04-19 | Bellsouth Intellectual Property Corporation | Network Update Manager |
US20070156827A1 (en) * | 2005-11-18 | 2007-07-05 | Aol Llc | Promoting interoperability of presence-based systems through the use of ubiquitous online identities |
US20070288573A1 (en) * | 2002-05-21 | 2007-12-13 | At&T Bls Intellectual Property, Inc. | Resource List Management System |
Families Citing this family (65)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7296066B2 (en) * | 2001-03-04 | 2007-11-13 | Adomo, Inc. | Mobile communication system for a network |
US7400879B2 (en) * | 2001-03-04 | 2008-07-15 | Adomo, Inc. | Method for conducting mobile communications for a network |
US7516182B2 (en) * | 2002-06-18 | 2009-04-07 | Aol Llc | Practical techniques for reducing unsolicited electronic messages by identifying sender's addresses |
US7899867B1 (en) * | 2002-07-31 | 2011-03-01 | FaceTime Communications, Inc, | SpIM blocking and user approval techniques for real-time messaging networks |
US7620691B1 (en) | 2003-02-10 | 2009-11-17 | Aol Llc | Filtering electronic messages while permitting delivery of solicited electronics messages |
US7290033B1 (en) * | 2003-04-18 | 2007-10-30 | America Online, Inc. | Sorting electronic messages using attributes of the sender address |
US7590695B2 (en) * | 2003-05-09 | 2009-09-15 | Aol Llc | Managing electronic messages |
US7882360B2 (en) * | 2003-12-19 | 2011-02-01 | Aol Inc. | Community messaging lists for authorization to deliver electronic messages |
US7242927B2 (en) | 2004-08-25 | 2007-07-10 | Scenera Technologies, Llc | Establishing special relationships between mobile devices |
US7808980B2 (en) * | 2005-02-07 | 2010-10-05 | Avaya Inc. | Integrated multi-media communication system |
US20060177011A1 (en) * | 2005-02-07 | 2006-08-10 | Jens Skakkebaek | System and method for providing code on voicemail appliance |
US8059793B2 (en) | 2005-02-07 | 2011-11-15 | Avaya Inc. | System and method for voicemail privacy |
US8559605B2 (en) | 2005-02-07 | 2013-10-15 | Avaya Inc. | Extensible diagnostic tool |
US7321655B2 (en) * | 2005-02-07 | 2008-01-22 | Adomo, Inc. | Caching user information in an integrated communication system |
US8233594B2 (en) | 2005-02-07 | 2012-07-31 | Avaya Inc. | Caching message information in an integrated communication system |
US7330537B2 (en) | 2005-02-07 | 2008-02-12 | Adomo, Inc. | Integrating messaging server directory service with a communication system voice mail message interface |
US20060177024A1 (en) * | 2005-02-07 | 2006-08-10 | Heine Frifeldt | Integrated voice mail user/email system user setup in integrated multi-media communication system |
US7346150B2 (en) * | 2005-02-07 | 2008-03-18 | Adomo, Inc. | Controlling messaging actions using form-based user interface |
US7564954B2 (en) * | 2005-02-07 | 2009-07-21 | Adomo, Inc. | Form-based user interface for controlling messaging |
US8175233B2 (en) | 2005-02-07 | 2012-05-08 | Avaya Inc. | Distributed cache system |
US7724880B2 (en) | 2005-02-07 | 2010-05-25 | Avaya Inc. | Networked voicemail |
US7650383B2 (en) * | 2005-03-15 | 2010-01-19 | Aol Llc | Electronic message system with federation of trusted senders |
US7647381B2 (en) * | 2005-04-04 | 2010-01-12 | Aol Llc | Federated challenge credit system |
US7571228B2 (en) * | 2005-04-22 | 2009-08-04 | Microsoft Corporation | Contact management in a serverless peer-to-peer system |
US8036140B2 (en) * | 2005-04-22 | 2011-10-11 | Microsoft Corporation | Application programming interface for inviting participants in a serverless peer to peer network |
US9065727B1 (en) | 2012-08-31 | 2015-06-23 | Google Inc. | Device identifier similarity models derived from online event signals |
US7761226B1 (en) * | 2005-07-27 | 2010-07-20 | The United States Of America As Represented By The Secretary Of The Navy | Interactive pedestrian routing system |
US20070088793A1 (en) * | 2005-10-17 | 2007-04-19 | Landsman Richard A | Filter for instant messaging |
US7764701B1 (en) | 2006-02-22 | 2010-07-27 | Qurio Holdings, Inc. | Methods, systems, and products for classifying peer systems |
US7779004B1 (en) | 2006-02-22 | 2010-08-17 | Qurio Holdings, Inc. | Methods, systems, and products for characterizing target systems |
US8495147B1 (en) * | 2006-07-13 | 2013-07-23 | Avaya Inc. | Threading of mixed media |
US7873988B1 (en) | 2006-09-06 | 2011-01-18 | Qurio Holdings, Inc. | System and method for rights propagation and license management in conjunction with distribution of digital content in a social network |
US7992171B2 (en) | 2006-09-06 | 2011-08-02 | Qurio Holdings, Inc. | System and method for controlled viral distribution of digital content in a social network |
US7801971B1 (en) | 2006-09-26 | 2010-09-21 | Qurio Holdings, Inc. | Systems and methods for discovering, creating, using, and managing social network circuits |
US7925592B1 (en) | 2006-09-27 | 2011-04-12 | Qurio Holdings, Inc. | System and method of using a proxy server to manage lazy content distribution in a social network |
US8214208B2 (en) * | 2006-09-28 | 2012-07-03 | Reqall, Inc. | Method and system for sharing portable voice profiles |
US7782866B1 (en) | 2006-09-29 | 2010-08-24 | Qurio Holdings, Inc. | Virtual peer in a peer-to-peer network |
US8554827B2 (en) | 2006-09-29 | 2013-10-08 | Qurio Holdings, Inc. | Virtual peer for a content sharing system |
US7886334B1 (en) * | 2006-12-11 | 2011-02-08 | Qurio Holdings, Inc. | System and method for social network trust assessment |
US8346864B1 (en) | 2006-12-13 | 2013-01-01 | Qurio Holdings, Inc. | Systems and methods for social network based conferencing |
US7698380B1 (en) | 2006-12-14 | 2010-04-13 | Qurio Holdings, Inc. | System and method of optimizing social networks and user levels based on prior network interactions |
US7730216B1 (en) | 2006-12-14 | 2010-06-01 | Qurio Holdings, Inc. | System and method of sharing content among multiple social network nodes using an aggregation node |
US9195996B1 (en) | 2006-12-27 | 2015-11-24 | Qurio Holdings, Inc. | System and method for classification of communication sessions in a social network |
FI20070044A (en) * | 2007-01-18 | 2008-08-25 | Software Cellular Network Ltd | Communication facilitating arrangement in the communication system |
US8064576B2 (en) | 2007-02-21 | 2011-11-22 | Avaya Inc. | Voicemail filtering and transcription |
US8160212B2 (en) | 2007-02-21 | 2012-04-17 | Avaya Inc. | Voicemail filtering and transcription |
US8107598B2 (en) | 2007-02-21 | 2012-01-31 | Avaya Inc. | Voicemail filtering and transcription |
US8156098B1 (en) * | 2007-04-29 | 2012-04-10 | Aol Inc. | Generating and implementing A-lists to manage user relationships |
US8488751B2 (en) | 2007-05-11 | 2013-07-16 | Avaya Inc. | Unified messenging system and method |
WO2008144412A2 (en) * | 2007-05-15 | 2008-11-27 | Social Project, Inc. | System and method for creating a social-networking online community |
US8819132B2 (en) * | 2009-05-27 | 2014-08-26 | Microsoft Corporation | Real-time directory groups |
US8301581B2 (en) * | 2009-09-24 | 2012-10-30 | Avaya Inc. | Group compositing algorithms for presence |
US9595013B2 (en) * | 2009-12-10 | 2017-03-14 | Equinix, Inc. | Delegated and restricted asset-based permissions management for co-location facilities |
US8484366B2 (en) * | 2010-01-05 | 2013-07-09 | Accenture Global Services Limited | Hierarchical service management |
US9253630B2 (en) | 2011-06-02 | 2016-02-02 | Truphone Limited | Identity management for mobile devices |
US9603006B2 (en) | 2011-09-19 | 2017-03-21 | Truphone Limited | Managing mobile device identities |
US9053185B1 (en) | 2012-04-30 | 2015-06-09 | Google Inc. | Generating a representative model for a plurality of models identified by similar feature data |
US8914500B1 (en) * | 2012-05-21 | 2014-12-16 | Google Inc. | Creating a classifier model to determine whether a network user should be added to a list |
US8886575B1 (en) | 2012-06-27 | 2014-11-11 | Google Inc. | Selecting an algorithm for identifying similar user identifiers based on predicted click-through-rate |
US8874589B1 (en) | 2012-07-16 | 2014-10-28 | Google Inc. | Adjust similar users identification based on performance feedback |
US8782197B1 (en) | 2012-07-17 | 2014-07-15 | Google, Inc. | Determining a model refresh rate |
US8886799B1 (en) | 2012-08-29 | 2014-11-11 | Google Inc. | Identifying a similar user identifier |
WO2016032518A1 (en) * | 2014-08-29 | 2016-03-03 | Hewlett Packard Enterprise Development Lp | Multiplexing network connections |
JP6772184B2 (en) * | 2015-04-29 | 2020-10-21 | コーニンクレッカ フィリップス エヌ ヴェKoninklijke Philips N.V. | How and equipment to operate the device by the members of the group |
US20180181762A1 (en) * | 2016-12-28 | 2018-06-28 | Intel Corporation | Techniques for persistent firmware transfer monitoring |
Citations (50)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5276901A (en) * | 1991-12-16 | 1994-01-04 | International Business Machines Corporation | System for controlling group access to objects using group access control folder and group identification as individual user |
US5721906A (en) * | 1994-03-24 | 1998-02-24 | Ncr Corporation | Multiple repositories of computer resources, transparent to user |
US5761669A (en) * | 1995-06-06 | 1998-06-02 | Microsoft Corporation | Controlling access to objects on multiple operating systems |
US5793365A (en) * | 1996-01-02 | 1998-08-11 | Sun Microsystems, Inc. | System and method providing a computer user interface enabling access to distributed workgroup members |
US5884172A (en) * | 1995-05-31 | 1999-03-16 | Telefonaktiebolaget L M Ericsson (Publ) | Local control enhancement in a telecommunications systems |
US5926816A (en) * | 1996-10-09 | 1999-07-20 | Oracle Corporation | Database Synchronizer |
US5941947A (en) * | 1995-08-18 | 1999-08-24 | Microsoft Corporation | System and method for controlling access to data entities in a computer network |
US6085191A (en) * | 1997-10-31 | 2000-07-04 | Sun Microsystems, Inc. | System and method for providing database access control in a secure distributed network |
US6182142B1 (en) * | 1998-07-10 | 2001-01-30 | Encommerce, Inc. | Distributed access management of information resources |
US6189036B1 (en) * | 1998-11-05 | 2001-02-13 | International Business Machines Corporation | User access to objects in group based access control based on result of greatest common divisor of assigned unique prime numbers of user and object |
US6192361B1 (en) * | 1997-12-23 | 2001-02-20 | Alcatel Usa Sourcing, L.P. | Full group privileges access system providing user access security protection for a telecommunications switching system |
US6233618B1 (en) * | 1998-03-31 | 2001-05-15 | Content Advisor, Inc. | Access control of networked data |
US6236996B1 (en) * | 1997-10-31 | 2001-05-22 | Sun Microsystems, Inc. | System and method for restricting database access to managed object information using a permissions table that specifies access rights to the managed objects |
US6275825B1 (en) * | 1997-12-29 | 2001-08-14 | Casio Computer Co., Ltd. | Data access control apparatus for limiting data access in accordance with user attribute |
US6311205B1 (en) * | 1998-10-19 | 2001-10-30 | International Business Machines Corporation | Persistent user groups on servers managed by central servers |
US20020035605A1 (en) * | 2000-01-26 | 2002-03-21 | Mcdowell Mark | Use of presence and location information concerning wireless subscribers for instant messaging and mobile commerce |
US6366915B1 (en) * | 1998-11-04 | 2002-04-02 | Micron Technology, Inc. | Method and system for efficiently retrieving information from multiple databases |
US6381579B1 (en) * | 1998-12-23 | 2002-04-30 | International Business Machines Corporation | System and method to provide secure navigation to resources on the internet |
US20020069247A1 (en) * | 2000-06-14 | 2002-06-06 | Daryoush Paknad | Business network platform method and system |
US6405035B1 (en) * | 2000-08-24 | 2002-06-11 | Telefonaktiebolaget L.M. Ericsson | System and method for forwarding messages to a subscriber device |
US6405202B1 (en) * | 1998-04-27 | 2002-06-11 | Trident Systems, Inc. | System and method for adding property level security to an object oriented database |
US6408336B1 (en) * | 1997-03-10 | 2002-06-18 | David S. Schneider | Distributed administration of access to information |
US20020083134A1 (en) * | 2000-12-22 | 2002-06-27 | Bauer Kirk Wayne | Method and system of collaborative browsing |
US6415318B1 (en) * | 1997-04-04 | 2002-07-02 | Microsoft Corporation | Inter-enterprise messaging system using bridgehead servers |
US20020087678A1 (en) * | 2000-10-27 | 2002-07-04 | Gabriel Padilla | Intelligent management of information in a network environment |
US20020087704A1 (en) * | 2000-11-30 | 2002-07-04 | Pascal Chesnais | Systems and methods for routing messages to communications devices over a communications network |
US20020102965A1 (en) * | 2001-01-26 | 2002-08-01 | Michael Mandahl | Wireless information exchange and management system and method |
US20020112054A1 (en) * | 2001-02-12 | 2002-08-15 | International Business Machines Corporation | Method and system for automated session resource clean-up in a distributed client-server environment |
US20020118809A1 (en) * | 2000-12-01 | 2002-08-29 | Alfred Eisenberg | Initiation and support of video conferencing using instant messaging |
US6453353B1 (en) * | 1998-07-10 | 2002-09-17 | Entrust, Inc. | Role-based navigation of information resources |
US20020130904A1 (en) * | 2001-03-19 | 2002-09-19 | Michael Becker | Method, apparatus and computer readable medium for multiple messaging session management with a graphical user interfacse |
US6487667B1 (en) * | 1996-06-03 | 2002-11-26 | Gary S. Brown | System for remote pass-phrase authentication |
US20020184357A1 (en) * | 2001-01-22 | 2002-12-05 | Traversat Bernard A. | Rendezvous for locating peer-to-peer resources |
US6510466B1 (en) * | 1998-12-14 | 2003-01-21 | International Business Machines Corporation | Methods, systems and computer program products for centralized management of application programs on a network |
US20030018726A1 (en) * | 2001-04-27 | 2003-01-23 | Low Sydney Gordon | Instant messaging |
US20030023476A1 (en) * | 2001-06-29 | 2003-01-30 | Incidentreports, Inc. | System and method for recording and using incident report data |
US20030041154A1 (en) * | 2001-08-24 | 2003-02-27 | Tran Trung M. | System and method for controlling UNIX group access using LDAP |
US20030041000A1 (en) * | 2000-12-18 | 2003-02-27 | Paul Zajac | System and method for providing a graphical user interface for a multi-interface financial transaction system |
US20030065721A1 (en) * | 2001-09-28 | 2003-04-03 | Roskind James A. | Passive personalization of buddy lists |
US6564261B1 (en) * | 1999-05-10 | 2003-05-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Distributed system to intelligently establish sessions between anonymous users over various networks |
US6601009B2 (en) * | 2001-07-12 | 2003-07-29 | Yahoo Inc | Method and system of automatic bandwidth detection |
US20040003132A1 (en) * | 2000-12-06 | 2004-01-01 | Biosentients, Inc. | Data pool architecture, system, and method for intelligent object data in heterogeneous data environments |
US6677968B1 (en) * | 1997-02-24 | 2004-01-13 | America Online, Inc. | User definable on-line co-user lists |
US6820082B1 (en) * | 2000-04-03 | 2004-11-16 | Allegis Corporation | Rule based database security system and method |
US6870830B1 (en) * | 2000-11-30 | 2005-03-22 | 3Com Corporation | System and method for performing messaging services using a data communications channel in a data network telephone system |
US6874061B1 (en) * | 1998-10-23 | 2005-03-29 | Oracle International Corporation | Method and system for implementing variable sized extents |
US6935951B2 (en) * | 2001-09-04 | 2005-08-30 | Igt | Electronic signature capability in a gaming machine |
US7016978B2 (en) * | 2002-04-29 | 2006-03-21 | Bellsouth Intellectual Property Corporation | Instant messaging architecture and system for interoperability and presence management |
US7136858B2 (en) * | 2002-05-21 | 2006-11-14 | Bellsouth Intellectual Property Corporation | Network update manager |
US7263535B2 (en) * | 2002-05-21 | 2007-08-28 | Bellsouth Intellectual Property Corporation | Resource list management system |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5991807A (en) * | 1996-06-24 | 1999-11-23 | Nortel Networks Corporation | System for controlling users access to a distributive network in accordance with constraints present in common access distributive network interface separate from a server |
US6697806B1 (en) * | 2000-04-24 | 2004-02-24 | Sprint Communications Company, L.P. | Access network authorization |
US20050210263A1 (en) | 2001-04-25 | 2005-09-22 | Levas Robert G | Electronic form routing and data capture system and method |
AUPR513301A0 (en) | 2001-05-21 | 2001-06-14 | Kwei, David Wah Hao | System and method for pooled electronic purchasing |
US20050021467A1 (en) | 2001-09-07 | 2005-01-27 | Robert Franzdonk | Distributed digital rights network (drn), and methods to access operate and implement the same |
US7774273B2 (en) | 2002-07-30 | 2010-08-10 | Acs State & Local Solutions, Inc. | Systems and methods for processing benefits |
US20040093595A1 (en) | 2002-08-08 | 2004-05-13 | Eric Bilange | Software application framework for network-connected devices |
US8340979B2 (en) | 2002-10-01 | 2012-12-25 | Acs State & Local Solutions, Inc. | Systems and methods for electronically processing government sponsored benefits |
US7457807B2 (en) | 2004-01-08 | 2008-11-25 | Oco I, Inc. | Data migration and analysis |
-
2002
- 2002-08-13 US US10/217,916 patent/US7346696B2/en not_active Expired - Fee Related
-
2003
- 2003-05-20 WO PCT/US2003/016097 patent/WO2003100646A1/en not_active Application Discontinuation
- 2003-05-20 AU AU2003243291A patent/AU2003243291A1/en not_active Abandoned
-
2008
- 2008-03-18 US US12/050,673 patent/US20080168566A1/en not_active Abandoned
Patent Citations (52)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5276901A (en) * | 1991-12-16 | 1994-01-04 | International Business Machines Corporation | System for controlling group access to objects using group access control folder and group identification as individual user |
US5721906A (en) * | 1994-03-24 | 1998-02-24 | Ncr Corporation | Multiple repositories of computer resources, transparent to user |
US5884172A (en) * | 1995-05-31 | 1999-03-16 | Telefonaktiebolaget L M Ericsson (Publ) | Local control enhancement in a telecommunications systems |
US5761669A (en) * | 1995-06-06 | 1998-06-02 | Microsoft Corporation | Controlling access to objects on multiple operating systems |
US5941947A (en) * | 1995-08-18 | 1999-08-24 | Microsoft Corporation | System and method for controlling access to data entities in a computer network |
US5793365A (en) * | 1996-01-02 | 1998-08-11 | Sun Microsystems, Inc. | System and method providing a computer user interface enabling access to distributed workgroup members |
US6487667B1 (en) * | 1996-06-03 | 2002-11-26 | Gary S. Brown | System for remote pass-phrase authentication |
US5926816A (en) * | 1996-10-09 | 1999-07-20 | Oracle Corporation | Database Synchronizer |
US6677968B1 (en) * | 1997-02-24 | 2004-01-13 | America Online, Inc. | User definable on-line co-user lists |
US6785728B1 (en) * | 1997-03-10 | 2004-08-31 | David S. Schneider | Distributed administration of access to information |
US6408336B1 (en) * | 1997-03-10 | 2002-06-18 | David S. Schneider | Distributed administration of access to information |
US6604133B2 (en) * | 1997-04-04 | 2003-08-05 | Microsoft Corporation | Inter-enterprise messaging system using bridgehead servers |
US6415318B1 (en) * | 1997-04-04 | 2002-07-02 | Microsoft Corporation | Inter-enterprise messaging system using bridgehead servers |
US6236996B1 (en) * | 1997-10-31 | 2001-05-22 | Sun Microsystems, Inc. | System and method for restricting database access to managed object information using a permissions table that specifies access rights to the managed objects |
US6085191A (en) * | 1997-10-31 | 2000-07-04 | Sun Microsystems, Inc. | System and method for providing database access control in a secure distributed network |
US6192361B1 (en) * | 1997-12-23 | 2001-02-20 | Alcatel Usa Sourcing, L.P. | Full group privileges access system providing user access security protection for a telecommunications switching system |
US6275825B1 (en) * | 1997-12-29 | 2001-08-14 | Casio Computer Co., Ltd. | Data access control apparatus for limiting data access in accordance with user attribute |
US6233618B1 (en) * | 1998-03-31 | 2001-05-15 | Content Advisor, Inc. | Access control of networked data |
US6405202B1 (en) * | 1998-04-27 | 2002-06-11 | Trident Systems, Inc. | System and method for adding property level security to an object oriented database |
US6453353B1 (en) * | 1998-07-10 | 2002-09-17 | Entrust, Inc. | Role-based navigation of information resources |
US6182142B1 (en) * | 1998-07-10 | 2001-01-30 | Encommerce, Inc. | Distributed access management of information resources |
US6311205B1 (en) * | 1998-10-19 | 2001-10-30 | International Business Machines Corporation | Persistent user groups on servers managed by central servers |
US6874061B1 (en) * | 1998-10-23 | 2005-03-29 | Oracle International Corporation | Method and system for implementing variable sized extents |
US6366915B1 (en) * | 1998-11-04 | 2002-04-02 | Micron Technology, Inc. | Method and system for efficiently retrieving information from multiple databases |
US6189036B1 (en) * | 1998-11-05 | 2001-02-13 | International Business Machines Corporation | User access to objects in group based access control based on result of greatest common divisor of assigned unique prime numbers of user and object |
US6510466B1 (en) * | 1998-12-14 | 2003-01-21 | International Business Machines Corporation | Methods, systems and computer program products for centralized management of application programs on a network |
US6381579B1 (en) * | 1998-12-23 | 2002-04-30 | International Business Machines Corporation | System and method to provide secure navigation to resources on the internet |
US6564261B1 (en) * | 1999-05-10 | 2003-05-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Distributed system to intelligently establish sessions between anonymous users over various networks |
US20020035605A1 (en) * | 2000-01-26 | 2002-03-21 | Mcdowell Mark | Use of presence and location information concerning wireless subscribers for instant messaging and mobile commerce |
US6820082B1 (en) * | 2000-04-03 | 2004-11-16 | Allegis Corporation | Rule based database security system and method |
US20020069247A1 (en) * | 2000-06-14 | 2002-06-06 | Daryoush Paknad | Business network platform method and system |
US6405035B1 (en) * | 2000-08-24 | 2002-06-11 | Telefonaktiebolaget L.M. Ericsson | System and method for forwarding messages to a subscriber device |
US20020087678A1 (en) * | 2000-10-27 | 2002-07-04 | Gabriel Padilla | Intelligent management of information in a network environment |
US6870830B1 (en) * | 2000-11-30 | 2005-03-22 | 3Com Corporation | System and method for performing messaging services using a data communications channel in a data network telephone system |
US20020087704A1 (en) * | 2000-11-30 | 2002-07-04 | Pascal Chesnais | Systems and methods for routing messages to communications devices over a communications network |
US20020118809A1 (en) * | 2000-12-01 | 2002-08-29 | Alfred Eisenberg | Initiation and support of video conferencing using instant messaging |
US20040003132A1 (en) * | 2000-12-06 | 2004-01-01 | Biosentients, Inc. | Data pool architecture, system, and method for intelligent object data in heterogeneous data environments |
US20030041000A1 (en) * | 2000-12-18 | 2003-02-27 | Paul Zajac | System and method for providing a graphical user interface for a multi-interface financial transaction system |
US20020083134A1 (en) * | 2000-12-22 | 2002-06-27 | Bauer Kirk Wayne | Method and system of collaborative browsing |
US20020184357A1 (en) * | 2001-01-22 | 2002-12-05 | Traversat Bernard A. | Rendezvous for locating peer-to-peer resources |
US20020102965A1 (en) * | 2001-01-26 | 2002-08-01 | Michael Mandahl | Wireless information exchange and management system and method |
US20020112054A1 (en) * | 2001-02-12 | 2002-08-15 | International Business Machines Corporation | Method and system for automated session resource clean-up in a distributed client-server environment |
US20020130904A1 (en) * | 2001-03-19 | 2002-09-19 | Michael Becker | Method, apparatus and computer readable medium for multiple messaging session management with a graphical user interfacse |
US20030018726A1 (en) * | 2001-04-27 | 2003-01-23 | Low Sydney Gordon | Instant messaging |
US20030023476A1 (en) * | 2001-06-29 | 2003-01-30 | Incidentreports, Inc. | System and method for recording and using incident report data |
US6601009B2 (en) * | 2001-07-12 | 2003-07-29 | Yahoo Inc | Method and system of automatic bandwidth detection |
US20030041154A1 (en) * | 2001-08-24 | 2003-02-27 | Tran Trung M. | System and method for controlling UNIX group access using LDAP |
US6935951B2 (en) * | 2001-09-04 | 2005-08-30 | Igt | Electronic signature capability in a gaming machine |
US20030065721A1 (en) * | 2001-09-28 | 2003-04-03 | Roskind James A. | Passive personalization of buddy lists |
US7016978B2 (en) * | 2002-04-29 | 2006-03-21 | Bellsouth Intellectual Property Corporation | Instant messaging architecture and system for interoperability and presence management |
US7136858B2 (en) * | 2002-05-21 | 2006-11-14 | Bellsouth Intellectual Property Corporation | Network update manager |
US7263535B2 (en) * | 2002-05-21 | 2007-08-28 | Bellsouth Intellectual Property Corporation | Resource list management system |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8166110B2 (en) | 2002-05-21 | 2012-04-24 | At&T Intellectual Property I, L.P. | Resource list management system |
US20110022671A1 (en) * | 2002-05-21 | 2011-01-27 | Malik Dale W | Resource List Management System |
US7831664B2 (en) | 2002-05-21 | 2010-11-09 | At&T Intellectual Property I, Lp | Resource list management system |
US20040003084A1 (en) * | 2002-05-21 | 2004-01-01 | Malik Dale W. | Network resource management system |
US7536392B2 (en) | 2002-05-21 | 2009-05-19 | At&T Intelllectual Property I, L.P. | Network update manager |
US20070288573A1 (en) * | 2002-05-21 | 2007-12-13 | At&T Bls Intellectual Property, Inc. | Resource List Management System |
US20070088759A1 (en) * | 2002-05-21 | 2007-04-19 | Bellsouth Intellectual Property Corporation | Network Update Manager |
US20070162555A1 (en) * | 2005-11-18 | 2007-07-12 | Aol Llc | Promoting interoperability of presence-based systems through the use of ubiquitous online identities |
US8396922B2 (en) | 2005-11-18 | 2013-03-12 | Aol Inc. | Promoting interoperability of presence-based systems through the use of ubiquitous online identities |
US20070162600A1 (en) * | 2005-11-18 | 2007-07-12 | Aol Llc | Promoting interoperability of presence-based systems through the use of ubiquitous online identities |
US20070156827A1 (en) * | 2005-11-18 | 2007-07-05 | Aol Llc | Promoting interoperability of presence-based systems through the use of ubiquitous online identities |
US8996620B2 (en) * | 2005-11-18 | 2015-03-31 | Aol Inc. | Promoting interoperability of presence-based systems through the use of ubiquitous online identities |
US9392069B2 (en) | 2005-11-18 | 2016-07-12 | Aol Inc. | Promoting interoperability of presence-based systems through the use of ubiquitous online identities |
US9825889B2 (en) | 2005-11-18 | 2017-11-21 | Oath Inc. | Presence-based systems and methods using electronic messaging activity data |
Also Published As
Publication number | Publication date |
---|---|
US7346696B2 (en) | 2008-03-18 |
US20030220975A1 (en) | 2003-11-27 |
AU2003243291A1 (en) | 2003-12-12 |
WO2003100646A1 (en) | 2003-12-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7346696B2 (en) | Group access management system | |
US8166110B2 (en) | Resource list management system | |
US7096255B2 (en) | System and method for providing a roster list of temporary contacts having expiration periods designated by a user in an instant messaging environment | |
US7536392B2 (en) | Network update manager | |
US7447756B2 (en) | Temporary aliasing for resource list | |
US20040003084A1 (en) | Network resource management system | |
JP4444518B2 (en) | A distributed system that establishes intelligent sessions between anonymous users over various networks | |
US9077738B1 (en) | Systems and methods for setting up a collaborative communication system | |
US7159125B2 (en) | Policy engine for modular generation of policy for a flat, per-device database | |
US20060259958A1 (en) | Method and system using presence information to manage network access | |
US7181490B1 (en) | Method and apparatus for mapping network events to names of network devices | |
US20020194295A1 (en) | Scalable data-sharing architecture | |
CN116633775B (en) | Container communication method and system of multi-container network interface | |
US8826026B2 (en) | Systems and methods for tracking electronic files in computer networks using electronic signatures | |
US20060168553A1 (en) | Software development kit for real-time communication applications and system | |
JP2001111756A (en) | Network facsimile system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: BELLSOUTH INTELLECTUAL PROPERTY CORPORATION, DELAWARE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MALIK, DALE W.;REEL/FRAME:056688/0311 Effective date: 20020812 Owner name: AT&T INTELLECTUAL PROPERTY I, L.P., GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AT&T DELAWARE INTELLECTUAL PROPERTY, INC.;REEL/FRAME:056693/0671 Effective date: 20210623 Owner name: AT&T INTELLECTUAL PROPERTY, INC., TEXAS Free format text: CHANGE OF NAME;ASSIGNOR:BELLSOUTH INTELLECTUAL PROPERTY CORPORATION;REEL/FRAME:056700/0904 Effective date: 20070427 Owner name: AT&T BLS INTELLECTUAL PROPERTY, INC., DELAWARE Free format text: CHANGE OF NAME;ASSIGNOR:AT&T INTELLECTUAL PROPERTY, INC.;REEL/FRAME:056701/0006 Effective date: 20070727 Owner name: AT&T DELAWARE INTELLECTUAL PROPERTY, INC., DELAWARE Free format text: CHANGE OF NAME;ASSIGNOR:AT&T BLS INTELLECTUAL PROPERTY, INC.;REEL/FRAME:056701/0059 Effective date: 20071101 |
|
AS | Assignment |
Owner name: ATLASSIAN INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AT&T INTELLECTUAL PROPERTY I, L.P.;REEL/FRAME:057156/0587 Effective date: 20210629 |
|
AS | Assignment |
Owner name: ATLASSIAN US, INC., CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:ATLASSIAN, INC.;REEL/FRAME:061085/0690 Effective date: 20220701 |