Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q10/00—Administration; Management
  • G06Q10/10—Office automation; Time management
  • G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
  • H04L51/21—Monitoring or handling of messages
  • H04L51/212—Monitoring or handling of messages using filtering or selective blocking

Definitions

• the disclosure generally relates to the online management of electronic mailing lists, and more specifically, to automatic email message moderation for mailing lists.
• Electronic mailing lists allow users to distribute email messages to a large number of subscribers of the mailing lists. Typically, one creates a mailing list by adding or inviting subscribers and becomes the owner and manager of that mailing list.
• a mailing list Once a mailing list is created, it becomes an on-line forum that can be used to share ideas and facilitate discussion.
• members of mailing lists are able to easily send messages to other members of the mailing list in order to communicate with one another. Consequently, ill-intended users can take advantage of this freedom and send unwanted or offensive messages to the entire mailing list. Additionally, careless users can send messages not appropriate for distribution.
• Moderation of the mailing list is an important aspect of managing the list, and ensures that the list remains as effective in achieving its purpose as possible. Therefore, a need remains for a system to facilitate the moderation and general management of mailing lists by regular users who are not trained list administrators and who do not have a great deal of time to devote to list management. A need also remains for an organization-specific mail list system that is both easy to use and ensures security of information disseminated using the system.
• Email messages in a mailing list are monitored, filtered, or queued for moderation based on predetermined characteristics of the message. Messages queued for moderation are presented to a manager of the mailing list for approval and distribution or rejection. Alternatively, an automatic decision is made to approve or reject the message based on the predetermined characteristics.
• the predetermined characteristics include: the size of the mailing list; the size of the email message; the existence of specified words (such as "confidential" or a product trademark indicative of spam) within the message; no subject line; the sender has sent too many messages already; and the email address matches a predetermined list.
• One embodiment includes a moderation system for a mailing list.
• the system includes a first computing subsystem adapted to receive a message from a client. The message is addressed to a plurality of addresses belonging to the mailing list.
• the system also includes a second computing subystem adapted to communicate with the first computing subsystem.
• the second computer subsystem is configured to examine a portion of the message and determine whether the portion passes a predetermined test.
• the system further includes a third computing subsystem adapted to communicate with the second computing system.
• the third computing system is adapted to mark the email message for processing. In one embodiment, the processing includes marking the message for moderation, and in other embodiments, the processing includes deleting the message.
• Another embodiment includes a computer-implemented method for moderating a mailing list.
• the method includes receiving, by a first computing subsystem, an email message from a client wherein the message is addressed to a plurality of email addresses belonging to the mailing list.
• the method also includes examining, by a second computing subsystem, a portion of the email message and determining, by the second computing subsystem, whether the portion passes a predetermined test.
• the method further includes marking, by a third computing subsystem, the email message for processing.
• the processing includes marking the message for moderation, and in other embodiments, the processing includes deleting the message.
• FIG. 1 is a block diagram illustrating a system for automatic message moderation for mailing lists in accordance with one embodiment.
• FIG. 2 is a block diagram illustrating a client device in accordance with one embodiment.
• FIG. 3 is a block diagram illustrating a membership engine in accordance with one embodiment.
• FIG. 4 is a block diagram illustrating a message moderation server in accordance with one embodiment.
• FIG. 5 is a flow diagram illustrating a process for message moderation in accordance with one embodiment.
• FIG. 6 is a flow diagram illustrating a process for message analysis in accordance with one embodiment.
• FIG. 7 is an exemplary screenshot of a user interface for mailing list management in accordance with one embodiment.
• FIG. 8 is an exemplary screenshot of a user profile in accordance with one embodiment.
• FIG. 1 is a block diagram illustrating a system 100 for automatic message moderation for mailing lists in accordance with one embodiment.
• the system 100 facilitates the online management of subscribers to a mailing list and also facilitates the distribution of email messages to the subscribers of the mailing lists.
• the system 100 includes one or more client devices 110, a network 140 and a mailing list management server 120.
• the mailing list management server 120 includes a front end server 122, a membership engine 124, an email delivery engine 125, a permissions library 126, an email archive engine 128, and a message moderation engine 129.
• Many conventional features, such as firewalls, load balancers, application servers, failover servers, site management tools, and so forth are not shown so as not to obscure the features of the system.
• the functionality attributed to a particular server, engine or module can be performed by different or multiple servers, engines or modules operating together.
• Each of the various servers is implemented as server program executing on server- class computer comprising a CPU, memory, network interface, peripheral interfaces, and other well known components.
• the computers themselves preferably run an open-source operating system such as LINUX, have generally high performance CPUs, IGB or more of memory, and 100 GB or more of disk storage.
• LINUX open-source operating system
• other types of computers can be used, and it is expected that as more powerful computers are developed in the future, they can be configured in accordance with the teachings here.
• the functionality implemented by any of the elements can be provided from computer program products that are stored in tangible computer accessible storage mediums (e.g., RAM, hard disk, or optical/magnetic media).
• a client 110 executes a browser 112 and connects to the front end server 122 via the network 140, which is typically the Internet, but may also be any network, including but not limited to any combination of a LAN, a MAN, a WAN, a mobile, wired or wireless network, a private network, or a virtual private network. While only a single client 110 and browser 112 are shown, it is understood that very large numbers (e.g., millions) of clients are supported and can be in communication with the system 100 at any time. In one embodiment, the browser 112 is used to access a website for management of mailing lists.
• the network 140 enables communications between the client 110 and the mailing list management server 120.
• the network 140 uses standard communications technologies and/or protocols.
• the network 140 includes links using technologies such as Ethernet, 802.11, integrated services digital network (ISDN), digital subscriber line (DSL), asynchronous transfer mode (ATM), InfiniBand, PCI Express Advanced Switching, etc.
• the networking protocols used on the network 140 include in various embodiments multiprotocol label switching (MPLS), the transmission control protocol/Internet protocol (TCP/IP), the User Datagram Protocol (UDP), the hypertext transport protocol (HTTP), the simple mail transfer protocol (SMTP), the file transfer protocol (FTP), etc.
• MPLS multiprotocol label switching
• TCP/IP transmission control protocol/Internet protocol
• UDP User Datagram Protocol
• HTTP hypertext transport protocol
• HTTP simple mail transfer protocol
• FTP file transfer protocol
• the data exchanged over the network 140 is represented using conventional technologies and/or formats including the hypertext markup language (HTML), the extensible markup language (XML), etc.
• all or some of links in some embodiments are encrypted using conventional encryption technologies such as the secure sockets layer (SSL), Secure HTTP and/or virtual private networks (VPNs) or Internet Protocol security (IPsec).
• SSL secure sockets layer
• VPNs virtual private networks
• IPsec Internet Protocol security
• the entities use custom and/or dedicated data communications technologies instead of, or in
• the front end server 122 provides a user interface for mailing list management as well as message viewing and composing.
• the front end server 122 is adapted to communicate with clients 110 via the network 140 and is also adapted to communicate with the membership engine 124, email delivery engine 125 and message moderation engine 129.
• the front end server 122 receives composed messages and other mailing list task requests from clients 110 and communicates with the membership engine 124, email delivery engine
• the front end server 122 facilitates convenient management and modification of mailing lists by providing a user interface for mailing list administration.
• the front end server 122 is adapted to communicate with the membership engine 124 in order to retrieve membership information to be displayed on the user interface.
• the user interface is displayed on the web browser 112 of the client 110 and users can easily access membership information, as well as other information related to the mailing list, via the user interface.
• An exemplary screenshot of the user interface is shown in FIG. 7, the description of which is provided in further detail below.
• the membership engine 124 stores membership information for various mailing lists.
• the membership engine 124 is coupled for communication with the permissions library
• the membership engine 124 includes a permissions retrieval module 302 for retrieving permissions information form the permissions library 126 and a membership database 304 for storing membership information.
• Membership information for various mailing lists includes email addresses of users belonging to the mailing list.
• membership information includes a name and/or other identifying information associated with each email address.
• membership information also includes permission levels, mailing list associations, an employee title, email delivery preferences, a membership date, and a membership type associated with each user.
• the membership engine 124 also stores identifying information associated with users who have been invited to join the mailing list, but have not yet confirmed membership.
• the membership engine 124 also stores identifying information associated with users who are banned from the mailing list. In other embodiments, the membership engine 124 stores other information associated with each user, such as information associated with a user ID, the user's login information or credentials, the user's residential location, the user's email address, a username, the user's country of residence, the user's date of birth, the user's gender, identifying information of other mailing lists of which the user is a member, as well as additional information related to the particular user. In one embodiment, the membership engine 124 stores all of the aforementioned information, and in other embodiments, the membership engine stores only some of the aforementioned information.
• the email delivery engine 125 of the system 100 facilitates the sending and receiving of email messages to and from clients 110 of the system 100.
• the email delivery engine 125 is adapted for communication with the front end server 122 and the email archive engine 128.
• the email delivery engine 125 uses the Simple Mail Transfer Protocol (SMTP) to send email messages to a local mail transfer agent (MTA), typically run by a user's Internet Service Provider (ISP).
• SMTP Simple Mail Transfer Protocol
• MTA local mail transfer agent
• ISP Internet Service Provider
• the email delivery engine 125 uses another email transfer mechanism to deliver email messages to and from clients 110 in the system 100.
• the message moderation engine 129 facilitates the automatic moderation of email messages being distributed to the mailing lists.
• the message moderation engine 129 is adapted for communication with the front end server 122 and the email delivery engine 125.
• the message moderation engine 129 is adapted to receive composed email messages from the front end server 122 and route approved email messages for delivery to the email delivery engine 125.
• the message moderation engine 129 examines the content and characteristics of email messages to determine whether the email message should first be moderated by the mailing list owner before being distributed and marks the email message for later approval or rejection by the mailing list owner. More detail concerning the components and functionality of the message moderation engine 129 is provided below with reference to FIGS. 4-6.
• the permissions library 126 provides permission information to the message moderation system 100.
• the permissions library 126 is adapted to communicate with the membership engine 124 and provide permission information for members of the mailing lists.
• the permissions library 126 includes permission information for members of mailing lists.
• the permissions library 126 stores the email addresses of members of the mailing lists, and for each email address, the permissions library 126 stores the associated mailing lists and the levels of access associated with the email address for each mailing list.
• the permissions library 126 considers a group of users as an individual entity for purposes of determining and managing permissions. Thus, if a new user joins a group, that user automatically gets permissions based on membership in the group.
• the permissions library 126 also stores permission information for other applications, systems or websites with access to the permissions library 126 and acts as a central repository for permissions information for email addresses and groups stored in the permissions library 126.
• the users associated with the email addresses stored in the permissions library 126 may also be members of other systems or websites, such as those used for photo sharing, document editing and social networking.
• the permissions library 126 stores permissions information for these members of the photo sharing websites and in other embodiments, the permissions library 126 stores permissions information for the members with access to the document editing website.
• the email archive engine 128 stores email messages sent to members of the mailing lists.
• the email archive engine 128 is adapted to communicate with the email delivery engine 125, receives email messages that are sent to members of the mailing lists and sends the email messages to an email archive database 130 to be stored therein.
• the email archive engine 128 stores all email messages sent to members of the mailing list.
• the email delivery engine 125 retrieves stored email messages from the email archive engine 128, for instance in order to provide a "digest version" of all messages received in one day.
• FIG. 2 is a block diagram illustrating the main components of client 110 in accordance with one embodiment. Illustrated are at least one processor 202 coupled to a bus 204. Also coupled to the bus 204 are a memory 206, a storage device 208, a keyboard 210, a graphics adapter 212, a pointing device 214, and a network adapter 216. In one embodiment, the functionality of the bus 204 is provided by an interconnecting chipset. A display 218 is coupled to the graphics adapter 212.
• the storage device 208 is any device capable of holding data, such as a hard drive, compact disk read-only memory (CD-ROM), DVD, or solid-state memory device.
• the memory 206 holds instructions and data used by the processor 202.
• the pointing device 214 may be a mouse, track ball, or other type of pointing device, and is used in combination with the keyboard 210 to input data into the computer system 200.
• the graphics adapter 212 displays images and other information on the display 218.
• the network adapter 216 couples the computer system 200 to a local or wide area network.
• the client 110 can have different and/or other components than those shown in FIG. 2.
• the client 110 can lack certain illustrated components such as keyboard 210, pointing device 214, graphics adapter 212, and/or display 218.
• the storage device 208 can be local and/or remote from the client 110, such as embodied within a storage area network (SAN).
• client 110 is adapted to execute computer program modules for providing functionality described herein.
• module refers to computer program logic utilized to provide the specified functionality.
• a module can be implemented in hardware, firmware, and/or software.
• program modules are stored on the storage device 208, loaded into the memory 206, and executed by the processor 202.
• the message moderation engine 129 includes a message analysis module 402 and a moderated messaged module 404 and is adapted to communicate with the front end server 122 and the email delivery engine 125.
• the message moderation engine 129 receives composed email messages from the front end server 122 and analyzes the email messages via the message analysis module 402 of the message moderation engine 129.
• the analyzed email messages that are queued for moderation are stored in the moderated messages module 404 and are later routed to the email delivery engine 125 for delivery.
• FIG. 5 is a flow diagram illustrating a process 500 for message moderation in accordance with one embodiment.
• the process 500 begins when an email message is composed and sent 502 to a mailing list via the browser 112 of a client 110.
• the email message is received 504 at the front end server 122 of the mailing list management server 120.
• the message passes to the message moderation engine 129 of the mailing list management server 120 and is analyzed 506 to determine whether the message should be delivered to the intended recipients or queued for moderation.
• the email message must first be approved before the email message is delivered to the intended recipients.
• the message is analyzed 506 to determine whether the message should be delivered to the intended recipients or be automatically rejected.
• a rejected message is automatically deleted.
• a rejected message is stored in the moderated messages module 404 and not routed to the email delivery engine 125 for delivery.
• FIG. 6 is a flow diagram illustrating a process for message analysis 506 in accordance with one embodiment.
• the message analysis module 402 of the message moderation engine 129 examines various characteristics of the email message in order to determine whether the message should be queued for moderation or automatically rejected.
• the message analysis module 402 of the message moderation engine 129 examines 602 the email addresses of the sender and recipients of the email message.
• a determination 604 is made as to whether the examination of the recipients passes a predetermined test.
• the predetermined test is based on the total number of intended recipients in the mailing list who have been sent a message from this sender in a particular period of time.
• the test is not passed (604-No) and the message is sent to the moderated message module 404 and queued 510 for moderation or automatically rejected. If the total number of recipients does not exceed a predetermined number, then the test is passed (604- Yes), and the process 506 continues.
• a similar test looks to the number of members of a list and queues a message for moderation if the number of members exceeds a threshold.
• the predetermined test is based on the email address of the sender of the message.
• the email address of the sender of the message is compared to a list of email addresses that are banned from distributing messages to particular mailing lists. If the email address of the sender appears on the list, then the test is not passed (604-No) and the message is sent to the moderated message module 404 and queued 510 for moderation or automatically rejected. If the email address of the sender of the email message does not appear on the list, then the test is passed (604-Yes), and the process 506 continues.
• the message analysis module 402 of the message moderation engine 129 also examines 606 the content of the subject of the message. A determination 608 is made as to whether the examination of the subject of the email message passes a predetermined test. In one embodiment, the predetermined test is based on whether the message contains a subject. If the message does not contain a subject, then the test is not passed (608-No) and the message is sent to the moderated messages module 404 and queued 510 for moderation. If the message contains a subject, then the test is passed (608-Yes) and the process 506 continues. In another embodiment, the predetermined test is based on whether the subject of the message contains certain specified words.
• the words of the subject of the message are compared to a list of specified words and if the subject of the email message includes words in the list, then the test is not passed (608-No) and the message is sent to the moderated messages module 404 and queued 510 for moderation.
• the test is not passed (608-No) and the message is sent to the moderated messages module 404 and queued 510 for moderation.
• the message manager of the mailing list may not want the message to be distributed to the intended recipients and therefore, the message does not pass the test (608-No) and the message is sent to the moderated messages module 404 and queued 510 for moderation. If the message does not contain words in the list, the message passes the test (608-Yes) and the process 506 continues.
• the message analysis module 402 of the message moderation engine 129 also examines 610 the content of the body of the email message and attachments, if any.
• a determination 612 is made as to whether the examination of the content of the body of the email message passes a predetermined test.
• the predetermined test is based on whether the body of the message contains any content. If the body of the message contains no content, then the sender may not have intended for the email message to be sent. If the body of the email message does not contain any content, then the test is not passed (612-No) and the message is sent to the moderated messages module 404 and queued 510 for moderation. If the body of the message contains content, then the test is passed (612- Yes) and the process 506 continues.
• the predetermined test is based on whether the body of the email message contains certain specified words.
• the words of the body of the message are compared to a list of specified words and if the body of the email message includes words in the list, then the test is not passed (612-No) and the message is sent to the moderated messages module 404 and queued 510 for moderation.
• the message manager of the mailing list may not want the message to be distributed to the intended recipients and therefore, the message does not pass the test (612-No) and the message is sent to the moderated messages module 404 and queued 510 for moderation.
• the message passes the test (612- Yes) and the process 506 continues.
• the predetermined test is based on the overall size of the message (including attachments, e.g., 5 Megabytes); in alternate embodiments, a test is also made as to the number of words in the body of the email message. In such embodiments, an analysis is performed to determine whether the size of the message exceeds a predetermined threshold. If so, then the test is not passed (612-No) and the message is sent to the moderated messages module 404 and queued 510 for moderation. If the message does not exceed the predetermined threshold, then the test is passed (612-Yes) and the process 506 continues.
• an analysis is performed to determine whether the body of the email message contains many repeating words or particular patterns. Such characteristics may signal that the message is spam or nonsubstantive content. If the body of the message contains a number of repeating words or patterns greater than a predetermined threshold, then the test is not passed (612-No) and the message is sent to the moderated messages module 404 and queued 510 for moderation. If the body of the message does not contain a number of repeating words greater than a predetermined threshold, then the test is passed (612-Yes) and the process 506 continues.
• one of the aforementioned tests is performed on the email message to determine if the message should be queued 510 for moderation, automatically rejected or sent to the email delivery engine 125 for delivery to the intended recipients.
• a combination of some of the tests are performed, and in yet other embodiments, all of the tests are performed to determine if the message should be queued for moderation, automatically rejected or sent to the email delivery engine 125 for delivery to the intended recipients.
• the moderated messages module 404 creates a notification and sends the notification to the message sender via the email delivery engine 125.
• the tests provide a reasonably simply manner for queuing certain messages for moderation while allowing others to be sent without moderation, thereby reducing the burden on the person moderating the list from what would be required if all messages were submitted for moderation.
• the message is sent 508 to the email delivery engine 125 to be delivered to the intended recipients. If the message does not pass one or more of the aforementioned tests, the message is sent to the message moderation module 404 and queued 510 for moderation. [0041] Once the messages are queued for moderation, the moderated messages are examined 512 at a client B 100. If the message is approved 514, the message is routed 516 for delivery by the email delivery engine 125. In one embodiment, if the message is rejected 514, the message is automatically deleted (not shown). In another embodiment, if the message is rejected 514, the message is stored and not routed to the email deliver engine 125 for delivery.
• FIG. 7 is an exemplary screenshot of a user interface 700 for mailing list management in accordance with one embodiment.
• the user interface 700 allows mailing list managers to modify access control for the mailing list.
• the access to the mailing list is accessible to email addresses with a certain domain name.
• access to the mailing list is accessible to email addresses identified as being a part of a certain subgroup.
• option 702 is selected to limit discussion viewing access to those users with a "company.com” email address.
• option 704 is selected to limit mailing list membership viewing access to those users with a "company.com” email address.
• members are identified as belonging to a certain category.
• the category is based on employment status within a company.
• the category is based on a person's title or job description within a company.
• the category may be based on any other characteristics that can be used to distinguish a certain group of members from other members.
• option 706 is selected to limit access to users identified as "engineers” and option 708 is selected to limit access to users identified as "full time employees.”
• Mail list users in an organizational (e.g., corporate) environment differ from mail list users in the general public in a number of ways.
• corporations create many more functional groupings of personnel than people create in their personal lives. Accordingly, corporate mail users may expect to be in a larger number of groups than users of a public mailing list.
• groups may be used to increase mailing list effectiveness.
• a user interface 800 includes a user profile 802 for an employee.
• peers may be appropriate to allow, for instance, peer-level colleagues of an employee to see on the employee's profile interface 800 the various mailing lists 804 to which the employee subscribes.
• employees may subscribe to dozens, if not hundreds, of highly focused groups.
• peers can very quickly determine additional groups to which they may wish to subscribe.
• Embodiments of the systems and methods described herein can include other and/or different modules than the ones described here.
• the functionality attributed to the modules can be performed by other or different modules in other embodiments.
• this description occasionally omits the term "module" for purposes of clarity and convenience.
• the modules include processors, subsystems, or processor subsystems for performing various tasks and enabling various functionalities and the actions performed by the modules are enabled or performed by the processors, subsystems, or processor subsystems.
• any reference to "one embodiment” or “an embodiment” means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment.
• the appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.
• Coupled and “connected” along with their derivatives. It should be understood that these terms are not intended as synonyms for each other. For example, some embodiments may be described using the term “connected” to indicate that two or more elements are in direct physical or electrical contact with each other. In another example, some embodiments may be described using the term “coupled” to indicate that two or more elements are in direct physical or electrical contact. The term “coupled,” however, may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other. The embodiments are not limited in this context.
• the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having” or any other variation thereof, are intended to cover a non-exclusive inclusion.
• a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
• "or” refers to an inclusive or and not to an exclusive or. For example, a condition A or B is satisfied by any one of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present).

