FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION (See section 10, rule 13)
1. Title of the invention: SYSTEM AND METHOD FOR TIRE REGISTRATION
2. Applicant(s)
NAME NATIONALITY ADDRESS
CEAT LIMITED Indian RPG HOUSE, 463, Dr. Annie Besant Road, Worli, Mumbai - Maharashtra 400030, India
3. Preamble to the description
COMPLETE SPECIFICATION
The following specification particularly describes the invention and the manner in which it
is to be performed.

FIELD OF INVENTION
[0001] The present invention relates generally to tire registration and
more particularly to systems and methods for registration of tires, for purposes such as processing a warranty and/or claim.
BACKGROUND
[0002] Tires are among the most important replacement parts of vehicles.
It is expected that the tires would support the weight of a vehicle they are fitted into and the passengers inside, handle daily driving demands in various weather conditions, and last for years after the purchase. The vehicle’s tires also affect braking, make a ride smooth, and play a major role in a vehicle’s performance. However, the tires are also consumable, and they occasionally wear out prematurely or become damaged beyond repair. Road hazards, tire defects, and mechanical wear are some of the primary reasons for premature tire wear.
[0003] Tire manufacturers may have a warranty policy that may provide
tire repair or replacement under certain conditions to protect their consumers from paying full price on tire repair or replacement of the damaged tire. Tire warranties may protect consumers against premature wear, material defects, and even road hazards by offering a prorated replacement price that may be calculated based on certain conditions set by the tire manufacturers. The consumers, therefore, while making use of the tire warranty policy may avail concession on tire repair or replacement costs. Tire manufacturers may offer a few different types of warranties on their tires, such as tread-life warranties, road hazard warranties, workmanship and materials warranties, uniformity warranties, etc.
BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The following detailed description references the drawings,
wherein:
[0005] Figure 1 illustrates a network environment comprising a warranty
registration system for tires, in accordance with an example implementation
of the present subject matter;
[0006] Figure 2 illustrates the warranty registration system for tires, in
accordance with an example implementation of the present subject matter;
[0007] Figure 3a illustrates a pattern name image of the tire, in
accordance with an example implementation of the present subject matter;
[0008] Figure 3b illustrates a size image of the tire, in accordance with an
example implementation of the present subject matter;
[0009] Figure 3c illustrates serial number image of the tire, in accordance
with an example implementation of the present subject matter; and
[0010] Figure 4 illustrates a method for warranty registration of tires within
a networked environment, in accordance with an example implementation
of the present subject matter.
[0011] Throughout the drawings, identical reference numbers designate
similar, but not necessarily identical, elements. The figures are not
necessarily to scale, and the size of some parts may be exaggerated to
more clearly illustrate the example shown. Moreover, the drawings provide
examples and/or implementations consistent with the description; however,
the description is not limited to the examples and/or implementations
provided in the drawings.
DETAILED DESCRIPTION
[0012] Once a tire is fitted into a vehicle, there is no way to tell exactly how
long that tire is going to last. The lifespan and mileage of a tire depend on a combination of factors, such as its design, the driver’s habits, the climate, the road conditions, and the care that is put into the tires. Generally, the tires are expected to last for years or at least as long as their advertised life, however, they occasionally wear out prematurely due to various reasons, for example,

road hazards, tire defects, and mechanical wear, thereby requiring repair or replacement.
[0013] Tires may come with warranties that may be availed by consumers
for the repair or replacement of the tires. Therefore, if a defective tire is covered under the tire manufacturer’s warranty, the consumer may want to take the benefit of the same to avoid paying the full price for tire replacement or repair depending upon the warranty policy put in place by the tire manufacturer.
[0014] However, the consumers at present are dependent mainly on
channel partners, who sell tires and related services for a tire manufacturer, to perform the process of the warranty and claim registration for the tire. Sometimes the registration process may not happen due to operational inefficiency of the channel partners, or the consumer may be required to wait for a longer period for the registration process to get completed. Further, there is no way to make it mandatory for the channel partners to either register the purchased tire or at least provide the consumers with the means to register the purchased tire for warranty and/or claim even in cases where a channel partner may possess the required infrastructure to consolidate the pertinent tire warranty and claim registration information.
[0015] Hence, it has been observed that the channel partners often fail to
undertake the warranty registration responsibility for every tire sold to each of their consumers because of the time or paperwork burden that such action has traditionally required. As such, the task of completing the warranty registration is either placed on the individual consumer or goes unattended. The individual consumers may often face challenges in completing the warranty registration process like identifying or reading descriptions, such as the tire size, serial number, pattern name, etc., written on the tire which is necessary to register a warranty or a claim a warranty or both. Also, in cases where a warranty is not registered for a tire and a claim is made for an unregistered tire, it may be difficult for the person handling the claim to get the size, pattern, and serial number from the worn or damaged tire.

[0016] Moreover, the existing process requires trained human resources
for processing warranty requests or claims made by consumers. The conventional methods of processing warranty and/or claim requests involve manual intervention which may consume time, effort and maybe prone to error due to manual inspection.
[0017] Thus, there exists an urgent need for a technique that may allow the
consumers to complete the warranty and/or claim registration for their tire
efficiently without requiring any intervention of the channel partners in said
process. At the same time, a technique to minimize manual intervention
involved in processing warranty and/or claim requests is also desired.
[0018] Example implementations of a registration system for tires are
described for registering tires to enable submission of warranty and/or claim information electronically. In an example, electronic registration of the tires may allow an eligible tire to be registered with its manufacturer so that, when the tire becomes unusable for any reason, the tire may be replaced with an equivalent new tire on the basis outlined in its warranty. Each tire manufacturer may have specific warranty coverage and certain conditions that apply.
[0019] In an example implementation, the system for registration of tires
comprises a user information module that receives a user input comprising contact information of a user. As will be understood, the user may be the person who has purchased the tire(s) to be registered or maybe a user of a vehicle in which the tire is mounted. The system further comprises a vehicle information module that receives make and model information of the vehicle that is associated with the tire to be registered for warranty benefits. A vehicle's make is the brand of the vehicle, while the model refers to the name of a car product and sometimes a range of products.
[0020] Further, for the completion of the tire warranty registration
process, specific details related to the tire to be registered, such as the tire pattern name, size, serial number, etc., are also required to be provided to the system. These details are usually embossed on the sidewalls of the tire

at the time of its manufacturing. The system further includes a pattern recognition module that receives a pattern name image of the tire. The pattern name image comprises information corresponding to the pattern name on the tire. Furthermore, a size recognition module is provided that receives a size image of the tire that is to be recognized. The size image comprises information corresponding to the size of the tire.
[0021] Once the pattern name and size of the tire that is to be registered
is identified by the system, the next step is to determine stock-keeping unit (SKU) of the tire. An SKU may be a number, an alphanumeric number, e.g., 145/60R13 83 J, a code, such as a bar code or a QR code, that is usually assigned to a tire for the purpose of its inventory management and ease of record-keeping, for example. For this purpose, the system includes an SKU recognition module that identifies the SKU of the tire based on its pattern name and size, respectively.
[0022] The system also includes a serial number recognition module to
receive a serial number image of the tire that is to be registered. The serial number image comprises a serial number of the tire. The serial number may be understood as a number that, together with the SKU, uniquely identifies each tire. It may comprise different shapes according to the marks but is generally in the form of a series of alphanumeric values, e.g., numbers and/or letters. For example, the serial number may identify a factory, a month, a year of manufacture of the tire, and possibly a code used for the retreading of the tire. In an example embodiment, one or more prompts may be generated by the system to prompt the user to capture the pattern name image, size image, and serial number image, respectively, and provide the same to the system.
[0023] The identification of the SKU and serial number marks the
completion of the tire identification, and the next step after the tire identification is registering the tire with the system for claiming the warranty benefits in case the registered tire wears out before the end of the warranty period. For this purpose, the system includes a warranty registration module

that generates a unique warranty registration number based on the SKU
and the serial number of the tire, respectively. Further, the warranty
registration module provides a notification of the unique warranty
registration number to the user through their contact information.
[0024] Thus, the system for registration of tires enables performing the
warranty and/or claim registration process for the tires digitally. With the use of the present registration system, warranty and/or claim requests may be submitted online by the users, and the status of the same may also be tracked online without having to involve channel partners in the process. Also, based on the image, type of defect on the tire and the distance covered by the vehicle may be identified automatically by the system, thereby reducing the manual intervention. The present system may also be advantageous for the tire manufacturers as it reduces the cost per contact, allows quick access to customer records, enables the collection of image data to create more use cases, helps in the improvement of claim handling accuracy due to its all-digital interface, reduces claim expenses, etc.
[0025] The above-described system for registration of tires is further
described with reference to Figures 1 to 4. It should be noted that the description and figures merely illustrate the principles of the present subject matter along with examples described herein and should not be construed as a limitation to the present subject matter. It is thus noted that various arrangements may be devised that, although not explicitly described or shown herein, describe the principles of the present subject matter. Moreover, all statements herein reciting principles, aspects, and examples of the present subject matter, as well as specific examples thereof, are intended to encompass equivalents thereof.
[0026] Figure 1 illustrates a network environment 100 comprising a
registration system 102 for tires that may facilitate efficient tire registration, i.e., a process of the registration of a tire with a manufacturer of the tire or an agent thereof in order to avail a warranty and/or claim for the tire, according to an example of the present subject matter. The registration system 102

captures information pertaining to a tire to be registered and a user registering the same to enable the warranty registration of the tire electronically with minimal to no manual intervention, thereby facilitating an efficient and user-friendly tire warranty registration process.
[0027] System 102 may be accessed through network 108 by a locally
installed tire recognition client 110 on at least one user device 106 or
through browsers. Examples of the user device 106 may include but are not
limited to a tablet, a smartphone, and similar devices. As shown in Figure 1,
the user device 106 may be configured to receive inputs from users and
communicate said inputs to the system 102, or components thereof.
[0028] For example, network 108 may be a single network or a
combination of multiple networks and may use a variety of different communication protocols. Network 108 may be a wireless or a wired network, or a combination thereof. Examples of such individual networks include, but are not limited to, Global System for Mobile Communication (GSM) network, Universal Mobile Telecommunications System (UMTS) network, Personal Communications Service (PCS) network, Time Division Multiple Access (TDMA) network, Code Division Multiple Access (CDMA) network, Next Generation Network (NON), Public Switched Telephone Network (PSTN). Depending on the technology, network 108 may include various network entities, such as gateways, routers; however, such details have been omitted for sake of brevity of the present description.
[0029] The user device 106 may, in certain embodiments, be interfaced
with an image capture device, such as a camera, operable in conjunction with the user device 106 to capture images or video. In an example, the camera may be inbuilt or integrated into the user device 106, such as a webcam. A webcam may be a complementary metal-oxide-semiconductor (CMOS) camera as an example. Although not shown, in an example, the camera 106 also includes an external camera coupled to the computing device 100, such as an external webcam coupled to the computing device 100 through a universal serial bus (USB).

[0030] The network environment 100 may further include a central server
112. The central server 112 may comprise a central database 104 configured to store the various information that may be received, exchanged, generated, or stored for the purposes of tire warranty and/or claim registration, referred to as tire registration information. System 102 may be configured to transmit and receive tire registration information over network 108 to the central server 112. The central server 112 may thus serve as a repository of electronic, computer-readable information for the tire manufacturer and/or for a tire registration authority, as examples. In this way, in certain embodiments, the tire registration information may be submitted electronically via network 108 to a tire registration entity, e.g., tire manufacturer.
[0031] The network environment 100 may also include a remote access
machine 114 to allow authorized individuals, such as channel partners, or organizations to communicate with the central server 112. The remote access machine 114 may include a central server access client 116, such as an internet browser, that executes on the remote access machine 114 and accesses the central server 112 via a network such as, for example, the network 108.
[0032] Based on the information provided by the users through the user
devices 106 and information available in the central database 104, the tire registration process is completed electronically. Thus, system 102 provides an efficient mechanism for tire registration that minimizes manual intervention and enables prompt tire warranty and/or claim registration for a large number of users who may be remotely located. For an explanation of the implementation and operation of system 102 to perform the tire registration process, a reference is made to Figure 2.
[0033] Figure 2 illustrates the registration system 102 for tires according
to an example implementation of the present subject matter. In an example, the registration system 102 depicted in Figure 2 may be a server, such as a web server communicatively coupled to the central server 112. For

example, the warranty registration system 102 may be connected to central
server 112 via network 108. In another example, the registration system 102
may also be part of a hosted service executed on the central server 112.
[0034] The registration system 102 of the present invention provides a
platform for the tire registration that may be performed easily and efficiently,
without requiring the user to take a lot of extra steps to complete the tire
registration process, such as manually identifying or reading descriptions,
such as the tire size, serial number, pattern name, etc., written on the tire.
[0035] As depicted in Figure 2, in an example implementation, the
registration system 102 of tires may include at least one processor 202 and a memory 204 coupled to the processor 202. In an example, the processor 202 may be implemented as microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. The memory 204 may include any computer-readable medium known in the art including, for example, volatile memory (e.g., RAM), and/or non-volatile memory (e.g., EPROM, flash memory, etc.). The memory 204 may also be an external memory unit, such as a flash drive, a compact disk drive, an external hard disk drive, or the like.
[0036] Also as depicted in Figure 2, in an example implementation,
interface(s) 206 may be coupled to the processor 202. The interface(s) 206
may include a variety of software and hardware interfaces that allow
interaction of the warranty registration system 102 with other
communication and computing devices, such as network entities, external
repositories, and peripheral devices. The interface(s) 206 may also enable
the coupling of components of the registration system 102 with each other.
Further, in an example, the interface(s) 206 may couple the user device 106
to the system 102. Likewise, the interface(s) 206 may couple the central
server 112 and the registration system 102.
[0037] The registration system 102 may also comprise module(s) 208

and data 234 coupled to the processor 202. In one example, the module(s) 208 and data 234 may reside in memory 204.
[0038] In an example, the data 234 may comprise user information data
236, an image data 238, and other data 240. The module(s) 208 may include routines, programs, objects, components, data structures, and the like, which perform particular tasks or implement particular abstract data types. The module(s) 208 may further include modules that supplement applications on the warranty registration system 102 for tires, for example, modules of an operating system. The module(s) 208 further includes modules that implement certain functionalities of the warranty registration system 102, such as processing the information received by the warranty registration system 102 from the user. The data 234 serves, amongst other things, as a repository for storing data that may be fetched, processed, received, or generated by one or more of the module(s) 208. In an example, the user information data 236 may be received from at least one user device 106. The image data 238 may comprise an image or series of images, comprising a video, captured by the user device 106.
[0039] To initiate the registration of a tire, system 102 may require user
input comprising contact information of a user, such as full name, mobile number, etc. of a user initiating the registration process. Accordingly, in an example embodiment, system 102 may include a user information module 210 that may generate a notification for the user device 106 including a prompt for a user to enter contact information. The user information module 210 receives the contact information of the user in response to the prompt. The contact information so received is stored as user information data 236 in the data of the system 102.
[0040] System 102 may further require information of a vehicle into which
the tire to be registered is mounted or is to be mounted. Accordingly, a vehicle information module 212 of the system 102 may interact with the user device 106 to receive model information from the user pertaining to the vehicle associated with the tire to be registered, wherein the model

information may comprise vehicle's make and model, for example.
[0041] Upon having received the contact information and the model
information of the vehicle, system 102 may further require specific details, such as pattern name, size, serial number, pertaining to the tire in order to identify the tire to be registered. Accordingly, a pattern recognition module 214 of system 102 may interact with the user device 106 to receive a pattern name image of the tire, such as the form shown in Figure. 3a. For this purpose, in one example, the pattern recognition module 214 may activate the camera of the user device 106 and prompt the user to capture a “pattern name image”, wherein the pattern name image comprises information corresponding to a pattern name on the tire. For example, "FUELSMARRT" is the pattern name of the tire which is illustrated in Figure 3a. As will be understood, the pattern name corresponds to a name assigned to a set of tires having a particular pattern, design or configuration, by a manufacturer of the tires and the same may be inscribed on the tires, for instance, on sidewalls of the respective tires.
[0042] The pattern recognition module 214 receives the pattern name
image in response to the prompt and analyzes the pattern name image to identify the pattern name written on the sidewall of the tire.
[0043] After having analyzed the pattern name of the tire from the pattern
name image, the user may be prompted to confirm whether the pattern name identified by the pattern recognition module 214 and the one present on the tire is the same. Once the user confirms that the pattern name identified by the pattern recognition module 214 is correct, the same is communicated to the central server 112.
[0044] Similarly, a size recognition module 216 of the system 102 may
interact with the user device 106 to receive a size image of the tire that is to be registered. The size image, such as the form shown in Figure 3b, may comprise information corresponding to the size of the tire. As is generally the case, the size of the tire may be inscribed on the tires, for instance, on sidewalls of the respective tires at the time of manufacture, and an image

capturing the size inscribed on the tires may be captured by the user and
provided to the size recognition module 216. For example, "165/70R14817"
is indicative of the size of the tire which is illustrated in Figure 3b.
[0045] The size recognition module 216 may in turn analyze the size
image to identify the size of the tire written on the sidewall of the tire. After having analyzed the size of the tire from the size image, in one example implementation, the user may be prompted to confirm whether the size of the tire identified by the size recognition module 216 and the one mentioned on the tire is the same. Once the user confirms that the size identified by the system 102 is correct, the same is communicated to the central server 112.
[0046] After having identified the pattern name and size of the tire by
system 102, the SKU of the tire needs to be determined. For this purpose, the system 102 includes an SKU recognition module 218 that identifies the SKU of the tire based on its pattern name and size, respectively. In an example, the pattern name of the tire may not be unique for every tire, but it may be unique for every SKU.
[0047] In an example embodiment, the SKU may be identified by the SKU
recognition module 218 that uses a fuzzy match based on the pattern name and size of the tire which is concatenated and then fed to a fuzzy match logic. In an implementation, the central server 112 of the system 102 may already have a list of SKUs that may fit on a specific vehicle make and model. Further, a comparison of the concatenation of pattern name and size of the tire is made with said SKUs list, where the SKU recognition module 218 tries to fuzzy match with the vehicle make and model that the user has specified, thereby identifying the correct SKU for said tire. Once the SKU of the tire is identified by the SKU recognition module 218, the same is stored in central server 112.
[0048] The system 102 also includes a serial number recognition module
220 that may interact with the user device 106 to receive a serial number image of the tire that is to be registered. The serial number image, such as

the form shown in Figure 3c, may comprise information pertaining to manufacturing week, year, place, and other data, and may be inscribed on the sidewall of the tire at the time of manufacturing. The serial number may be understood as a number that, together with the SKU, uniquely identifies each tire. For example, "PTWWYY" is indicative of the serial number of the tire which is illustrated in Figure 3c.
[0049] After receiving the serial number image from the user, the serial
number recognition module 220 may analyze said image to identify the serial number of the tire written on the sidewall of the tire. After having analyzed the serial number of the tire from the serial number image, the user may be prompted to confirm whether the serial number of the tire identified by the serial number recognition module 220 and the one present on the tire is same. Once the user confirms that the serial number identified by the serial number recognition module 220 is correct, the same is stored in the central server 112.
[0050] In the above operations, the user is prompted in a visual manner
to confirm the pattern name, size, the serial number of the tire recognized by the respective modules, for example, by popping a box, a prompt confirm key, and the like. The user may also be prompted in an audio manner to confirm the pattern name, size, and the serial number of the tire, for example, by playing voice information for prompting.
[0051] After identifying the SKU and the serial number of the tire, the
system 102 proceeds to register the tire for warranty. For this purpose, a
warranty registration module 222 of the system 102 may generate a unique
warranty registration number based on the SKU and the serial number of
the tire. The warranty registration module 222 may provide a notification of
the unique warranty registration number to the user through their contact
information. Once a warranty for a tire is registered, information pertaining
to said warranty registration is stored in the central database 104.
[0052] In some of the cases, it is possible that the user may have not
been able to register their new tire for warranty with the system 102 at the

time of purchase. Therefore, to allow claim registration for a tire for which warranty was not registered earlier, the system 102, in an embodiment, may receive the pattern name, size, serial number of said tire in accordance with the techniques discussed above. Further, the system 102 includes a tread depth recognition module 224 that may interact with the user device 106 to receive a tread pattern image of the tire for which the claim is being sought. The tread pattern image may comprise information corresponding to the tread depth of the tire. The tread depth recognition module 224 may compute the tread depth based on the tread pattern image. The tread depth of a tire, for example, maybe understood as a vertical measurement from an outermost surface atop the tire to the bottom of the tire's deepest grooves.
[0053] The system 102 further includes a tire defect-recognition module
226 that may be configured to interact with the user device 106 to receive one or more defect images of the tire. The one or more defect images, in an example, may be indicative of information corresponding to a defect on the tire and a location of the defect on said tire. The tire defect-recognition module 226 may then identify the defect on the tire based on the analysis of the one or more defect images by using AI-based techniques. In an example, a data labeling technique that may make use of rectangular boxes to define the location of the target defect in the defect image may be used. In said example technique, each defect image may be labeled for different types of defects that may include, but are not limited to, run-flat, through cut on sidewalls, through cut on tread portion, belt separation, sidewall bulge, burst concussion, fitment/locking damage, flow crack on the sidewall, tread shoulder separation, etc.
[0054] In an example implementation of the registration system 102 for
tires, when a user approaches the channel partner to replace a tire and wants to avail warranty benefits on said tire, the channel partner may input the user's contact information into the central server access client 116, that is locally installed in the remote access machine 114, to access, for

