WO2019159091A1

WO2019159091A1 - Laundry service management

Info

Publication number: WO2019159091A1
Application number: PCT/IB2019/051189
Authority: WO
Inventors: Satishkumar Chamyvelumani
Original assignee: Satishkumar Chamyvelumani
Priority date: 2018-02-14
Filing date: 2019-02-14
Publication date: 2019-08-22

Abstract

The present subject matter discloses a laundry service environment (100) for providing laundry service by laundry service providers to customers, in accordance with an embodiment of the present subject matter. The laundry service environment 100 includes a customer device (104), a laundry container (110), a status tag (112), and laundry service provider device (102), communicatively tied together by a laundry service management system (108).

Description

LAUNDRY SERVICE MANAGEMENT

TECHNICAL FIELD

[0001] The present subject matter relates, in general, to laundry service management and, particularly but not exclusively, to laundry service management using internet of things.

BACKGROUND

[0002] Laundry service is provided by a laundry service provider to assist in washing dirty clothes, and drying, ironing, and folding of clean clothes. Also, with the advancement of technology people tend to monitor status of clothes sent out for laundry service along with tracking quality of service provided by laundry service provider. Since, current internet of things (IoT) platforms support data collection and control interfaces to multiple distribute IoT devices, use of IoT for management of laundry service is an active area of research.

BRIEF DESCRIPTION OF DRAWINGS

[0003] The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the drawings to reference like features and components.

[0004] Fig. 1 illustrate schematics of a laundry service environment, in accordance with an implementation of the present subject matter.

[0005] Fig. 2 illustrates laundry service management at customers end, in accordance with an implementation of the present subject matter.

[0006] Fig. 3 illustrates laundry service management at laundry service provider’s end, in accordance with an implementation of the present subject matter.

[0007] Fig. 4 illustrates laundry service management at delivery personnel’s end, in accordance with an implementation of the present subject matter.

[0008] Fig, 5(a) illustrates laundry service management system, in accordance with an embodiment of the present subject matter. [0009] Fig. 5(b) illustrates the laundry service management system, in accordance with another embodiment of the present subject matter.

[0010] Fig. 6 illustrates an example of a non-transitory computer readable medium for laundry service management.

[0011] Fig. 7 illustrates another example of a non-transitory computer readable medium for laundry service management.

DETAILED DESCRIPTION

[0012] In conventional laundry services provided by a laundry service provider, a customer is required to package dirty clothes and request the laundry service provider to pick the package for laundry. The request by the customer is mostly made by a telephonic call, message, or by physically visiting the laundry service provider’s facility. Once, the package is picked by the laundry service providers, the customer can track status of the laundry service by way of telephonic call, message, or by physically visiting the laundry service provider’s facility. However, conventional laundry services are deprived of a unified management system to ensure monitoring of laundry service, and track quality of service (QoS) provided by the laundry service provider. Thus, there is a need for a laundry service management mechanism for managing communication between laundry service provider and customer, and providing visibility to the customer in laundry service, in addition to providing a convenient way of doing so.

[0013] To this end, system and method for unified management of laundry service is described herein. In an embodiment, internet of things (IoT) may control unified management of laundry service, to overcome the above-described problems associated with manual management of laundry services.

[0014] Various embodiments of the present subject matter disclose a method and system for laundry service management. In accordance with an embodiment, a laundry service environment may have multiple laundry service providers and customers registered for laundry service using laundry service management system as an interface. The laundry service management system may be installed on computing devices of the laundry service providers and customers. Thus, the laundry service management system provides a centralized and unified platform for providing ease of communication between the laundry service providers and customers.

[0015] The registered customers may be provided with a laundry container and status tags. In an embodiment, the laundry container is installed at a conveniently accessible location in the customer’s facility. In said embodiment, the status tags may be switchable, multiple color coded, and washable and can be removably attached to clothes of the customer.

[0016] In accordance with an implementation, a registered customer may removably attach status tag to dirty clothes, switch the status of the status tag to ON, and place the tagged dirty clothes in the laundry container, as an indication for laundry request. In an embodiment, the customer may define laundry service criteria for laundry service provider before placing the tagged dirty clothes in the laundry container in a customer device, communicable with the laundry service management system. The laundry service providers may receive a broadcast from the laundry container, based on the status tag, over the laundry service management system corresponding to the laundry request from the customer. A laundry service provider with requisite capacity and capability of meeting the laundry service criteria may acknowledge the laundry request via laundry service management system, and may visit the customer’s facility to pick up the tagged dirty clothes from the laundry container, after receiving location data from the laundry container though the laundry service management system. In an embodiment, the laundry service provider may access the laundry container using a unique secure access code which is sent to the laundry service provider’s delivery services based on proximity to the container. After the pick-up, the laundry service provider performs various laundry related tasks on the dirty clothes, while updating status tag and laundry service management system. Upon completion of all the tasks on the dirty clothes, clean clothes may be sent to the customer facility, and be placed in the laundry container for pick up by the customer.

[0017] In an embodiment, the customer may receive notifications from the laundry container, based on the status tag, over the laundry service management system at each step from pick up of dirty clothes, to laundry tasks, and final drop off of clean clothes in the laundry container. In another embodiment, the customer may monitor status of laundry service, and track quality of service (QoS) of the laundry service, based on the pre-defined service criterias.

[0018] Thus, the present subject matter discloses a symbiotic relationship between the laundry service management system, the laundry container, and the status tags in laundry service environment for providing centralized and unified laundry service management. The laundry service management system provides service transparency to the customer by enabling a customer to view status of the laundry at any given instance of time by way of communication from status tag through, say communication equipment at the laundry service provider’s end. Further, the desired QoS is ensured to the customer, as the customer provides pre-defined service criterias, and monitors if the laundry service provider is satisfying each service criteria. Also, the status tags allow individual tracking status and location for each cloth, ensuring ease of status monitoring for the customer and the laundry service provider. Further, access of laundry container by unique secure access code ensures safety to customer’s clothes. Hence, the laundry service environment as disclosed in the present subject matter, is efficient, unified, secure, and provides ease of access for the laundry service provider as well as the customer.

[0019] These and other advantages of the present subject matter would be described in greater detail in conjunction with the following figures. While aspects of laundry service management can be implemented in any number of different configurations, the embodiments are described in the context of the following device(s) and method(s). [0020] Fig. 1 illustrate schematics of a laundry service environment 100 for providing laundry service by laundry service providers to customers, in accordance with an embodiment of the present subject matter. The laundry service provider connects to the laundry service environment 100 by laundry service provider devices (LSPD)s 102-1... 102-N. The LSPDs 102-1, ..., 102-N, may be collectively referred to as LSPDs 102. Fig. 1 (b) illustrates the schematics of LSPD 102, according to an embodiment of the present subject matter. In one implementation, the LSPD 102 includes processor(s) 118 coupled to a memory 122. The LSPD 102 further includes interface(s) 120, for example, to facilitate communication with other devices. The interface(s) 120 may include a variety of software and hardware interfaces, for example, interfaces for peripheral device(s). Further, the interface(s) 120 enables the LSPD 102 to communicate with other devices, such as web servers and external repositories. The interface(s) 120 can also facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example LAN, cable, etc., and wireless networks such as WLAN, cellular, or satellite. For the purpose, the interface(s) 120 may include one or more ports for connecting a number of computing devices to each other or to other server computers.

[0021] The processor(s) 118 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor(s) 118 are configured to fetch and execute computer-readable instructions stored in the memory 122.

[0022] The memory 122 may include a computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), etc., and/or non-volatile memory, such as erasable program read only memory (EPROM), flash memory, etc.

[0023] Further, the memory 122 includes engine(s) 124 and data 126. The engine(s) 124 include, for example, a request receiving engine 128, a determination engine 130, a request processing engine 132, and other engine(s) 134. The other engine(s) 134 may include programs or coded instructions that supplement applications or functions performed by the LSPD 102.

[0024] The data 126 includes a request data 136, laundry service criteria 138, and other data 140. In one implementation, the request data 136, laundry service criteria 138 are stored in the memory 122 in the form of look-up tables. Further, the other data 140, amongst other things, may serve as a repository for storing data that is processed, received, or generated as a result of the execution of one or more engines in the engine(s) 124. Although the data is shown internal to the LSPD 102, it may be understood that the data may reside in an external repository (not shown in the figure), which is coupled to the LSPD 102. The LSPD 102 may communicate with the external repository through the interface(s) 120 to obtain information from the data.

[0025] In an implementation, customers connect to the laundry service environment 100 by customer devices (CD)s 104-1... 104-N. The CDs 104-1, ..., 104-N, may be collectively referred to as CDs 104. Examples of the LSPDs 102 and

CDs 104 include, but are not restricted to handheld devices, tablet computers, mobile phones, PDAs, smartphones, and the like. Each of the LSPDs 102 and CDs 104 work on a communication protocol as defined by a communication network 116 to which the LSPDs 102 and CDs 104 is coupled.

[0026] The LSPDs 102 and CDs 104 register for the laundry service using laundry service management system 108 over the communication network 116. Pig. 1 (c) illustrates the schematics of laundry service management system 108, according to an embodiment of the present subject matter. In one implementation, the laundry service management system 108 includes processor(s) 142 coupled to a memory 146. The laundry service management system 108 further includes interface(s) 144, for example, to facilitate communication with the CDs 104. The interface(s) 144 may include a variety of software and hardware interfaces, for example, interfaces for peripheral device(s). Purther, the interface(s) 144 enables the laundry service management system 108 to communicate with other devices, such as web servers and external repositories. The interface(s) 144 can also facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example LAN, cable, etc., and wireless networks such as WLAN, cellular, or satellite. For the purpose, the interface(s) 144 may include one or more ports for connecting a number of computing devices to each other or to other server computers.

[0027] The processor(s) 142 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor(s) 142 are configured to fetch and execute computer-readable instructions stored in the memory 146.

[0028] The memory 146 may include a computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), etc., and/or non-volatile memory, such as erasable program read only memory (EPROM), flash memory, etc.

[0029] Further, the memory 146 includes engine(s) 148 and data 150. The engine(s) 148 include, for example, a receiving engine 152, a request processing engine 154, and other engine(s) 156. The other engine(s) 156 may include programs or coded instructions that supplement applications or functions performed by the laundry service management system 108.

[0030] The data 150 includes a laundry service request 158, location data 160, laundry service criteria 162, customer identification details 164, and other data 166. In one implementation, the laundry service request 158, location data 160, laundry service criteria 162, customer identification details 164 are stored in the memory 146 in the form of look-up tables. Further, the other data 166, amongst other things, may serve as a repository for storing data that is processed, received, or generated as a result of the execution of one or more engines in the engine(s) 148. Although the data is shown internal to the laundry service management system 108, it may be understood that the data 150 may reside in an external repository (not shown in the figure), which is coupled to the laundry service management system 108. The laundry service management system 108 may communicate with the external repository through the interface(s) 144 to obtain information from the data.

[0031] The communication network 116 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, the communication network 116 includes various network entities, such as gateways, routers; however, such details have been omitted for sake of brevity of the present description.

[0032] Fig. 1 also illustrates that the LSPDs 102, the CDs 104, the laundry service management system 108, laundry container 110, and status tag 112 together form laundry service architecture 106. The LSPDs 102, CDs 104, and delivery device 114, communicate with each other and the laundry service architecture 106 via communication network 116.

[0033] In an implementation, the laundry container 110 may have at least two storage compartments. One of the storage compartments may be used for placement of dirty clothes for pickup by a laundry service provider and the other storage compartment may be used for placement of clean clothes after laundry. In another implementation, the laundry container 110 may include communication hardware, i.e., equipment for allowing communication with other elements in the network, and proximity sensors. In an example, the communication hardware may be a wireless communication enabled device, such as a WiFi router. In another example, the communication hardware may be a Radio Frequency (RF) transceiver. Further, the communication hardware may either be provided as a separate unit from the laundry container 110 or it may be integrated into the laundry container 110. Additionally, after placement of clothes in the laundry container 110, the communication hardware of the laundry container 110 may transmit the location data 160 with the laundry service management system 108.

[0034] In an embodiment, the laundry service management system 108 receives a laundry service request 158 from a customer by a CD 104. The request may be received by the receiving engine 152 along with the location data 160. In an implementation, the laundry service management system 108 may prompt the CD 104 to enter unique registration details for authenticating the service request. After placing the service request, the customer may removably attach status tag 112 to each cloth before sending the clothes for laundry. Additionally, the customer may switch ON the status tag 112 after attaching the status tag 112 to the clothes. In an example, the status tag 112 may be switchable between ON and OFF states, multiple color coded, and washable. In an implementation, the laundry service management system 108 may prompt the CD 104 to enter service criterias. The service criterias may be indicative of desired quality of service (QoS) as specified by the customer using CD 104. The service criterias for example may be priority level for each cloth to be serviced, detergent to be used for laundry, preferred location of the laundry service provider, expected turnaround time (TAT), and the like. The laundry service criteria 162 may be received by the receiving module along with laundry service request 158, in an example.

[0035] In an implementation, after attaching the status tag the customer can place the clothes in the laundry container 110. In an example, the laundry container 110 may be placed at a convenient location in customer’s facility. In an implementation, the communication hardware of the laundry container 110 may allow access of the laundry container 110 to the customer by a unique customer access code by generating a one time password (OTP) based on proximity of the customer to the laundry container 110. Alternatively, the communication hardware may accept a unique customer access code from the customer for access of the laundry container 110. Further, the communication hardware of the laundry container 110 may be able to detect and read status tag 112 on the clothes. The status tags 112 may also communicate its status as set by the customer to the communication hardware of the laundry container 110. In an example, the status tags 112 may communicate with the communication hardware using diverse short-range communication technologies such as RFID, near-field communication (NFC) technology, and beacon.

[0036] In an implementation of the present subject matter, the status tags 112 may be active RFID tags. The active RFID tags may include a transceiver, an internal power source, and a microprocessor. The internal power source may maintain the active RFID tag in active state, such that the active RFID tag pre-emptively polls and searches for a compatible RFID reader via the transceiver. Additionally, upon establishing a connection with the compatible RFID reader the active RFID tag initiates communication.

[0037] In another implementation of the present subject matter, the status tags 112 may be passive RFID tags. The passive RFID tags may include a transceiver and a microprocessor. Further, the passive RFID tags lack internal power source. Thus, the passive RFID tags remain in idle state, till an RFID reader communicates with the passive RFID tags. The passive RFID tag is powered by an external power source, such as power source of the RFID reader. In an example, multiple passive RFID tags may be used for defining laundry service criteria.

[0038] In an embodiment, one of the active RFID tag and the passive RFID tag may be used as the status tag 112. In an example, both active RFID tag and the passive RFID tag may be simultaneously, detachably attached to the cloth as status tags 112. In such a scenario, one of the active RFID tag and the passive RFID tag may be used as secondary status tag. [0039] After, the customer places the clothes in the laundry container 110, various laundry service providers may receive the service request related broadcast from the communication hardware of the laundry container 110 over the laundry service management system 108 on their respective LSPDs 102. In an implementation, the laundry container may include a RFID reader to communicate with the status tags 112 based on RFID. In an example, when a passive RFID tag is used as status tag 1 12 the RFID reader of the laundry container may power the status tag 112. In an example, the broadcast may be by the request processing engine 154 and may be received by request receiving module 128. Based on the service criterias and laundry service provider’s capacity, a laundry service provider may acknowledge the broadcast from the laundry service management system 108, and request a delivery personnel to pick up the clothes from the laundry container 110. In an example, the determination engine 130 may ascertain if the laundry service criteria 138 are met.

[0040] In an implementation, the delivery personnel may receive the pick up request broadcast via the laundry service management system 108 installed on delivery device 114. In another implementation, the delivery personnel may receive the broadcast via delivery application installed on delivery device 114. In an example, the delivery application may be a sub-application of the laundry service management system 108. In another example, the delivery application may be a separate application dedicated for delivery. In yet another example, the delivery application may be accessible to both the laundry service provider and the delivery personnel.

[0041] Upon receiving the pick up request, the delivery personnel visits the customer facility, and upon coming in vicinity of the laundry container 110, the delivery personnel may receive a unique delivery access code from the communication hardware of the laundry container 110 onto the delivery device 114. In an implementation, the laundry container 110 may have a proximity sensor configured to detect presence of the delivery device 114, generate the delivery access code, and share the delivery access code with the delivery device 114 through the communication hardware. After receiving the delivery access code, the delivery personnel may access the laundry container 110 to acquire clothes for laundry. The delivery personnel may deliver the acquired clothes to the laundry service provider.

[0042] Upon receiving the clothes, the laundry service provider may sort the clothes based on the service criterias. For example, clothes with high priority level may be separated from clothes with low and medium priority level. In an implementation, the sorting may be performed by the laundry service provider manually. In another implementation, the status tags may store the laundry service criteria 138 for their respective clothes, and they may communicate with machines of the laundry service provider for automated sorting.

[0043] The laundry service provider may perform multiple laundry related tasks on the clothes received after sorting. In an example, the laundry related tasks are washing, drying, ironing, and folding. In another example, the laundry service provider may update status of the clothes in the laundry service management system 108 for access by the customer. In yet another example, the status tags 112 attached to the clothes are washable and attached to the clothes during each of the task. After execution of the tasks on the clothes, the laundry service provider may raise another pick up request to the delivery personnel for pick up and delivery of clothes to the customer. In another example, a notification may be transmitted to the CD 104 upon completion of the laundry operation.

[0044] Upon receiving the pick up request, the delivery personnel visits the laundry service provider, carries the clothes to the customer’s facility. After, coming in vicinity of the laundry container 110, the delivery personnel may receive a unique delivery access code from the laundry container 110 onto the delivery device 114. Upon receiving the delivery access code, the delivery personnel may access the laundry container 110 to drop off the clothes from the laundry service provider.

[0045] The status tag 112 may communicate with laundry container 110 to broadcast the CD 104 that the clothes have been placed in the laundry container 110 for pick up by the customer. The customer may operate the laundry container 110 using the customer access code. In an embodiment, the customer may switch OFF the status tag 112 on each cloth upon picking up the clothes from the laundry container 110.

[0046] Method for management of laundry service is described in Figs. 2-5(b) for laundry service environment 100, according to an implementation of the present subject matter. The order in which the method is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any appropriate order to execute the method or an alternative method. Additionally, individual blocks may be deleted from the method without departing from the spirit and scope of the subject matter described herein.

[0047] The method is synergistically executed and managed by hardware components of the laundry service architecture 106, i.e. laundry container 110, status tags 112, and communication devices communicatively connected using laundry service management system 108, at the customer end (elaborated in fig. 2), the laundry service provider end (elaborated in fig. 3), and the delivery personnel end (elaborated in fig. 3). Accordingly, the method is discussed as an amalgamation of fig. 2, fig. 3, and fig. 4 below. Further, Fig. 5(a) and 5(b) elaborate inter-working of the laundry service management system with the customer device 104 and laundry service provider device 102.

[0048] Fig. 2 discloses systematic steps performed by the customer for raising the service request using the laundry container 110 and the status tags 112 in communication with the laundry service management system 108. Referring to block 202, the customer may log in to the laundry service management system 108. The customer may log in using the unique registration details.

[0049] At block 204, the customer may attach the status tags 112 to the clothes that need to be sent for laundry. The status tags 112 may be removably attached to the clothes. In an implementation, the customer may manually switch ON the status tags 112. In another implementation, the status tags 112 may communicate using diverse short-range communication technologies such as RFID, near-field communication (NFC) technology, and beacon.

[0050] At block 206, the customer may define desired service criterias associated with each cloth from amongst the tagged clothes.

[0051] At block 208, the customer may access the laundry container 110 using the unique customer access code. Additionally, the customer may place the clothes in the laundry container 110. In an implementation, the customer may access the laundry container 110 using a one-time access code, shared by the laundry container 110 to the customer when the customer device 104 comes in vicinity of the laundry container 110.

[0052] Fig. 3 and Fig. 4 disclose flow of communication between the laundry service provider and delivery personnel for picking up of the clothes from the customer facility, performing laundry related tasks on the clothes, and delivering the clothes to the customer facility, at laundry service provider end and delivery personnel end, respectively.

[0053] Referring to block 302, the laundry service provider may receive the laundry request from the laundry container 110 in the customer facility over the laundry service management system 108. In an implementation, the laundry service provider may be able to view the laundry request after logging in to the laundry service management system 108.

[0054] At block 304, the laundry service provider may raise a pick up request for picking up the clothes from the customer. Consequently, at block 402, the delivery personnel may receive the laundry pick up request from the laundry service provider.

[0055] At block 404, the delivery personnel may pick up the clothes from the customer facility. In an implementation, the delivery personnel may pick up the clothes from the laundry container 110. Additionally, as a part of the pick up request, the delivery personnel may drop off the clothes with the laundry service provider. [0056] At block 306, the laundry service provider may perform various laundry related tasks on the clothes. In an implementation, the laundry service provider may periodically update status of the laundry on the laundry service management system 108 for access by the customer.

