Fault diagnosis file acquisition method and device
A fault diagnosis and file acquisition technology, applied in the direction of non-redundancy-based fault handling, response error generation, instruments, etc., can solve problems such as loss of fault diagnosis files and difficulty in obtaining fault diagnosis files
Active Publication Date: 2021-10-15
HONOR DEVICE CO LTD
8 Cites 1 Cited by
AI-Extracted Technical Summary
Problems solved by technology
 The embodiment of the present application provides a method and device for obtaining a fault diagnosis file, which can be used to solve the problem that the faul...
By the above method, after compressing the fault diagnosis file whose size is greater than the preset threshold in the first storage area, then transfer to the log partition in the non-volatile memory, which can greatly save memory and improve the transmission efficiency of data .
Through above-mentioned method, the fault diagnosis file in the data subregion is compressed and then uploaded, memory can be greatly saved, it is beneficial to the fault diagnosis file to be transmitted back to the network, the uploading efficiency of the fault diagnosis file is improved, and the daily fault diagnosis file is effectively satisfied. upload requirements.
 Through the method provided by the embodiment of the present application, since the terminal device transfers the fault diagnosis file from the storage area on the volatile memory to the log partition in the non-volatile memory after restarting without powering off, After the terminal device is powered off and restarted, the fault diagnosis files in the log partition will not be lost. In addition, after the fault diagnosis files in the log partition are transferred to the data partition in the non-volatile memory, the fault diagnosis files can be directly accessed and obtained. Diagnosis files, which makes it easier to obtain fault diagnosis files.
 Through the above method, the fault diagnosis file is uploaded to the preset shared area, so that various fault diagnosis files generated in different terminal devices can be shared, which is conducive to more comprehensive fault analysis on the operating system of the term...
