IT202100019313A1 - PROVISION OF SERVICES THROUGH USERS' PERSONAL IDENTIFIERS - Google Patents

Description

DESCRIPTION

Technical field

The present invention refers to the data processing sector. Pi? specifically, the present invention relates to the provision of services.

Technological context

The technological context of the present invention will be? discussed below. In any case, even if this discussion concerns techniques found in documents, deeds and/or artefacts, it is not? intended to suggest or acknowledge that such techniques are to be considered part of the state of the art and/or general knowledge in the sector for the purposes of the present invention.

The provision of services (for example, shows, visits, travel, and payments) ? typically subject to the purchase of corresponding tickets.

Tickets can be purchased on site (requiring dedicated staff and facilities for issuing and checking tickets, as well as determining possible queues), or online.

In the case of tickets purchased online, printing may be required. Anyway, there? does it require availability? of the relative equipment or, in the case of printing by means of ticket offices or self-service workstations, appropriate procedures for recovering tickets using identifying information (for example, credit card number used for the purchase, e-mail address provided at the of the purchase, names of the people for whom the tickets were purchased).

In the case of tickets purchased online, they could be issued in electronic format, for example in order to be stored on a mobile device (for example, a smartphone), or be replaced by corresponding booking codes. In any case, electronic tickets or related booking codes, in addition to requiring dedicated personnel to read them, require a certain degree of confidence in the use of the mobile device, and present a certain degree of volatility. (indeed, e-tickets and booking codes can be lost, for example as accidentally deleted, or not accessible, for example as the mobile device has a flat battery or no connection to the cellular network).

In addition, for some categories of services, such as services with variable tariffs (that is, services whose tariff depends on variables such as duration and delivery area), typical of services such as travel by local public transport, the purchase of the corresponding tickets it requires a certain knowledge of the pricing systems to which these services are subject (for example, in some cities there is a pricing system based on local public transport zones); therefore, since the purchase of tickets for these categories of services is difficult for a significant number of users, it is? it is often necessary to contact dedicated personnel (with inevitably longer purchase times).

Summary

A simplified summary of the present invention ? presented here in order to provide a basic understanding thereof; however, the sole purpose of this summary is to introduce some concepts of the invention in a simplified form as a prelude to its following description more? detailed, isn't it ? to be interpreted as a? identification of its key elements n? as a delimitation of its scope.

In general terms, the present invention ? based on the idea of using the personal identification of users to provide services.

In particular, one aspect of the present invention provides a method for dispensing one or more services. The method comprises storing, in a control processing system, the personal identifiers of registered users; read, to the control processing system, the personal identifier of a requesting user from an identification tool of the requesting user; authorize the provision of the service to the requesting user in response to the presence of the requesting user?s personal identifier in the personal identifiers stored in the control processing system; charge an amount for the service provided on a payment instrument associated with the personal identification of the requesting user.

A further aspect provides a computer program (software) for implementing the method.

An additional aspect provides a corresponding software program product. A further aspect provides a corresponding system.

Pi? specifically, one or more aspects of the present invention are indicated in the independent claims and advantageous features thereof are indicated in the dependent claims, with the text of all the claims incorporated herein by reference (with any beneficial features provided in respect of each specific aspect applying mutatis mutandis to every other aspect).

Brief description of the figures

The present invention, as well as further features and their relative advantages, will be better understood with reference to the following detailed description, provided purely for indicative and non-limiting purposes, to be read in conjunction with the attached figures (in which, for simplicity?, corresponding elements are indicated with the same or similar references and their explanation is not repeated, and the name of each entity is generally used to indicate both its type and its attributes, such as value, content and representation). In particular:

Figure 1 shows a basic block diagram of an infrastructure according to an embodiment of the present invention;

Figure 2 shows the main hardware components of infrastructure processing apparatuses, according to an embodiment of the present invention;

Figure 3 shows the main software components of infrastructure processing apparatuses, according to an embodiment of the present invention;

Figures 4A-4G show an exemplary service management application scenario, in accordance with an embodiment of the present invention;

Figures 5A-5L show an exemplary service management application scenario, in accordance with another embodiment of the present invention, and Figure 6 shows an activity diagram of a service delivery method in accordance with an embodiment of the present invention.

Detailed description of preferred embodiments of the present invention Figure 1 shows a block diagram of principle of an infrastructure 100 according to an embodiment of the present invention.

In the following, when one or more? characteristics are introduced by the wording ?in accordance with an embodiment?, are they to be understood as additional or alternative characteristics to those previously introduced, unless otherwise indicated and/or unless manifestly incompatible? between combinations of features.

In accordance with an embodiment, the infrastructure 100 comprises a management processing system (hereinafter, management system) 105, for example a data processing center (?data center?), able to manage a multiple? services. Examples of services that may be managed by the 105 management system include, but are not limited to, entertainment (e.g., concerts, sporting events, movie screenings, and theater performances), visits (e.g., museums, exhibits, and trade shows), and travel (for example, travel on the motorway network, or travel by local public transport).

In accordance with one embodiment, the management system 105 reports to a management organization. The management organization can be a delivery organization that delivers the services, a marketing organization that markets the services on behalf of the delivery organization, or a support organization that supports the delivery organization and/or the marketing organization.

In accordance with one embodiment, the management system 105 is act to manage functionality? such as user registration (such as user U1 shown in the figure) and, for each registered user, modification of a user profile (for example, enabling or disabling a service of interest (or more services of interest) among the managed services from the management system 105, and/or modification of one or more payment instruments associated with the registered user, and/or access to a personal area of the registered user (for example, in order to view or consult a history of services provided and/or amounts charged).

In accordance with one embodiment, a registration request can be submitted by the user U1 through one or more? recording channels (?touchpoints?). In accordance with one embodiment, such registration channels also allow the access of registered users to their respective user profiles (for example, so as to make changes thereto).

As conceptually represented in the figure, examples of recording channels include, but are not limited to, user computing devices, such as a smartphone 110A or a personal computer 110B, physical exercises supervised by operators 110C, and physical self-service stations ( such as kiosks or totems) 110D.

In accordance with one embodiment, each recording channel ? communicatively coupled to the management system 105 to allow the user U1 to submit the registration request. In accordance with one embodiment, each recording channel ? communicatively coupled to the management system 105 via a telecommunications network 115, such as an Internet-based telecommunications network.

In accordance with one embodiment, for registration purposes, user U1 ? requested to provide a personal identifier of the U1 user, for example the U1 user?s tax code or other personal identifier capable of uniquely identifying the U1 user.

In accordance with one embodiment, the mode? with which the user U1 can? providing the tax code (or other personal identification) depends on the registration channel used for submitting the registration request. By way of example, in the event of submission of the registration request made autonomously by the user U1 through the user's computing devices U1 or through physical self-service workstations, ? It is possible to provide for the insertion of the tax code (or other personal identification) by the U1 user manually (that is, by personally typing his tax code in a corresponding fillable field of an electronic registration form). By way of further example, in the event of submission of the registration request made through physical exercises supervised by operators or through advanced self-service physical workstations, ? It is possible to provide for the acquisition of the tax code (or other personal identification) automatically, for example by reading an identification instrument 120 of the user U1.

In accordance with one embodiment, the identification tool 120 of the user U1 comprises an identification document issued by an authority of certification that certifies a? identity? of user U1. Without losing generality?, the? authority? certification can? be a public body or a private body (for example, a company or a studio). By way of non-limiting example, the? Authority? certification can? for example being a municipality of residence of user U1.

In accordance with an embodiment, the identification tool 120 of the user U1 comprises a smart card (Smart-Card), i.e. an integrated circuit (typically incorporated in a support of plastic material in the shape of a bank card) capable of memorizing in secure form (for example, via digital signature) the U1 user?s identification information, including his tax code (or other personal identification), and whose reading (for example, in order to obtain the U1 user?s identification information memorized) takes place through a suitable Smart-Card reader.

In accordance with one embodiment, the identification tool 120 is non-contact type, for example in ?Near-Field Communication? (NFC), for which the reading of the corresponding identification information of the user U1 stored in it can? take place in mode non-contact (for example, by placing the identification instrument 120 near a non-contact type operating base, for example a non-contact type Smart-Card reader).

In accordance with one embodiment, the identification tool 120 of the user U1 comprises an identity card user?s electronics U1. In accordance with one embodiment, the identification tool 120 of the user U1 comprises an electronic card of the user U1 (for example, a health card or a driver's license) equipped with functionalities of strong authentication to digital services.

According to one embodiment, user U1 ? required to enable one or more? services among the services managed by the management system 105. In accordance with an embodiment, the enabling of the services by the user U1 can? be carried out during registration and/or after it (for example, in a phase of modification of the user profile).

In accordance with one embodiment, for registration purposes, user U1 ? requested to provide identification data of a payment instrument 125 (or more payment instruments) from which to debit the amount relating to the services provided to the user U1. Examples of payment instrument 125 include, but are not limited to, credit/debit cards and bank checking accounts.

In accordance with one embodiment, in the event that the payment instrument 125 comprises a credit/debit card, the identification data of the payment instrument 125 may comprise the PAN code (?Primary Account Number?) present on the front of the card credit/debit card and uniquely identifying it.

In accordance with one embodiment, in the event that the payment instrument 125 comprises a bank current account, the identification data of the payment instrument 125 may comprise the IBAN code (?International Bank Account Number?) identifying the bank current account in uniquely.

In accordance with one embodiment, user U1 can? be allowed to provide identification data of a plurality? of (for example, two or more?) payment instruments from which to charge the amount relating to the services provided.

According to one embodiment, in case of enabling a plurality? of services among the services managed by the management system 105, and in the event that the user U1 provides identification data of a plurality? of payment instruments, the user U1 can? be allowed to associate each payment instrument (or each group of payment instruments) to one or more? respective enabled services (or groups of enabled services). In this way, the charge of the amount relating to each service provided (or to each group of services provided) can take place on the respective payment instrument (or group of payment instruments).

According to one embodiment, in case the user U1 provides identification data of a plurality? of payment instruments, the user U1 can? be required to set up a default payment instrument and/or payment instrument preference order. In this way, the charge of the amount relating to the services provided can take place on the default payment instrument and/or on the first payment instrument which, according to the order of preference set, is available? of funds.

According to one embodiment, one or more? User U1's payment instruments may be shared with (i.e. further associated with) one or more additional users registered in the 105 management system (for example, in order to centralize the amounts of services provided to different registered users who are members of the same family unit or a group of acquaintances).

In accordance with an embodiment, the infrastructure 100 comprises a virtual acceptance system 130, for example a virtual POS terminal (?Point Of Sale?), for entering the data relating to the payment instrument 125 of the user U1 .

In accordance with one embodiment, each recording channel ? communicatively coupled to the virtual acceptance system 130 (to allow the user U1 to supply the data relating to the payment instrument 125 of the user U1). In accordance with one embodiment, each recording channel ? communicatively coupled to the virtual acceptance system 130 via the telecommunications network 115 (or, alternatively, via a different telecommunications network).

In accordance with one embodiment, the mode? with which the user U1 can? providing the identification data of the payment instrument to the virtual acceptance system 130 depends on the registration channel used for submitting the registration request. By way of example, in the event of submission of the registration request made autonomously by the user U1 through the user's computing devices or through physical self-service workstations, ? It is possible to provide for the user U1 to enter the identification data of the payment instrument manually (that is, by personally entering the identification data of the payment instrument in a corresponding fillable field on a web page of the virtual acceptance system 130 to which the ?user U1 is addressed during the registration procedure). By way of further example, in the event of submission of the registration request made through physical exercises supervised by operators or through advanced self-service physical workstations, ? It is possible to envisage the acquisition of the identification data of the payment instrument automatically, for example by reading the payment instrument 125 by a physical acceptance system, for example a physical POS terminal, and the subsequent transmission of the identification data acquired by the physical check-in system to the virtual check-in system 130.

In accordance with an embodiment, the infrastructure 100 comprises a payment authorization system 135 (typically managed by a subject, called an ?acquirer?, authorized to interface with the payment circuits) to perform verification/authorization procedures of the (or of each) payment instrument 125 and for debiting the amounts relating to the services provided.

In accordance with one embodiment, during the registration phase, the virtual check-in system 130 is communicatively coupled to the payment authorization system 135 to carry out an authorization transaction of the payment instrument based on the identification data of the payment instrument 125 acquired to the virtual acceptance system 130. In accordance with one embodiment, such an authorization transaction can? for example, provide for the use of an appropriate security protocol (such as the ?3-D Secure? protocol).

In accordance with one embodiment, in the event of a positive outcome of the authorization transaction, the management system 105 ? configured to store (for example, in the management system 105 or in a storage system external to it, not shown) the personal identifier of the user U1 in association with the payment instrument 125 (that is, the identification data of the payment instrument payment). There? decrees the registration of user U1 with the 105 management system (and the association of user U1 with one or more enabled services).

In accordance with one embodiment, the management system 105 is configured to memorize, for each of the users registered with the 105 management system, an association of personal identification / payment instrument (that is, the personal identification of the user registered with the 105 management system in association with one or more instruments payment methods provided by the registered user).

In accordance with one embodiment, for each of the registered users (i.e., for each of the registered users' personal identifiers), the management system 105 ? configured to memorize an indication of the corresponding enabled services (if present, or if this registered user has requested the enabling of one or more services of his/her interest among the services managed by the management system 105).

In accordance with an alternative embodiment, the management system 105 is configured to memorize the personal identification / payment instrument association for each service managed by the management system 105 (that is, with each of the services managed by the management system 105 which is associated with a respective plurality of personal identification / payment instrument associations ).

In accordance with one embodiment, the management system 105 is configured to store an exclusion of each of the registered users (for example, in response to a failure of one or more of the corresponding charges, as better discussed below).

In accordance with one embodiment, the management system 105 is configured to store a reinstatement of each of the excluded registered users (for example, in response to a failed payment of the corresponding charges, as further discussed below).

In accordance with one embodiment, the management system 105 is further suitable for managing the delivery of the services managed by it to requesting users (such as the requesting user U2 illustrated in the figure).

For this purpose, in accordance with one embodiment, the infrastructure 100 comprises, for each of the services managed by the management system 105, a control processing system 140 (hereinafter, control system) communicatively coupled to the management system 105 In accordance with one embodiment, the infrastructure 100 comprises, for each of the services managed by the management system 105, a plurality of services. of control systems, each structurally and functionally implemented on the basis of specificity? of the corresponding service.

In accordance with an embodiment, the control system 140 comprises an access control system to a protected area suitable for providing the corresponding service. In accordance with one embodiment, the control system 140 is placed in correspondence with the protected area (for example, externally or internally) in order to regulate and control the flow of incoming and/or outgoing users. Without losing generality, as illustrated by way of example in the figure, the control system 140 can include a turnstile (for example, a turnstile placed in a subway station), a validator (for example, a validator installed on a local public transport vehicle such as a bus or a tram), or a digital assistant (for example, an assistant supplied to the control personnel in charge of the control near and/or inside the protected area).

In accordance with one embodiment, the control system 140 comprises (or is associated with) a smart-card reader 140SC. In accordance with one embodiment, as discussed below, the Smart-Card reader 140SC is configured to read the identification tool 120 (for example, the electronic identity card) of the requesting user U2, in order to obtain the personal identification (for example, the tax code) of the requesting user U2. In accordance with an embodiment, as better discussed below, based on the personal identification of the requesting user U2 read by the Smart-Card reader 140SC, the control system 140 ? configured to authorize (or not authorize) the requesting user U2 to provide the corresponding (requested) service. In the continuation of the present description, by authorization by the control system 140 to supply the corresponding service we mean the execution of one or more actions aimed at communicating or signaling the legitimacy? of the requesting user U2 to the provision of the corresponding service. For example, in the event that the control system 140 comprises a turnstile, these actions may include hindering entry to the protected area to unregistered users (or registered users not authorized to provide the corresponding service) and allowing access to the protected area. entry and/or exit of one registered user enabled at a time. For example, if the control system 140 includes a validator, these actions may include emitting differentiated acoustic and/or light signals for unregistered users (or for registered users who are not enabled to provide the corresponding service) and for registered users . For example, in the case where the control system 140 includes a digital assistant of the control personnel, such actions may include displaying a message (e.g., a text message or in code form intended for the control personnel) differentiated for users not registered (or for registered users who are not authorized to provide the corresponding service) and for registered users.

In accordance with an embodiment, the reading of the identification tool 120 of the requesting user U2 comprises a validation step of the personal data of the requesting user U2 contained therein (including the personal identification of the requesting user U2), in so as to ascertain that the personal data have actually been provided by the? authority? certification (ie, their authenticity?) and have not been corrupted (ie, their integrity?). Without losing generality, this validation phase can? understand verify authenticity and integrity of the personal identifier read by the identification device 120 in accordance with digital certificates, cryptographic hash functions, and/or encryption algorithms.

In accordance with embodiments, such authentication verification? and integrity of the personal identifier read by the identification device 120 ? performed locally by the control system: in these embodiments, the validation phase can? understand recover (by the control system) a digital certificate of? authority? certificate stored in the control system. In accordance with alternative embodiments, not shown, such authentication verification and integrity of the personal identifier read by the identification device 120 ? performed by a verification system external to the control system 140 (this external verification system including, for example, the certification authority responsible for issuing the identification tool 120): in these embodiments, the phase validation can? include interrogating (by the control system) the verification system in real time (e.g. via a dedicated communication channel).

According to one embodiment, the validation step can? understand acquire (by the control system) one or more? biometric data of the person (for example, one or more photographs, fingerprints, and / or representation of the iris). According to one embodiment, the validation step can? understand verify (by the control system) the?identity? of the person in accordance with a comparison between the captured biometric data and corresponding biometric data stored on the identification tool. According to embodiments, the identity? of the person can? be verified by cognitive techniques in accordance with the biometric data stored in the identification tool.

By way of a further example, this validation phase can? be carried out on the basis of one or more? security codes associated with the identification tool and/or biometric data of the corresponding user.

In accordance with one embodiment, the management system 105 is configured to distribute to each control system (such as to the control system 140), through the corresponding communication link, the personal identifiers of the registered users for storage thereof in each control system.

For this purpose, the 105 management system can be configured to distribute to each control system the personal identifiers of only the registered users authorized to provide the corresponding service, or can the management system 105? be configured to distribute to each control system the personal identifiers of registered users (that is, of all users registered with the management system 105) each in association with the indication of the corresponding enabled services.

In accordance with one embodiment, the management system 105 is configured to distribute to each control system (such as to the control system 140), through the corresponding communication coupling, the personal identifiers of the excluded registered users (e.g., excluded in response to a failure of one or more of the corresponding charges) for their removal from each control system.

In accordance with one embodiment, the management system 105 is configured to distribute to each control system (such as to the control system 140), through the corresponding communication coupling, the personal identifiers of the replenished registered users (e.g., replenished in response to a failed payment of the corresponding charges) for storage in each control system.

In accordance with one embodiment, as further discussed below, the control system 140 is configured to authorize (or not authorize) the requesting user U2 to provide the corresponding service (requested) in response to the presence of the personal identification of the requesting user U2 (read by the 140SC Smart-Card reader) in the personal identifications stored in the control system 140 (and, possibly, in response to the presence of the indication of the requested service among the enabled services associated with the personal identification of the requesting user U2).

In accordance with one embodiment, the control system 140 is configured to transmit to the management system, through the corresponding communication coupling, an indication of the service provided and an indication of the personal identification of the requesting user U2, for example in order to start (by the management system 105) a procedure for calculating the amount of the service provided and charging the same to the payment instrument associated with the personal identifier of the requesting user U2 (as better discussed below).

In accordance with one embodiment, the indication of the personal identifier of the requesting user can include a personal identifier alias (for example, a string of text or symbol associated with the personal identifier), or a string encrypted using a cryptographic hash function. In the following, transmission of the personal identification of the requesting user U2 means the dual possibility implementation of direct transmission of the personal identifier (that is, transmission of the personal identifier as it is), or indirect transmission of the personal identifier (that is, transmission of the indication of the personal identifier).

As mentioned earlier, the 105 management system can be implemented through a data processing system (?data center?). In accordance with one embodiment, the data processing system can understand a plurality of servers (for example, rack or blade type), a plurality? of storage disks (for example of the RAID type) which implement mass memories, a console for its control, and a switch/router subsystem to manage communications between the servers, the disks and the console, and a communications network; for this purpose the servers, the disks and the console can be connected to the switch/router subsystem (for example, by means of corresponding network adapters) via a cabling subsystem.

Figure 2 shows, in accordance with an embodiment of the present invention, the main hardware components of each server of the management system 105, of the identification tool 120, and of the control systems 140 (which will be referred to collectively below). as processing equipment).

In accordance with one embodiment, each processing apparatus comprises one or more? microprocessors 205 adapted to control the operation of the processing apparatus.

In accordance with one embodiment, each processing apparatus comprises a non-volatile memory (for example, a ROM memory) 210 suitable for storing a base code for starting the processing apparatus.

In accordance with one embodiment, each processing apparatus comprises a volatile memory (for example, a RAM memory) 215 suitable for being used as working memory by the microprocessors 205.

In accordance with one embodiment, each processing apparatus comprises a mass memory 220 for storing programs and data. By way of example, the mass memory 220 of the management system 105 can include one or more hard drives. By way of further example, the mass memory 220 of the control system 140 and of the identification instrument 120 can understand one or more flash memories E<2>PROM.

In accordance with one embodiment, each processing apparatus comprises one or more? input/output devices (hereinafter, I/O devices) 225.

By way of example, the I/O peripherals 225 of the management system 105 can comprise a network card for communication of the processing apparatus with the telecommunications network.

By way of example, the I/O peripherals 225 of the control system 140 may comprise (according to their function) a proximity module? (active) for communication with the identification tool 120, a network card (NIC) for communication with the telecommunications network, a display, a light and/or acoustic signaller, a camera, and an interface module for ?interfacing between the control system 140 and the Smart-Card reader 140SC associated therewith.

By way of example, the I/O peripherals 235 of the identification tool 120 may comprise a battery of contacts for connection to physical contact operating bases and a proximity module for communication with non-contact operating bases, the identification instrument integrated circuit 120 being, for example, powered by the contact operating bases (for example, through the battery of contacts) or by the non-contact operating bases (for example, through a ?proximity module antenna suitable for transforming radio signals into electrical energy by induction).

In accordance with an embodiment, each processing apparatus comprises a communication bus 230 to allow a communication (for example, a two-way communication) between the microprocessors 205, the non-volatile memory 210, the volatile memory 215, the mass memory 220 , and 225 I/O devices.

Figure 3 shows the (main) software components of each processing apparatus, according to an embodiment of the present invention.

In accordance with one embodiment, these software components are stored in the mass memory and loaded (at least in part) into the working memory of each processing apparatus when the programs are running. The programs are initially installed on the mass memory, for example, from units? removable storage or from the Internet. In this regard, each program can? represent a module, segment or portion of code, which includes one or more? executable statements to implement the specified logical function.

In accordance with an embodiment, the software components of the management system 105 comprise a services database 305 suitable for storing information relating to registered users. In accordance with one embodiment, the service database 305 ? designed to memorize, for each of the registered users, a personal identification / payment instrument association (that is, the personal identification of the user registered with the 105 management system in association with one or more payment instruments provided by the user registered). In accordance with one embodiment, the service database 305 ? designed to memorize, for each of the registered users (that is, for each of the personal identifiers of the registered users), the indication of the corresponding enabled services. In accordance with an alternative embodiment, the service database 305 ? designed to memorize the personal identification / payment instrument association for each service managed by the 105 management system.

For example, the services 305 database can? include an entry for the personal identifier (for example, the tax code) of each registered user and for the payment instruments associated with it. The voice can further include personal data of the registered user (for example, name, date and place of birth) and corresponding operational information (such as password, e-mail address, telephone number).

In accordance with one embodiment, the service database 305 ? further suitable for memorizing, for each registered user, any service provision notifications and any booking amounts charged.

In accordance with an embodiment, the software components of the management system 105 comprise an external interface 310 suitable for receiving registration requests and/or user profile modification requests (for example, enabling or disabling one or more - services among the services managed by the management system 105, and/or modification of one or more payment instruments associated with registered users). In accordance with one embodiment, the external interface 310 accesses (in reading/writing) the services database 305.

In accordance with one embodiment, the software components of the management system 105 include an accounting manager? 315 suitable for determining the amounts relating to the services provided and arranging the charges in the payment authorization system 135. In accordance with one embodiment, the accounting manager? 315 accesses (in reading/writing) the services database 305. In accordance with an embodiment, not shown, the accounting manager? 315 (or other software component of the management system) ? configured to interface with an external accounting system (for example, external to the management system 105) capable of determining the amounts relating to the services provided.

In accordance with an embodiment, the software components of the management system 105 comprise a service manager 320 able to manage the services provided to registered users. For example, the service manager 320 ? capable of receiving, from the control systems, notifications relating to the respective services provided, ? suitable for notifying, for example to the personal devices of registered users, the results of the procedures for charging the amounts relating to the services provided, and ? suitable for updating the 305 services database (for example, storing in it the users excluded following failed debit procedures and/or the users excluded subsequently reinstated). In accordance with one embodiment, the service manager 320 ? capable of accessing (reading/writing) the database services 305 and the accounting manager? 315.

In accordance with one embodiment, the software components of the control system 140 comprise a user database 325 capable of storing the personal identifiers (for example, tax codes) of registered users for whom the service controlled by the control system 140 is? enabled (or, alternatively, the personal identifiers of users registered with the 105 management system in association with the indication of the respective enabled services).

In accordance with one embodiment, the software components of the control system 140 include a proximity controller? 330 act to control the proximity module? of the Smart-Card reader (for example, in order to read the identification tool of the requesting user and determine from it the personal identification of the requesting user).

In accordance with one embodiment, the software components of the control system 140 comprise an operations controller 335 adapted to control the execution of the operations (for example, in the case in which the control system 140 comprises a turnstile, controlling the opening or the closing of the turnstile in accordance with the result of the authorisation).

In accordance with an embodiment, the software components of the control system 140 comprise an authorization agent 340 suitable for managing the authorizations for the provision of services. In accordance with one embodiment, the authorization agent 340 is capable of interacting with the proximity controller? 330 (for example, in order to receive the personal identification of the requesting user read by the Smart-Card reader), with the user database 325 (for example, in order to verify if the personal identification of the requesting user corresponds to a user registered in the management system 105 and the requested service is one of the enabled services associated with the requesting user), with the operations controller 335 (for example, in order to control the opening or closing of the turnstile in accordance with the outcome of the authorization), and with the service manager 320 of the management system 105 (for example, to send it the notifications relating to the respective services provided, or to the authorizations granted).

In accordance with one embodiment, the software components of the identification tool 120 include a proximity controller? 345 act to control the module of proximity? of the identification tool 120.

In accordance with an embodiment, the software components of the identification instrument 120 comprise a security module 350 suitable for implementing a security protocol for dialogue with the operating bases. In accordance with one embodiment, the security module 350 ? suitable for carrying out the validation phase (discussed above) of the personal data of the requesting user U2 contained in the identification tool 120 (as previously mentioned).

In accordance with an embodiment, the software components of the identification tool 120 comprise a data structure 355 suitable for storing personal data of the person, including the personal identification of the requesting user.

Figures 4A-4G show an exemplary service management application scenario, according to an embodiment of the present invention.

In the illustrated embodiment, the requesting user U2 submits a service request to perform an activity, for example attending a show such as a cinema screening.

For this purpose, the requesting user U2 approaches the control system 140 (for example, a turnstile) which controls access to the cinema hall, and arranges for the reading of his own identification tool 120 (for example, his own credit card electronic identity), for example by placing one's own identification tool 120 near the of the Smart-Card reader 140SC associated with the control system 140 (Figure 4A).

In accordance with an embodiment, if the personal identification of the requesting user U2 (read by the Smart-Card reader 140SC) is ? present in the personal identifiers memorized in the control system 140, the control system 140 authorizes the requesting user U2 to provide the service (Figure 4B), for example by opening the turnstile to allow the requesting user U2 to access the headquarters? activity? (for example, the movie theater).

In accordance with one embodiment, if the personal identifier of the requesting user U2 is not ? present in the personal identifiers memorized in the control system 140 (for example, since the requesting user U2 is not entitled to access the place of business), the control system 140 does not authorize the requesting user U2 to disburse the service, for example by keeping the turnstile closed in order to prevent the requesting user U2 from accessing the place of business.

In accordance with one embodiment, the requesting user U2 is not? authorized to access the headquarters of? activity? as the requesting user U2 is not ? registered with the management system 105: there? can? be the case of, for example, a failure to register the requesting user U2, or a subsequent exclusion of the user (for example, as mentioned above, an exclusion or cancellation of the user from the list of registered users carried out by management system 105 as a result of one or more previous failed debit procedures).

In accordance with an alternative embodiment, the requesting user U2 is not? authorized to access the headquarters of? activity? as the requesting user U2 ? registered with the 105 management system, but the requested service is not? one of the enabled services associated with the requesting user U2: what? can? be the case of, for example, a failure to enable the requested service by the requesting user U2, or its subsequent disabling.

The provision of the service therefore takes place in a very simple way, being it based on the personal identification of the user acquired immediately through an identification tool (for example, the identity card) that people have (or should have) usually with s? (for example, for security reasons).

Furthermore, the provision of the service takes place without requiring the burden of any additional device, and without performing other actions necessary in the prior art (for example, providing a credit card, ticket, or reservation code).

In addition, the provision of the service takes place without the corresponding authorization by the control system involving communications between the control system and the management system (since the personal identifiers of registered users who are enabled for the corresponding service are stored locally in the control system), thus avoiding slowdowns that could compromise the provision of the service in (practical) scenarios of high user flows.

In accordance with an embodiment, following the authorization of the requesting user U2 for the provision of the service by the control system 140, the control system 140 ? configured to transmit or notify the management system 105, through the corresponding communication coupling, an indication of the service provided and the personal identification of the requesting user U2, preferably the indication of the personal identification of the requesting user U2 (Figure 4C) . The instant of notification time, following the authorization of the requesting user U2 to provide the service, in which such transmission or notification occurs? carried out can? be chosen on the basis of specific design criteria; for example, the instant notification time can? be determined so as to make data traffic efficient in the communication coupling between the control system 140 and the management system 105.

In accordance with one embodiment, the control system 140 is configured to transmit or notify the management system 105, in addition to the indication of the service provided and the personal identification of the requesting user U2, a time information of the provision of the service (for example, a time stamp). There? can? be advantageous in embodiments, discussed below, in which the amount of the service provided depends on an interval of time between a start or start of the service delivery and a termination of the service delivery (for example, in the case of services at variable rates).

In accordance with one embodiment, the management system 105 is configured to determine, on the basis of the indication of the service provided notified to it by the control system 140, and on the basis of a tariff of the service provided (for example, available from the management system 105), the amount of the service provided ( Figure 4D).

As mentioned above, in some embodiments (for example, for certain types of services) the amount of the service provided can be further based on the time interval between the start of service delivery and the end of service delivery. In these embodiments, the management system 105 can prepare (for example, upon detection of the start of service delivery by the control system 140) a charge of a booking amount (for example, a lump sum or an estimated amount) by the payment authorization system 135 , and determine (for example, upon detection of the end of service provision by the control system 140) the (actual) amount of the service provided on the basis of the booking amount (thus to be prepared by the payment authorization 135 the debit of a balance amount depending on the amount of the service provided and the amount of the reservation).

In accordance with one embodiment, the management system 105 is configured to determine, on the basis of the personal identification of the requesting user U2 notified by the control system 140, and on the basis of the personal identification / payment instrument association stored in the management system 105, the payment instrument 125 associated with the user applicant U2 which ? the service has been provided (and, possibly, the payment instrument associated with the service provided) (Figure 4D).

In accordance with one embodiment, the management system 105 is configured to transmit to the payment authorization system 135, through the corresponding communication coupling, the identification data of the payment instrument 125, preferably an indication of the identification data of the payment instrument 125, and the amount of the service provided to be charged (Figure 4E) . In accordance with one embodiment, the indication of the identification data of the payment instrument 125 can comprise an alias of the identification data of the payment instrument 125 (for example, a string of text or symbol associated with the identification data of the payment instrument 125), or a string encrypted using a cryptographic hash function. In the following, by transmission of the identification data of the payment instrument 125 we mean the double possibility implementation of direct transmission of the identification data of the payment instrument 125 (that is, transmission of the identification data of the payment instrument 125 as such), or indirect transmission of the identification data of the payment instrument 125 (that is, transmission of the indication of the identification data of the payment instrument 125).

As further discussed below, in accordance with one embodiment, the amount of the service provided to be charged can be include a cumulative amount of each service provided during a predetermined period of time to the requesting user U2 (for example, one or more? days): in the example in question, the amount of the service provided to be charged can? include, in addition to the amount to attend the film screening, one or more? additional amounts for additional services provided during the predetermined period of time to the requesting user U2 (these additional services including, for example, transport services to and from the cinema screening venue).

In accordance with an embodiment, in response to a positive result of debiting the amount of the service provided on the payment instrument 125 (or on one of the payment instruments) associated with the requesting user U2 to which ? has the service been provided, and in response to a communication of this outcome from the payment authorization system 135 to the management system 105, the management system 105 ? configured to notify (for example, through the telecommunications network 115) the positive outcome of the transaction to the corresponding user (for example, to one of its processing devices, such as a smartphone 110A or a personal computer 110B), preferably together with a? indication of the amount charged (Figure 4F).

In accordance with one embodiment, in response to a negative result of debiting the amount of the service provided on the payment instrument 125 (or on each payment instrument) associated with the requesting user U2 to which ? has the service been provided, and in response to a communication of this outcome from the payment authorization system 135 to the management system 105, the management system 105 ? configured to memorize an exclusion of that user from registered users and to transmit to the control system the personal identification of the excluded registered user for his removal from the control system (Figure 4G). In the (practical) case in which, for the same service or for further services managed by the management system 105, there are more? control systems, the 105 management system can? be configured to distribute to such monitoring systems (or a subset thereof) the personal identifier of the registered user excluded for his removal from such monitoring systems.

In accordance with an embodiment, in response to the communication from the payment authorization system 135 to the management system 105 of the negative outcome of the charge of the amount of the service provided, and/or in response to the storage (in the management system 105 ) of the exclusion of the user from registered users, and/or in response to the distribution to the control systems of the personal identifiers of the excluded registered users for their removal from the control systems, the management system 105 ? configured to notify (for example, through the telecommunications network 115) the corresponding event to the requesting user U2 (for example, to a processing device thereof, such as a smartphone 110A or a personal computer 110B) (Figure 4G).

In accordance with an embodiment, not shown, if the excluded user subsequently proceeds to pay the amount of the failed debit (or of the failed debits), the management system 105 ? configured to reinstate the excluded user and distribute to the control systems (or to each respective control system) the personal identifier of the reinstated user for its storage in the control systems.

Figures 5A-5L show an exemplary service management application scenario, according to another embodiment of the present invention. In the following, features and advantages discussed with reference to the application scenario of Figures 4A-4G will not be repeated, where not necessary, for the sake of brevity. of exposure.

In the illustrated embodiment, the requesting user U2 submits a service request to perform an activity? at variable fares, for example traveling by local public transport (for example, by metropolitan train). For this purpose, it is assumed that there is a control system 140 (shown in Figures 5A-5C ) which controls entry to the business location. (hereinafter, entry control system), and a control system 140 (shown in Figures 5G-5H) which controls the exit from the site of the business? (hereinafter, output control system).

In order to submit the service request to perform the activity, the requesting user U2 approaches the entrance control system 140 (for example, an entrance turnstile which controls the entrance to the underground station), and arranges the reading of one's identification tool 120 (for example, one's electronic identity card), for example by placing one's identification tool 120 near the of the Smart-Card reader 140SC associated with the control system 140 (Figure 5A).

In accordance with an embodiment, if the personal identification of the requesting user U2 (read by the Smart-Card reader 140SC) is ? present in the personal identifiers stored in the entry control system 140, the entry control system 140 authorizes the requesting user U2 to provide the service (Figure 5B), for example by opening the turnstile to allow the requesting user U2 to access to the headquarters of the activity? (for example, the subway station).

In accordance with one embodiment, if the personal identifier of the requesting user U2 is not ? present in the personal identifiers stored in the entry control system 140 (for example, since the requesting user U2 is not entitled to access the place of business), the entry control system 140 does not authorize the requesting user U2 to the provision of the service, for example by keeping the turnstile closed in order to prevent the requesting user U2 from accessing the place of business.

In accordance with one embodiment, the authorization of the requesting user U2 for the provision of the service decrees the detection of the beginning of the provision of the service (although this is not to be understood in a limiting manner).

In accordance with an embodiment, following the authorization of the requesting user U2 to provide the service by the input control system 140, the input control system 140 ? configured to transmit or notify the management system 105, through the corresponding communication coupling, an indication of the service provided, the personal identification of the requesting user U2, and the time information of the provision of the service (Figure 5C). In alternate embodiments, not shown, such transmission or notification, what is? relating to the detection of the beginning of the provision of the service, pu? be carried out at a later stage, for example upon detection of the end of the service delivery (for example, at the same time as the notification relating to the detection of the end of the service delivery).

In accordance with one embodiment, the management system 105 is configured to determine, on the basis of the personal identification of the requesting user U2 notified to it by the input control system 140, and on the basis of the personal identification / payment instrument association stored in the management system 105, the associated payment instrument to the requesting user U2 (and, possibly, the payment instrument associated with the service provided) (Figure 5D).

In accordance with one embodiment, the management system 105 is configured to transmit to the payment authorization system 135, through the corresponding communication coupling, the identification data of the payment instrument, and order the debit of a reservation amount (for example, a lump sum or an estimated amount) by the system authorization form 135 (Figure 5E). In any case, this operation can? be omitted in basic embodiments, or in alternative embodiments (for example, in case of absence or postponed notification relating to the detection of the start of service delivery).

In accordance with one embodiment, in response to a positive outcome of the booking amount debit on the payment instrument 125 (or on one of the payment instruments) associated with the requesting user U2, the payment authorization system 135 ? configured to communicate this outcome to the management system 105 (Figure 5E).

In accordance with an embodiment, in response to a negative outcome of the debiting of the amount of the service provided on the payment instrument 125 (or on each payment instrument) associated with the requesting user U2, and in response to a communication of this outcome from the payment authorization system 135 to the management system 105, the management system 105 ? configured to store an exclusion of this user from registered users and to distribute to the control systems (including the entrance control system 140) the personal identification of the excluded user for its removal from the control systems (Figure 5F) . In alternative embodiments, not shown, the storage of the user?s exclusion from registered users and the distribution to the control systems of the personal identifier of the excluded user for its removal from the control systems takes place in a subsequent phase (e.g. example, when, upon detection of the end of the service, the management system has the charge of the actual amount of the service provided), for example because the availability? of funds in the payment instrument (or any other problem that led to the negative outcome of the charge of the amount of the service provided) could have been remedied at the same time.

In accordance with an embodiment, in response to the communication from the payment authorization system 135 to the management system 105 of the negative outcome of the charge of the amount of the service provided, and/or in response to the storage (in the management system 105 ) of the exclusion of the user from registered users, and/or in response to the distribution to the control systems of the personal identifier of the excluded registered user for his removal from the control systems, the management system 105 ? configured to notify (for example, through the telecommunications network 115) the corresponding event to the user (for example, to one of its processing devices, such as a smartphone 110A or a personal computer 110B) (Figure 5F).

There? could lead the user to restore the availability? of funds in the payment instrument (or to solve any other problem that led to the negative outcome of the charge of the amount of the service provided) before the end of the provision of the corresponding service, for example before the end of the trip.

At the end of the provision of the service, for example at the end of the journey, the requesting user U2 approaches the corresponding exit control system 140 (for example, an exit turnstile which controls the exit from the underground station), and has the reading of one's identification tool 120 (for example, one's electronic identity card), for example by placing one's identification tool 120 near the of the Smart-Card reader 140SC associated with the output control system 140 (Figure 5G).

In accordance with an embodiment, if the personal identification of the requesting user U2 (read by the Smart-Card reader 140SC) is ? present in the personal identifiers stored in the exit control system 140, the control system 140 ? configured to authorize the requesting user U2, for example by opening the turnstile to allow the requesting user U2 to leave the premises? (for example, the subway station).

In accordance with one embodiment, if the personal identifier of the requesting user U2 is not ? present in the personal identifiers memorized in the exit control system 140 (for example, because, during the journey, the management system 105 has excluded the requesting user U2), the exit control system 140 does not authorize the passage of the? requesting user U2, for example by keeping the turnstile closed so as to prevent the requesting user U2 from leaving the underground station. Following this?, the requesting user U2 can? for example, contact the station staff to pay the amount of the service provided.

In accordance with an embodiment, the authorization of the requesting user U2 by the output control system 140 decrees the detection of the end of the service delivery (although this is not to be understood in a limiting way).

In accordance with one embodiment, following the authorization of the requesting user U2 by the output control system 140, the control system 140 ? configured to transmit or notify the management system 105, through the corresponding communication coupling, an indication of the service provided, the personal identifier of the requesting user U2, and the time information relating to the end of the service delivery (Figure 5H) .

In accordance with one embodiment, the management system 105 is configured to determine, on the basis of the personal identification of the requesting user U2 notified by the output control system 140, and on the basis of the personal identification / payment instrument association stored in the management system 105, the payment instrument associated with the? requesting user U2 (and, possibly, the payment instrument associated with the service provided) (Figure 5I).

In accordance with one embodiment, the management system 105 is configured to determine, on the basis of the indication of the service provided notified by the output control system 140, on the basis of the tariff of the service provided (for example, available from the management system 105), on the basis of the time interval between the start of service delivery and the end of service delivery, the amount of the service provided (Figure 5I), and instructs the payment authorization system 135 to charge this amount (or, in the case of a previous debit of a booking amount, the debit of a balance amount depending on the amount of the service provided and the booking amount) on the payment instrument associated with the requesting user U2 (Figure 5L).

In accordance with an embodiment, as discussed in relation to Figure 4F, in response to a positive outcome of the debiting of the amount of the service provided on the payment instrument 125 (or on one of the payment instruments) associated with the requesting user U2 to which ? has the service been provided, and in response to a communication of this outcome from the payment authorization system 135 to the management system 105, the management system 105 ? configured to notify the positive outcome of the transaction to the corresponding user (for example, to one of its processing devices, such as a smartphone 110A or a personal computer 110B), preferably together with an indication of the amount charged.

In accordance with one embodiment, in response to a negative result of debiting the amount of the service provided on the payment instrument 125 (or on each payment instrument) associated with the requesting user U2 to which ? has the service been provided, and in response to a communication of this outcome from the payment authorization system 135 to the management system 105, the management system 105 ? configured to store an exclusion of that user from registered users, and to distribute the personal identification of the excluded user to the control systems for his removal from the control systems.

In accordance with an embodiment, in response to the communication from the payment authorization system 135 to the management system 105 of the negative outcome of the charge of the amount of the service provided, and/or in response to the storage (in the management system 105 ) of the exclusion of the user from registered users, and/or in response to the distribution to the control systems of the personal identification of the excluded user for his removal from the control systems, the management system 105 ? configured to notify the corresponding event to the user (for example, to a processing device thereof, such as a smartphone 110A or a personal computer 110B).

In accordance with an embodiment, not shown, if the user subsequently resolves the problem that led to the negative outcome of the charge of the amount of the service provided (for example, proceeding to pay the amount of the charge failed (or of failed debits)), the management system 105 ? configured to reinstate the excluded user and distribute to the control systems (or to each respective control system), the personal identifier of the reinstated user for its storage in the control systems.

As discussed above, according to embodiments, the amount of the service provided to be charged can be include a cumulative amount of each service provided during a predetermined period of time to the requesting user U2 (for example, one or more? days): in the example in question, the amount of the service provided to be charged can? include, in addition to? the amount to make the trip, one or more? additional amounts for additional services provided during the predetermined period of time to the requesting user U2. In these embodiments, the charge of the reservation amount can be be performed only once (for example, at the first service provided during the predetermined period of time), or more? times (for example, at the first delivery of each service), as better discussed below.

In addition to the advantages described above, the present invention allows, for services with variable tariffs, to automatically determine and charge the exact amount corresponding to the actual use of the services, therefore without the need to that users know the related pricing systems, and therefore without the need? to contact dedicated personnel.

Figure 6 shows an activity diagram? of a method 600 for providing services in accordance with an embodiment of the present invention.

In accordance with one embodiment, each node (action and decision) of the activity diagram? corresponds to one or more instructions executable by the corresponding entity? involved (management system or control system) to implement the related logical function.

In accordance with one embodiment, the method 600 comprises receiving, to the system, a registration request made by a user through one or more? recording channels (for example, through an own computing device, accessing the external interface of the management system via a web browser) ? action node 602.

In accordance with one embodiment, as discussed above, the registration request includes entering a personal identification of the user, for example the user?s tax code or other personal identification capable of allowing the identification of the user? user in an unambiguous way, and the entry of identification data of a payment instrument (or more payment instruments) from which to debit the amount relating to the services provided to the user.

In accordance with one embodiment, the method 600 comprises performing a verification of the payment instrument (e.g., as discussed above, by a payment instrument authorization transaction at the payment authorization system based on the identification data of the payment instrument acquired to the virtual acceptance system to which the user is addressed) (action node 604).

In accordance with an embodiment, the method 600 comprises, in the event of a negative outcome of the authorization transaction (exit branch N of the decision node 606), the method 600, preferably notifying an error message to the user (for example, through the external interface). According to embodiments, not shown, the generation of the error message can be followed by guided procedures for the reacquisition of the identification data of the payment instrument whose authorization transaction has given a negative result, or for the acquisition of one or more? other payment instruments.

In accordance with an embodiment, the method 600 comprises, in the event of a positive outcome of the authorization transaction (output branch Y of the decision node 606), storing, in the management system (for example, in the services database) , the personal identifier / payment instrument association (that is, the personal identifier of the user registered with the management system in association with one or more payment instruments provided by the registered user) (action node 608).

In accordance with an embodiment, as discussed above, said memorizing comprises, for each of the registered users (that is, for each of the personal identifiers of the registered users), memorizing an indication of the corresponding enabled services (if, during the registration , the user has enabled one or more services among the services managed by the management system).

According to one embodiment, said memorize ? carried out by the service manager, who creates a corresponding new entry for the user in the service database.

In accordance with an embodiment, the method 600 comprises distributing to each control system the personal identifiers of the registered users (action node 610).

In accordance with one embodiment, said distributing comprises distributing to each control system the personal identifiers of only registered users for whom the corresponding service (that is, the service controlled by that control system) ? enabled, or distribute to each control system the personal identifiers of all registered users each in association with the indication of the corresponding enabled services.

In accordance with one embodiment, said distributing comprises, for each newly registered user, distributing the personal identifier of the new registered user, or distributing the personal identifiers of all registered users, including the personal identifier of the new registered user.

In accordance with an embodiment, the nodes 602-610 are performed as they are (or substantially as they are) even in the case in which a registered user accesses the management system to make changes to his own user profile. For example, if a registered user accesses the management system to make changes to one or more? payment instruments (or to add a new payment instrument) nodes 602-610 are executed as such. By way of further example, in the event that a registered user accesses the management system to make changes to the enabled services, nodes 604 and 606 can be omitted, and action nodes 602 and 608-610 can be performed as they are.

In accordance with one embodiment, the method 600 comprises, receiving, to each control system, the personal identifiers of registered users (or each newly registered user) (action node 612), and storing them therein (e.g., in the respective user database) (action node 614).

In accordance with an embodiment, the method 600 comprises, at the control system, receiving a service request submitted by a requesting user by arranging the reading of the identification tool of the requesting user (action node 616), and acquiring the ?personal identifier of the requesting user stored therein (action node 618). As previously discussed, in accordance with one embodiment, the reading of the identification tool of the requesting user takes place by means of the proximity controllers? of the control system and of the identification tool, by accessing the data structure of the identification tool through the respective security module (preferably, after validation, by the security module or the external verification system), of the personal data of the user applicant contained in the identification tool).

In accordance with an embodiment, the method 600 understands, if the personal identifier of the requesting user is not ? present in the personal identifiers stored in the control system (for example, in the corresponding user database) (output branch N of the decision node 620), for example, since the requesting user is not? authorized to access the place of business, deny the user requesting authorization to supply the service (action node 622), and wait for a new service request (as conceptually represented in the figure by connection between the action node 622 and the action node 616). As previously discussed, in accordance with one embodiment, the verification of the legitimacy of the requesting user to provide the service ? carried out by the authorization agent (by accessing the user database), and the authorization denied to the requesting user takes place by means of the corresponding control of the operation controller by the authorization agent.

In accordance with an embodiment, the method 600 comprises, if the personal identifier of the requesting user ? present in the personal identifiers stored in the control system (output branch Y of the decision node 620), authorize the requesting user to provide the service (action node 624). As discussed above, in accordance with one embodiment, the granting of the authorization to the requesting user takes place by means of the corresponding control of the operation controller by the authorization agent.

In accordance with an embodiment, following the authorization of the requesting user for the provision of the service by the control system, the method 600 comprises notifying the management system of the provision of the service (action node 626), such notification including the indication of the service provided, the personal identification of the requesting user. In accordance with an embodiment, this notification further comprises the time information relating to the provision of the service (so as to be able to detect the start of the provision of the service and the end of the provision of the service in relation to a specific activity). variable rates, as will become clear shortly).

In accordance with an embodiment, the method 600 comprises, upon receipt of the personal identification of the requesting user to the management system (for example, to the service manager) (action node 628), determining, on the basis of the identification association personal data / payment instrument stored in the management system (for example, in the services database), the payment instrument associated with the requesting user (and, possibly, the payment instrument associated with the service provided) (action node 630).

In accordance with an embodiment, the method 600 comprises disposing, from the management system (for example, from the service manager) to the payment authorization system, the charge of a reservation amount (for example, a lump sum or an amount estimated) for the service provided (or being provided).

In accordance with one embodiment, the provision of the charge of the reservation amount takes place in the event that the indication of the service provided contained in the notification of service provision decrees the detection of the start of an activity. at variable tariffs (such as a journey on a metropolitan train), or in the event that the time information contained in the notification of the provision of the service decrees that the service provided? the first service provided to the requesting user during the predetermined period of time (for example, the first service provided to the requesting user during the current day).

In accordance with an embodiment, the method 600 comprises, in the event that the service provided does not constitute the start of a business? at variable rates or the first service provided to the requesting user during the predetermined period of time (exit branch N of the decision node 632), memorize in the management system the notification of the provision of the service by the requesting user (node of action 644).

In accordance with an embodiment, the method 600 comprises, in the event that the service provided constitutes the beginning of an activity, with variable rates or the first service provided to the requesting user during the predetermined period of time (output branch Y of the decision node 632), order the debit of the booking amount on the payment instrument associated with the requesting user (node of action 634). In accordance with one embodiment, the booking amount is charged by means of a suitable communication between the management system (for example, the service manager) and the payment authorization system.

In accordance with an embodiment, the method 600 comprises, in response to a positive outcome of the debiting of the reservation amount on the payment instrument (or on one of the payment instruments) associated with the requesting user (exit branch Y of the decision node 636), store in the management system (for example, in the services database) the notification of the provision of the service and the booking amount charged to the payment instrument (action node 664).

In accordance with an embodiment, the method 600 comprises, in response to a negative outcome of the debit of the reservation amount on the payment instrument (or on each payment instrument) associated with the requesting user (exit branch N of the decision node 636), store an exclusion of the requesting user from the registered users (action node 638), and distribute to each control system (for example, analogously to what was discussed with regard to action node 610) the identifier personal data of the registered user excluded (action node 640).

In accordance with an embodiment, the method 600 comprises notifying the corresponding event to the user (for example, to a processing device thereof, such as a smartphone or a personal computer) (action node 642). Although in the illustrated embodiment the notification of the user?s exclusion (action node 642) is performed before the distribution to each control system of the personal identification of the excluded registered user (action node 640), what? Not ? to be understood in a limited way.

In accord of the amount of the services provided to that user, take into consideration the failure to charge the booking amount.

In accordance with an embodiment, the method 600 comprises, receiving, to each control system, the personal identification of the excluded user (action node 646) and storing it therein (action node 648). In accordance with one embodiment, storing the excluded registered user comprises deleting the excluded registered user from the list of registered users stored in the control systems (for example, in the user database).

According to one embodiment, after storing the personal identification of the excluded user (action node 648), each control system ? again ready to receive new service requests (as conceptually represented in the figure by means of a ring connection between the action node 648 and the action node 616).

Returning to the management system, according to one embodiment, nodes 628-644 are executed within the predetermined period of time. In accordance with one embodiment, method 600 comprises iterating nodes 628-644 until the predetermined period of time is reached. terminated (as conceptually represented in the figure by means of a ring connection between the output branch N of the decision node 650 and the action node 628).

In accordance with an embodiment, the method 600 comprises, at the end of the predetermined period of time (output branch Y of the decision node 650), determining the amount of the service provided (or services provided) to be charged to each user requestor (action node 652). As mentioned above, according to one embodiment, the amount of the service provided to be charged comprises the cumulative amount of each service provided during the predetermined period of time to the requesting user.

In accordance with one embodiment, the determination of the amount of the provided service(s) is? based on the indications of the services provided notified by the control systems, on the tariffs of the services provided, and, for each variable-rate service identified, on the time interval between the start of the service supply and the end of the supply service. In accordance with one embodiment, as discussed above, the determination of the amount of the provided service(s) is? carried out by the accounting manager? (for example by interfacing with the service manager and with the service database to retrieve the information on the services provided, the tariffs for the services provided, and, for each variable-rate service identified, the start of the service and the end of the ?service provision), or by an external accounting system communicatively coupled to the accounting manager? (or other software component of the management system).

In accordance with embodiments, the determination of the amount of the provided service(s) is? carried out on the basis of loyalty programs and/or promotional campaigns (for example, offers, subscriptions or packages that the supply organization, marketing organization or support organization proposes to promote or incentivize the use of one or more - services by users, or to reward (for example, through discounts or other benefits) users associated with a high or frequent supply of services over time).

In accordance with one embodiment, the method 600 comprises directing the payment authorization system to debit the amount (or, in the case of a previous debit of a reservation amount, to debit a balance amount dependent on the amount of the service provided and the booking amount) on the payment instrument associated with the requesting user (action node 654).

In accordance with an embodiment, in response to a positive result of debiting the amount of the service provided (or services provided) on the payment instrument (or on one of the payment instruments) associated with the requesting user to whom ? the service (or services) having been provided (output branch Y of the decision node 656), the method 600 terminates, preferably by notifying the positive outcome of the transaction to the corresponding user (for example, to one of its processing devices, such as smartphone or personal computer), preferably together with an indication of the amount charged.

In accordance with one embodiment, in response to a negative result of debiting the amount of the service provided (or services provided) on the payment instrument (or on each payment instrument) associated with the requesting user to whom ? the service has been provided (exit branch N of the decision node 656), the method 600 comprises storing the exclusion of the requesting user from the registered users (action node 658), and distributing to each control system (for example, similarly to what has been discussed regarding the action node 610) the personal identifier of the excluded user (action node 660).

In accordance with an embodiment, the method 600 comprises notifying the corresponding event to the user (for example, to a processing device thereof, such as a smartphone or a personal computer) (action node 662). Although in the illustrated embodiment the user?s exclusion notification (action node 662) is performed before the distribution to each control system of the personal identification of the excluded registered user (action node 660), what? Not ? to be understood in a limited way.

In accordance with an embodiment, the method 600 comprises, receiving, to each control system, the personal identifier of the excluded registered user (action node 664) and storing it therein (action node 666).

In accordance with one embodiment, storing the excluded user includes deleting the excluded user from the list of registered users stored in the control systems (for example, in the user database).

According to one embodiment, after storing the personal identification of the excluded user (action node 666), each control system ? again ready to receive new service requests (as conceptually represented in the figure by means of a ring connection between the action node 666 and the action node 616).

Naturally, in order to satisfy contingent and specific needs, the person skilled in the art can make numerous logical and/or physical modifications and variations to the present invention. Pi? Specifically, although the present invention has been described in some detail with reference to one or more its embodiments, ? it is clear that various omissions, substitutions and changes in form and detail so? as other embodiments are possible. In particular, different embodiments of the present invention can be put into practice even without the specific details (such as the numerical values) disclosed in the previous description to provide their more complete understanding; conversely, well-known features may have been omitted or simplified in order not to obscure the description with unnecessary detail. Furthermore, ? It is expressly understood that specific elements and/or method steps described in relation to each embodiment of the present invention may be incorporated into any other embodiment as a normal design choice. Furthermore, elements presented in the same group and different embodiments, examples or alternatives should not be interpreted as de facto equivalent to each other (but are separate and autonomous entities). In any case, any numeric value should be read as modified by the about term (if not already specified), and any range of numeric values should be understood as expressly specifying any possible number along the continuum within the range (including its extremes). Also, are ordinal or other qualifiers merely used as labels to distinguish elements with the same name but do not connote per se? themselves no priority, precedence or order. Furthermore, the terms include, include, have, contain, entail, and the like should be understood to have an open meaning and not exhaustive (i.e., not limited to the recited items), the terms based on, dependent on, in accordance with, according to, in function of and the like should be understood with a non-exclusive relationship (that is, with any further variables involved), the term one/one should be understood as one or more? elements (unless expressly stated otherwise), and the term means for (or any functional formulation) should be understood as any structure suitable or configured to perform the relevant function.

For example, one embodiment provides a method for dispensing one or more services. However, the services can be in any number and of any type (for example, payments, activities, entrances, services).

In accordance with one embodiment, the method comprises storing, in a service delivery management processing system, corresponding personal identifiers of a plurality of identifiers. of users registered in the management processing system each in association with at least one payment instrument. Anyway, one or more? a user's payment instruments may be shared with (that is, further associated with) one or more additional registered users (for example, belonging to the same household). In addition, the management processing system can be of any type (see below), and pu? store additional information relating to each registered user (for example, name, date and place of birth) and corresponding operational information (such as password, e-mail address, telephone number).

In accordance with one embodiment, the method comprises distributing, from the management processing system to one or more? control processing systems of each of the services, the personal identifiers for their storage in each of the control processing systems. Without losing generality, the distribution of personal identifiers can be carried out in any way, for example asynchronously (for example, with each addition / modification of one or more personal identifiers), or synchronously (for example, at pre-established time intervals).

In accordance with an embodiment, the method comprises receiving from one of the control processing systems of one of the services a request for provision of the current service from a requesting user by reading the personal identification of the requesting user from a identification of the requesting user. Without losing generality, reading the personal identification of the requesting user from the identification tool of the requesting user can be carried out in mode? in contact and/or in mode? non-contact (for example, in NFC or RFID technology). Furthermore, reading the personal identification of the requesting user from the identification tool of the requesting user can be carried out in accordance with the modality with which this personal identifier ? stored in the identification medium (for example, by digital signature, with access code protection, and/or by password).

In accordance with one embodiment, the method comprises authorizing the current control processing system to provide the current service to the requesting user in response to the presence of the requesting user?s personal identifier in the personal identifiers stored in the system current control processing. Without losing generality?, the authorization can? be of any type (for example, granted, denied, or conditioned (for example, conditioned on the verification of one or more security codes and/or one or more biometric data)). Furthermore, the authorization can be granted in any way, for example dependent on the corresponding service: by way of non-limiting examples, the authorization can? be granted by opening a turnstile, opening a door of an office/house, or confirming it with a transport inspector).

In accordance with an embodiment, the method comprises transmitting from the current control processing system to the management processing system an indication of the current service provided and the personal identification of the requesting user. Without losing generality, the transmission from the current control processing system to the management processing system of the indication of the current service provided and of the personal identification of the requesting user can be carried out in any way and with appropriate timing (for example, in synchronous or asynchronous mode).

In accordance with an embodiment, the method comprises causing the management processing system to debit an amount of the current service provided on the at least one payment instrument associated with the personal identifier of the requesting user. Without losing generality, the charge of the amount of the current service provided can be placed (for example, distributed) on two or payment instruments (for example, in the case of setting a payment instruments preference order, in order to exhaust the availability of funds according to this preference order).

In accordance with one embodiment, the method comprises storing, in the management processing system, an indication of one or more? enabled services in association with each of at least part of the personal identifiers. Without losing generality?, memorization of the indication of enabled services can? be performed in any suitable apparatus, for example in one or more? separate (and accessible) devices from the management processing system.

In accordance with an embodiment, the method comprises distributing, from the management processing system to the control processing systems of each of the services, the personal identifiers in association with the indication of the corresponding services enabled for their storage in each of the systems of control processing. Without losing generality, the distribution of personal identifiers in association with the indication of the corresponding services enabled for their storage in each of the control processing systems can be carried out in any way and with appropriate timing (for example, in synchronous or asynchronous mode).

In accordance with an embodiment, the method comprises authorizing by the current control processing system the provision of the current service to the further requesting user in response to the presence of the indication of the current service in association with the personal identifier of the ?requesting user in the personal identifiers stored in the current control processing system. Without losing generality?, the authorization to supply the current service can? be conferred subject to the verification of further requisites, such further requisites depending on the type of current service.

In accordance with one embodiment, the method comprises storing, in the management processing system, each of the personal identifiers of one or more secondary registered users each in association with at least one payment instrument of a primary registered user. Without losing generality, each payment instrument can be associated with any number of secondary registered users, or with a predetermined maximum number of secondary registered users.

In accordance with one embodiment, the method comprises detecting, from a current of one or more? further control processing systems of each of the services, a starting and ending of the current service, and determining, by the management processing system, the amount of the current service based on the starting and ending of the current service. Without losing generality?, the start and end of the current service can also be? detected by the management processing system, for example on the basis of timestamps associated with the authorizations granted by the control processing systems.

In accordance with an embodiment, the method comprises causing the management processing system to charge a cumulative amount for each service provided during a predetermined period of time to the requesting user. Without losing generality, the predetermined period of time can be chosen by each registered user, or mandated by the management organization, marketing organization, and/or support organization. In accordance with an embodiment, said transmitting from the current control processing system to the management processing system an indication of the service provided and the personal identification of the requesting user further comprises causing a charge from the management processing system of a booking amount to a payment circuit associated with the selected payment instrument. In any case, the charge of the reservation amount can be omitted in basic embodiments. Without losing generality, the provision of the charge of the reservation amount can take place in the event that in the event of detection of? the start of an? activity? at variable tariffs or in the event that the service provided is the first service provided to the requesting user during the predetermined period of time. Also, the booking amount can be chosen by each registered user, or mandated by the management organization, marketing organization, and/or support organization.

In accordance with an embodiment, said causing the management processing system to debit the amount of the service provided on the selected payment instrument comprises causing the management processing system to debit a balance amount depending on the amount of the service provided and the booking amount.

In accordance with one embodiment, the method comprises storing, in the management processing system, a ban of each of the registered users in response to a failure of one or more of the registered users. of the corresponding charges. Without losing generality, the exclusion of the user from registered users can take place in response to failure to charge the balance amount only (i.e., not in response to failure to charge the reservation amount).

In accordance with one embodiment, the method comprises distributing, from the management processing system to the control processing systems, the personal identifiers of the excluded registered users for their removal from the control processing systems. Without losing generality, the distribution of personal identifiers of excluded registered users can be carried out in any way, for example asynchronously (for example, to each new excluded registered user or to each new group of excluded registered users), or synchronously (for example, at pre-established time intervals).

In accordance with one embodiment, the method comprises storing, in the management processing system, a reinstatement of each of the excluded registered users in response to a payment of the corresponding failed charges, and distributing, from the management processing system to the control processing, the personal identifiers of registered users reintegrated for their storage on control processing systems.

In accordance with an embodiment, the request for service delivery comprises a request for access to a protected area suitable for providing the service. Without losing generality?, the protected area can? be of any kind (for example, the place of an activity, a headquarters/office of a company/studio, a home, or a means of transport).

In accordance with an embodiment, the control processing system comprises an access control system to said protected area. Without losing generality, the access control system can be of any type and pu? be placed in any position with respect to the protected area. The control system can be a turnstile (e.g., bar/revolving door, sliding panel), door, gate), validator (e.g., a validator installed on a bus or tram), or digital assistant (e.g. example, a digital assistant of the control personnel in charge of the control near and/or inside the protected area).

In accordance with an embodiment, the identification tool of the requesting user comprises an identity card email of the requesting user. Without losing generality?, the identification tool can? be of any type (for example, a passive Smart-Card, an active Smart-Card, a USB stick, an SD card, a driving licence, a health card, a SIM, a staff badge, a passport) and can be read in any way (e.g., tactile, (e.g., magnetic and/or optical reading), and/or non-tactile).

In general, similar considerations apply if the present invention is implemented with equivalent methods (using similar steps with the same functions of several steps or their portions, removing some non-essential steps or adding further optional steps); moreover, the steps can be performed in different order, in parallel or overlapping (at least partially).

One embodiment provides a computer program configured to cause a computer system to implement each of the above methods. One embodiment provides a computer program product comprising a computer readable storage medium which embeds a computer program, the computer program being loadable into a working memory of a computer system thereby? configuring the computer system to implement each of the same methods. However, each program pu? be run on any computer system (see below), and pu? be implemented as a module s? stand-alone, as an add-on program (plug-in) to a pre-existing program (for example, a delivery organization or marketing organization management program), either directly into the latter or provided as a service. In any case, similar considerations apply if the program ? structured differently, or if additional modules or functions are planned; similarly, memory structures can be of other types, or can be replaced with entities? equivalent (not necessarily consisting of physical storage media). The program can take any form suitable for use by any computer system (see below), with the ci? configuring the computer system to perform desired operations; in particular, the program pu? be in the form of external or resident software, firmware or micro-code (whether in object code or source code, for example, to be compiled or interpreted). Furthermore, ? You may provide the program on any computer-readable storage medium; the storage medium? any tangible support (other than transient signals per se) that pu? maintain and memorize instructions for use by the computer system. For example, the storage medium can? be electronic, magnetic, optical, electromagnetic, infrared or semiconductor; examples of such storage media are hard disks (where the program can be preloaded), removable disks, memory sticks (for example, USB) and the like. The program can be downloaded to the computer system from the storage medium or via a network (for example, the Internet, a wide area network and/or a local area network including transmission cables, optical fibers, wireless connections, network devices); one or more network adapters of the processing system receives the program from the network and forwards it for storage in one or more? computer system storage devices. In any case, the present invention also lends itself to being implemented with a hardware structure (for example, by electronic circuits integrated in one or more chips of semiconductor material), or with a combination of software and hardware suitably programmed or otherwise configured.

One embodiment provides a system comprising means configured to perform the steps of each of the above methods. One embodiment provides a system including circuitry (e.g., any suitably configured hardware such as via software) for performing each of the steps of the same methods. However, the system pu? be of any type (for example, the management system with one or more control systems, only the management system or only one of the control systems); the management system can? be of any type (for example, one or more servers, a cloud structure, and so on), any control system can be of any type, and they may communicate with each other in any way (for example, via a local, wide area, global, cellular or satellite network using any type of wired and/or wireless connection).

In general, similar considerations apply if the system includes equivalent components or has other operating characteristics. In any case, any of its components can? be separated into more elements, or two or more? components can be combined into a single element; moreover, each component pu? be replicated to support the execution of the corresponding operations in parallel. Also, unless otherwise noted, any interactions between different components generally need not be continuous, and can be continuous. be both direct and indirect through one or more? intermediaries.

Claims (10)

1. A method (600) to deliver one or more? services, wherein the method comprises: storing (608), in a service delivery management processing system (105), corresponding personal identifiers of a plurality of? of users registered in the management processing system each in association with at least one payment instrument; distribute (610), from the management processing system to one or more? control processing systems (140) of each of the services, the personal identifiers for their storage in each of the control processing systems; receive (612) from one of the control processing systems of one of the services a request for provision of the current service from a requesting user by reading the personal identification of the requesting user from an identification tool (120) of the requesting user ; authorize (624) by the current control processing system the provision of the current service to the requesting user in response to the presence of the requesting user?s personal identifier in the personal identifiers stored in the current control processing system; transmitting (626) from the current control processing system to the management processing system an indication of the current service provided and the personal identification of the requesting user; cause (654) from the management processing system a charge of an amount of the current service provided on the at least one payment instrument (125) associated with the personal identification of the requesting user. The method (600) according to claim 1, wherein the method comprises: store (608), in the management processing system (105), an indication of one or more? enable the services in association with each of at least part of the personal identifiers; distribute (610), from the management processing system to the control processing systems (140) of each of the services, the personal identifiers in association with the indication of the corresponding services enabled for their storage in each of the control processing systems; and authorizing (624) by the current control processing system the provision of the current service to the requesting user further in response to the presence of the current service indication in association with the requesting user?s personal identifier in the stored personal identifiers in the current control processing system. The method (600) according to claim 1 or 2, wherein the method comprises: store (608), in the management processing system, each of the personal identifiers of one or more? secondary registered users each in association with the at least one payment instrument (125) of a primary registered user. The method (600) according to any one of claims 1 to 3, wherein the method comprises: detect (632), from a current of one or more? further control processing systems of each of the services, a start and finish of the current service, and determine (652), from the management processing system (105), the amount of the current service based on the start and finish of the current service. The method (600) according to any one of the preceding claims, wherein the method comprises: causing (654) the management processing system (105) to charge a cumulative amount for each service provided during a predetermined period of time to the requesting user. 6. Method (600) according to any one of the preceding claims, wherein said transmitting (626) from the current control processing system (140) to the management processing system (105) an indication of the service provided and the identifier personnel of the requesting user further comprises causing (634) from the management processing system a debit of a reservation amount to a payment circuit associated with the selected payment instrument, and in which said causing (654) from the management processing system the debiting of the amount of the service provided on the at least one payment instrument (125) includes causing (654) the management processing system to debit a balance amount depending on the amount of the service provided and the amount of reservation. 7. The method (600) according to any one of the preceding claims, wherein the method comprises: store (638,658), in the management processing system (105), an exclusion of each of the registered users in response to a failure of one or more? of the corresponding charges, e distribute (640,660), from the management processing system to the control processing systems, the personal identifiers of the excluded registered users for their removal from the control processing systems (140). The method (600) according to claim 7, wherein the method comprises: store, in the management processing system, a reinstatement of each of the excluded registered users in response to a payment of the corresponding failed charges, and distribute, from the management processing system to the control processing systems, the personal identifiers of the reintegrated registered users for their storage on the control processing systems. 9. The method (600) in accordance with any one of the preceding claims, wherein the request for service provision comprises a request for access to a protected area capable of providing the service, and wherein the control processing system ( 140) comprises an access control system to said protected area. 10. The method (600) according to any one of the preceding claims, wherein the identification tool (120) of the requesting user comprises an identity card? email of the requesting user.