WO2022043873A1

WO2022043873A1 - Systems and methods for providing and scheduling the use of dedicated spaces

Info

Publication number: WO2022043873A1
Application number: PCT/IB2021/057759
Authority: WO
Inventors: Rance HESKETH
Original assignee: Hesketh Rance
Priority date: 2020-08-28
Filing date: 2021-08-24
Publication date: 2022-03-03

Abstract

A method of scheduling use of a dedicated space includes receiving user information from a user at a processing device, the user information including a request for temporary use of a dedicated space, searching by the processing device among a record indicative of a plurality of dedicated spaces, presenting one or more dedicated spaces from the record to a user, and receiving a selection of a dedicated space from the user. The method also includes, upon arrival at the dedicated space, verifying the user, and based on the verifying, providing access to the reserved dedicated space to the user.

Description

SYSTEMS AND METHODS FOR PRO AIDING AND SCHEDULING THE USE OF DEDICATED SPACES

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent Application No. 63/071,746, filed on August 28, 2020, in the United States Patent Office, and all the benefits accruing therefrom under 35 U.S. C. § 119, the content of which is incorporated herein by reference in its entirety.

BACKGROUND

[0001] Exemplary embodiments of the present invention relate to temporarily utilized spaces, and more particularly, to scheduling and matching users with temporary workspaces and/or other dedicated spaces.

[0002] The use of workspaces for co-working is becoming more and more popular. The need for temporary workspaces is growing, e.g., because of the rapid rise of freelancing work, where workers can work remotely and not in an office. Due to the increasing demand, there is a need to provide facilities for temporary work or other uses.

SUMMARY

[0003] An embodiment of a method of scheduling use of a dedicated space includes receiving user information from a user at a processing device, the user information including a request for temporary use of a dedicated space, searching by the processing device among a record indicative of a plurality of dedicated spaces, presenting one or more dedicated spaces from the record to a user, and receiving a selection of a dedicated space from the user. The method also includes, upon arrival at the dedicated space, verifying the user, and based on the verifying, providing access to the reserved dedicated space to the user.

[0004] In addition to one or more features described herein, each dedicated space is installed in a captive location configured for use on a temporary basis. [0005] In addition to one or more features described herein, the method further includes reserving the selected dedicated space for the user at a requested date and time.

[0006] In addition to one or more features described herein, the verifying is based on at least one of: receiving a check in message from the user, and detecting a presence of the user.

[0007] In addition to one or more features described herein, the captive location includes a rental property.

[0008] In addition to one or more features described herein, the captive location is a location in which persons are expected to remain for a predictable period of time.

[0009] In addition to one or more features described herein, the dedicated space is a modular space installed at the captive location and removable from the captive location.

[0010] In addition to one or more features described herein, the method further includes assigning a unique user identifier to the user.

[0011] In addition to one or more features described herein, reserving the dedicated space includes assigning a unique reservation identifier, the unique reservation identifier configured to uniquely identify the user, the reserved dedicated space, and the captive location in which the reserved dedicated space is installed.

[0012] In addition to one or more features described herein, verifying the user includes receiving an input from the user at the captive location, and matching the input to the unique identifier.

[0013] In addition to one or more features described herein, reserving the dedicated space includes providing an access code to the user, the access code specific to the reserved dedicated space and the requested data and time.

[0014] In addition to one or more features described herein, the verifying includes receiving an input from the user at an input device located at the captive location, and matching the input to the access code. [0015] An embodiment of a system for scheduling use of a dedicated space includes a processing device configured to communicate with a plurality of user devices. The processing device is configured to receive user information from a user device at the processing device, the user information including a request for temporary use of a dedicated space, search among a record indicative of a plurality of dedicated spaces, present one or more dedicated spaces from the record to a user, and receive a selection of a dedicated space from the user. The processing device to also configured to, upon arrival at the dedicated space, verify the user, and based on the verifying, provide access to the reserved dedicated space to the user.

[0016] In addition to one or more features described herein, each dedicated space is installed in a captive location configured for use on a temporary basis.

[0017] In addition to one or more features described herein, the processing device is further configured to reserve the selected dedicated space for the user at a requested date and time.

[0018] In addition to one or more features described herein, the verifying is based on at least one of: receiving a check in message from the user, and detecting a presence of the user.

[0019] In addition to one or more features described herein, the dedicated space is a modular space installed at the captive location and removable from the captive location.

[0020] In addition to one or more features described herein, the processing device is configured to assign a unique user identifier to the user, and reserving the dedicated space includes assigning a unique reservation identifier, the unique reservation identifier configured to uniquely identify the user, the reserved dedicated space, and the captive location in which the reserved dedicated space is installed.

[0021] In addition to one or more features described herein, verifying the user includes receiving an input from the user at the captive location, and matching the input to the unique identifier. [0022] In addition to one or more features described herein, the input device is included in a hardware controller attached to the reserved dedicated space or located within the captive location, the hardware device in wireless communication with the processing device.

[0023] Additional features and advantages are realized through the techniques of the present invention. Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention. For a better understanding of the invention with advantages and features, refer to the description and to the drawings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0024] The subject matter that is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the end of the specification. The subject matter is described in more detail with reference to exemplary embodiments of apparatuses and methods, given by way of example, and with reference to the accompanying drawings, in which:

[0025] Figure 1 is a block diagram illustrating an embodiment of a system for scheduling the use of, and/or providing access to, dedicated spaces;

[0026] Figure 2 depicts an example of a dedicated space;

[0027] Figure 3 is a flow diagram illustrating an embodiment of a method of scheduling the use of, and/or providing access to, dedicated spaces;

[0028] Figure 4 is a flow diagram depicting aspects of the method of Figure 3, including a process for providing access to a dedicated space;

[0029] Figure 5 is a flow diagram depicting aspects of the method of Figure 3, including a process for reserving a dedicated space for a user;

[0030] Figure 6 is a flow diagram depicting aspects of the method of Figure 3, including a process for reserving a dedicated space for a user; [0031] Figure 7 is a flow diagram depicting an example of the method of Figure 3;

[0032] Figure 8 depicts an example of a data structure maintained by the system of Figure 1, the data structure storing user information;

[0033] Figure 9 depicts an example of a data structure maintained by the system of Figure 1, the data structure storing information regarding locations having dedicated spaces;

[0034] Figure 10 depicts an example of a data structure maintained by the system of Figure 1, the data structure storing billing and feature/amenity information;

[0035] Figure 11 depicts an example of a data structure maintained by the system of Figure 1, the data structure storing dedicated space usage information;

[0036] Figure 12 depicts an example of a page configured as a management/operational dashboard, displaying user and inventory information maintained by the system of Figure 1; and

[0037] Figure 13 is a block diagram illustrating an example of a computer system within which embodiments described herein can be implemented.

DETAILED DESCRIPTION

[0038] Systems, methods and computer program processes are described for providing dedicated spaces to users on a temporary basis. The dedicated spaces may be workspaces such as co-working spaces, or any other temporarily utilized spaces. It is noted that the term “workspace” is not intended to limit the use of a dedicated space for any specific purpose; thus “workspace” is as used herein is a dedicated space temporarily assigned to a user for any desired purpose. A “dedicated space” as described herein is any suitable space that can be installed in any suitable location (e.g., a hotel, airport, a retail space, a commercial space, etc.) intended for temporary use. In an embodiment, the dedicated space is installed in a “captive location,” which is defined as a location or space in which a person and potential user is expected to remain for some predictable period of time. Examples of captive locations include rental properties, which may be any property intended to be rented or used on a temporary bases. Rental properties include, for example, hotels, motels, bed and breakfasts, vacation rental properties, train stations, airports, waiting rooms and others. Captive locations, in some instances, may restrict a person’s ability to leave (e.g., an airport), and/or have resources (e.g., retail stores, food services and other amenities in an airport) that are ultimately controlled by a single entity or group of entities.

[0039] An embodiment of a system for providing dedicated spaces includes a processing device that stores aspects of an application, software programs, modules or any other processing unit or units. In an embodiment, the system stores aspects of an application, such as a mobile application or mobile “app,” that is configured to perform functions related to the management of dedicated spaces and scheduling assignments of dedicated spaces to users.

[0040] The application may be a software application built on a web-based platform or a native platform (e.g., a native app built on a specific platform). For example, aspects of the system can be realized via a mobile application, a responsive website and/or a progressive web app (PWA). The application may include various components to facilitate the methods described herein. For example, a web-based application can include protected routing (e.g., adding an authentication header to a user request). The application may support direct payment or payment via a third party service, at the time of registration, at the time of reservation or at any other suitable time. The application may be configured to allow payment at the site of a dedicated space.

[0041] Other features may include push notifications that can be sent to a user. Push notifications can be sent when a booking or reservation is made, when payment is complete, to remind a user of an upcoming reservation, to notify the user when a reserved time in a dedicated space is ending, etc.

[0042] In an embodiment, the application includes a user interface configured to be presented to a user, and a backend system for performing various functions, such as receiving user input, authenticating users, checking availability and scheduling reservations of spaces (e.g., via a booking engine), managing access to spaces, billing and payment handling, security, etc. For example, the backend system can receive user information and a request for a dedicated space at a requested date and time, present available spaces to a user, schedule the use of a dedicated space, issue an identifier and/or access code, perform verification, and grant access to the scheduled dedicated space to the user.

[0043] In an embodiment, the dedicated spaces include modular spaces that are installed in (and can be removed from) various captive locations. The modular spaces, also referred to as “pods,” each include an enclosure that defines one room therein. The enclosure may be transparent or opaque (or a combination, such as an enclosure having opaque walls with windows), and may have features such as soundproofing, shades, electrochromic glass, "smart glass" and/or "switchable glass". Each modular space may also include or be proximate to an access device (a Bluetooth and/or Near Field Communication wall reader) that permits access to a user at a scheduled date and time, and for a scheduled or selected duration. The access device may be installed on an exterior of the modular space, or be separately located within the captive location (e.g., as a kiosk) or within the mobile app.

[0044] In an embodiment, each modular space or pod is reserved as a single unit having a single room (or sub-divided into multiple rooms), which is reserved to a single user, group of users or other entity. The reserving user or group may invite one or more persons in addition to the user, or the system can be configured to send invites or notifications to one or more persons designated by the user.

[0045] In an embodiment, the modular space includes multiple individual rooms or seats, where each room or seat can be reserved individually by different registered users. If a modular space includes multiple reservable rooms or seats, each room or seat may be provided with a respective access device, or a single access device may be used to grant access to each room.

[0046] Embodiments described herein present a number of advantages and technical effects. The systems and methods described herein provide a convenient and flexible option to users in need of temporary workspaces or co- working spaces. For example, dedicated spaces can be reserved for variable amounts of time on a pay-per-use-basis, and can eliminate the need for contracts and annual fees.

[0047] Many users, such as freelancers, do not have the resources to rent spaces in coworking facilities or only need workspaces on a short-term or sporadic basis. In addition, it can be inconvenient for a user to travel to co-working facilities. The embodiments described herein provide a solution to this problem, by providing workspaces that can operate self-sufficiently and be located at various locations without requiring such locations to install any additional infrastructure. In addition, the workspaces and associated application(s) can be easily installed and moved, and the associated application(s) are easily scalable, allowing for installation in many locations. In this way, workspaces can be distributed to many locations and provide users with additional options, and provide opportunities for users that may not normally utilize co-working locations.

[0048] Another problem is that many locations have underutilized spaces (e.g., empty hotel rooms and conference rooms) that represent lost opportunities and inefficiencies. Embodiments described herein address such a problem by providing an additional use of under-utilized hotel rooms, hotel conference spaces, rental properties and other captive locations. In addition, the embodiments take advantage of the often logistically superior locations of captive spaces, and the hospitality infrastructure (e.g., food service, amenities, internet connection, etc.) already in place.

[0049] A further problem includes logistical and security challenges that could arise from installing a workspace in an existing location. For example, it may be difficult or undesirable to have the owner of a location be responsible for security and ensuring that a workspace is not accessed by unauthorized persons. Embodiments provide a solution by providing security and verification features incorporated with a dedicated space that allow a user to conveniently book a dedicated space and be granted access by a hardware component or device without requiring any participation by a location owner.

[0050] Figure 1 depicts an embodiment of a system 10 for scheduling the use of, and providing temporary access to, dedicated spaces, such as workspaces. The system 10 includes a processing unit or system such as a server 12. The server 12 is connected via a network 14 to one or a plurality of user devices 16. The user devices 16 may be any computing devices, such as desktop computers, laptop computers, on-board vehicle processors, and mobile devices. For example, the user devices 16 include mobile devices such as smartphones or tablets. The server 12 may be a system or device at a given location, or include multiple distributed devices.

[0051] The network 14 can be any network that connects a variety of devices, including, but not limited to, local area networks (LANs), wireless networks, wide-area networks (WAN), blockchain networks, the Internet (a network of heterogeneous networks using the Internet Protocol, IP), and virtual private networks.

[0052] In an embodiment, each user device 16 is registered as a client, and the server 12 is configured as a host. A “server” or “host” may refer to a process or processes that provide a service, and/or the host computer device that performs the process or processes. Likewise, a “client” may refer to a process or processes of communication with the host, and/or the computer device that performs such process or processes.

[0053] The server 12 includes a processor 18 and memory 20 that stores various applications, software programs, processing modules and/or other processing units configured to perform functions related to interacting with the devices 16, acquiring user information, managing dedicated spaces, scheduling the use of dedicated spaces, verification and providing access to dedicated spaces. For example, the server 12 stores an application 22, such as a backend application, for performing one or more of the above functions, as well as any other desired functions.

[0054] The system 10 includes additional components connected to the network 14. In an embodiment, the system 10 includes one or more databases or other storage devices for storing data used by the application 22. For example, a user database 24 may be used to store user information, including user identification information, contact information, verification data and others. A scheduling and inventory database 26 may be used to store scheduling information and information regarding the dedicated spaces. It is noted that the system 10 may store information in various locations, and is not limited to the storage locations shown in Figure 1.

[0055] In an embodiment, the server 12 is configured to communicate with processing units 28 installed at each of a plurality of dedicated spaces 30. Each dedicated space 30 is disposed at a captive location, and each captive location may house one or more dedicated spaces. For example, one or more dedicated spaces are located within a hotel 32 or other rental property. A “rental property” is defined herein as any space, room or property that is rented or otherwise provided on a temporary basis. Rental properties include hotels, motels, private rentals, vacation rentals, bed and breakfasts, etc.

[0056] Captive locations include locations at which people are expected to remain temporarily for a predictable period of time. Captive locations, in some instances, may require that a person remain within a selected location or area (e.g., an airport), or remain within a vicinity of the location. In such captive locations, there may be restrictions in the available resources, and the resources may be ultimately controlled by a single entity or group of entities. Examples of captive locations include airports, bus stations, train stations, waiting rooms and others. For example, as shown in Figure 1, one or more dedicated spaces are located within an airport terminal 34.

[0057] Each device 16 is configured to install parts of the application 22, particularly front end components of the application 22. For example, each device 16 includes a processing device and storage for storing front end components 36 of the application 22. Front end components include one or more user interfaces, and one or more processing modules or units configured to store and transmit information input to the user, and receive communications from the server 12. Each device 16 includes a display 38, such as a touchscreen, that displays a user interface, such as a GUI and/or page. The user interface allows a user to input user information, browse available spaces, select and schedule the use of spaces, provide billing information and/or perform other functions.

[0058] In an embodiment, one or more of the dedicated spaces 30 are configured as a modular space that is installed within an existing captive location, such as a hotel lobby, conference room, business center, room, airport terminal, etc. The modular space provides an enclosed space that defines one or more rooms and includes various amenities and features for use by the user. The modular space is also referred to as a pod.

[0059] Figure 2 depicts an example of a dedicated space 30 configured as a modular space or pod 40. The pod 40 includes an enclosure 42 that encloses the space within. The enclosure may be, for example, transparent walls. The pod 40 may define a single room or space, or define multiple separate rooms or areas. For example, the pod 40 includes partitions 44 that define multiple rooms or areas therein. In an embodiment, the entire pod 40 is reservable as a dedicated space 30.

[0060] In this example, the pod 40 includes a room 46 having features that include a desk 48, a computer 50, a chair 52 and a couch 54. Another room 56 is designed for three people, and has features that include a desk 48, a chair 52 and a computer 50 for each user. The room 56 can also include additional features, such as a television 58. A third room 60 is configured as a conference room, and includes a conference table 62 and a display device 64 such as a television, monitor and/or projection screen. The various features provided in or in conjunction with a dedicated space, workspace or seat may be referred to as “attributes.” Other features or attributes that may be included in the pod include lighting, furniture colors, privacy features, climate control, disinfectant features, various furniture configurations, and wheels for moving the pod 40. Disinfectant features include, for example, disinfection lighting technology (e.g., Ultraviolet disinfectant and antimicrobial light), provision of sanitizers, and disinfectant coatings (e.g., photocatalytic nano-coating),

[0061] In the above example, the workspace 46 has one seat at the desk 48 and three seats on the couch 54. The workspace 56 has three seats, and the workspace 60 has ten seats.

[0062] The pod 40 includes one or more entrances to allow access thereto. For example, the pod 40 includes an entry door 66 to each room in the pod 40. One or more of the entry doors 66 are operated by an access device 68 and/or a locking mechanism, which is a hardware device that can communicate with the server 12 and be used to gain entry into a workspace. Each access device 68 is configured to provide access to a user, e.g., by unlocking a door 66 of the pod 40. An access device 68 may be provided for each entry door 66, or a single access device 68 may be provided for the entire pod 40.

[0063] Although the access devices 68 are shown as disposed on the enclosure 42, the access devices 68 are not so limited and can be located remotely. For example, one or more of the access devices 68 may be part of a kiosk or other device located within a captive space occupied by the modular space 40. Remotely located access devices 68 can communicate with controllers at each door 66 via Bluetooth, wi-fi, cellular, wired and/or other connections.

[0064] The access device 68 may be any suitable hardware device that includes a user interface that allows a user to enter identification and/or verification information. For example, as discussed further below, a user may be assigned an access code (e.g., a bar code or QR code or hash (a long string of apparently random numbers and letters)) or a button on the mobile app that allows the user to enter an assigned or reserved dedicated space 30 at a scheduled date and time. In another example, the access device 68 includes a card reader or scanner that allows a user to scan an issued card or printed code.

[0065] Figure 3 depicts an embodiment of a method 100 for scheduling the use of dedicated spaces 30 and providing temporary access to such spaces. The method 100 includes a number of stages, aspects of which are represented by blocks 101-106. The stages may be performed in the order described, or one or more stages may be performed in a different order. In addition, the method may include fewer than all of the stages.

The method 100 is discussed in conjunction with the system 10 for illustrative purposes; however, the method 100 may be performed by any suitable processing device or system.

[0066] At block 101, user information and/or a request for a dedicated space 30 is received by the server 12 from a user device 16. In an embodiment, if the user has not yet registered, the user can register for the services provided by the application 22 by entering user information via a registration page or other user interface. The user information includes, for example, name, address, telephone number, e-mail and/or other identifying information. Other user information may be entered, such as the user location, payment information, and user preferences (e.g., type of space, space capacity, preferred features, preferred dates, times and durations of use, etc.) This user information is transmitted to the server 12 or other processing device, and stored in the user database 24 or other suitable location.

[0067] In some cases, if the user device 16 has GPS or other location tracking capability, the server 12 may automatically determine the user’s location and suggest available dedicated spaces 30 in the vicinity of the user.

[0068] After registration, or if the user is already registered, the user requests the use of a dedicated space 30 by inputting request information, via a request or reservation page or other user interface. The request information includes, for example, the requested date and time, the requested duration. The request information may also include information regarding features or attributes desired by the user. For example, the user can select a desired location or geographical region, the type of space (e.g., workspace, conference room), the size of the space, the number of people that the space can accommodate and others. The user can also request features or attributes such as soundproofing, privacy, the type of chair or other furniture, electronic devices (e.g., desktop computer, laptop computer, printer, scanner, television, projector, etc.), additional furniture (e.g., a couch, cot lounge chair, etc.), presentation devices, stationery and others. Requested attributes may also include food and/or beverage service, availability of food and/or beverage for purchase, nearby services (e.g., printing), and others.

[0069] It is noted that one or more features or attributes may be configured to automatically activate or adjust based on detecting the user approaching or entering a dedicated space 30. For example, lights may automatically turn on, and/or a climate control system may be turned on and adjusted to set the space 30 to a default temperature or a user specified temperature and/or humidity.

[0070] At block 102, the server 12 generates a unique identifier for the user, referred to as a “user identifier.” The unique user identifier is exclusive to the user and may be maintained by the system 10 for as long as the user is registered. The unique user identifier may be provided to the user at registration. For example, a user identifier is issued to the user after the user downloads the application 22 and registers. [0071] At block 103, the server 12 searches stored inventory information for available dedicated spaces 30. The inventory information includes, for example, a list of dedicated spaces 30 maintained by the system 10, and data indicating which dedicated spaces 30 have been reserved and the time, date and duration of the reservations. For example, inventory information (as well as other information described herein) can be stored in tables, lists and/or other data structures in the scheduling and inventory database 26.

[0072] The server 12 identifies dedicated spaces 30 that are in the location or region requested by the user, and are available during the requested date, time and duration. Available dedicated spaces 30 are then sent to the user device 16 and the front end of the application 22 displays the available spaces to the user.

[0073] If there are no dedicated spaces 30 available (or fewer than some minimum number) at the requested location, date and time, the server 12 may identify and transmit an indication of alternative dedicated spaces 30 available in alternative locations, date and/or times. Criteria by which alternative dedicated spaces 30 are identified are based on, for example, user preferences input during registration, in the process of requesting a dedicated space 30 or otherwise.

[0074] At block 104, the user selects an available dedicated space 30 and requests a reservation of the dedicated space for the requested date, time and duration. The request information is transmitted to the server 12, which reserves the selected dedicated space 30.

[0075] At block 105, the server 12 enables access for the unique user identifier (“permission”) or assigns an access code to the user. The “permission” or access code is specific to the reserved dedicated space 30, as well as the date, time and/or duration of the reservation. The access code may be a numerical and/or textual code, a bar code, a Quick Response (QR) code, or hash (a long string of apparently random numbers and letters) or be in any other format. For example, the server 12 assigns a QR code to the user and returns the QR code with a confirmation message sent to the user (e.g., via email, text, display page, browser page, etc.). The QR code (or other access code) may be issued for each individual registration, or the QR code can be assigned to a user at or after registration, and maintained for use by the user for all or some future reservations.

[0076] The access code is generally defined herein as any set of values, graphical element or other set of data that is recognizable by a controller or other processing device associated with a given dedicated space 30. The access code may be provided as discussed above in a virtual format, or stored in an access card or other physical implementation that can be scanned or otherwise read by the controller.

[0077] At block 106, upon arrival of a user at a reserved dedicated space, the user is verified, and if verification is successful, including verifying the user’s credit balance, the user is granted access to the reserved dedicated space by scanning his/her device or inputting the access code into a controller at or proximate to the reserved dedicated space 30. For example, the user can enter the access code at a keypad or touchscreen, can scan an access card, can scan a printed QR code, or can scan a QR code displayed on a user’s smartphone or other device.

[0078] Once the access code has been entered, the access code is matched to reservation data stored, for example, in a cloud-based data structure or other remotely stored data structure, at the controller or otherwise accessible by the controller. For example, the controller may transmit the input access code to the server 12, which matches the code to stored reservation information. If the access code is matched to the reservation information, the server 12 transmits a message to the controller to open a door or otherwise grant access to the user.

