Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
  • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
  • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• • 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/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• • 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]
• • 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
  • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
  • G06Q50/10—Services
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
  • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
  • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
• • 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/42—Mailbox-related aspects, e.g. synchronisation of mailboxes
• • 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
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications

Definitions

• Figure 1 is a diagram showing an exemplary environment for provisioning services and reconciling service properties.
• the following description is directed to techniques and solutions for service provisioning, including reconciling service properties for overlapping services.
• the various techniques and solutions can be used in combination or independently. Different embodiments can implement one or more of the described techniques and solutions.
• a service provisioning environment can manage service provisioning tasks (e.g., storage, provisioning, and deprovisioning of services) for a number of internal and/or external service providers.
• service provisioning tasks e.g., storage, provisioning, and deprovisioning of services
• the programs 1) 40 can use the service provisioning system 1) 10 to perform service provisioning tasks.
• the programs 1) 40 can send a provisioning request (e.g., to provision or deprovision a service for a user) to the service provisioning system 1) 10.
• the provisioning request can be sent using an application programming interface (API) provided by the service provisioning system 1) 10.
• API application programming interface
• the service providers can receive information regarding effective service properties to use for a specific user or users.
• Provisioning information can also include information identifying the service (such as a service name or identifier) and other information about the service, such as service properties.
• Service properties describe the attributes or details of the service. For example, service properties for a webmail service can include mailbox size, expiration information, and authorized devices.
• offer data includes provisioning information describing offers and services.
• An offer includes the following information:
• Offer ID (unique identifier for the offer)
• Service ID (unique identifier for the service)
• the WebmailGoldOffer offer includes two services, ServicelOO and Service300.
• the first service with a Service ID of ServicelOO, has a number of properties.
• ServicelOO has an inbox property with a value of "20GB” and a weight of 100, and an expire property with a value of "Never” and a weight of 100.
• Other offers also include the service ServicelOO, but with different properties.
• the WebmailSilverOffer offer also includes Service 100, but with a 10GB inbox and a lYear expiration.
• provisioning state data includes an association between a user, an offer, and a service.
• a specific user can be associated with a number of provisioned service instances.
• Userl234 is associated with two service instances (an overlapping service), each with different service properties for the ServicelOO webmail service.
• a provisioning state for a user with respect to a particular mailbox service could indicate that one or more service instances of the mailbox service have already been provisioned for the user.
• the provisioning state can indicate that a property action needs to be performed to reconcile service properties among the service instances.
• Fig. 3) is an example provisioning state diagram 3) 00.
• the example provisioning state diagram 3) 00 indicates provisioning state and the appropriate tasks and actions to perform when changing state.
• Offer Action refers to the requested action (e.g., a request to provision or deprovision an offer and/or a service for a user).
• the second column, "Initial User State,” refers to the current provisioning state of the service for the user.
• the initial user state can indicate that no instances of the service have yet been provisioned for the user (e.g., that the user is not currently subscribed to the service).
• the initial user state can also indicate that one instance of the same service has already been provisioned for the user, or that multiple instances of the same service have already been provisioned for the user (that the user has been
• Service Action refers to the action to be performed. In some situations, no action needs to be performed. In other situations, the service is added (e.g., if this is the first time the service is being provisioned for the user). In yet other situations, the service is be removed (e.g., if the user does not have any instances remaining for the service).
• the fourth column, "Property Action,” refers to the action to be performed with respect to the service properties. In some situations, new properties are added. In other situations, properties are reconciled. In yet other situations, properties are removed.
• the first row 3) 10 indicates what tasks and actions are performed when receiving a request to provision a service (a provisioning request) when the service is not currently provisioned for the user (when the initial user state indicates that there are no current service instances for the user).
• the service will be added for the user (the Service Action) and new service properties will be stored (the Property Action). This can result in a new service instance (indicating the service, including service properties, has been provisioned for the user) being stored (e.g., in a provisioning state database).
• this state (row 3) 10) would apply.
• the webmail service (ServicelOO) would be added for the user (e.g., the service provider of the webmail service would allocate, or enable, the user's webmail account) with the service properties indicated by the service (in this 10GB inbox and a one year expiration).
• the service instance could then be stored (in this case, the service instance could include the offer identifier, service identifier, user identifier, and service properties).
• the effective service properties (in this case, the properties of the one instance) could also be stored and/or sent to the service provider to use when providing the service for the user.
• a user could also subscribe to the ServicelOO webmail service outside of any offer.
• the user could directly subscribe to the ServicelOO webmail service, including specific service properties (e.g., a 5GB inbox with a one year expiration).
• the service instance could then be stored (in this case, the service instance could include the service identifier, user identifier, and service properties).
• the service instance could also include an indication that the instance is not related to an offer.
• the second row 3) 20 indicates what tasks and actions are performed when receiving a request to provision a service (a provisioning request) when one instance of the service is currently provisioned for the user (when the initial user state indicates that there is one current service instances for the user).
• the service does not have to be added for the user (the Service Action) because the user is already subscribed to the service, and service properties will be reconciled (the Property Action).
• the reconciling will be performed for the properties of the new service provisioning request and the properties of the current (existing) instance of the service.
• the reconciling is performed to determine the effective service properties to be used for the service (those properties values that represent the best, or desired, level of service across the instances).
• the effective service properties will be applied to the service, and can also be stored.
• a new service instance will be stored for the new provisioning request (indicating the service, service properties, and user).
• the reconciling would compare the inbox property (an overlapping service property because the inbox property occurs in both instances of the service) using the weights (the 10GB inbox property value with a weight of 60 compared to the 5 GB inbox property value with a weight of 40) to determine an effective inbox property value (in this case, 10GB would be the effective inbox property value).
• the expiration property would be compared.
• the resulting effective property values would then be applied to the webmail service for the user (the user would receive a 10GB inbox with a one year service expiration).
• the effective service properties could be sent to the service provider to use when providing the user the webmail service.
• the effective service properties could also be saved (e.g., in a database at the service provisioning system and/or in a database at the service provider).
• updating (or sending) effective service properties to the service provider can be skipped. For example, if the new service instance does not include properties with better (or more desirable) values than existing instance (s), then effective properties do not have to be sent as they would be the same as the ones currently in use (e.g., this could occur if the user has a 10GB inbox currently provisioned and the new instance is for a 5GB inbox).
• the third row 3) 30 indicates what tasks and actions are performed when receiving a request to provision a service (a provisioning request) when multiple instance of the service is currently provisioned for the user (when the initial user state indicates that there are two or more current service instances for the user).
• the service does not have to be added for the user (the Service Action) because the user is already subscribed to the service, and service properties will be reconciled (the Property Action). The reconciling will be performed for the properties of the new service provisioning request and the properties of the current
• the reconciling is performed to determine the effective service properties to be used for the service (those properties values that represent the best level of service across the instances).
• the effective service properties will be applied to the service, and can also be stored. Also, a new service instance will be stored for the new provisioning request (indicating the service, service properties, and user).
• the result of this activity would be three service instances for the webmail account service, which could each have different service properties (overlapping service properties).
• the service properties could be reconciled across the three instances and the best value for each property selected as the effective service properties.
• the effective service properties would then be applied (used for) the webmail account service for the user.
• the fourth row 3) 40 indicates what tasks and actions are performed when receiving a request to deprovision a service when the service is not currently provisioned for the user (when the initial user state indicates that there are no current service instances for the user). In this situation, no service actions or property actions need to be performed.
• This row is included in the example provisioning state diagram 3) 00 for completeness, and represents what occurs when receiving a deprovisioning request to deprovision a service instance that is not present.
• the fifth row 3) 50 indicates what tasks and actions are performed when receiving a request to deprovision a service (a deprovisioning request) when one instance of the service is currently provisioned for the user (when the initial user state indicates that there is one current service instances for the user).
• the service will be removed for the user (the Service Action).
• the service properties will also be removed because the user is no longer subscribed to the service. For example, consider a user who had previously subscribed to the WebmailSilverOffer offer (see Section IV above), which includes a one year webmail inbox service. If a year has passed (or if the user indicates a desire to cancel the service), then a deprovisioning request can be received to deprovision the service for the user.
• the sixth row 3) 60 indicates what tasks and actions are performed when receiving a request to deprovision a service (a deprovisioning request) when multiple instances of the service are currently provisioned for the user (when the initial user state indicates that there are two or more current service instances for the user).
• the service is not removed for the user (the Service Action) because at least one service instance will remain after the deprovisioning event (the user will still be a subscriber to the service).
• the deprovisioning event can indicate an identifier for the specific instance to be deprovisioned
• service properties for the remaining service instances will be reconciled (the Property Action).
• WebmailSilverOffer offer (see Section IV above), which includes the Service 100 webmail service, and currently subscribed to the ServicelOO webmail service (e.g., Webmail Separate, not part of an offer) and thus has two instances of the ServicelOO service provisioned. If the user then decides to cancel the WebmailSilverOffer offer, this state (row 3) 60) would apply.
• the WebmailSilverOffer offer would be removed, and the service properties of the remaining instance would be reconciled.
• the properties of the one remaining service instance would be the new effective service properties (the Webmail Separate properties, which include a 5GB inbox).
• the user's webmail service (ServicelOO) is not completely removed when the user cancels the WebmailSilverOffer offer while the user still maintains subscriptions to other offers that include the service (ServicelOO) or the user is directly subscribed to the service.
• the service properties of the remaining service instances are reconciled (e.g., the user may receive a reduced level of service, such as a 5GB inbox instead of a 10GB inbox).
• service properties need to be reconciled in order to determine which properties to apply (to use) for a particular service for a particular user.
• reconciliation is straightforward (e.g., just apply the new service properties).
• reconciling service properties between the new instance and the existing (or current) instances can be more difficult.
• reconciling service properties between the remaining instances can be more difficult.
• an algorithm represented by the following pseudo code is used to reconcile service properties to determine effective service properties.
• the algorithm can be implemented by a service provisioning system (e.g., by the service provisioning system depicted in Fig. 1) or the service syndication system depicted in Fig. 6)).
• the algorithm can be implemented when a provisioning event occurs (e.g., upon receiving a request to provision or deprovision a service for a user), such as when changing state as indicated in the provisioning state diagram depicted in Fig. 3).
• a list of effective service properties are determined for each service that the user is subscribed to (each service for which the user has one or more service instances).
• the effective service properties are created, in the above pseudo code, by adding properties that are not already present and otherwise including the property value with the greater weight (e.g., reflecting the value that provides the best relative level of service).
• the resulting effective service properties are then sent, according to the above pseudo code, to the service provider that is providing the service.
• Fig. 2 shows an exemplary method 2) 00 for provisioning services using, at least in part, a service provisioning system (e.g., the service provisioning system depicted in Fig. 1) or the service syndication system depicted in Fig. 6)).
• a service provisioning system e.g., the service provisioning system depicted in Fig. 1
• the service syndication system depicted in Fig. 6 e.g., the service syndication system depicted in Fig.
• reconciling service properties to determine effective service properties comprises comparing values for the same property from multiple service instances using relative weights to determine which property value represents the best relative level of service.
• Fig. 4) shows an exemplary method 4) 00 for reconciling service properties.
• the example method 4) 00 can be performed when receiving a provisioning request in order to determine effective service properties to apply for a service for a user.
• new service properties are compared with current service properties. For example, new values for service properties (from a provisioning request) can be compared with current values from one or more currently provisioned service instances for the service. Values of each specific service property can be compared to see which value represents the best relative level of service. For example, the comparison can be performed using relative weights associated with the property values.
• the values representing the best relative level of service for each property are selected based on the comparison 4) 20.
• the inbox property value representing the best relative level of service is selected as an effective property value (in this example, the property value of 10GB is selected as an effective property value for the inbox property, and the 5 GB property value is not selected and thus not currently applied to the service).
• Fig. 5) shows an exemplary method for provisioning services and reconciling service instances.
• the example method 5) 00 can be performed when receiving a provisioning request in order to determine effective service properties to apply for a service for a user.
• a provisioning request is received (e.g., received by a service
• the provisioning request comprises a request to provision a service (e.g., represented by a unique service identifier) for a user (e.g., represented by a unique user identifier).
• a service e.g., represented by a unique service identifier
• the provisioning request includes new service properties for the service.
• An example provisioning request is a request to provision a webmail service (e.g., ServicelOO) for a specific user (e.g.,
• a new service instance representing the provisioning request 5) 10 is stored.
• the service instance can comprise a unique service identifier, a unique user identifier, and new service properties.
• the service instance can also comprise a unique offer identifier.
• the service instance can be stored in a provisioning state database by a service provisioning system.
• the new service instance 5) 20 is reconciled with one or more existing service instances for the same service.
• the reconciling is performed to determine effective service properties for the service.
• properties of the service instances (which may have different values for the same property) are compared to determine which value represents the best level of service.
• the effective service properties are used (applied) for the service for the user.
• Fig. 6) depicts an exemplary service syndication environment 6) 00.
• the service syndication environment 6) 00 provides a centralized service provisioning solution for internal service providers 6) 40 and external service providers 6) 50.
• a service syndication system 6) 10 (a service provisioning system capable of supporting multiple internal and/or external service providers) provides centralized provisioning, deprovisioning, maintenance, and storage solutions.
• the service syndication system 6) 10 provides the centralized solutions by supporting various service provisioning operations (e.g., provisioning, deprovisioning, and maintenance service provisioning operations).
• the service syndication system 6) 10 receives requests (e.g., service provisioning requests) from programs 6) 80 and from internal service providers 6) 40 and external service providers 6) 50.
• the service syndication system 6) 10 can use various types of computing devices (e.g., server computers, database servers, networking devices, and other types of computing devices) to provide provisioning solutions.
• the service syndication system 6) 10 is associated with a data repository storing offer and service data 6) 20.
• the service and offer data 6) 20 includes information related to offers (e.g., go-to-market offers) and services (e.g., individual services or collections of services related to an offer) as well as service properties.
• offers e.g., go-to-market offers
• services e.g., individual services or collections of services related to an offer
• service properties e.g., the offer and service data can be stored according to the data schema described in Section IV above.
• service syndication environment 6) 00 internal service providers 6) 40 and external service providers 6) 50 can provide services to their subscribers (users) 6) 60 while utilizing the service syndication system 6) 10 for storage of provisioning
• the service syndication system 6) 10 would store the service instance in the provisioning state data store 6) 30.
• the service syndication system 6) 10 would also reconcile service properties if multiple service instances exist for the service (e.g., for the ServicelOO service) in the provisioning state data store 6) 30.
• the subscriber could also sign up for other offers that include the same service, which could be centrally provisioned by the service syndication system 6) 10. For example, if the subscriber signs up for the WebmailGoldOffer offer (as described in
• the external service provider (or program) would send a provisioning request to the service syndication system 6) 10.
• the service syndication system 6) 10 would use the offer and service data store 6) 20 to obtain information regarding the offer and store one or more provisioning instances (depending on the number of services in the offer) in the provisioning state data store 6) 30.
• the service syndication system 6) 10 would store a second service instance for the ServicelOO service (the first instance was the ServicelOO instance for the Webmail Separate offer for the subscriber) using the properties as defined in the WebmailGoldOffer offer.
• the service syndication system 6) 10 would reconcile the service properties across the two instances of the
• ServicelOO service e.g., the 5GB and 20GB inbox property values would be compared using their respective weights and the 20GB value would be selected as the effective inbox property value.
• the service syndication system 6) 10 would send updated effective service properties to the service provider in charge of the ServicelOO webmail service (in this example, to one of the internal service providers 6) 40).
• the service syndication environment 6) 00 also supports external provisioning systems 6) 70.
• Supporting external service provisioning systems 6) 70 allows service providers (e.g., external service providers 6) 50) to use a provisioning solution other than the service syndication system 6) 10 for provisioning, but still use the service syndication system 6) 10 for storage of provisioning information and reconciliation of service properties.
• an external service provider 6) 50 could provision a service for a subscriber 6) 60 using an external provisioning system 6) 70 and store (e.g., via a provisioning state update application programming interface (API)) the service instance at the service syndication system 6) 10.
• API application programming interface
• Instances of the same service could also be provisioned directly via the service syndication system 6) 10.
• Instances from both paths can be centrally stored and reconciled at the service syndication system 6) 10.
• IX Example Computing Environment
• Fig. 7) illustrates a generalized example of a suitable computing environment 7) 00 in which described embodiments, techniques, and technologies may be implemented.
• the computing environment 7) 00 can be one of the computing devices (e.g., a computer server) used to operate the service provisioning system 1)10 or the service syndication system 6) 10.
• the computing environment 7) 00 is not intended to suggest any limitation as to scope of use or functionality of the technology, as the technology may be implemented in diverse general-purpose or special-purpose computing environments.
• the disclosed technology may be implemented with other computer system configurations, including hand held devices, multiprocessor systems, microprocessor-based or
• the computing environment 7) 00 includes at least one central processing unit 7) 10 and memory 7) 20.
• This most basic configuration 7) 30 is included within a dashed line.
• the central processing unit 7) 10 executes computer- executable instructions and may be a real or a virtual processor. In a multi-processing system, multiple processing units execute computer-executable instructions to increase processing power and as such, multiple processors can be running simultaneously.
• the memory 7) 20 may be volatile memory (e.g., registers, cache, RAM), non-volatile memory (e.g., ROM, EEPROM, flash memory, etc.), or some combination of the two.
• the memory 7) 20 stores software 7) 80 that can, for example, implement the technologies described herein.
• a computing environment may have additional features.
• the computing environment 7) 00 includes storage 7) 40, one or more input devices 7) 50, one or more output devices 7) 60, and one or more communication connections 7) 70.
• An interconnection mechanism such as a bus, a controller, or a network, interconnects the components of the computing environment 7) 00.
• operating system software provides an operating environment for other software executing in the computing environment 7) 00, and coordinates activities of the components of the computing environment 7) 00.
• the storage 7) 40 may be removable or non-removable, and includes magnetic disks, magnetic tapes or cassettes, CD-ROMs, CD-RWs, DVDs, or any other medium which can be used to store information and which can be accessed within the computing environment 7) 00.
• the storage 7) 40 stores instructions for the software 7) 80, which can implement technologies described herein.
• the input device(s) 7) 50 may be a touch input device, such as a keyboard, keypad, mouse, pen, or trackball, a voice input device, a scanning device, or another device, that provides input to the computing environment 7) 00.
• the input device(s) 7) 50 may be a sound card or similar device that accepts audio input in analog or digital form, or a CD-ROM reader that provides audio samples to the computing environment 7) 00.
• the output device(s) 7) 60 may be a display, printer, speaker, CD-writer, or another device that provides output from the computing environment 7) 00.
• the communication connection(s) 7) 70 enable communication over a
• the communication medium conveys information such as computer-executable instructions, compressed graphics information, or other data in a modulated data signal.
• Computer-readable media are any available media that can be accessed within a computing environment 7) 00.
• computer-readable media include memory 7) 20, storage 7) 40, communication media (not shown), and combinations of any of the above.
• Computer-readable media are any available media that can be accessed within a computing environment 7) 00.
• computer-readable media include memory 7) 20 and/or storage 7) 40.
• the term computer-readable storage media includes the media for data storage such as memory 7) 20 and storage 7) 40, and not transmission media such as modulated data signals.
• Fig. 8) illustrates a generalized example of a suitable implementation environment 8) 00 in which described embodiments, techniques, and technologies may be
• a cloud 8) 10 various types of services (e.g., computing services) are provided by a cloud 8) 10.
• the cloud 8) 10 can comprise a collection of computing devices, which may be located centrally or distributed, that provide cloud- based services to various types of users and devices connected via a network such as the Internet.
• the cloud 8) 10 provides services for connected devices with a variety of screen capabilities 8) 20A-N.
• Connected device 8) 20A represents a device with a computer screen (e.g., a mid-size screen).
• connected device 8) 20A could be a personal computer such as desktop computer, laptop, notebook, netbook, or the like.
• Connected device 8) 20B represents a device with a mobile device screen (e.g., a small size screen).
• connected device 8) 20B could be a mobile phone, smart phone, personal digital assistant, tablet computer, and the like.
• service provisioning techniques and solutions described in this application can be used in various combinations to provide more efficient management of service instances, including service instances for overlapping services.