[0057] At block 308, the laundry service provider may invoke the delivery request for delivering the clothes to the customer. Consequently, at block 406, the delivery personnel may receive the laundry delivery request from the laundry service provider.

[0058] At block 408, the delivery personnel may deliver the clothes from the laundry service provider to the customer. In an implementation, the delivery personnel may place the clothes in the laundry container for access by the customer.

[0059] In fig. 5(a) at block 502, a laundry service request from the customer device 104 is received by the receiving engine 152. In an example, the laundry service request includes customer identification details and the laundry service criteria 162 associated to a cloth.

[0060] At block 504, location data from a laundry container housing the cloth is received by the receiving engine 152. Further, at block 506, a request to perform the laundry operation is broadcast by the request processing engine 154. In an example, the request may be broadcasted to a plurality of laundry service providers. Further, the request may include the laundry service criteria 162.

[0061] At block 508, a confirmation from a laundry service provider from amongst the plurality of laundry service providers to perform the laundry operation is received. In an example, the confirmation is received by the request processing engine 154 and may be received in response to the request to perform the laundry operation. In another example, the confirmation indicates that the laundry service provider meets the laundry service criteria 162 to perform the laundry operation on the cloth.

[0062] At block 510, the location data may be transmitted to the laundry service provider based on the confirmation, by the request processing engine 154. Further, at block 512, details of the laundry service provider may also be transmitted to the customer device 104 based on the confirmation, by the request processing engine 154.

[0063] In Fig. 5(b), at block 514 a request to perform a laundry operation on the cloth is received by the laundry service provider device 102. In an example, the request may be broadcast by the laundry service management system 108. In another example, the request may include the laundry service criteria 162 associated with the cloth.

[0064] At block 516, it may be ascertained if the laundry service criteria 162 is met by a laundry service provider associated with the laundry service provider device 102. In an example, the ascertaining may be executed by the determination engine 130.

[0065] Further, at block 518, a confirmation to perform the laundry operation based on the laundry service criteria 162 is transmitted. In an example, by the request processing engine 154 to the laundry service management system 108.

[0066] Also, at block 520, the location data of the laundry container 110 is received. In an example, the location data may be received by the request processing engine 154 from the laundry service management system.

[0067] Fig. 6 illustrates an example network environment 600 using a non- transitory computer readable medium 602 for management of laundry service, according to an example of the present subject matter. The network environment 600 may be a public networking environment or a private networking environment. In one example, the network environment 600 includes a processing resource 604 communicatively coupled to the non-transitory computer readable medium 602 through a communication link 606.

[0068] For example, the processing resource 604 may be a processor of a computing system, such as the laundry service management system 108. The non- transitory computer readable medium 602 may be, for example, an internal memory device or an external memory device. In one example, the communication link 606 may be a direct communication link, such as one formed through a memory read/write interface. In another example, the communication link 606 may be an indirect communication link, such as one formed through a network interface. In such a case, the processing resource 604 may access the non-transitory computer readable medium 602 through a network 608. The network 608 may be a single network or a combination of multiple networks and may use a variety of communication protocols.

[0069] The processing resource 604 and the non-transitory computer readable medium 602 may also be communicatively coupled to data sources 610 over the network 608. The data sources 610 may include, for example, databases and computing devices. The data sources 610 may be used by the database administrators and other users to communicate with the processing resource 604.

[0070] In one example, the non-transitory computer readable medium 602 includes a set of computer readable and executable instructions, such as the receiving engine 152 and the request processing engine 154. The set of computer readable instructions, referred to as instructions hereinafter, may be accessed by the processing resource 604 through the communication link 606 and subsequently executed to perform acts for network service insertion.

[0071] For discussion purposes, the execution of the instructions by the processing resource 604 has been described with reference to various components introduced earlier with reference to description of Fig. 5(a).

