WO2014101240A1

WO2014101240A1 - Data storage method and apparatus, data operation method and system, and access server

Info

Publication number: WO2014101240A1
Application number: PCT/CN2012/088144
Authority: WO
Inventors: 王世军; 张建勋; 黄堰姣
Original assignee: 华为技术有限公司
Priority date: 2012-12-31
Filing date: 2012-12-31
Publication date: 2014-07-03
Also published as: CN104040539A; CN104040539B

Abstract

A data storage method and apparatus, a data operation method and system, and an access server. The method includes that when a client subscribes a service and then the client becomes a user of the service, the method includes that: determined is that the client has opened an account; a first slice identifier included in a client identifier of the client is acquired, wherein the first slice identifier is a slice identifier of a client slice to which the client belongs; according to the first slice identifier, a user identifier including the first slice identifier is generated for the user, wherein the user identifier uniquely identifies the user in a user lifecycle, and the user lifecycle is a period from the time at which the user opens the account to the time at which the user logs out the account; according to the first slice identifier, a data source identifier corresponding to the first slice identifier is acquired from a slice and data source correspondence table; and user data is stored in the data source corresponding to the data source identifier, thus the access server acquire the user data from the data source corresponding to the first slice identifier according to the first slice identifier included in the user identifier.

Description

Data storage method and device, data operation method, system and access server

TECHNICAL FIELD The present invention relates to the field of communications technologies, and in particular, to a data storage method and apparatus, and a data operation method, system, and access server. BACKGROUND At present, there may be multiple users of the same group customer or family customer, or the same individual customer may have multiple users, such as: broadband users, fixed-line users, and mobile phone users. When storing these user data, the user data may be stored in different data sources. In some scenarios, when the service needs to access data of multiple users of the same group customer or home customer, it needs to access across data sources. And cross-data source access brings a lot of resource messages, and the efficiency of access is reduced. Summary of the invention

The embodiment of the present invention provides a data storage method and device, and a data operation method, a system, and an access server, so as to solve the problem that data of multiple users of the same client in the prior art is stored in different data sources, and when acquiring data, Issues that require access across data sources.

In order to solve the above technical problem, the embodiment of the present invention discloses the following technical solutions:

In a first aspect, a data storage method, when a customer subscribes to a service, when the client becomes a user of the service, the method includes: the data generating device determines that the client has opened an account, and obtains the first fragment identifier included in the customer identifier of the client The first fragment is identified as the fragmentation identifier of the customer's customer fragment, and the customer identifier uniquely identifies the customer during the customer's life cycle, and the customer life cycle refers to the period from the time the customer opens the account to the time the customer cancels the account; The generating device generates a user identifier including the first fragment identifier according to the first fragment identifier, where the user identifier uniquely identifies the user during the life cycle of the user, and the user life period refers to a period from after the user opens the account to before the user is turned off. The data generating device obtains the data source identifier corresponding to the first fragment identifier from the fragment data source correspondence table according to the first fragment identifier; and stores the user data in the data source corresponding to the data source identifier, so that The first fragment identifier is identified by the access server according to the first fragment identifier included in the user identifier. The corresponding data source obtains the user data, where the fragment data source correspondence table includes the correspondence between the fragment identifier of the client fragment and the data source identifier.

In a first possible implementation manner of the first aspect, the method further includes: the data generating device is configured according to the user's resources The number, from the routing table of the number segment, the second fragment identifier corresponding to the range of the number range of the resource number, wherein the routing table includes the correspondence between the fragment identifier and the range of the number of the resource number; The second fragment identifier, or the found second fragment identifier is inconsistent with the first fragment identifier, the data generating device adds the correspondence between the resource number and the first fragment identifier to the hash table in the database, The hash routing table includes a correspondence between the fragment identifier and a resource number that is not attributed to the routing table of the segment.

In combination with the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, before the customer subscribes to the service, the method further includes: when the customer opens an account, obtaining the tenant of the customer The data generating device obtains, according to the tenant identifier, a fragment identifier in the fragment identifier corresponding to the tenant identifier from the fragment data source correspondence table, and uses the obtained fragment identifier as the first fragment identifier, where The fragment data source correspondence table further includes a correspondence between the tenant identifier and the fragment identifier; the data generating device generates a client identifier including the first fragment identifier according to the first fragment identifier, and stores the client data in the first A slice identifies the corresponding data source, so that the access server obtains the data of the client from the data source corresponding to the first fragment identifier according to the first fragment identifier included in the client identifier.

In conjunction with the implementation of the first aspect, in a third possible implementation manner of the first aspect, the method further includes: when the data generating apparatus determines that the customer does not open an account, searching for the resource number from the number segment routing table according to the resource number of the user a second fragment identifier corresponding to the range of the number segment, wherein the number segment routing table includes a correspondence between the fragment identifier and the range of the number range of the resource number; when the data generating device finds the second fragment identifier, according to the second Fragment identification, generating a customer identifier including a two-slice identifier for the client, and generating a user identifier including the second fragment identifier for the user according to the second fragment identifier, and storing the customer data and the user data in the second score The data identifier corresponding to the slice identifier, so that the access server obtains the data of the client and/or the user from the data source corresponding to the second fragment identifier according to the second fragment identifier included in the client identifier and/or the user identifier. data.

In conjunction with the third possible implementation of the first aspect, in a fourth possible implementation manner of the first aspect, the method further includes: obtaining, when the second fragment identifier is not found, the tenant identifier of the tenant to which the customer belongs; The generating device obtains, according to the tenant identifier, a fragment identifier in the fragment identifier corresponding to the tenant identifier from the fragment data source correspondence table, and uses the obtained fragment identifier as the first fragment identifier, where the fragment data The source correspondence table further includes a correspondence between the tenant identifier and the fragment identifier. The data generating device generates a client identifier including the first fragment identifier according to the first fragment identifier, and generates a user identifier according to the first fragment identifier. a user identifier including a first fragment identifier; adding a correspondence between the resource number and the first fragment identifier to the hash routing table, where the hash routing table includes a fragment identifier and a resource not belonging to the segment routing table The correspondence between the numbers, and storing the data of the customer and the data of the user in the data source corresponding to the first fragment identifier, so as to facilitate access According to customer service identifier and / or user identifier identifying a first slice included in the slice corresponding to the identifier from the first data source Get customer data and/or user data.

With reference to the first aspect, the first possible, the second possible, the third possible or the fourth possible implementation of the first aspect, in a fifth possible implementation manner of the first aspect, the method further includes: The data generating device obtains all the fragment identifiers corresponding to the first data source identifier from the fragment data source correspondence table according to the first data source identifier; and identifies all the fragments corresponding to the first data source according to the relocation request. Select one or more fragment identifiers that meet the relocation requirements, and set the status of one or more fragment identifiers in the fragment data source correspondence table to the relocation status, so as to prohibit the network elements except the data generation device. Accessing data corresponding to one or more fragment identifiers; the data generating device relocates data in the first data source corresponding to one or more fragment identifiers to the second data source; and the data generating device deletes the data in the fragment data source correspondence table Corresponding relationship between the first data source identifier and one or more fragment identifiers; the data generating device adds a number in the fragment data source correspondence table Source identification data with more than one sub-identifier corresponding relationship between the sheet, and more than one fragment identified by the non-removal state setting state, in order to allow access to more than one fragment corresponding to the identification data.

A second aspect, a data operation method, comprising: an access server receives a data operation request sent by a data operation requesting device, where the data operation request includes an access number; and the access server obtains a customer corresponding to the access number according to the access number The fragmentation identifier of the slice; the access server obtains the data source identifier corresponding to the fragment identifier from the fragment data source correspondence table according to the fragment identifier corresponding to the access number, where the fragment data source correspondence table is saved The fragmentation identifier and the data source identifier; the access server sends the data operation request to the data source corresponding to the obtained data source identifier; and the access server receives the data operation response sent by the data source.

In a first possible implementation manner of the second aspect, obtaining the fragment identifier corresponding to the access number according to the access number, specifically: when the access number is a customer identifier or a user identifier, obtaining the client identifier or the user identifier If the access number is a resource number, the number of the fragment corresponding to the resource number is found in the hash routing table according to the resource number of the user, and when the fragment identifier corresponding to the resource number is found, If the fragment identifier of the resource number is not found, the fragment identifier corresponding to the number segment of the resource number is obtained in the routing table according to the resource number of the user, where the scatter number routing table includes The correspondence between the slice identifier and the resource number that is not attributed to the routing table of the number segment, and the routing table of the number segment includes the correspondence between the fragment identifier and the range of the number segment to which the resource number belongs.

In a third aspect, a data generating device includes: an obtaining module, a generating module, and a storage module, wherein the acquiring module is configured to: when the client subscribes to a service, when the client becomes a user of the service, determine that the client has opened an account and obtains The first fragment identifier included in the customer identifier of the customer, wherein the first fragment identifier is a fragment identifier of the customer fragment of the customer, the customer identifier uniquely identifies the customer during the customer life cycle, and the customer life cycle refers to the customer identifier After opening the account and before the customer cancels the account; the acquisition module is further used to send the inclusion to the generation module a user identifier generating request of the first fragment identifier; a generating module, configured to receive, by the acquiring module, a user identifier generating request that includes the first fragment identifier, and generate, according to the first fragment identifier, a first fragment identifier for the user The user identifier, the user identifier uniquely identifies the user during the life cycle of the user, and the user life cycle refers to the period from the time the user opens the account to the time before the user cancels the account; the obtaining module is further used to segment the data according to the first fragment identifier. The source correspondence table obtains the data source identifier corresponding to the first fragment identifier, and sends the data source identifier to the storage module. The storage module is configured to receive the data source identifier sent by the acquiring module, and store the user data in the data source. Identifying the corresponding data source, so that the access server obtains the user data from the data source corresponding to the first fragment identifier according to the first fragment identifier included in the user identifier, where the fragment data source correspondence table includes Correspondence between the fragmentation identifier of the client fragment and the data source identifier.

In a first possible implementation manner of the third aspect, the acquiring module is further configured to: search, according to the resource number of the user, the second fragment identifier corresponding to the range of the number segment to which the resource number belongs from the number segment routing table, and The storage module sends the query result, where the number segment routing table includes the correspondence between the fragment identifier and the range of the number range of the resource number; the storage module is further configured to receive the query result sent by the obtaining module, and determine, according to the query result, that the query cannot be found. If the second fragment identifier is different from the first fragment identifier, the corresponding relationship between the resource number and the first fragment identifier is added to the scatter table in the database, where The routing table contains the correspondence between the fragment identifier and the resource number that is not attributed to the routing table of the segment.

In a second possible implementation manner of the third aspect, the acquiring module is further configured to: before the customer subscribes to the service, the customer also obtains the tenant identifier of the customer when the customer opens the account, and according to the tenant identifier, the corresponding relationship from the fragment data source In the table, a fragment identifier of the fragment identifier corresponding to the tenant identifier is obtained, and the obtained fragment identifier is used as the first fragment identifier, where the fragment data source correspondence table further includes the tenant identifier and the fragment identifier. Corresponding relationship, and sending a client identity generation request including a first fragment identifier to the generating module; the generating module, configured to receive a client identity generation request that includes the first fragment identifier sent by the acquiring module, according to the first fragment identifier, The client generates a customer identifier that includes the first fragment identifier; the storage module is further configured to obtain, from the generating module, the first fragment identifier included in the client identifier, and store the data of the client in the data source corresponding to the first fragment identifier, In order for the access server to be from the first fragment according to the first fragment identifier included in the customer identifier Source identification data corresponding to the acquired customer data.

In a third possible implementation manner of the third aspect, the acquiring module is further configured to: when determining that the customer has not opened the account, according to the resource number of the user, searching for the second corresponding to the range of the number segment of the resource number according to the routing table of the number segment The fragment identifier is sent to the generating module, and the user identifier generating request including the second fragment identifier obtained by the query and the client identifier generating request including the second fragment identifier obtained by the query are sent to the generating module, where the fragment routing table includes the fragment identifier Corresponding relationship with the range of the number of the resource number; the generating module is further configured to receive the packet sent by the acquiring module a user identifier generation request including a second fragment identifier and a client identifier generation request including a second fragment identifier, and generating, by the second fragment identifier, a client identifier including the second fragment identifier according to the second fragment identifier; the acquiring module, further used for Obtaining, according to the second fragment identifier, the data source identifier corresponding to the second fragment identifier from the fragment data source correspondence table, and sending the data source identifier to the storage module; the storage module is further configured to store the customer data in the The second fragment identifies the corresponding data source, so that the access server obtains the data of the client from the data source corresponding to the second fragment identifier according to the second fragment identifier included in the client identifier.

In a fourth possible implementation manner of the third aspect, the acquiring module is further configured to: when determining that the customer has not opened the account, according to the resource number of the user, searching for the second corresponding to the range of the number of the resource number from the number segment routing table The segment identifier, where the segment routing table includes the correspondence between the fragment identifier and the range of the number of the resource number. When the second fragment identifier is not queried, the tenant identifier of the tenant to which the client belongs is obtained; and according to the tenant identifier, Obtaining, from the fragment data source correspondence table, a fragment identifier in the fragment identifier corresponding to the tenant identifier, and obtaining a fragment identifier as the first fragment identifier, where the fragment data source correspondence table further includes Corresponding relationship between the tenant identifier and the fragment identifier, and sending a user identifier generation request including the first fragment identifier and a client identifier generation request including the first fragment identifier to the generating module; the generating module is further configured to receive the sending by the acquiring module User identification generation request including the first fragment identification and customer identification generation including the first fragment identification And obtaining, by the first fragment identifier, a customer identifier that includes the first fragment identifier for the client; the storage module is further configured to add the correspondence between the resource number and the first fragment identifier to the hash routing table, where The scatter number routing table includes the correspondence between the fragment identifier and the resource number not attributed to the segment routing table, and stores the data of the client in the data source corresponding to the first fragment identifier, so that the access server is configured according to the customer identifier. The first fragment identifier included, and the data of the client is obtained from the data source corresponding to the first fragment identifier.

In a fifth possible implementation manner of the third aspect, the method further includes: a relocation module, configured to obtain, according to the first data source identifier, all the points corresponding to the first data source identifier from the fragment data source correspondence table According to the relocation requirement, one or more fragment identifiers that meet the relocation requirements are selected from all the fragment identifiers corresponding to the first data source identifier, and one or more fragment identifiers in the fragment data source correspondence table are identified. The data in the first data source corresponding to one or more fragment identifiers is relocated to the second data source. In the fragment data source correspondence table, the correspondence between the first data source identifier and one or more fragment identifiers is deleted; in the fragment data source correspondence table, the second data source identifier and one or more fragment identifiers are added. Correspondence relationship, and set the state of one or more slice identifiers to a non-relocation state, so as to allow access to more than one slice identifier corresponding to Data.

In a fourth aspect, an access server includes: a transceiver and a processor, where the transceiver is configured to receive a data operation request sent by a data operation requesting device, where the data operation request includes an access number, and sends the access number to the processor Sending an access number; a processor, configured to receive an access number sent by the transceiver, obtain a fragment identifier of the client fragment corresponding to the access number according to the access number; and according to the fragment identifier corresponding to the access number, The data source identifier corresponding to the fragment identifier is obtained, and the data source identifier is sent to the transceiver, where the fragment data source correspondence table holds the fragment identifier and the data source identifier; the transceiver, Further, the method is configured to receive a data source identifier sent by the processor, and send the data operation request to a data source corresponding to the data source identifier, and receive a data operation response sent by the data source.

In a first possible implementation manner of the fourth aspect, the processor is specifically configured to: when the access number is a customer identifier or a user identifier, obtain a fragment identifier included in the customer identifier or the user identifier; when the access number is a resource If the number is not the same as the resource number of the user, the shard ID corresponding to the resource number is found in the scatter number routing table. When the shard ID corresponding to the resource number is found, the shard ID is obtained. When the fragment is identified, the fragment identifier corresponding to the number segment to which the resource number belongs is obtained according to the resource number of the user, where the scatter number routing table includes the fragment identifier and the resource not attributed to the routing table of the number segment. The correspondence between the numbers and the number segment routing table includes the correspondence between the fragment identifier and the range of the number segment to which the resource number belongs.

A fifth aspect, a data operating system, comprising any data of the fourth aspect or the fourth aspect, the first possibility, the second possibility, the third possibility, the fourth possible or the fifth possible implementation Generating the apparatus and any of the first possible access servers as in the fifth aspect or the fifth aspect.

In the embodiment of the present invention, the first fragment identifier included in the user identifier generated by the data generating device and the first fragment identifier included in the client identifier are the same, and the same fragment identifier corresponds to the same data source, so that the user identifier can be implemented. The data of different users of the same customer is stored in the same data source, which solves the problem of accessing across data sources. DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings to be used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any inventive labor.

FIG. 1A is a schematic diagram of a scenario structure applied to an embodiment of the present invention; FIG.

FIG. 1B is a flowchart of an embodiment of a data storage method according to the present invention:

2 is a flow chart of another embodiment of a data storage method according to the present invention;

3 is a flow chart of another embodiment of a data storage method according to the present invention;

4 is a flow chart of an embodiment of a data relocation method according to the present invention; FIG. 5 is a flowchart of an embodiment of a data operation method according to the present invention; FIG.

Figure 6 is a block diagram of an embodiment of a data generating apparatus of the present invention;

Figure 7 is a block diagram of another embodiment of a data generating apparatus of the present invention;

Figure 8 is a block diagram of an embodiment of an access server of the present invention;

9 is a block diagram of another embodiment of an access server of the present invention;

Figure 10 is a block diagram of one embodiment of a data operating system of the present invention. detailed description

The following embodiments of the present invention provide a data storage method and apparatus, a data operation method, a system, and an access server.

The above-mentioned objects, features, and advantages of the embodiments of the present invention will become more apparent and understood. Give further details.

First, several technical terms in the embodiments of the present invention are introduced. A tenant refers to an operator that provides communication services in a certain area, for example: Beijing Telecom is a tenant 1, Beijing Mobile is a tenant 2, Beijing Unicom For tenants 3. Customer (customer) refers to an individual, group or legal organization that has signed an agreement with a tenant and has ordered or may order products and services provided by the tenant. The customer may be a consumer customer, such as a natural person; the customer may also be a group customer. (group customer), for example: a household customer or a corporate customer; a tenant contains a plurality of customers. When the customer opens an account, the data generating device generates a customer identification for the customer, and the customer identification uniquely identifies the customer during the customer life cycle, the customer life The period refers to the fragmentation identifier of the customer segment to which the customer belongs, from the time the customer opens the account to the time before the customer is posted. When a customer subscribes to a product or service at a tenant, the customer becomes a subscriber of the tenant. When the customer has processed multiple products or services, the customer becomes a plurality of users of the tenant, that is, one The customer can correspond to multiple users, and each user has a unique resource number. For example, the broadband user corresponds to a broadband number, and the mobile phone user corresponds to a mobile phone number. When the user opens an account, the client determines a resource number or the tenant allocates a resource number. For the customer, the data generating device generates a user identifier for the user, and the user identifier uniquely identifies the user during the life cycle of the user, and the user life cycle refers to the user identifier from the time the user opens the account to the time before the user accounts for the user. The fragment ID contained is the same as the fragment ID contained in the customer ID of the customer to which the user belongs. For example: A home customer can include broadband users, fixed-line users, and mobile phone users. Data source, used to store customer data and user data, such as: can be a database, a database diagram (Schema) or a database table (table). In the embodiment of the present invention, a customer segment is defined in advance. Each client segment can correspond to a certain number of customers. The segmentation identifier of the client segment can also be called the Customer Partition Index (CPI), and then each data segment can be assigned to each client segment. The data corresponding to the user identifier and/or the customer identifier of the fragment identifier of the client fragment may be stored in the data source corresponding to the fragment identifier. Wherein, each data source can correspond to at least one client fragment. The customer shards have a mapping relationship with the tenant, the customer, and the data source. One tenant corresponds to more than one customer shard, and the data source corresponding to each customer shard may be different, for example: customer shard 1 corresponds Data source 1, customer fragment 2 corresponds to data source 2.

In the embodiment of the present invention, a relationship table is also introduced, and a segment data source correspondence table generated based on a relationship between a client fragment and a data source is used, and the fragment data source correspondence table is used to save the client fragment. The correspondence between the fragment identifier and the data source identifier, and the correspondence between the fragment identifier and the tenant identifier of the tenant, where each data source identifier corresponds to at least one fragment identifier, and each tenant identifier corresponds to at least one fragment identifier. Further, the fragment data source correspondence table further includes a fragment identification status and a migration target data source identifier, and is used by the system to relocate the routing data according to the customer fragment, wherein the fragment identification status may indicate whether to relocate The status of the fragment identification status is 0 for the non-relocation status, and the fragment identification status is 1 for the relocation status. The migration destination data source identifier is the identifier of the target data source to which the routing data is migrated. The segment routing table is used to store the correspondence between the fragment identifier and the range of the number to which the resource number belongs. The range of the number segment is represented by the start number and the cutoff number, that is, the resource number between the start number and the cutoff number belongs to the The range of the number, the resource number here can be a mobile phone number, a broadband number or a fixed number. Further, the routing table of the segment may further include a tenant identifier corresponding to the fragment identifier, and an effective time and an expiration time of the routing table of the segment. The scatter table is initially empty. In the process of generating routing data, the scatter table will be used to store the correspondence between the shard ID and the resource number not attributed to the hop routing table. The access type and the access number are included, and the access type includes the type of access by the customer identifier, the type of access by the user identifier, or the type of access by the resource number. The access number may be a customer identifier, and the user identifier. Or the resource number, and the scatter table further includes the effective time and expiration time of the scatter table. The above-mentioned fragment data source correspondence table, the scatter number routing table, and the segment routing table may be stored locally in the data generating device, or may be separately stored in a database other than the data generating device.

FIG. 1A is a schematic diagram of a scenario architecture applied to an embodiment of the present invention:

The right side of Figure 1A shows the network entities involved in the data storage process, including the data generating device, and the database; the network entities involved in the data operation process, including the Gateway GPRS Support Node (GGSN), session description Session Description Protocol (SDP) Control Point, Access Server, and Database. The data generating device can be generally set in the operator's business hall; the above-mentioned fragment data source correspondence table, the segment routing table, and the scatter table are set in the database.

For the data storage process: the data generating device may save the correspondence between the fragment identifier and the data source identifier, and the correspondence between the fragment identifier and the tenant's tenant identifier to the fragment data source in the database according to the pre-planned client fragment. In the relationship table, the correspondence between the fragment identifier and the range of the number of the resource number is saved in the number segment routing table in the database; when the customer opens an account, or the customer's user opens an account, or the customer opens an account with the user at the same time, the data The generating device may generate a customer representation for the client and generate a user identifier for the user by searching a fragment data source correspondence table in the database, or a segment routing table; the data generating device may obtain the scatter resource number obtained in the process of generating the routing data. The correspondence with the fragment identifier is saved in the scatter table. The data maintenance module of the data generating device can also send the data of the client or the data of the user to the data source corresponding to the fragment identifier.

After receiving the data operation request, the GGSN or the SDP sends the data operation request to the access server, where the data operation request can query the data request, or add a data request, or delete the data request, etc., and the access server obtains the data operation request. The access number included in the data operation request is analyzed to obtain a fragment identifier, and the database is searched according to the fragment identifier, and the data source identifier corresponding to the fragment identifier is obtained, and the service corresponding to the access number is routed to The data source identifies the corresponding data source.

The database can be one or more. If there are multiple databases, the consistency of various data and routing tables maintained by each database through data synchronization. The database can contain multiple data sources. The data sources can also be independent and can be located outside the database. For example: The data source that stores customer data and user data can be a separate database located outside the database.

The embodiments of the data storage method and the data acquisition method of the present invention are described in detail below in conjunction with the above.

Referring to FIG. 1B, it is a flowchart of an embodiment of a data storage method according to the present invention. When a client subscribes to a service, when the client becomes a user of the service, the method includes:

Step 101: The data generating apparatus determines that the customer has opened an account, and obtains a first fragmentation identifier included in the customer identifier of the customer, where the first fragmentation identifier is a fragmentation identifier of the customer fragment of the customer, and the customer identifier is in the customer life cycle. Uniquely identifies the customer. The customer life cycle refers to the period from the time the customer opens the account to the time the customer cancels the account. In this embodiment, the customer has opened an account and has generated the customer ID of the customer. At this time, the customer subscribes to a certain customer. During the service, the customer may select a resource number or the tenant allocates a resource number to the client. The data generating device obtains the first fragment identifier included in the client identifier, and the first fragment identifier may be a prefix of the client identifier. It can also be the suffix of the customer ID, or the number of specific locations in the customer ID. For example, the first five digits of the eighteen customer identification are the first fragment identification.

Optional: Before the customer subscribes to the service, the method further includes: obtaining, by the customer, the tenant identifier of the customer when the account is opened; the data generating device obtains the fragment identifier corresponding to the tenant identifier from the correspondence data source correspondence table according to the tenant identifier a fragment identifier, the obtained fragment identifier is used as the first fragment identifier, where the fragment data source correspondence table further includes a correspondence between the tenant identifier and the fragment identifier; and the data generating device is configured according to the first fragment. And identifying, by the customer, the customer identifier that includes the first fragment identifier, and storing the data of the client in the data source corresponding to the first fragment identifier, so that the access server is configured according to the first fragment identifier included in the client identifier. The customer's data is obtained from the data source corresponding to the first fragment identification.