Landscapes

• Engineering & Computer Science (AREA)
• Business, Economics & Management (AREA)
• Human Resources & Organizations (AREA)
• Strategic Management (AREA)
• Entrepreneurship & Innovation (AREA)
• Marketing (AREA)
• Quality & Reliability (AREA)
• Computer Hardware Design (AREA)
• Signal Processing (AREA)
• Economics (AREA)
• Computer Networks & Wireless Communication (AREA)
• Operations Research (AREA)
• Data Mining & Analysis (AREA)
• Tourism & Hospitality (AREA)
• Physics & Mathematics (AREA)
• General Business, Economics & Management (AREA)
• General Physics & Mathematics (AREA)
• Theoretical Computer Science (AREA)
• Information Transfer Between Computers (AREA)
• Data Exchanges In Wide-Area Networks (AREA)

Priority Applications (5)

Applications Claiming Priority (2)

Publications (1)

Family

ID=43382151

Family Applications (1)

Country Status (7)

Families Citing this family (14)

Citations (4)

Family Cites Families (29)

• 2009
  • 2009-06-25 US US12/491,918 patent/US20100332975A1/en not_active Abandoned
• 2010
  • 2010-06-24 AU AU2010264439A patent/AU2010264439A1/en not_active Abandoned
  • 2010-06-24 CA CA2765708A patent/CA2765708A1/en not_active Abandoned
  • 2010-06-24 KR KR1020127001871A patent/KR20120087119A/ko not_active Withdrawn
  • 2010-06-24 JP JP2012517716A patent/JP2012531671A/ja active Pending
  • 2010-06-24 WO PCT/US2010/039765 patent/WO2010151628A1/en not_active Ceased
  • 2010-06-24 EP EP10792638.8A patent/EP2446371A4/en not_active Ceased

Patent Citations (4)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events