Patent Publication Number: US-2022237976-A1

Title: Method and system for access to a secured building

Description:
FIELD OF THE DISCLOSURE 
     The present disclosure generally relates to the field of building security. In particular embodiments or aspects, the disclosure relates to methods and systems for accessing a secured building. 
     BACKGROUND 
     Access to a secured building, for a non-tenant, generally require a tenant&#39;s presence at the building to permit access. Similarly, for service providers who may require access to a building, or a unit within the building, generally require a tenant&#39;s presence at the building and/or the unit to permit access. Service providers may include any party who requires access to the building and/or a unit within a building to provide a service. The service may be a plumbing service, and electrical service, a delivery of a package, mail, food, etc. 
     A service provider attempting to access a building may be unable to provide its services if a tenant is not present to permit access, where required, or otherwise, the tenant is unable to permit access as required according to the building security protocols. Accordingly 
     Accordingly, there is a need for improving the access to a secured building for service providers. 
     SUMMARY 
     It is an object of the present disclosure to provide a method and system for accessing a secured building. 
     An aspect of the invention provides for a method of accessing a secured building. The method includes retrieving information from a code associated with a carrier and an address. The method further includes confirming that the address is associated with the secured building. The method further includes validating the carrier as an authorized carrier. The method further includes validating a status associated with the information to be one of: in transit; and out for delivery. The method further includes allowing access to the secured building. In some embodiments, prior to allowing access to the secured building, the method further includes checking an that update to the status is within 24 hours. In some embodiments the step of validating the carrier as an authorized carrier includes determining an identification of the carrier associated with the information. In some embodiments the code is a barcode. In some embodiments the barcode is one of: 1 dimensional linear bar code; 2-dimensional bar code, an image, specialized augmented postal code; intelligent mail barcode; and electronic product code. In some embodiments the step of allowing access to the secured building comprises opening a secured door. In some embodiments the information is a tracking code. In some embodiments the method further includes displaying an access code for accessing a locker system including a locker associated with the address. In some embodiments, the method further includes receiving, by the locker system, the access code. In some embodiments, the method further includes validating the access code. In some embodiments, the method further includes allowing access to the locker. In some embodiments, the step of validating the access code includes: checking that a time window associated the access code is not expired. In some embodiments, the method further includes retrieving the information from the code associated with carrier and the address. In some embodiments, the method further includes confirming that the address is associated with the secured building. In some embodiments, the method further includes validating the carrier as the authorized carrier. In some embodiments, the method further includes validating a second status associated with the information to be one of in transit and out for delivery. In some embodiments, the method further includes allowing access to a locker system including a locker associated with the address. In some embodiments, the method further includes sending a message to a device associated with the address, the message indicating that access to the secured building has been granted for the carrier. In some embodiments, the method further includes sending a message to a device associated with the address, the message indicating that access to the locker has been granted for the carrier. In some embodiments, the method further includes the device is a mobile of a tenant associated with the address. 
     Another aspect of the invention provides for a system for accessing a secured building. The system includes at least one processor. The system further includes a non-transient computer readable memory for storing instructions which when executed by the at least one processor cause the system to perform the methods described herein. For example, such a system is caused to retrieve information from a code associated with a carrier and an address. The system is further caused to confirm that the address is associated with the secured building. The system is further caused to validate the carrier as an authorized carrier. The system is further caused to validate a status associated with the information to be one of in transit; and out for delivery. The system is further caused to allow access to the secured building. In some embodiments, the instructions further cause the system to check that an update to the status is within 24 hours. In some embodiments, the instructions which cause the system to validating the carrier as an authorized carrier includes: instructions to determine an identification of the carrier associated with the information. In some embodiments, the code is a barcode. In some embodiments, the barcode is one of: 1 dimensional linear bar code; 2-dimensional bar code, an image, specialized augmented postal code; intelligent mail barcode; and electronic product code. In some embodiments, the instructions which cause the system to allow access to the secured building includes: instructions to open a secured door. In some embodiments, the information is a tracking code. In some embodiments, the instructions further cause the system to: display an access code for accessing a locker system including a locker associated with the address. In some embodiments, instructions further cause the system to receive, by the locker system, the access code. In some embodiments, instructions further cause the system to validating the access code. In some embodiments, instructions further cause the system to allow access to the locker. In some embodiments, the instructions which cause the system to validating the access code includes: instructions to check that a time window associated the access code is not expired. In some embodiment, the instructions further cause the system to retrieve the information from the code associated with carrier and the address. In some embodiments, instructions further cause the system to confirm that the address is associated with the secured building. In some embodiments, instructions further cause the system to validate the carrier as an authorized carrier. In some embodiments, instructions further cause the system to validate a second status associated with the information to be one of: in transit; and out for delivery. In some embodiments, instructions further cause the system to allow access to the locker system including a locker associated with the address. In some embodiments, instructions further cause the system to send a message to a device associated with the address, the message indicating that access to the secured building has been granted for the carrier. In some embodiments, instructions further cause the system to send a message to a device associated with the address, the message indicating that access to the locker has been granted for the carrier. In some embodiments, the device is a mobile of a tenant associated with the address. 
     Embodiments have been described above in conjunctions with aspects of the present disclosure upon which they can be implemented. Those skilled in the art will appreciate that embodiments may be implemented in conjunction with the aspect with which they are described, but may also be implemented with other embodiments of that aspect. When embodiments are mutually exclusive, or are otherwise incompatible with each other, it will be apparent to those skilled in the art. Some embodiments may be described in relation to one aspect, but may also be applicable to other aspects, as will be apparent to those of skill in the art. 
    
    
     
       BRIEF DESCRIPTION OF THE FIGURES 
       Further features and advantages of the present disclosure will become apparent from the following detailed description, taken in combination with the appended drawings, in which: 
         FIG. 1  is a block diagram of a built-in entry console within a computing and communications environment used for implementing devices and methods according to an embodiment of the present invention; 
         FIG. 2  is a call flow diagram of a package delivery procedure according to an embodiment of the present invention; 
         FIG. 3  is a call flow diagram of the verification procedure discussed in  FIG. 2  according to an embodiment of the present invention; 
         FIG. 4  is another call flow diagram of the verification procedure discussed in  FIG. 2  according to an embodiment of the present invention; and 
         FIG. 5  illustrates a call flow diagram for depositing a package using the locker system, according to embodiments of the present invention. 
     
    
    
     Throughout the appended drawings, like features are identified by like reference numerals. 
     DETAILED DESCRIPTION 
     Embodiments described herein provide methods and systems for access to a secured building. Although example embodiments are described in reference to a service provider delivering a package, a person skilled in the art may apply the methods and systems as described by example embodiments herein for access to a building in the case of other service providers. Accordingly, delivery a package is but one example of a service provider, and thus example embodiments described herein are not limited to such example. 
     Every day, millions of packages or parcels are delivered throughout the world. In delivering the packages, service providers, for example, package delivery companies (“carriers”) use various tracking mechanisms to ensure efficient and effective delivery of the packages. When a sender delivers a package (sends a package for delivery), the carriers/service provider attach an information label including a unique code, such as a bar code (or barcode) to the package. The barcode contains information identifying the package, the sender, sender&#39;s address, the recipient, the recipient&#39;s address and other information relating to the status of the delivery (tracking information). The tracking information can be used by the carrier personnel, the sender, and/or recipient to determine the status of the delivery. 
     Despite the delivery mechanisms and the availability of the tracking information used by the carriers, not all packages are delivered to the recipients. One common reason for packages not being delivered to the recipient is because the recipient is not available to receive the package when the delivery person is at the recipient&#39;s address. In such circumstances, the carrier delivery person would attempt to deliver the package at a later time hoping that the recipient would be available to receive the package, or the delivery person would leave the package at a nearby carrier center for pick up by the recipient. 
     Similar problems are also likely for other service providers who require access to the building, such as an electrician, a plumber, a food delivery person, etc. 
       FIG. 1  is a block diagram of a built-in entry console (EC)  102  within a computing and communications environment  100  used for implementing the devices and methods disclosed herein. In some embodiments, the EC  102  is a device that connects to network infrastructure over a radio interface. In some embodiments, EC  102  is a Machine Type Communications (MTC) device (also referred to as a machine-to-machine (m2m) communication device). The EC  102  device may contain multiple instances of a component, such as multiple processors, memories, transmitters, receivers, etc. The EC  102  typically includes a processor  106 , such as a Central Processing Unit (CPU), I/O interface  116  to connect with I/O devices (such as a barcode scanner and an access door), a memory  106 , a network interface  108  and a bus  110  to connect the components of EC  102 . EC  102  may optionally also include components such as a mass storage device  112 , a video adapter  114  (shown in dashed lines). 
     The memory  106  may comprise any type of non-transitory system memory, readable by the processor  106 . The bus  110  may be one or more of any type of several bus architectures including a memory bus or memory controller, a peripheral bus, or a video bus. 
     The one or more network interfaces  108 , may include at least one of a wired network interface and a wireless network interface. The EC  102  can connect wirelessly to the console&#39;s cloud server  118  via network interface(s)  108  for sending and receiving information. The EC  102  can also include a radio access network interface  120  for connecting to other devices over a radio link. 
     The mass storage  112  may comprise any type of non-transitory storage device configured to store data, programs, and other information and to make the data, programs, and other information accessible via the bus  110 . In the illustrated embodiment, mass storage  112  is distinct from memory  106  where it is included, and may generally perform storage tasks compatible with higher latency, but may generally provide lesser or no volatility. In some embodiments, mass storage  112  may be integrated with a memory  106  to form a heterogeneous memory. 
     The I/O interface  116  is connected to I/O device(s)  124  such as a barcode scanner capable of reading a barcode attached to packages for delivery. The EC  102  is also connected to an access door used by a delivery person in delivering packages. The EC  102  can grant access to a delivery person to deliver a package where a package passes the verification procedure described elsewhere herein. The EC  102  grants access by opening a door permitting the delivery person to deposit the package. 
     The EC  102  can also be coupled to a touch-screen I/O device  124  for permitting the delivery person to manually input information into the EC  102 . The optional video adapter  114  (shown in dashed lines) provides interfaces to couple the EC  102  to a display for providing information to the delivery person. 
     In some embodiments, EC  102  is a built-in standalone device that can be installed in any property used for receiving one or more delivery packages. Such properties include any multi-unit/tenant property. 
       FIG. 2  is a call flow diagram of a package delivery procedure according to an embodiment of the present invention. In an embodiment, the package delivery procedure begins with a delivery person having arrived at the package delivery destination, the recipient&#39;s address, which would be indicated on the information label attached to the package. At step  208 , the delivery person, using the barcode scanner device  124 , scans the unique barcode included as part of the information label attached to the package. Alternatively, the delivery personnel can manually enter the barcode number disclosed on the information label using the touch screen of the EC  102 . 
     A code may be any form of information that a service provider may use to access a secured building. In the case of package delivery, a code may be a barcode. 
     A barcode is an encoded image (representation of data), usually displayed with black and white lines, but also in other variations, in various patterns that contains information that is readable by a machine. Barcodes may take various forms including non-specific 1 dimensional (1D) linear barcodes, 2-dimensional (2D) matrix barcodes, specialized augmented postal codes such as Postal Alpha Numeric Encoding Technique (PLANET), Postal Numeric Encoding Technique (POSTNET), Intelligent Mail barcodes, and other electronic product codes (EPC-s). 
     A code, for example, a barcode, includes various information, for example, a tracking code from which the following information can be determined: carrier type (the package delivery company), the sender information containing the sender&#39;s address, the recipient information containing the recipient&#39;s address, and other relevant information (packaging information). Further, the tracking code is associated with tracking information that is updated at the various stages of the delivery. The tracking information can be obtained via the tracking code to inform the sender and/or the recipient of the status of the delivery. All such information is stored and updated in a database (DB)  202  accessible by the EC  102 . 
     Tracking information is gathered at various stages of the package delivery and maintained in the DB  202 . Tracking information may be gathered by reporting the arrival and/or departure of the package at the various stages of the packing delivery. At each stage, information including the identity of the package, the location, the time, and the status of the delivery, for example, “in-transit” and “out for deliver” can be uploaded and updated to the DB  202 . Alternatively, tracking information may be gathered using Global Positioning System (GPS)-based vehicle tracking system, and/or beacons to locate the delivery vehicle that contains the package and record the tracking information in a real-time to DB  202 . Additional information related to the package may also be gathered, for example package information relating to the temperature, humidity, pressure, acceleration, elevation, and exposure to light at different time points, which may be relevant for delicate or perishable packages. 
     The package information including the tracking information is maintained in a DB  202 , which can be but need not be internal to the server cloud (SC)  118 . The DB  202  may also within a carrier&#39;s server cloud (CSC)  204  accessible by the console&#39;s BOS  118 . Alternatively, the BOS  118  may use both an internal DB  202  and an external database. The external data base may be within the CSC  204  or a separate entity, in which the external entity/DB may be accessed by both the console&#39;s BOS  118  and the CSC  204 . 
     The delivery personal can use the barcode scanner  124  to scan  208  the barcode. Alternatively, the delivery personnel can manually enter the barcode number disclosed on the information label using the touch screen I/O device  124 . The delivery personnel may manually enter the barcode number in situations where the barcode scanner is unable to read the barcode for whatever reason. 
     The EC  102  retrieves information  208  embedded in the scanned barcode, for example, a tracking code, from which the following information can be determined: carrier type (the package delivery company), the sender information containing the sender&#39;s address, the recipient information containing the recipient&#39;s address, and other relevant information (packaging information). Further, the tracking code is associated with tracking information that is updated at the various stages of the delivery. The tracking information can be obtained via the tracking code to inform the sender and/or the recipient of the status of the delivery. 
     The EC forwards  210  the retrieved information to the Building Operating System (BOS)  118 . Using the retrieved information, the BOS  118  and CSC  204  perform a verification procedure  212  to ensure that the package is indeed a legitimate package addressed to the recipient. Following the verification procedure  212 , the BOS  118  provides a response  240  instructing the EC  102  to permit or deny entry to a door associated with the recipient&#39;s address provided in the packaging information. The door associated with the recipient&#39;s address provided in the packaging information may be a door for providing access to a locker system for depositing the package to a locker associated with the recipient. The response may be a positive response, allowing the delivery person access via instructing the EC  102  to open the door, or a negative response, denying access to the door. 
     The EC  102  will then act on the response  242  from the BOS  118 . If the response  240  is a positive response, for example, “access allowed”, the EC  102  will open the door associated with the recipient&#39;s address for the delivery person to access the locker system for depositing the package. The EC  102  may display an access code that may be used at the locker system to access the recipient&#39;s locker/mailbox. 
     In some embodiments, where the response is positive, the EC  102  sends a message  246  to the BOS  118  indicating that the package has been delivered, and accordingly, the BOS  118  will update the tacking information in the DB  202  via a similar message  248  indicating that the package associated with the scanned barcode has been delivered to its destination. 
     In some embodiments, where the response  240  is a positive response, the EC  102  notifies  244  the recipient&#39;s mobile (RM)  206  via a message that a package addressed to the recipient has been received. The recipient may receive the message via various means including but not limited to email, voice message, text, and/or alert and other means of notifications/messaging. 
     If the response  240  is a negative response, for example “access denied”, the EC  102  will not open the door. In some embodiments, the EC  102  may display a message on the display  122  for the delivery person that the access is denied. The EC  102  may include the reason for denying access, which could be one or more of the following: the carrier is not a recognized carrier; package is not “in transit” or “out for delivery”; and last update status is not within the past 24 hours. The reason for denying access can be provided in the response  240  provided by the SC  102 . The reason for denying access may be useful to the delivery person in verifying the package at the delivery person&#39;s carrier center where more information about the package can be obtained. 
     In some embodiments, where the response  240  is a positive response, the EC  102  may notify the recipient&#39;s mobile (RM)  206  via a message that a package addressed to the recipient is expected to be received. The recipient may receive the message via various means including but not limited to email, voice message, text, app notification and/or alert and other means of notifications/messaging. 
     Where access has been granted at step  242 , the EC  102  may send a message  246  to the BOS  118  indicating that the package is expected to be deposit. Accordingly, the BOS  118  will update the tacking information in the DB  202  via a similar message  248  indicating that the package associated with the scanned barcode is expected to be deposited at the recipient&#39;s assigned locker. 
       FIG. 3  and  FIG. 4  are call flow diagrams of the verification procedure  212  discussed in  FIG. 2  according to embodiments of the present invention. 
     Referring to  FIG. 3 , when the BOS  118  receives the retrieved information including the unique tracking code  210 , the BOS  118  sends a verification request  214  including the retrieved information to its local DB  202 . The request  214  requests the following information: the carrier type associated with the tracking code; whether the package associated with the tracking code has a delivery status of either “in transit” or “out for delivery”; and whether the last delivery status update associated with the tracking code is within the last 24 hours. The local DB  202  includes a list of recognized/registered carrier types including but not limited to, United Parcel Service (UPS), FedEx, Dalsey Hillblom Lynn (DHL), Canada Post, Purolator and Intelcom Express. For each carrier type, the local DB  202  may receive updates from the CSC  204  on the status of package deliveries destined for the building. 
     At step  216 , If the DB  202  has been updated by the CSC  204  with the status of the package delivery requested information, the DB  202  responds by providing a verification response providing tracking information  216  associated with the tracking code to the BOS  118 . 
     Where the DB  202  determines that the carrier type of the tracking code is a registered carrier type with BOS  118  but is unable to determine whether the delivery status of the package is either “in transit” or “out for delivery”, the DB  202  may forward a request  218  to the carrier&#39;s server cloud  204  of the determined carrier. Where the DB  202  determines the carrier type of the tracking code but is unable to determine whether the last delivery status update of the package associated with the tracking code is within the last 24 hours, the DB  202  may also forward the request  218  to the server cloud  204  of the determined carrier. 
     In some embodiments (not shown), the BOS  118  may forward the request  218  to the CSC  204 , instead of the DB  202  sending the request  218  to the CSC  204 . Upon receiving the request  218 , the CSC  204  can search its internal network, including the GBS-based vehicles to locate the delivery vehicle that contains the package and record the tracking information  220  in real-time to DB  202 . 
     Accordingly, the DB  202  provides the updated tracking information  222  to BOS  118 . 
     The BOS  118  sends a response  240  instructing the EC  102  whether to permit or deny access to the delivery person. The BOS  118  permits access only if the following information (required information) is provided in the verification response  216  or  222 : the carrier type is recognized; the delivery status associated with the tracking code is either “in transit” or “out for delivery”; and the last delivery status is updated within the last 24 hours. If any of the required information is not provided in the responses  216  and/or  222 , the response  240  is a negative response, denying access to the delivery person. 
       FIG. 4  is alternative call flow diagram of the verification procedure  212  discussed in  FIG. 2  according to embodiments of the present invention. 
     Referring to  FIG. 4 , upon receiving the request for access  210 , the BOS  118  may alternatively send individual requests  224 ,  228 ,  235  to its local DB  202  for the required information in verifying the package as part of the verification procedure  212 . The BOS  118  sends a carrier request  224  to the DB  202 , including in the request the retrieved tracking code. 
     If the DB  202  recognizes the carrier type as a registered carrier type with BOS  118 , then the DB  202  responds positively with the name of carrier type. Otherwise, the DB may provide a negative respond. The negative response can be a no response, or a message to the BOS  118  that the DB does not recognize the carrier type of the tracking code. If the BOS  118  receives a negative response for carrier type, the BOS  118  accordingly sends a negative response at step  240  denying access to the delivery person. 
     Where the BOS  118  receives a carrier type response  226  recognizing the carrier type of the tracing code, BOS  118  sends a first validation request  228  to DB  202  requesting whether the delivery status associated with the tracking code is either “in transit” or “out for delivery”. 
     The DB  202  may respond that the delivery status is either “in transit” or “out for delivery”, provided DB  202  has been updated by the CSC  204 . The DB  202  may provide a negative response to the request  228 ; the negative response may be that DB has no information on the delivery status or a current delivery status other than “in transit” and “out for delivery” is associated with the tracking code. 
     Where the DB  202  provides a negative response, the DB  202  may forward the first validation request  232  to the server cloud  204  of the recognized carrier type. 
     The CSC  204  can search its own network, including the GBS-based vehicles to locate the delivery vehicle that contains the package and record the tracking information  233  in real-time to DB  202 . The tracking information  233  may include an update to the delivery status indicating “in transit” or “out for delivery”: and accordingly, the DB  202  forwards the tracking information  234  to BOS  118 . 
     If the response  234  is a negative response, meaning that the response does not include a delivery status that is one of “in transit” or “out for delivery” then the BOS  118  sends a negative response at step  240  the EC  102  denying access to the delivery person. 
     If the validation response  232  or  234  is a positive response indicating that the delivery status associated with the tracking code is one of “in transit” or “out for delivery”, then the BOS  118  sends a second validation request  235 , requesting the DB  202  if the last update status associated with the tracking code was within the last 24 hours. 
     It should be noted that BOS  118  can request the first  228  and second  235  validation requests in any order; and in some embodiments the BOS  118  may only ask for one validation request including both the first and second validation requests in one request. 
     The DB  202  may provide a positive or a negative response  236  to the BOS  118 . The positive response being that the last update status is within the last 24 hours and the negative response is that the last update status is not within the last 24 hours. If the DB  202  was last updated by the CSC  204 , then the response  236  is a positive response, otherwise response  236  is a negative response. 
     Where the DB  202  provides a positive response  236  to BOS  118 , having also provided a positive response for carrier type  226  recognizing a carrier type and a positive response  230  for the first validation request  228 , then the BOS  118  sends a positive verification response  240  to the EC  102  allowing access to the delivery person. 
     Where the DB provides a negative response  236 , the DB may forward the request  237  for the second validation request to the carrier&#39;s server cloud  204  of the recognized carrier. The CSC  204  can search its own network, including the GBS-based vehicles to locate the delivery vehicle that contains the package and record the tracking information  233  in real-time to DB  202 . The tracking information  238  may include an update to the delivery status; and accordingly, the DB  202  forwards the tracking information  239  to BOS  118 , indicating a status update within the last 24 hours. 
     If the response  239  is a negative response, meaning that the response indicates a last update status beyond the last 24 hours, the BOS  118  sends a negative response  240  the EC  102  denying access to the delivery person. 
       FIG. 5  illustrates a call flow diagram for depositing a package using the locker system, according to embodiments of the present invention. 
     As discussed in step  242  of  FIG. 1 , where the response is a positive response, the EC  102  will permit the delivery person to have access to the locker system  115  for depositing the package at the recipient&#39;s assigned locker/mail box. 
     Referring to  FIG. 5 , the locker system  115  includes a plurality of locker/mail boxes, each assigned to a registered tenant/recipient of the building, as determined by the BOS  118 . The locker system  115  may be separate from or part of the BOS  118 , but must be able to communicate with the BOS  118 . 
     Where the delivery person has been permitted access to the locker system at step  242 , the delivery person may proceed to depositing the package. 
     At step  502 , the delivery person may enter the access code that was displayed on the EC&#39;s display  122  at step  242 . Alternatively, the delivery person, using the barcode scanner of the locker system  115 , may scan the package&#39;s bar code or manually enter the barcode. 
     The access code may have a limited validation window during which the delivery person must use to deposit the package at the locker system. 
     At steps  503  and  504 , where the access code is used to access the recipient&#39;s locker, the locker system may confirm validity of the access code. The locker system  115  confirms the validity of the access code by confirming that the time window has not expired, and further confirming that the access code is associated with a recorded verification response in the local DB  202  and message at step  246  and/or  248  that the package is expected to be deposited at the locker system  118 . 
     At steps  503  and  506 , where the validation window for the access code has expired, or the delivery person has decided to scan or manually input the bar code to access the recipient&#39;s locker, then the locker system  115  along with the local DB  202  and the CSC  204  performs the verification procedure as described with reference to step  212  of  FIG. 2 , and further described in  FIG. 3  and  FIG. 4 . 
     At step  508 , If the verification procedure at step  503  results in a confirmation of the validity of access code at step  504  or a positive response to the verification procedure at step  506 , then the locker system will permit access to the recipient&#39;s locker. 
     If at step  504  the access code determined not be valid, then the locker system will deny access to the recipient&#39;s locker and display a message. The message may indicate that the delivery person should attempt to deposit package using the barcode. Further the message may indicate that the validation window has expired. The message may also indicate that the access code is not associated with a verified response (referring to the response at step  240  of  FIGS. 2, 3 and 4 . 
     If the verification procedure  506  results in a negative response, then the locker system  115  will refuse access to the recipient&#39;s locker and display a message. The message may indicate the reason for the negative response as was discussed above, and reproduced here for convenience. The reason for refusing access may be one or more of the following: unregistered recipient; the carrier is not a registered carrier; package is not “in transit” or “out for delivery”; and last update status is not within the past 24 hours. 
     At step  510 , where the delivery person is permitted access to the recipient&#39;s assigned locker at step  508 , the locker system  115  may notify the recipient&#39;s mobile (RM)  206  via a message that a package addressed to the recipient has been received. The recipient may receive the message via various means including but not limited to email, voice message, text, app notification and/or alert and other means of notifications/messaging. 
     At step  512  and  514 , where access has been granted at step  508 , the locker system  115  will update the tacking information in the DB  202  via a message indicating that the package associated with the scanned barcode has been deposited at the recipient&#39;s assigned locker. 
     At step  514 , the local DB  202  will then notify the CSC  204  that the package has been received at the recipient&#39;s address. 
     Example embodiments described herein provide methods and systems for access to a secured building. Although example embodiments are described in reference to a service provider delivering a package, a person skilled in the art may apply the methods and systems as described by example embodiments herein for access to a building in the case of other service providers, who require access to the building. Accordingly, delivery a package is but one example of a service provider, and thus the methods and systems described herein are not limited to such example. 
     An statements herein reciting principles, aspects and embodiments of the disclosure, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future, i.e., any elements developed that perform the same function, regardless of structure. 
     Other embodiments consistent with the present disclosure will be apparent from consideration of the specification and the practice of the disclosure disclosed therein. Accordingly, the specification and the embodiments disclosed therein are to be considered examples only, with a true scope of the disclosure being disclosed by the following numbered claims.