Parking lot guiding method and device, terminal and storage medium

Abstract

The invention relates to the technical field of navigation, and discloses a parking lot guiding method and device, a terminal and a storage medium, and the guiding method comprises the steps: responding to a path planning request of a user, and generating an advancing path on a static map of a parking lot based on the current position and a target parking space of the user; dividing the travel path into at least one guide section according to a preset key node; for each guiding section, determining corresponding advancing guiding information; in the advancing process of the user based on the advancing guide information, if an instruction of reaching the end point of the current guide section is received or the predicted advancing duration is exceeded, navigation is suspended, a navigation propelling prompt is generated, and navigation is continued after a navigation continuation instruction is received. According to the invention, the accuracy of indoor vehicle finding and position finding can be improved at low cost.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of navigation technology, in particular to a parking lot guiding method and device, a terminal and a storage medium. BACKGROUND

[0002] With the continuous expansion of indoor parking lot scale and the increasing complexity of structure, the problem of user difficulty in finding a car is becoming increasingly prominent. Existing car finding solutions mainly include hardware positioning systems based on Bluetooth, UWB, etc. and intelligent terminal systems based on image recognition, but both require the deployment of a large number of devices, with high construction and maintenance costs, making it difficult to be popularized and applied in traditional parking lots. Some solutions rely on GPS or mobile phone trajectory records, but in underground environments, navigation signals are missing and positioning fails. In addition, existing static map guidance lacks direction guidance and process confirmation mechanisms, and users are prone to deviate from the path and cannot be corrected in time. SUMMARY

[0003] Therefore, the embodiments of the present application provide a parking lot guiding method, device, terminal and storage medium.

[0004] In a first aspect, the embodiments of the present application provide a parking lot guiding method applied to an electronic terminal, comprising: In response to a user's path planning request, a travel path is generated on a static map of a parking lot based on the user's current location and a target parking space; According to a preset key node, the travel path is divided into at least one guiding segment; For each guiding segment, corresponding travel guidance information is determined; During the user's travel based on the travel guidance information, if an instruction to reach the end of the current guiding segment or an expected travel time is exceeded is received, navigation is paused and a navigation promotion prompt is generated, and after a continue navigation instruction is received, navigation is continued.

[0005] In an optional implementation, it further includes: at any moment during the travel process, in response to a user-initiated repositioning operation instruction, current position information of the electronic terminal is extracted; According to the current position information, a new navigation starting point is taken; based on the new navigation starting point and the target parking space, a subsequent travel path is regenerated.

[0006] In an optional implementation, the key node is a key location point with a spatial feature or a functional identifier in the parking lot; and the dividing of the travel path into at least one guiding segment according to the preset key node includes: According to the preset key node, a plurality of guiding segment breakpoints are set on the travel path, and a plurality of continuous guiding segments are formed in units of paths between adjacent two guiding segment breakpoints.

[0007] In an optional implementation, the determining, for each of the guide segments, the travel instruction information based on the guide module built in the electronic terminal comprises: For each of the guide segments, a predetermined travel direction and path length from a starting point to an ending point are determined, and a predicted travel duration of the current guide segment is generated according to a travel speed mode set by the user; The travel instruction information is generated based on the travel direction, the path length and the predicted travel duration, and is output on the electronic terminal to guide the user to complete the walking of the current guide segment; wherein when the user starts to perform the current guide segment, the orientation of the electronic terminal monitored by the guide module built in the electronic terminal is acquired and displayed to enable the user to check whether the walking direction of the user is consistent with the predetermined travel direction.

[0008] In an optional implementation, the real scene information is pre-associated at at least one of the key nodes; the real scene information is displayed through a real scene image or an AR diagram; the method further comprises: In response to a real scene viewing operation of the user on the key node, the corresponding real scene information is displayed for the user to compare with the actual environment and determine whether the current walking path is correct.

[0009] In an optional implementation, the method further comprises: converting the predicted travel duration into countdown information, and outputting the countdown information on the display interface of the electronic terminal in at least one of a countdown progress bar, a digital timer or a voice period broadcast; When the predicted travel duration is exceeded and the continue navigation instruction is not received within a preset time period after the navigation promotion prompt is generated, a path deviation warning prompt is generated to guide the user to perform a repositioning operation.

[0010] In an optional implementation, the static map comprises a parking lot topology structure composed of topology nodes and connection edges, and a hierarchical map display graph from a partition overview map to a parking space detailed map; wherein the topology node is a feature position point with a direction guiding function; and the connection edge represents a feasible path between adjacent topology nodes.

[0011] In a second aspect, an embodiment of the present application provides a parking lot guide device applied to an electronic device, comprising: A planning module configured to generate a travel path on a static map of a parking lot based on a current position and a target parking space of a user in response to a path planning request of the user; A division module configured to divide the travel path into at least one guide segment according to a preset key node; An output module configured to determine corresponding travel instruction information for each of the guide segments; The confirmation module is used to pause navigation and generate a navigation progress prompt when the user receives an instruction to reach the end of the current guidance segment or exceeds the expected travel time during the user's journey based on the travel guidance information. After receiving a instruction to continue navigation, navigation will resume.

[0012] Thirdly, embodiments of this application provide a terminal device, the terminal device including a processor and a memory, the memory storing a computer program, and the processor executing the computer program to implement the above-described parking guidance method.

[0013] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed on a processor, implements the above-described parking guidance method.

[0014] The embodiments of this application have the following beneficial effects: This application generates a travel path based on a static map and divides it into multiple guidance segments according to preset key nodes. Then, for each guidance segment, its corresponding travel guidance information is determined, thereby achieving direction perception without relying on external positioning devices. Navigation is paused and the user is prompted to confirm the location upon reaching the end of the guidance segment or upon timeout, thus effectively preventing the accumulation of path deviations. This application does not require the deployment of hardware such as Bluetooth or UWB, thereby improving the accuracy and reliability of indoor vehicle finding and positioning at a low cost. Attached Figure Description

[0015] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0016] Figure 1 A flowchart illustrating a static map construction method according to an embodiment of this application is shown. Figure 2 A first flowchart of a parking guidance method according to an embodiment of this application is shown; Figure 3 This paper illustrates a second flowchart of a parking guidance method according to an embodiment of the present application. Figure 4 A third flowchart of the parking guidance method according to an embodiment of this application is shown; Figure 5 This illustration shows a scenario diagram of a parking lot guidance method according to an embodiment of this application; Figure 6 A schematic diagram of a parking guidance device according to an embodiment of this application is shown. Detailed Implementation

[0017] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0018] The components of the embodiments of this application described and illustrated in the accompanying drawings can be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of this application provided in the drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0019] In the following text, the terms "comprising," "having," and their cognates, which may be used in various embodiments of this application, are intended only to indicate a particular feature, number, step, operation, element, component, or combination thereof, and should not be construed as primarily excluding the presence of one or more other features, numbers, steps, operations, elements, components, or combinations thereof, or adding the possibility of one or more combinations thereof. Furthermore, the terms "first," "second," "third," etc., are used only for distinguishing descriptions and should not be construed as indicating or implying relative importance.

[0020] Unless otherwise specified, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which the various embodiments of this application pertain. Terms (such as those defined in commonly used dictionaries) shall be interpreted as having the same meaning as in their contextual meaning in the relevant technical field and shall not be construed as having an idealized or overly formal meaning, unless clearly defined in the various embodiments of this application.

[0021] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0022] With the acceleration of urbanization and the continuous growth of motor vehicle ownership, large underground or multi-level parking lots have become standard facilities in public places such as commercial complexes, transportation hubs, hospitals, and office buildings. However, due to the complex internal structure, crisscrossing passages, dense parking spaces, and lack of visual references in these parking lots, users often find it difficult to accurately remember their parking location after parking, leading to the common problem of "difficulty in finding their car" when retrieving it. At the same time, in the case of reserved parking spaces, users often have difficulty quickly locating their target parking space after entering the parking lot due to the lack of effective guidance, which seriously affects the user experience.

[0023] To address the aforementioned issues, existing technologies have proposed various indoor vehicle or parking space location solutions, mainly falling into the following three categories: The first category is hardware-based dynamic navigation systems. This type of solution deploys Bluetooth beacons, ultra-wideband (UWB) positioning base stations, or Wi-Fi fingerprint recognition devices within parking lots, combining these with mobile terminals to achieve high-precision positioning and continuous path guidance. However, implementing this type of system requires modifications to the parking lot infrastructure, involving multiple stages such as equipment installation, network cabling, and system debugging. Construction and maintenance costs are high, and deployment is particularly difficult in traditional existing parking lots, limiting its applicability.

[0024] The second type is intelligent car-finding terminal systems based on image recognition. These solutions typically deploy cameras and car-finding kiosks in various areas of the parking lot, using license plate recognition technology to record vehicle parking locations. Users can obtain parking space information and map guidance by entering their license plate number. This type of system relies on high-density surveillance coverage and strong backend image processing capabilities, which not only presents challenges to data security and privacy protection, but also provides guidance information primarily through static map displays, lacking directional awareness and real-time interactive mechanisms. Users are still prone to deviating from their intended path in complex environments.

[0025] The third category is smartphone-based functional assistance solutions. For example, using a phone's GNSS module to record parking coordinates, or overlaying virtual navigation signs using augmented reality (AR) technology. However, due to severe attenuation or even complete absence of GNSS signals in indoor environments, positioning results are unreliable. AR navigation, on the other hand, requires continuous camera access to capture environmental images, placing high demands on device performance, battery life, and ease of operation. It also performs unstably in low-light, crowded, or limited-view scenarios, restricting its widespread application.

[0026] Furthermore, the aforementioned solutions generally lack effective monitoring and phased confirmation mechanisms for the user's progress. Once a user deviates from the planned path, the system struggles to detect and provide corrective guidance in a timely manner, easily leading to continuous misjudgments. Especially in the absence of continuous positioning support, ensuring that users progress step by step along the predetermined path remains a technical challenge that has not yet been properly resolved.