Step 102: The data generating device generates, according to the first fragment identifier, a user identifier that includes the first fragment identifier, where the user identifier uniquely identifies the user during the user lifetime, and the user life cycle refers to the user after the account is opened to the user. During the period before the household.

Step 103: The data generating device obtains, according to the first fragment identifier, the data source identifier corresponding to the first fragment identifier from the fragment data source correspondence table, and stores the user data in the data source corresponding to the data source identifier. The access server obtains the user data from the data source corresponding to the first fragment identifier according to the first fragment identifier included in the user identifier, where the fragment data source correspondence table includes the fragment identifier of the client fragment. Correspondence with the data source identifier.

Optionally, the data generating device searches, according to the resource number of the user, the second fragment identifier corresponding to the range of the number range of the resource number from the routing table of the number segment, where the routing table includes the fragment identifier and the resource number. Corresponding relationship between the range of the number of segments; determining that the second fragment identifier is not found, or the second fragment identifier that is found is inconsistent with the first fragment identifier, the correspondence between the resource number and the first fragment identifier by the data generating device Add to the scatter table in the database, where the scatter table contains the correspondence between the shard ID and the resource number that is not attributed to the hop routing table.

Optionally, the data generating device determines, according to the resource number of the user, the second fragment identifier corresponding to the range of the number segment to which the resource number belongs according to the resource number of the user, where the routing table of the number segment includes Corresponding relationship between the slice identifier and the range of the number of the resource number; when the second fragment identifier is found, the data generating device generates a customer identifier including the second fragment identifier for the client according to the second fragment identifier, and according to the second a fragment identifier, generating a user identifier including a second fragment identifier for the user, and storing the data of the client and the data of the user in a data source corresponding to the second fragment identifier, so that the access server is configured according to the client identifier and/or The second fragment identifier included in the user identifier acquires data of the client and/or data of the user from a data source corresponding to the second fragment identifier.

Optionally, when the second fragment identifier is not found, obtaining the tenant identifier of the tenant to which the client belongs; data generation The device obtains a fragment identifier in the fragment identifier corresponding to the tenant identifier from the fragment data source correspondence table according to the tenant identifier, and uses the obtained fragment identifier as the first fragment identifier, where the fragment data source is The correspondence relationship table further includes a correspondence between the tenant identifier and the fragment identifier. The data generating device generates a client identifier including the first fragment identifier for the client according to the first fragment identifier, and generates the inclusion for the user according to the first fragment identifier. a user identifier of the first fragment identifier; adding a correspondence between the resource number and the first fragment identifier to the scatter number routing table, where the scatter number routing table includes the fragment identifier and the resource number not attributed to the segment routing table Corresponding relationship, and storing the data of the client and the data of the user in the data source corresponding to the first fragment identifier, so that the access server according to the first fragment identifier included in the customer identifier and/or the user identifier, from the first A slice identifies the data of the customer and/or the data of the user in the corresponding data source.

Optionally, the data generating device obtains, according to the first data source identifier, all the fragment identifiers corresponding to the first data source identifier from the fragment data source correspondence table; and corresponding to the first data source identifier according to the relocation request Select one or more fragment identifiers that meet the relocation requirements in all the fragment identifiers, and set the status of one or more fragment identifiers in the fragment data source correspondence table to the relocation status, so as to prohibit the data generation device from being disabled. The outer network element accesses data corresponding to one or more fragment identifiers; the data generating device relocates data in the first data source corresponding to one or more fragment identifiers to the second data source; and the data generation device corresponds to the fragment data source In the table, the correspondence between the first data source identifier and one or more fragment identifiers is deleted, and the data generating device adds a correspondence between the second data source identifier and one or more fragment identifiers in the fragment data source correspondence table, and The status of one or more fragment identifiers is set to a non-relocation state, so as to allow access to the number corresponding to one or more fragment identifiers. according to.

Referring to FIG. 2, it is a flowchart of another embodiment of a data storage method according to the present invention, including:

Step 201: When the customer opens an account, the data generating device obtains the tenant identifier of the tenant to which the customer belongs; after the customer selects a tenant, the customer opens the account under the tenant, so the data generating device naturally obtains the tenant identifier of the tenant to which the customer belongs.

Step 202: The data generating device acquires a fragment identifier in the fragment identifier corresponding to the tenant identifier, and uses the obtained fragment identifier as the first fragment identifier.

The data generating device may randomly select one fragment identifier from all the fragment identifiers, or determine the requirements of the data source according to the attributes of the client, and then select a data source that meets the requirements, and the correspondence table from the fragment data source. The segment identifier corresponding to the data source identifier of the data source is determined. For example: the data generating device identifies that the customer is an important customer, and the security requirement level of the customer data is the highest level, and selects the highest-level security data source from the plurality of data sources to store the customer corresponding to the fragment identifier. Data or user data, and from the fragment data source correspondence table, determine the fragment identifier corresponding to the data source identifier of the data source.

Step 203: The data generating apparatus generates, according to the first fragment identifier, a first fragment identifier for the client. The customer identifier is stored in the data source corresponding to the first fragmentation identifier, and the customer identifier is the unique identifier of the customer during the life cycle of the customer, and the customer life cycle is from the time the customer opens the account to the time before the customer cancels the account. Throughout the period.

In various embodiments of the present invention, the first fragment identifier may be used as a prefix of the customer identifier, or may be used as a suffix of the customer identifier, and may also be a specific digit of the customer identifier, for example, the customer identifier is an 18-digit number. The first 1-4 bits are the first slice identifier, and the fifth bit is the type flag. For example, the type flag bit 0 indicates the client identifier, and the 6-18 bits are the sequence numbers generated according to certain rules.

The customer's data here can be the customer identification, the customer's name left by the customer when opening the account, the customer's home address, the customer's work unit, and so on.

After the customer has opened an account, the data storage process of the customer's user when opening an account includes:

Step 204: When the client subscribes to a certain service, that is, when the customer becomes a user of the service, the data generating device obtains the first fragment identifier included in the customer identifier of the customer.

When a customer subscribes to a service, the customer can select a resource number or a tenant to slice a resource number for the user, such as a mobile phone number, a broadband number, or a Subscriber Identity Module (SIM) card number.

Step 205: Generate, according to the obtained first fragment identification data generating device, a user identifier that includes the first fragment identifier, and save the user data in a data source corresponding to the first fragment identifier, so as to facilitate The access server obtains data of the user from the data source corresponding to the first fragment identifier according to the first fragment identifier included in the user identifier.

The user's data may include the resource number, the type of service of the user, the type of the service, the validity period of the user's business, and the like.

In various embodiments of the present invention, the first fragment identifier may be a prefix of the user identifier, or may be a suffix of the user identifier, or may be a specific digit of the user identifier, for example, the user identifier is an 18-digit number. The first 1-4 bits are the first fragment identification, and the fifth digit is the type identifier. For example, the type flag bit 1 indicates the user identifier, the 6-18 bits are the sequence number generated according to a certain rule, or the resource number of the user.

Step 206: According to the resource number of the user, the data generating device searches for the second fragment identifier corresponding to the range of the number segment of the resource number.

Step 207: If the data generating device does not find the second fragment identifier, or if the second fragment identifier found by the data generating device is inconsistent with the first fragment identifier, the data generating device saves the resource in the hash routing table. The correspondence between the number and the first fragment ID.

For example, when a user transfers a number to another tenant, the number of segments in the routing table is The resource number is not included in the scope. Or the second fragment identifier corresponding to the range of the number segment, that is, the second CPI, is obtained when the range of the number of the segment number includes the resource number. The data generating apparatus needs to determine the second fragment identifier and the first fragment that are found because the first fragment identifier selected may be different from the second fragment identifier that is found according to the resource number when the client opens the account. If the identifier is consistent, if the second fragment identifier found by the data generating device is inconsistent with the first fragment identifier, the data generating device saves the correspondence between the resource number and the first fragment identifier in the hash routing table, and thereafter The fragment identifier corresponding to the resource number is the first fragment identifier. Therefore, the subsequent access server searches for the fragment identifier corresponding to the user by using the resource number, and needs to first search from the hash table, and then the slave segment routing table. If the second fragment identifier that is found by the data generating device is consistent with the first fragment identifier, the correspondence between the range of the number segment to which the resource number belongs and the first fragment identifier is pre-stored. Therefore, the data generating device does not need to save the range of the number segment to which the resource number belongs and the first fragment identifier in the routing table. Correspondence relationship.

