CN109408779A - A kind of data processing method and device - Google Patents
A kind of data processing method and device Download PDFInfo
- Publication number
- CN109408779A CN109408779A CN201710712753.9A CN201710712753A CN109408779A CN 109408779 A CN109408779 A CN 109408779A CN 201710712753 A CN201710712753 A CN 201710712753A CN 109408779 A CN109408779 A CN 109408779A
- Authority
- CN
- China
- Prior art keywords
- structural body
- tag value
- next stage
- processing rule
- target object
- 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.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/137—Hierarchical processing, e.g. outlines
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/103—Formatting, i.e. changing of presentation of documents
- G06F40/117—Tagging; Marking up; Designating a block; Setting of attributes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/183—Processing at user equipment or user record carrier
Abstract
The embodiment of the present application provides a kind of data processing method and device, passes through the target object that determination is to be processed；Based on defined in preset processing rule, the tag value of the element called during handling the target object, the element is handled, to obtain handling the result of the target object (wherein, the processing rule definition, the tag value of object element in target structure, different from be located at the object element in next stage element tag value) mode, so that in processing target object, convenient for the differentiation to the object element and the next stage element in the object element that are located in target structure, to reduce in generation/parsing eUICC data, data processing complex, the generation of error-prone situation.
Description
Technical field
This application involves eUICC technical fields, more particularly to a kind of data processing method and device.
Background technique
Existence form of the eUICC technology as a kind of new SIM card at present, it is positive to start to be used by large area.Realize eUICC
Technology must comply with eUICC Profile Package Interoperable Format Technical
Specification specification.
But it has been investigated that: the prior art often exists because of eUICC Profile Package Interoperable
The current released version (v2.1 version) of Format Technical Specification specification, it is fixed to the element in structural body
Justice is lack of standardization, and causes based on eUICC Profile Package Interoperable Format Technical
The current released version of Specification specification when generation/parsing eUICC data, is easy to produce data processing complex, easily
The problem of error.
In view of this, a kind of data processing method and device are provided, to reduce the data in generation/parsing eUICC data
The generation of complicated, the error-prone situation of processing, is a problem to be solved.
Summary of the invention
In view of this, the embodiment of the present application provides a kind of data processing method, to reduce in generation/parsing eUICC data
When, the generation of data processing complex, error-prone situation.
To achieve the goals above, technical solution provided by the embodiments of the present application is as follows:
A kind of data processing method, comprising:
Determine target object to be processed；
Based on the preset tag for handling the element that rule is defined, calls during handling the target object
Value, is handled the element, to obtain handling the result of the target object；
Wherein, the definition of processing rule, object element in the target structure tag value, different from being located at
The tag value of next stage element in the object element.
Preferably, the processing rule includes eUICC Profile Package Interoperable Format
Technical Specification specification.
Preferably, the target structure is the KeyList structural body in PE_SecurityDomain structural body
When,
The object element is the KeyObject structural body in the KeyList structural body.
Preferably, the next stage element in the object element, comprising: be located at the KeyObject structure
KeyCompontents structural body in body.
Preferably, the processing rule also definition, each next stage element in the object element tag value,
Different from the tag value of the element in the next stage element.
Preferably, the next stage element in the object element, comprising: be located at the KeyObject structure
When keyCompontents structural body in body,
Element in the described next stage element, comprising: in the keyCompontents structural body
SEQUENCE element.
Preferably, when the target structure is PE_Application structural body,
The object element is the ApplicaitonInstance structure in the PE_Application structural body
Body.
Preferably, the next stage element in the object element, comprising: be located at described
ProcessData element in ApplicaitonInstance structural body.
A kind of data processing equipment, comprising:
Determination unit, for determining target object to be processed；
Processing unit is adjusted defined in preset processing rule, during handling the target object for being based on
The tag value of element, handles the element, to obtain handling the result of the target object；
Wherein, the definition of processing rule, object element in the target structure tag value, different from being located at
The tag value of next stage element in the object element.
Preferably, the processing rule includes eUICC Profile Package Interoperable Format
Technical Specification specification.
The embodiment of the present application provides a kind of data processing method and device, passes through the target object that determination is to be processed；It is based on
The tag value for the element that preset processing rule is defined, calls during handling the target object, to the element
Handled, with obtain handling the target object result (wherein, the processing rule definition, be located at target structure
In object element tag value, different from be located at the object element in next stage element tag value) mode so that
When processing target object, convenient for the next stage member to the object element being located in target structure and in the object element
The differentiation of element, to reduce the generation of data processing complex, error-prone situation in generation/parsing eUICC data.
Detailed description of the invention
In order to illustrate the technical solutions in the embodiments of the present application or in the prior art more clearly, to embodiment or will show below
There is attached drawing needed in technical description to be briefly described, it should be apparent that, the accompanying drawings in the following description is only this
The some embodiments recorded in application, for those of ordinary skill in the art, without creative efforts,
It is also possible to obtain other drawings based on these drawings.
Fig. 1 is a kind of data processing method flow chart provided by the embodiments of the present application；
Fig. 2 is a kind of structural schematic diagram of data processing equipment provided by the embodiments of the present application.
Specific embodiment
In order to make those skilled in the art better understand the technical solutions in the application, below in conjunction with the application reality
The attached drawing in example is applied, the technical scheme in the embodiment of the application is clearly and completely described, it is clear that described implementation
Example is merely a part but not all of the embodiments of the present application.Based on the embodiment in the application, this field is common
The application protection all should belong in technical staff's every other embodiment obtained without making creative work
Range.
Embodiment:
Fig. 1 is a kind of data processing method flow chart provided by the embodiments of the present application.
As shown in Figure 1, this method comprises:
S101, target object to be processed is determined；
Optionally, the target object to be processed includes: the shell script for generating data, or for being resolvable to
The data of shell script.
Optionally, when the target object is the shell script for generating data, at the target object
Reason, with the result of the obtained processing target object for eUICC data corresponding with the shell script.
Optionally, when for the data for being resolvable to shell script, (data are eUICC number to the target object
According to) when, the target object is handled, the structure with the obtained processing target object is corresponding with the data
Shell script.
S101, the element that rule is defined, calls during handling the target object is handled based on preset
Tag value, the element is handled, to obtain handling the result of the target object.
In the embodiment of the present application, it is preferred that the target object is handled, during handling the target object,
Determine the element called when handling the target object, after determining the element called when handling the target object, really
The tag value of the identified element of fixed processing rule definition, and based on identified tag value to identified element at
Reason, each element finally called during to the target object is handled all after the completion of processing, obtain described in processing
The result of target object.
It optionally, in the process of processing to target object, is to handle according to data structure target object, number
It is a structural body according to structure itself, may include the structural body of multiple levels in the data structure.
Optionally, the definition of processing rule, object element in the target structure tag value, be different from position
The tag value of next stage element in the object element.That is, tag value, the difference of the object element being located in target structure
In the tag value of each element for the next stage being located in the object element.
Optionally, tag value, the difference of object element defined by the processing rule, in target structure
In be located at the object element in next stage element tag value, it is ensured that target object in the process of processing, it is right
The differentiation of the object element that the target object is called and the next stage element in the object element.
Optionally, the processing rule includes eUICC Profile Package Interoperable Format
Technical Specification specification.For example, the processing rule is eUICC Profile Package
Interoperable Format Technical Specification specification.
In the embodiment of the present application, it is preferred that the processing rule can be for eUICC Profile Package
Current released version (the v2.1 version) of Interoperable Format Technical Specification specification changes
Into version, specific processing rule provided by the embodiments of the present application and eUICC Profile Package Interoperable
Format Technical Specification specification current released version (v2.1 version) the difference is that: it is described
Processing rule definition is located at the tag value of the object element in target structure, different from next in the object element
The tag value of grade element.
It is above only the preferred embodiment of processing rule provided by the embodiments of the present application, inventor can be according to their own needs
The specific manifestation form of any setting processing rule, it is not limited here.
In the embodiment of the present application, it is preferred that the target structure is in PE_SecurityDomain structural body
KeyList structural body when, the object element is KeyObject structural body in the KeyList structural body；It is described
Next stage element in the object element, comprising: the keyCompontents in the KeyObject structural body
Structural body.
Further, processing rule provided by the embodiments of the present application also defines: under each of described object element
The tag value of level element, different from the tag value of the element in the next stage element.That is, under being directed in the object element
For each element of level-one, the tag value of the element is different from the tag value of each element of the next stage of the element.
Optionally, the next stage element in the object element, comprising: be located at the KeyObject structure
Element when keyCompontents structural body in body, in the described next stage element, comprising: be located at described
SEQUENCE element in keyCompontents structural body.
Optionally, when the target structure is PE_Application structural body, the object element is positioned at described
ApplicaitonInstance structural body in PE_Application structural body；It is described be located at the object element under
Level element, comprising: the ProcessData element in the ApplicaitonInstance structural body.
Optionally, eUICC Profile Package Interoperable Format in the prior art
Technical Specification specification current released version (v2.1 version) define, be located at PE_
The tag value of the KeyObject structural body in KeyList structural body in SecurityDomain structural body, be located at PE_
KeyCompontents knot in the KeyObject structural body in KeyList structural body in SecurityDomain structural body
The tag value of structure body is identical.
EUICC Profile Package Interoperable Format in compared with the existing technology
It is provided by the embodiments of the present application pre- for the current released version (v2.1 version) of Technical Specification specification
If processing rule, can be by definition " in the KeyList structural body in PE_SecurityDomain structural body
The tag value of KeyObject structural body, different from the KeyList structural body in PE_SecurityDomain structural body
The tag value of keyCompontents structural body in KeyObject structural body " mode, " definition is located at target structure to Lai Shixian
In object element tag value, different from be located at the object element in next stage element tag value " purpose.
In the embodiment of the present application, it is preferred that eUICC Profile Package in the prior art
The base of the current released version (v2.1 version) of Interoperable Format Technical Specification specification
On plinth, preset processing rule provided by the embodiments of the present application is defined " in PE_SecurityDomain structural body
The tag value of KeyObject structural body in KeyList structural body, different from being located in PE_SecurityDomain structural body
The mode of the tag value of the keyCompontents structural body in KeyObject structural body in KeyList structural body ", including three
Kind mode, specific as follows:
First way are as follows: the processing rule definition, the KeyList in PE_SecurityDomain structural body
The tag value of KeyObject structural body in structural body, is different from, eUICC Profile Package in the prior art
The current released version (v2.1 version) of Interoperable Format Technical Specification specification is determined
The tag value of KeyObject structural body adopted, in the KeyList structural body in PE_SecurityDomain structural body.
The second way are as follows: the processing rule definition, the KeyList in PE_SecurityDomain structural body
The tag value of the keyCompontents structural body in KeyObject structural body in structural body, is different from, in the prior art
EUICC Profile Package Interoperable Format Technical Specification is standardized current
Defined in released version (v2.1 version), in the KeyList structural body in PE_SecurityDomain structural body
The tag value of keyCompontents structural body in KeyObject structural body.
The third mode are as follows: the processing rule definition, the KeyList in PE_SecurityDomain structural body
The tag value of KeyObject structural body in structural body, is different from, eUICC Profile Package in the prior art
The current released version (v2.1 version) of Interoperable Format Technical Specification specification is determined
The tag value of KeyObject structural body adopted, in the KeyList structural body in PE_SecurityDomain structural body；
Also, the processing rule defines, in the KeyList structural body in PE_SecurityDomain structural body
The tag value of keyCompontents structural body in KeyObject structural body, is different from, eUICC in the prior art
The current release of Profile Package Interoperable Format Technical Specification specification
Defined in this (v2.1 version), in the KeyList structural body in PE_SecurityDomain structural body
The tag value of keyCompontents structural body in KeyObject structural body；Also, the processing rule definition is located at PE_
The tag value of the KeyObject structural body in KeyList structural body in SecurityDomain structural body, be located at PE_
KeyCompontents knot in the KeyObject structural body in KeyList structural body in SecurityDomain structural body
The tag value of structure body is different.
Optionally, eUICC Profile Package Interoperable Format in the prior art
Technical Specification specification current released version (v2.1 version) define, be located at PE_
The tag value of the KeyObject structural body in KeyList structural body in SecurityDomain structural body, be located at PE_
KeyCompontents knot in the KeyObject structural body in KeyList structural body in SecurityDomain structural body
The tag value of structure body, and tied with the KeyObject in the KeyList structural body in PE_SecurityDomain structural body
The tag value of the SEQUENCE element in keyCompontents structural body in structure body is identical.
EUICC Profile Package Interoperable Format in compared with the existing technology
It is provided by the embodiments of the present application pre- for the current released version (v2.1 version) of Technical Specification specification
If processing rule, can be by definition " in the KeyList structural body in PE_SecurityDomain structural body
The tag value of KeyObject structural body, be located at PE_SecurityDomain structural body in KeyList structural body in
The tag value of keyCompontents structural body in KeyObject structural body, and tied with PE_SecurityDomain is located at
The SEQUENCE in the keyCompontents structural body in the KeyObject structural body in KeyList structural body in structure body
It is different between the tag value of element " mode, " definition is located at the tag value, no of the object element in target structure to Lai Shixian
It is same as the tag value for the next stage element being located in the object element, and definition is located under each of described object element
The tag value of level element, different from the tag value of the element in the next stage element " purpose.
In the embodiment of the present application, it is preferred that eUICC Profile Package in the prior art
The base of the current released version (v2.1 version) of Interoperable Format Technical Specification specification
On plinth, preset processing rule provided by the embodiments of the present application is defined " in PE_SecurityDomain structural body
The tag value of KeyObject structural body in KeyList structural body, be located at PE_SecurityDomain structural body in
The tag value of the keyCompontents structural body in KeyObject structural body in KeyList structural body, and be located at PE_
KeyCompontents knot in the KeyObject structural body in KeyList structural body in SecurityDomain structural body
It is different between the tag value of SEQUENCE element in structure body " mode, it is specific as follows:
From " the KeyObject structural body in the KeyList structural body in PE_SecurityDomain structural body, with
In the KeyObject structural body in the KeyList structural body in PE_SecurityDomain structural body
KeyCompontents structural body, and be located at PE_SecurityDomain structural body in KeyList structural body in
Both chosen in this three of the SEQUENCE element in keyCompontents structural body in KeyObject structural body ", for
For each being selected, the tag value of the person is defined by the processing rule, is different from eUICC in the prior art
The current release of Profile Package Interoperable Format Technical Specification specification
The tag value of the person defined in this (v2.1 version)；Also, the tag value of the two of the processing rule definition being selected
It is different.
Optionally, eUICC Profile Package Interoperable Format in the prior art
Technical Specification specification current released version (v2.1 version) define, be located at the PE_
The tag value of ApplicaitonInstance structural body in Application structural body, be located at the PE_
The tag value of the ProcessData element in ApplicaitonInstance structural body in Application structural body is identical.
EUICC Profile Package Interoperable Format in compared with the existing technology
It is provided by the embodiments of the present application pre- for the current released version (v2.1 version) of Technical Specification specification
If processing rule, can pass through definition " in the PE_Application structural body ApplicaitonInstance knot
The tag value of structure body, different from the ApplicaitonInstance structural body in the PE_Application structural body
ProcessData element tag value " mode, realize that " definition is located at the tag value, no of the object element in target structure
It is same as the tag value for the next stage element being located in the object element " purpose.
Specifically, eUICC Profile Package Interoperable Format in the prior art
On the basis of the current released version (v2.1 version) of Technical Specification specification, the embodiment of the present application is provided
Preset processing rule, define " the ApplicaitonInstance structure in the PE_Application structural body
The tag value of body, different from the ApplicaitonInstance structural body in the PE_Application structural body
The mode of the tag value of ProcessData element ", including three kinds of modes, specific as follows:
First way are as follows: the processing rule defines, in the PE_Application structural body
The tag value of ApplicaitonInstance structural body, is different from, eUICC Profile Package in the prior art
The current released version (v2.1 version) of Interoperable Format Technical Specification specification is determined
The tag value of ApplicaitonInstance structural body adopted, in the PE_Application structural body.
The second way are as follows: the processing rule defines, in the PE_Application structural body
The tag value of ProcessData element in ApplicaitonInstance structural body, is different from, eUICC in the prior art
The current release of Profile Package Interoperable Format Technical Specification specification
Defined in this (v2.1 version), the ApplicaitonInstance structure in the PE_Application structural body
The tag value of ProcessData element in body.
The third mode are as follows: the processing rule defines, in the PE_Application structural body
The tag value of ApplicaitonInstance structural body, is different from, eUICC Profile Package in the prior art
The current released version (v2.1 version) of Interoperable Format Technical Specification specification is determined
The tag value of ApplicaitonInstance structural body adopted, in the PE_Application structural body；Also, institute
State the definition of processing rule, in the ApplicaitonInstance structural body in the PE_Application structural body
The tag value of ProcessData element, is different from, eUICC Profile Package Interoperable in the prior art
Defined in the current released version (v2.1 version) of Format Technical Specification specification, positioned at described
The tag value of the ProcessData element in ApplicaitonInstance structural body in PE_Application structural body；
Also, the processing rule definition, the ApplicaitonInstance structure in the PE_Application structural body
In the tag value of body and the ApplicaitonInstance structural body being located in the PE_Application structural body
The tag value of ProcessData element is different.
It is above only the preferred embodiment of processing rule provided by the embodiments of the present application, inventor can be according to their own needs
The particular content of any setting processing rule, it is not limited here.
For the ease of now passing through specific implementation to a kind of understanding of data processing method provided by the embodiments of the present application
It elaborates to a kind of data processing method provided by the embodiments of the present application:
1, eUICC Profile Package Interoperable Format Technical in the prior art
The current released version (v2.1 version) of Specification specification, for being located in the PE_Application structural body
ApplicaitonInstance structural body be defined as follows:
Due to eUICC Profile Package Interoperable Format Technical in the prior art
The current released version (v2.1 version) of Specification specification does not give the Tag value of ApplicaitonInstance
Specific definition out, therefore in PE_Application, according to the definition rule of ASN.1, SEQUENCE OF type
The Tag of processData also uses default value, is 0x30.
Therefore, according to eUICC Profile Package Interoperable Format in the prior art
The definition rule of current released version (the v2.1 version) and ASN.1 of Technical Specification specification, this segment data
Specific content it is as follows:
In the embodiment of the present application, it is preferred that distinguish same level to facilitate in the data structure of multilayer tag
The data content that each Tag is respectively indicated proposes to improve, and the value of 0x30 is defined as by processing rule provided by the embodiments of the present application
Others can distinguish the Tag value of data content, be exemplified below:
Increase definition [private 6] for the Tag of ApplicationInstance, the value of the Tag of processData increases
Add and is defined as [private 11], as follows:
Then processing rule provided by the embodiments of the present application has continued to use the definition rule of the tag value of element at the same level, definition
The tag value of processData data field is [PRIVATE 11], that is, 0xEB.Definition can be easily discriminated each Tag in this way
The data content of representative, but it is almost the same with the definition rule of the Tag of identical level.
According to the rule of ASN.1, then the Tag value of ApplicationInstance is 0xC6, keyCompontents's
Tag value is 0xEB.
Correspondingly, improved data structure is as follows:
2, eUICC Profile Package Interoperable Format Technical in the prior art
The current released version (v2.1 version) of Specification specification, for the important element of PE_SecurityDomain
KeyList is defined as follows: KeyList SEQUNECE OF KeyObject OPTIONAL, and for KeyObject,
SEQUENCE categorical data, just like giving a definition:
Wherein, same to be explicitly defined because not providing, according to the definition rule of ASN.1, SEQUNCE type
The Tag of KeyObject uses default value 0x30, wherein may include one or more by above again under keyCompontents
The SEQUENCE of three elements composition.
Therefore, according to eUICC Profile Package Interoperable Format in the prior art
The definition rule of current released version (the v2.1 version) and ASN.1 of Technical Specification specification, this segment data
Specific content it is as follows:
At this point, just having multiple tag values in multilayer is 0x30, the understanding and data parsing for data are all brought very
It is big difficult.
And in ASN.1, the definition of the default Tag value of SEQUENCE and SEQUENCE OF both types, industry
Also it disagrees, or is defined as 0x30, or be defined as 0x10.
In the embodiment of the present application, it is preferred that distinguish same level to facilitate in the data structure of multilayer tag
The data content that each Tag is respectively indicated proposes to improve, and the Tag for being KeyObject, which increases, defines [14], KeyComponents
The value increase of Tag be defined as [6], it is as follows:
According to the rule of ASN.1, then the Tag value of KeyObject is 0xAE, and the Tag value of keyCompontents is
0xA6。
Correspondingly, improved data structure is as follows, wherein green font is to update key point:
By above-mentioned to a kind of description of the specific implementation of data processing method provided by the embodiments of the present application, so that
A kind of data processing method provided by the embodiments of the present application is clearer, perfect.
The embodiment of the present application provides a kind of data processing method, passes through the target object that determination is to be processed；Based on preset
The tag value for the element that processing rule is defined, calls during handling the target object, at the element
Reason, to obtain handling result (wherein, the regular mesh defining, in target structure of the processing of the target object
Mark element tag value, different from be located at the object element in next stage element tag value) mode so that processing mesh
When marking object, convenient for the area to the object element and the next stage element in the object element that are located in target structure
Point, to reduce the generation of data processing complex, error-prone situation in generation/parsing eUICC data.
It is illustrated in figure 2 a kind of structural schematic diagram of data processing equipment provided by the embodiments of the present application.
As shown in Fig. 2, the device includes:
Determination unit 21, for determining target object to be processed；
Processing unit 22, for being based on defined in preset processing rule, during handling the target object
The tag value of the element of calling, handles the element, to obtain handling the result of the target object；
Wherein, the definition of processing rule, object element in the target structure tag value, different from being located at
The tag value of next stage element in the object element.
In the embodiment of the present application, it is preferred that the processing rule includes eUICC Profile Package
Interoperable Format Technical Specification specification.
The embodiment of the present application provides a kind of data processing equipment, passes through the target object that determination is to be processed；Based on preset
The tag value for the element that processing rule is defined, calls during handling the target object, at the element
Reason, to obtain handling result (wherein, the regular mesh defining, in target structure of the processing of the target object
Mark element tag value, different from be located at the object element in next stage element tag value) mode so that processing mesh
When marking object, convenient for the area to the object element and the next stage element in the object element that are located in target structure
Point, to reduce the generation of data processing complex, error-prone situation in generation/parsing eUICC data.
Each embodiment in this specification is described in a progressive manner, the highlights of each of the examples are with other
The difference of embodiment, the same or similar parts in each embodiment may refer to each other.For device disclosed in embodiment
For, since it is corresponded to the methods disclosed in the examples, so being described relatively simple, related place is said referring to method part
It is bright.
The above is only the preferred embodiment of the application, make skilled artisans appreciate that or realization the application.It is right
A variety of modifications of these embodiments will be apparent to one skilled in the art, general original as defined herein
Reason can be realized in other embodiments without departing from the spirit or scope of the application.Therefore, the application will not
Be intended to be limited to the embodiments shown herein, and be to fit to it is consistent with the principles and novel features disclosed in this article most
Wide range.
Claims (10)
1. a kind of data processing method characterized by comprising
Determine target object to be processed；
It is right based on the preset tag value for handling the element that rule is defined, calls during handling the target object
The element is handled, to obtain handling the result of the target object；
Wherein, the definition of processing rule, object element in the target structure tag value, be different from being located at it is described
The tag value of next stage element in object element.
2. the method according to claim 1, wherein processing rule includes eUICC Profile
Package Interoperable Format Technical Specification specification.
3. method described in -2 any one according to claim 1, which is characterized in that the target structure is positioned at PE_
When KeyList structural body in SecurityDomain structural body,
The object element is the KeyObject structural body in the KeyList structural body.
4. according to the method described in claim 3, it is characterized in that, the next stage element in the object element,
It include: the keyCompontents structural body in the KeyObject structural body.
5. according to the method described in claim 4, it is characterized in that, processing rule also defines, is located at the object element
In each next stage element tag value, different from the tag value of the element in the next stage element.
6. according to the method described in claim 5, it is characterized in that, the next stage element in the object element,
When including: the keyCompontents structural body in the KeyObject structural body,
Element in the described next stage element, comprising: the SEQUENCE member in the keyCompontents structural body
Element.
7. method described in -2 any one according to claim 1, which is characterized in that the target structure is PE_
When Application structural body,
The object element is the ApplicaitonInstance structural body in the PE_Application structural body.
8. the method according to the description of claim 7 is characterized in that the next stage element in the object element,
It include: the ProcessData element in the ApplicaitonInstance structural body.
9. a kind of data processing equipment characterized by comprising
Determination unit, for determining target object to be processed；
Processing unit, for based on defined in preset processing rule, call during handling the target object
The tag value of element, handles the element, to obtain handling the result of the target object；
Wherein, the definition of processing rule, object element in the target structure tag value, be different from being located at it is described
The tag value of next stage element in object element.
10. device according to claim 9, which is characterized in that the processing rule includes eUICC Profile
Package Interoperable Format Technical Specification specification.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710712753.9A CN109408779B (en) | 2017-08-18 | 2017-08-18 | Data processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710712753.9A CN109408779B (en) | 2017-08-18 | 2017-08-18 | Data processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109408779A true CN109408779A (en) | 2019-03-01 |
| CN109408779B CN109408779B (en) | 2023-03-17 |
Family
ID=65463167
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710712753.9A Active CN109408779B (en) | 2017-08-18 | 2017-08-18 | Data processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109408779B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080097744A1 (en) * | 2006-10-20 | 2008-04-24 | Adobe Systems Incorporated | Context-free grammar |
| CN105407475A (en) * | 2015-12-03 | 2016-03-16 | 中国联合网络通信集团有限公司 | Processing method for use of configuration file and eUICC (Embedded Universal Integrated Circuit Card) |
| CN106814998A (en) * | 2015-11-27 | 2017-06-09 | 阿里巴巴集团控股有限公司 | List sequencing method and device |
-
2017
- 2017-08-18 CN CN201710712753.9A patent/CN109408779B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080097744A1 (en) * | 2006-10-20 | 2008-04-24 | Adobe Systems Incorporated | Context-free grammar |
| CN106814998A (en) * | 2015-11-27 | 2017-06-09 | 阿里巴巴集团控股有限公司 | List sequencing method and device |
| CN105407475A (en) * | 2015-12-03 | 2016-03-16 | 中国联合网络通信集团有限公司 | Processing method for use of configuration file and eUICC (Embedded Universal Integrated Circuit Card) |
Non-Patent Citations (4)
| Title |
|---|
| HONG ZHU 等: ""Quality Model and Metrics of Ontology for Semantic Descriptions of Web Services"", 《TSINGHUA SCIENCE AND TECHNOLOGY》 * |
| 肖珑 等: ""描述元数据结构及其扩展规则研究"", 《现代图书情报技术》 * |
| 胡明: ""基于OLAP的多维关联规则挖掘研究"", 《东北师大学报（自然科学版）》 * |
| 赵治国 等: ""基于Linux的网络监控技术的实现"", 《计算机与现代化》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109408779B (en) | 2023-03-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106990952B (en) | Form verification method and system based on Vue | |
| CN105704188B (en) | Using the dispositions method and device with service | |
| CN104035804B (en) | A kind of application integration method and device | |
| CN106095432B (en) | Method for identifying application type | |
| CN103116503B (en) | The implementation method of a kind of multiwindow and device | |
| CN106170993B (en) | Intermediate node in M2M network is avoided to the circulation in intermediate node registration | |
| CN105511864A (en) | Resource positioning method and device | |
| CN108984328A (en) | A kind of method and device of Stack back trace | |
| CN104636154B (en) | Application program installation method and device | |
| CN105975277A (en) | Template-based mixed cloud elastic telescoping set building method | |
| CN106325800A (en) | Method, system and mobile terminal for controlling screen resolution | |
| CN109408779A (en) | A kind of data processing method and device | |
| CN103793875B (en) | A kind of image processing system for supporting third-party application | |
| CN105516782B (en) | The realization method and system of android system smart television suspension interface mutual exclusion function | |
| CN104717103A (en) | Method and device for testing network device | |
| CN104883819B (en) | PCB silk-screen processing method and system | |
| CN103108242A (en) | Method of solving conflict between intelligent television video application and television video | |
| CN107391283A (en) | A kind of message treatment method and device | |
| CN105812596B (en) | Caller ID display method, relevant apparatus and system in a kind of IMS network | |
| CN104052638B (en) | Intermodule collision detection method, device and server | |
| CN105451233B (en) | A kind of anti-method monitored, system and mobile terminal | |
| CN103309710A (en) | Method and system for loading OUT file through VXWORKS operating system | |
| CN106911634A (en) | A kind of login method and equipment | |
| CN110175030A (en) | A kind of API service gateway processes method | |
| CN109410176A (en) | A kind of method, apparatus and storage medium monitoring shelf assembled state |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |