A method for resource allocation in an office environment and related electronic device

Abstract

A server device is provided. The server device comprises memory circuitry, processor circuitry, and an interface. The server device is configured to receive a resource request from a user device. The resource request comprises resource request data associated with an event. The resource request data comprises a time parameter indicative of a tolerance margin associated with a timing of the event. The server device is configured to obtain, based on the resource request data, resource availability data. The resource availability data is associated with an availability of one or more resources. The server device is configured to determine, based on the resource request data and the resource availability data, a resource response indicative of a candidate resource. The server device is configured to transmit the resource response to the user device.

Description

[0001] A METHOD FOR RESOURCE ALLOCATION IN AN OFFICE ENVIRONMENT AND RELATED

[0002] ELECTRONIC DEVICE

[0003] The present disclosure pertains to the field of managing and / or booking resources. The present disclosure relates to a method for allocating resources in an office environment and a related device.

[0004] BACKGROUND

[0005] Well-executed resource management can be helpful for corporate office and commercial settings. With employees working both in an office environment as well as remotely, often across multiple office locations or buildings, delegating appropriate office space, including physical location space, has become increasingly challenging. Flexible working encourages participants to work at times that suit their own personal and professional life, often leading to differing availability, even across the same time zone. To further complexify matters, many commercial events include employees from multiple companies and offer options like catering and various need-based accommodations.

[0006] SUMMARY

[0007] Thus, finding an appropriate time and space for an event can be challenging. Therefore, there is a need for improved systems and processes for allocation of office resources for in-person or hybrid events.

[0008] Accordingly, there is a need for devices and methods for resource allocation, which may mitigate, alleviate, or address the shortcomings existing and may provide more efficient and effective resource allocation, such as dynamic assignment of resources, including physical spaces, for events, based on participant attendance and other relevant factors.

[0009] A server device is provided. The server device comprises memory circuitry, processor circuitry, and an interface. The server device is configured to receive a resource request from a user device. The resource request comprises resource request data associated with an event. The resource request data optionally comprises a time parameter indicative of a tolerance margin associated with a timing of the event. The server device is configured to obtain, based on the resource request data, resource availability data. The resource availability data is optionally associated with an availability of one or more resources. The server device is optionally configured to determine, based on the resource request data and the resource availability data, a resource response indicative of a candidate resource. The server device is optionally configured to transmit the resource response to the user device.

[0010] A method, performed by a server device, is disclosed. The method comprises receiving a resource request from a user device. The resource request comprises resource request data associated with an event. The resource request data comprises a time parameter indicative of a tolerance margin associated with a timing of the event. The method comprises obtaining resource availability data associated with an availability of one or more resources. The obtaining is based on the resource request data. The method comprises determining, based on the resource request data and the resource availability data, a resource response indicative of a candidate resource. The method comprises transmitting the resource response to the user device.

[0011] It is an advantage of the present disclosure that the disclosed server device allows for resources to be allocated dynamically, according to a tolerance margin for the time of the event and participant preferences. Advantageously, resources, for example, meeting rooms, may be assigned and reassigned as described herein based on the resource(s) availability. In other words, resources may be reallocated based on input received up to a specified time parameter, thereby allowing for changes that are more accommodating to and reflective of the reality of the needs of the system.

[0012] This may advantageously allow for improved efficiency in allocating resources, and thus reducing overbooking of resources. For example, rather than having resources unoccupied due to last minute changes or inadequately sized or equipped resources based on the dynamic nature of a working environment, the server device can ensure a best fit for the current demands based on available resources. Thus, booked but unoccupied resources are reduced, and less participant time is wasted on attempting to address last-minute accommodations in a system that is not fit for the purpose.

[0013] Further, the present disclosure enables an optimization across multiple constraints. For example, the time parameter, tolerance margin, and participant data that factor in a probability of the participant attending the event. Moreover, these and other factors are considered by the server device from an objective perspective, further increasing the benefit of the multi-constraint optimization efforts of the server device in resource allocation. A user device is disclosed. The user device comprises memory circuitry, processor circuitry, and an interface. The user device is configured to obtain a participant input indicative of a resource request. The user device is configured to transmit the resource request to a server device. The user device is optionally configured to obtain from a server device a resource response. The resource response is optionally indicative of a candidate resource. The user device is optionally configured to provide the resource response.

[0014] A method performed by a user device is disclosed. The method comprises obtaining a participant input indicative of a resource request. The method comprises transmitting the resource request to a server device. The method comprises obtaining a resource response indicative of a candidate resource from the server device. The method comprises providing the resource response.

[0015] BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The above and other features and advantages of the present disclosure will become readily apparent to those skilled in the art by the following detailed description of examples thereof with reference to the attached drawings, in which:

[0017] Fig. 1 is a diagram illustrating an example system comprising an example server device and an example user device according to this disclosure,

[0018] Figs. 2A-C show a flow-chart illustrating an example method, performed by a server device, for an allocation of resources according to this disclosure,

[0019] Fig. 3 is a flow-chart illustrating an example method, performed by a user device of a wireless communication system, for obtaining an allocation of resources according to this disclosure, Fig. 4 is a block diagram illustrating an example server device according to this disclosure, and Fig. 5 is a block diagram illustrating an example user device according to this disclosure.

[0020] DETAILED DESCRIPTION

[0021] Various examples and details are described hereinafter, with reference to the figures when relevant. It should be noted that the figures may or may not be drawn to scale and that elements of similar structures or functions are represented by like reference numerals throughout the figures. It should also be noted that the figures are only intended to facilitate the description of the examples. They are not intended as an exhaustive description of the disclosure or as a limitation on the scope of the disclosure. In addition, an illustrated example needs not have all the aspects or advantages shown. An aspect or an advantage described in conjunction with a particular example is not necessarily limited to that example and can be practiced in any other examples even if not so illustrated, or if not so explicitly described.

[0022] In many commercial settings, office meeting rooms are delegated by meeting organizers, such as facilitators or administrators, in advance of the meeting start. The decision for these meeting room delegations, including the decision of which meeting room to use, is processed by a solution and the processing is based on conditions. Some of those input conditions may be a type of meeting, a number of participants, an office presence (such as whether or not attendees will be in an office on the given day), guests (such as out-of-town guests), catering, company policies and other requirements.

[0023] In other words, organizers, including employees, have limited tools. For example, calendar systems are used for this type of scheduling force facilitators to add attendees and then adjust the start and end-time based on availability, and then once a time has been found, add a free resource, such as, meeting room, even without confirmation of physical attendees.

[0024] Currently, resource utilization in an office setting is determined largely by a set of tools available to employees. As such, much of the employees’ booking behaviours is limited by these tools. For example, calendar systems force facilitators to add participant and then adjust the start and end time based on participant availability. It is not until the final step that the facilitator is enabled to add a free resource (such as a meeting room) even if it is uncertain how many attendees will physically or virtually attend the meeting. Therefore, office resources (for example, desks and meeting rooms) are not able to be used to their fullest potential in modern office environment.

[0025] For example, a current office software add-on for scheduling meetings exists. Using this software solution, an organizer can send multiple suggestions of meeting times to a group of potential meeting attendees. The potential participant make an active choice when to attend the meeting. This solution requires participants to take action to show when participants prefer to have the meeting. As described above, in this solution, the resource (such as a meeting room) is to be added manually afterwards depending on when participants can attend.

[0026] The present disclosure provides, inter alia, techniques enabling improved systems and processes for allocation of resources for in-person or hybrid events.

[0027] A resource may be seen as one or more elements that may be relevant to and potentially available for an event. For example, a resource may include a meeting room and / or an event space. In one or more examples, a resource may include equipment for the meeting, such as audio-visual equipment or accessibility equipment to make a meeting more accessible for those with special needs, such as visual and / or audio impairment, such as limited mobility. In one or more examples, a resource may include catering or other hospitality-related options, for example, snacks, meals, or beverages for an event. In one or more examples a resource may include participants of an event, including potential participants. For example, a resource may include one or more of: a meeting room, equipment, catering, and a participant.

[0028] A participant may be seen as an invitee of an event, such as a potential attendee of the event. In one or more examples, a participant may be an employee of a company organizing the event. In one or more examples, a participant may be an external invitee, for example, a person from another company or a client company invited to attend the event. In one or more examples, a participant may be an organizer of the event. For example, one or more participants to a meeting include one or more of: internal invitee(s), external invitee(s), and a facilitator. The facilitator may be seen as the person organizing and / or administrating the event.

[0029] An event may be seen as a gathering of participants at a point in time, for example, a meeting. In one or more examples, an event may be a company or external event, such as a weekly meeting, a networking event, or another suitable type of gathering. The event may for example be an event occurring in a physical and / or virtual space. The event is for example associated with (such as occurring at) a facility. The facility may for example be a corporate facility (such as office facility, conference hall, co-working space, etc.), a hospitality facility (such as a hotel), an educational facility (such as a school, university, etc.), a healthcare facility (such as a hospital), a sports facility (such as a fitness center), a travel facility (such as an airport, bus terminal, ferry terminal, etc.), or any other facility suitable for an event.

[0030] The figures are schematic and simplified for clarity, and they merely show details which aid understanding the disclosure, while other details have been left out. Throughout, the same reference numerals are used for identical or corresponding parts.

[0031] Fig. 1 is a diagram illustrating an example system 1 comprising an example server device 400, for example server device 400 of Fig. 4 and an example user device 300, for example user device 300 of Fig. 5, according to this disclosure.

[0032] The system 1 described herein may comprise one or more user devices 300, 300A, and / or one or more server devices 400. A user device may refer to a mobile device and / or a user equipment, UE.

[0033] The user device 300, 300A may be configured to communicate with the server device 400 via a wired and / or wireless link 10, 10A.

[0034] The server device (such as server device 400) may be seen as a device configured to receive request (such as a resource request) and provide response (such as a resource response).

[0035] In one or more examples, a participant (for example, a facilitator) may send a resource request from a user device 300 (for example user device 300 of Fig. 5) to the server device 400 (for example server device 400), via a wired and / or wireless link 10.

[0036] In one or more examples, the facilitator (such as a user of a user device 300) invites, using the user device 300, other potential participants for example by adding their emails addresses to a meeting invitation, such as an invitation to an event. The facilitator may input a duration of the meeting, any parameters, or requirements regarding in person versus hybrid or remote attendance options, any equipment that is needed (for example, TV, a digital whiteboard, an audio system).

[0037] In one or more examples, the facilitator may provide if there is a preference for a morning, lunchtime, or afternoon meeting. In one or more examples, the facilitator may input a due date for a standalone meeting (for example, the meeting must occur before 22 March). For reoccurring meetings (such as weekly, bi-weekly, monthly), the facilitator may specify a desired frequency. Together, the provided information may be considered the resource request. A resource request is further described herein.

[0038] In one or more examples, in response to receiving the resource request, the server device 400 may obtain, based on the resource request data, resource availability data. In one or more examples, the server device 400 may act as a “concierge service” and check participants calendar availability based on the resource request data and / or information received in the resource request. In some examples, the server device 400 can determine a resource response indicating a candidate resource. The determination may be based on the resource request data and the resource availability data. For example, the server device 400 may determine a particular time and a particular meeting room location for the requested event. In one or more examples, the server device 400 of the system 1 may transmit, to one or more user devices 300, 300A, a resource response. In one or more examples, the resource response may be a meeting invitation. The meeting invitation may be sent to participants. In some examples, the facilitator’s resource request may have indicated a set of required participants and another set of optional participants. In this case, the server device 400 may try to find a matching time for the required participants, but in an example case when this is not possible, the server device can find an acceptable time for the mandatory participants. In an example where the server device 400 finds no available resources matching any of the criteria, a notification may be sent via the user device 300 to the facilitator, for example, the facilitator’s mobile device, proposing one or more alternative times. In one or more examples, one or more alternative times may be sent to the participants. In one or more examples, the server device 400 may transmit, to the user device 300, alternative options, including proposing “online-only” meetings (i.e., dropping the in-person element), breaking the meeting into multiple meeting rooms, dropping optional participant(s), or other suitable solutions. In some examples, alternative options may be based on a pre-determined policy. In some examples, alternative options may be created dynamically by the server device 400, the user device 300, or the facilitator. In one or more examples, the server device 400 may transmit a response requesting, from the facilitator, a change or update in the criteria (in other words, an updated resource request).

[0039] Figs. 2A-2C show a flow diagram of an example method 100, performed by a server device according to the disclosure, for allocating one or more resources for an event, such as based on resource availability and a resource request. The server device is for example the server device disclosed herein, such as the server device 400 of Fig. 1 and Fig. 4.

[0040] The method 100 comprises receiving S102 a resource request from a user device. The resource request comprises for example resource request data associated with an event. The resource request data comprises for example a time parameter indicative of a tolerance margin associated with a timing of the event. For example, a user device (such as the user device disclosed herein, such as user device 300 of Fig. 1 and Fig. 5) may be a company or personal laptop or mobile phone, wearable, or other suitable device as disclosed herein.

[0041] The resource request may be seen as a request for resource to be used at an event. For example, a resource request may be received as part of a message from the user device. Resource request data may be seen as data associated with a request, such as data specifying items requested. In some examples, the items requests can be related to timing aspects of the event, the particulars of the event, and / or information regarding the participants. In one or more examples, resource request data is data that a user inputs, for example, to a user device, for example user device 300 of Fig. 1 and Fig. 5, which is then received by the server device, for example server device 400 of Fig. 1 and Fig. 4. For example, the resource request data may include, as described herein, names, emails addresses or other identifiers of participants to a meeting invitation. In some examples, the resource request data may also include a duration of the meeting, any parameters, or requirements regarding in person versus hybrid or remote attendance options, any equipment that is needed (for example, TV, a digital whiteboard, an audio system). In one or more examples, resource request data may also include a preference for a morning, lunchtime, or afternoon meeting. For example, the resource request data may also state a due date for a standalone meeting (for example, the meeting must occur before 22 March). For reoccurring meetings (such as weekly, bi-weekly, monthly), the facilitator may specify a desired frequency.

[0042] A time parameter may be seen as a parameter to be applied to the timing of the event. For example, the time parameter may be seen as a tolerance margin which indicates a time range in which the event should occur. For example, the time parameter may include a tolerance margin parameter. For example, a time parameter may be “within a week” of the requested date or of the time the resource request is sent.

[0043] In one or more examples, the tolerance margin associated with the timing of the event may be seen as a time range in which the event, such as a meeting, needs to occur. In one or more examples the tolerance margin may be input by the participant or facilitator organizing the event. In one or more examples, the tolerance margin may be predetermined or determined by a company policy or the like.

[0044] The method 100 comprises obtaining (such as receiving, and / or retrieving), S104 based on the resource request data, resource availability data associated with an availability of one or more resources.

[0045] Resource availability data may be seen as data indicating an availability of a resource, for example, a room or a participant’s calendar, to be booked at a particular time. In one or more examples, the resource availability data may comprise participant calendar data and / or participant response data, indicative of whether or not each participant will attend. The resource availability data may indicate which resources (such as, meeting rooms, equipment (such as sound systems, visual display systems, or other resources), and / or catering) are available for a requesting participant’s use.

[0046] In one or more examples, the resource availability data associated with the availability of one or more resources may be accessed from a local or remote server, from local or remote memory, or in another way. For example, resource availability data may be stored in memory associated with a company’s calendar system for participants, rooms, equipment, and / or catering. For example, resource availability data may be stored in the cloud and stored and / or accessed in another manner. The resource availability data may also indicate a particular time or set of time periods during which the resource or resources are available.

[0047] The method 100 comprises determining, S116 based on the resource request data and the resource availability data, a resource response indicative of a candidate resource.

[0048] A candidate resource may be seen as a resource identified as a potential fit for the resource request. For example, a candidate resource can be a meeting room identified that fits the current number of participants, time criteria and other criteria (as defined in the resource request data). As described herein, the candidate resource may be confirmed or updated based on received user input, for example from a user device such as user device 300 of Fig. 1 and Fig.5.

[0049] The method 100 comprises transmitting, S132 to the user device, the resource response. A resource response may be seen as a response to a resource request. For example, the resource response may be indicating one or more resources assigned (such as recommended) for the event. In one or more examples, the resource response may comprise a time and / or a location for the particular event.

[0050] In one or more examples, a resource response may comprise a message to one or more participants. For example, the resource response can include an email confirming a date and time of the event to any of: the participants, the participants who appear available, the participants who are internal, and / or another subset of participant, and / or non-participant users.

[0051] In one or more examples, the server device is configured to identify, based on the resource request from the user device, a set of one or more external entities. In some examples, external entities may be seen as external resources, and / or more specifically, external participants. In some examples, the server device may identify the external participants by comparing an email domain with a company email domain. If the email domain differs, the server device may identify the particular participant associated with the email address as an “external participant”. In some examples, the server device may identify locations or rooms as “external”, thus requiring a different set of logistical instructions.

[0052] In one or more examples, the server device is configured to generate, based on the identifying a set of one or more external entities, a set of one or more communications. In one or more examples, the server device can generate, based on identifying a set of one or more external participants, as described herein, a set of communications intended for the external recipients. For example, a communication can be an email, and the email can contain information relevant to the event for an external participant, such as a company wi-fi code, specific directions or location information for the room (for example, directions not needed for those who frequent the location often), policy information such as a confidentiality policy, emergency information, including for example, an emergency contact information, an emergency exit map, or other emergency information, and the like. The server device can be configured to transmit the communication to all external participants. In some examples, the server device can be configured to transmit a draft of this communication along with a list of identified external recipients to a user device, for example, a user device associated with the facilitator. The communication can also provide an option for the facilitator to confirm the list, edit, or authorize the server device to send the communication to external recipients.

[0053] In one or more examples, the server device may be configured to determine, based on the identified external recipients, if there is a situation which can be problematic with regard to external recipients. For example, a meeting in which only external recipients are available for an on-site meeting. For example, a meeting in which the only internal persons attending are at the last minute unable to attend. In one or more examples, the server device may notify the facilitator and / or all participants. In one or more examples, the server device may recommend moving the meeting to an online-only event. In one or more examples, the server device may automatically or with input from a participant, cancel any catering, cancel the meeting booking, or other relevant tasks to move, delay, or cancel the event.

[0054] In one or more examples, the communication generated by the server device may include a request for input regarding a meal option. For example, the server device may generate and transmit, as described herein, a communication that suggests the meal options for the day (such as “today’s meat, fish, vegetarian, vegan, kosher, or other dietary meal option”). The communication may also include timing and location information about when and where the meal or snack is to be dropped off for the event. For example, options can include “outside of meeting room” or “pick-up location”. In some examples, there may be an integration with a catering system to provide more dietary options. The server device may be configured to receive input from one or more participants, via one or more user devices, responsive to a request for dietary or other preferences, as described herein.

[0055] In one or more example methods, the resource request data comprises time data, event data, and / or participant data associated with one or more requested participants.

[0056] Time data may be seen as data indicating time-related aspects of the event, such as requirement(s) related to the timing of the event. For example, time data can indicate a periodicity of the event, such as a meeting. For example, the time data included in the resource request data can include a preferred or requested timing of the event (such as, Tuesday 12 March at 10am). In some examples, the time data can include the time parameter, indicating a tolerance margin (such as, beginning of week 10, no later than week 12). In some examples, time data can include a time of day and / or day of the week (such as, mornings and / or Wednesdays). In some examples, the time data can include a time not to schedule a meeting (such as, not Wednesday). In some examples, the time data can include a preferred recurrence of the event (such as, weekly, or more specifically, weekly on Thursdays anytime, or more specifically, weekly on Thursday afternoons). For example, the time data included in the resource request data can include one or more of: a preferred or requested timing of the event, the time parameter, indicating a tolerance margin, a time of day and / or day of the week, a time not to schedule a meeting, and a preferred recurrence of the event.

[0057] Event data may be seen as data about the event that is being scheduled, such as requested event data. In one or more examples, event data can include a type of event, for example, a meeting, a networking event, a lunch event, an informal event, panel, conference, or other descriptors that can help in characterizing the event in a particular manner. In some examples, event data may also include a date, time, and maximum number of anticipated participants for the specified event. For example, the event data of the resource request data can be seen as original or initial event data.

[0058] A participant may be seen as one or more potential attendees of the event, including a facilitator or organizer (such as the person organizing the meeting).

[0059] Participant data may be seen as data associated with one or more of the participants, such as requested in the response request. For example, participant data may comprise email addresses of one or more, such as each, participants. In one or more examples, participant data can also include other contact information for the participant, such as role or title data for the job the participant holds within the company, seniority data, accessibility needs or preferences, dietary preferences, or other data that may be relevant to the event booking. In one or more examples, the server device may use the email addresses to determine whether a participant is an internal or external participant. Accordingly, and based on the determination, the server device may adjust the resource response.

[0060] In one or more example methods, the resource response indicative of a candidate resource is determined based on the resource availability data and one or more of: the time data, the event data, and / or the participant data associated with the one or more requested participants (for example, from the resource request).

[0061] In one or more example methods, the method 100 comprises obtaining (such as receiving at the server device, from a participant device and / or the user device), S122 in response to the transmitting of the resource response to the user device, a participant input.

[0062] A participant input may be seen as input received by the server device from one or more user devices, for example, the user device 300 in Fig. 1 and Fig. 5. In other words, a participant input can be input received from one or more requested participants. In one or more examples, a participant input can include a response indicating the participant has accepted the event request (for example, “yes” or “accept”). In some examples, the participant input can indicate the participant has declined the event request (for example, “no” or “decline”). In some examples, the participant input can include a response indicating whether the participant may join in person or online. In some examples, the response can indicate the participant is unsure if he or she will attend (for example, “maybe”), and / or unsure if he or she will attend online or in person (for example, “location unsure” or “to be determined”).

[0063] In one or more examples, the participant input can be input from the facilitator or event organizer. In some examples, the server device may be configured to obtain responses from a facilitator’s user device only. For example, a setting can allow the facilitator to first review the resource response (in other words, for example, the recommended date, time, and location of the meeting). Pending a facilitator’s approval or confirmation or input of some type, the resource response can be distributed to participants in the participant list. In some examples, the resource response distribution can also be triggered automatically after, for example, a specified time period, if the facilitator does not respond. In one or more examples, upon the facilitator’s approval of the resource response, all or part of the resource response can be distributed to a select set of participants, for example, only internal participants. In some examples, a recurring or reoccurring event may be specified in the resource request data. In some examples, the resource request data may contain an indication of whether or not the event should begin at the same time on each occasion. In some examples, the weekly recurrence may be of importance, but the specific timing may be less important. For example, it may be important to have the event occur once every week and that every invited participant is able to attend, but it might be less important that the event is always on, for example, a Wednesday, or for example, at 10am. In some examples, the facilitator may provide various deviation information as part of the resource request or as participant input at a later date. For example, the facilitator may specify a particular hour or day during which the recurring meeting should be scheduled by the server device.

[0064] In one or more example methods, the method 100 comprises generating, S118 based on the resource request data and the resource availability data, event data associated with the event. For example, the even data generated may include information regarding the candidate resource, the participant(s) that have accepted the event (such as tentatively, and / or firmly), etc. In other words, the event data generated in S118 may be seen as event data updated based on the participant input(s) received so far, and other information regarding venue, meeting rooms etc.

[0065] In one or more example methods, the method 100 comprises determining S120 whether a participant input is received. In some examples, the server device, for example server device 400, determines an absence of participant input within a particular range, for example a time range. The particular range may be specified in the resource request data. In some examples, the particular range may be derived from the resource request data. In one or more examples, the server device may determine that a participant input is received, for example, within a time period from the transmittal of the resource response.

[0066] In one or more example methods, the method 100 comprises determining S124 that the participant input is not received (such as withing a time period). In one or more example methods, the method 100 comprises obtaining (such as receiving and / or retrieving) S126 historical participant data associated with a participant profile upon determining S124 that the participant input is not received (such as within a time period). In one or more example methods, the participant profile is associated with one of the one or more requested participants.

[0067] Historical participant data may be seen as calendar or other system data (for example, from an internal or external employee or participant system or database) associated with a participant’s attendance. For example, historical participant data may include data indicating how often a participant actually attends a meeting, after replying with an affirmative or tentative response to the meeting (in other words, how often the participant attends meetings he or she accepts). In some examples, the historical participant data can also include data indicating other instances of attendance or non-attendance, such as how often the participant attends when he or she has declined the meeting invitation, how often the participant attends when he or she has not responded to the invitation, how often the participant is absent from a meeting when he or she has accepted the invitation, how often the participant is absent from the meeting when he or she has declined the meeting or how often the participant is absent when he or she has not responded to the invitation. In some examples, lateness or punctuality data can be collected and associated with the participant attendance, for example, how often a participant is late, and by how many minutes, when he or she has accepted the invitation, and other punctuality-based metrics. Historical participant data can also include an element of online versus in-person, for each of the above-described examples. In some examples, the historical participant data may associate other relevant data to the particular participant’s historical attendance, including time of day, location, or the like.

[0068] In one or more examples, historical data may be collected automatically or retrieved from the calendar or other system by the server device. For example, a participant input (such as “accept”) for a particular event (such as a meeting) may be received. For example, when the meeting is online or a hybrid (partially online, for example, via a video or telephonic conference), the video conferencing software may automatically note and communicate which profiles, users, or devices were in attendance (such as, via an attendance list shared with a facilitator or all participants at the end of the meeting). In some examples, a facilitator, organizer, or other event participant may provide input as to which participants attended and which did not. For example, in an in-person meeting or hybrid meeting, an organizer can submit via, for example, the video conferencing software integrated with a calendaring system, an attendance list or confirmation of potential attendees. In this way, historical participant data can be more accurately collected, for example, in cases where a participant has declined or responded with a “no” to the meeting invitation, but then attended the meeting in person at the selected location.

[0069] A participant profile may be seen as a software abstraction layer connected with a database for storing relevant data about a particular participant. The participant profile may be seen as a set of a parameters characterizing an aspect or behavior of the participant. The data for the participant profile may be obtained from one or more systems, including personal and / or corporate calendar software systems, GPS systems, or other systems. The participant profile can store relevant data, including some of the data types described here such as historical participant data and participant data. In some examples, the participant profile can also contain a variety of participant preferences, which can be obtained passively (such as through data collection) or actively (such as by user input), for any number of preferences relevant to an event, including an online versus in-person preference, a time of day or day of the week preference for particular meetings, dietary or temperature preferences, or other preferences, as described herein.

[0070] In one or more example methods, the method 100 comprises determining S128, based on the historical participant data, an attendance parameter upon determining S124 that the participant input is not received. In one or more example methods, the attendance parameter is indicative of a probability of the participant associated with the participant profile attending the event. An attendance parameter may be seen as a metric indicating a likelihood that a particular participant attends or does not attend an event. For example, in an instance when a particular participant (such as one of the invited or potential attendees of the event) has not received, the server device may obtain historical participant data, or other relevant participant data from the participant profile, to determine, using a probabilistic rule, how likely it is that that participant will in fact attend the meeting.

[0071] In one or more example methods, the attendance parameter is determined by applying a probabilistic rule. A probabilistic rule may be seen as a conditional probabilistic rule. In one or more examples, the conditions (such as pre-conditions) are known. For example, the following conditions can be known the prior attendance behavior for the individual based on the participant invited, duration, time of day, day of the week, advance notices of the meetings, and / or other information.

[0072] In one or more examples, the probabilistic rule may be an approach to estimating the probability of attendance based on one or more of the conditions. In one or more examples, Bayesian inference may be used for example with some other techniques. This may allow to inference attendance probability for a participant that frequently or repetitively fails to attend meetings before a particular time, for example, 10AM. For example, for such a participant, the probability of attendance for such meetings obtained via Baye’s rule would decrease. In one or more examples, when a participant often attends meetings with his superior, the probability of attendance at meetings in which the boss is present obtained via Baye’s rule may increase.

[0073] In one or more examples, the probabilistic approach may be based on heuristics.

[0074] In one or more examples in absence of one or more aspects of prior attendance data, a heuristic approach (for example, a guided heuristic technique using a heuristic function) may be used. For example, the probability of attendance may be determined to be 0% if the determination is based on an assumption that the early morning takes precedence. In one or more examples, a probability of attendance may be determined to be 50% when the weighting is unknown, and the probability of attendance may be determined to be 100% when the presence of the superior is determined to be the most important factor.

[0075] In one or more examples, the conditional probabilistic rule may be expressed, such as: P_attendance | X = F(P_prior_attendance| X) where X is the conditions of the meeting and F is a (heuristic) function. In other words, the probability of attendance given condition X may be equal to a heuristic function applied to the probability of attendance of prior meetings given the same condition.

[0076] In one or more example methods, the method 100 comprises updating S130 the event data based on the attendance parameter upon determining S124 that the participant input is not received.

[0077] In some examples, the server device can, based on the determined attendance parameter (such as an 80% likelihood that the particular participant from whom no input has been received will attend the particular meeting), update the event data when the participant input is not received by the server device. For example, the server device can update the event data to include the particular participant. In some examples, the server can indicate (for example, using metadata) that this particular participant, for which there is a “yes”, “maybe” or an “attending” determination, was based on an inference rather than a direct response. In this way, the event data would accurately reflect the current status of the resource requirements.

[0078] In one or more examples, the updating of the event data for participants who have not responded can occur based on a particular timing threshold. For example, depending on specific factors associated with the participant as well as the event, the server device may determine a particular timing threshold that once met, will trigger the activating step. For example, for participant A, who is the company CTO, for all onsite meetings, the updating of the event data occurs when the participant input has not been received 30 minutes before the start of the event. For example, for another participant with a less busy calendar, the updating can occur when the participant has not responded by the start of the day of the event.

[0079] In one or more example methods, the probabilistic rule is a Bayes’ rule.

[0080] In one or more example methods, determining S116 the resource response comprises determining S116A, based on the time parameter, the resource response. In one or more examples, the resource response (such as resource response data, such as a meeting date, time, and location) may be determined based the time parameter, for example, a time parameter that requires a meeting to occur within two weeks of the resource request, for example thereby allowing for some tolerance in the timing aspects of the event. In some examples, the time parameter may require an event to occur by a certain date or during a certain time of day, or it may specify another time-related constraint.

[0081] In one or more example methods, determining S116 the resource response comprises determining S116B whether the candidate resource satisfies one or more criteria. In one or more examples, the one or more criteria may be various elements specified by the resource request data. For example, the criteria may include a particular participant or set of participants who must be available to attend the event. In some examples, the criteria can include a time parameter, as described herein. In some examples, the criteria can be based on one or more settings or parameters defined by a company, a company policy, a server device administrator, or in another way. For example, the criteria can be based on a setting that meetings lasting over 3 hours must always be in a location that satisfies a well-being standard. In some examples, in the determining whether the candidate resource satisfies one or more criteria, the server device may confirm, for an all-day meeting, that the candidate resource, in this case a conference room, satisfies the criterion. In some examples, the criteria can include the availability of a meeting room capable of hosting the number of participants at the requested time (with time tolerance).

[0082] In one or more example methods, the one or more criteria are based on one or more respective thresholds. In some examples and as described above, the criteria (such as, a well-being standard) may be determined to be met, when the server device checks when the resource (such as a conference room) has been satisfied, may be based on one or more thresholds related to the number of participants, the time, the equipment, catering etc. For example, the thresholds can include having at least one window, having direct access to more than two doors, having sufficient air flow, having two plants, or other well-being metrics.

[0083] In one or more example methods, the method 100 comprises assigning (such as allocating, reserving for a time period) S106, for a first time period, a resource as the candidate resource. In some examples, a candidate resource, for example a particular meeting room, may be assigned (such as temporarily, such as a placeholder), by the server device as the resource that satisfies the resource request. The candidate resource assignment may last for a particular time period (in other words a first time period). In one or more examples, an assignment may be seen as a reservation of a resource for a time period, for example, a temporary reservation of a resource. For example, the resource (such as a meeting room) may be “held” or “reserved” for a period of time. In some examples, the period of time may be predetermined by the server device. In some examples, the period of time may be based on the resource request data, for example, the time period may be related to the time of the event itself. For example, the time period may last from the time the candidate resource is assigned to fifteen minutes before the event itself. In some examples, the time period for which the candidate resource is “held” may be specified in the resource request.

[0084] In one or more example methods, the method 100 comprises updating S108, upon an expiry of the first time period, the assignment of the resource as the candidate resource. In some examples, the candidate resource (such as a meeting room) may be updated (for example, additional data received from one or more user device, including, for example, participant input) upon the expiry of the first time period (for example, a time period (such as 1 day, 12h, 5h, 3h, or 10min) before a start time of the event specified in the particular resource request).

[0085] In one or more example methods, the method 100 comprises updating S110, upon the expiry of the first time period, the assignment of the resource as the candidate resource by confirming and / or modifying the assignment.

[0086] In one or more examples, the candidate resource (such as a meeting room) may be updated by confirming the assignment. For example, 10 minutes before the event is scheduled to take place, the server device may check that the candidate resource is still suitable to fulfill the various criteria provided by the resource request data (for example, in light of further input received from facilitator or attendee participants). In some examples, the candidate resource is confirmed and designated as part of the resource response.

[0087] In one or more examples, the candidate resource (such as a meeting room) may be updated upon the expiry of the first time period by modifying the assignment. For example, during the first time period, one or more additional inputs or requests pertaining to the relevant event (such as an addition of more participants, an addition of a catering need, a removal of external attendees or the like) may have been received. In some examples, one or more additional inputs or requests may have been received by the server device that are not directly pertaining to the event (such as a company-wide meeting has been requested, a board meeting has been requested, or the like). In some examples, the new or additional information may cause the server device to modify the assignment of the candidate resource (for example, the server device may reassign the candidate resource, the server device may remove the assignment of the candidate resource, or modify the assignment in some other way). In some examples, the candidate resource assignment may be confirmed and / or modified without further input from a user device. In one or more example methods, the method 100 comprises receiving S112 an updated resource request from the user device.

[0088] In one or more example methods, the method 100 comprises updating S114 the assignment based on the updated resource request.

[0089] For example, the resource response (including elements such as a room reservation), may accommodate any last-minute changes and allow for a more dynamic use of resources (such as meeting rooms).

[0090] In some examples, one or more participants, for example, the facilitator, may make changes to the resource response. For example, the server device may transmit the resource response with a confirmation of a resource, such as a meeting room location, at the expiry of a time period, such as the first time period. In some examples, the facilitator may override or update one or more element indicated in the resource response, including for example, selecting a different meeting room location, adding one or more participants, or updating in another way.

[0091] In one or more example methods, the method 100 comprises generating S134 notification information based on the participant data.

[0092] In one or more example methods, the method 100 comprises transmitting S136 notification information based on the participant data.

[0093] In some examples, the server device may generate and transmit notification information (such as an email, text, or audio message) to one or more user devices, as described herein. For example, the server device may generate and transmit an email or set of emails to all participants or a subset of participants (for example, participants who have been identified as external to the company).

[0094] In one or more example methods, the resource availability data comprises calendar data, location data, facility data, accessibility data, and / or policy data.

[0095] Calendar data may be seen as data associated with or derived from one or more calendars or calendar systems. For example, calendar data may be from a company calendar software system. For example, calendar data may be from a personal calendar software system. For example, calendar data may indicate a person or other resource’s availability at a particular date and / or at a particular time.

[0096] Location data may be seen as one or more data points indicating a physical location. For example, location data may indicate a particular city (for example, Copenhagen) or a particular country (for example, Denmark). In one or more examples, location data may indicate a particular address (for example, a street and number) or particular geographical or satellite coordinates. In one or more examples, location data may indicate a relative location (for example, north of the corporate headquarters building) and / or it may indicate a particular building location (for example, building 2D, 4thfloor).

[0097] Facility data may be seen as data associated with or provided for a particular facility (for example the facility associated with the event), such as an office building. In one or more examples, facility data may include physical facility data (such as an event space) or a virtual or online facility (such as a video conferencing room, a virtual reality, augmented reality or metaverse space).

[0098] Accessibility data may be seen as data associated with accessibility features or information for a particular location or locations. For example, the accessibility data may indicate a wheelchair accessibility for a particular meeting room. In one or more examples, the accessibility data may also indicate a hearing aid capability for a particular resource room, the presence of visual or hearing impairment or language resource (such as a sign language translator, a language translator, braille, or other accessibility resources).

[0099] Policy data may be seen as data corresponding to a set of one or more policies. For example, policy data may comprise a company policy, such as a remote working policy. In some examples, the policy data may also include a catering policy, a security policy (such as a physical and / or digital security policy for external participants or guests), a data use and retention policy, or any other policy.

[0100] In one or more example methods, the resource availability data is obtained from a resource system. The resource system may be seen as an internal company software system. In some examples, the resource system may be a calendar software system, a video conferencing system, an email system, another type of system, and / or any combination of the aforementioned systems. For example, the system may be a calendar system integrated into an email and video conferencing software system.

[0101] Fig. 3 shows a flow diagram of an example method 200, performed by a user device according to the disclosure, for obtaining an assignment of resources. The user device is for example the user device disclosed herein, such as user device 300 of Fig. 1 and Fig. 5.

[0102] The method 200 comprises obtaining S202 a participant input indicative of a resource request.

[0103] In one or more examples, the participant input, such as participant input described at S122 of Figs. 2A-C, may be obtained by the user device.

[0104] The method 200 comprises transmitting S204 the resource request to a server device. In some examples, the server device may be server device 400 of Fig. 1 and Fig. 4. The resource request, is for example the resource request received by the server device 400 at S 102 of method 100 of Figs. 2A-C.

[0105] The method 200 comprises obtaining S206, from the server device, a resource response indicative of a candidate resource. In some examples, the resource response may be the resource response transmitted by the server device at S132 of method 100 of Figs. 2A-C. In one or more examples, the server device may transmit, to the user device, a resource response (such as an event booking time, location, and other data) that includes or indicates the candidate resource (such as a tentative room or time booking). In some examples, the user device may obtain the resource response indicating one or more elements that are candidate resource and one or more elements that are confirmed resources.

[0106] The method 200 comprises providing S208 the resource response. In some examples, the user device may provide the resource response via a user interface, for example a Ul as part of a display on a mobile device or other screen on a user device. The resource response may be provided audibly (such as spoken or read by a software system in the user device). The resource response may be provided in any other way that is compatible with a user interaction via a user device.

[0107] In some examples, the user device may transmit to a set of user devices associated with a set of participants of the event the resource response. In examples, the set of participants may include participants who have responded (for example, have indicated they will attend) as well as participants who have not responded (for example, via a participant input). As described herein, the resource response may comprise, inter alia, a room reservation, thus providing participants with a location of the event. In examples, this transmittal may occur just prior to the event, for example, 10 minutes before the meeting, as a reminder. In one or more examples, this transmittal may occur prior to the event, for example, 1 day before the meeting.

[0108] Fig. 4 shows a block diagram of an example server device 400 according to the disclosure. The server device may be configured to allocate resources, via a resource response. The server device 400 comprises memory circuitry 401 . The server device 400 comprises processor circuitry 402. The server device 400 comprises an interface 403. The server device 400 may be configured to perform any of the methods disclosed in Figs. 2A-C. In other words, the server device 400 may be configured for allocation of resources, such as, office meeting rooms. The server device 400 is configured to communicate with a user device, such as user device disclosed herein, using a system.

[0109] The interface 403 is configured for wired and / or wireless communications via a wired wireless communication system.

[0110] The server device 400 is configured to receive (such as, via the interface 403), a resource request from a user device. In one or more examples the resource request comprises resource request data associated with an event. In one or more examples, the resource request data comprises a time parameter indicative of a tolerance margin associated with a time or the event.

[0111] The server device 400 is configured to obtain (such as, via the interface 403 and / or using the memory circuitry 401 ), and based on the resource request data, resource availability data associated with an availability of one or more resources.

[0112] The server device 400 is configured to determine (such as, using the processor circuitry 402), based on the resource request data and the resource availability data, a resource response indicative of a candidate resource.

[0113] The server device 400 is configured to transmit (such as, via the interface 503), to the user device, the resource response. In one or more example server devices, the resource request data comprises time data, event data, and / or participant data associated with one or more requested participants.

[0114] In one or more example server devices, the server device is configured to obtain (such as, via the interface 403 and / or using the memory circuitry 401 ), in response to the transmittal of the resource response to the user device, a participant input.

[0115] In one or more example server devices, the server device is configured to generate (such as, using the processor circuitry 402), based on the resource request data and the resource availability data, event data associated with the event.

[0116] In one or more example server devices, the server device is configured to determine (such as, using the processor circuitry 402) whether a participant input is received.

[0117] In one or more example server devices, the server device is configured to, upon determining that the participant input is not received, obtain (such as, via the interface 403 and / or using the memory circuitry 401) historical participant data associated with a participant profile. In one or more example server devices, the participant profile is associated with one of the one or more requested participants.

[0118] In one or more example server devices, the server device is configured to, upon determining that the participant input is not received, determine (such as, using the processor circuitry 402) , based on the historical participant data, an attendance parameter.

[0119] In one or more example server devices, the attendance parameter is indicative of a probability of the participant associated with the participant profile attending the event.

[0120] In one or more example server devices, the attendance parameter is determined by applying a probabilistic rule.

[0121] In one or more example server devices, the server device is configured to, upon determining that the participant input is not received, update (such as, using the processor circuitry 402 and / or using the memory circuitry 401) the event data based on the attendance parameter.

[0122] In one or more example server devices, the probabilistic rule is a Bayes’ rule.

[0123] In one or more example server devices, the determination of the resource response comprises determining (such as, using the processor circuitry 402), based on the time parameter, the resource response.

[0124] In one or more example server devices, the determination of the resource response comprises determining (such as, using the processor circuitry 402), whether the candidate resource satisfies one or more criteria.

[0125] In one or more example server devices, the one or more criteria are based on one or more respective thresholds.

[0126] In one or more example server devices, the server device is configured to assign (such as, using the processor circuitry 402), for a first time period, a resource as the candidate resource.

[0127] In one or more example server devices, the server device is configured to update (such as, using the processor circuitry 402) , upon an expiry of the first time period, the assignment of the resource as the candidate resource.

[0128] In one or more example server devices, the server device is configured to update (such as, using the processor circuitry 402 and / or using the memory circuitry 401 ) , upon the expiry of the first time period, the assignment of the resource as the candidate resource by confirming and / or modifying the assignment.

[0129] In one or more example server devices, the server device is configured to receive (such as, via the interface 403), an updated resource request from the user device.

[0130] In one or more example server devices, the server device is configured to update such as, using the processor circuitry 402 and / or using the memory circuitry 401 ) the assignment based on the updated resource request.

[0131] In one or more example server devices, the server device is configured to generate (such as, using the processor circuitry 402), and transmit (such as, via the interface 403), notification information based on the participant data.

[0132] In one or more example server devices, the resource availability data comprises calendar data, location data, facility data, accessibility data, and / or policy data.

[0133] In one or more example server devices, the resource availability data is obtained from a resource system.

[0134] Processor circuitry 402 is optionally configured to perform any of the operations disclosed in Figs. 2A-C (such as any one or more of S102, S104, S116, S106, S108, S110, S112, S114, S116A, S116B, S118, S120, S122, S124, S126, S128, S130, S132, S134, S136). The operations of the server device 400 may be embodied in the form of executable logic routines (for example, lines of code, software programs, etc.) that are stored on a non-transitory computer readable medium (for example, memory circuitry 401) and are executed by processor circuitry 402.

[0135] Furthermore, the operations of the server device 400 may be considered a method that the server device 400 is configured to carry out. Also, while the described functions and operations may be implemented in software, such functionality may also be carried out via dedicated hardware or firmware, or some combination of hardware, firmware and / or software.

[0136] Memory circuitry 401 may be one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, a random-access memory (RAM), or other suitable device. In a typical arrangement, memory circuitry 401 may include a nonvolatile memory for long term data storage and a volatile memory that functions as system memory for processor circuitry 402. Memory circuitry 401 may exchange data with processor circuitry 402 over a data bus. Control lines and an address bus between memory circuitry 401 and processor circuitry 402 also may be present (not shown in Fig. 4). Memory circuitry 401 is considered a non-transitory computer readable medium.

[0137] Memory circuitry 401 may be configured to store resource availability data in a part of the memory.

[0138] Fig. 5 shows a block diagram of an example user device 300 according to the disclosure. The user device 300 comprises memory circuitry 301 , processor circuitry 302, and an interface 303.

[0139] The interface 303 is configured for wired and / or wireless communications via a wired and / or wireless communication system.

[0140] The user device 300 may be configured to perform any of the methods disclosed in Fig. 3. In other words, the user device 300 may be configured for allocation of resources, such as, office meeting rooms.

[0141] Processor circuitry 302 is optionally configured to perform any of the operations disclosed in Fig. 3 (such as any one or more of S202, S204, S206, S208). In other words, the wireless device 300 may be configured to obtain (such as, via the interface 303 and / or using the memory circuitry 301) a participant input indicative of a resource request.

[0142] The user device is configured to transmit (such as, via the interface 303 and / or using processor circuitry 302), the resource request to a server device.

[0143] The user device is configured to obtain (such as, via the interface 303), from the server device, a resource response indicative of a candidate resource.

[0144] The user device is configured to provide (such as, via the interface 303 and / or using processor circuitry 302), the resource response.

[0145] The operations of the user device 300 may be embodied in the form of executable logic routines (for example, lines of code, software programs, etc.) that are stored on a non-transitory computer readable medium (for example, memory circuitry 301 ) and are executed by processor circuitry 302).

[0146] Furthermore, the operations of the wireless device 300 may be considered a method that the wireless device 300 is configured to carry out. Also, while the described functions and operations may be implemented in software, such functionality may also be carried out via dedicated hardware or firmware, or some combination of hardware, firmware and / or software. Memory circuitry 301 may be one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, a random-access memory (RAM), or other suitable device. In a typical arrangement, memory circuitry 301 may include a nonvolatile memory for long term data storage and a volatile memory that functions as system memory for processor circuitry 302. Memory circuitry 301 may exchange data with processor circuitry 302 over a data bus. Control lines and an address bus between memory circuitry 301 and processor circuitry 302 also may be present (not shown in Fig. 5). Memory circuitry 301 is considered a non-transitory computer readable medium.

[0147] Memory circuitry 301 may be configured to store information (such as resource request data, resource availability data, event data, historical participant data, attendance parameter, one or more criteria, one or more thresholds, an assigned candidate resource, updated resource request, and / or notification information) in a part of the memory.

[0148] Examples of methods and products (server device and user device) according to the disclosure are set out in the following items:

[0149] Item 1 . A server device, comprising memory circuitry, processor circuitry, and an interface, wherein the server device is configured to: receive a resource request from a user device, the resource request comprising resource request data associated with an event, wherein the resource request data comprises a time parameter indicative of a tolerance margin associated with a timing of the event; obtain, based on the resource request data, resource availability data associated with an availability of one or more resources; determine, based on the resource request data and the resource availability data, a resource response indicative of a candidate resource; and transmit, to the user device, the resource response.

[0150] Item 2. The server device according to item 1 , wherein the resource request data comprises time data, event data, and / or participant data associated with one or more requested participants. Item 3. The server device according to any of the previous items, wherein the server device is configured to: obtain, in response to the transmittal of the resource response to the user device, a participant input.

[0151] Item 4. The server device according to any of the previous items, wherein the server device is configured to generate, based on the resource request data and the resource availability data, event data associated with the event.

[0152] Item 5. The server device according to items 3-4, wherein the server device is configured to determine whether a participant input is received.

[0153] Item 6. The server device according to item 5, wherein the server device is configured to, upon determining that the participant input is not received: obtain historical participant data associated with a participant profile, wherein the participant profile is associated with one of the one or more requested participants; determine, based on the historical participant data, an attendance parameter, wherein the attendance parameter is indicative of a probability of the participant associated with the participant profile attending the event, and wherein the attendance parameter is determined by applying a probabilistic rule; and update the event data based on the attendance parameter.

[0154] Item 7. The server device according to item 6, wherein the probabilistic rule is a Bayes’ rule.

[0155] Item 8. The server device according to any of the previous items, wherein the determination of the resource response comprises determining, based on the time parameter, the resource response. Item 9. The server device according to any of the previous items, wherein the determination of the resource response comprises determining whether the candidate resource satisfies one or more criteria.

[0156] Item 10. The server device according to item 9, wherein the one or more criteria are based on one or more respective thresholds.

[0157] Item 11. The server device according to any of the previous items, wherein the server device is configured to assign, for a first time period, a resource as the candidate resource.

[0158] Item 12. The server device according to item 11 , wherein the server device is configured to update, upon an expiry of the first time period, the assignment of the resource as the candidate resource.

[0159] Item 13. The server device according to item 12, wherein the server device is configured to update, upon the expiry of the first time period, the assignment of the resource as the candidate resource by confirming and / or modifying the assignment.

[0160] Item 14. The server device according to any of items 12-13, wherein the server device configured to: receive an updated resource request from the user device; and update the assignment based on the updated resource request.

[0161] Item 15. The server device according to any of the previous items, wherein the server device is configured to generate and transmit notification information based on the participant data.

[0162] Item 16. The server device according to any of the previous items, wherein the resource availability data comprises calendar data, location data, facility data, accessibility data, and / or policy data. Item 17. The server device according to any of the previous items, wherein the resource availability data is obtained from a resource system.

[0163] Item 18. A user device comprising memory circuitry, processor circuitry, and an interface, wherein the user device is configured to: obtain a participant input indicative of a resource request; transmit the resource request to a server device; obtain, from the server device, a resource response indicative of a candidate resource; and provide the resource response.

[0164] Item 19. A method, performed by a server device, for the assignment of resources, the method comprising: receiving a resource request from a user device, the resource request comprising resource request data associated with an event, wherein the resource request data comprises a time parameter indicative of a tolerance margin associated with a timing of the event; obtaining, based on the resource request data, resource availability data associated with an availability of one or more resources; determining, based on the resource request data and the resource availability data, a resource response indicative of a candidate resource; and transmitting, to the user device, the resource response.

[0165] Item 20. The method according to item 19, wherein the resource request data comprises time data, event data, and / or participant data associated with one or more requested participants.

[0166] Item 21. The method according to any of the previous items, wherein the method comprises: obtaining, in response to the transmitting of the resource response to the user device, a participant input.

[0167] Item 22. The method according to any of the previous items, wherein the method comprises generating, based on the resource request data and the resource availability data, event data associated with the event.

[0168] Item 23. The method according to items 21-22, wherein the method comprises determining whether a participant input is received.

[0169] Item 24. The method according to item 23, wherein the method comprises upon determining that the participant input is not received: obtaining historical participant data associated with a participant profile, wherein the participant profile is associated with one of the one or more requested participants; determining, based on the historical participant data, an attendance parameter, wherein the attendance parameter is indicative of a probability of the participant associated with the participant profile attending the event, and wherein the attendance parameter is determined by applying a probabilistic rule; and updating the event data based on the attendance parameter.

[0170] Item 25. The method according to item 24, wherein the probabilistic rule is a Bayes’ rule.

[0171] Item 26. The method according to any of the previous items, wherein determining the resource response comprises determining (S116A), based on the time parameter, the resource response.

[0172] Item 27. The method according to any of the previous items, wherein determining the resource response comprises determining (S116B) whether the candidate resource satisfies one or more criteria. Item 28. The method according to item 27, wherein the one or more criteria are based on one or more respective thresholds.

[0173] Item 29. The method according to any of the previous items, wherein the method comprises assigning (S106), for a first time period, a resource as the candidate resource.

[0174] Item 30. The method according to item 29, wherein the method comprises updating (S108), upon an expiry of the first time period, the assignment of the resource as the candidate resource.

[0175] Item 31. The method according to item 30, wherein the method comprises updating (S110), upon the expiry of the first time period, the assignment of the resource as the candidate resource by confirming and / or modifying the assignment.

[0176] Item 32. The method according to any of items 30-31 , wherein the method comprises: receiving (S112) an updated resource request from the user device; and updating (S114) the assignment based on the updated resource request.

[0177] Item 33. The method according to any of the previous items, wherein the method comprises generating (S134) and transmitting (S136) notification information based on the participant data.

[0178] Item 34. The method according to any of the previous items, wherein the resource availability data comprises calendar data, location data, facility data, accessibility data, and / or policy data.

[0179] Item 35. The method according to any of the previous items, wherein the resource availability data is obtained from a resource system. Item 36. A method, performed by a user device, the method comprising: obtaining a participant input indicative of a resource request; transmitting (S204) the resource request to a server device; obtaining (S206), from the server device, a resource response indicative of a candidate resource; and providing (S208) the resource response.

[0180] The use of the terms “first”, “second”, “third” and “fourth”, “primary”, “secondary”, “tertiary” etc. does not imply any particular order, but are included to identify individual elements. Moreover, the use of the terms “first”, “second”, “third” and “fourth”, “primary”, “secondary”, “tertiary” etc. does not denote any order or importance, but rather the terms “first”, “second”, “third” and “fourth”, “primary”, “secondary”, “tertiary” etc. are used to distinguish one element from another. Note that the words “first”, “second”, “third” and “fourth”, “primary”, “secondary”, “tertiary” etc. are used here and elsewhere for labelling purposes only and are not intended to denote any specific spatial or temporal ordering. Furthermore, the labelling of a first element does not imply the presence of a second element and vice versa.

[0181] It may be appreciated that Figures 1-5 comprise some circuitries or operations which are illustrated with a solid line and some circuitries, components, features, or operations which are illustrated with a dashed line. Circuitries or operations which are comprised in a solid line are circuitries, components, features, or operations which are comprised in the broadest example. Circuitries, components, features, or operations which are comprised in a dashed line are examples which may be comprised in, or a part of, or are further circuitries, components, features, or operations which may be taken in addition to circuitries, components, features, or operations of the solid line examples. It should be appreciated that these operations need not be performed in order presented. Furthermore, it should be appreciated that not all of the operations need to be performed. The example operations may be performed in any order and in any combination. It should be appreciated that these operations need not be performed in order presented. Circuitries, components, features, or operations which are comprised in a dashed line may be considered optional.

[0182] Other operations that are not described herein can be incorporated in the example operations. For example, one or more additional operations can be performed before, after, simultaneously, or between any of the described operations. Certain features discussed above as separate implementations can also be implemented in combination as a single implementation. Conversely, features described as a single implementation can also be implemented in multiple implementations separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations, one or more features from a claimed combination can, in some cases, be excised from the combination, and the combination may be claimed as any sub-combination or variation of any sub-combination.

[0183] It is to be noted that the word "comprising" does not necessarily exclude the presence of other elements or steps than those listed.

[0184] It is to be noted that the words "a" or "an" preceding an element do not exclude the presence of a plurality of such elements.

[0185] It is to be noted that the term "indicative of may be seen as “associated with”, “related to”, “descriptive of’, “characterizing”, and / or “defining”. The terms “indicative of”, “associated with”, “related to”, “descriptive of’, “characterizing”, and “defining” can be used interchangeably. The term “indicative of” can be seen as indicating a relation. For example, weight data indicative of weight may comprise one or more weight parameters.

[0186] It is to be noted that the word "based on" may be seen as “as a function of” and / or “derived from”. The terms “based on” and “as a function of’ can be used interchangeably. For example, a parameter determined “based on” a data set can be seen as a parameter determined “as a function of” the data set. In other words, the parameter may be an output of one or more functions with the data set as an input.

[0187] A function may be characterizing a relation between an input and an output, such as mathematical relation, a database relation, a hardware relation, logical relation, and / or other suitable relations.

[0188] It should further be noted that any reference signs do not limit the scope of the claims, that the examples may be implemented at least in part by means of both hardware and software, and that several "means", "units" or "devices" may be represented by the same item of hardware. Language of degree used herein, such as the terms “approximately,” “about,” “generally,” and “substantially” as used herein represent a value, amount, or characteristic close to the stated value, amount, or characteristic that still performs a desired function or achieves a desired result. For example, the terms “approximately”, “about”, “generally,” and “substantially” may refer to an amount that is within less than or equal to 10% of, within less than or equal to 5% of, within less than or equal to 1% of, within less than or equal to 0.1 % of, and within less than or equal to 0.01% of the stated amount. The various example methods, devices, nodes, and systems described herein are described in the general context of method steps or processes, which may be implemented in one aspect by a computer program product, embodied in a computer-readable medium, including computerexecutable instructions, such as program code, executed by computers in networked environments. A computer-readable medium may include removable and non-removable storage devices including, but not limited to, Read Only Memory (ROM), Random Access Memory (RAM), compact discs (CDs), digital versatile discs (DVD), etc. Generally, program circuitries may include routines, programs, objects, components, data structures, etc. that perform specified tasks or implement specific abstract data types. Computer-executable instructions, associated data structures, and program circuitries represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps or processes.

[0189] Although features have been shown and described, it will be understood that they are not intended to limit the claimed disclosure, and it will be made obvious to those skilled in the art that various changes and modifications may be made without departing from the scope of the claimed disclosure. The specification and drawings are, accordingly, to be regarded in an illustrative rather than restrictive sense. The claimed disclosure is intended to cover all alternatives, modifications, and equivalents.

Claims

CLAIMS1 . A server device, comprising memory circuitry, processor circuitry, and an interface, wherein the server device is configured to: receive a resource request from a user device, the resource request comprising resource request data associated with an event, wherein the resource request data comprises a time parameter indicative of a tolerance margin associated with a timing of the event; obtain, based on the resource request data, resource availability data associated with an availability of one or more resources; determine, based on the resource request data and the resource availability data, a resource response indicative of a candidate resource; and transmit, to the user device, the resource response.

2. The server device according to claim 1 , wherein the resource request data comprises time data, event data, and / or participant data associated with one or more requested participants.

3. The server device according to any of the previous claims, wherein the server device is configured to: obtain, in response to the transmittal of the resource response to the user device, a participant input.

4. The server device according to any of the previous claims, wherein the server device is configured to generate, based on the resource request data and the resource availability data, event data associated with the event.

5. The server device according to any of claims 3-4, wherein the server device is configured to determine whether a participant input is received.

6. The server device according to claim 5, wherein the server device is configured to, upon determining that the participant input is not received:obtain historical participant data associated with a participant profile, wherein the participant profile is associated with one of the one or more requested participants; determine, based on the historical participant data, an attendance parameter, wherein the attendance parameter is indicative of a probability of the participant associated with the participant profile attending the event, and wherein the attendance parameter is determined by applying a probabilistic rule; and update the event data based on the attendance parameter.

7. The server device according to claim 6, wherein the probabilistic rule is a Bayes’ rule.

8. The server device according to any of the previous claims, wherein the determination of the resource response comprises determining, based on the time parameter, the resource response.

9. The server device according to claim 1 , wherein the determination of the resource response comprises determining whether the candidate resource satisfies one or more criteria.

10. The server device according to claim 9, wherein the one or more criteria are based on one or more respective thresholds.11 . The server device according to any of the previous claims, wherein the server device is configured to assign, for a first time period, a resource as the candidate resource.

12. The server device according to claim 11 , wherein the server device is configured to update, upon an expiry of the first time period, the assignment of the resource as the candidate resource.

13. The server device according to claim 12, wherein the server device is configured to update, upon the expiry of the first time period, the assignment of the resource as the candidate resource by confirming and / or modifying the assignment.

14. The server device according to any of items claim 12-13, wherein the server device configured to: receive an updated resource request from the user device; and update the assignment based on the updated resource request.

15. The server device according to any of the previous claims, wherein the server device is configured to generate and transmit notification information based on the participant data.

16. The server device according to any of the previous claims, wherein the resource availability data comprises calendar data, location data, facility data, accessibility data, and / or policy data.

17. The server device according to any of the previous claims, wherein the resource availability data is obtained from a resource system.

18. A user device comprising memory circuitry, processor circuitry, and an interface, wherein the user device is configured to: obtain a participant input indicative of a resource request; transmit the resource request to a server device; obtain, from the server device, a resource response indicative of a candidate resource; and provide the resource response.

19. A method, performed by a server device, for the assignment of resources, the method comprising: receiving a resource request from a user device, the resource request comprising resource request data associated with an event, wherein theresource request data comprises a time parameter indicative of a tolerance margin associated with a timing of the event; obtaining, based on the resource request data, resource availability data associated with an availability of one or more resources; - determining, based on the resource request data and the resource availability data, a resource response indicative of a candidate resource; and transmitting, to the user device, the resource response.

20. The method according to claim 19, wherein the resource request data comprises time data, event data, and / or participant data associated with one or more requested participants.

Images