Distributed sensor system for real-time curbside parking detection and segment length estimation

Abstract

Systems and methods are disclosed for detecting real-time curbside parking availability in unmarked parking areas. A plurality of sensing devices are deployed sequentially along a curb at known intervals and detect the presence or absence of vehicles. Detection data from multiple adjacent devices is aggregated to indirectly estimate the lengths of occupied and available curbside segments. The system operates without requiring physically marked parking spaces or wired infrastructure and supports real-time availability determination, vehicle compatibility assessment, and optional reservation functionality.

Description

SpecificationTitleDistributed Sensor System for Real-Time Curbside Parking Detection and Segment Length EstimationCross-Reference to Related Applications

[0001] This application claims the benefit of U.S. Provisional Patent Application No.63 / 744,046, filed on January 10, 2025, entitled “Enhanced Parking Solution”, the entire contents of which are incorporated herein by reference.Statement Regarding Federally Sponsored Research or Development

[0002] Not applicable.Reference to Sequence Listing, Large Table, or Computer Program Listing Appendix

[0003] Not applicable.Background of the InventionField of the Invention

[0004] The present invention relates generally to intelligent transportation systems and urban mobility technologies, and more particularly to systems and methods for detecting real-time availability of curbside parking areas using distributed sensing devices, estimating the effective length of available and occupied parking segments, and optionally enabling reservation and guidance functionalities.Description of the Related Art

[0005] In dense urban environments, on-street parking is often organized along curbs without fixed or physically marked parking spaces. Unlike off-street parking lots or curbside areas with painted or metered individual spaces, these unmarked curbside zones present significant challenges for automated parking detection systems.

[0006] Existing parking detection solutions typically rely on one sensor per parking space, image-based detection using cameras, or infrastructure requiring extensive cabling and fixed installation. Such approaches are ill-suited for unmarked curbside parking areas, where the number, size, and position of available parking spaces vary dynamically depending on how vehicles are parked.

[0007] Furthermore, many existing systems only provide binary availability information and are unable to determine whether a given available curbside segment is long enough to accommodate a particular vehicle. This limitation leads to inefficient use of curb space, increased cruising time for drivers, traffic congestion, and unnecessary emissions.

[0008] Accordingly, there is a need for a scalable, low-infrastructure system capable of detecting real-time curbside parking availability in unmarked areas, estimating the effective length of available and occupied segments, and optionally supporting higher-level services such as guidance, analytics, and reservation.Brief Summary of the Invention

[0009] The present invention provides systems and methods for detecting real-time availability of curbside parking areas using a plurality of intelligent sensing devices deployed sequentially along parking areas adjacent to a curb, on a roadway-facing side, at known intervals.

[0010] Each sensing device detects the presence or absence of an object within a defined detection range. By aggregating detection data from multiple adjacent sensing devices and accounting for the known spacing between them, the system indirectly estimates the length of occupied and free curbside segments. This approach enables accurate identification of parking availability even in curbside areas that are not physically delimited into individual spaces.

[0011] The sensing devices communicate with one or more central devices, which aggregate and transmit data to a backend server via a network interface. The backend server processes the data to determine real-time parking availability, estimate segment lengths, and identify which vehicle types can fit into available curbside segments.

[0012] The system may provide real-time parking availability information to drivers via a user application or a third-party interface. Reservation functionality may optionally be enabled, allowing certain users to reserve suitable curbside segments under defined conditions. Such reservation functionality is not required for the core detection operation and may be enabled or disabled depending on deployment configuration or policy constraints.

[0013] In addition to availability information, the sensing devices may incorporate one or more visual indicators, such as light-emitting diodes (LEDs), integrated within the device housings and positioned so as to be visible to motorists traveling on the roadway. The visual indicators may be used to support dynamic curbside space management or reservation-based parking, for example by displaying a color-coded status representing availability, occupancy, or reservation of a curbside segment.

[0014] In such implementations, the system may optionally support reservation functionality allowing certain users to reserve suitable curbside segments under defined conditions, for example via a user application. Upon reservation, the visual indicators of the sensing devices associated with the reserved curbside segment may display a reservation status, thereby providing a physical, street-level indication that helps prevent multiple vehicles from simultaneously navigating toward the same available curbside space. Reservation functionality is not required for the core detection operation and may be enabled or disabled depending on deployment configuration, regulatory constraints, or policy choices.Brief Description of the Drawings

[0015] FIG. l is a schematic diagram illustrating an example system architecture for detecting curbside parking availability, including sensing devices deployed along a curb, a central device, a backend server infrastructure, and a user application, together with communication paths therebetween.

[0016] FIG. 2 is a schematic perspective view of an example sensing device, illustrating a protective housing, a sensor opening, and a solar energy harvesting surface.

[0017] FIG. 3 is a schematic perspective view of an example sensing device, illustrating a protective housing, one or more visual indicators, and a solar energy harvesting surface.

[0018] FIG. 4 is a schematic side view illustrating an example sensing device positioned adjacent a curb and oriented to detect a vehicle within an obliquely oriented detection zone.

[0019] FIG. 5 is a schematic top view illustrating estimation of an available curbside parking segment length based on detection states of a plurality of sensing devices deployed along a curb.

[0020] FIG. 6 is a schematic top view illustrating flexible association of sensing devices with multiple central devices across different curbside parking areas.Detailed Description of the InventionSystem Overview

[0021] The system comprises a plurality of sensing devices deployed along one or more curbside parking areas. The sensing devices are installed sequentially at regular or predetermined intervals along a parking area adjacent to a curb, preferably on a side facing the roadway rather than the sidewalk, without requiring that parking spaces be physically marked.

[0022] Each sensing device is configured to detect the presence or absence of an object, such as a vehicle, within a predefined detection zone. Detection may be performed using laser-based sensors, ultrasonic sensors, magnetic sensors, radar, infrared sensors, optical sensors, or any other suitable sensing technology, including combinations thereof.

[0023] The sensing devices communicate with one or more central devices. Each central device aggregates data from an associated group of sensing devices and transmits the aggregated data to a backend server via a network connection. In some embodiments, the backend server exposes an application programming interface (API) through which the system communicates with user applications and / or third-party services.[0023 A] Referring to FIG. 1, a plurality of sensing devices 01 are deployed sequentially along a curbside parking area and are configured to detect presence or absence of vehicles. The sensing devices 01 communicate with a central device 02 via a local wireless communication link 06. The central device 02 aggregates detection data received from the sensing devices 01 and transmits aggregated data to a backend server infrastructure 04 via a network communication link 07.[0023B] The backend server infrastructure 04 comprises one or more server components and one or more data storage components and is accessible through an application programming interface (API) 03. A user device 05 executing a user application communicates with the backend server infrastructure 04 via a communication link 08 to receive real-time parking availability information and, in some embodiments, to request reservation of curbside segments.Sensing Devices — Physical Construction and Durability

[0024] In some embodiments, each sensing device includes a ruggedized housing configured to withstand vehicular loads, impacts, vibration, and environmental exposure. The housing may be waterproof and dustproof and may provide thermal durability across temperature ranges typical of outdoor roadway deployment. In some embodiments, the housing is configured using materials and / or structural features that protect internal electronics while enabling reliable operation under compression or shock events.

[0025] The housing may be configured to allow propagation of radio signals used for wireless communication, for example by using materials or structural windows that are substantially transparent to relevant frequencies, while still maintaining environmental sealing.

[0026] Sensing devices may be low-profile devices configured to be mounted to the roadway surface adjacent the curb, for example in a manner similar to road reflectors, thereby minimizing obstruction and enabling deployment without excavation, drilling, or wiring.[0026A] Referring to FIG. 2, an example sensing device comprises a protective housing 01 configured for roadway deployment. The housing 01 encloses internal electronic components and is configured to withstand mechanical loads, environmental exposure, and thermal variations associated with curbside installation.[0026B] The sensing device further comprises at least one sensor arranged behind a protected opening 02 formed in the housing 01. The opening 02 is configured to allow the sensor to detect objects positioned adjacent the curb while protecting the sensor from direct impact, debris, and environmental ingress.[0026C] In the illustrated embodiment, the sensing device further includes a solar energy harvesting surface 03 positioned on an upper portion of the housing 01. The solar energy harvesting surface 03 is configured to supply electrical power to the sensing device, either alone or in combination with an internal energy storage component.[0026D] Referring to FIG. 3, the sensing device housing 01 may further include one or more visual indicators 02, such as light-emitting diodes, arranged behind a protected opening in the housing 01. The visual indicators 02 are positioned so as to be visible to motorists traveling along the roadway.[0026E] The visual indicators 02 are configured to display different visual states corresponding to parking-related conditions, including availability, occupancy, reservation status, or other curbside management states. The specific colors, patterns, or illumination behaviors associated with each state are implementation-dependent.[0026F] As shown in FIG. 3, the sensing device may further include a solar energy harvesting surface 03 configured to provide electrical power to the sensing device, thereby enabling autonomous operation without wired power connections.Sensing Devices — Sensing Orientation and Detection Behavior

[0027] Each sensing device may include one or more sensors oriented to detect objects located in front of the device and / or within a defined region adjacent the curb. In some embodiments, the sensor axis is oriented at an angle relative to the roadway surface, such as an oblique angle (e.g., approximately 45 degrees, though not limited thereto), to detect the presence of a vehicle body or wheel region facing the device.[0027A] Referring to FIG. 4, a sensing device 01 may be positioned adjacent a curb and configured such that a sensing axis is oriented at an oblique angle relative to the roadway surface. In this configuration, the sensing device 01 detects the presence or absence of a vehicle positioned in front of the sensing device rather than directly above the sensing device.[0027B] The sensing device 01 defines a detection zone 02 extending outward from the sensing device along the sensing axis. The detection zone 02 may encompass a portion of a vehicle body, wheel, bumper, or other vehicle structure positioned adjacent the curb.[0027C] Orienting the sensing axis at an oblique angle allows reliable detection of parked vehicles while reducing sensitivity to non-vehicle objects such as pedestrians, bicycles, or transient objects passing above the sensing device. This configuration further enables the sensing device 01 to be installed close to the curb without requiring vertical clearance above the device.[0027D] The oblique orientation of the sensing axis may correspond to an angle relative to the roadway surface selected based on sensor type, detection range, installation constraints, or desired detection geometry. The angle is not limiting and may vary across implementations.

[0028] Each sensing device may perform detection periodically, continuously, or according to a duty cycle. In some embodiments, sensing devices may enter a low-power mode and wake at intervals to perform detection and communication. In some embodiments, detection may include filtering, confirmation logic, or multi-sample validation to reduce false positives caused by transient objects, pedestrians, weather, or debris.Sensing Devices — Energy Autonomy and Power Management

[0029] The sensing devices are preferably self-powered using one or more energy sources including a battery, a solar cell, or a hybrid combination thereof. In some embodiments, a solar power manager and / or power management circuitry regulates energy capture, charging, and power delivery to internal components.

[0030] In some embodiments, different device versions may be deployed, including a solar-rechargeable variant, a long-life battery variant, or a hybrid variant, depending on the deployment environment, shading conditions, maintenance preferences, or cost constraints.Sensing Devices — Visual Indicators and Local Autonomy

[0031] In some embodiments, sensing devices incorporate one or more visual indicators such as LEDs integrated into the housing and positioned so as to be visible to motorists traveling on the roadway. The LEDs may present different colors, patterns, or intensities to indicate status.

[0032] In some embodiments, the sensing device is configured with a degree of local autonomy such that, upon detecting presence or absence of an object, the sensing device automatically updates a displayed status using the LEDs. For example, a detected occupancy state may cause a first visual state (e.g., a first color), while a vacancy state may cause a second visual state (e.g., a second color). The specific mapping between states and colors is implementationdependent.

[0033] In some embodiments, LED status may also be commanded by the central device (or by the backend server via the central device), for example to indicate reservation status, restricted status, enforcement status, temporary closure, loading-zone status, or other curbside management signals.Sensing Devices — Communication with Central Devices

[0034] Sensing devices communicate with the central device using one or more local wireless protocols. The particular protocol is not limiting and may include peer-to-peer wireless protocols, short-range protocols, mesh protocols, or low-power wide-area protocols. In some embodiments, the protocol supports communication over ranges of multiple meters to multiple tens of meters or more, depending on the environment and antenna configuration.

[0035] In some embodiments, sensing devices connect or synchronize with the central device periodically (e.g., at scheduled intervals) and / or upon state change events (e.g., vacancy-to-occupancy transitions), enabling near real-time updates while maintaining power efficiency.Central Devices — Installation, Mounting, and Power

[0036] Each central device may be configured to manage a parking area (or multiple parking areas) and to aggregate and relay information from a plurality of sensing devices.

[0037] Central devices may be mounted on existing urban furniture, such as poles, signs, or lamp posts. In some embodiments, the central device is mounted using a belt system, clamp system, bracket system, or other non-invasive fixation mechanism, allowing rapid deployment without drilling or permanent modification.

[0038] Central devices may be self-powered, including via a battery, solar energy source, or hybrid solution, and may include a power manager for regulating energy usage. In some embodiments, central devices are configured for long-term autonomous operation with minimal maintenance.[0038A] Referring to FIG. 6, sensing devices deployed within different curbside parking areas may be flexibly associated with one or more central devices. In the illustrated example, sensing devices within a first parking area 01 are communicatively associated with both a first central device 04 and a second central device 05.[0038B] A first central device 04 may aggregate detection data from sensing devices located in multiple parking areas, such as the first parking area 01 and a second parking area 02.Similarly, a second central device 05 may aggregate detection data from sensing devices located in the first parking area 01 and a third parking area 03.[0038C] The association between sensing devices and central devices is not limited by parking area boundaries. In some embodiments, sensing devices within a single parking area may be associated with different central devices based on communication range, signal quality, load balancing, redundancy, installation constraints, or maintenance considerations.[0038D] This flexible association enables scalable deployment, redundancy, and dynamic reconfiguration of the system without requiring physical relocation of sensing devices. Associations between sensing devices and central devices may be defined during installation and may be updated dynamically by the backend server.Communication to Backend Server and Cloud Infrastructure

[0039] Central devices transmit aggregated sensing data to a backend server via a wide-area network connection. The network connection may include cellular-based connectivity, Wi-Fi, wired connectivity, satellite connectivity, or other network technologies, and may use one or more communication protocols such as publish / subscribe protocols, request / response protocols, or lightweight loT protocols. The specific protocol and provider are not limiting.

[0040] The backend server may be implemented on a cloud server platform, serverless infrastructure, one or more application servers, or a hybrid architecture. The backend may include an API layer that supports communication with user applications, central devices, administrative interfaces, and third-party systems.

[0041] The backend may interface with one or more databases for storage of real-time and historical status, device metadata, mapping data, and user data (where permitted). In some embodiments, the backend includes caching systems to accelerate frequently requested data and backup systems for resilience and continuity of operations.Estimation of Parking Segment Lengths

[0042] Unlike systems that associate one sensor with one parking space, the present invention derives parking availability indirectly. By combining detection states from multiple adjacent sensing devices and accounting for the known spacing between them, the backend server estimates the effective length of occupied and free curbside segments.

[0043] For example, a sequence of sensing devices reporting no detected object indicates a free segment whose length corresponds to a function of the distance between the outermost devices in the sequence, and optionally includes additional offsets or calibration parameters depending on sensor placement and detection geometry.

[0044] Similarly, sequences reporting detected objects indicate occupied segments corresponding to parked vehicles, where a vehicle may be confirmed by multiple adjacent devices, improving robustness in unmarked environments.

[0045] This indirect estimation approach allows the system to operate effectively in unmarked curbside environments and to dynamically adapt to varying parking patterns, including uneven spacing, partial occupancy, and variable vehicle lengths.[0045A] Referring to FIG. 5, a plurality of sensing devices are deployed sequentially along a curb 05 adjacent a roadway 06. Each sensing device is configured to detect presence or absence of a vehicle within a respective detection zone along a sensing axis 03.[0045B] In the illustrated example, sensing devices 01 indicate detection of a vehicle and correspond to occupied portions of the curb side parking area, while sensing devices 02 indicate absence of a detected vehicle and correspond to available portions of the curbside parking area.[0045C] The backend server identifies one or more contiguous sequences of sensing devices 02 indicating availability and estimates a length 04 of an available curbside segment based on the number of contiguous sensing devices and predefined spatial intervals between the sensing devices.[0045D] The estimated length 04 represents a usable parking segment that is not physically marked on the roadway and may vary dynamically depending on vehicle positioning and parking behavior. The estimation is performed without requiring predefined parking space boundaries.[0045E] Based on the estimated length 04, the backend server may determine whether the available curbside segment can accommodate a given vehicle and may use the estimated length as input to allocation, guidance, or optional reservation processes.Real-Time Availability and Vehicle Compatibility

[0046] The backend server processes detection data in real time to identify available curbside segments and estimate their lengths. Based on vehicle dimension data provided by users, inferred from vehicle categories, or stored in the system, the server determines whether a given vehicle can fit within a particular available segment.

[0047] Vehicle dimension data may include vehicle type categories (e.g., compact car, sedan, SUV) and associated minimum required segment length or minimum required consecutive sensing devices. Such mappings may be configurable and may vary by region or curb policy.

[0048] Real-time availability information may be communicated to drivers through a user application, embedded navigation system, or third-party interface. In some embodiments, the system provides a set of candidate segments along with suitability indicators.Allocation and Optimization of Suggested Segments

[0049] In some embodiments, when suggesting segments to users (including for reservation), the server may evaluate multiple candidate vacant segments and select an optimal segment using one or more criteria, optionally weighted.

[0050] In some embodiments, the system identifies groups of consecutive vacant sensing devices, forming clusters of available curbside segments for evaluation.

[0051] The system may map vehicle categories to required sensor counts, for example: a first category requiring three consecutive devices, a second category requiring four consecutive devices, and a third category requiring five consecutive devices, though other mappings may be used.

[0052] For each candidate cluster that satisfies a vehicle requirement, the server may compute a space usage metric such as “wastage” or “fragmentation,” for example a difference between total available consecutive devices and the required number for the vehicle.

[0053] In some embodiments, the selection algorithm chooses a candidate that minimizes wastage and reduces space fragmentation, thereby maximizing remaining usable curb space for future users.

[0054] In some embodiments, the selection algorithm additionally accounts for driving access time to the candidate segment, walking distance from the candidate segment to a user’s destination, and / or other operational factors (e.g., approach direction, entry points, turn restrictions, roadworks). In some embodiments, the server selects a segment based on a weighted combination of (i) minimizing walking time, (ii) minimizing driving access time, and (iii) minimizing space wastage.Optional Reservation Functionality (Reservation Layer)

[0055] In some implementations, the system supports optional reservation of curbside segments. Reservation may be enabled only when specific criteria are met, such as proximity of the user to the segment, time constraints, eligibility requirements, regulatory rules, or policy constraints.

[0056] In some embodiments, a user reserves a segment via the user application. The reservation request is processed by the backend server and transmitted to the relevant central device, which then communicates with the sensing devices corresponding to the reserved segment to update LED indicators.

[0057] Reservation status information is communicated to users via the user application or other digital interfaces, thereby reducing the likelihood that multiple vehicles simultaneously navigate toward the same available curb side segment. In addition, the update of LED indicators on the sensing devices associated with a reserved segment provides a physical, street-level indication of reservation status, assisting drivers in identifying segments that are already reserved and discouraging unauthorized occupancy.

[0058] When a segment or parking area is detected as occupied, it is removed from availability and is not eligible for reservation.

[0059] In some embodiments, penalty mechanisms may be applied to discourage unauthorized occupancy of reserved segments. Penalty mechanisms may include financial penalties, account restrictions, reduced access to reservation features, reduced ranking or prioritization, or other enforcement actions, subject to legal and policy constraints.

[0060] Reservation functionality is optional and not required for basic real-time detection and availability estimation. In some deployments, reservation may be disabled without affecting the core availability detection and segment length estimation operation.User Application and Payment

[0061] The user application may allow users to view real-time parking availability near destinations, obtain navigation guidance to selected segments, reserve segments whenpermitted, and pay for parking when payment is required. Payment may be performed through one or more payment processors or payment mechanisms, and the specific payment implementation is not limiting.

[0062] In some embodiments, the user application includes penalty-related workflows, such as notifying users of unauthorized occupancy, processing penalties where permitted, and providing dispute or support mechanisms.Installation, Adhesives, and Digital Twin Mapping

[0063] In some embodiments, sensing devices are installed along a parking area using an adhesive selected to provide strong adhesion to roadway surfaces while allowing removal when necessary for replacement, repair, repositioning, or deinstallation. Removal may be facilitated using mechanical action, thermal action, solvent action, or combinations thereof.

[0064] In some embodiments, devices are installed according to a predefined plan per parking area, and the plan is digitally replicated within the backend, creating a digital map of device placement.

[0065] Each sensing device may have a unique identifier, which may include hierarchical components such as (i) geographic region or city, (ii) parking area identifier, (iii) associated central device identifier, and (iv) sensing device index within the parking area. Additional attributes may include GPS coordinates, installation date, device generation or hardware revision, firmware version, and status information.

[0066] During installation, GPS position and association with a particular central device may be captured and stored in the backend. In some embodiments, a designated central device acts as a primary relay for a defined set of sensing devices.

[0067] The backend may provide monitoring tools to track installation completion, device health, communication status, firmware updates, maintenance schedules, and operational analytics.Data Utilization and Analytics

[0068] Data collected by the system may be stored and analyzed to generate historical parking usage patterns, predict future availability, and support urban planning, traffic management, and logistics optimization.

[0069] In some embodiments, presence / absence data may be combined with other data sources (e.g., time-of-day patterns, weather, events, traffic conditions, regulations) to produce statistical or probabilistic models that help fleet operators or other customers plan routes and curb usage.Non- Limiting Examples and Variations

[0070] The described embodiments are non-limiting. Variations may include different sensing types, different spacing patterns, different communication architectures, different power systems, different reservation policies, and different optimization criteria, without departing from the scope of the claims.

Claims

AMENDED CLAIMSreceived by the International Bureau on 14 June 2026 (14.06.2026)1. A system for detecting real-time curbside parking availability, comprising: a plurality of sensing devices disposed sequentially along a curbside parking area at predefined spatial intervals, each sensing device configured to detect presence or absence of a vehicle within a detection zone, each sensing device having a sensing axis oriented at an oblique angle relative to the roadway surface and the detection zone extending along the sensing axis; at least one central device communicatively coupled to a subset of the plurality of sensing devices; and a server in communication with the at least one central device; wherein the server is configured to: receive detection data from the plurality of sensing devices via the at least one central device; aggregate detection data from multiple adjacent sensing devices; estimate lengths of occupied curbside segments and available curbside segments based on the aggregated detection data and the predefined spatial intervals between sensing devices; and determine whether a candidate vehicle fits within an available curbside segment by comparing the estimated length of that segment to a stored dimension of the candidate vehicle.

2. The system of claim 1, wherein the curbside parking area is not physically divided into individual marked parking spaces.

3. The system of claim 1, wherein estimating the lengths of available curbside segments comprises identifying contiguous sequences of sensing devices indicating absence of a vehicle and computing a segment length based on the number and spacing of the contiguous sensing devices.

4. The system of claim 1, wherein each central device is associated with a plurality of sensing devices and aggregates detection data prior to transmission to the server.

5. The system of claim 1, wherein the sensing devices are wirelessly powered and installed without physical cabling.

6. The system of claim 1, wherein each sensing device is powered by at least one of a battery and a solar energy source.

7. The system of claim 1, further comprising a user interface configured to provide realtime information regarding available curbside segments to a user.

8. A system for optionally reserving curbside parking segments, comprising the system of claim 1 and a user application configured to communicate with the server to request reservation of an available curbside segment; wherein reservation is enabled only after the server determines that the available curbside segment satisfies predefined eligibility criteria, the predefined eligibility criteria including a requirement that a user device be located within a threshold distance of the available curbside segment; and wherein reservation functionality is disabled without affecting real-time detection and estimation of curbside parking availability.

9. The system of claim 8, wherein, upon reservation, the server causes a subset of the plurality of sensing devices associated with the reserved curbside segment to emit a visual indication indicating a reserved status.

10. The system of claim 1, wherein the server is further configured to store historical detection data and generate parking usage analytics.

11. A method for detecting curbside parking availability, comprising: deploying a plurality of sensing devices sequentially along a curbside parking area, each sensing device having a sensing axis oriented at an oblique angle relative to the roadway surface; detecting, by each sensing device, presence or absence of a vehicle; aggregating detection data from multiple adjacent sensing devices; estimating lengths of occupied and available curbside segments based on the aggregated detection data; and determining whether a candidate vehicle fits within an available curbside segment by comparing the estimated length of that segment to a stored dimension of the candidate vehicle.

12. The method of claim 11, wherein the curbside parking area lacks predefined parking space markings.

13. The method of claim 11, further comprising enabling a user to reserve an available curbside segment when reservation criteria are satisfied.Statement under Article 19(1)The claims have been amended to clarify the subject matter the Applicant regards as involving an inventive step, the International Searching Authority having found the claims novel. Independent claims 1 and 11 (method) now recite that each sensing device has a sensing axis oriented at an oblique angle relative to the roadway surface, and that the system and method determine whether a candidate vehicle fits an available curbside segment by comparing the estimated segment length to a stored vehicle dimension. Independent claim 8 now recites granting a reservation only upon a proximity-based eligibility criterion, and permitting the reservation function to be disabled without affecting real-time detection and estimation. These amendments find basis in the claims, description and drawings as originally filed and introduce no new matter. The Applicant submits that the combination of an oblique sensing geometry with indirect segment-length estimation on an unmarked curb and per-vehicle fit assessment involves an inventive step over the cited documents.

Images