[0027] Based on this, this embodiment provides a parking lot guidance method, aiming to achieve efficient, reliable, and low-cost indoor vehicle finding and location services in parking lots without GNSS signals, without relying on dedicated positioning equipment. This method improves the user's navigation accuracy and experience in complex indoor spaces by constructing a hierarchical map display with a topological structure, and combining segmented guidance, initial direction perception, human-machine collaborative confirmation, and path correction mechanisms.

[0028] First, the method for constructing the static map used in this embodiment will be explained, such as... Figure 1 As shown, the static map construction method includes steps S110-S130: Step S110: Obtain the design drawings of the parking lot, and based on the spatial layout information and semantic annotation information in the design drawings, use the triangulation algorithm to perform grid processing on the design drawings to generate a path topology network composed of topological nodes and connecting edges.

[0029] In this context, topological nodes are characteristic location points that provide directional guidance, such as intersections, turning points, or places where people can stay on a lane; connecting edges represent feasible paths between adjacent topological nodes.

[0030] The design drawings are in electronic format (such as DWG, DXF, and other CAD files), containing spatial layout information and semantic annotation information. Spatial layout information refers to the spatial geometric data of the parking lot's physical structure, including lane centerlines, wall outlines, column positions, turning radii, and passage widths, used to determine the traversable space and path boundaries for users. Semantic annotation information refers to text or symbolic markings that assign functional meanings to specific locations, such as "Area A," "Parking Space B2001," "Elevator Lobby," "Entrance / Exit," and "Fire Hydrant," used to identify key areas and navigation reference points.

[0031] Based on the above information, the server uses a triangulation algorithm (such as the Delaunay triangulation algorithm) to geometrically mesh the passable area of ​​the parking lot. The specific process is as follows: First, the lane area is abstracted into a two-dimensional planar space; then, areas occupied by obstacles such as walls and pillars are removed, retaining free space for pedestrians; next, multiple sampling points are inserted into this free space, and a triangulation algorithm is applied to generate non-overlapping triangular meshes; then, key locations are extracted from the intersections of the mesh vertices and boundaries as topological nodes, including intersections where lanes meet, turning points where directions change significantly, and easily identifiable and locating locations for users (such as near elevator lobbies or main passage intersections); finally, for any two adjacent and unobstructed connected topological nodes, a connecting edge is established to represent the reachable path between them, and the actual distance or estimated walking cost is recorded. The final path topology is stored in graph form, providing a foundation for subsequent path planning and navigation guidance.

[0032] Step S120: Based on the topology, the parking lot is divided into multiple logical areas according to the pre-marked area division information.

[0033] Each logical area contains numbered parking spaces.

[0034] The zoning information consists of functional zoning rules pre-marked during the map modeling stage, used to define the spatial organization structure of the parking lot. This information can be entered manually or through system presets, and includes, but is not limited to: zone identifiers based on geographical scope (such as "Zone A", "Zone B", "Zone C"), floor numbers based on building floors (such as "B1", "B2"), and zone types based on functional use (such as "near-end parking area", "far-end parking area", "VIP area", "charging parking area"), etc.

[0035] This area division information is associated with topological nodes and connecting edges as metadata, and is used to construct a hierarchical map semantic system.

[0036] Based on this, the server performs affiliation analysis on each topological node in the path topology network and its associated parking spaces according to the regional division information, and assigns all nodes and parking spaces belonging to the same regional identifier to the corresponding logical region. Each logical region contains several parking spaces with unique numbers (such as A1002, A1001), and these numbers follow the standard naming rules of the parking lot operation management system and are automatically synchronized during the map modeling process to ensure complete consistency with the physical identification on site.

[0037] This partitioning method allows users to select target areas during subsequent navigation, enabling precise location of specific parking spaces and significantly improving route planning efficiency and ease of use. Simultaneously, it preserves complete connectivity topology between logical areas, ensuring continuity and accuracy in cross-area route planning.

[0038] Step S130: Construct a hierarchical map display graphic from the zoning overview map to the parking space detail map to generate a static map of the parking lot used in the parking lot guidance method.

[0039] This step primarily involves constructing a hierarchical map display structure from macro to micro levels to support efficient browsing and precise positioning for users. Specifically, based on the generated path topology and logical region division results, a two-level map display structure is constructed: the upper layer is a zone overview map, and the lower layer is a detailed parking space map.

[0040] The zoning overview map presents the overall layout of the entire parking lot in a simplified form, showing only the core elements such as each logical area (e.g., area A, area B), main roads, key entrances and exits, and elevator lobbies, making it easy for users to quickly identify their current area or target direction. When a user selects a logical area, they can enter the corresponding detailed parking space map by clicking or zooming. This map finely displays the boundary outlines, numbering labels, lane directions, and local path topology of all parking spaces in the area, supporting high-precision navigation guidance.