Referring to FIG. 3, it is a flowchart of another embodiment of a data storage method according to the present invention. The embodiment shows that when a customer accounts for a service, the customer subscribes to a certain service, that is, the customer becomes a user of the service, and the data storage. Process:

Step 301: According to the resource number of the user, look up the second fragment identifier corresponding to the range of the number segment to which the resource number belongs from the routing table of the number segment.

Step 302: Determine whether the second fragment identifier is found. When the second fragment identifier is found, step 303 is performed. When the second fragment identifier is not found, step 304 is performed.

Step 303: When the second fragment identifier is found, generate a client identifier that includes the second fragment identifier for the client according to the second fragment identifier, and generate a second fragment identifier for the user according to the second fragment identifier. a user identifier, and storing the data of the client and the data of the user in a data source corresponding to the second fragment identifier, so that the access server is configured according to the second fragment identifier included in the customer identifier and/or the user identifier. The data source of the customer and/or the data of the user are obtained from the data source corresponding to the two-slice identification.

Step 304: When the second fragment identifier is not found, obtain the tenant identifier of the tenant to which the client belongs.

For example, when a user transfers a number to a tenant and transfers from one tenant to another tenant, the range of any number in the routing table of the number segment does not include the resource number.

Step 305-step 307: The same as steps 202-204, and details are not described herein again.

Step 308: The data generating apparatus generates a user identifier including the first fragment identifier for the user according to the first fragment identifier, and saves the correspondence between the resource number and the first fragment identifier in the hash routing table, and the user's The data is stored in the data source corresponding to the first fragment identifier, so that the access server obtains the data of the user from the data source corresponding to the first fragment identifier according to the first fragment identifier included in the user identifier. As can be seen from the embodiment shown in FIG. 1B to FIG. 3, since the customer identifier and the user identifier include the same fragmentation identifier of the client fragment, and one fragment corresponds to a data source, the data of the client can be User data is stored in the same data source. And according to the attributes of the customer, the requirements of the data source can be determined, so that the data source that meets the requirements can be flexibly allocated to the customer and the user.

Referring to FIG. 4, any method embodiment of data storage based on FIG. 1B-3 is a flowchart of an embodiment of a data migration method according to the present invention. The embodiment shows a process of data migration in units of client shards: 401: The data generating device obtains, according to the first data source identifier, all the fragment identifiers corresponding to the first data source identifier from the fragment data source correspondence table.

For example: When the data of the customer and the data of the user included in the first data source are continuously increased, the basic resource of the first data source may not be able to support all the customers under it, and some data under the first data source is needed. After being relocated to the second data source, in the embodiment of the present invention, since the customer is fragmented, the data relocation and migration can be performed in units of customer fragments.

Step 402: According to the relocation request, select one or more fragment identifiers that meet the relocation requirement from all the fragment identifiers corresponding to the first data source identifier, and set the status of one or more fragment identifiers in the fragment data source correspondence table. It is set to the relocation state, so that the network element other than the data generating device is prohibited from accessing data corresponding to one or more fragment identifiers.

For example, the data corresponding to the customer segment of the first data source that exceeds 1% of the data source may be relocated, or the data of the important customer in the first data source may be requested to be relocated, or may be required. Randomly relocate the corresponding data of half of the fragment IDs of all the fragment identifiers.

When one or more fragment identifiers that meet the requirements are selected from all the fragment identifiers corresponding to the first data source identifier according to the relocation request, one or more fragments in the corresponding data source correspondence table need to be separately selected. The status of the logo is set to the relocation status.

Step 403: Relocate data in the first data source corresponding to one or more slice identifiers to the second data source.

Step 404: In the fragment data source correspondence table, delete the correspondence between the first data source identifier and one or more fragment identifiers. In the fragment data source correspondence table, add the second data source identifier and one or more fragments. Corresponding relationship of the identifiers, and setting the status of one or more fragment identifiers to a non-relocation state, so as to allow the network element to access data corresponding to more than one fragment identifier.

It can be seen from the foregoing embodiment that, in the data migration, since the correspondence between the resource number, the customer identifier, the user identifier, and the fragment identifier does not need to be changed, only the mapping of the fragment identifier and the data source identifier of the relocated client fragment needs to be modified. The relationship is OK, and the mapping relationship between the fragment identifier and the data source identifier is small, so it is reduced during the relocation. There is less modification of routing data, and the relocated customer shards do not affect the business of other customer shards, thus reducing the complexity of customer relocation.

Referring to FIG. 5, it is a flowchart of an embodiment of a data operation method according to the present invention. The embodiment is based on any of the foregoing data storage method embodiments of FIG.

Step 501: The access server receives a data operation request sent by the data operation requesting device, and the data operation request includes an access number.

The data operation requesting device may be a GGSN or another access device such as an SDP.

Step 502: The access server obtains a fragment identifier of the client fragment corresponding to the access number according to the access number. When the access number is a customer identifier or a user identifier, obtain a fragment identifier included in the customer identifier or the user identifier;

When the access number is the resource number, the fragment identifier corresponding to the resource number is searched in the hash routing table according to the resource number of the user, and the fragment identifier is obtained when the fragment identifier corresponding to the resource number is found; When the fragment identifier corresponding to the resource number is found, the fragment identifier corresponding to the number segment to which the resource number belongs is obtained according to the resource number of the user, where the scatter number routing table includes the fragment identifier and the non-attribute to The correspondence between the resource numbers of the routing table of the number segment, and the routing table of the number segment includes the correspondence between the fragment identifier and the range of the number segment to which the resource number belongs.

Step 503: The access server obtains a data source identifier corresponding to the fragment identifier from the fragment data source correspondence table according to the fragment identifier corresponding to the access number, where the fragment data source correspondence table holds the fragment identifier. With the data source ID.

Step 504: The access server sends a data operation request to the data source corresponding to the obtained data source identifier.

Step 505: The access server receives a data operation response sent by the data source.

It can be seen from the foregoing embodiment that when routing data generated according to an embodiment of the present invention is routed, fast routing of multiple access numbers is implemented, and routing flexibility is improved.

Corresponding to embodiments of the data storage method and data manipulation method of the present invention, the present invention also provides an embodiment of a data generation apparatus, system, and access server. Referring to FIG. 6, based on the method embodiment of FIG. 1B-5 above, a block diagram of an embodiment of the data generating apparatus of the present invention is shown:

The device includes: an apparatus comprising: an obtaining module 610, a generating module 620, and a storage module 630, wherein the obtaining module 610 is configured to: when the client subscribes to a service, when the client becomes a user of the service, determine The customer has opened an account and obtained the first fragmentation identifier included in the customer's customer identification. The first fragmentation identifier is the fragmentation identifier of the customer's customer segment. The customer identifier uniquely identifies the customer during the customer's life cycle. Refers to the period from the time the customer opens the account to the time before the customer cancels the account;

The obtaining module 610 is further configured to send, to the generating module 620, a user identifier generating request that includes the first fragment identifier;

The generating module 620 is configured to receive the user identifier generating request that includes the first fragment identifier, and generate, according to the first fragment identifier, a user identifier that includes the first fragment identifier, where the user identifier is in the user life cycle. The user is uniquely identified, and the user life cycle refers to the period from the time the user opens the account to the time before the user cancels the account;

The obtaining module 610 is further configured to obtain, according to the first fragment identifier, the data source identifier corresponding to the first fragment identifier from the fragment data source correspondence table, and send the data source identifier to the storage module 630;

The storage module 630 is configured to receive the data source identifier sent by the obtaining module 610, and store the data of the user in a data source corresponding to the data source identifier, so that the access server obtains the first fragment identifier according to the user identifier. The user data is obtained from the data source corresponding to the first fragment identifier, where the fragment data source correspondence table includes the correspondence between the fragment identifier of the client fragment and the data source identifier.

Optionally, the obtaining module 610 is further configured to: search, according to the resource number of the user, the second fragment identifier corresponding to the range of the number segment to which the resource number belongs from the routing table, and send the query result to the storage module 630, where The segment routing table includes a correspondence between the fragment identifier and the range of the number segment to which the resource number belongs. Correspondingly, the storage module 630 is further configured to receive the query result sent by the obtaining module 610, and determine, according to the query result, that the second score is not found. If the slice identifier, or the found second fragment identifier is inconsistent with the first fragment identifier, add the correspondence between the resource number and the first fragment identifier to the scatter number routing table in the database, where the scatter number routing table Contains the correspondence between the fragment identifier and the resource number that is not attributed to the segment routing table.

Optionally, the obtaining module 610 is further configured to: before the customer subscribes to the service, the customer obtains the tenant identifier of the customer when the customer opens the account, and obtains the corresponding point of the tenant identifier from the corresponding data of the fragment data source according to the tenant identifier. A slice identifier of the slice identifier, the obtained fragment identifier is used as the first fragment identifier, where the fragment data source correspondence table further includes a correspondence between the tenant identifier and the fragment identifier, and is sent to the generating module 620. a client identifier generation request including a first fragment identifier; correspondingly, the generating module 620 is configured to receive a client identifier generation request that includes the first fragment identifier sent by the obtaining module 610, and generate the inclusion for the client according to the first fragment identifier. The customer identifier of the first fragment identifier; correspondingly, the storage module 630 is further configured to obtain, by the generating module 620, the first fragment identifier included in the client identifier, and store the data of the client in the data source corresponding to the first fragment identifier. In order to facilitate the access server according to the first fragment identifier included in the customer identifier, from the first fragment Identify the data of the customer in the corresponding data source.

Optionally, the obtaining module 610 is further configured to: when the customer is not open, according to the resource number of the user, the second fragment identifier corresponding to the range of the number segment of the resource number is searched from the routing table of the number, and the generating module 620 is configured. Sending a user identity generation request including the second fragment identifier obtained by the query and a client identity generation request including the second fragment identifier obtained by the query, where the number segment routing table includes the fragment identifier and the range of the number range of the resource number Correspondingly, the generating module 620 is further configured to receive, by the acquiring module, a user identifier generating request that includes the second fragment identifier and a client identifier generating request that includes the second fragment identifier, according to the second fragment identifier, The client generates a customer identifier that includes the second fragment identifier, and generates a user identifier that includes the second fragment identifier for the user according to the second fragment identifier. The obtaining module 610 is further configured to use the second fragment identifier from the fragment. The data source correspondence table obtains the data source identifier corresponding to the second fragment identifier, and the data source identifier The storage module 630 is further configured to store the data of the client and the data of the user in a data source corresponding to the second fragment identifier, so that the access server is configured according to the client identifier and/or the user identifier. The second fragment identifier included in the method, the customer data and/or the user data are obtained from the data source corresponding to the second fragment identifier.

Optionally, the obtaining module 610 is further configured to: when determining that the customer has not opened the account, according to the resource number of the user, the second fragment identifier corresponding to the range of the number range of the resource number is obtained from the routing table of the number segment, where the number of the route is The table contains the corresponding relationship between the fragment ID and the range of the number of the resource number. When the second fragment ID is not queried, the tenant ID of the tenant to which the customer belongs is obtained; and according to the tenant ID, from the fragment data source correspondence table And obtaining a fragment identifier in the fragment identifier corresponding to the tenant identifier, and the obtained fragment identifier is used as the first fragment identifier, where the fragment data source correspondence table further includes a correspondence between the tenant identifier and the fragment identifier. And generating, by the generating module 620, a user identifier generating request that includes the first fragment identifier and a client identifier generating request that includes the first fragment identifier; and correspondingly, the generating module 620 is further configured to receive, by the acquiring module 610, the first a user identification generation request for the fragment identification and a customer identification generation request including the first fragment identification. Correspondingly, the storage module 630 is further configured to add the correspondence between the resource number and the first fragment identifier to the scatter number routing table, according to the first fragment identifier, The scatter number routing table includes a correspondence between the shard ID and the resource number that is not attributed to the hop routing table, and the customer data is stored in the data source corresponding to the first shard identifier, so that the access server is based on the client. The first fragment identifier included in the identifier and/or the user identifier is obtained from the data source corresponding to the first fragment identifier.

Optionally, as shown in FIG. 7, the data generating apparatus further includes: a relocation module 640, configured to obtain, according to the first data source identifier, all the points corresponding to the first data source identifier from the fragment data source correspondence table. Slice identification; According to the relocation requirement, select one of the fragmentation identifiers corresponding to the first data source identifier that meets the relocation requirements. The above fragment identifiers are set, and the state of one or more fragment identifiers in the fragment data source correspondence table is set to a relocation state, so as to prohibit the network elements other than the data generating device from accessing one or more fragment identifiers. Data: The data in the first data source corresponding to one or more slice identifiers is relocated to the second data source; in the data source correspondence table, the correspondence between the first data source identifier and one or more fragment identifiers is deleted. The corresponding relationship between the second data source identifier and one or more fragment identifiers is added in the fragment data source correspondence table, and the state of one or more fragment identifiers is set to a non-relocation state, so as to allow access to more than one point. The slice identifies the corresponding data.

Referring to FIG. 8, a block diagram of an embodiment of the access server according to the foregoing FIG. 1B-5 is a block diagram of an embodiment of an access server according to the present invention. The method includes: a transceiver 810 and a processor 820, where

The transceiver 810 is configured to receive a data operation request sent by the data operation requesting device, where the data operation request includes an access number, and send the access number to the processor 820;

The processor 820 is configured to receive an access number sent by the transceiver 810, obtain a fragment identifier of the client fragment corresponding to the access number according to the access number, and obtain the fragmentation data according to the fragment identifier corresponding to the access number. In the source correspondence table, the data source identifier corresponding to the fragment identifier is obtained, and the data source identifier is sent to the transceiver 810, where the fragment data source correspondence table stores the fragment identifier and the data source identifier;

The transceiver 810 is further configured to receive the data source identifier sent by the processor 820, and send the data operation request to the data source corresponding to the data source identifier, and receive the data operation response sent by the data source.

Optionally, the processor 820 is specifically configured to: when the access number is a customer identifier or a user identifier, obtain a fragment identifier included in the customer identifier or the user identifier; when the access number is a resource number, according to the user The resource number, in the hash routing table, the fragment identifier corresponding to the resource number, and when the fragment identifier corresponding to the resource number is found, the fragment identifier is obtained; when the fragment identifier corresponding to the resource number is not found, And obtaining, according to the resource number of the user, the fragment identifier corresponding to the number segment to which the resource number belongs, where the scatter number routing table includes the correspondence between the fragment identifier and the resource number not attributed to the routing table of the number segment. The segment routing table contains the correspondence between the fragment identifier and the range of the number segment to which the resource number belongs.

Referring to FIG. 9, which is a block diagram of an embodiment of a data generating apparatus according to the present invention, the data generating apparatus in the embodiment of the present invention may be implemented based on a computer system, and the method shown in FIG. 1B-4 may be in a data generating apparatus based on a computer system. achieve. The data generating apparatus in this embodiment may include: a processor 901, a memory 902, and a communication interface 903. The memory 902 is used to store program codes. The processor 901 is configured to execute program code stored in the memory 902. In an embodiment of the present invention, the memory 902 stores the first program code, and the processor 901 is configured to execute the first program code, and the following operations are performed: when the client subscribes to a service, when the client becomes a user of the service, the method includes The customer has opened an account and obtained the first fragmentation identifier included in the customer's customer identification. The first fragmentation identifier is the fragmentation identifier of the customer's customer fragment. The customer identifier is only in the customer life cycle. A customer identification, the customer life cycle refers to the period from the customer opening the account to the customer before the customer is posted; according to the first fragment identification, the user identifier containing the first fragment identification is generated for the user, and the user identifier is in the user life cycle. Uniquely identifies the user. The user lifetime refers to the period from the time the user opens the account to the time before the user cancels the account. According to the first fragment identifier, the data source identifier corresponding to the first fragment identifier is obtained from the fragment data source correspondence table. And storing the user data in the data source corresponding to the data source identifier, so that the access server obtains the user data from the data source corresponding to the first fragment identifier according to the first fragment identifier included in the user identifier. The fragment data source correspondence table includes a correspondence between the fragment identifier of the client fragment and the data source identifier. The communication interface 903 is configured to communicate with an external device, such as with an access server. Messages that interact between the data generating device and the access server (as shown in FIG. 1B-5 of the method embodiment) are both transmitted and received via communication interface 903. The processor 901 processes the message received by the communication interface 903 according to the program code in the memory 902, and interacts with the external device through the communication interface 903. The processor 901 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or the like. The device for processing the ICE address in this embodiment may include a bus 904. The processor 901, the memory 902, and the communication interface 903 can be connected and communicated via a bus 904. The memory 902 may include: a random access memory (RAM), a read-only memory (ROM), a disk and the like having a storage function. The call context in the embodiment of the present invention can be cached in the RAM.

