WO2011032468A1 - Système de gestion de données d'utilisateur de service et son procédé de mise en œuvre de gestion de données d'utilisateur de service - Google Patents

Système de gestion de données d'utilisateur de service et son procédé de mise en œuvre de gestion de données d'utilisateur de service Download PDF

Info

Publication number
WO2011032468A1
WO2011032468A1 PCT/CN2010/076717 CN2010076717W WO2011032468A1 WO 2011032468 A1 WO2011032468 A1 WO 2011032468A1 CN 2010076717 W CN2010076717 W CN 2010076717W WO 2011032468 A1 WO2011032468 A1 WO 2011032468A1
Authority
WO
WIPO (PCT)
Prior art keywords
user data
service user
business
service
query
Prior art date
Application number
PCT/CN2010/076717
Other languages
English (en)
Chinese (zh)
Inventor
王蔚
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2011032468A1 publication Critical patent/WO2011032468A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Definitions

  • the invention relates to a telecom value-added service, in particular to a service user data management system and a method for realizing business user data management. Background technique
  • the processing capability of the data processing device of the business user is greatly reduced, and the inconsistency of the data of the business user is easily generated, and the problem of comparison processing in the background is required.
  • the number of devices will continue to increase.
  • the service user data processing device needs to continuously increase the interface and processing of synchronizing service user data with other devices or systems that need service user data, thus greatly increasing the complexity of the service user data processing device.
  • business systems need to obtain business user data that they do not have, and obtain relevant business user data from other business systems.
  • business systems need more and more business data about users in order to give users a better experience.
  • the SMS value-added service needs to obtain the user's location information from the positioning system, and also obtains the user's status information from the rendering engine to accurately provide the user with information information. Therefore, a business system will obtain relevant business user data from more and more other external business systems or engines.
  • Increasing data interfaces between systems and systems, using systems such as mesh intertwined, are becoming more complex, and system upgrades and maintenance become more and more difficult.
  • the main object of the present invention is to provide a service user data management system capable of unified management of service user data and sharing and synchronizing service user data in multiple service systems.
  • Another object of the present invention is to provide a method for implementing service user data management by a service user data management system, which can implement unified management of service user data, and share and synchronize business user data in multiple service systems.
  • a business user data management system comprising at least a business user data model component, a data source registration center, and a business user data component, wherein
  • a service user data model component configured to be responsible for managing a stored business user data model
  • a data source registration center configured to receive a registration request from a service user data source, and manage registration information of the service user data source
  • a service user data component configured to receive a service user data query request from a service user data requester, according to a corresponding business user data model in the business user data model component, and a registration information of the data source in the data source registration center, from the service The corresponding business user data is queried in the user data data source.
  • the system further includes a business user data management component, configured to be responsible for management of the business user data; according to the corresponding business user data model in the business user data model component, and the registration information of the data source in the data source registration center, Manage corresponding business user data in the business user data source;
  • the service user data management module provides a management interface for service user data.
  • the service user data model component provides a service user data model query interface, and is used by the service user data model requester to query the business user data model;
  • the business user data model is a data model for business user data and is used to represent business use.
  • the data items of the user data and the logical relationship between these data items.
  • the business user data model component also provides a configuration interface of the business user data model, and the business user data model manages the requester to configure the business user data model.
  • the registration interface provided by the data source registration center is used to register the registration information of the service user data source.
  • the service user data data source is used to store service user data
  • the service user data data source may be one or more.
  • the service user data data source is a service engine, a business system, or a database.
  • a method for implementing business user data management by a business user data management system comprising at least a business user data model component, a data source registration center, and a business user data component, the method comprising:
  • the business user data component receives the business user data query request, obtains the business user data model from the business user data model component, obtains the registration information from the data source registration center, and obtains the business user data model and the registration information to the business user data source according to the obtained business user data model.
  • the corresponding business user data is queried.
  • the service user data query request carries a query condition
  • the obtaining the service user data model from the service user data model component is: the service user data model component queries the corresponding query service user data model information according to the query condition; and the obtaining the registration information from the data source registration center is: according to the query.
  • the incoming business user data model queries the data source registry for the registration information of the requested business user data.
  • the service user data query request further carries a data structure with a required query result; the method further includes:
  • the business user data component generates a query result according to the data structure, and returns a query request to the business user data query.
  • the registration information includes: configuration information of a service user data source, and/or used to represent a service
  • the user data management system obtains query policy information of the service user data provided by the data source, and/or change policy information for indicating that the service user data management system updates the data source related service user data.
  • the configuration information includes: a correspondence relationship with the data item in the service user data model, data source access interface information, and data source access authentication information;
  • the query policy information is that no query, or real-time query, or change query is needed;
  • the change policy information is that no update, real-time update, or timed update is required.
  • the system further includes a business user data management component, the method further comprising:
  • the business user data component Based on the registration information of the returned business user data, the business user data component requests the business user data source that needs to be changed to change the business user data required for the current request, and obtains the update result.
  • the method further includes: the service user data management component notifying the service user data change requester of the obtained update result.
  • the system of the present invention mainly includes a service user data model component, a data source registration center, and a service user data component.
  • the business user data component receives the business user data query request, obtains the business user data model from the business user data model component, obtains the registration information from the data source registration center, and obtains the business user data model and the registration information to the business user data source according to the obtained business user data model. The corresponding business user data is queried.
  • the unified management of the service user data is realized, and the management interface provided by the service user data management system realizes the unified opening and opening of the service user data, so that each service system and application pass the service user data management system, The required business user data is managed.
  • FIG. 1 is a schematic diagram of a location of a service user data management system in a network according to the present invention
  • FIG. 2 is a schematic structural diagram of a service user data management system according to the present invention
  • FIG. 3 is a flowchart of a first embodiment of implementing a service user data query according to the present invention
  • FIG. 4 is a flowchart of a second embodiment of implementing a service user data query according to the present invention
  • FIG. 6 is a flowchart of a second embodiment of a service user data management system according to the present invention
  • FIG. 7a is a schematic diagram of a first usage mode of a service user data management system according to the present invention
  • Figure 7c is a schematic diagram of a third usage mode of the service user data management system of the present invention
  • Figure 7d is a schematic diagram of a fourth usage mode of the service user data management system of the present invention.
  • FIG. 1 is a schematic diagram of a location of a service user data management system in a network according to the present invention.
  • a service system A, a service engine, a database C, and the like are used as data sources of a service user data management system, and are used for responsible services. Provision and storage of user data.
  • the business system D, the business engine E, the application F, and the like are users of the business user data management system, and are used to request to query or change the business user data.
  • the business system, the business engine ⁇ database C, the business system 0, the business engine £, the application F only indicate the type of entity connected with the business user data management system, does not indicate the exact quantity, the number of these entities can be zero One, one or more.
  • the service system A and the service system D, or the service engine B and the service engine E, respectively may be the same or different. There are two cases in which the service system A and the service system D, or the service engine B and the service engine E are the same:
  • the business system or business engine is the provider of some data items for business user data, and the user of other data items for business user data.
  • the business system or the business engine is the provider of the business user data.
  • the business system or the business engine needs to synchronize the changed data to the business user data management system.
  • Business user data At this time, the business system or the business engine acts as a user of the business user data management system, and invokes the business user data change interface of the business user data management system.
  • the service user data management system mainly includes a service user data model component, a data source registration center, and a service user data component, where
  • the business user data model component is responsible for managing the business user data model, at least including the business user data model query operation, and further includes management of the business user data model change operation.
  • the business user data model is a data model for business user data, which is used to indicate the business user data model query interface that the enterprise can provide through the business user data model component, and query the business user data model.
  • the business user data model component is also used to provide a configuration interface for the business user data model to be configured for the business user data model management requestor to configure the business user data model.
  • the data source registration center is configured to receive a registration request from a service user data source, manage configuration information of the service user data source, and/or query policy, and/or change policy and the like.
  • the business user data source can be registered through the data source registration center. Registration information of the user data data source.
  • a service user data component configured to receive a service user data query request from a service user data requester, according to a corresponding business user data model in the business user data model component, and a data source configuration, a query policy, and the like in the data source registration center.
  • the registration information is used to query the corresponding business user data from the business user data source.
  • the service user data requester can query the service user data through the service user data query interface provided by the service user data component.
  • the service user data requester may be the business system 0, the business engine £, the application F, and the like as shown in FIG.
  • the service user data management system of the present invention further includes a service user data management component, which is responsible for management of service user data, such as notification, change, synchronization, etc., and the change may include operations such as adding, modifying, and deleting service user data.
  • the service user data management component may perform corresponding business user data in the service user data source according to the corresponding business user data model in the business user data model component, and the registration information of the data source configuration and the query policy in the data source registration center. Change, synchronize, etc.
  • the service user data management requester can perform notification, change, and synchronization of the service user data through the management interface of the service user data provided by the service user data management module.
  • the service user data management requester may be the business system 0, the business engine £, the application F, and the like as shown in FIG.
  • the service user data source in the above is used to store the business user data, that is, the owner of the business user data.
  • the business user data data source may be one or more, and may be various business engines, business systems or databases, and the like. As shown in Figure 1, the business system, business engine ⁇ database C, and so on.
  • the service user data source source registers the registration information of the data source configuration, query policy, and change policy with the data source registration center of the business user data management system.
  • the configuration information of the data source may include: a correspondence relationship with the data item in the service user data model, data source access interface information (including interface type, address, request parameter, return result, and the like), and data source access authentication information.
  • the query policy information of the data source is a policy for the business user data management system to obtain the business user data provided by the data source, such as no query, real-time query, or change query. Some data sources only need to synchronize business user data from the business user data management system.
  • the query strategy of the data source should be no query. After the data of the service user in some data sources is changed, the service user data management system is notified through the management interface of the service user data management system, and the related business user data in the data source is changed.
  • the query policy of the data source may be a change query. After the service user data management system receives the change notification of the data source, the query access is performed; when the service user data management system does not receive the change notification of the data source, the service user data management system can use the cached data without performing the Inquire. In some data sources, the service user data is updated faster, such as the location information of the user in the location system.
  • the query policy of the data source should be a real-time query, that is, when the service user data management system needs the service user data provided by the data source. Inquire.
  • the change policy information of the data source is a policy for the business user data management system to update the user data of the data source related to the data source, such as no update, real-time update, or regular update.
  • Some data sources only provide relevant business user data for the business user data management system.
  • the data change processing is handled by the data source itself, and the data source's change strategy should be no need to update.
  • Some data sources need to synchronize relevant business user data from the business user data management system in real time.
  • the data source's change strategy should be updated in real time.
  • Some data sources are not required for the real-time performance of business user data. Only the business user data management system needs to synchronize the relevant business user data to it.
  • the change strategy of the data source should be a regular update.
  • Step 300 The service user data query requester sends a service user data query request to the service user data component.
  • the service user data query requester can be a customer service system, a user self-service portal, a location short message application, and the like.
  • the service user data query request carries at least the query conditions, such as the user identifier and the service identifier. Further, the data structure of the required query result, such as the user's service subscription relationship and the user basic information, may be carried.
  • Step 301 The business user data component queries the business user data model component from the business user data model component.
  • the service user data model query request carries query conditions, such as user identification, service identifier, and the like.
  • Step 302 The business user data model component returns the business user data model information.
  • Step 303 The service user data component queries the data source registration center according to the service user data model to query the registration information such as the data source configuration and the query policy of the requested service user data.
  • Step 304 The data source registration center returns the data source configuration and the query policy information of the corresponding service user data stored by the data source registration center to the service user data component.
  • Step 305 The service user data component requests the service user data data source that needs to be queried according to the service user data source configuration and the query policy information returned by the data source registration center to query the service user data required by the current request.
  • Step 306 The business user data data source returns corresponding business user data.
  • Step 307 The service user data component generates a query result according to the data structure required in the service user data query request, and returns the data query requester to the service user.
  • the query result may be generated according to a default, that is, a preset data structure, or the queryed service user data may be directly returned to the requester.
  • the requester generates a query result according to its own data structure.
  • the number of steps 305 and 306 is determined by the number of business user data sources.
  • the service user data management system of the present invention realizes the capability of uniformly providing service user data for each service system, service engine, and application.
  • a plurality of policies may be used.
  • the query user is cached for the service user data in the data source of the change query, so that when the service user data query requester requests the service data, directly
  • the data is retrieved from the cache without having to request relevant business user data from the data source each time.
  • the relevant business user data is queried from the data source only after receiving the change notification of the data source.
  • FIG. 4 is a flowchart of a second embodiment of implementing the service user data query according to the present invention. As shown in FIG. 4, the method includes the following steps:
  • Step 400 The service user data query requester sends a service user data query request to the service user data component.
  • the service user data query requester can be a customer service system, a user self-service portal, a location short message application, and the like.
  • the service user data query request carries at least the query conditions, such as the user identifier and the service identifier. Further, the data structure of the required query result, such as the user's service subscription relationship and the user basic information, may be carried.
  • Step 401 The business user data component returns a service user data query request to the business user data query requester, but does not return the query result.
  • Step 402 The business user data component queries the business user data model component from the business user data model component.
  • the service user data model query request carries query conditions, such as user identification, service identifier, and the like.
  • Step 403 The business user data model component returns the business user data model information.
  • Step 404 The service user data component queries the data source registration center according to the service user data model to query data source configuration and query policy information of the requested service user data.
  • Step 405 The data source registration center stores the data source of the corresponding business user data stored therein.
  • the query policy information is returned to the business user data component.
  • Step 406 The service user data component requests the service user data data source that needs to be queried according to the service user data source configuration and the query policy information returned by the data source registration center to query the service user data required by the current request.
  • Step 407 The service user data source returns the corresponding service user data.
  • Step 408 The service user data component generates a query result according to the data structure required by the service user data query request, and returns the data query requester to the service user.
  • FIG. 5 is a flowchart of a first embodiment of implementing service user data management according to the present invention. It is assumed that a service user data model has been configured, and a related service user data source has been registered in a data source registration center in the service user data management system. . As shown in FIG. 5, the following steps are included: Step 500: The service user data change requester sends a service user data change request to the service user data component.
  • the business user data change requester can operate the support system, integrate the address book service, and the like.
  • the business user data change request carries at least the update type (such as add, delete, modify), the data source identifier, the corresponding data item in the data model, and the updated data value.
  • Step 501 The business user data component queries the business user data model component from the business user data model component.
  • the business user data model query request carries at least the data items that need to be queried.
  • Step 502 The business user data model component returns business user data model information.
  • Step 503 The service user data component queries the data source registration center according to the service user data model to query the data source configuration and the change policy information of the requested service user data.
  • Step 504 The data source registration center returns the data source configuration and the change policy information of the corresponding service user data stored by the data source registration center to the service user data component.
  • Step 505 The service user data component requests, according to the service user data source configuration and the change policy information returned by the data source registration center, the service user data data required to change the current request to the service user data source source that needs to be changed.
  • the service user data data source may be zero, one or more, depending on the configuration and change policy information of the service user data data source registered in the service user data source registration center.
  • Step 506 The business user data data source returns an update result of the business user data, such as success or failure.
  • Step 507 The business user data management component notifies the business user data change requester of the obtained update result.
  • step 505 shown in FIG. 5 if the business user data is changed to a plurality of business user data sources, the business user data management component needs to perform transaction processing to ensure the consistency of the business user data in each data source. That is, when the related business user data change in some data sources fails, the rollback policy can be retrieved, and the change operation of the partially successful data source is rolled back, so that all the data sources in the data source that need to update the business user data can be consistent.
  • the update of the service user data of the data source of the plurality of service users is realized.
  • the data of the data source of a certain service user is changed, the corresponding data source of the other service user data is also corresponding.
  • the business user data has been changed to realize the functions of synchronization and subscription of business user data.
  • the operation support system adds the user's business order relationship, and the operation support system changes the relevant business user data through the management interface of the business user data management system, and the business user data management system can change through the process shown in FIG.
  • the data is synchronized to related business systems, customer service systems, and the like.
  • FIG. 6 is a flowchart of a second embodiment of implementing service user data management according to the present invention. As shown in FIG. 6, the method includes the following steps:
  • Step 600 The service user data change requester sends a service user data change request to the service user data component.
  • the business user data change requester can operate the support system, integrate the address book service, and the like.
  • the business user data change request carries at least the update type (such as adding, deleting, modifying), data The source ID, the corresponding data item in the data model, and the updated data value.
  • Step 601 The business user data component returns a service user data change request to the business user data change requester, but does not return the query result.
  • Step 602 The business user data component queries the business user data model component from the business user data model component.
  • the business user data model query request carries at least the data items that need to be queried.
  • Step 603 The business user data model component returns the business user data model information.
  • Step 604 The service user data component queries the data source registration center according to the service user data model to query the data source configuration and the change policy information of the requested service user data.
  • Step 605 The data source registration center returns the data source configuration and the change policy information of the corresponding service user data stored by the data source registration center to the service user data component.
  • Step 606 The service user data component requests, according to the service user data source configuration and the change policy information returned by the data source registration center, the service user data data required to change the current request to the service user data source source that needs to be changed.
  • the service user data source may be zero, one or more, depending on the configuration and change policy information of the service user data source registered in the service user data source registry.
  • Step 607 The business user data data source returns an update result of the business user data, such as success or failure.
  • Step 608 The business user data management component notifies the business user data change requester of the obtained update result.
  • FIG. 7a is a schematic diagram of the first usage mode of the service user data management system of the present invention.
  • the service system itself stores required service user data, and the service system needs related service user data.
  • the business user data management requester is required to request data change from the business user data management system through the management interface.
  • the business user data management component in the business user data management system updates the business user data to the corresponding business system according to the business user data model and the business user data data source configuration and the change policy information. This update operation can be updated to one or more business systems simultaneously.
  • FIG. 7b is a schematic diagram of the second usage mode of the service user data management system of the present invention.
  • the service system itself stores required service user data, and the service system needs related service user data.
  • the business system requests the business user data management system to change the related business user data through the management interface.
  • FIG. 7c is a schematic diagram of the third usage mode of the service user data management system of the present invention.
  • the service system itself stores required service user data, and the service system needs related service user data.
  • the relevant business user data in the business system changes, it is also processed internally by the business system.
  • the business user data management system needs related business user data in the business, the related data is queried to the business system.
  • FIG. 7d is a schematic diagram of the fourth usage mode of the service user data management system of the present invention.
  • the service system does not save the required service user data, and when the service system needs the service user data, The service system requests the corresponding service user data from the service user data query system through the service user data query interface.
  • the business user data changes, it is processed by the business user data management system and does not need to be updated to the business system.
  • the four modes shown in Figs. 7a to 7d can coexist. Controlled by the query policy and change policy in the registration information of the business user data source.
  • the query policy should be a real-time query, and the change policy should be no change required; for the fourth usage mode, the query policy does not require a query, and the change policy does not require a change.
  • Correct Different business systems can use different methods according to the characteristics of their related business user data. For example, if the user location information in the positioning system changes in real time, the third usage mode can be used.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention porte sur un système de gestion de données d'utilisateur de service et sur son procédé de mise en œuvre de gestion de données d'utilisateur de service. Le système de la présente invention comprend principalement : une composante de modèle de données d'utilisateur de service, un centre d'enregistrement de source de données et une composante de données d'utilisateur de service. La composante de données d'utilisateur de service reçoit une requête de recherche de données d'utilisateur de service, obtient un modèle de données d'utilisateur de service à partir de la composante de modèle de données d'utilisateur de service, obtient des informations d'enregistrement à partir du centre d'enregistrement de source de données, et recherche des données d'utilisateur de service correspondantes dans la source de données des données d'utilisateur de service conformément au modèle de données d'utilisateur de service obtenu et aux informations d'enregistrement obtenues. La gestion uniforme des données d'utilisateur de service est mise en œuvre par les solutions de la présente invention, et l'ouverture extérieure uniforme des données d'utilisateur de service est mise en œuvre par les interfaces de gestion fournies par le service de gestion de données d'utilisateur de service, de sorte que les données d'utilisateur de service requises sont gérées par l'intermédiaire du système de gestion de données d'utilisateur de service par système de service, par application, etc.
PCT/CN2010/076717 2009-09-17 2010-09-08 Système de gestion de données d'utilisateur de service et son procédé de mise en œuvre de gestion de données d'utilisateur de service WO2011032468A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910092964.2 2009-09-17
CN2009100929642A CN102026148A (zh) 2009-09-17 2009-09-17 业务用户数据管理系统及其实现业务用户数据管理的方法

Publications (1)

Publication Number Publication Date
WO2011032468A1 true WO2011032468A1 (fr) 2011-03-24

Family

ID=43758094

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/076717 WO2011032468A1 (fr) 2009-09-17 2010-09-08 Système de gestion de données d'utilisateur de service et son procédé de mise en œuvre de gestion de données d'utilisateur de service

Country Status (2)

Country Link
CN (1) CN102026148A (fr)
WO (1) WO2011032468A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7667003B2 (en) 2000-09-29 2010-02-23 Bristol-Myers Squibb Company Antibody directed to human mist (mast cell immunoreceptor signal transducer)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107133323A (zh) * 2017-05-04 2017-09-05 山东浪潮云服务信息科技有限公司 数据模型构建方法、政务服务业务的实现方法及装置
CN110457334A (zh) * 2019-07-31 2019-11-15 北京三快在线科技有限公司 信息推送方法、装置、电子设备及可读存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070061292A1 (en) * 2005-09-13 2007-03-15 Soufiane Azizi System and method of ready to render business intelligence result sets
CN1949763A (zh) * 2005-10-11 2007-04-18 北京航空航天大学 共享信息服务器系统
CN101083656A (zh) * 2007-07-05 2007-12-05 上海交通大学 基于数据流技术的多源异构数据集成系统
CN101174957A (zh) * 2007-10-09 2008-05-07 南京财经大学 面向异源数据的协同业务平台
US20090037236A1 (en) * 2007-07-31 2009-02-05 Oracle International Corporation Analytical reporting and data mart architecture for public organizations

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070208574A1 (en) * 2002-06-27 2007-09-06 Zhiyu Zheng System and method for managing master data information in an enterprise system
US8438238B2 (en) * 2002-10-16 2013-05-07 Sap Ag Master data access
CN101360345A (zh) * 2008-09-27 2009-02-04 中国移动通信集团设计院有限公司 一种数据业务的管理方法、装置及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070061292A1 (en) * 2005-09-13 2007-03-15 Soufiane Azizi System and method of ready to render business intelligence result sets
CN1949763A (zh) * 2005-10-11 2007-04-18 北京航空航天大学 共享信息服务器系统
CN101083656A (zh) * 2007-07-05 2007-12-05 上海交通大学 基于数据流技术的多源异构数据集成系统
US20090037236A1 (en) * 2007-07-31 2009-02-05 Oracle International Corporation Analytical reporting and data mart architecture for public organizations
CN101174957A (zh) * 2007-10-09 2008-05-07 南京财经大学 面向异源数据的协同业务平台

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7667003B2 (en) 2000-09-29 2010-02-23 Bristol-Myers Squibb Company Antibody directed to human mist (mast cell immunoreceptor signal transducer)