The invention discloses a fault diagnosis file acquisition method and device, and the method comprises the steps: generating a fault diagnosis file and storing the fault diagnosis file in a storage region of a volatile memory after an operation system of terminal equipment is abnormal, and after the terminal equipment is not powered off and restarted, the fault diagnosis file in the storage area of the volatile memory is transferred to a log partition in the nonvolatile memory, and after the terminal equipment is powered off and restarted, the fault diagnosis file in the log partition is transferred to a data partition in the nonvolatile memory. After the terminal equipment is powered off and restarted, the fault diagnosis file in the log partition cannot be lost, further, after the fault diagnosis file in the log partition is transferred to the data partition in the nonvolatile memory, the fault diagnosis file can be directly accessed and acquired, and then the acquisition of the fault diagnosis file is relatively simple.
Non-redundant fault processing
Data partitioningOperating system +5
- Experimental program(1)
 Below in conjunction with the accompanying drawings of the present application example embodiments, the technical solutions in the embodiments of the present application will be described.
 The terms used in the following examples are embodiments only for the purpose of describing particular embodiments, and is not intended as a limitation on the present disclosure. As claimed in the specification and the appended claims of the present application is used as a book, the singular forms expression, "a", "an", "the", "above", "an" and "the" are intended to including, for example, "one or more" this form of expression, unless the context clearly indicated to the contrary. It should also be understood that the embodiments described in this application the following, "at least one", "one or more" means one, two or more. The term "and / or" used to describe the relationship of associated objects representing three relationships may exist; for example, A and / or B, may be expressed: A exists alone, A and B are present at the same time, the case of B alone, wherein A, B may be singular or plural. Character "/" generally indicates associated objects before and after an "or" relationship.
 Reference described in this specification to "one embodiment" or "some embodiments," etc., means that a particular feature embodiments including the embodiments described embodiment, structure, or characteristic in one or more embodiments of the present disclosure. Thus, in the present specification is different from the statement appears "in one embodiment", "in some embodiments", "in other embodiments," "in some further embodiments," and the like are not necessarily both refer to the same embodiment, but rather "one or more, but not all embodiments" unless otherwise is additionally emphasized. The term "comprising", "including", "having" and variations thereof mean "including but not limited to", unless otherwise is further emphasized.
 The following drawings fault diagnosis native file acquisition process will be described in conjunction.
 figure 1 Shows an exemplary schematic flow chart of the native file acquired fault diagnosis, such as figure 1 Shown, in normal use the user terminal device, the terminal device occurs crash dump (blue screen failure), troubleshooting file generated automatically and stored in the DDR, then there will be two results, the results of the first, if the user does not have offline grab logging facility conditions, will be forced to restart the terminal device or a terminal device automatic restart after power-on reset at this time when the terminal device, troubleshooting files stored in the DDR will be lost. Another result, if you have the conditions to use offline arrested logging facilities, use the grab tool log off manually crawl and eventually get to the troubleshooting document. Wherein, troubleshooting log file is a record operating system abnormality information terminal device, the operating system for the fault diagnosis, fault log may include logging and fault diagnosis.
 In the above process, the user generally does not have the condition grasping offline logging tool, the further terminal device is restarted, the file stored in the fault diagnosis in the volatile memory will be lost, resulting in obtaining more difficult fault diagnosis file.
 In order to solve the fault diagnosis file is lost, it is difficult to obtain further problem troubleshooting documents embodiment of the present application provides a fault diagnosis method and device for obtaining files.
 Wherein the method is applied to a terminal device, the terminal device may be a mobile phone, a tablet computer, laptop, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), handheld computers, netbooks, personal digital assistants (personal digital assistant, PDA), smart wearable devices and virtual reality equipment, terminal equipment, the embodiment of this application without any restrictions.
 In mobile phones, for example, in conjunction with the accompanying drawings, the present application provides the program will be introduced by the various embodiments described.
 The present embodiment provides an application file acquisition method of fault diagnosis, the failure diagnosis method is applied to a terminal device file acquisition. Wherein, troubleshooting log file is a record operating system abnormality information terminal device, the operating system for the fault diagnosis, fault log may include logging and fault diagnosis. See figure 2 Workflow illustrated schematic embodiment of the disclosed fault diagnosis document acquisition method comprising the steps of embodiment of the present application:
 201: After the terminal device running an operating system abnormality occurs, generates a fault diagnosis file and stored in the first storage area.
 Wherein the first storage area in the terminal device is easy to storage area on the nonvolatile memory, such as DDR.
 Fault diagnosis and fault log files include log fault diagnosis, fault logging for exception information reflecting the operating system, fault diagnosis log is used to reflect the operating system for abnormal positioning information.
 202: After the terminal device less than power-on reset, read the file from the first storage fault diagnosis region.
 Specifically, the terminal apparatus is less than one form of power-on reset system reset, less than the terminal device after power-on reset, it enters log crawl mode, in this log crawl mode, the terminal device may utilize preset abnormality detection failure module reads fault diagnosis and fault log log in the first storage area.
 203: The terminal device a first fault diagnosis file storage area in the dump terminal device in the nonvolatile memory in the log partition.
 Illustratively, the terminal device in the nonvolatile memory may be flash memory.
 Log data stored in the partition Specifically, the nonvolatile memory, when the terminal device after the power-on reset and are not lost, but can not access the log data stored in the partition directly.
 Optionally, before performing step 203, the failure diagnosis can first file of the first storage area is compressed by:
 First, the file size fault diagnosis terminal device determines whether the first storage area is greater than a predetermined threshold value.
 Alternatively, the preset threshold may be set to 512KB (Kilobyte, kilobytes), the present application is not limited to this embodiment.
 Then, if the file size of the fault diagnosis in the first storage area is greater than a preset threshold, the terminal device troubleshooting compressed file of the first memory area, otherwise, the terminal device does not compress the first failure diagnosis file storage area.
 Further, there are many ways the terminal device compresses the first failure diagnosis file storage area, a possible implementation:
 First, the terminal device to judge the size of the fault diagnosis is smaller than the size of the compressed file before compression.
 Further, it can be used to predict the size of the default open-source programs to predict troubleshooting compressed file size is less than before compression.
 Second, if the size of the compressed file to predict the failure diagnosis smaller than the size before compression, the terminal equipment troubleshooting compressed file of the first memory area, otherwise, the terminal device does not compress the first failure diagnosis file storage area.
 Alternatively, in another possible implementation, the compression may be performed directly on the fault diagnosis of the first file in the storage area, is not limited particularly.
 Incidentally, since the failure diagnosis file in the first storage area, share fault log memory is much greater than the fault log memory associated with the diagnosis, and therefore before performing step 203, only the first storage area may each the fault log is compressed in the above manner, respectively, each of the fault diagnosis and the first storage area log dump terminal device directly in the nonvolatile memory in the log partition. It may be performed for all the fault log region in a first storing compressed together as described above, can also be compressed and then all the partition dump troubleshooting log file of the first storage area in the manner described above, is not limited particularly.
 After the failure diagnosis first file of the first storage area compressed by the above-described embodiment, step 203 should be split into the following steps:
 First, fault diagnosis file to determine whether the first storage area compressed success.
 Secondly, if the first failure diagnosis file storage area is successful, the success of the terminal device troubleshooting compressed file into the terminal device in the nonvolatile memory in the log partition, if a first fault diagnosis storage area file compression fails, the terminal discards the fault diagnosis of the compressed file failure.
 After the above-described embodiment, the first storage area size is larger than a predetermined threshold fault diagnosis file is compressed again in the nonvolatile memory dump log partition can significantly save memory, improve data transmission efficiency.
 Incidentally, before performing step 203, the failure diagnosis can be compressed file of the first storage area, may not be compressed, it is not limited particularly.
 204: After the terminal device in the next power-on reset, failure diagnosis in the nonvolatile memory log file partition dump data to partition the non-volatile memory.
 Wherein the data partitioning of the nonvolatile memory device will be mounted at the terminal after power-on reset, so that less than the terminal device after power-on reset, fault diagnosis requires first file in a first storage area of the nonvolatile dump log partition memory as a transition in the power-on reset terminal device, the data of the nonvolatile memory partition mounted to the troubleshooting log file partition dump data to the partition, for subsequent operations.
 Specifically, by using the terminal apparatus preset log file monitoring module failure diagnosis in the nonvolatile memory dump log partition to partition the data in the nonvolatile memory.
 Illustratively, use log monitoring module detects whether a timing fault diagnosis flash memory file (log partition), the fault is detected if the diagnostic file, then move it to flash memory (data partitioning) of.
 Step 201 to step S204 to provide a fault diagnosis file acquisition method, the abnormal operation occurs after the operating system and trigger a system reset, the terminal equipment failure diagnosis file from the storage area in the volatile memory to the non-rollover log partition in the volatile memory, after the power-on reset terminal device, the fault diagnosis log file partition dump data partition to the non-volatile memory.
 The method provided by the embodiment of the present application, since the terminal device after the power-on reset less than the fault diagnosis from a file storage area of the volatile memory, non-volatile memory dump to the log partition, so the terminal device after the power-on reset, troubleshooting log file partition is not lost, moreover, the troubleshooting log file partition dump data to the nonvolatile memory partition, and can directly access the file acquired fault diagnosis, thus making the documents for fault diagnosis is relatively simple.
 Also, see image 3 Workflow diagram shown, another method of the present application to obtain troubleshooting documents embodiments disclosed embodiment, after performing steps 201 to 204, further comprising the steps of:
 301: The terminal device troubleshooting file data partition uploaded to the pre-shared area.
 Specifically, the area can be set to share large data cloud website.
 By the above manner, the default troubleshooting file uploaded to the shared area, making all kinds of fault diagnosis of terminal devices in different file generated can be shared, it is beneficial for the operating system of the terminal device more comprehensive failure analysis, thereby further improving fault diagnostic accuracy.
 Further, log upload module may be utilized provided in the terminal device of the failure diagnosis uploaded file data in the partition to a predetermined shared area, optionally, one implementation, log upload module may be by way of the data in the partition troubleshooting file uploads to a pre-shared area:
 First, fault diagnosis compressed file data partition to obtain a compressed file.
 Alternatively, compression may be encrypted and compressed or non-compressed encrypted, is not limited particularly.
 Secondly, the pre-compressed file uploaded to the shared area.
 By the above manner, the failure diagnosis data partition file compression and then upload, can significantly save memory, useful for troubleshooting network file return, improve the efficiency of fault diagnosis upload files, effectively meet the troubleshooting file upload daily needs .
 Alternatively, in other possible implementations, the original may be directly troubleshooting file upload data in the partition, which is not limited particularly.
 302: terminal device to obtain the diagnostic file, the operating system of the terminal apparatus for fault diagnosis, and generates instructions to repair the system.
 Specifically, the terminal apparatus acquires all the troubleshooting from the shared area file, all files shared fault diagnosis fault diagnosis region includes file upload different terminal devices. In addition, research testers fault diagnostic module may be provided on the terminal to use of various types of operating system file troubleshooting fault diagnosis, and generates instructions to repair the system.
 After the R & D testing can not only be on troubleshooting file this terminal device uploads analysis can also be analyzed troubleshooting file other terminal devices to upload, so you can more fully to the operating system of the terminal device troubleshooting, determine the cause of the malfunction, the operating system generates a repair system to repair instructions and repair the system sends an instruction to the corresponding terminal device.
 303: terminal equipment repair instruction response system, and the operating system to perform system repair.
 , On the operating system of the terminal device fault diagnosis fault diagnosis by analyzing individual file shared region in the above manner, the operating system repair system can be greatly reduced according to the results of operating system failure diagnosis occurs during subsequent normal operation of the terminal device the probability of abnormal, effectively improve the user experience of the terminal device.
 To further clarify the application of the present method of obtaining the advantages of another embodiment of the disclosed document troubleshooting embodiment, exemplarily, see Figure 4 Specific examples of a schematic flow chart of another embodiment of the disclosed fault diagnosis method for obtaining the file of the embodiment of the present application.
 exist Figure 4 In normal use when the user if the terminal device, the terminal device occurs crash dump (blue screen failure), troubleshooting file generated automatically and stored in the DDR, the present application fault diagnosis method for obtaining another embodiment of the present disclosure documents, after reading the DDR fault log logging and fault diagnosis, fault log compression, dumped into the log in non-volatile memory partition, the fault diagnosis log directly dumped into the log in non-volatile memory partition after the forcible restart the terminal device or automatic restart the terminal device, the fault abnormality detection module fault exception anomaly detection, detecting post-log partition fault diagnosis file to the fault diagnosis file (fault log and fault diagnosis logs) dump to partition data in non-volatile memory, the log file upload module compression failure diagnosis data partition, and uploads the data to large site troubleshooting compressed files, eventually get to the troubleshooting document.
 By using the acquisition method of the present application further troubleshooting documents embodiment disclosed embodiment, the terminal device failure diagnosis file from a volatile memory storage area, a nonvolatile memory dump to the log partition, this time, in after the power-on reset terminal device, troubleshooting log file partition is not lost, and further, the troubleshooting log file partition dump data to the nonvolatile memory partition, the direct access and can be obtained fault diagnosis file, thus making documents for fault diagnosis is relatively simple, in addition, and to repair the system by analyzing the respective terminal device file sharing fault diagnosis region based on the results, not only to further improve the accuracy of fault diagnosis, but also greatly reduce the probability of occurrence of an abnormal operation of the system during subsequent normal operation of the terminal equipment, improve the experience of the terminal device.
 Further, the present application in order to achieve a further embodiment of the disclosed fault diagnosis method for obtaining files embodiment, Figure 5 The present example shows an application layer software architecture schematic flowchart of a method corresponding to the acquired file to another embodiment of the disclosed fault diagnosis embodiment, such as Figure 5 Shown, implemented in the software architecture layer further embodiment the present application discloses a further embodiment of the fault diagnosis file acquisition method used in normal operation in the mobile phase (Kernel phase), error reset trigger system generates a file in the DDR troubleshooting (including fault diagnosis and fault log logs), no less than the system power-on reset, enter the mobile phone start-up phase, the fault detection module fault abnormality anomaly detection, that is, read the fault log and fault diagnosis log DDR, and then, troubleshooting aid diagnostic logging, logging the fault diagnosis directly stored in the flash memory (log partition); and for the fault log (minidump), first through all the fault log, a log for each fault, the fault log is determined whether the size is larger than 512KB, if more than 512KB, the failure to predict the size is smaller than the size of the log compression before compression, is less than or equal to 512KB, then the fault log is stored directly in the flash memory (log partition) in.
 After size before whether the size of the anticipation fault log compression smaller than the compression, the size of the post if the fault log compression smaller than the size before compression, the compression fault log and determine whether the fault log is successful, the size of the post if the fault log compression greater than or equal to the size before compression, then the fault log stored directly in the flash memory (log partition) in.
 Determining whether the fault log is successful, the fault if the fault log after the log is successful, the flash memory will be stored in the compressed (log partition), if the fault log compression is unsuccessful, the fault log is discarded.
 After the power-on reset in the phone, the phone into the normal operation of the stage, this time log monitoring module startup, fault diagnosis and fault log log, then the fault log log monitoring and fault diagnosis module if it detects the presence of (log partition) is stored in flash memory log rotation to flash memory (data partitioning) of. Finally, log upload module fault logs and fault diagnosis log flash storage (data partition) in uploading data to large sites.
 Here embodiment apparatus of the present embodiment corresponding to the above-described application Example.
 Image 6 The present application is a configuration diagram of a fault diagnosis apparatus obtaining files provided in the embodiment. In one embodiment, the apparatus is applied to a terminal apparatus, may include: a failure diagnosis file generating module 601, the abnormality detection module 602 and a fault log monitoring module 603, the apparatus furthermore may further comprise uploading a log module 604 and system repair module 605 and more or fewer units and modules is not limited in the present embodiment, the structure of the apparatus.
 Wherein the fault diagnosis file generating module 601, configured to run an operating system abnormality occurs, generates a fault diagnosis file and stored in the first storage area, wherein the first storage area is a storage area on the terminal device in the volatile memory fault diagnosis file to record the operating system running log exception information for the operating system troubleshooting.
 Fault anomaly detection module 602, a power less than the terminal device after restarting, the file is read from the first memory fault diagnosis region. And a first failure diagnosis file storage area in the dump terminal device logs in the nonvolatile memory partitions.
 Log monitoring module 603, configured to, after the power-on reset terminal device, the fault diagnosis in the nonvolatile memory log file partition dump data to partition the non-volatile memory.
 Alternatively, in some embodiments, the apparatus further comprising:
 Log upload module 604 for uploading troubleshooting file data partition to a pre-shared area.
 Alternatively, in other embodiments, the apparatus further comprising:
The system repair module 605 is configured to respond to the system repair instruction, and perform system repair on the operating system, where the system repair instruction is a fault diagnosis file in the terminal device, and the operating system of the terminal device is generated after troubleshooting. .
 Optionally, in other embodiments, log upload module 604 includes:
 The first compression architecture is used to compress the fault diagnosis file in the data partition to obtain a compressed file.
 Upload monomorphism is used to upload compressed files to the preset shared area.
 Optionally, in other embodiments, the fault abnormality detection module 602 includes:
 Read the child module for reading a fault diagnostic file from the first storage area after the terminal device is not overwhelmed.
 The second compression laser module determines whether the size of the fault diagnosis file in the first storage area is greater than if the fault diagnosis file in the first storage area is transmitted to the log partition in the non-volatile memory in the terminal device. Preset threshold.
 The second compression laser module is also used to compress the fault diagnosis file in the first storage area if the size of the fault diagnostics file in the first storage area is greater than the preset threshold.
 Optionally, in still other embodiments, fault abnormal detection module 602 also includes:
 The determination sub-module is used to determine if the fault diagnosis file in the first storage area is compressed.
 Transfer submodule, used to transfill the fault diagnostic file compressed in the first storage area to the log partition in the non-volatile memory in the terminal device.
 Discard Submodule, used to discard the fault diagnosis file of compression failure if the fault diagnosis file compression is compressed.
 Further, in a hardware implementation, the present application embodiment provides a communication device for implementing the method in the foregoing embodiment.
 The structure of the communication device can be the same as the structure of the aforementioned fault diagnostic file acquisition device, or may not be the same. In some embodiments, see Figure 7 A structural schematic diagram of a communication device is shown, the communication device comprising:
 At least one processor 701 and a memory;
 The memory is used to store program instructions;
 The processor 701 is configured to invoke and execute program instructions stored in the memory to achieve the aforementioned Figures 2 to 5 All or some of the steps in the corresponding embodiments.
 Further, the communication device can also include: transceiver 702 and bus 703, the memory comprising a random access memory 704 and a read only memory 705.
 The processor 701 is coupled to the receiver 702, the random access memory 704, and the read only memory 705 by the bus, respectively. Here, when it is necessary to run the communication device, boot the device to enter the normal operating state by curing by curing by curing the basic input / output system in the read only memory 705 or the BootLoader boot system in the embedded system. After the device enters the normal operating state, the application and operating system are run in the random access memory 704, so that the communication device is executed. Figures 2 to 5 All or some of the steps in the corresponding embodiments.
 The apparatus of the embodiment of the present invention may correspond to the above Figures 2 to 5 The fault diagnosis file acquisition device in the corresponding embodiment, and the processor in the apparatus can achieve 2 to Figure 5 The functions of the fault diagnosis file acquisition device in the corresponding embodiment and / or the various steps and methods implemented, and will not be described herein.
 It should be noted that the present embodiment may also be based on a network device implemented by a network functional virtualization (English: Network Function Virtualization, NFV) technology, the network device to virtual network devices (eg, virtual hosts, virtual Router or virtual switch). The virtual network device can be a virtual machine that runs a program for transmitting a communication message (English: Virtual Machine, VM), which is deployed on a hardware device (eg, physical server). The virtual machine is a complete computer system that runs in a complete isolation environment through the software simulation. Those skilled in the art can virtually multiple network devices having the above functions on a universal physical server by reading this application. Not will be described here.
 When implementing the software implementation, you can fully or partially in the form of a computer program product. For example, in the aforementioned Image 6 The fault diagnosis file generating module 601 and the faulty abnormality detection module 602 can be implemented between the fault diagnostic file generation module 601 and the faulty abnormality detecting module 602, the function of the fault abnormality detection module 602 and the log monitoring module 603 can be by the processor. 10 Implementation, the partial function of the fault diagnostic file generation module 601 can be implemented by the memory 20.
 Further, in the specific implementation, the present application embodiment provides a computer readable storage medium including instructions. Among them, it is possible to implement when the computer readable medium is running on the computer in any device. Figures 2 to 5 All or some of the steps in the corresponding embodiments. The storage medium of the computer readable medium can be a disk, an optical disk, read-only storage memory (English: Read-Only Memory, referred to as ROM) or random storage memory (English: Random Access Memory, Abb: RAM), etc. .
 The various illustrative logic units and circuits described in the present application embodiments may be through a general processor, a digital information processor, a dedicated integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device. Different gates or transistors logic, discrete hardware components, or any of the above-mentioned designs to implement or operate. A general purpose processor can be a microprocessor, optionally, which can also be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented by a combination of computing devices, such as digital information processors, microprocessors, plurality of microprocessors, one or more microprocessors combined with a digital information processor core, or any other similar configuration. accomplish.
 The steps of the methods or algorithms described in the present application embodiments can be directly embedded in hardware, processor software units, or binding of both. Software units can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, register, hard disk, removable disk, CD-ROM, or other inventive storage medium in the art. Illustratively, the storage medium can be connected to the processor so that the processor can read information from the storage medium and can store information to the storage medium. Alternatively, the storage medium can also be integrated into the processor. The processor and storage medium can be set in the ASIC, and the ASIC can be set in the UE. Alternatively, the processor and the storage medium can also be disposed in different components in the UE.
 It should be understood that in various embodiments of the present application, the size of the sequence numbers of each process does not mean that the order of execution sequence, the execution order of each process should be determined in its function and inherent logic, and should not be the embodiment of the present application The implementation process constitutes any defined.
 In the above embodiment, it can be achieved through software, hardware, firmware, or any combination thereof in whole or in part. When implementing the software implementation, you can fully or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When loading and executing the computer program instruction on a computer, all or partially generated the flow or function as described in the present application embodiment. The computer can be a general purpose computer, a dedicated computer, a computer network, or another programmable device. The computer instruction can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center. Transfer by wired (e.g., same shaft cable, fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.), is transmitted to another website site, computer, server, or data center. The computer readable storage medium may be any available medium that the computer can access or a data storage device such as a server, data center, such as one or more available media. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape, a photologies (eg, a DVD), or a semiconductor medium (e.g., a solid-state hard disk SOLID State Disk (SSD)).
 The same similar part of the various embodiments of the present specification see each other, each of which is focused on other embodiments. In particular, for devices and system embodiments, since it is substantially similar to method embodiments, the description of the relatively simple, relevant, referring to the description of the method embodiment portion.
 Those skilled in the art will clearly understand that the techniques of the embodiments of the present invention can be implemented by means of software plus necessary. Based on this, the technical solution in the embodiment of the present invention essentially or contributes to the prior art in the form of a software product, which can be stored in a storage medium, such as ROM / RAM. , Disk, optical disc, etc., including several instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to perform certain portions of the various embodiments or embodiments of the present invention.
 The same similar part of the various embodiments in this specification can be seen each other. In particular, for the embodiment of the road constraint determination apparatus disclosed herein, since it is substantially similar to the method embodiment, the described relatable is simple, and the description of the method embodiment will be described.
 The present application embodiment described above is not constituting the limitation of the scope of the present application.
Description & Claims & Application Information
We can also present the details of the Description, Claims and Application information to help users get a comprehensive understanding of the technical details of the patent, such as background art, summary of invention, brief description of drawings, description of embodiments, and other original content. On the other hand, users can also determine the specific scope of protection of the technology through the list of claims; as well as understand the changes in the life cycle of the technology with the presentation of the patent timeline. Login to view more.