example, by interrogating the central database 104 of the central server 112, the unique warranty registration number issued against said contact information of the user. This interrogation is to confirm if any warranties are previously registered for the tire that the user wants to get replaced. If registered, the remote access machine 114 displays details of the user, the tire registered for warranty, and the model information of the vehicle associated with the tire. The channel partner may then assess whether the vehicle and tire information displayed on the remote access machine 114 and the one made available to the channel partner for availing warranty benefits are the same. If it is found that the information is the same, the channel partner may send the warranty request for processing by the registration system 102.
[0055] For the final calculation of the tire replacement cost, in an
example, the system 102 may additionally require an odometer reading of
the vehicle that is associated with the tire for which claim is being sought.
For this purpose, module(s) 208 may comprise an odometer reading
recognition module 228. The odometer reading recognition module 228 may
interact with the user device 106 to receive an odometer reading image of
the vehicle, wherein the odometer reading image comprises information
corresponding to a distance, i.e., a number of miles/kilometers the vehicle
has traveled. Based on the odometer reading image, odometer reading
recognition module 228 may identify the distance the vehicle has traveled.
The distance traveled is then put into a formula that may give a replacement
cost of the tire in consideration of the type of defect identified on the tire.
[0056] The components of the module(s) 208 may be trained to identify
ill-exposed and non-tire images captured by the user device 106. To identify the ill-exposed and non-tire image captured by the user device 106, the module(s) 208 of the system 102 may make use of an image classification algorithm that may be pre-trained on the image data having the presence of blur and defocusing within a frame and the tire and non-tire image respectively and is able to classify correctly whether the image has a tire in

it or not.
[0057] In an example embodiment, the recognition modules of the system
102 as discussed above may be trained in an end-to-end fashion using various open-source machine learning models. For example, the serial number recognition module 220 may be trained using a machine learning model to enable it to detect and recognize the serial number of the tire from the serial number image. Likewise, in another example, the tire defect-recognition module 226 may be trained using an open-source machine learning model that enables the tire defect-recognition module 226 to identify and pinpoint the area of defects on the tire by analyzing one or more defect images. Also, some or all parameters of the recognition modules may be learned through the training process.
[0058] For example, an open-source machine learning model may be
trained using training data that includes input data, such as pattern name image, size image, ill-expose image, serial number image, etc., and the correct or preferred output of the model for the corresponding input data. The machine learning model may repeatedly process the input data, and the parameters of the machine learning model may be modified in what amounts to a trial-and-error process until the model produces or “converges” on the correct or preferred output, such as extracting correct text from the tire which is usually challenging because of the curved black text with a black background. This way, the system 102, by using image analytics may categorize defects quickly, thereby helping customer service engineers to settle claims quickly.
[0059] An example scenario is explained below to elaborate on the
working of the system 102. The warranty registration may be considered as a first process that determines if a claim can be filed with additional 6 months warranty period. However, the warranty period may not be limited to just 6 months and may vary depending upon the category of the tire for which the warranty is being registered. In an example, to enable the registration of a tire for warranty, a user is prompted by the system 102 to provide his contact