Also Published As

Publication number Publication date
CN102026148A (zh) 2011-04-20

Similar Documents

Publication Publication Date Title
EP2005709B1 (fr) Registre de services et système et procédé associés
CN100478943C (zh) 访问不同类型后端数据存储器的系统和方法
JP5193056B2 (ja) 無線装置の最新データを維持するための方法及びシステム
US9465819B2 (en) Distributed database
JP4088549B2 (ja) 電気通信網における方法
US20060234623A1 (en) System and method for efficient transfer of applications and data during device swap
CN101562578B (zh) 一种用户数据订阅通知方法及装置
US20090083210A1 (en) Exchange of syncronization data and metadata
WO2010006497A1 (fr) Système de liste d'adresses et procédé de mise en œuvre correspondant
CN102694824B (zh) 一种用户数据存储系统及其数据访问方法
CN110213156A (zh) 一种跨中心群组即时通信方法和系统
WO2010025653A1 (fr) Procédé, système, et dispositif de recherche d'information, et procédé d'inscription dans un moteur de recherche vertical
CN113157980A (zh) 数据同步方法、装置、设备和存储介质
CN104166661A (zh) 数据存储系统和数据存储方法
CN100396002C (zh) 一种利用关联查询进行鉴权的系统及其方法
WO2011032468A1 (fr) Système de gestion de données d'utilisateur de service et son procédé de mise en œuvre de gestion de données d'utilisateur de service
CN112965837B (zh) 配置和服务热重载更新方法、装置、计算机设备及存储介质
CN102316128A (zh) 一种用于生成网络服务的方法及装置
CN104714923B (zh) 一种实现设备共享的方法和装置
CN108681588A (zh) 一种接口访问实时统计方法及系统
CN112800066A (zh) 索引管理的方法、相关设备及存储介质
CN103460681B (zh) 融合地址薄能力的管理方法
CN1555164B (zh) 路由服务装置及应用该装置实现呼叫路由的方法和系统
WO2011032470A1 (fr) Service de gestion de données d'utilisateur de service et son procédé de réalisation de gestion de données d'utilisateur de service
CN108574592B (zh) 一种基于电信云的资源管理方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10816672

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10816672

Country of ref document: EP

Kind code of ref document: A1