Landscapes

• Engineering & Computer Science (AREA)
• Business, Economics & Management (AREA)
• Human Resources & Organizations (AREA)
• Strategic Management (AREA)
• Economics (AREA)
• Tourism & Hospitality (AREA)
• Entrepreneurship & Innovation (AREA)
• Computer Networks & Wireless Communication (AREA)
• Marketing (AREA)
• Signal Processing (AREA)
• Physics & Mathematics (AREA)
• General Business, Economics & Management (AREA)
• General Physics & Mathematics (AREA)
• Theoretical Computer Science (AREA)
• Quality & Reliability (AREA)
• Operations Research (AREA)
• Educational Administration (AREA)
• General Health & Medical Sciences (AREA)
• Development Economics (AREA)
• Game Theory and Decision Science (AREA)
• Primary Health Care (AREA)
• Health & Medical Sciences (AREA)
• Computer Hardware Design (AREA)
• Data Mining & Analysis (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)
• Information Transfer Between Computers (AREA)
• Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Priority Applications (6)

Applications Claiming Priority (2)

Publications (2)

Family

ID=44258907

Family Applications (1)

Country Status (10)

Families Citing this family (14)

Family Cites Families (23)

• 2010
  • 2010-01-11 US US12/685,577 patent/US8548442B2/en active Active
  • 2010-12-31 CN CN201080061062.3A patent/CN102713881B/zh not_active Expired - Fee Related
  • 2010-12-31 AU AU2010339650A patent/AU2010339650B2/en not_active Ceased
  • 2010-12-31 CA CA2786675A patent/CA2786675A1/en not_active Abandoned
  • 2010-12-31 KR KR1020127017937A patent/KR20120113225A/ko not_active Ceased
  • 2010-12-31 EP EP10842769.1A patent/EP2524318B1/en not_active Not-in-force
  • 2010-12-31 JP JP2012548952A patent/JP5688099B2/ja not_active Expired - Fee Related
  • 2010-12-31 WO PCT/US2010/062644 patent/WO2011084874A2/en not_active Ceased
• 2012
  • 2012-07-04 IL IL220753A patent/IL220753A/en not_active IP Right Cessation
  • 2012-07-09 CL CL2012001913A patent/CL2012001913A1/es unknown

Also Published As

Similar Documents

Legal Events