[0079] The access code may include, or refer to, one or more unique identifiers associated with a reserved space. For example, the access code includes or refers to a unique user identifier (e.g., the user identifier generated at block 102). The access code may also include or refer to a unique reservation identifier, which includes the unique user identifier, a unique store identifier that indicates the location of the reserved space, and a unique “pod” identifier that indicates the specific space 30 that was reserved. For example, if the user reserved a workspace or pod, the seat/space identifier indicates the workspace or pod. [0080] In an embodiment, the system 10 is configured to perform a verification process. The verification process includes receiving a check-in notification or message from the user. For example, upon arrival at the captive location of the reserved dedicated space (or within some time period prior to the reserved start time), the user checks in and is requested to provide verification information. The verification information includes, for example, the user’s email address and phone number, and may include the reservation information. Prior to granting access to the user the system 10 determines whether the user is present at the correct location and the correct time (e.g., within a selected amount of time from the start time of the reservation) and whether the user has sufficient credit.

[0081] The verification may also include prompting the user to provide information that is matched to records maintained by the system 10. For example, the user can be prompted to provide an email address and phone number, which is matched to stored user information. The verification process may also include verification of the unique identifier previously given to the user.

[0082] The system 10 can determine a user’s arrival and/or verify the user in a variety of manners. For example, a user can check in via a mobile application, a kiosk or other device. In another example, the system 10 can include sensors or detectors proximate to a reserved space that detects the presence of the user and may also allow identification of the user, e.g., using facial recognition. Such sensors or detectors can also be utilized in a verification process.

[0083] Figures 4 and 5 illustrate an example of aspects of the method 100, which include aspects related to granting access to a reserved dedicated space 30 (Figure 4), and aspects related to scheduling a dedicated space (Figure 5). The aspects are described below as a process 110 for verifying a user and/or granting user access to a reserved space, and a scheduling process 120. In this example, the dedicated space 30 is a conference room defined by a modular space or pod.

[0084] The process 110 of Figure 4 includes a number of stages represented by blocks 111-119. The stages may be performed in the order described, or one or more stages may be performed in a different order. In addition, the process 110 may include fewer than all of the stages. The process 110 is discussed in conjunction with the system 10, but may be performed by any suitable processing device or system.

[0085] At block 111, upon arrival, the user checks in via the application 22, e.g., by clicking or selecting an option in a booking ticket issued to the user. At block 112, the system 10 determines whether the user has arrived on time, etc.

[0086] If the arrival is on time or late (but within the reservation time), at block 113, the system 10 verifies that the user has arrived. Then, the user can enter the QR code (or other access code) or hash (a long string of apparently random numbers and letters) at an access point or device located proximate to the reserved space to access the space (block 114).

[0087] If the user has arrived early, the system 10 optionally can check whether the reserved space or a nearby space is available (block 115). If there is availability, at block 116, an offer (an early-start offer) may be provided to the user. The system 10 then receives a response from the user (block 117). If yes, the previously assigned QR code may be used or canceled (118) and a new QR code may be issued (block 119)

[0088] The scheduling process 120 of Figure 5 includes a number of stages represented by blocks 121-128. The stages may be performed in the order described, or one or more stages may be performed in a different order. In addition, the scheduling process 120 may include fewer than all of the stages. The scheduling process 120 is discussed in conjunction with the system 10, but may be performed by any suitable processing device or system.

[0089] At block 121, a user opens front end application components and accesses a user interface via a user device 16. In this example, the interface is referred to as a landing page. The user may log in or be prompted to log in as discussed below. It is noted that the user can be logged in indefinitely, or may log in and log out for each session. A session may include various operations related to requesting a workspace or workspaces, scheduling us of a workspace or workspaces, verifying a user and/or providing user access. For example, a session includes one or more of the steps of blocks 121-128. [0090] At block 122, the user selects an option for “conference room” and is directed to a reservation page. The user then enters a desired location, date, time and duration. The user may also select options such as size, seating capacity and preferred locations, and also select desired features or attributes (e.g., availability of food service, type of seats, computers, presentation equipment, etc.)

[0091] At block 123, the server 12 searches a database for available spaces 30 that match the user preferences (or alternatives if one or more preferences are not available). The server 12 than presents available spaces 30. At block 124, the user selects a space 30 from the available spaces 30.

[0092] At block 125, the server 12 determines whether the user is logged in. If not, the user is prompted to sign in or log in (block 126) or create a new account (block 127). In an embodiment, the user is kept logged on permanently or indefinitely.

[0093] At block 128, a confirmation (booking ticket) is provided to the user, as well as an access code, e.g., a QR code or hash (a long string of apparently random numbers and letters), that includes or refers to a unique identifier.

[0094] Figure 6 is a flow diagram that depicts an example of aspects of the method 100 related to scheduling the use of a dedicated space 30. The aspects are represented by a scheduling process 130 that includes a number of stages represented by blocks 131-136. The stages may be performed in the order described, or one or more stages may be performed in a different order. In addition, the scheduling process 130 may include fewer than all of the stages. The scheduling process 130 is discussed in conjunction with the system 10, but may be performed by any suitable processing device or system.

[0095] At block 131, a user accesses the application 22 and a reservation/scheduling page or other display is presented. At block 132, the application 22 receives an input from the user that requests a dedicated space 30 and specifies a desired time and date (or multiple times and/or dates), a number of people that will be using the space during the requested date(s) and time(s), and other data such as desired location (e.g., at a specific hotel or geographical location). The input may also include user data, such as user name, telephone number, e-mail address, physical address and any other information (e.g., if the user data was not provided at registration or if the user updates the user data).

[0096] The user input requesting a dedicated space 30 may also specify various features or attributes. Examples include availability of food and/or beverage service, equipment (e.g., computers, display devices, furniture) and other features such as sit/stand desks, cushioned seats, windows, privacy features and others. Features such as soundproofing and disinfectant features may be selectable features or optional features, or come standard with one or more dedicated spaces 30.

[0097] At block 133, the server 12 checks for availability of dedicated spaces 30 that match the user’s specifications.

[0098] At block 134, the system 10 provides a confirmation to the user via a confirmation notification or e-mail or other suitable communication (e.g., mobile text message, voice call, etc.). The confirmation notification or email confirms availability, price and payment method. The confirmation notification or email may also confirm whether various features and amenities are available, such as food service. For example, the user may be able to select and schedule delivery of food or other amenities via the application.

[0099] At block 135, the server 12 receives confirmation from the user and receives payment. At block 136, the server 12 then reserves the selected dedicated space for the scheduled date, time and duration.

[00100] Figure 7 illustrates an example of aspects of the method 100, which include aspects related to registering a user, verifying a user upon arrival, and providing access to a reserved space. This example is represented by a process 140 that includes a number of stages represented by blocks 141-154. The stages may be performed in the order described, or one or more stages may be performed in a different order. In addition, the process 140 may include fewer than all of the stages. The process 140 is discussed in conjunction with the system 10, but may be performed by any suitable processing device or system. [00101] At block 141, a user downloads the application 22 (front end components), creates a login password, enters payment information (e.g., credit card information), and may also choose a price plan. At this stage, the user may be assigned a unique user identifier. The user may also provide an upfront payment to be maintained as a balance by the system 10.

[00102] Examples of price plans include a pay per use plan, by which a user is billed only for reservations made and features or amenities used, assuming a minimum balance is maintained. Other price plans may include periodic payment plans, such as monthly plans, by which a user can make reservations as needed up to some maximum.

[00103] When a user reserves a dedicated space 30, the server 12 receives the user’s request and reserves a dedicated space 30 for a specific date, time and duration. The user may be assigned an access code, such as a QR code or hash (a long string of apparently random numbers and letters), which can be used by the user to access the reserved space.

[00104] At block 142, the user checks in with the application 22 when the user arrives at a location of the reserved dedicated space 30. This check in can be in any form, such as a button or check box displayed on a page of the application or in a confirmation notification or email. The check in is transmitted to the server 12 for verification, or the controller itself may perform the verification.

[00105] At block 143, the system 10 determines the user’s current balance, and then verifies that the user has a sufficient payment balance (block 144). If the balance is below a selected threshold amount, the system 10 can increase the balance using stored payment information (block 145).

[00106] At block 146, the user presses a button in the mobile app or scans the assigned access code at the controller. The controller and/or server 12, upon verifying that the access code is correct, begins a seat booking process.

[00107] In this example, the user presses a button in the mobile app or scans the access code at a hardware controller at the reserved space. The hardware controller may be a device (e.g., a processing unit 28) attached to an exterior of the reserved space 30, or otherwise located, or contained in the mobile app.

[00108] As part of the booking process, if more than one dedicated space 30 or “pod” is located at the location arrived at by the user, the controller or the application 22 prompts the user to select a “pod”, e.g., from a floor plan visual display (block 147). The floor plan may be displayed by the controller, or displayed on the user’s device.

[00109] At block 148, a dynamic password may be issued to the user, which is specific to the dedicated space 30 or “pod” selected by the user. The password may be used to access amenities. If the user is issued the dynamic password, the “pod” booking period starts (block 149).

[00110] At block 150, when the user is ready to leave, the user checks out, e.g., using an interface provided by the application 22. The interface may be displayed on the user’s device, a computer or screen provided with the “pod”, or at the controller. “Pod” booking ends at block 151.

[00111] In an embodiment, the user may be charged according to the actual amount of time spent in the dedicated space, as opposed to a pre-set duration, or the amount may be rounded up to the nearest minute or increment of minutes, e.g. 10 or 15 minutes. The system 10, upon verification of the balance and upon the user scanning the QR code, starts a taximeter or timer (block 152) to keep track of the duration of the user’s stay and the amount to be billed. When check out is completed, the taximeter is stopped (block 153), and the user’s balance is appropriately deducted (block 154).

[00112] In the above, each pod 40 is a single dedicated space 30, but is not so limited. The pod 40 may define a single space or define multiple individual separate spaces. For example, the partitions 44 of the pod 40 can define multiple individual dedicated spaces. A user may request one of the individual spaces, or request a seat within one of the individual spaces. Thus, a dedicated space 30 having multiple individual rooms, or multiple seats or workstations, can be reserved by individual users independent of one another. [00113] Figures 8-11 depict examples of data records that can be stored by the system 10, for example, in the database 24, the database 26, the server 12 and/or any other suitable location. The data may be stored in any suitable format, such as arrays, lists, files, pages, objects, collections, hierarchies and others. In these examples, the data is stored in a non-relational database (NoSQL database) structure, in which various forms of information are organized as collections. It is noted that any suitable data structure and/or type of database (e.g., relational or non-relational) may be used.

[00114] Referring to Figure 8, an example of stored user information is shown. The user information includes a “user collection” 200, which includes a record or document for each user registered by the system 10. Figure 8 shows one of the user records 202, configured as a document. The user record 202 includes fields or entries indicating the user’s name, email, telephone number, country, etc. The user record 202 also stores a unique user identifier, which in this example is based on a combination of the user’s email and telephone number, but is not so limited. In addition, the user record 202 includes an entry for the access code (e.g., QR code) assigned to the user (if applicable).

[00115] The user record 202 may also include information related to the user’s activity in the system 10. For example, the user record 202 stores the user’s sign-up or initial registration date, the user’s initial use (“guest visit”) of a dedicated space 30, and metrics indicative of the number of visits, amount of time spent and total amount of money spent.

[00116] Referring to Figure 9, inventory data is stored in a “location collection” 210, which includes a store or location record 212 for each location in which dedicated spaces 30 are available. Each store record 212 is configured as a document in this example. The store records 212 may be categorized and/or organized based on the type of location (e.g., hotel, airport, etc.).

[00117] The store record 212 stores information including a unique location or store identifier, which may be based on location information (e.g., the name, address and/or telephone number). Other information includes name, address, number of dedicated spaces in the location, and the size of dedicated spaces. [00118] The store record 212 may also include information regarding the individual dedicated spaces at the location. For example, the store record 212 includes a subcollection indicative of the inventory of dedicated spaces 30 at the location. Each type of space may be given a respective record or document (sub-document).