[0072] On execution by the processing resource 604, the receiving engine 152 may receive a laundry service request 158 from the customer device 104. In an example, the laundry service request 158 may include customer identification details 164 and at least one laundry service criteria 162 associated to a cloth. The receiving engine 152 may also receive location data 160 from a laundry container 110 housing the cloth. Further, the request processing engine 154 may broadcast a request to perform the laundry operation to a plurality of laundry service providers. In an example, the request may include the at least one laundry service criteria 162. The request processing engine 154 may also receive a confirmation from a laundry service provider 102, from amongst the plurality of laundry service providers, in response to the request to perform the laundry operation. The confirmation may indicate that the laundry service provider meets the at least one laundry service criteria to perform the laundry operation. Additionally, the request processing engine 154 transmits the location data 160 to the laundry service provider 102 based on the confirmation, and details of the laundry service provider 102 to the customer device 104.

[0073] Fig. 7 illustrates an example network environment 700 using a non- transitory computer readable medium 702 for laundry service management, according to an example of the present subject matter. The network environment 700 may be a public networking environment or a private networking environment. In one example, the network environment 700 includes a processing resource 704 communicatively coupled to the non-transitory computer readable medium 702 through a communication link 706.

[0074] For example, the processing resource 704 may be a processor of a computing system, such as the laundry service provider device. The non-transitory computer readable medium 702 may be, for example, an internal memory device or an external memory device. In one example, the communication link 706 may be a direct communication link, such as one formed through a memory read/write interface. In another example, the communication link 706 may be an indirect communication link, such as one formed through a network interface. In such a case, the processing resource 704 may access the non-transitory computer readable medium 702 through a network 708. The network 708 may be a single network or a combination of multiple networks and may use a variety of communication protocols.

[0075] The processing resource 704 and the non-transitory computer readable medium 702 may also be communicatively coupled to data sources 710 over the network 708. The data sources 710 may include, for example, databases and computing devices. The data sources 710 may be used by the database administrators and other users to communicate with the processing resource 704. [0076] In one example, the non-transitory computer readable medium 702 includes a set of computer readable and executable instructions, such as the request receiving engine, the determination engine, and the request processing engine 132. The set of computer readable instructions, referred to as instructions hereinafter, may be accessed by the processing resource 704 through the communication link 706 and subsequently executed to perform acts for network service insertion.

[0077] For discussion purposes, the execution of the instructions by the processing resource 704 has been described with reference to various components introduced earlier with reference to description of Fig. 5(b).

[0078] On execution by the processing resource 704, the request receiving engine

128 may receive a broadcast including a request 136 to perform a laundry operation on a cloth. In an example, the request 136 may include the laundry service criteria 138 associated with the cloth. Further, the determination engine 130 may ascertain if the laundry service criteria 138 is met by the laundry service provider device 102. Additionally, the request processing engine 132 may transmit a confirmation to perform the laundry operation based on the ascertaining and receiving the location data 160 of a laundry container 110.

[0079] Although implementations for laundry service management are described, it is to be understood that the present subject matter is not necessarily limited to the specific features of the systems or methods described herein. Rather, the specific features and methods are disclosed as implementations for laundry service management.

Claims

V We claim:

1. A laundry service management system (100) communicable with a customer device (104) over a communication network (116) to perform a laundry operation on at least one cloth, the laundry service management system (100) comprising:

a receiving engine (152) to:

receive a laundry service request (158) from the customer device (104), wherein the laundry service request (158) includes customer identification details (164) and at least one laundry service criteria (162) associated to the at least one cloth; and

receive location data (160) from a laundry container (110) housing the at least one cloth;

a request processing engine (154) communicatively coupled to the receiving engine (152) to:

broadcast a request to perform the laundry operation to a plurality of laundry service providers (102), wherein the request includes the at least one laundry service criteria (162);

receive a confirmation from a laundry service provider (102) from amongst the plurality of laundry service providers, in response to the request to perform the laundry operation, wherein the confirmation indicates that the laundry service provider meets the at least one laundry service criteria to perform the laundry operation;

transmit the location data (160) to the laundry service provider (102) based on the confirmation; and

transmit details of the laundry service provider (102) to the customer device (104) based on the confirmation.

2. The laundry service management system (108) as claimed in claim 1 further comprises of a plurality of status tags (112) communicatively associated with the customer device (104) and the laundry container (110).

3. The laundry service management system (108) as claimed in claim 2, wherein the plurality of status tags (112) are switchable between ON and OFF states and the status tags (112) are multiple color coded, and washable.

4. The laundry service management system (108) as claimed in claim 2, wherein at least one status tag (112) from amongst the plurality of status tags (112) is detachably attached to the at least one cloth for the laundry operation.

