Patent Application
20150220650
The disclosure relates to the field of Internet technologies, and in particular, to a blog content search method and system.
A blog article or a microblog article published within a certain time segment may be searched in some situations. For example, a user may want to find and view an interesting quotation or article published at a certain time, and the user may search for the blog content within a specified time segment via a search time segment range in a blog search entry. For example, the blog content may be searched for content added on the previous day, within the last three days, or the like.
In an existing blog content search method, inverted data blocks are generated according to an reverse chronological sequence of articles based on their respective publication time. The inverted data blocks may include an inverted index data structure storing a mapping from the content, such as words to corresponding locations in a database file, or in a document, or a set of documents. The inverted data blocks may be used to perform a full text search to find particular words in the blog content. Upon receiving a search request including constituent search terms and a search time segment, the inverted data blocks of the constituent search terms are obtained and then merged. It is then determined whether the publication time of the content corresponding to the merged blocks is within the search time segment in the search request. The merged blocks are discarded if the publication time is not within the request time segment, else and the merged blocks are used as a qualified result if the corresponding publication time is within the requested time segment. When merging of the inverted data block of a search term is completed, merging continues to be performed on a next inverted data block of the search term, until merging of all inverted data blocks of the search term is completed or enough results are found.
In the existing blog content search method, merging and determining are performed on each inverted data block, which causes a long searching time, and a user needs to wait for a long time to obtain the search result. In addition, in the existing blog content search method, the result is returned, and the search is stopped, when certain amount of blog content is found. Therefore, the user may not find the expected result since not all results are returned.
In one aspect of the present disclosure, a blog content search method is provided. the method may include receiving a search request, the search request including a search term and a search time segment range. The blog content search method also includes searching for a first inverted data block of the search term from a database. The blog content search method also include skipping, according to a timestamp skip list of the first inverted data block and the search time segment range, to a second inverted data block including data that meets a condition of the search request. The blog content search method may include performing merging on the second inverted data block. The blog content search method also includes providing a search result based on a search performed based on the result of the merging.
The blog content search method may further include generating inverted data blocks of a unit of content before receiving the search request, where the inverted data blocks of the unit of content are generated according to a blog content publication time. The blog content search method may also include adding a timestamp skip list indicating the blog content publication time to the inverted data blocks. The timestamp skip list may include a timestamp indicating last publication of each article of the inverted data block, and the timestamp skip list is added to a header of the inverted data block. Receiving the search request may include determining whether the search request contains the search time segment range. The merging may be performed on the second inverted data block of the search term including data that meets the condition if the search request contains the search time segment range. The merging may be performed on the first inverted data block which is searched for from the database if the search request does not carry the search time segment range. Skipping, according to the timestamp skip list of the first inverted data block and the search time segment range, to the second inverted data block including data that meets the condition includes: identifying that the second inverted data block includes data that meets the condition by using header information of the second inverted data block of the search term. The blog content search method may also include skipping to the second inverted data block including data that meets the condition. The performing merging on the second inverted data block including data that meets the condition may include performing time filtering on a merging result. The blog content search method may also include determining whether a predetermined number of filtering results have been found. The blog content search method may also include returning the filtering results as the search result if the predetermined number of filtering results have been found. The blog content search method may also include skipping, according to the timestamp skip list of the second inverted data block and the search time segment range, to another inverted data block including data that meets the condition if the number of filtering results that have been found is less than the predetermined number. The method may be applied to a conventional blog, a microblog, or a light blog.
In another aspect of the present disclosure, a blog content search system is further provided, including a processor and a non-transitory processor-readable medium having processor-executable instructions stored thereon, the processor-executable instructions including a plurality of modules. The modules may include a request receiving module configured to receive a search request, the search request including a search term and a search time segment range. The blog content search system also include a data skipping module configured to search for a first inverted data block of the search term from a database according to the search term in the search request, and skip searching the first inverted data block, according to a timestamp skip list of the first inverted data block and the search time segment range, to a second inverted data block including data that meets a condition of the search request. The blog content search system may also include a result returning module configured to perform merging on the second inverted data block including data that meets the condition and obtain a search result for the search request.
In still another aspect of the present disclosure, a computer program including program code is further provided. Execution of the program code may include receiving a search request, the search request including a search term and a search time segment range. The execution of the computer program also includes searching for inverted data blocks of the search term from a database. The execution of the computer program also includes identifying, according to a timestamp skip list of the respective inverted data blocks and the search time segment range, an inverted data block including data that meets the search request. The execution of the computer program also includes performing merging on the inverted data block including data that meets the search request and obtaining a search result.
According to the blog content search method and system of the present disclosure, a timestamp skip list indicating a blog content generation time is added to a header of the inverted data block. The inverted data block is directly skipped to an inverted data block from which a result may be obtained using the timestamp skip list based on a search time segment range input by a user. In this way, the search time is shortened and the search efficiency is improved. In addition, old data can be searched via the timestamp skip list, which ensures accuracy and completeness of the search result.
The foregoing description is only a summary of the technical solutions of the present disclosure. To understand and implement the technical solutions according to the disclosure and to make the foregoing and other aspects, features, and advantages of the present disclosure more understandable, embodiments of the present disclosure are described in detail below with reference to accompanying drawings.
The example embodiments described throughout the present disclosure may be better understood with reference to the following drawings and description. The components in the drawings are not necessarily to scale. Moreover, in the drawings, like-referenced numerals designate corresponding parts throughout the different views.
The foregoing and other technical content, features and effects of the present disclosure are clearly presented in the following description and accompanying drawings. The technical solutions and effects of the present disclosure can be understood through the detailed descriptions. The accompanying drawings and embodiments are merely provided for reference and description, and are not intended to limit the present disclosure.
In S100, a time stamp skip list indicating a blog content publication or generation time may be added to an inverted data block of the blog content.
The blog content may be published as, or may be part of one or more blog articles. A blog article may also be referred to as a blog post. The blog articles may be part of a single blog or multiple blogs. The blogs may be hosted by a blogging platform (such as WordPress), a microblog platform (such as Twitter), or a light blogging platform.
An inverted data block may be generated according to a reverse chronological sequence for a piece of blog data in blog content published within a predetermined period of time. The piece of blog data may be a unit of content, such as a word, a number, a phrase, or a sentence in the blog content. The inverted data block may include an inverted index data structure storing a mapping from the unit of content to corresponding location of the unit of content in a database file, or in a document, or a set of documents that contains the blog articles. The inverted data block may be used to perform a full text search to find occurrences of the unit of content in the blog content. In an example, the inverted data block may map the unit of content to chronological occurrence of the unit of content in the blog by using the predetermined period of time. The predetermined period of time may be one month, three months, or a time period set by a user or a system.
Alternatively, an inverted data blocks may be generated to map the unit of content to a sequential occurrence of the unit of content in the blog by using the a predetermined number of units of content. The mapping may be performed in reverse chronological order of publication. For example, the inverted data blocks may identify inverted index of the unit of content in a sequence of 5000 pieces of published blog data, or 10000 pieces of published blog data, or an arbitrary number of pieces of blog data set by the user or system.
For example, consider a blog that has been in publication for one year and that includes 50000 pieces of blog data. In an example, the blog may be indexed into four inverted data blocks in case the inverted data blocks are generated according to publication time of three months each. The inverted index of the unit of content in this case would map occurrence of the unit of information within the four possible blocks of three months each. In another example, the blog may be indexed into five inverted data blocks in case the inverted data blocks are generated according to an inverted sequence of publication time with 10000 pieces of blog data in each block. The inverted index of the unit of content in this case would map occurrence of the unit of information within the five possible blocks of 10000 units of content each. In addition, the blog content may be ranked according to the blog data generation time, which may be the time at which the blog data is published or posted.
In an example, the inverted data block may have a corresponding header. A timestamp skip list may be added to the header of the inverted data block. The timestamp skip list may be used to identify the inverted data block of the blog from which a search result may be obtained based on a search term and a search time segment range of a search query. The timestamp skip list may facilitate skipping one or more inverted data blocks of the search term during the search, thus facilitating a more efficient and consequently a quicker search. An example structure of the header of the inverted data block is as follows:
The timestamp skip list (TimeStampSkipList) may include a timestamp that indicates a time at which the latest (in time) post, or article of each inverted data block was published or generated. In an example, the timestamp skip list may be stored as an array with a total of 4*BlockNum bytes, where BlockNum is the total number data blocks that are indexed by the inverted data block. For example, if the inverted data block maps occurrence of the unit of information across fifty (50) articles, the BlockNum is 50. It may be understood that the header structure of the inverted data block is not limited to the foregoing specific structure.
In S110, a blog content search request may be received. The search request may include a search term and a search time segment range.
In S110, the search time segment range may be set arbitrarily by a user.
In S120, an inverted data block corresponding to the search term may be searched for and obtained from a database. The identified inverted data block may be skipped, according to a time stamp skip list in the header of the identified inverted data block, to another inverted data block including data that meets a predetermined condition.
Thus, in step S120, a set of inverted data blocks corresponding to the search term may be identified. Further, from the identified set of inverted data blocks, a subset of inverted data blocks including data that meets the predetermined condition are determined by using header information of the inverted data blocks in that set. Further yet, from the subset of inverted data blocks, the inverted data block that includes data that meets the predetermined condition is obtained to perform a subsequent search operation.
In an example where the search term contains more than one constituent terms, another inverted data block of the search term may be obtained for each constituent term. Thus, Step S120 may provide one or more inverted data blocks that include data that meets the predetermined condition and that may be used for the subsequent search operation.
The inverted data block including data that meets the condition may refer to that the inverted data block possibly including data that meets the search time segment range in the search request.
In S130, merging may be performed on the inverted data block that include data that meets the condition. Further, time filtering may be performed on the results of the merging, and a search result from the time filtered inverted data block may be returned. For example, the inverted data blocks identified for each separate constituent terms of the search term may be merged by S130.
The time filtering may include filtering the results of the merging operation according to the search time segment range input by the user. If enough results are obtained after the time filtering is performed on the results of the merging, the search may end; or otherwise, the step S120 may be performed to search for a next inverted data block including data that meets the condition.
The following is a specific application of an example blog data search method described throughout the present disclosure. It will be understood that embodiments of the present disclosure are not limited to the specific application. For example, a user may search blog content with a combination of a keyword A and a keyword B, and with a search time segment range from 2011-4-1 to 2011-4-10. The keyword A and the keyword B may be combined in any form, for example, the keyword A and the keyword B may be combined to form a character string “AB”; or the keyword A and the keyword B may be separated by using a symbol such as a space.
The inverted data blocks of the blog may include time information. The time information may be added by an indexing module of a system that searches the blog. In an example, the time information may be in a format of an array composed of a timestamp indicating time of generation of the last article of each inverted data block. For example, timestamp skip list information of the keyword A for a corresponding inverted data block is {2012-4-01 0:0:0, 2012-1-01 0:0:0, 2011-8-01 0:0:0, 2011-6-01 0:0:0, 2011-1-01 0:0:0, 2010-10-01 0:0:0, . . . }, and timestamp skip list information of the keyword B for a corresponding inverted data block is {2012-3-01 0:0:0, 2011-12-01 0:0:0, 2011-7-01 0:0:0, 2011-3-01 0:0:0, 2011-2-01 0:0:0, 2010-11-01 0:0:0, . . . }. In an example, keywords A and B may each have multiple timestamp skip list. Each timestamp skip list may correspond to respective inverted data block. In another example, each keyword may have a single timestamp skip list that is added to headers of each inverted data block of the keyword.
A search module performs the following steps (1) to (4) according to a data index provided by the indexing module.
(1) The first inverted data blocks of the keywords A and the keyword B and their relevant information are obtained separately. Each keyword may have a corresponding first inverted data block.
(2) It is determined, according to the timestamp skip list in the first inverted data block, whether a result that meets a condition may be obtained from the first inverted data block; and if not, the first inverted data block is skipped and the second inverted data block is obtained, and so on.
It may be determined, according to the timestamp skip list, that timestamp information of the first to fourth inverted data blocks of the keyword A is respectively 2012-4-01 0:0:0, 2012-1-01 0:0:0, 2011-8-01 0:0:0, and 2011-6-01 0:0:0, which are all later than the search time segment range from 2011-4-1 to 2011-4-10. Therefore, the result that meets the condition cannot be obtained from the first to fourth inverted data blocks. Time stamp information of the fifth inverted data block 2011-1-01 0:0:0 is earlier than the search time segment range from 2011-4-1 to 2011-4-10. Hence, a result that meets the condition may be obtained from the fifth inverted data block for the keyword A. Similarly, a result that meets the condition may be obtained from the fourth inverted data block for the keyword B.
(3) The two inverted data blocks of the two keywords A and B that meet the condition may be selected, in the above example, the fifth inverted data block of the keyword A and the fourth inverted data block of the keyword B, are selected. Merging may be performed on the two inverted data blocks. Blog articles that include the combination of the two keywords A and B are found from the merged blocks. In addition, time filtering may be performed on the merged blocks to find a blog article that includes the combination of the two keywords A and B and is within the search time segment range from 2011-4-1 to 2011-4-10.
(4) If at least a predetermined number of results that are obtained from the merged blocks corresponding to the condition using a combination of the two keywords A and B, the search may end; or otherwise, step (2) may be performed again to search for a next inverted data block from which a result that meets the condition may be obtained.
In S200, an inverted data block may be generated according to a blog content publication or generation time.
In an example, the inverted data block is generated according to a chronologically reverse sequence of blog content published for a certain period of time. The predetermined time period may be one month, three months, or any other time period. The time period may be setup by a user or a system. Alternatively, the inverted data block may be generated according to a reverse chronological sequence of published blog content for certain pieces of blog data. For example, the inverted data block may be for a certain number of pieces of blog data such as 5000 blog posts, or 10000 blog posts, or any other number of blog posts. The user or system may set the number of blog posts included in the inverted data block. For example, an entire blog is with a publication time of one year and blog data of 50000 pieces, then there are totally four inverted data blocks in a case that the inverted data blocks are generated according to an inverted sequence of publication time for three months, and there are totally five inverted data blocks in a case that the inverted data blocks are generated according to an inverted sequence of publication time for 10000 pieces of blog data.
In S210, a timestamp skip list indicating a blog content publication or generation time may be added to the inverted data block.
The timestamp skip list may be added to a header of each inverted data block. The timestamp skip list may be used to directly skip to an inverted data block from which a result may be obtained, instead of searching through all inverted data blocks of the blog being searched. For example, the timestamp skip list may facilitate the skipping based on the search time segment range in the search request. In an example, a header structure of the inverted data block is as follows:
The timestamp skip list (TimeStampSkipList) may include a time stamp indicating generation of the last article of each inverted data block, which forms an array and has a total of 4*BlockNum bytes. It may be understood that the header structure of the inverted data block is not limited to the foregoing specific structure.
In S220, a blog content search request may be received, and it may be determined whether the search request includes a time segment range. S230 may be performed if the search request includes a time segment range, else S240 may be performed if the search request does not include a time segment range. The search request may include a search term. The search term may include a combination of one or more keywords. For example, the combination may be a Boolean expression of the one or more keywords.
The time segment range in the received search request may be set by a user. The time segment range may indicate that only the blog posts published during that time segment range are to be searched for the search term included in the search request.
In S230, a first inverted data block of a search term in the search request is obtained. The first inverted data block may be skipped, that is a search within the first inverted data block may not be performed, in response to the timestamp skip list in the header of the first inverted data block failing to meet the time segment range of the search request. For example, the timestamp skip list in the header of the first inverted data block may be outside the time segment range. Further, a second inverted data block of the search term that meets the condition may be identified using the timestamp skip list. The second inverted data block may be searched for the search term of the search request to obtain search results.
In S230, a first inverted data block of the search term may be selected. Whether the first inverted data block includes data that meets the condition may be determined by first examining the header information of the first inverted data block. A subsequent search operation may be performed within the first inverted data block, if examining the timestamp skip list in the header information indicates that the first inverted data block contains content published in the search time segment range of the search request. In addition or alternatively, a second inverted data block of the search term may also be selected.
In S240, merging may be performed on the first inverted data block that includes data that meets the condition. For example, the first inverted data block may be merged with the second inverted data block. In an example, the first inverted data block and the second inverted data block may each correspond to separate constituent terms within the search term. Time filtering may be performed on a merging result.
The time filtering refers to filtering the merging result according to the search time segment range of the search request.
In S250, it may be determined whether the number of filtering results meets a predetermined threshold number. In case the predetermined threshold number is reached, S260 may be performed; otherwise, S230 may be performed.
In S260, a search result may be returned and presented in response to the search request. For example, the result may be displayed on a display device. Alternatively or in addition, the result may be transmitted to a device for presentation.
The information adding module 310 may add a timestamp skip list indicating a blog content publication or generation time to an inverted data block of blog content.
The timestamp skip list may be added to a header of each inverted data block. The timestamp skip list may be used to directly skip to an inverted data block from which a result may be obtained based on the search time segment range of a search request. For example, the information adding module 310 may add a header to each inverted data block, with the header having a following structure. In other examples, the information adding module 310 may add headers with different structures.
The timestamp skip list (TimeStampSkipList) in a header of the inverted data block may include a timestamp that represents time of generation of the last article of the data block indexed by the inverted data block. In an example, the timestamp skip list may be recorded as an array that has a total of 4*BlockNum bytes, where the BlockNum is the number of data blocks that are indexed by the inverted data block. It will be understood that the header structure of the inverted data block is not limited to the foregoing specific structure.
The request receiving module 320 may receive a blog content search request. The search request may include a search term and a time segment range. The search term may include one or more keywords. The search term may be a combination, such as a Boolean expression, of the keywords. The time segment range may limit the blog posts that are to be searched for the search term. The time segment range may be set according to requirement of a user initiating the search request.
The request receiving module 320 may separate the search term into its constituent keywords. The system may search for inverted data blocks for the separate keywords and the results may then be merged as described throughout the present disclosure.
The data skipping module 330 may search for and identify one or more inverted data blocks corresponding to the search term in the search request. For example, the data skipping module 330 may identify the inverted data blocks from a database according to the search term in the search request.
The data skipping module 330 may examine the timestamp skip list in the respective headers of the one or more identified inverted data blocks. The data skipping module 330, based on the examination, may determine to skip performing a subsequent search based on an inverted data block. The data skipping module 330 may, instead, identify a second inverted data block that corresponds to the search term, and meets a condition to perform a subsequent search operation based on the timestamp skip list of the second inverted data block. In addition, the data skipping module 330 may identify more inverted data blocks corresponding to the search term to perform further search operation on.
The result returning module 340 may perform merging and filtering on the inverted data blocks identified by the data skipping module 330. The result returning module 340 may also return a search result.
The data generating module 410 may generate an inverted data block according to a blog content based on publication or generation time of blog content. The data generating module 410 may generate the inverted data block according to a reverse chronological sequence of the publication time of the blog content. In addition, the data generation module 410 may rank the blog content according to the publication time of the blog content.
The information adding module 310 may add the timestamp skip list that indicates the blog content publication or generation time to the header of the inverted data block of blog content.
A timestamp skip list may be added to a header of the inverted data block. The inverted data block may be directly skipped to another inverted data block from which a result may be obtained via the timestamp skip list based on the search time segment range input by a user. For example, a header structure of the inverted data block is as follows:
The timestamp skip list (TimeStampSkipList) may include a time stamp indicating generation of the last article of each data block indexed by the inverted data block. The timestamp skip list may form an array that has a total of 4*BlockNum bytes, BlockNum being the number of the data blocks indexed. It may be understood that the header structure of the inverted data block is not limited to the foregoing specific structure.
The request receiving module 320 may receive a blog content search request. The search request may contain a search term and a search time segment range. The search request may initiate a search for posts that are related to the search term and have been posted within the search time segment range using the blog search system and/or methods described throughout the present disclosure.
The request determining module 420 may determine whether the search request contains the time segment range. If the search request contains the time segment range, the data skipping module 330 may identify an inverted data block corresponding to the search term. Otherwise, if the search request does not carry a time segment range, the result filtering module 430 may perform a merging operation on the inverted data block that include data that meets a condition of the search term alone.
The data skipping module 330 may search for and obtain an inverted data block of the search term from a database. The data skipping module 330 may examine the timestamp skip list of the inverted data block based on the search time segment range. Based on the examination, the data skipping module 330 may skip to another inverted data block including data for the search term. The data skipping module 330 may obtain the inverted data blocks of the search term, determine a first inverted data block including data that meets the time range condition by using the header information of the first inverted data block, and then obtain the data block indexed by the inverted data block that on which to perform a subsequent search operation. In addition, the data skipping module may also obtain another inverted data block for the search term, for example for a separate constituent within the search term.
The result filtering module 430 may perform merging on the inverted data blocks that data that meets the condition of the search query. The result filtering module 430 may perform time filtering on the resulting merged inverted data blocks, and return a filtering result.
The result determining module 440 may determine whether the number of filtering results reaches a set number; and if the number of filtering results reaches the set number, the result returning module returns the search result; or otherwise, the data skipping module obtains another inverted data block of the search term.
The result returning module 340 may return the search result.
According to an embodiment of the present disclosure, the blog content search method shown in
According to another embodiment of the present disclosure, the blog content search method shown in
According to another embodiment of the present disclosure, some or all of the modules in the blog content search system shown in
According to another embodiment of the present disclosure, the blog content search system shown in
According to the blog content search method and system in the embodiments of the present disclosure, a timestamp skip list indicating a blog content generation time is added to a header of the inverted data block, and it is directly skipped to an inverted data block from which a result may be obtained via the timestamp skip list based on a search time segment range input by a user. In this way, the search time is shortened and the search efficiency is improved. In addition, old data can be searched via the timestamp skip list, which ensures accuracy and completeness of the search result.
For example, a blog may contain multiple articles. Each article may contain text and/or numbers. Each article may be associated with a respective timestamp at which the article was published. The blog may be indexed to obtain inverted data blocks, or inverted indices of the articles. For example, an inverted index may be obtained for each text symbol that may be found in the articles. The inverted index for a symbol, for example, may indicate all the articles in which that symbol is used.
The inverted indices are used in response to a search query that may be received to search for a search term. The search term may include one or more keywords. Using the inverted indices for a first keyword, a set of articles that contain the first keyword may be identified. Similarly, sets of articles that contain the other keywords of the search term may be identified using the inverted indices of the respective keywords. The identified sets may be merged, by taking an intersection of the sets, to identify the articles that contain all the keywords in the search term.
The described examples of method and system for blog search improve a conventional search technique by generating inverted indexes in an innovative manner. For example, the inverted indexes are generated in reverse chronological order of the articles in the blog and further, separate inverted indexes may be generated for predetermined blocks of the articles. For example, the articles may be divided based on a publication time. For example, the articles of the blog may be categorized into groups of articles published within three month periods. Separate inverted indexes may be generated for each group. Alternatively, the articles may be grouped based on a number of articles, such as each group contains 5000 articles. Inverted indexes may be generated for each such group.
A further improvement proposed in the present disclosure is to add, in a header of each inverted index, a timestamp skip list. The timestamp skip list may identify the last publication time of an article that is indexed in the inverted index. Such a modified inverted index strategy, as described throughout the above examples, facilitates efficient search. Particularly, higher efficiency may be observed if the search request contains a search term and a search time range that indicates searching only those articles that have been published within the specified time range. In such a case, the timestamp skip list may facilitate skipping the inverted index that may not provide a result for the search result. Thus, only those inverted indexes that identify articles that were published within the specified time range are merged using this strategy. Accordingly, a detailed search is performed on lesser number of articles thus leading to quicker search results.
A second action may be said to be “in response to” a first action independent of whether the second action results directly or indirectly from the first action. The second action may occur at a substantially later time than the first action and still be in response to the first action. Similarly, the second action may be said to be in response to the first action even if intervening actions take place between the first action and the second action, and even if one or more of the intervening actions directly cause the second action to be performed. For example, a second action may be in response to a first action if the first action sets a flag and a third action later initiates the second action whenever the flag is set.
To clarify the use of and to hereby provide notice to the public, the phrases “at least one of <A>, <B>, . . . and <N>” or “at least one of <A>, <B>, . . . <N>, or combinations thereof” or “<A>, <B>, . . . and/or <N>” are to be construed in the broadest sense, superseding any other implied definitions hereinbefore or hereinafter unless expressly asserted to the contrary, to mean one or more elements selected from the group comprising A, B, . . . and N. In other words, the phrases mean any combination of one or more of the elements A, B, . . . or N including any one element alone or the one element in combination with one or more of the other elements which may also include, in combination, additional elements not listed.
While various embodiments have been described, it will be apparent to those of ordinary skill in the art that many more embodiments and implementations are possible. Accordingly, the embodiments described herein are examples, not the only possible embodiments and implementations.
| Number | Date | Country | Kind |
|---|---|---|---|
| 201210401046.5 | Oct 2012 | CN | national |
The present application is a continuation of International Patent Application No. PCT/CN2013/082893, filed on Sep. 4, 2013, which claims the priority to Chinese Patent Application No. 201210401046.5, filed on Oct. 19, 2012, both of which are incorporated herein by reference in their entirety.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2013/082893 | Sep 2013 | US |
| Child | 14688101 | US |
