BACKGROUND

[0001] Serialization is used to uniquely identify each of a large set of items. For example, bar codes may be used to identify retail items. Similarly, serial numbers on various products are used to identify each individual product in the set. Such identifiers may be applied to packaging material or may be applied to objects using labels or medallions, or even impressed or stamped on the object.

BRIEF DESCRIPTION OF THE DRAWINGS

[0002] For a more complete understanding of various examples, reference is now made to the following descriptions taken in connection with the accompanying drawings in which:

[0003] Figure 1 illustrates an example object with a serialization identifier;

[0004] Figure 2 illustrates an example identifier and an example progression;

[0005] Figure 3 illustrates an example progression of a binary representation of identifiers.

[0006] Figure 4 illustrates an example system for generation of identifiers; and

[0007] Figure 5 is a flow chart illustrating an example method.

DETAILED DESCRIPTION

[0008] In various examples, a set of identifiers for mass serialization may be created for a set of items. The items may be any of a variety of items, such as items for retail sale, packaging or manufacturing, for example. In various examples, each identifier in the mass serialization set may have a representation, such as a binary representation. The representation of the identifiers may be of a predetermined length of characters such as letters or digits or, in the case of binary strings, a predetermined length of bits having a value of "0" or "1". In the various examples described herein, identifiers represented as binary strings are used. Those skilled in the art will appreciate that other types of representations are possible and are contemplated. In accordance with the disclosed examples, the number of a certain character in a representation of the identifier, such as the number of 1 's in a binary string, may be within a predefined range. In some examples, the number of the certain character in the representation may be set at a different number at different stages of a serialization flow, such as from production to packaging to retail, for example.

[0009] In various examples described herein, identifiers may be generated and/or used for mass serialization, such as for unique identification of a product. Referring now to Figure 1 , an example object 10 is illustrated with an example identifier 20. The object 10 may be any of a variety of objects, such as an object for retail sale, a component for a larger assembly, etc. The identifier 20 may be any of a variety of identifiers, such as a bar code 22, a 2-D bar code such as a quick-response (QR) code 24, or the like. The identifier 20 may be used to identify various features of the product 10. For example, in the retail arena, the identifier 20 may be used to identify the type of product (e.g., brand, type and size of a box of cereal) to be used at the point of sale. In other examples, the identifier 20 may be used to uniquely identify each item in a set of items such as, for example, a serial number for each component in a set of identical components.

[0010] A set of identifiers for mass serialization may require a large number of unique identifiers. For example, a serial number may be assigned to each unit of a product for which a large number of units may be produced. Thus, each unit would be assigned a unique identifier.

[0011] A discussion of certain concepts is useful in understanding the various examples described herein. First, it is noted that the number of combinations (C _n , _P ) for selecting p items out of n items, where p and n are both non-negative integers and where p < n, is defined as: where n! is the factorial operator: n! = n _* (n-1) _* (n-2) _* ... _* 1. By definition, 0! = 1.

[0012] Serialization may provide a unique identifier to each of a plurality of items. For serialization, the number of serialization combinations is dictated by the base, b, of the character to be printed, raised to the power of N, the number of digits to be printed. For example, if the 26 uppercase and 26 lowercase English characters, along with the 10 numerals are used, then the base is 62, and the number of possible mass serialized values is 62 ^N . In other examples, for a binary string, the base is 2. In general, the number of mass serialized values, n _M s, is given by:

N

n MS b [0013] If the base of the serialization is a power of 2; that is, b=2 ^p , then the number of mass serialized values is:

n ⁿ MS = 2 ^ ^PN

[0014] Thus, the mass serialization may represents PN bits. If b is not a power of two, then:

_ _? N log ₂ b

[0015] Thus, in various examples, the serialization provides Nlog ₂ b bits of data. For mapping to this serialization, then, the fractional portion of Nlog ₂ b may be ignored, and the integer portion may represent the number of bits encoded into the N digits using the b-wide character set.

[0016] In various examples, the number of bits of data may represent the length of a binary representation of the serialization and may be set to a predetermined length (B). Further, in various examples, the number of 1 's in the binary representation may be set within a predefined range. In one example, the length of the binary representation may be set at 40, and the number of 1 's in the binary represenation may be set between 18 and 22, as described below with reference to Table 1.

[0017] In the various examples described below, the number of 1 's is set in a range defined by a lower number (L) of 1 's (e.g., 18) and an upper number (U) of 1 's (e.g., 22). Thus, the total number of allowed mass serialization values may be given by:

[0018] Conversely, the number of non-allowed mass serialization values may be given

[0019] Thus, the percentage of allowable mass serialization values are:

[0020] This ratio may be used to formulate a strategy to avoid any duplication of identifiers, referred to as a collision strategy. For example, a database of binary strings may be used for a static set of mass serialized numbers with between L and U 1 's in the string. The same database may be used for a set of incremental information objects (or IIOs) which may accommodate a stage progression. In this regard, the number of 1 's may change within the range defined by U and L at different stages. In various examples, the number of 1 's may jump from less 1 's to more 1 's. For example, the serialization of a product may flow from manufacturing to packaging to retail. This serialization flow may be achieved through various types of IIOs, such as progressive barcodes, for example.

[0021] For example, referring now to Figure 2, an example identifier is illustrated that may be used as an identifier. The example identifier of Figure 2 is a two-dimensional, machine- readable, bar code having a plurality of regions (e.g., squares) that may be white or black. In other examples, additional colors may also be used. A blank template of the example identifier is illustrated in 2(a). In this regard, the template includes black squares along two adjacent sides and alternating black and white squares along the two other adjacent sides. This configuration may allow for orientation of the identifier by a machine reading the identifier, such as a scanner.

[0022] Referring now to Figures 2(b) - 2(d), an example identifier is illustrated at various stages of a serialization flow. For example, Figure 2(b) illustrates the identifier at a first stage, which in various examples may be a manufacturing stage. The identifier may be modified at a second stage (e.g., packaging stage) by changing additional white squares to black, as indicated in Figure 2(c). The identifier may be similarly modified further at a third stage (e.g., retail stage), as illustrated in Figure 2(d).

[0023] In various examples, the identifiers may have a representation as a string of characters. For example, the identifiers of Figure 2 may be represented as a binary string of 0's and l 's. In other examples, the string of characters may include various other types of characters, such as lower case letters, upper case letters, numerals, and/or various other types of characters.

[0024] Figure 3 illustrates an example identifier represented as a binary string of 0's and 1 's. Figure 3(a) illustrates and example set of identifiers at, for example, a first stage. For sake of simplicity, Figure 3 illustrates a set including only five identifiers, each identifier being eight characters in length. Of course, those skilled in the art will appreciate that a set may include any number of identifiers and may have any selected length.

[0025] In various examples, each identifier in the set may be formed to have a predefined range of number of characters. For example, in the illustrated example of Figure 3, the identifiers may be formed to have between 2 and 6 1 's. Further, in various examples, at each stage of serialization, each identifier in the set may have a predetermined number, or a predetermined range of number, of 1 's. In the illustrated example of Figure 3(a), each identifier in the set has two 1 's. At another stage in the serialization flow, each identifier in the set may have a different number or range of numbers of 1 's, such as three 1 's in the example of Figure 3(b). Similarly, at still another stage in the serialization flow, each identifier may have still a different number or range of numbers of 1 's, such as four 1 's as illustrated in the example of Figure 3(c).

[0026] Organizing the mass serialized numbers according to the number of certain characters provides various advantages. For example, searching of a database of identifiers can be accelerated significantly. In this regard, in various examples, a database of identifiers for a mass serialization may be searched based at least in part on a number of one of the characters in the representation (e.g., a binary string representation) of the identifiers. In one example, the database may be searched for a number or a range of number of 1 's in a binary representation of the identifiers. Such searching based on the number or a range of number of characters may be performed in conjunction with other types of searching. For example, searching may also be performed based on a value of a selected byte in the binary representation, such as the first byte of a multi-byte representation.

[0027] For a large set of identifiers, as may be desirable for a mass serialization, avoidance of collisions (e.g., two or more supposedly unique identifiers being identical) can be of great importance. In this regard, the odds of any two mass serialized strings colliding is:

[0028] The probability of a newly-generated random mass serialization string colliding with an existing set of M unique strings, p _co iiision, is: collision