Still referring to FIG. 9, which is a block diagram of an embodiment of an access server according to the present invention, the access server in the embodiment of the present invention may be implemented based on a computer system, and the method shown in FIG. 5 may be implemented in an access server based on a computer system. The access server in this embodiment may include: a processor 901, a memory 902, and a communication interface 903. The memory 902 is used to store program codes. The processor 901 is configured to execute program code stored in the memory 902. In one embodiment of the present invention, the memory 902 stores a first program code, and the processor 901 is configured to execute the first program code, including: performing a data operation request sent by the data operation requesting device, where the data operation request includes accessing The number is obtained according to the access number, and the fragment identifier of the client fragment corresponding to the access number is obtained. According to the fragment identifier corresponding to the access number, the data source corresponding to the fragment identifier is obtained from the fragment data source correspondence table. The identifier, where the fragment data source correspondence table holds the fragment identifier and the data source identifier; sends the data operation request to the data source corresponding to the obtained data source identifier; and receives the data operation response sent by the data source. The communication interface 903 is configured to communicate with an external device, such as a data generating module. Messages that interact between the data generating device and the access server (as shown in FIG. 1B-5 of the method embodiment) are both transmitted and received via communication interface 903. The processor 901 processes the message received by the communication interface 903 according to the program code in the memory 902, and interacts with the external device through the communication interface 903. The processor 901 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or the like. The device for processing the ICE address in this embodiment may include a bus 904. The processor 901, the memory 902, and the communication interface 903 can be connected and communicated via a bus 904. The memory 902 may include: a random access memory (RAM), a read-only memory (ROM), a disk and the like having a storage function. The call context in the embodiment of the present invention can be cached in the RAM.

As can be seen from the foregoing embodiment, in the embodiment of the present invention, since the customer identifier and the user identifier include the same fragmentation identifier of the client fragment, and one fragment corresponds to a data source, the client data and the user data can be both Stored in the same data source. And according to the attributes of the customer, the requirements of the data source can be determined, so that the data source that meets the requirements can be flexibly allocated to the customer and the user.

As shown in FIG. 10, a schematic structural diagram of a data operating system according to an embodiment of the present invention includes a data generating apparatus 1010 as shown in FIG. 6, 7 or 9, and an access server 1020 as shown in FIG. 8 or FIG.

It will be apparent to those skilled in the art that the techniques in the embodiments of the present invention can be implemented by means of software plus a necessary general hardware platform. Based on such understanding, the technical solution in the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product, which may be stored in a storage medium such as a ROM/RAM. , a disk, an optical disk, etc., including instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention or portions of the embodiments.

The various embodiments in the present specification are described in a progressive manner, and the same or similar portions between the various embodiments may be referred to each other, and each embodiment focuses on differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant part can be referred to the description of the method embodiment.

The embodiments of the present invention described above are not intended to limit the scope of the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and scope of the invention are intended to be included within the scope of the invention.

Claims

Rights request

A data storage method, characterized in that, when a customer subscribes to a service, and the client becomes a user of the service, the method includes:

The data generating device determines that the client has opened an account, and obtains a first fragment identifier included in the client identifier of the client, where the first fragment identifier is a fragment identifier of the client fragment to which the client belongs, The customer identification uniquely identifies the customer during the customer's life cycle, and the customer life cycle refers to the period from the time the customer opens the account to the time the customer signs the account;

The data generating device generates, according to the first fragment identifier, a user identifier that includes the first fragment identifier for the user, where the user identifier uniquely identifies the user during a user lifetime, and the user life The period refers to the period from the time the user opens the account to the time before the user cancels the account;

The data generating device obtains, according to the first fragment identifier, a data source identifier corresponding to the first fragment identifier from a fragment data source correspondence table, and stores the user data in the data source. And identifying, by the access server, the data of the user from the data source corresponding to the first fragment identifier according to the first fragment identifier included in the user identifier, where The fragment data source correspondence table contains the correspondence between the fragment identifier of the client fragment and the data source identifier.

2. The method according to claim 1, further comprising:

The data generating device searches for a second fragment identifier corresponding to the range of the number segment to which the resource number belongs from the number segment routing table according to the resource number of the user, where the number segment routing table includes the score Correspondence between the slice identifier and the range of the number segment to which the resource number belongs;

Determining that the second fragment identifier is not found, or the found second fragment identifier is inconsistent with the first fragment identifier, the data generating device uses the resource number and the first score The corresponding relationship of the slice identifier is added to the scatter number routing table in the database, where the scatter number routing table includes a correspondence between the fragment identifier and the resource number not attributed to the segment routing table.

The method according to claim 1 or 2, wherein before the client subscribes to the service, the method further includes:

When the customer opens an account, the tenant identifier of the customer is obtained;

The data generating device acquires, according to the tenant identifier, a fragment identifier in the fragment identifier corresponding to the tenant identifier from the fragment data source correspondence table, and uses the obtained fragment identifier as a first fragment identifier, where the fragment data source correspondence table further includes a correspondence between a tenant identifier and a fragment identifier;

Generating, by the data generating device, the first score for the client according to the first fragment identifier a customer identifier of the slice identifier, and the data of the client is stored in a data source corresponding to the first fragment identifier, so that the access server is configured according to the first fragment identifier included in the client identifier. Acquiring the data of the client in the data source corresponding to the first fragment identifier.

4. The method according to claim 1, further comprising:

When the data generating device determines that the client has not opened an account, the second fragment identifier corresponding to the range of the number segment to which the resource number belongs is searched according to the resource number of the user, where the number is The segment routing table includes the correspondence between the fragment identifier and the range of the number segment to which the resource number belongs;

When the second fragment identifier is found, the data generating device generates, according to the second fragment identifier, a client identifier that includes the two-part identifier, and the second fragment identifier according to the second fragment identifier. Generating, for the user, a user identifier that includes the second fragment identifier, and storing data of the client and data of the user in a data source corresponding to the second fragment identifier, so that the access server is configured according to the And the second fragment identifier included in the customer identifier and/or the user identifier, and acquiring data of the client and/or data of the user from a data source corresponding to the second fragment identifier.

5. The method according to claim 4, further comprising:

Obtaining the tenant identifier of the tenant to which the client belongs when the second fragment identifier is not found; the data generating device acquiring the tenant from the fragment data source correspondence table according to the tenant identifier Identifying a fragment identifier of the corresponding fragment identifier, and the obtained fragment identifier is used as the first fragment identifier, where the fragment data source correspondence table further includes a correspondence between the tenant identifier and the fragment identifier. Relationship

The data generating device generates, according to the first fragment identifier, a client identifier that includes the first fragment identifier for the client, and generates, according to the first fragment identifier, the user that includes the first a user ID identified by a slice;

Adding the corresponding relationship between the resource number and the first fragment identifier to the scatter number routing table, where the scatter number routing table includes a correspondence between the fragment identifier and a resource number not belonging to the segment routing table. And storing the data of the customer and the data of the user in a data source corresponding to the first fragment identifier, so that the access server is configured according to the first fragment identifier included in the customer identifier and/or the user identifier. And acquiring data of the client and/or data of the user from a data source corresponding to the first fragment identifier.

The method according to any one of claims 1 to 5, wherein the method further comprises:

The data generating device obtains, according to the first data source identifier, all the fragment identifiers corresponding to the first data source identifier from the fragment data source correspondence table;

According to the relocation request, selecting the matching object from all the fragment identifiers corresponding to the first data source identifier Determining one or more fragment identifiers of the relocation request, and setting the state of the one or more fragment identifiers in the fragment data source correspondence table to a relocation state, so as to prohibit prohibition of the data generation device The network element accesses data corresponding to the one or more fragment identifiers;

The data generating device relocates data in the first data source corresponding to the one or more fragment identifiers to the second data source;

The data generating device deletes, in the fragment data source correspondence table, a correspondence between the first data source identifier and the one or more fragment identifiers;

And the data generating device adds a correspondence between the second data source identifier and the one or more fragment identifiers in the fragment data source correspondence table, and sets a state of the one or more fragment identifiers It is a non-relocation state, so as to allow access to the data corresponding to the one or more fragment identifiers.

7. A data operation method, comprising:

The access server receives a data operation request sent by the data operation requesting device, where the data operation request includes an access number;

And obtaining, by the access server, a fragment identifier of the client fragment corresponding to the access number according to the access number;

The access server obtains a data source identifier corresponding to the fragment identifier from the fragment data source correspondence table according to the fragment identifier corresponding to the access number, where the fragment data source correspondence The table saves the fragment identifier and the data source identifier;

Sending, by the access server, the data operation request to the obtained data source corresponding to the data source identifier;

The access server receives a data operation response sent by the data source.

The method according to claim 7, wherein the obtaining, according to the access number, the fragment identifier corresponding to the access number, specifically includes:

And obtaining, when the access number is a customer identifier or a user identifier, a fragment identifier included in the customer identifier or the user identifier;

When the access number is a resource number, the fragment identifier corresponding to the resource number is searched in the hash routing table according to the resource number of the user, and when the fragment identifier corresponding to the resource number is found, Obtaining the fragment identifier; when the fragment identifier corresponding to the resource number is not found, obtaining, according to the resource number of the user, the number segment corresponding to the resource number in the number segment routing table a slice identifier, where the scatter number table includes a correspondence between the slice identifier and a resource number not attributed to the number segment routing table, where the number segment routing table includes the fragment identifier and the The correspondence between the range of the number segment to which the resource number belongs.

A data generating device, comprising: an obtaining module, a generating module, and a storage module, wherein

The obtaining module is configured to: when a customer subscribes to a service, when the client becomes a user of the service, determine that the client has opened an account, and obtain a first fragment identifier included in the client identifier of the client, The first fragment is identified as a fragment identifier of the client fragment to which the customer belongs, and the customer identifier uniquely identifies the client during a customer lifetime, and the customer life cycle refers to after the customer opens an account. During the period before the customer cancels the account;

The obtaining module is further configured to send, to the generating module, a user identity generation request that includes the first fragment identifier;

The generating module is configured to receive, by the acquiring module, a user identifier generation request that includes the first fragment identifier, and generate, according to the first fragment identifier, a first fragment identifier for the user The user identifier, the user identifier uniquely identifies the user during the life cycle of the user, and the user life cycle refers to a period from after the user opens the account to before the user cancels the account;

The obtaining module is further configured to obtain, according to the first fragment identifier, a data source identifier corresponding to the first fragment identifier from a fragment data source correspondence table, and send the data source identifier to the Storage module

The storage module is configured to receive the data source identifier sent by the acquiring module, and store the data of the user in a data source corresponding to the data source identifier, so that the access server is included according to the user identifier. The first fragment identifier, the data of the user is obtained from a data source corresponding to the first fragment identifier, where the fragment data source correspondence table includes a fragment identifier and a data source identifier of the client fragment. Correspondence.

The device according to claim 9, wherein the acquiring module is further configured to: according to the resource number of the user, search for a range corresponding to a range of the number range of the resource number from the number segment routing table a segmentation identifier, and sending a query result to the storage module, where the number segment routing table includes a correspondence between the fragment identifier and a range of a number range of the resource number;

The storage module is further configured to receive the query result sent by the acquiring module, and determine, according to the query result, that the second fragment identifier is not found, or the second fragment identifier that is found is When the first fragment identifiers are inconsistent, the corresponding relationship between the resource number and the first fragment identifier is added to the scatter number routing table in the database, where the scatter number routing table includes the fragment identifier and the non-attribute Correspondence of resource numbers in the routing table of the segment.

The device according to claim 9 or 10, wherein the obtaining module is further configured to: before the customer subscribes to the service, the customer also obtains the tenant identifier of the customer when the customer opens the account, And obtaining, according to the tenant identifier, a fragment identifier in the fragment identifier corresponding to the tenant identifier, and using the obtained fragment identifier as the first fragment identifier. The fragment data source correspondence table further includes a correspondence between the tenant identifier and the fragment identifier, and sends a client identifier generation request including the first fragment identifier to the generating module.

The generating module is configured to receive a client identity generation request that is sent by the acquiring module and includes the first fragment identifier, and generate, by the first fragment identifier, a client that includes the first fragment identifier according to the first fragment identifier. Identification

The storage module is further configured to: obtain, by the generating module, the first fragment identifier included in the customer identifier, and store the data of the client in a data source corresponding to the first fragment identifier, so as to facilitate the The access server obtains data of the client from a data source corresponding to the first fragment identifier according to the first fragment identifier included in the client identifier.

The device according to claim 9, wherein the obtaining module is further configured to: when the client is not open, according to the resource number of the user, look up the resource from a segment routing table. a second fragment identifier corresponding to the range of the number segment, and sending, to the generating module, a user identifier generation request including the second fragment identifier obtained by the query, and a client including the second fragment identifier obtained by the query An identifier generation request, where the number segment routing table includes a correspondence between the fragment identifier and a range of a number range to which the resource number belongs;

The generating module is further configured to receive a user identifier generation request that includes the second fragment identifier sent by the acquiring module, and a client identifier generation request that includes the second fragment identifier, according to the second fragment Identifying, generating, for the customer, a customer identifier that includes the second fragment identifier;

The obtaining module is further configured to obtain, according to the second fragment identifier, a data source identifier corresponding to the second fragment identifier from the fragment data source correspondence table, and send the data source identifier to the Storage module

The storage module is further configured to store the data of the client in a data source corresponding to the second fragment identifier, so that the access server obtains the second fragment identifier included in the client identifier. The data of the customer is obtained from a data source corresponding to the second fragment identifier.

The device according to claim 9, wherein the acquiring module is further configured to: when the client is not open, according to the resource number of the user, look up the resource from a segment routing table. The second fragment identifier corresponding to the range of the number segment of the number, wherein the number of the segment identifiers includes the correspondence between the fragment identifier and the range of the number of the resource number, and the second fragment identifier is not queried. Obtaining a tenant identifier of the tenant identifier corresponding to the tenant identifier from the fragment data source correspondence table according to the tenant identifier, and obtaining a fragment identifier in the fragment identifier corresponding to the tenant identifier, The one fragment identifier is used as the first fragment identifier, where the fragment data source correspondence table further includes a correspondence between the tenant identifier and the fragment identifier, and the first module is sent to the generating module. a user identification generation request of the slice identifier and a client identity generation request including the first fragmentation identifier;

The generating module is further configured to receive a user identifier generation request that includes the first fragment identifier sent by the acquiring module, and a client identifier generation request that includes the first fragment identifier, according to the first fragment Identifying, generating, for the customer, a customer identifier that includes the first fragment identifier;

The storage module is further configured to add a correspondence between the resource number and the first fragment identifier to a scatter number routing table, where the scatter number routing table includes a fragment identifier and a non-attribution number segment Corresponding relationship between the resource numbers of the routing table, and storing the data of the client in the data source corresponding to the first fragment identifier, so that the access server is configured according to the first fragment identifier included in the client identifier. Obtaining data of the client from a data source corresponding to the first fragment identifier.

The device according to any one of claims 9 to 13, further comprising: a relocation module, configured to obtain, according to the first data source identifier, the fragment data source correspondence table All the fragment identifiers corresponding to the first data source identifier are selected; and one or more fragment identifiers that meet the relocation request are selected from all the fragment identifiers corresponding to the first data source identifier according to the relocation request, and The state of the one or more fragment identifiers in the segment data source correspondence table is set to a relocation state, so as to prevent the network element except the data generating device from accessing the data corresponding to the one or more fragment identifiers. Relocating data in the first data source corresponding to the one or more fragment identifiers to the second data source; deleting the first data source identifier in the fragment data source correspondence table Corresponding relationship with the one or more fragment identifiers; adding, in the fragment data source correspondence table, the second data source identifier and the one or more fragment identifiers Corresponding relationship, and said more than one fragment identified non relocation state setting state, in order to allow access to the more than one fragment corresponding to the identification data.

An access server, comprising: a transceiver and a processor, wherein the transceiver is configured to receive a data operation request sent by a data operation requesting device, where the data operation request includes an access number, And sending an access number to the processor;

The processor is configured to receive an access number sent by the transceiver, obtain a fragment identifier of a client fragment corresponding to the access number according to the access number, and obtain a corresponding identifier according to the access number. a fragment identifier, the data source identifier corresponding to the fragment identifier is obtained from the fragment data source correspondence table, and the data source identifier is sent to the transceiver, where the fragment data source correspondence is The table saves the fragment identifier and the data source identifier;

The transceiver is further configured to receive the data source identifier sent by the processor, and send the data operation request to a data source corresponding to the data source identifier, and receive the number sent by the data source According to the operation response.

The access server according to claim 15, wherein the processor is specifically configured to: when the access number is a customer identifier or a user identifier, obtain the score included in the customer identifier or the user identifier. a slice identifier; when the access number is a resource number, searching for a fragment identifier corresponding to the resource number in the hash number routing table according to the resource number of the user, and searching for a score corresponding to the resource number When the fragment is identified, the fragment identifier is obtained. When the fragment identifier corresponding to the resource number is not found, the resource number belongs to the number segment routing table according to the resource number of the user. a fragment identifier corresponding to the segment, where the scatter number routing table includes a correspondence between the fragment identifier and a resource number not attributed to the number segment routing table, where the number segment routing table includes the fragment identifier Correspondence with the range of the number segment to which the resource number belongs.

A data operating system, comprising: a data generating device according to any of claims 9-14 and any access server according to claims 15-16.