[00119] As shown in Figure 9, for example, a sub-record 214 is provided for office spaces and “phone booths” designed for single users, and sub-records 216, 217 and 218 are provided for small spaces (space S), medium spaces (space M), and large spaces (space L), respectively. Small, medium and large sizes may refer to any desired sizes or size ranges. An example of a size range is about 1 square meter (m²) to about 12 m² (e.g. small refers to a range of about 1 m² to about 3 m², medium refers to a range of about 3 m² to about 6 m², and large refers to a range of about 6 m² to about 12 m²). Individual dedicated spaces in each sub-record are identified via a serial number or other suitable identifier.

[00120] As noted above, a dedicated space may include various features and/or amenities. The store record and/or individual dedicated space records may indicate the features and/or amenities provided. For example, as shown in Figure 9, the “phone booth 1” entry includes an entry indicating “furniture package A,” which is a set of features provided by the “phone booth 1” dedicated space.

[00121] Examples of features are shown in Figure 10, which illustrates an example of a collection 220 that stores categories of dedicated spaces available in a location, dedicated spaces owned by a given owner, or all dedicated spaces maintained by the system 10. The collection 220 includes a services record 222, configured as a document that includes entries for each type of space. In this example, the dedicated spaces are categorized by size. Each entry may also include the billing rate for use.

[00122] The collection 220 may also store information describing features and/or amenities available with one or more dedicated spaces. For example, the collection includes sub-records 224 (subdocuments) that indicate packages of features such as “furniture packages” including features such as sit/stand or height adjustable desks, soft seating, and others. It is noted that the configuration of these “pods” and the specified features are shown for illustrative purposes and are not intended to be limiting.

[00123] Figure 11 shows an example of a guest visit collection 230, which stores information regarding each registered user’s visits to dedicated spaces 30. The guest visit collection 230 includes a visitation record 232 (document) for each user. The visitation record 232 includes user and location information (e.g., unique user identifier, user name, location identifier, location name, etc.). The record 232 also records user visits by checkin time, check-out time, and pod selection.

[00124] Figure 12 depicts an example of a display page 250 generated by components of the application 22. The display page 250 is accessible to an administrator or owner of one or more dedicated spaces 30 maintained by the system 10. This page is denoted as a management and/or operational “dashboard” page, and provides information regarding the number, type and location of each dedicated space 30. The dashboard page 250, as shown provides information such as the total number of users that reserved dedicated spaces 30, revenue, total number of seats provided by the dedicated spaces 30. As shown, the display page 250 includes links to other pages, such as a “user management” page for managing records of registered users, a “plans” page that describes the layout and features of owned dedicated spaces 30, a “property” page that includes records of captive locations in which owned dedicated spaces 30 are located, a “transaction” page detailing information regarding individual transactions, and a “reports” page.

[00125] Figure 13 depicts an example of a computer device 300 that may be used to perform functions described herein. Components of the computer device 300 include one or more processors or processing units 312, a system memory 314, and a bus 316 that couples various system components including the system memory 314 to the one or more processing units 312. The system memory 314 may include a variety of computer system readable media. Such media can be any available media that is accessible by the one or more processing units 12, and includes both volatile and non-volatile media, removable and non-removable media. [00126] For example, the system memory 314 includes a storage system 318 for reading from and writing to a non-removable, non-volatile memory 320 (e.g., a hard drive). It is noted that the storage system 318 is not so limited, and can be disposed within the device 300 and/or externally (e.g., in a database). The system memory 314 may also include volatile memory 322, such as random access memory (RAM) and/or cache memory. The computer device 300 can further include other removable/non- removable, volatile/non-volatile computer system storage media.

[00127] As will be further depicted and described below, system memory 314 can include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

[00128] For example, the system memory 314 stores an application 324 or components thereof (e.g., front end components if the computer device 300 is a client device, or a full application if the computer device 300 is a server or other host device). The application 324 may include one or more application programs, program modules, and/or program data. Program modules of the application 324 generally carry out the functions and/or methodologies of embodiments described herein.

[00129] For example, the program modules include an input module 326 configured to receive data such as user information and user requests. The program modules can also include an inventory module 328 configured to maintain lists, tables and/or other information regarding dedicated spaces 30, and a scheduling or reservation module 30 configured to maintain information regarding reservations of dedicated spaces 30.

[00130] The one or more processing units 312 can also communicate with one or more external devices 332 such as a keyboard, a pointing device, a display, and/or any devices (e.g., network card, modem, etc.) that enable the one or more processing units 12 to communicate with one or more other computing devices. In addition, the one or more processing units 312 can communicate with an external storage device such as a database 334. Such communication can occur via Input/Output (I/O) interfaces 36. Other interfaces might include application programming interfaces (APIs) not shown here. [00131] The one or more processing units 312 can also communicate with one or more networks 338 such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 340. The processing units 12 can also communicate wirelessly via, for example, a Bluetooth connection 342 or the like. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with the computing system 310. Examples, include, but are not limited to microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

[00132] Some portions of the exemplary embodiments described above are presented in terms of algorithms and symbolic representations of operations on data bits within a processor-based system. The operations are those requiring physical manipulations of physical quantities. These quantities may take the form of electrical, magnetic, optical, or other physical signals capable of being stored, transferred, combined, compared, and otherwise manipulated, and are referred to, principally for reasons of common usage, as bits, values, elements, symbols, characters, terms, numbers, or the like. Nevertheless, it should be noted that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the description, terms such as “executing” or “processing” or “computing” or “calculating” or “determining” or the like, may refer to the action and processes of a processor-based system, or similar electronic computing device, that manipulates and transforms data represented as physical quantities within the processor-based system’s storage into other data similarly represented or other such information storage, transmission or display devices.

[00133] Various embodiments of the present invention can be realized in hardware, software, or a combination of hardware and software. Embodiments can be implemented using one or more program modules and data storage units, and can be realized in a centralized fashion in one computer system or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system - or other apparatus adapted for carrying out the methods described herein - is suited. A typical combination of hardware and software could be a general- purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.

[00134] Exemplary embodiments of the present invention can also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which - when loaded in a computer system - is able to carry out these methods. Computer program means or computer program as used in the present invention indicates any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: (a) conversion to another language, code or, notation; and (b) reproduction in a different material form.

[00135] A computer system in which exemplary embodiments can be implemented may include, among others, one or more computers and at least a computer program product on a computer readable medium, allowing a computer system, to read data, instructions, messages or message packets, and other computer readable information from the computer readable medium. The computer readable medium may include nonvolatile memory, such as ROM, Flash memory, Disk drive memory, CD-ROM, and other permanent storage. Additionally, a computer readable medium may include, for example, volatile storage such as RAM, buffers, cache memory, and network circuits. Furthermore, the computer readable medium may comprise computer readable information in a transitory state medium such as a network link and/or a network interface including a wired network or a wireless network that allow a computer system to read such computer readable information.

[00136] It will be appreciated that features, elements and/or characteristics described with respect to an embodiment of the disclosure may be variously used with other embodiments of the disclosure as may be desired. [00137] It will be appreciated that the effects of the present disclosure are not limited to the above-mentioned effects, and other effects, which are not mentioned herein, will be apparent to those in the art from the disclosure and accompanying claims.

[00138] Although the preferred embodiments of the present disclosure have been disclosed for illustrative purposes, those skilled in the art will appreciate that various modifications, additions and substitutions are possible, without departing from the scope and spirit of the disclosure and accompanying claims.

[00139] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

[00140] Embodiments of the disclosure are described herein with reference to diagrams and/or cross-section illustrations, for example, that are schematic illustrations of idealized embodiments (and intermediate structures) of the disclosure. As such, variations from the shapes of the illustrations as a result, for example, of manufacturing techniques and/or tolerances, are to be expected. Thus, embodiments of the disclosure should not be construed as limited to the particular shapes of components illustrated herein but are to include deviations in shapes that result, for example, from manufacturing.

[00141] Any reference in this specification to "one embodiment," "an embodiment," "exemplary embodiment," etc., means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment. [00142] While the subject matter has been described in detail with reference to exemplary embodiments thereof, it will be apparent to one skilled in the art that various changes can be made, and equivalents employed, without departing from the scope of the disclosure.

[00143] In conclusion, it will be understood by those persons skilled in the art that the present disclosure is susceptible to broad utility and application. Many embodiments and adaptations of the present disclosure other than those herein described, as well as many variations, modifications and equivalent arrangements, will be apparent from or reasonably suggested by the present disclosure and foregoing description thereof, without departing from the substance or scope of the disclosure.

[00144] Accordingly, while the present disclosure has been described here in detail in relation to its exemplary embodiments, it is to be understood that this disclosure is only illustrative and exemplary of the present disclosure and is made to provide an enabling disclosure of the disclosure. Accordingly, the foregoing disclosure is not intended to be construed or to limit the present disclosure or otherwise to exclude any other such embodiments, adaptations, variations, modifications and equivalent arrangements.

Claims

CLAIMS What is claimed is:

1. A method of scheduling use of a dedicated space, the method characterized by: receiving user information from a user at a processing device, the user information including a request for temporary use of a dedicated space; searching by the processing device among a record indicative of a plurality of dedicated spaces; presenting one or more dedicated spaces from the record to a user, and receiving a selection of a dedicated space from the user; upon arrival at the dedicated space, verifying the user; and based on the verifying, providing access to the reserved dedicated space to the user.

2 The method of claim 1 , wherein each dedicated space is installed in a captive location configured for use on a temporary basis.

3. The method of any of claims 1 to 2, further comprising: reserving the selected dedicated space for the user at a requested date and time.

4. The method of any of claims 1 to 3, wherein the verifying is based on at least one of: receiving a check in message from the user, and detecting a presence of the user.

5. The method of any of claims 1 to 4, wherein the captive location includes a rental property.

6. The method of any of claims 1 to 5, wherein the captive location is a location in which persons are expected to remain for a predictable period of time.

7. The method of any of claims 1 to 6, wherein the dedicated space is a modular space installed at the captive location and removable from the captive location.

8. The method of any of claims 1 to 7, further comprising assigning a unique user identifier to the user.

9. The method of any of claims 1 to 8, wherein reserving the dedicated space includes assigning a unique reservation identifier, the unique reservation identifier configured to uniquely identify the user, the reserved dedicated space, and the captive location in which the reserved dedicated space is installed.

10. The method of any of claims 1 to 9, wherein verifying the user includes receiving an input from the user at the captive location, and matching the input to the unique identifier.

11. The method of any of claims 1 to 10, wherein reserving the dedicated space includes providing an access code to the user, the access code specific to the reserved dedicated space and the requested data and time.

12. The method of any of claims 1 to 11, wherein the verifying includes receiving an input from the user at an input device located at the captive location, and matching the input to the access code.

13. A system for scheduling use of a dedicated space, the system comprising: a processing device configured to communicate with a plurality of user devices, the system characterized by the processing device being configured to perform: receiving user information from a user device at the processing device, the user information including a request for temporary use of a dedicated space; searching among a record indicative of a plurality of dedicated spaces; presenting one or more dedicated spaces from the record to a user, and receiving a selection of a dedicated space from the user; upon arrival at the dedicated space, verifying the user; and based on the verifying, providing access to the reserved dedicated space to the user.

14 The system of claim 13, wherein each dedicated space is installed in a captive location configured for use on a temporary basis.

15. The system of any of claims 13 to 14, wherein the processing device is further configured to perform: reserving the selected dedicated space for the user at a requested date and time.

16. The system of any of claims 13 to 15, wherein the verifying is based on at least one of: receiving a check in message from the user, and detecting a presence of the user.

17. The system of any of claims 13 to 16, wherein the dedicated space is a modular space installed at the captive location and removable from the captive location.

18. The system of any of claims 13 to 17, wherein the processing device is configured to assign a unique user identifier to the user, and reserving the dedicated space includes assigning a unique reservation identifier, the unique reservation identifier configured to uniquely identify the user, the reserved dedicated space, and the captive location in which the reserved dedicated space is installed.

19. The system of any of claims 13 to 18, wherein verifying the user includes receiving an input from the user at the captive location, and matching the input to the unique identifier.

20. The system of any of claims 13 to 19, wherein the input device is included in a hardware controller attached to the reserved dedicated space or located within the captive location, the hardware device in wireless communication with the processing device.