CN101754167B - Data storage method, device and system - Google Patents
Data storage method, device and system Download PDFInfo
- Publication number
- CN101754167B CN101754167B CN 200810184599 CN200810184599A CN101754167B CN 101754167 B CN101754167 B CN 101754167B CN 200810184599 CN200810184599 CN 200810184599 CN 200810184599 A CN200810184599 A CN 200810184599A CN 101754167 B CN101754167 B CN 101754167B
- Authority
- CN
- China
- Prior art keywords
- subclauses
- clauses
- entry type
- pointed
- another name
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Disclosed is a technical proposal of a data storage method, device and storage system. Wherein, the data storage method comprises: the storage processing request is received, when a data item which need the storage process is determined to be an alias item, the item type directed by the data item which need the storage process and is acquired from the request and the item type directed by the data item which is acquired from item type information directed by the alias item in a pre-set directory information tree are compared. If the type is same, the data item is stored. If the type is not same, the data item is not stored. In the technical proposal, each alias item directs an item which is determined the type under the condition that the directory information tree contains the alias item, thereby the directory information tree has the determinacy.
Description
Technical field
The present invention relates to the communications field, be specifically related to date storage method, data storage device and data-storage system.
Background technology
Amalgamation database is a kind of data storage device.It provides a storage platform, with the data centralization storage of heterogeneous networks, different network elements.After introducing amalgamation database and since user data can centralized stores in amalgamation database, therefore, former each network element that stores user data need to carry out business and data separating transformation, the improved network element logic of only managing business gets final product.The Lightweight Directory Access Protocol (Light Directory Access Protocol that improved network element can externally provide by amalgamation database, LDAP), XML Configuration Access Protocol (extensible markup language configuration access protocol, the access interface access amalgamation database such as XCAP).
Amalgamation database uses the Directory Information Tree (directory information tree of LDAP, DIT) Home Location Register (attaching position register is described, HLR), Home Subscriber Server (home subscriber server, the model of practical application such as HSS), for the many-to-many relationship that exists in the practical application, LDAP uses Alias (another name) to be described.InternationalMobile Subscriber Identity (international mobile subscriber identity among above-mentioned many-to-many relationship such as the HLR, IMSI) and Mobile StationInternational ISDN Number (Mobile Subscriber International ISDN number, MSISDN) corresponding relation between, for another example (the total identify label of the IP Multimedia Public Identity among the HSS, IMPU) and IPMultimedia Private Identity (privately owned identify label, the corresponding relation between IMPI).
In realizing process of the present invention, the inventor finds: the Alias among the LDAP points to any clauses and subclauses at present, therefore, and the data in HLR, the HSS etc. that use Alias definition field of telecommunications use, during with the storage data, can't make the DIT of the application such as HLR, HSS have certainty.
Summary of the invention
Embodiment of the present invention provides date storage method, device and system, when including the another name clauses and subclauses in directory information tree, makes every alias clauses and subclauses all point to definite type entries, thereby makes directory information tree have certainty.
The date storage method that embodiment of the present invention provides comprises:
Receive the stores processor request;
In the data clauses and subclauses of determining to carry out stores processor during for the another name clauses and subclauses, the described data clauses and subclauses entry type pointed that obtains in the described data clauses and subclauses that need stores processor of obtaining from described request entry type pointed and the another name clauses and subclauses from the directory information tree that the sets in advance entry type information pointed is compared;
If identical, then described data clauses and subclauses are carried out stores processor;
If not identical, then described data clauses and subclauses are not carried out stores processor.
The data storage device that embodiment of the present invention provides comprises:
Memory module is used for the another name clauses and subclauses entry type information pointed that store inventory information is set;
Receiver module is used for receiving the stores processor request;
Judge module, be used for when identifying data clauses and subclauses that need stores processor that stores processor request that receiver module receives carries for the another name clauses and subclauses, the described data clauses and subclauses that need stores processor of obtaining from described request entry type pointed and the described data clauses and subclauses entry type pointed that obtains from described memory module are compared;
The stores processor module is used for when being identical, described data clauses and subclauses being carried out stores processor at the comparative result of described judge module, otherwise, described data clauses and subclauses are not carried out stores processor.
The data-storage system that embodiment of the present invention provides comprises:
At least one first network equipment is used for sending the stores processor request;
Second network equipment, be provided with amalgamation database and store another name clauses and subclauses entry type information pointed in the directory information tree, be used for receiving the described request that first network equipment sends, the data clauses and subclauses that need stores processor of carrying in identifying the described request that receives are another name during clauses and subclauses, and the described data clauses and subclauses of obtaining from described request entry type pointed and the described data clauses and subclauses entry type pointed that obtains from pre-stored configuration information are compared; If identical, then described data clauses and subclauses are carried out stores processor; If not identical, then described data clauses and subclauses are not carried out stores processor.
Description by technique scheme as can be known, by the another name clauses and subclauses entry type information pointed in the directory information tree is set, and the comparison of the entry type information pointed to of the information of in data clauses and subclauses storing process, utilizing this setting, then, when entry type information pointed is consistent, just store the data clauses and subclauses, avoided the uncertainty of the data clauses and subclauses of storage entry type pointed, define every alias clauses and subclauses concrete clauses and subclauses pointed, thereby make every alias clauses and subclauses all point to definite type entries, make directory information tree have certainty.
Description of drawings
Fig. 1 is the amalgamation database networking schematic diagram that the embodiment of the invention is used;
Fig. 2 is the date storage method flow chart of the embodiment of the invention one;
Fig. 3 is the Alias object definition schematic diagram of MSISDN and IMSI during the HLR of the embodiment of the invention two uses;
Fig. 4 be the embodiment of the invention six use, utilize the schematic diagram that Alias clauses and subclauses entry type information pointed is set based on the configuration information outside the model definition for HLR;
Fig. 5 is the flow chart of the increase MsisdnAlias clauses and subclauses of the embodiment of the invention eight;
Fig. 6 is the data storage device schematic diagram of the embodiment of the invention nine;
Fig. 7 is the data-storage system schematic diagram of the embodiment of the invention ten.
Embodiment
The adaptable concrete amalgamation database networking of technical scheme that the embodiment of the invention is described as shown in Figure 1.
Centralized stores has the data of the device storage such as former HLR and former HSS in the amalgamation database of Fig. 1; Amalgamation database externally provides the access interfaces such as LDAP, XCAP; Can the data in the amalgamation database be configured by Provisioning (service dispense) entity; Each HLR FE among Fig. 1 (the professional front end of HLR) and HSS FE (the professional front end of HSS) only carry out business logic processing.
Below in conjunction with accompanying drawing various embodiments of the present invention are described.
The flow chart of embodiment one, date storage method as shown in Figure 2.
Among Fig. 2, step 200, the request of reception stores processor namely receive the data clauses and subclauses that need to carry out stores processor.The data clauses and subclauses that the needs here carry out stores processor can be to need the data clauses and subclauses that increase, and also can be needs the data clauses and subclauses revised etc.At least carry data strip purpose name information and the data clauses and subclauses entry type information pointed that to carry out stores processor in the above-mentioned stores processor request.This name information can go out alias clauses and subclauses by unique identification, and this name information can represent with the position of another name clauses and subclauses, also can represent with the ID (identifier) of another name clauses and subclauses.
Wherein, the stores processor request can be that the professional front end of HLR sends, and also can be that the professional front end of HSS sends.
The above-mentioned packets of information that sets in advance contains the another name clauses and subclauses entry type information pointed in the directory information tree.The storage mode of the above-mentioned information that sets in advance can be diversified.For example, can be stored in the model definition information; Again for example, can be stored in the configuration information outside the model definition information, namely this configuration information is independent of model definition information, and this configuration information can exist with forms such as allocation list, configuration databases.The another name clauses and subclauses of above-mentioned setting entry type information pointed is namely called the sensing scope of clauses and subclauses.
The mode that the information that sets in advance is stored in the model definition information can be diversified.First concrete example is: another name clauses and subclauses entry type information pointed is arranged in the expanded definition field of the object in the alias object definition.Second concrete example is: another name clauses and subclauses entry type information pointed is arranged in the expanded definition field of clauses and subclauses definition.The 3rd concrete example is: another name clauses and subclauses entry type information pointed is arranged in the expanded definition field of relative clause name definition; The 4th concrete example is: another name clauses and subclauses entry type information pointed is arranged in the expanded definition field of directory information tree organization definition.Certainly, the information that sets in advance also can be arranged at other position in the model definition information, for example, alias object definition or clauses and subclauses definition or relatively clause name definition or result the new extended field of increase in the definition is described, to store the above-mentioned information that sets in advance.
Optionally, in step 250, all right output error message, this error message need to represent the data clauses and subclauses entry type pointed of stores processor to exceed the another name clauses and subclauses entry type scope pointed that sets in advance.This error message can be carried in the LDAP Add Response message, for example: the error code definition to the LDAPResult field in the LDAPAdd Response message is expanded, and the error code after the utilization expansion represents the error message among the embodiment one.Object lesson of the error code definition in the expansion LDAP Add Response message such as the record of following embodiment seven.In addition, this error message also can be carried in the LDAP Modify Response message, for example: the error code definition to the LDAPResult field in the LDAP Modify Response message is expanded, and the error code after the utilization expansion represents the error message among the embodiment one.Certainly, also can adopt other message to carry above-mentioned error message, for example, utilize newly-increased message to carry above-mentioned error message etc.
Can find out from the description of above-described embodiment one, by in model definition information or the another name clauses and subclauses entry type information pointed of directory information tree is set in the configuration information outside model definition information, thereby in fused data library storage data strip purpose process, can utilize the information of setting to call the comparison of clauses and subclauses entry type information pointed, then, just store the data clauses and subclauses when consistent comparing another name clauses and subclauses entry type information pointed, thereby the concrete entry type that the data clauses and subclauses that define each storage are pointed, avoided the inconsistent data clauses and subclauses of entry type of the entry type that will point to and setting to be stored in phenomenon in the amalgamation database, the data clauses and subclauses entry type pointed of having avoided storing in the amalgamation database has probabilistic phenomenon; Thereby make every alias clauses and subclauses all point to definite type entries, make the directory information tree of LDAP have certainty.In addition, the date storage method of embodiment one description can be useful in each field that comprises DIT and needs use Alias.
Another name clauses and subclauses entry type information pointed is set among the embodiment one can be realized by multiple different mode, the below exemplifies explanation take embodiment two to embodiment six as example to the different implementations that another name clauses and subclauses entry type information pointed is set among the embodiment one.
Embodiment two, object definition arranges another name clauses and subclauses entry type information pointed based on Alias, namely on the basis of the Alias object definition that existing LDAP Schema (model) defines, increase corresponding descriptor, to limit the concrete sensing of Alias clauses and subclauses.
Object definition among the LDAP is described below:
ObjectClassDescription＝LPAREN WSP
Numericoid; The OID of object (object identifier) definition
[SP " NAME " SP qdescrs]; The title definition of object
[SP " DESC " SP qdstring]; The description of object
[SP " OBSOLETE "]; Represent that this object class is inactive
[SP " SUP " SP oids]; The parent object definition
[SP kind]; The type of object, the type of object comprises: three kinds of abstract class, structure class, assisted class
[SP " MUST " SP oids]; Essential attribute type
[SP " MA Y " SP oids]; The optional attribute type
Extensions WSP RPAREN; The expanded definition of object
Above-mentioned kind=" ABSTRACT "/" STRUCTURAL "/" AUXILIARY ", and extensions is defined as:
extensions＝*(SP xstring SP qdstrings)
xstring＝″X″HYPHEN1*(ALPHA/HYPHEN/USCORE)
Present embodiment can take the Alias object among the LDAP as parent object, utilize the expanded definition (extensions) of the object in the Alias object definition to describe Alias clauses and subclauses entry type information pointed.The Alias object definition of this moment can be called the Alias object definition of expansion.
A concrete example that utilizes the expanded definition of the object in the Alias object definition to describe Alias clauses and subclauses entry type information pointed is:
According to the syntactic structure of extensions, partly use field at the extensions of Alias object definition
AliasDestination＝
" X-AliasDestination "; Be used for recording the field name that the Alias clauses and subclauses are pointed to, namely represent to include among this extensions the concrete entry type information that the Alias clauses and subclauses are pointed to.The field name of Alias objects point namely can limit Alias clauses and subclauses entry type information pointed
SP oid; Be used for recording Alias clauses and subclauses concrete entry type information pointed, the type of this field is the oid type that defines in the standard
In actual applications, an object lesson that with the Alias object definition of expansion Alias clauses and subclauses entry type information pointed is set is:
(
1.3.4.1.4.142.2.27.1.2.200; The OID of the Alias object of expansion
NAME ' newAliasobject '; The title of the Alias object of expansion, dissimilar Alias uses different titles
DESC specified Alias object; The description of the Alias object of expansion is the Alias object that limits
SUP ' Alias '; Describe the parent object title of this object, be the Alias object of LDAP definition
AliasExtension; Use above-mentioned expanded definition to limit the sensing scope of Alias object
)
The definition of the MSISDN in using below in conjunction with accompanying drawing 3, to HLR and the Alias object of IMSI describes.
During the HLR of Fig. 3 used, the MSISDNAlias clauses and subclauses should be pointed to the MSISDN clauses and subclauses, and the IMSIAlias clauses and subclauses should be pointed to the IMSI clauses and subclauses.
MSISDNAlias object among Fig. 3 is defined as follows:
(
1.3.4.1.4.142.2.27.1.2.201; The OID of the MSISDNAlias object of expansion
NAME ' msisdnAlias '; The Alias object oriented of msisdn type
DESC specified Alias object; The description of the MSISDNAlias object of expansion is the Alias object that limits
SUP ' Alias '; The parent object name of having described this object is called the Alias object that defines in the LDAP standard
X-AliasDestination 1.3.5; 1.3.5 the oid of the MSISDN clauses and subclauses of using for this HLR has determined the concrete entry type that points to of these Alias clauses and subclauses
)
Adopt above-mentioned similar method can the IMSIAlias object among Fig. 3 be defined, no longer describe in detail at this.
Need to prove that for clarity, two alias clauses and subclauses among Fig. 3 have different another name clause names, i.e. MSISDNALIAS and IMSIALIAS; Certainly, two alias clauses and subclauses among Fig. 3 all can called after ALIAS, in this case, can identify different another name clauses and subclauses by the position at another name clauses and subclauses place.
Embodiment three, based on clauses and subclauses definition another name clauses and subclauses entry type information pointed is set, namely on the basis of existing DITContentRule (DIT clauses and subclauses) definition, increases corresponding descriptor, to limit the concrete sensing of Alias clauses and subclauses.
Determine in the present embodiment the concrete sensing of Alias clauses and subclauses by extended description information in the DITContentRule of LDAP Schema (model) definition.That is to say, Alias clauses and subclauses entry type information pointed is not set in Alias object definition process, and when being Alias object definition clauses and subclauses, the Extensions that defines DITContentRuleDescription with clauses and subclauses partly describes Alias clauses and subclauses entry type information pointed.
Utilize the Extensions of DITContentRuleDescription partly to describe among Alias clauses and subclauses entry type information pointed such as the above-mentioned embodiment two for the record of Extension part, do not describing in detail at this.
Implement four, based on relative clause name definition another name clauses and subclauses entry type information pointed be set, namely on the basis of existing NameFormDescription (clause name is described relatively) definition, increase corresponding descriptor, to limit the concrete sensing of Alias clauses and subclauses.
Determine in the present embodiment the concrete sensing of Alias clauses and subclauses by extended description information in the NameFormDescription of LDAP Schema (model) definition.That is to say, Alias clauses and subclauses entry type information pointed is not set in Alias object definition process and in the clauses and subclauses definition procedure, and when being the relative clause name of Alias object definition, with the Extensions of NameFormDescription Alias clauses and subclauses entry type information pointed is described partly.
Utilize the Extensions of NameFormDescription partly to describe among Alias clauses and subclauses entry type information pointed such as the above-mentioned embodiment two for the record of Extensions part, do not describing in detail at this.
Embodiment five, based on the directory information tree organization definition another name clauses and subclauses entry type information pointed is set, namely on the basis of existing DITStructureRuleDescription (description of DIT structure) definition, increase corresponding descriptor, to limit the concrete sensing of Alias clauses and subclauses.
Determine in the present embodiment the concrete sensing of Alias clauses and subclauses by extended description information in the DITStructureRuleDescription of LDAP Schema definition.That is to say, in Alias object definition process, in the clauses and subclauses definition procedure and in relative clause name definition procedure, Alias clauses and subclauses entry type information pointed be not set all, and when being Alias object definition entry structure, with the Extensions of DITStructureRuleDescription Alias clauses and subclauses entry type information pointed is described partly.
Utilize the Extensions of DITStructureRuleDescription partly to describe among Alias clauses and subclauses entry type information pointed such as the above-mentioned embodiment two for the record of Extensions part, do not describing in detail at this.
Embodiment six, based on the configuration information outside the model definition another name clauses and subclauses entry type information pointed is set.
In the present embodiment, the sensing scope of Alias clauses and subclauses need to be set in the model definition processes such as Alias object definition, clauses and subclauses definition, relative clause name definition and directory information tree organization definition, and in the allocation list outside model definition, configuration database etc. configuration information is set, to describe Alias clauses and subclauses entry type information pointed.A kind of specific implementation process is: describe successively Alias clauses and subclauses entry type information pointed for each the Alias clauses and subclauses among the practical application DIT in configuration file.
Use, utilize and the example of Alias clauses and subclauses entry type information pointed is set shown in accompanying drawing 4 and table 1 based on the configuration information outside the model definition for HLR for one.
Among Fig. 4, for the Alias clauses and subclauses have defined two father's clauses and subclauses, these two father's clauses and subclauses are respectively MSISDN clauses and subclauses and IMSI clauses and subclauses among the DIT of the LDAP Schema of HLR.Then, indicate the Alias clauses and subclauses entry type information pointed of each position in Alias clauses and subclauses allocation list, Alias clauses and subclauses allocation list is as shown in table 1.
Table 1
| The Alias position | The entry type information that Alias is pointed |
| HlrApp.IMSI | MSISDN |
| HlrApp.MSISDN | IMSI |
In the table 1, Alias has recorded the position ancestors' clause name of each Alias clauses and subclauses in the LDAP Schema definition, this ancestors' clause name begins from the root clauses and subclauses of DIT until number separate with ". " between father's clause name of these Alias clauses and subclauses and the dissimilar ancestor clause name, this ancestors' clause name has recorded the particular location of corresponding Alias clauses and subclauses clearly, utilizes this ancestors' clause name can Alias clauses and subclauses of unique identification; It is corresponding one by one with the Alias position that Alias points to clause name, to show the Alias clauses and subclauses clause name pointed of this position, the Alias clauses and subclauses entry type pointed that is Fig. 4 left side is MSISDN, and the Alias clauses and subclauses entry type pointed on Fig. 4 the right is IMSI.
When needs storage data clauses and subclauses, the data clauses and subclauses that can utilize two Alias clauses and subclauses entry type information pointed of clearly expressing in the table 1 that needs are stored are pointed to the inspection of entry type, point to whether exceed preset range to judge the data strip purpose that needs storage, judging when exceeding preset range, can these data clauses and subclauses not carried out stores processor, and can return corresponding error message, judging when not exceeding preset range, tackle these data clauses and subclauses and carry out stores processor.
Output error message among the embodiment one can realize by multiple different mode, and the below is take embodiment seven as example, and a kind of implementation of output error message among the embodiment one is exemplified explanation.
Embodiment seven, the error message that defines to realize exceeding the sensing scope by the error code in the expansion LDAP Add Response message.
LDAPResult in the LDAP Add Response message of existing LDAP definition is defined as follows:
LDAPResult::＝SEQUENCE{
resultCode ENUMERATED{
success (0)，
affectsMultipleDSAs (71)，
--72-79unused--
other (80)，
...}，
matchedDN LDAPDN，
diagnosticMessage LDAPString，
referral [3]Referral OPTIONAL}
Wherein, result code 72-79 is untapped reservation item, and present embodiment can utilize any one result code among the 72-79 or utilize other result code of new expansion to represent that the data clauses and subclauses entry type pointed of needs increase has exceeded the error message of the Alias clauses and subclauses sensing scope that presets.
Below in conjunction with embodiment eight, be applied as example with HLR a kind of implementation of the date storage method of embodiment one exemplified explanation.
Embodiment eight, based on the flow process of the increase MsisdnAlias clauses and subclauses of HLR application model shown in Figure 3 as shown in Figure 5.
Among Fig. 5, step 1, HLR FE need to increase the MsisdnAlias clauses and subclauses, and HLR FE sends LDAP increase request (LDAP Add Request) to amalgamation database, carry the MsisdnAlias items for information that needs increase in this LDAP increase request.
After step 2, amalgamation database receive this LDAP increase request, obtaining the clause name information that needs to increase from this request is MsisdnAlias clause name information, when determining these MsisdnAlias clauses and subclauses for the another name clauses and subclauses, from request, obtain MsisdnAlias clauses and subclauses entry type information pointed, for example from the AliasedObjectName that this request is carried, obtain the MsisdnAlias clauses and subclauses entry type information pointed that needs increase; Obtained need the MsisdnAlias clauses and subclauses that increase entry type information pointed after, whether the MsisdnAlias clauses and subclauses that judge to need increase again entry type information pointed is identical with the sensing MSISDN that arranges in the model definition, and the Alias sensing clause name of the 2nd list item compares in the sensing scope of the MsisdnAlias clauses and subclauses that also needs can be increased in other embodiments and the above-mentioned table 1.If judging the MsisdnAlias clauses and subclauses entry type information pointed that needs to increase is MSISDN, then the above-mentioned MsisdnAlias clauses and subclauses that need to increase are increased processing, otherwise, in LDAP Add Response (LDAP increases response), carry the result code of above-mentioned expanded definition, go beyond the scope with indication MsisdnAlias clauses and subclauses entry type pointed.
Need to prove, in above-mentioned steps 2, obtaining the operation of MsisdnAlias clauses and subclauses entry type information pointed from request can carry out together with the operation of obtaining the clause name information that needs increase from this request, namely obtains simultaneously clause name information and these clauses and subclauses entry type information pointed that need to increase from request.
Below in conjunction with accompanying drawing to the data storage device, and the specific embodiment of data-storage system describe.
Embodiment nine, data storage device are as shown in Figure 6.
Data storage device among Fig. 6 comprises: memory module 600, receiver module 610, judge module 620 and stores processor module 630; Optional this data storage device also comprises: sending module 640.
Store the another name clauses and subclauses entry type information pointed in the directory information tree in the memory module 600.The another name clauses and subclauses entry type information pointed of storage can realize in many ways in the memory module 600, for example, stores model definition information in the memory module 600, includes another name clauses and subclauses entry type information pointed in this model definition information; Again for example, store configuration information in the memory module 600, include another name clauses and subclauses entry type information pointed in this configuration information, and this configuration information is the information except model definition information.
In the model definition information of memory module 600 storages, include in the situation of another name clauses and subclauses entry type information pointed, the model definition information of storage can comprise in the memory module 600: include the alias object definition information of another name clauses and subclauses entry type information pointed, the another name clauses and subclauses type information pointed of this moment can be arranged in the expanded definition field of object definition; The model definition information of storage also can comprise in the memory module 600: include the clauses and subclauses definition information of another name clauses and subclauses type information pointed, the another name clauses and subclauses type information pointed of this moment can be arranged in the expanded definition field of clauses and subclauses definition; The model definition information of storage also can comprise in the memory module 600: include the relative clause name definition information of another name clauses and subclauses type information pointed, the another name clauses and subclauses type information pointed of this moment can be arranged in the expanded definition field of relative clause name definition; The model definition information of storage can also comprise in the memory module 600: include in the directory information tree organization definition information of another name clauses and subclauses type information pointed, the another name clauses and subclauses entry type information pointed of this moment can be arranged in the expanded definition field of directory information tree organization definition.
In the configuration information of memory module 600 storages, include in the situation of another name clauses and subclauses entry type information pointed, the configuration information of storage can be such as forms such as allocation list or configuration databases in the memory module 600, for example, storage information as shown in Table 1 above.
The specific implementation of clauses and subclauses entry type information pointed such as the description of above-mentioned embodiment two to embodiment six are called in storage in the memory module 600, no longer describe in detail at this.
The data clauses and subclauses that judge module 620 carries in identifying the request that receiver module 610 receives are during for the another name clauses and subclauses, from request, obtain the entry type information that needs the data of stores processor clauses and subclauses pointed, and obtain these data clauses and subclauses entry type information pointed in the configuration information from memory module 600, then, two entry types that relatively obtain, and output comparative result.
When stores processor module 630 is identical at the comparative result of judge module 620 outputs, the data clauses and subclauses that receiver module 610 receives are carried out stores processor; When not identical, the data clauses and subclauses that receiver module 610 do not received are carried out stores processor at the comparative result of judge module 620 output.
Sending module 640 at the comparative result of judge module 620 output when not identical, output error message, need the data clauses and subclauses entry type pointed of storage to exceed these data clauses and subclauses scope pointed that sets in advance with indication, i.e. the requirement of the entry type that these data clauses and subclauses that indication needs the data clauses and subclauses entry type pointed of storage not meet to set in advance are pointed.Sending module 640 can be carried at error message in the LDAPResult field in LDAP Add Response message or the LDAP Modify Response message, for example, error code definition to the LDAPResult field of LDAP Add Response message is expanded, and utilizes the error code after the expansion to represent above-mentioned error message.Object lesson that the error code definition of the LDAPResult field of LDAP Add Response message is expanded such as the description of above-mentioned embodiment seven no longer describe in detail at this.
Can find out from the description of above-described embodiment nine, by the another name clauses and subclauses that directory information tree is set in memory module 600 entry type information pointed, thereby judge module 620 can utilize canned data in the memory module 600 to call the comparison of clauses and subclauses entry type information pointed, like this, compare another name clauses and subclauses entry type information pointed when consistent at judge module 620, stores processor module 630 is just stored the data clauses and subclauses, thereby the concrete entry type that the data clauses and subclauses that define each storage are pointed, avoided stores processor module 630 that the inconsistent data clauses and subclauses of entry type of the entry type that points to and setting are stored in phenomenon in the amalgamation database, the data clauses and subclauses entry type pointed of having avoided storing in the amalgamation database has probabilistic phenomenon; Thereby make every alias clauses and subclauses all point to definite type entries, make directory information tree have certainty.
Embodiment ten, data-storage system are as shown in Figure 7.
Data-storage system among Fig. 7 comprises: at least one first network equipment 700 and second network equipment 710.First network equipment can be HLR FE, and HSS FE etc.
Be provided with amalgamation database in the second network equipment 710, and store the another name clauses and subclauses entry type information pointed of directory information tree in the second network equipment 710.Second network equipment 710 receives the stores processor request that first network equipment 700 sends, when the data clauses and subclauses that second network equipment 710 carries in identifying the stores processor request that receives are the another name clauses and subclauses, from the stores processor request that receives, obtain these data clauses and subclauses entry type information pointed, obtain these data clauses and subclauses entry type information pointed as increasing the request from LDAP.Second network equipment 710 obtains above-mentioned data clauses and subclauses entry type pointed from the configuration information of its storage, and two entry type information will obtaining compare; If identical, then the data clauses and subclauses that receive are carried out stores processor; If not identical, then the data clauses and subclauses that receive are not carried out stores processor.
Can find out from the description of above-described embodiment ten, by the another name clauses and subclauses that directory information tree is set in second network equipment 710 entry type information pointed, thereby second network equipment 710 can utilize the information that sets in advance of its storage to call the comparison of clauses and subclauses entry type information pointed, like this, second network equipment 710 is comparing another name clauses and subclauses entry type information pointed when consistent, just store the data clauses and subclauses, thereby the concrete entry type that the data clauses and subclauses that define each storage are pointed, avoided second network equipment 710 that the inconsistent data clauses and subclauses of entry type of the entry type that points to and setting are stored in phenomenon in the amalgamation database, the data clauses and subclauses entry type pointed of having avoided storing in the amalgamation database has probabilistic phenomenon; Thereby make every alias clauses and subclauses all point to definite type entries, make directory information tree have certainty.
Through the above description of the embodiments, those skilled in the art can be well understood to the present invention and can realize by the mode that software adds essential hardware platform, can certainly all implement by hardware, but the former is better execution mode in a lot of situation.Based on such understanding, technical scheme of the present invention is to can embodying with the form of software product in whole or in part that background technology contributes, this computer software product can be stored in the storage medium, such as ROM/RAM, magnetic disc, CD etc., comprise that some instructions are with so that a computer equipment (can be personal computer, server, the perhaps network equipment etc.) carry out the described method of some part of each embodiment of the present invention or embodiment.
Although described the present invention by embodiment, those of ordinary skills know, the present invention has many distortion and variation and do not break away from spirit of the present invention, and the claim of application documents of the present invention comprises these distortion and variation.
Claims (10)
1. a date storage method is characterized in that, comprising:
Receive the stores processor request;
When the definite data clauses and subclauses that need to carry out stores processor are the another name clauses and subclauses, the described data clauses and subclauses entry type pointed that obtains in the described data clauses and subclauses that need stores processor of obtaining from described request entry type pointed and the another name clauses and subclauses from the directory information tree that the sets in advance entry type information pointed is compared, described another name clauses and subclauses entry type information pointed is stored in the model definition information, perhaps is stored in the configuration information outside the model definition information;
If identical, then described data clauses and subclauses are carried out stores processor;
If not identical, then described data clauses and subclauses are not carried out stores processor.
2. the method for claim 1, it is characterized in that, described another name clauses and subclauses entry type information pointed is arranged in the model definition information, and perhaps, described another name clauses and subclauses entry type information pointed is arranged in the configuration information outside the model definition information.
3. method as claimed in claim 2 is characterized in that, described another name clauses and subclauses entry type information pointed be arranged at comprise in the model definition information following each:
Described another name clauses and subclauses entry type information pointed is arranged in the expanded definition field of the object in the alias object definition;
Described another name clauses and subclauses entry type information pointed is arranged in the expanded definition field of clauses and subclauses definition;
Described another name clauses and subclauses entry type information pointed is arranged in the expanded definition field of relative clause name definition;
Described another name clauses and subclauses entry type information pointed is arranged in the expanded definition field of directory information tree organization definition.
4. such as claim 1 or 2 or 3 described methods, it is characterized in that if described comparative result is not for identical, then described method also comprises:
Output exceeds the error message that the another name clauses and subclauses are pointed to the entry type scope.
5. a data storage device is characterized in that, comprising:
Memory module is used for the another name clauses and subclauses entry type information pointed that store inventory information is set, and described another name clauses and subclauses entry type information pointed is stored in the model definition information, perhaps is stored in the configuration information outside the model definition information;
Receiver module is used for receiving the stores processor request;
Judge module, be used for when identifying data clauses and subclauses that need stores processor that stores processor request that receiver module receives carries for the another name clauses and subclauses, the described data clauses and subclauses that need stores processor of obtaining from described request entry type pointed and the described data clauses and subclauses entry type pointed that obtains from described memory module are compared;
The stores processor module is used for when being identical, described data clauses and subclauses being carried out stores processor at the comparative result of described judge module, otherwise, described data clauses and subclauses are not carried out stores processor.
6. device as claimed in claim 5, it is characterized in that, include another name clauses and subclauses entry type information pointed in the model definition information of described memory module storage, and/or, include another name clauses and subclauses entry type information pointed in the configuration information outside the model definition information of described memory module storage.
7. device as claimed in claim 6 is characterized in that, includes in the model definition information of memory module storage in the situation of another name clauses and subclauses entry type information pointed, comprise following each:
Include another name clauses and subclauses entry type information pointed in the expanded definition field of the object in the alias object definition of described memory module storage;
Include another name clauses and subclauses entry type information pointed in the expanded definition field of the clauses and subclauses definition of described memory module storage;
Include another name clauses and subclauses entry type information pointed in the expanded definition field of the relative clause name definition of described memory module storage;
Include another name clauses and subclauses entry type information pointed in the expanded definition field of the directory information tree organization definition of described memory module storage.
8. such as claim 5 or 6 or 7 described devices, it is characterized in that described device also comprises:
Sending module is used at the comparative result of described judge module when not identical, and output exceeds the error message of another name clauses and subclauses sensing entry type scope.
9. a data-storage system is characterized in that, described system comprises:
At least one first network equipment is used for sending the stores processor request;
Second network equipment, be provided with amalgamation database and store another name clauses and subclauses entry type information pointed in the directory information tree, be used for receiving the described request that first network equipment sends, the data clauses and subclauses that need stores processor of carrying in identifying the described request that receives are another name during clauses and subclauses, and the described data clauses and subclauses of obtaining from described request entry type pointed and the described data clauses and subclauses entry type pointed that obtains from pre-stored configuration information are compared; If identical, then described data clauses and subclauses are carried out stores processor; If not identical, then described data clauses and subclauses are not carried out stores processor;
Wherein, described another name clauses and subclauses entry type information pointed is stored in the model definition information, perhaps is stored in the configuration information outside the model definition information.
10. system as claimed in claim 9, it is characterized in that, include another name clauses and subclauses entry type information pointed in the model definition information of described second network device storage, and/or, include another name clauses and subclauses entry type information pointed in the configuration information outside the model definition information of described second network device storage.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200810184599 CN101754167B (en) | 2008-12-17 | 2008-12-17 | Data storage method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200810184599 CN101754167B (en) | 2008-12-17 | 2008-12-17 | Data storage method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101754167A CN101754167A (en) | 2010-06-23 |
| CN101754167B true CN101754167B (en) | 2013-03-27 |
Family
ID=42480394
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200810184599 Expired - Fee Related CN101754167B (en) | 2008-12-17 | 2008-12-17 | Data storage method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101754167B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1859357A (en) * | 2006-03-16 | 2006-11-08 | 华为技术有限公司 | Communication method, system and device |
| CN101199190A (en) * | 2005-05-06 | 2008-06-11 | 高通股份有限公司 | Method and system for providing and managing public telephone directory service |
| US20080253403A1 (en) * | 2007-04-10 | 2008-10-16 | Apertio Limited | Nomadic subscriber data system |
| US20080256250A1 (en) * | 2007-04-10 | 2008-10-16 | Apertio Limited | Sub-tree access control in network architectures |
| WO2008122650A2 (en) * | 2007-04-10 | 2008-10-16 | Apertio Limited | Improved data access in home subscriber servers |
-
2008
- 2008-12-17 CN CN 200810184599 patent/CN101754167B/en not_active Expired - Fee Related
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101199190A (en) * | 2005-05-06 | 2008-06-11 | 高通股份有限公司 | Method and system for providing and managing public telephone directory service |
| CN1859357A (en) * | 2006-03-16 | 2006-11-08 | 华为技术有限公司 | Communication method, system and device |
| US20080253403A1 (en) * | 2007-04-10 | 2008-10-16 | Apertio Limited | Nomadic subscriber data system |
| US20080256250A1 (en) * | 2007-04-10 | 2008-10-16 | Apertio Limited | Sub-tree access control in network architectures |
| WO2008122650A2 (en) * | 2007-04-10 | 2008-10-16 | Apertio Limited | Improved data access in home subscriber servers |
Non-Patent Citations (1)
| Title |
|---|
| 李重武,倪惜珍.轻量目录访问协议分析.《计算机系统应用》.2002,全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101754167A (en) | 2010-06-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103002415B (en) | A kind of method and apparatus by short message sending identifying code | |
| US6996583B2 (en) | Real-time database update transaction with disconnected relational database clients | |
| CN101309162B (en) | Method, system, apparatus and user terminal realizing interaction of multimedia information | |
| CN108023794B (en) | Equipment access control method and device | |
| US20040078457A1 (en) | System and method for managing network-device configurations | |
| CN101009516A (en) | A method and system for data synchronization | |
| CN100488203C (en) | Method and apparatus for improving data processing speed | |
| CN102208945B (en) | Method for obtaining network address and FCoE target and communication system | |
| CN102017687A (en) | Method and device for instantiating management object of management tree in terminal device | |
| US20090097458A1 (en) | Method and System for Agent Redirecting the Terminal Request | |
| CN1859392B (en) | Service addressing method, system and its application | |
| US20070002778A1 (en) | Method for query of domain names of telephone numbers | |
| US20030105763A1 (en) | System, method, and computer program product for providing a wholesale provisioning service | |
| WO2002046889A2 (en) | Family tree website architecture | |
| JP4009591B2 (en) | Domain naming system (DNS) for accessing databases | |
| CN102694824B (en) | User data storage system and data access method thereof | |
| CN104392366B (en) | The method of data comparison information acquisition, Apparatus and system | |
| CN101754167B (en) | Data storage method, device and system | |
| CN109684450B (en) | Industrial network data distribution service system and method based on semantic identification | |
| JP2002368781A (en) | User location management domain name conversion system | |
| CN103200153B (en) | A kind of IP Multimedia System service activating method, equipment and system | |
| CN101674319B (en) | Method, system and equipment for accounting and accessing data | |
| CN106792468A (en) | The method and system of identification discovery in machine communication | |
| CN101753428A (en) | Method, device and processing system for capturing and reporting the information of instance labels | |
| CN114222284B (en) | Terminal equipment identification method, device and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20130327 Termination date: 20161217 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |