CN107317693B - Service management equipment, device and method - Google Patents

Service management equipment, device and method Download PDF

Info

Publication number
CN107317693B
CN107317693B CN201610272872.2A CN201610272872A CN107317693B CN 107317693 B CN107317693 B CN 107317693B CN 201610272872 A CN201610272872 A CN 201610272872A CN 107317693 B CN107317693 B CN 107317693B
Authority
CN
China
Prior art keywords
service
database
user
user identifier
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201610272872.2A
Other languages
Chinese (zh)
Other versions
CN107317693A (en
Inventor
方圆
张优杨
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba China Co Ltd
Original Assignee
Alibaba China Co Ltd
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 Alibaba China Co Ltd filed Critical Alibaba China Co Ltd
Priority to CN201610272872.2A priority Critical patent/CN107317693B/en
Publication of CN107317693A publication Critical patent/CN107317693A/en
Application granted granted Critical
Publication of CN107317693B publication Critical patent/CN107317693B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50Network service management, e.g. ensuring proper service fulfilment according to agreements
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/33Querying
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computational Linguistics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The invention discloses a service management device, a device and a method, which are used for managing a second service based on first service data of a first service. Wherein, in response to receiving the first service data, the first service data is stored in a first database, the first service data including a user identifier of the corresponding user. In response to creating the second service, a service execution condition of the second service is acquired, first service data that meets the service execution condition is retrieved from the first database, and a user identifier thereof is extracted, and the extracted user identifier is stored in the second database in association with the second service. The invention can conveniently and efficiently meet the second service with special requirements based on the first service data.

Description

Service management equipment, device and method
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a service management device, an apparatus, and a method.
Background
When the single-database data of the server side is increased, in order to avoid single-point failure of the data or bottleneck problem of single-table retrieval, data storage is often performed in a mode of dividing databases and tables of service data, so that technical difficulty is brought to realization of some special requirements.
For example, the order form data is sorted according to the month of the order creation time, but the service sometimes requires to search for the qualification of the user within several years (for example, whether the user has successfully placed an order, and whether the user is in a common region for placing an order). For another example, the data of the red envelope table is sorted according to the tail number of the user obtaining the red envelope, but the service requires to search the user state (such as the game and the use machine type) when the red envelope is received.
In the face of these particular requirements, some large companies have adopted the following:
firstly, a retrieval middle layer (such as the TDDL in Ali and Atlas in 360) is added in a service layer and a data persistence layer, so that for service implementation, the service layer and the data persistence layer are faced with an integral data layer (a database-table-division strategy is transparent to an application), thereby reducing the difficulty of data retrieval for special requirements.
Second, a single database service (e.g., ODPS in ali, Spanner in google) is built by itself, such a service needs to satisfy data storage of any capacity and support data retrieval on the millisecond level.
Although the two schemes can meet some services with special requirements to a certain extent, both schemes have certain technical barriers, for example, at present, no single open-source database service exists, and the self-establishment of the service needs a lot of time and energy and deep accumulation of technology to be realized. And the first essence is to carry out secondary retrieval, and the second essence is to carry out data communication between servers crossing the computer room. Both of these schemes reduce data retrieval performance to some extent.
In summary, the two general schemes mentioned above have the meaning of a cow knife for killing chicken for realizing specific services, and the complexity of the two schemes mentioned above inevitably causes uncontrollable services.
Disclosure of Invention
The invention mainly aims to provide a service management device, a service management device and a service management method, which can simply and efficiently meet a second service with special requirements based on first service data of a first service.
According to an aspect of the present invention, a service management apparatus is disclosed for managing a second service based on first service data of a first service, the apparatus comprising: a memory; the communication module receives first service data; and a processor connected to the memory and the communication module, wherein the processor stores first service data in a first database on the memory in response to receiving the first service data, the first service data including a user identifier of a corresponding user, and the processor acquires a service execution condition of a second service in response to creating the second service, retrieves the first service data meeting the service execution condition from the first database, extracts the user identifier thereof, and stores the extracted user identifier in association with the second service in a second database on the memory.
Thus, a first service database containing user identifiers of users is established for a first service, user identifiers meeting or not meeting service execution conditions of a second service are extracted from the first service database according to the established second service, and the extracted user identifiers are stored in association with the second service. Thus, the information of the user who satisfies or does not satisfy the second service can be simply and quickly identified to determine whether the user performs the second service.
Preferably, in the case where the second service has been created, the processor may determine whether the first service data meets a service execution condition in response to receiving the first service data, extract a user identifier thereof in the case where the first service data meets the service execution condition, and store the extracted user identifier in the second database in association with the second service.
Therefore, after the second service is created, before the second service is executed or the second service is finished, the first service data can be continuously processed, whether the corresponding user meets the execution condition of the second service or not is judged, and then the second database is updated.
Preferably, after the second service is initiated, the processor may query, in response to a second service query request including a user identifier of the current user, in the second database whether the user identifier of the current user is stored in association with the second service, and determine whether to execute the second service for the current user according to a result of the query.
According to another aspect of the present invention, there is also disclosed a service management apparatus for managing a second service based on first service data of a first service, the apparatus comprising: a data storage unit, configured to store first service data in a first database in response to receiving the first service data, where the first service data includes a user identifier of a corresponding user; a service creation unit for creating a second service; a condition acquisition unit, configured to acquire a service execution condition of a second service in response to creating the second service; a retrieval unit, which is used for retrieving the first service data which accords with the service execution condition from the first database and extracting the user identifier; and a first association storage unit for storing the extracted user identifier in association with the second service in the second database.
Preferably, the apparatus may further comprise: a condition judging unit, configured to, in a case where the second service has been created, judge, in response to receiving the first service data, whether the first service data meets a service execution condition; an identifier extraction unit, which is used for extracting the user identifier of the first service data under the condition that the first service data accords with the service execution condition; and a second association storage unit for storing the extracted user identifier in association with the second service in the second database.
Preferably, the apparatus may further comprise: a service inquiry unit configured to, after starting the second service, inquire in the second database whether the user identifier of the current user is stored in association with the second service in response to a second service inquiry request including the user identifier of the current user; and the service determining unit is used for determining whether to execute the second service aiming at the current user according to the query result.
According to another aspect of the present invention, there is also provided a service management method for managing a second service based on first service data of a first service, the method including: in response to receiving the first service data, storing the first service data in a first database, the first service data including a user identifier of a corresponding user; responding to the establishment of the second service, and acquiring a service execution condition of the second service; retrieving first service data meeting service execution conditions from a first database and extracting a user identifier thereof; and storing the extracted user identifier in association with the second service in a second database.
Preferably, the method may further comprise: under the condition that the second service is created, responding to the received first service data, and judging whether the first service data meets the service execution condition; under the condition that the first service data accords with the service execution condition, extracting a user identifier of the first service data; and storing the extracted user identifier in association with the second service in a second database.
Preferably, the method may further comprise: after the second service is started, in response to a second service inquiry request containing the user identifier of the current user, inquiring in a second database whether the user identifier of the current user is stored in association with the second service; and determining whether to execute the second service for the current user according to the query result.
Preferably, the service execution condition is a condition for executing the second service, and in a case where the query result indicates that the user identifier of the current user is stored in the second database in association with the second service, it is determined that the second service is executed for the current user, and in a case where the query result indicates that the user identifier of the current user is not stored in the second database in association with the second service, it is determined that the second service is not executed for the current user; or the service execution condition is a condition that the second service is not executed, and in a case where the query result indicates that the user identifier of the current user is not stored in the second database in association with the second service, it is determined that the second service is executed for the current user, and in a case where the query result indicates that the user identifier of the current user is stored in the second database in association with the second service, it is determined that the second service is not executed for the current user.
Drawings
The above and other objects, features and advantages of the present disclosure will become more apparent by describing in greater detail exemplary embodiments thereof with reference to the attached drawings, in which like reference numerals generally represent like parts throughout.
Fig. 1 shows a schematic block diagram of a traffic management device according to an embodiment of the invention.
Fig. 2 shows a schematic flow diagram of a traffic management method according to an embodiment of the invention.
Fig. 3 shows a schematic block diagram of a traffic management device according to another embodiment of the present invention.
Fig. 4 shows a schematic flow diagram of a traffic management method according to another embodiment of the invention.
Fig. 5 shows a schematic block diagram of a traffic management device according to an embodiment of the invention.
Detailed Description
As mentioned above, based on the existing service data storage scheme, it may bring technical difficulties to the implementation of some services with special requirements (such as first individual reduction of services). In view of the above, the present invention provides a simple and efficient service data management scheme, which can manage a second service based on first service data of a first service, so that the second service with special requirements can be well satisfied.
The service data management scheme of the present invention can be implemented as a service management apparatus and method. Preferred embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Fig. 1 shows a schematic block diagram of a traffic management device according to an embodiment of the invention.
Fig. 2 shows a schematic flow diagram of a traffic management method according to an embodiment of the invention.
As shown in fig. 1, the service management apparatus 10 of the present invention includes a data storage unit 110, a service creation unit 120, a condition acquisition unit 130, a retrieval unit 140, and a first association storage unit 150.
As shown in fig. 2, in step S110, the first service data may be stored in the first database, for example, by the data storage unit 110, in response to receiving the first service data, wherein the first service data includes the user identifier of the corresponding user.
Here, the first service may be user ordering information, user participation activity information, and the like. Taking the game recharging information of the user as the first service, after the user finishes game recharging in the recharging system (cashier desk), the recharging system will generate a successful recharging order, in which the user identifier of the user is stored, and at this time, the data storage unit 110 can store the order in the first database. Preferably, the system can be used as a data center, the solr can automatically share and have cluster management construction capacity and lateral expansion capacity, and therefore enough data can be stored by the solr.
In step S120, a service execution condition of the second service may be acquired, for example, by the condition acquisition unit 130, in response to creating the second service.
Wherein the second service may be created by the service creation unit 120. The service execution condition corresponding to the second service may be a positive condition or a negative condition, that is, the service execution condition may be a condition for executing the second service or a condition for not executing the second service.
As mentioned above, the first service is the order placing information of the user, the second service may be a first order decreasing service, the corresponding service execution condition may be a preset positive condition that the first order time range is in, the first order decreasing applicable object is met, the transaction frequency/number of times in a specific time period is less than a predetermined value, and the user meeting the positive conditions may execute the second service.
In addition, the corresponding service execution condition may also be a negative condition that the service execution condition is not in the first order time range, does not conform to the first order used object, and the transaction frequency/number of times in a specific time period is greater than a predetermined value, and the user conforming to the negative condition does not execute the second service.
In step S130, the first service data meeting the service execution condition may be retrieved from the first database and the user identifier thereof may be extracted, for example, by the retrieving unit 140.
When the service execution condition is a positive condition, the user corresponding to the extracted user identifier is a white list user, and when the service execution condition is a negative condition, the user corresponding to the extracted user identifier is a black list user.
In step S140, the extracted user identifier may be stored in association with the second service in the second database, for example, by the first association storage unit 150.
After the user identifier that meets the service execution condition of the second service is extracted, it can be stored in association with the second service. Here, there may be a plurality of storage manners, for example, a user list corresponding to the second service may be established, a user identifier meeting the service execution condition is stored in the table, or a combination of the service identifier and the user identifier may be stored in pairs, all such combinations are searched in a subsequent query, and a KV database in which the service identifier of the second service is a key and the corresponding user list is a value may be established. The kv database is different from a general database in that it can permanently store data and ensure that data is not lost, and it has a pressure measurement capability against 5w TPS, so that a user identifier may be stored in the kv database in association with a second service as a preference.
Therefore, a first service database containing user identifiers of users is established for the first service, the user identifiers of the users meeting or not meeting the service execution conditions of the second service are extracted from the first service database according to the established second service, and the extracted user identifiers are stored in association with the second service, so that the information of the users meeting or not meeting the second service can be simply and quickly identified, and whether the users meet the conditions for executing the second service or not is judged.
Fig. 3 shows a schematic block diagram of a traffic management device according to another embodiment of the present invention.
Fig. 4 shows a schematic flow diagram of a traffic management method according to another embodiment of the invention.
As shown in fig. 3, the service management apparatus of the present invention may optionally include a condition judgment unit 310, an identifier extraction unit 320, and a second association storage unit 330.
As shown in fig. 4, in step S310, for example, the condition judgment unit 310 may judge whether the first service data meets the service execution condition in response to receiving the first service data in the case that the second service has been created.
While step S310 is executed, step S110 may also be executed simultaneously, that is, the first service data continues to be stored in the first database for later use when creating other second services.
As described above, the service execution condition may be a positive condition or a negative condition.
In step S320, for example, the identifier extracting unit 320 may extract the user identifier of the first service data when the first service data meets the service execution condition.
The extracted user identifier is a white list user when the service execution condition is a positive condition, and the extracted user identifier is a black list user when the service execution condition is a negative condition.
In step S330, the extracted user identifier may be stored in association with the second service in the second database, for example, by the second association storage unit 330.
Therefore, after the service creation unit 120 creates the second service, before the second service is executed or the second service is finished, the first service data may be further processed, whether the user corresponding to the first service data meets the second service execution condition is determined, and then the second database is updated.
In addition, when the second service is a service in which a user has only one chance (such as first individual decreasing activity), in the second service execution process, the user identifier corresponding to the second service data may also be set as a blacklisted user in response to the second service data. And when the white list user is stored in the second service database, the user identifier in the white list user is removed, and when the black list user is stored in the second service database, the user identifier is added. Thereby, the user can be prevented from repeatedly performing the second service.
As shown in fig. 3, the service management apparatus of the present invention may further optionally include a service querying unit 340 and a service determining unit 350.
Referring to fig. 4, in step S340, it may be queried, for example, by the service querying unit 340, after the second service is initiated, whether the user identifier of the current user is stored in association with the second service in the second database in response to the second service query request containing the user identifier of the current user.
In step S350, it may be determined, for example, by the service determination unit 350, whether to execute the second service for the current user according to the query result.
As described above, when the service execution condition is a positive condition, the service execution condition is a condition for executing the second service, and when the query result indicates that the user identifier of the current user is stored in the second database in association with the second service, it is determined that the second service is executed for the current user, and when the query result indicates that the user identifier of the current user is not stored in the second database in association with the second service, it is determined that the second service is not executed for the current user.
In addition, when the service execution condition is a reverse condition, the service execution condition is a condition that the second service is not executed. In case the query result indicates that the user identifier of the current user is not stored in the second database in association with the second service, it is determined that the second service is performed for the current user, and in case the query result indicates that the user identifier of the current user is stored in the second database in association with the second service, it is determined that the second service is not performed for the current user.
So far, the service management scheme of the present invention is described in detail with reference to fig. 1 to fig. 4, and in addition, the service management scheme of the present invention can also be implemented as the following service management device.
As shown in fig. 5, the traffic management device 50 of the embodiment of the present invention includes a memory 510, a communication module 520, and a processor 530.
The communication module 520 is configured to receive first service data. The processor 530 is connected to the memory 510 and the communication module 520.
The processor 530 stores the first service data in a first database on the memory 510 in response to receiving the first service data, the first service data including a user identifier of a corresponding user, and the processor 530 acquires a service execution condition of the second service in response to creating the second service, retrieves the first service data meeting the service execution condition from the first database, extracts the user identifier thereof, and stores the extracted user identifier in association with the second service in a second database on the memory 510.
In the case where the second service has been created, the processor 530 determines whether the first service data meets a service execution condition in response to receiving the first service data, extracts a user identifier thereof in the case where the first service data meets the service execution condition, and stores the extracted user identifier in association with the second service in the second database.
After initiating the second service, processor 530 may query, in response to a second service query request including the user identifier of the current user, whether the user identifier of the current user is stored in association with the second service in a second database, and determine whether to perform the second service for the current user according to the query result.
In addition, the service management device according to the embodiment of the present invention may also implement, through the processor, the scheme that is mentioned above in conjunction with fig. 1 to fig. 4 and is not mentioned here, and is not described here again.
It should be noted that the determination result of whether to execute the second service may also be sent through the communication module 520, so that the corresponding server, such as a cash register, determines whether to execute the second service.
In addition, the communication module 520 may further receive a request sent by the user to execute the second service (such as first standalone service), and in response to receiving the request of the user to execute the second service, the processor 530 queries the second database to determine whether the user satisfies a condition for executing the second service. The steps of querying and determining are described in detail above, and are not described herein again.
Therefore, the user only needs to send a request for executing the second service to the service management device of the invention, and the service management device inquires whether the user meets the condition of executing the second service, so that the user experience can be improved.
The service management device, apparatus and method according to the present invention have been described in detail above with reference to the accompanying drawings.
Furthermore, the method according to the invention may also be implemented as a computer program comprising computer program code instructions for carrying out the above-mentioned steps defined in the above-mentioned method of the invention. Alternatively, the method according to the present invention may also be implemented as a computer program product comprising a computer readable medium having stored thereon a computer program for executing the above-mentioned functions defined in the above-mentioned method of the present invention. Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems and methods according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Having described embodiments of the present invention, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen in order to best explain the principles of the embodiments, the practical application, or improvements made to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims (4)

1. A traffic management device, comprising:
a memory;
the communication module receives first service data;
a processor connected to the memory and the communication module,
wherein the processor stores first service data in a first database on the memory in response to receiving the first service data, the first service data including a user identifier of a corresponding user, and
the processor acquires a service execution condition of a second service in response to creating the second service, retrieves first service data that meets the service execution condition from the first database, extracts a user identifier thereof, and stores the extracted user identifier in association with the second service in a second database on the memory, thereby managing a user who will execute the second service based on whether the first service data of the first service meets the service execution condition;
after the second service is started, the processor responds to a second service query request containing a user identifier of a current user, queries whether the user identifier of the current user is stored in association with the second service in the second database, and determines whether the current user is allowed to execute the second service according to a query result;
before the second service is finished, the processor judges whether the first service data meets the service execution condition or not in response to receiving the first service data, extracts the user identifier of the first service data under the condition that the first service data meets the service execution condition, and stores the extracted user identifier in the second database in association with the second service.
2. A traffic management apparatus comprising:
a data storage unit, configured to store, in response to receiving first service data, the first service data in a first database, where the first service data includes a user identifier of a corresponding user;
a service creation unit for creating a second service;
a condition obtaining unit, configured to obtain a service execution condition of the second service in response to creating the second service;
a retrieval unit, configured to retrieve first service data that meets the service execution condition from the first database, and extract a user identifier thereof;
a first association storage unit operable to store the extracted user identifier in association with the second service in a second database so as to manage a user who will execute the second service based on whether or not first service data of a first service meets the service execution condition;
a service querying unit, configured to, after the second service is started, respond to a second service query request including a user identifier of a current user, query, in the second database, whether the user identifier of the current user is stored in association with the second service;
a service determining unit, configured to determine whether to allow the current user to execute the second service according to a query result;
a condition judging unit, configured to, before the second service is ended, respond to receipt of first service data, and judge whether the first service data meets the service execution condition;
an identifier extraction unit, configured to extract a user identifier of the first service data when the first service data meets the service execution condition; and
a second association storage unit for storing the extracted user identifier in association with the second service in the second database.
3. A method of service management, comprising:
in response to receiving first service data, storing the first service data in a first database, the first service data including a user identifier of a corresponding user;
responding to the establishment of a second service, and acquiring a service execution condition of the second service;
retrieving first service data meeting the service execution condition from the first database and extracting a user identifier thereof;
storing, in a second database, the extracted user identifier in association with the second service, thereby managing users who will execute the second service based on whether or not first service data of a first service meets the service execution condition;
after the second service is started, in response to a second service query request containing a user identifier of a current user, querying in the second database whether the user identifier of the current user is stored in association with the second service;
determining whether to allow the current user to execute the second service according to the query result;
before the second service is finished, responding to the received first service data, and judging whether the first service data meets the service execution condition;
under the condition that the first service data meets the service execution condition, extracting a user identifier of the first service data; and
storing the extracted user identifier in association with the second service in the second database.
4. The traffic management method according to claim 3,
the service execution condition is a condition for executing the second service, the second service is determined to be executed for the current user in a case where the query result indicates that the user identifier of the current user is stored in the second database in association with the second service, and the second service is determined not to be executed for the current user in a case where the query result indicates that the user identifier of the current user is not stored in the second database in association with the second service; or
The service execution condition is a condition in which the second service is not executed, the second service is determined to be executed for the current user in a case where the query result indicates that the user identifier of the current user is not stored in the second database in association with the second service, and the second service is determined not to be executed for the current user in a case where the query result indicates that the user identifier of the current user is stored in the second database in association with the second service.
CN201610272872.2A 2016-04-27 2016-04-27 Service management equipment, device and method Active CN107317693B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610272872.2A CN107317693B (en) 2016-04-27 2016-04-27 Service management equipment, device and method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610272872.2A CN107317693B (en) 2016-04-27 2016-04-27 Service management equipment, device and method

Publications (2)

Publication Number Publication Date
CN107317693A CN107317693A (en) 2017-11-03
CN107317693B true CN107317693B (en) 2021-06-22

Family

ID=60184479

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610272872.2A Active CN107317693B (en) 2016-04-27 2016-04-27 Service management equipment, device and method

Country Status (1)

Country Link
CN (1) CN107317693B (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101902761A (en) * 2010-07-14 2010-12-01 中兴通讯股份有限公司 Value added service promotion method and service data analysis device and system
CN104809110A (en) * 2014-01-23 2015-07-29 安徽海汇金融投资集团有限公司 Large data system

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102339422A (en) * 2011-01-29 2012-02-01 深圳市新希元软件技术有限公司 Method and system for modeling service object
US20130340037A1 (en) * 2012-06-19 2013-12-19 Wrench Monkey Designs Pte Ltd Data storage apparatus with authentification facility and a method of authentification

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101902761A (en) * 2010-07-14 2010-12-01 中兴通讯股份有限公司 Value added service promotion method and service data analysis device and system
CN104809110A (en) * 2014-01-23 2015-07-29 安徽海汇金融投资集团有限公司 Large data system

Also Published As

Publication number Publication date
CN107317693A (en) 2017-11-03

Similar Documents

Publication Publication Date Title
US10574752B2 (en) Distributed data storage method, apparatus, and system
WO2015188750A1 (en) Method, apparatus and system for implementing location based services
US10536456B2 (en) Method and system for identifying user information in social network
CN105653537B (en) Paging query method and device for database application system
US10503749B2 (en) Data processing method, device and system of query server
US20140351273A1 (en) System and method for searching information
CN105100050A (en) User permission management method and system
US20180232452A1 (en) Data retrieval method and system
CN109299101B (en) Data retrieval method, device, server and storage medium
WO2020143181A1 (en) Data storage method, apparatus, computer device and storage medium
EP3633519A1 (en) Method for storing objects, and object store gateway
CN104424352A (en) System and method for providing agent service to user terminal
CN106407395A (en) A processing method and device for data query
CN113377817A (en) Data processing method, system, device and storage medium
CN107317693B (en) Service management equipment, device and method
CN110798492B (en) Data storage method and device and data processing system
CN110909072B (en) Data table establishment method, device and equipment
CN108829735B (en) Synchronization method, device, server and storage medium for parallel execution plan
CN112612834B (en) Database middleware and method for connecting client and server
CN108874798B (en) Big data sorting method and system
CN111343101B (en) Server current limiting method, device, electronic equipment and readable storage medium
US20180018385A1 (en) System, data combining method, integration server, data combining program, database system ,database system cooperation method, and database system cooperation program
CN111061719B (en) Data collection method, device, equipment and storage medium
CN113254553A (en) Web map publishing method and system based on intelligent agent platform
CN108206933B (en) Video data acquisition method and device based on video cloud storage system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
TA01 Transfer of patent application right

Effective date of registration: 20200713

Address after: 310052 room 508, floor 5, building 4, No. 699, Wangshang Road, Changhe street, Binjiang District, Hangzhou City, Zhejiang Province

Applicant after: Alibaba (China) Co.,Ltd.

Address before: 510627 Guangdong city of Guangzhou province Whampoa Tianhe District Road No. 163 Xiping Yun Lu Yun Ping B radio square 14 storey tower

Applicant before: Guangzhou Dongjing Computer Technology Co.,Ltd.

TA01 Transfer of patent application right
GR01 Patent grant
GR01 Patent grant