[0041] This hierarchical display structure is achieved through map zoom levels and layer switching mechanisms. Map data at different levels is stored independently and loaded on demand to improve rendering efficiency and response speed. Users can trigger a "drill-down browsing mode" via gestures (such as double-tap and pinch to zoom) or interface buttons to progressively acquire information from "overall—region—parking space". Simultaneously, the system maintains the continuity of the current location and navigation path during layer switching, avoiding interruptions to the user experience. This design effectively reduces information overload in complex indoor environments, improving map usability and human-computer interaction efficiency.

[0042] After completing the hierarchical map construction, the server packages a static map data package containing path topology network, logical region division information, key node annotations, and real-world binding data. This package is then published to one or more electronic terminal devices via a wireless communication interface for use in vehicle location or parking space navigation when real-time positioning is unavailable. These electronic terminals can be user mobile terminals (such as smartphones, tablets, wearable devices, etc.) or in-vehicle terminals. When used in scenarios where a vehicle enters a parking lot and searches for a target parking space, the user can receive and display navigation guidance through the in-vehicle terminal or mobile terminal. When used in scenarios where the user is retrieving their vehicle, they can obtain their current location through their mobile terminal and initiate a reverse vehicle location navigation process.

[0043] The parking lot guidance method will be explained below with reference to some specific embodiments.

[0044] Figure 2 A schematic flowchart of a parking guidance method according to an embodiment of this application is shown.

[0045] Step S210: In response to the user's route planning request, a travel route is generated on the static map of the parking lot based on the user's current location and the target parking space.

[0046] Before step S210, a static map needs to be retrieved first. Specifically, when a user initiates a car-finding or parking space navigation request, the electronic terminal establishes a communication connection with a remote server via a wireless network. Based on the user's current location or the target parking lot selected by the user, the server determines the target parking lot, retrieves the corresponding static map from a pre-stored map database, and sends it to the electronic terminal. The static map includes a path topology and hierarchical map display graphics, and has been pre-modeled and published on the server. After receiving the static map, the electronic terminal loads and renders it locally for subsequent route planning and segmented guidance. This map data can support offline caching, making it suitable for scenarios without a continuous network connection, such as underground parking lots.

[0047] In step S210, in response to the user's route planning request, a feasible route from the current location to the target parking space is generated based on the received static map. Specifically, when the user initiates a route planning operation through an application on a mobile terminal, the system first obtains the starting point and destination information for navigation. The starting point can be obtained by the user manually selecting a nearby parking space number, scanning a QR code for on-site positioning, voice input of location information, or automatic identification based on the previous parking record; the destination is the target parking space, which is usually selected by the user by clicking on the map interface, or automatically filled in through reservation information, history, etc.

[0048] After obtaining the starting and ending points, a path planning algorithm (such as Dijkstra's algorithm or A* algorithm) can be used to search for a path based on the pre-defined path topology in the static map. This search process uses topological nodes as the basic unit, assigning weights to connecting edges based on actual distance, traversal difficulty, or preset priorities to ensure the generated path is optimal or near-optimal reachable. Once calculated, the path can be overlaid on the static map as a highlighted line, labeled with directional arrows, key node hints, and total length, forming a complete visual guide route. The generated path not only meets connectivity and reachability requirements but also considers ease of walking and user cognitive habits, such as avoiding narrow passages, reducing the number of turns, and prioritizing main roads, thereby improving the navigation experience. This path serves as the basis for subsequent segmented guidance, used to divide guidance segments, output directional guidance, and execute manual confirmation procedures.

[0049] Step S220: Divide the travel path into at least one guide segment according to the preset key nodes.

[0050] To address the risk of path deviation due to the lack of continuous positioning during static map navigation, this embodiment employs a structured segmentation mechanism, breaking down the complete navigation process into several independently executable and manually verifiable sub-task units. Each guidance segment corresponds to a path interval with a clearly defined start and end point. Users can pause navigation after completing the current guidance segment to verify the consistency between their actual location and the expected path before proceeding to the next guidance segment. This segmented guidance mode effectively suppresses the cumulative propagation of navigation errors, significantly improving the reliability and user experience of indoor vehicle or parking location searches, and is particularly suitable for traditional parking lot environments without real-time positioning equipment support.

[0051] In some implementations, such as Figure 3 As shown, step S220 further includes steps S310-S320: Step S310: Based on preset key nodes, set multiple guide segment breakpoints on the travel path.

[0052] In this step, multiple guide segment breakpoints are automatically identified and set on the generated travel path based on the preset key node types.

[0053] Key nodes refer to locations within a parking lot that possess significant spatial characteristics or functional identifiers, providing users with clear directional guidance or positioning references. Specifically, key nodes include, but are not limited to: intersections where lanes intersect or branch, elevator lobbies where people gather and disperse, common destinations such as restrooms and car wash areas, and fixed facilities such as fire hydrants. These nodes are labeled as topological nodes with specific semantics during the map modeling phase and distributed to electronic terminals along with the static map. The electronic terminals automatically set such nodes located on the path as guide segment breakpoints by matching the spatial relationship between the travel path and the key nodes.

[0054] Step S320: Multiple consecutive guide segments are formed, taking the path between two adjacent guide segment breakpoints as a unit.

[0055] In this step, the electronic terminal divides the path between two adjacent guide segment breakpoints into multiple continuous guide segments. Each guide segment represents an independent, executable navigation sub-path, with both its start and end points being key points, and its length being moderate (typically 15–50 meters) to ensure that the user can clearly identify the start and end markers while walking. All guide segments are sequentially connected, covering the complete path from the current location to the target parking space. This segmented structure not only facilitates step-by-step guidance and manual confirmation but also provides basic unit support for subsequent directional prompts, time estimation, and real-world comparison.

[0056] Step S230: For each guide segment, determine the corresponding travel guidance information.

[0057] This step aims to achieve an intuitive and reliable simulated navigation experience without continuous positioning support by utilizing the terminal's own sensors and multimodal interaction mechanisms. Specifically, such as... Figure 5 As shown, for each divided guidance segment, the system combines the path geometry features in the static map with the guidance module data of the electronic terminal (the guidance module includes one or more of a gyroscope, accelerometer, and magnetometer, used to detect the spatial attitude and orientation of the electronic terminal) to generate travel guidance information containing the predetermined travel direction, path length, and estimated travel time, or generates guidance information that does not include a specific travel direction but provides guidance to a certain node (such as an elevator, a specific parking space, etc.). This information is output to the user interface through text, graphics, or voice to help the user accurately identify the walking direction and complete the current guidance segment.

[0058] In some implementations, such as Figure 4 As shown, step S230 includes steps S410-S430: Step S410: For each guide segment, determine the predetermined travel direction and path length from the starting point to the end point, and generate the estimated travel time of the current guide segment according to the travel speed mode set by the user.

[0059] In this step, based on the coordinates of the start and end points of each guide segment in the static map, the direction of travel is determined through vector operations. This direction is represented as a deflection angle relative to true north or the previous path segment (e.g., "30° to the right and forward"), and then converted into a user-friendly directional description (e.g., "go straight ahead," "turn left," etc.). The path length is obtained by summing the actual distances of the connecting edges in the topology network.

[0060] Based on this, such as Figure 5 As shown, the system generates the estimated travel time for the current guidance segment based on the user's pre-set travel speed mode. This travel speed mode includes several preset movement rate configurations. Users can select the appropriate speed level based on their actual mode of movement (e.g., walking, driving) or personal habits, such as: slow (e.g., 1.0 m / s), normal speed (e.g., 1.2 m / s), fast (e.g., 1.5 m / s), or low-speed driving mode (e.g., 1.4 m / s). When generating the estimated travel time, users can manually select a speed mode based on the travel speed mode. The system then divides the path length by the selected speed to obtain the estimated travel time (e.g., "approximately 25 seconds"), which serves as the basis for subsequent rhythm control. In essence, the travel speed mode is a set of speed parameters set based on experience, used to estimate the reasonable time consumption for each path segment, serving as a time benchmark for subsequent countdowns and anomaly detection.

[0061] Step S420: Based on the direction of travel, path length and estimated travel time, generate travel guidance information and output it on the electronic terminal to guide the user to complete the current guided segment.

[0062] This step generates user-oriented travel guidance information based on the travel direction, path length, and estimated travel time obtained from the previous steps. The guidance information must include at least one of the following formats: text prompts, graphic arrows, or voice announcements.

[0063] The text prompts display operation instructions in natural language, such as "Please walk straight ahead for about 30 meters" or "Walk to the right front, estimated arrival time is 25 seconds"; the graphic arrows are dynamic arrow icons superimposed on the map view or full-screen navigation mode of the terminal interface to intuitively indicate the direction of walking; the voice broadcast can play pre-recorded or synthesized voice through the speaker to prompt the walking requirements of the current guidance segment, such as "Now start, please walk to the left along the passage".

[0064] The above information can be used individually or in combination, supporting personalized configuration by users according to their preferences. The system renders the guidance information to the terminal interface in real time and continuously updates status information such as remaining distance and countdown during navigation. This embodiment, through a multimodal collaborative guidance mechanism, enables users to accurately understand and execute the walking task of the current guidance segment even in complex intersections or environments with few visual references, significantly improving the usability and user experience of static map guidance.

[0065] Understandably, when a user begins executing the current guided segment, the orientation of the electronic terminal, monitored by the built-in guidance module, can be obtained and displayed so that the user can check whether their walking direction is consistent with the predetermined direction of travel.

[0066] As an example, when a user begins the current guided navigation segment, the system obtains the device's current orientation monitored by the built-in guidance module of the electronic terminal, and dynamically adjusts the rotation angle of directional indicators on the screen (such as navigation arrows) accordingly to ensure their pointing is consistent with the actual spatial orientation. Specifically, when the user clicks "Start Navigation" or confirms entry into the current guided navigation segment, the system calls the gyroscope to obtain the device's yaw angle data. If the intended direction of travel is forward and the gyroscope detects that the phone is currently pointing to the right, the arrow on the interface will automatically rotate to the right, prompting the user to correct their hand position to the left. This processing only occurs at the initial stage of the guided navigation segment and is used to assist in orientation perception. It does not require continuous position tracking and is therefore unaffected by gyroscope drift, making it suitable for environments without GNSS signals, such as underground parking lots. In this way, users can quickly determine whether their direction of travel is correct by comparing the correspondence between the arrows on the screen and the physical environment, thereby reducing the barrier to understanding abstract maps and improving navigation usability.

[0067] Specifically, after the current guided segment begins, the system automatically starts a countdown timer, providing real-time feedback to the user on the expected completion time for this segment. When the countdown ends and the user has not yet reached the end of the current guided segment and has not performed a location confirmation operation, the system generates a route deviation warning and pauses the navigation process. The warning is presented through an interface pop-up and an audio alert, such as displaying: "You have exceeded the estimated time. Please check if your current location is correct." Simultaneously, the system guides the user into a repositioning process and provides quick access options such as "voice input of parking space number," "scanning a QR code," or "viewing a real-view image for comparison" to assist the user in reconfirming their current location and resuming navigation.

[0068] Step S240: During the user's journey based on the travel guidance information, if an instruction to reach the end of the current guidance segment is received or the expected travel time is exceeded, navigation is paused and a navigation progress prompt is generated. After receiving a continued navigation instruction, navigation resumes.

[0069] As an example, once the user completes the current guided segment, the system, in response to the user's confirmation command indicating arrival at the end of the segment, automatically pauses the navigation process and displays a navigation progress prompt on the electronic terminal interface. This prompt reminds the user to stop and verify that the current location matches the expected location. The confirmation command is triggered through at least one of the following interactive methods: clicking the "Confirm Arrival" or "Continue" button on the interface; issuing a preset voice command (such as "I've arrived") and having it parsed by the voice recognition module; scanning the location QR code at a key node; or entering the currently visible parking space number.

[0070] Navigation prompts can be presented in the form of text prompts (such as "You have arrived at the elevator lobby. Please confirm that you are on the right track"), highlighted graphic icons, or voice announcements (such as "Please check if your current location matches") to guide users to visually observe the surrounding environment (such as referring to on-site signs, parking space numbers, or linked real-world images) to determine whether they are on the correct path.

[0071] If the user clicks the "Confirm" or "Continue" button, the path data for the next guidance segment will be automatically loaded, and the navigation will enter the directional guidance preparation state for that segment. If the user does not perform any operation within the preset time period, or actively selects the "Position Deviation" option, the navigation will remain paused, waiting for further interaction instructions.

[0072] In some implementations, the preset time period can be set to 10 to 15 seconds to wait for user response after generating navigation progress prompts. If no navigation continuation instruction is received during this period, the system determines that the user may have deviated from the path, thereby triggering a path deviation warning to remind the user that there may be a route error, and guiding the user to perform repositioning operations, such as scanning a nearby QR code, entering a parking space number, or viewing real-view images of key nodes for calibration.

[0073] This method, by setting periodic pause points and introducing manual confirmation into the navigation process, can effectively block the cumulative propagation of path deviations, thereby improving the reliability and accuracy of static map guidance in environments without continuous positioning.

[0074] In some implementations, the method further includes: at any point during the journey, in response to a user-initiated relocation command, extracting the current location information of the electronic terminal; using the current location information as a new navigation starting point; and regenerating the subsequent travel path based on the new navigation starting point and the target parking space. The relocation command is triggered by voice input of the parking space number, scanning a QR code at the location site, or image recognition of the parking space number.

[0075] It is understood that this embodiment also includes a dynamic relocation function during the journey to address situations where the user deviates from the path or the initial positioning is incorrect. Specifically, at any point during navigation execution, the system continuously listens for relocation operation commands initiated by the user. When a relocation request is detected, the system first extracts the current location information carried in the command. Relocation operation commands can be triggered in several ways: the user can input the currently visible parking space number (such as "A1002") via voice, and the system can call the voice recognition module for semantic parsing; or the user can scan the on-site positioning QR code posted on a pillar, wall, or parking space to obtain a preset location code; or the user can activate the camera to photograph nearby parking space signs and automatically extract the parking space number from the image using optical character recognition (OCR) technology.

[0076] The system matches the acquired current location information with pre-stored geographic coordinate data in a static electronic map to determine the corresponding topological node as the new navigation starting point. Then, based on this new starting point and the original target parking space, the path planning algorithm is invoked again to generate the remaining travel path from the current location to the target parking space, and the system automatically enters the navigation preparation state for the next guidance segment. This relocation mechanism supports discontinuous, non-real-time positioning correction, achieving efficient and convenient path recovery without relying on hardware facilities such as Bluetooth or UWB, significantly improving the fault tolerance of the navigation system and the user experience.

[0077] In some implementations, the method further includes: pre-associating real-world information at at least one key node; displaying the real-world information through real-world images or augmented reality (AR) illustrations; and displaying the corresponding real-world information in response to the user's real-world viewing operation at the key node, so that the user can compare it with the actual environment and determine whether the user's current walking path is correct.

[0078] It is understood that this embodiment pre-associates real-world information at at least one key node to enhance the user's ability to identify their current location. Key nodes include locations with significant visual features or functional identifiers, such as intersections, elevator lobbies, restrooms, car wash areas, or fire hydrants. During the map modeling phase, operators or system administrators upload real-world images (such as on-site photos) or preset augmented reality (AR) illustrations (such as virtual arrows or label overlay templates) corresponding to the node through the management platform, and bind these images to the node's geographic coordinates on a static electronic map to form visual reference data.

[0079] During navigation, when a user approaches a key node, the system provides a "Real-View" entry (such as a button or icon) on the electronic terminal interface. In response to the user's click or long-press action on the node, the system retrieves and displays the associated real-view information. The user can compare the real-view image or AR icon on the screen with the surrounding real environment to determine if they are in the correct location. For example, before reaching the elevator lobby, the user can compare the image with a pre-captured photo of the elevator nameplate on the screen to confirm whether the current floor and direction match. This function does not require real-time image acquisition or continuous AR rendering; it loads images only when needed, reducing device resource consumption and effectively assisting users in verifying their route, preventing deviations caused by visual confusion.

[0080] This embodiment constructs a segmented guidance mechanism based on a static map, achieving efficient, reliable, and low-cost indoor parking lot vehicle location and parking space guidance without deploying additional positioning hardware such as Bluetooth or UWB. Furthermore, this embodiment automatically divides the complete navigation path into multiple guidance segments based on key nodes such as intersections, elevator lobbies, and restrooms, pausing navigation at the end of each segment to prompt the user for location confirmation. This effectively prevents the accumulation of path deviations caused by a lack of continuous positioning, significantly improving the accuracy of the navigation process and user trust. Additionally, utilizing the gyroscope built into the electronic terminal, the system can accurately identify the direction of travel at the start and output directional guidance through various methods such as text prompts, graphic arrows, and voice broadcasts, helping users effectively associate the screen display with their actual spatial location and lowering the barrier to understanding abstract maps. For situations where users may take the wrong path, rapid relocation is supported through voice input of parking space numbers, scanning on-site QR codes, or image recognition. The system then replans the subsequent route accordingly, further enhancing the fault tolerance and flexibility of the overall guidance process. It is understood that this embodiment makes full use of the sensor and communication capabilities already available in the electronic terminal, without relying on high-power AR continuous rendering or complex real-time image recognition. It has the advantages of low power consumption, strong adaptability to weak networks, and simple operation, and is especially suitable for the intelligent upgrade of traditional existing parking lots. It has wide applicability and a good user experience.

[0081] This application also provides a static map construction method, including: obtaining the design drawings of a parking lot, and based on the spatial layout information and semantic annotation information in the design drawings, using a triangulation algorithm to perform gridding processing on the design drawings to generate a path topology network composed of topological nodes and connecting edges; wherein, the topological nodes are feature location points with directional guidance; the connecting edges represent feasible paths between adjacent topological nodes; based on the topology, according to pre-annotated area division information, the parking lot is divided into multiple logical areas; wherein, each logical area contains numbered parking spaces; and a hierarchical map display graphic from a zone overview map to a detailed parking space map is constructed to generate a static map of the parking lot used in the parking lot guidance method.

[0082] As can be understood, this embodiment uses a triangulation algorithm to mesh the passable area of ​​the parking lot, removing the space occupied by obstacles such as walls and pillars, inserting sampling points within the free area, and generating a Delaunay triangular mesh. Subsequently, feature points with directional guidance are extracted as topological nodes, such as lane intersections, obvious turning points, or areas in front of elevator lobbies, and connecting edges are established between adjacent barrier-free connected nodes, forming a graph structure that can be searched using A* or Dijkstra algorithms.

[0083] The specific implementation of this static map construction method has been described in the above embodiments, so it will not be repeated here.

[0084] Figure 6 A schematic diagram of a parking guidance device according to an embodiment of this application is shown. Exemplarily, the parking guidance device includes: The planning module 100 is used to respond to the user's route planning request and generate a travel route on the static map of the parking lot based on the user's current location and target parking space.

[0085] The segmentation module 200 is used to divide the travel path into at least one guide segment based on preset key nodes.

[0086] The output module 300 is used to determine the corresponding travel guidance information for each guide segment.

[0087] The confirmation module 400 is used to pause navigation and generate a navigation progress prompt when the user receives an instruction to reach the end of the current guidance segment or exceeds the expected travel time during the process of traveling based on the travel guidance information. After receiving the instruction to continue navigation, navigation will continue.

[0088] It is understood that the device in this embodiment corresponds to the parking lot guidance method in the above embodiment, and the options in the above embodiment are also applicable to this embodiment, so they will not be described again here.

[0089] This application also provides a terminal device, exemplary of which includes a processor and a memory, wherein the memory stores a computer program, and the processor executes the computer program to enable the terminal device to perform the parking guidance method or the static map construction method described above.

[0090] The processor can be an integrated circuit chip with signal processing capabilities. The processor can be a general-purpose processor, including at least one of a Central Processing Unit (CPU), Graphics Processing Unit (GPU), Network Processor (NP), Digital Signal Processor (DSP), Application-Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor or any conventional processor, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application.

[0091] The memory can be, but is not limited to, Random Access Memory (RAM), Read Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), etc. The memory is used to store computer programs, and the processor can execute the computer programs accordingly after receiving execution instructions.

[0092] This application also provides a computer-readable storage medium for storing the computer program used in the aforementioned terminal device. For example, the computer-readable storage medium may include, but is not limited to, various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0093] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings show the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that, in alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0094] In addition, the functional modules or units in the various embodiments of this application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0095] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a smartphone, personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.

[0096] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A parking lot guidance method, characterized in that, Applied to electronic terminals, including: In response to the user's route planning request, a travel route is generated on the static map of the parking lot based on the user's current location and target parking space; Based on preset key nodes, the travel path is divided into at least one guiding segment; For each of the aforementioned guide segments, determine the corresponding travel guidance information; If, during the user's journey based on the travel guidance information, an instruction to reach the end of the current guidance segment is received or the expected travel time is exceeded, navigation is paused and a navigation progress prompt is generated. Navigation resumes upon receiving a continued navigation instruction.

2. The parking lot guidance method according to claim 1, characterized in that, Also includes: At any point during the journey, in response to a user-initiated relocation command, the current location information of the electronic terminal is extracted. Based on the current location information, use it as the new navigation starting point; Based on the new navigation starting point and the target parking space, the subsequent travel path is regenerated.

3. The parking lot guidance method according to claim 1, characterized in that, The key nodes are key location points within the parking lot that have spatial characteristics or functional identifiers. The step of dividing the travel path into at least one guiding segment based on preset key nodes includes: Based on the preset key nodes, multiple guide segment breakpoints are set on the travel path. Multiple consecutive guide segments are formed, with the path between two adjacent guide segment breakpoints as the unit.

4. The parking lot guidance method according to claim 1, characterized in that, For each of the guiding segments, determining the corresponding travel guidance information includes: For each of the aforementioned guide segments, the predetermined direction of travel and path length from the starting point to the end point are determined, and the estimated travel time of the current guide segment is generated according to the travel speed mode set by the user. Based on the direction of travel, the path length, and the estimated travel time, the travel guidance information is generated and output on the electronic terminal to guide the user to complete the current guided segment. When the user starts the current guided segment, the orientation of the electronic terminal monitored by the guidance module built into the electronic terminal is obtained and displayed so that the user can check whether their walking direction is consistent with the predetermined direction of travel.

5. The parking lot guidance method according to claim 4, characterized in that, At least one of the key nodes is pre-associated with real-world information; The real-scene information is displayed through real-scene images or AR illustrations; the method further includes: In response to the user's real-view operation for the key nodes, the corresponding real-view information is displayed so that the user can compare the actual environment and determine whether the current walking path is correct.

6. The parking lot guidance method according to claim 4 or 5, characterized in that, Also includes: The estimated travel time is converted into countdown information and output on the display interface of the electronic terminal in at least one of the following forms: countdown progress bar, digital timer, or voice periodic broadcast. If the estimated travel time is exceeded and no continue navigation instruction is received within a preset time period after the navigation progress prompt is generated, a path deviation warning is generated, and the user is guided to perform a relocation operation.

7. The parking lot guidance method according to claim 1, characterized in that, The static map includes a parking lot topology structure composed of topological nodes and connecting edges, as well as a hierarchical map display graphic from a zoning overview map to a detailed parking space map; wherein, the topological nodes are characteristic location points that provide directional guidance; and the connecting edges represent feasible paths between adjacent topological nodes.

8. A parking lot guidance device, characterized in that, Applied to electronic devices, including: The planning module is used to respond to the user's route planning request and generate a travel route on the static map of the parking lot based on the user's current location and target parking space; The segmentation module is used to divide the travel path into at least one guide segment based on preset key nodes; The output module is used to determine the corresponding travel guidance information for each of the guide segments; The confirmation module is used to pause navigation and generate a navigation progress prompt when the user receives an instruction to reach the end of the current guidance segment or exceeds the expected travel time during the user's journey based on the travel guidance information. After receiving a instruction to continue navigation, navigation will resume.

9. A terminal device, characterized in that, The terminal device includes a processor and a memory, the memory storing a computer program, and the processor executing the computer program to implement the method of any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed on a processor, implements the method according to any one of claims 1-7.

Images