information, such as name, mobile number, pin code, etc. Further, the system 102 allows the user to select model information of a vehicle that is associated with the tire to be registered which may include vehicle make and model. Thereafter, the user may choose to use the system 102 to register the warranty. The user may do so by following the steps requiring them to upload an image that has the pattern name, e.g.: FUELSMARRT. The next step may be to upload an image that has the SKU size, e.g.: 185/60R17 58 J. After the SKU size image, the user is prompted to upload an image that has the serial number of the tire to be registered, e.g.: PN 1220.
[0060] With the above details, the warranty may be registered for one tire.
If the user is willing to register more than one tire having the same information, i.e., serial number, pattern name, etc., they may do so by selecting an option promoted by the system 102, at the time of selecting the model information of the vehicle. In an example, a prompt to avail the option may read “Please register the warranty for all ‘x’ tires”, wherein x is the number of tires the user has procured.
[0061] After having completed the warranty registration for the one or
more tire, a user willing to replace the tire may file a claim by entering their mobile number. Since the warranty registration for said tire has already been done, all the information about the tire, such as SKU name, serial number, etc., is available in the central database 104. While performing the claim registration for such tire, the user may be prompted by the system 102 to upload an image of the odometer reading, tire defect, and tread pattern. Based on the analysis of these images by the system 102, a claim may be registered, and an offer may be given to the user if the claim is accepted. Otherwise, if the claim request is not as per the policy, the claim may be rejected.
[0062] In another example, the system 102 may also allow a direct claim
registration for a tire for which the warranty was not registered earlier. In that case, the system 102 to capture the information which is necessary to

process the claim, such as SKU name, serial number, etc., may prompt the user to upload the tire image which has the pattern name, SKU size, serial number, respectively. Thereafter, the users may be prompted by the system 102 to upload the image of the odometer reading, tire defect, and tread pattern, respectively. Accordingly, as also discussed above, based on the analysis of these images, the claim may be registered. Thereafter, the claim is processed for acceptance or rejection of the same.
[0063] Figure 4 illustrates a method 400 for registration of tires within a
networked environment, in accordance with an example implementation of the present subject matter.
[0064] The order in which the method 400 is described is not intended to
be construed as a limitation, and any number of the described method
blocks may be combined in any order to implement method 400, or an
alternative method. Furthermore, the method 400 may be implemented by
processor(s) or computing device(s) through any suitable hardware, non-
transitory machine-readable instructions, or combination thereof.
[0065] It may be understood that blocks of the method 400 may be
performed, for example, by the above-described registration system 102 for tires, as illustrated in FIGS. 1 and 2. In an example, the registration system 102 for tires may be installed in a network environment, such as the network environment 100 described in reference to FIG.1.
[0066] The blocks of the method 400 may be executed based on
instructions stored in a non-transitory computer-readable medium, as will be readily understood. The non-transitory computer-readable medium may include, for example, digital memories, magnetic storage media, such as magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media.
[0067] Referring to Figure 4, at block 402, the user information module
210 receives a user input comprising contact information of a user. As discussed earlier, the contact information of the user may comprise but is not limited to name and mobile number.

[0068] At block 404, the vehicle information module 212 interacts with the
user device 106 to receive the model information of the vehicle that is
associated with the tire to be registered. As discussed previously, the model
information may cover but is not limited to the vehicle's make and model.
[0069] At block 406, the pattern recognition module 214 interreacts with
the user device 106 to receive at least one pattern name image of the tire. At least one pattern name image may comprise information corresponding to a pattern name of the tire.
[0070] At block 408, the size recognition module 216 interacts with the
user device 106 to receive at least one size image of the tire. At least one
size image may comprise information corresponding to the size of the tire.
[0071] At block 410, the SKU recognition module 218, identifies the SKU
number of the tire based on its pattern and size, respectively.
[0072] At block 412, the serial number recognition module 220 by
interacting with the user device 106 receives at least one serial number image of the tire. At least one serial number image may comprise the serial number of the tire.
[0073] At block 414, the warranty registration module 222 generates a
unique warranty registration number based on the SKU and the serial number of the tire, respectively. Additionally, or alternatively, a confirmation message may be provided on the user device 106 notifying the user that the registration of the tire has been completed.
[0074] At block 416, the warranty registration module 222 may provide a
notification of the unique warranty registration number to the contact information. In an example, notification of the unique warranty registration number may also appear on a screen of the user device 106.
[0075] The methods and devices of the present subject matter enable a
user to register the tire for warranty and file claims online directly with the manufacturer rather than through a channel partner. The underlying objective of the warranty registration system for tires is to help users in completing the warranty registration for their tires electronically at their

respective locations, thereby facilitating an efficient and user-friendly tire
warranty registration process, reducing complications and related costs.
[0076] Although implementations have been described in a language
specific to structural features and/or methods, it is to be understood that the appended claims are not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as examples for registration of tires for purposes such as processing a warranty and/or claim.

I/We claim:
1. A registration system (102) for tires, the system (102) comprising:
at least one processor (202);
a memory (204) in communication with the at least one processor (202);
a user information module (210) coupled to the at least one processor (202), to receive a user input comprising contact information of a user;
a vehicle information module (212) coupled to the at least one processor (202), to receive model information of a vehicle associated with the tire to be registered provided by the user;
a pattern recognition module (214) coupled to the at least one processor (202), to
receive at least one pattern name image of the tire, wherein the
at least one pattern name image comprises information corresponding
to a pattern name on the tire, and
identify the pattern name based on the at least one pattern name
image;
a size recognition module (216) coupled to the at least one processor (202), to
receive at least one size image of the tire, wherein the at least one
size image comprises information corresponding to size of the tire; and identify the size based on the at least one size image;
a stock keeping unit (SKU) recognition module (218) coupled to the at least one processor (202), to identify SKU number of the tire based on the pattern name and size, respectively; and
a serial number recognition module (220) coupled to the at least one processor (202), to
receive at least one serial number image of the tire, wherein the
at least one serial number image comprises a serial number of the tire;
and

identify the serial number based on the at least one serial number image;
a warranty registration module (222) coupled to the at least one processor (202), to:
generate a unique warranty registration number based on the SKU and serial number of the tire; and
provide a notification of the unique warranty registration number to the contact information.
2. The system (102) as claimed in claim 1, further comprising:
a tread depth recognition module (224) coupled to the at least one processor (202), to
receive at least one tread pattern image of the tire, the at least one tread pattern image comprising information corresponding to tread depth of the tire; and
compute the tread depth based on the at least one tread pattern image;
a tire defect recognition module (226) coupled to the at least one processor (202), to
receive at least one defect image of the tire, wherein the at least one defect image is indicative of information corresponding to a defect on the tire and a location of the defect on the tire; and
assess the defect based on the at least one defect image.
3. The system (102) as claimed in claim 2, wherein the warranty registration module (222) is further configured to provide a replacement cost for the tire to the user based on the tread depth and defect on the tire.
4. The system (102) as claimed in claim 3, wherein the warranty registration module (222) is to determine the replacement cost based on a user input comprising assessment of the defect on the tire.

5. The system (102) as claimed in any one of claims 1-4, wherein the
system (102) is to communicate with at least one user device (106), wherein
the system (102) is to prompt the at least one user device (106) to capture
the at least one of: pattern name image, size image, serial number image,
tread pattern image, and defect image.
6. A method (400) of registration of tires, the method comprising:
receiving (402), by a user information module (210), a user input
comprising contact information of a user;
receiving (404), by a vehicle information module (212), a model information of a vehicle associated with a tire to be registered provided by the user in response to a prompt;
receiving (406), by a pattern recognition module (214), at least one pattern name image of the tire, wherein the at least one pattern name image comprises information corresponding to a pattern name on the tire;
receiving (408), by a size recognition module (216), at least one size image of the tire, wherein the at least one size image comprises information corresponding to size of the tire;
identifying (410), by a stock keeping unit (SKU) recognition module (218), an SKU number of the tire based on its pattern and size, respectively;
receiving (412), by a serial number recognition module (220), at least one serial number image of the tire, wherein the at least one serial number image comprises a serial number of the tire;
generating (414), by a warranty registration module (222), a unique warranty registration number based on the SKU and serial number of the tire, respectively; and
providing (416), by the warranty registration module (222), a notification of the unique warranty registration number to the contact information.

7. The method (400) as claimed in claim 6, further comprising:
receiving at least one tread pattern image of the tire, wherein the at
least one tread pattern image comprises information corresponding to tread depth of the tire; and
receiving at least one defect image of the tire, wherein the at least one defect image is indicative of information corresponding to a defect on the tire and a location of the defect on the tire.
8. The method (400) as claimed in claim 7, further comprising providing a replacement cost for the tire to the user based on the tread depth and defect on the tire.
9. The method (400) as claimed in claim 7, further comprising determining the replacement cost of the tire based on a user input comprising assessment of the defect on the tire.
10. The method (400) as claimed in any one of claims 6-9, further comprising communicating with at least one user device (106) to prompt the at least one user device (106) to capture the at least one of: pattern name image, size image, serial number image, tread pattern image, and defect image.