5. A method for management of a laundry service to perform a laundry operation on at least one cloth by a laundry service management system (108) interacting with a customer device (104) over a communication network (116), the method comprising: receiving, by a receiving engine (152), a laundry service request (158) from the customer device (104), wherein the laundry service request (158) includes customer identification details ( 164) and the at least one laundry service criteria ( 164) associated to the at least one cloth;

receiving, by the receiving engine (152), a location data (160) from a laundry container (110) housing the at least one cloth;

broadcasting, by a request processing engine ( 154) communicatively coupled to the receiving engine (152), a request to perform the laundry operation to a plurality of laundry service providers, wherein the request includes the at least one laundry service criteria (162);

receiving, by the request processing engine (154), a confirmation from a laundry service provider (102) from amongst the plurality of laundry service providers, in response to the request to perform the laundry operation, wherein the confirmation indicates that the laundry service provider (102) meets the at least one laundry service criteria (162) to perform the laundry operation;

transmitting, by the request processing engine (154), the laundry service provider based on the confirmation; and

transmitting, by the request processing engine (154), details of the laundry service provider to the customer device (104) based on the confirmation.

6. The method as claimed in claim 5, further comprises receiving, by the receiving engine (152), a notification from the laundry container (110) when the at least one cloth upon completion of the laundry operation is placed in the laundry container (110).

7. A non-transitory computer readable medium (602), communicatively coupled to a laundry service management system (108), having computer executable instructions for management of a laundry service to perform a laundry operation on at least one cloth comprising:

receiving a laundry service request from the customer device (104), wherein the laundry service request includes customer identification details and at least one laundry service criteria ( 162) associated to the at least one cloth;

receiving a location data from a laundry container (110) housing the at least one cloth;

broadcasting a request to perform the laundry operation to a plurality of laundry service providers, wherein the request includes the at least one laundry service criteria (162);

receiving a confirmation from a laundry service provider (102) from amongst the plurality of laundry service providers in response to the request to perform the laundry operation, wherein the confirmation indicates that the laundry service provider (102) meets the at least one laundry service criteria (162) to perform the laundry operation;

transmitting the laundry service provider (102) based on the confirmation; and transmitting details of the laundry service provider (102) to the customer device (104) based on the confirmation.

8. A laundry service provider device (102) communicable with a laundry service management system (108) over a communication network (116), the laundry service provider device (102) comprising:

a request receiving engine (128) to: receive a broadcast, the broadcast including a request (136) to perform a laundry operation on at least one cloth, wherein the request (136) includes at least one laundry service criteria (138) associated with the at least one cloth; a determination engine (130) to:

ascertain if the at least one laundry service criteria (138) is met by the laundry service provider device (102);

a request processing engine (132) to:

transmit a confirmation to perform the laundry operation based on the ascertaining; and

receive location data (160) of a laundry container (110), wherein the laundry container (110) houses the at least one cloth for the laundry operation.

9. A method for management of a laundry service by a laundry service provider device communicable with a laundry service management system over a communication network, the method comprising:

receiving, by a request receiving engine (128) communicatively coupled with the laundry service provider device (102), a broadcast, the broadcast including a request to perform a laundry operation on at least one cloth, wherein the request includes at least one laundry service criteria (138) associated with the at least one cloth;

ascertaining, by a determination engine (130) communicatively coupled with the request receiving engine (128), if the at least one laundry service criteria (138) is met by the laundry service provider device (102);

transmitting, by a request processing engine (132) communicatively coupled with the determination engine (130), a confirmation to perform the laundry operation based on the ascertaining; and

receiving, by the request processing engine (128), location data (160) of a laundry container (110), wherein the laundry container (110) houses the at least one cloth for the laundry operation.

10. A non-transitory computer readable medium (702), communicatively coupled to a laundry service provider device (102), having computer executable instructions for management of a laundry service to perform a laundry operation on at least one cloth comprising:

receiving a broadcast, the broadcast including a request to perform a laundry operation on at least one cloth, wherein the request includes at least one laundry service criteria (138) associated with the at least one cloth;

ascertaining if the at least one laundry service criteria is met by the laundry service provider device (102);

transmitting a confirmation to perform the laundry operation based on the ascertaining; and

receiving location data of a laundry container (110), wherein the laundry container houses the at least one cloth for the laundry operation.