[0029] The odds of having one or more collisions in a randomly-generated batch of M new strings can now be determined. As above, the number of mass serialized values can be computed from:

[0030] The probability of a collision, p _co iiision, is simply 1 minus the odds of no collision: collision 1.0-Π ^l MS J

[0031] For example, suppose n _M s=16 and three mass serialized strings are desired. The odds of no collision are 15/16 when creating the second string and 14/16 when creating the third string (assuming the first two did not collide). Thus, p _co iiision = (15/16)(14/16) = 210/256, in agreement with the equation above.

[0032] In some examples, inference forward may be desired using an IIO approach described above with reference to Figures 2 and 3. In this regard, inference refers to associating of related objects in a mass serialized set. Conventionally, inference may be achieved through association within a database. In accordance with various examples, inference may be built-in with the mass serialization and serialization flow.

[0033] Suppose integers K, J and B are defined by K < J < B, where B is the number of bits in the string and K and J are the number of 1 's at progression states n and n+1. In various examples, n and n+1 may refer to various stages in the serialization flow, such as manufacturing, packaging and retail, for example. Thus, the identifiers in the serialization may progress from K 1 's in the string to J 1 's in the string from state n to state n+1. For example, as described in the example of Figure 3 above, the number of 1 's progresses from 2 in Figure 3(a) to 3 in Figure 3(b).

[0034] The number of possible states at J given the state at K may therefore be defined as S(K^J):

[0035] Suppose B=8, J=6 and K=4, then S(K- J)=6. Looking backwards from J to K, however, every state with J 1 's may have arisen from the number of states with l's defined as S(K -J) given by:

(A J\

S(K <- J)

K\(J - K)\

[0036] For the same combination of values, B=8, J=6 and K=4, we have S(K -J)=15. Note that, in general, S(K- -J), and the ratio is defined by:

[0037] This ratio depends on the relative sizes of J, K and B. It can be controlled to set the probabilities of guessing the valid values looking forward S(K- J) and looking backward S(K - J) to the desired low probabilities.

[0038] In one example of an IIO-based inference model, 40 bits for serialization may be used. Thus, there are 2 ⁴⁰ = 1,099,511,627,776 different 40-bit binary strings. Table 1 records the number of combinations possible for every value of p, where p is the number of 1 's in the 40- bit binary string. It is noted that well over half of the possible strings are in the range p = {18...22} . In the example of Table l, the range p = {19, 20, 21 } is used to uniquely serialize a set of products, providing more than 4 x 10 ¹¹ combinations available. Thus, if 10 million products are to be labeled in this serialization, the odds of guessing a legitimate serial identifier is still only 1 in 40,000. In addition to this serialization, an incremental information set (having full inference) having four states is added, which uses p=15, 18, 22 and 25. Each of these p- values corresponds to at least 40 billion workflows, meaning if 10 million workflows are eventually supported by this inference set, the odds of guessing a legitimate state at any state of the workflow is less than 1 in 4,000.

Table 1

20 137,846,528,820 Mass Serialization Set 1 12.54%

21 131,282,408,400 Mass Serialization Set 1 11.94%

22 113,380,261,800 Inference Set 1 State 3 10.31%

23 88,732,378,800 8.07%

24 62,852,101,650 5.72%

25 40,225,345,056 Inference Set 1 State 4 3.66%

26 23,206,929,840 2.11%

27 12,033,222,880 1.09%

28 5,586,853,480 0.51%

29 2,311,801,440 0.21%

30 847,660,528 0.08%

31 273,438,880 0.02%

32 76,904,685 0.01%

33 18,643,560 0.00%

34 3,838,380 0.00%

35 658,008 0.00%

36 91,390 0.00%

37 9,880 0.00%

38 780 0.00%

39 40 0.00%

40 1 0.00%

SUM 1,099,511,627,776 One Inference Set, One 100.0%

Mass Serialization Set

[0039] Thus, for exmaple, in moving from p=15 to p=18, for example, there are 25!/22!3! = 2300 possible next states. Similarly, in moving from p=18 to p=22, there are 22!/18!4! = 7315 possible next states. Finally, in moving from p=22 to p=25, there are 18!/15!3! = 816 possible next steps. [0040] The p-bands can themselves be assigned to sub-bands based on the values of individual bytes. As noted above, a database search may be performed based on the number of 1 's (p value) as well as the value of a particular bye in a multi-byte string. In the example of Table 1 above, 40 bits is equivalent to five bytes. Thus, a column-based data look-up indexed on the first byte may be used to sub-divide the search for collisions in the database into 256 sub- bands.

[0041] Referring now to Figure 4, an example system is schematically illustrated. The example system of Figure 4 may be used to generate a mass serialization set. The example system 100 includes a processor 110 that can perform various functions and may be interfaced with various other components.

[0042] The processor 110 may be coupled to an identifier generation module 120 which is configured to generate identifiers for a mass serialization set, for example. In various examples, the identifier generation module 120 may be a separate processor or may be a module embedded within the processor 110.

[0043] The identifier generation module 120 may generate a set of identifiers, either as a complete set, as individual identifiers, or as groups of identifiers, for mass serialization. The generated identifiers may be, for example, bar codes, 2-dimensional bar codes or other types of identifiers. In generating the identifiers, the identifier generation module 120 may select identifiers that have a representation as a string of characters. As noted above, the characters may be, for example, lower case letters, upper case letters, and/or numerals. In one example, the representation is a binary string of 0's and 1 's.

[0044] The length of the string of the representation may be predetermined. For example, in the above-described example of Table 1, the identifiers are represented by a binary string of 40 characters. Further, the representation of each identifier may include a number of a certain character within a predefined range. For example, as noted above with the example of Table 1, in a 40-character string, the number of 1 's may be selected to be between 19 and 21.

[0045] Further, the number (or range of numbers) of the character may be different for each of a plurality of stages of a serialization flow. For example, the number of 1 's at one stage may be different from the number of 1 's at another stage.

[0046] The system 100 may further include a storage device, such as an identifier database 130. The processor 110 may receive the set of identifiers form the identifier generation module 120 and store them in the identifier database 130. The processor 110 may further be coupled to various other devices or interfaces (e.g., a communication interface) and may provide the set of identifiers to other components through such devices or interfaces, for example.

[0047] Referring now to Figure 5, flow chart illustrates an example method 200. In the example method 200, a set of identifiers for a mass serialization is generated (block 210). In this regard, the set of identifiers may be generated by an identifier generation module 120 described above with reference to Figure 4, for example. As noted above, each identifier in the set of identifiers may have a representation of at least two different characters, such as a binary representation of 0's and 1 's. Further, the representation of each identifier in the set may have a predetermined length. For example, as described above, the representation may be a binary string of 40 characters. In various examples, the number of one of the characters in the representation may be within a predefined range. For example, the number of 1 's in the 40- character binary string may be set between 19 and 21 in the example of Table 1 above.

[0048] The identifiers in the generated set of identifiers may be associated with objects and/or stages of serialization that may be associated with the objects (block 220). For example, the various identifiers in the generated set may be associated with objects for retail and/or different stages of the objects flow (e.g., manufacturing, packaging, etc.).

[0049] The generated set of identifiers and the association of the identifiers to objects and/or stages of serialization may be stored in, for example, the identifier database 130 of Figure 4 (block 130).

[0050] Thus, identifiers for a mass serialization may be provided that provide for avoiding collisions and accelerated lookup of the serialization value in a database.

[0051] Various examples described herein are described in the general context of method steps or processes, which may be implemented in one example by a software program product or component, embodied in a machine-readable medium, including executable instructions, such as program code, executed by entities in networked environments. Generally, program modules may include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps or processes.

[0052] Software implementations of various examples can be accomplished with standard programming techniques with rule-based logic and other logic to accomplish various database searching steps or processes, correlation steps or processes, comparison steps or processes and decision steps or processes.

[0053] The foregoing description of various examples has been presented for purposes of illustration and description. The foregoing description is not intended to be exhaustive or limiting to the examples disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of various examples. The examples discussed herein were chosen and described in order to explain the principles and the nature of various examples of the present invention and its practical application to enable one skilled in the art to utilize the present invention in various examples and with various modifications as are suited to the particular use contemplated. The features of the examples described herein may be combined in all possible combinations of methods, apparatus, modules, systems, and computer program products.

[0054] It is also noted herein that while the above describes examples, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications which may be made without departing from the scope as defined in the appended claims.