CN110569046B - Data processing method, device, equipment and storage medium - Google Patents

Data processing method, device, equipment and storage medium Download PDF

Info

Publication number
CN110569046B
CN110569046B CN201810574783.2A CN201810574783A CN110569046B CN 110569046 B CN110569046 B CN 110569046B CN 201810574783 A CN201810574783 A CN 201810574783A CN 110569046 B CN110569046 B CN 110569046B
Authority
CN
China
Prior art keywords
diagnosis
version
request
software
user equipment
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810574783.2A
Other languages
Chinese (zh)
Other versions
CN110569046A (en
Inventor
刘长通
汤雪华
杨青
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Banma Zhixing Network Hongkong Co Ltd
Original Assignee
Banma Zhixing Network Hongkong Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Banma Zhixing Network Hongkong Co Ltd filed Critical Banma Zhixing Network Hongkong Co Ltd
Priority to CN201810574783.2A priority Critical patent/CN110569046B/en
Publication of CN110569046A publication Critical patent/CN110569046A/en
Application granted granted Critical
Publication of CN110569046B publication Critical patent/CN110569046B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/362Software debugging
    • G06F11/366Software debugging using diagnostics
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3688Test management for test execution, e.g. scheduling of test suites
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

The embodiment of the application provides a data processing method, a data processing device, data processing equipment and a storage medium, so that the diagnosis efficiency of the reason of version query failure is improved. The method comprises the following steps: after user equipment fails to inquire a target version of a software program, acquiring corresponding software installation parameters from the user equipment; querying a server by using the software installation parameters so as to diagnose corresponding failure reasons through the server; and receiving the diagnosis result returned by the server. The server can automatically diagnose the corresponding failure reason based on the software installation parameters, then the console obtains the corresponding diagnosis result, and the processing efficiency can be effectively improved through automatic diagnosis of the failure reason.

Description

Data processing method, device, equipment and storage medium
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a data processing method, a data processing apparatus, an electronic device, and a storage medium.
Background
Over-the-Air Technology (OTA) may be applied in an upgrade scenario for a software program, in which a hardware device sends a request to a server Over the internet to query for an updated version of a system or application program, and then may download an upgrade package for the updated version and perform an upgrade.
However, when the OTA is used for upgrading, a problem that various software programs cannot be upgraded sometimes occurs, for example, the user equipment prompts the upgrade but cannot query an updated version, and for example, the test equipment cannot download the tested updated version when testing the updated version.
When the reasons that the updated version cannot be obtained and downloaded are checked, the reasons that the updating fails are usually manually checked, and the parameter items are required to be checked one by one in the manual checking process, so that the manual checking efficiency is low.
Disclosure of Invention
The embodiment of the application provides a data processing method, so that the diagnosis efficiency of the reason of version query failure is improved.
Correspondingly, the embodiment of the application also provides a data processing device, an electronic device and a storage medium, which are used for ensuring the realization and the application of the system.
In order to solve the above problem, an embodiment of the present application discloses a data processing method, where the method includes: after user equipment fails to inquire a target version of a software program, acquiring corresponding software installation parameters from the user equipment; querying a server by using the software installation parameters so as to diagnose corresponding failure reasons through the server; and receiving the diagnosis result returned by the server.
Optionally, the target version of the software includes: the version to be upgraded of the software and/or the version to be installed of the software; the user equipment comprises test equipment.
Optionally, the obtaining of the corresponding software installation parameter from the user equipment includes: generating a parameter request and sending the parameter request to the user equipment; and receiving a parameter response fed back by the user equipment according to the parameter request, and acquiring software installation parameters from the parameter response.
Optionally, the generating a parameter request and sending the parameter request to the user equipment includes: determining a diagnosis identifier, and generating a parameter request according to the diagnosis identifier; and sending the parameter request to the user equipment through a first message channel.
Optionally, the querying the server by using the software installation parameter includes: and generating diagnosis information according to the diagnosis identifier and the software installation parameters, and sending the diagnosis information to a server.
Optionally, the sending the diagnostic information to the server includes: and accessing the diagnosis interface through a second message channel, and sending the diagnosis message to the server.
Optionally, the method further includes: and displaying the diagnosis result.
Optionally, the method further includes: and adjusting the software installation condition of the target version according to the diagnosis result.
Optionally, the software installation condition includes at least one of: version state conditions, device model conditions, version number conditions, incremental upgrade package conditions, black and white list conditions, and custom filter conditions.
The embodiment of the application also discloses a data processing device, which comprises: the software installation management system comprises a parameter acquisition module, a software installation management module and a software installation management module, wherein the parameter acquisition module is used for acquiring corresponding software installation parameters from user equipment after the user equipment fails to inquire a target version of a software program; the diagnosis module is used for inquiring a server by adopting the software installation parameters so as to diagnose the corresponding failure reason through the server; and the result receiving module is used for receiving the diagnosis result returned by the server.
Optionally, the target version of the software includes: a version of the software to be upgraded and/or a version of the software to be installed; the user equipment comprises test equipment.
Optionally, the parameter obtaining module includes: the request generation submodule is used for generating a parameter request; the request sending submodule is used for sending a parameter request to the user equipment; and the request receiving submodule is used for receiving the parameter response fed back by the user equipment according to the parameter request and acquiring the software installation parameters from the parameter response.
Optionally, the request generating sub-module is configured to determine a diagnostic identifier, and generate a parameter request according to the diagnostic identifier; and the request sending submodule is used for sending the parameter request to the user equipment through a first message channel.
Optionally, the diagnostic module includes: the diagnostic information generation submodule is used for generating diagnostic information according to the diagnostic identifier and the software installation parameters; and the diagnostic information sending submodule is used for sending the diagnostic information to the server.
Optionally, the diagnostic information sending sub-module is configured to access the diagnostic interface through a second message channel, and send the diagnostic message to the server.
Optionally, the method further includes: and the display module is used for displaying the diagnosis result.
Optionally, the method further includes: and the adjusting module is used for adjusting the software installation condition of the target version according to the diagnosis result.
Optionally, the software installation condition includes at least one of: version state conditions, equipment model conditions, version number conditions, increment upgrade package conditions, black and white list conditions and custom filtering conditions.
The embodiment of the application also discloses an electronic device, which comprises: a processor; and a memory having executable code stored thereon, which when executed, causes the processor to perform a data processing method as described in one or more of the embodiments of the application.
One or more machine-readable media having stored thereon executable code that, when executed, causes a processor to perform a data processing method as described in one or more of the embodiments of the present application are also disclosed.
Compared with the prior art, the embodiment of the application has the following advantages:
in the embodiment of the application, after the user equipment fails to inquire the target version of the software program, the console can acquire the corresponding software installation parameters from the user equipment, and then adopts the software installation parameters to inquire the server, so that the server can automatically diagnose the corresponding failure reasons based on the software installation parameters, and then the console acquires the corresponding diagnosis result, and the processing efficiency can be effectively improved through the automatic diagnosis of the failure reasons.
Drawings
FIG. 1 is a schematic diagram of a management system according to an embodiment of the present application;
FIG. 2 is a flow chart of steps of an embodiment of a data processing method of the present application;
FIG. 3 is a flow chart of steps in another data processing method embodiment of the present application;
FIG. 4 is a schematic interface diagram of a console according to an embodiment of the present application;
FIG. 5 is a schematic illustration of a diagnostic query interface according to an embodiment of the present application;
FIG. 6 is a block diagram of an embodiment of a data processing apparatus according to the present application;
FIG. 7 is a block diagram of another data processing apparatus embodiment of the present application;
fig. 8 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, the present application is described in further detail with reference to the accompanying drawings and the detailed description.
When the OTA is used for operations such as installation and upgrade of software programs, problems that various software programs cannot be installed and upgraded sometimes occur, for example, the user equipment prompts upgrade but cannot query an updated version, and for example, the test equipment cannot download a test version when testing the updated version. If the mode of manually checking the failure reasons is adopted, the parameter items need to be checked one by one, so that the manual checking efficiency is low. The embodiment of the application can adopt an automatic troubleshooting mode, and after the corresponding software installation parameters are obtained from the user equipment, the server can be inquired by adopting the software installation parameters, so that the diagnosis result of the server is obtained, and the troubleshooting efficiency of failure reasons in the software program installation and upgrading processes can be effectively improved.
As shown in fig. 1, the management system comprises: the system comprises a console, user equipment and a server, wherein the console is used for providing control service for a software developer and can be applied to electronic equipment such as the server and terminal equipment; the server is positioned at a server side of the management system and refers to electronic equipment for providing program management service of the software program; the user equipment is located at the equipment end of the management system, and refers to electronic equipment used by a user, such as a personal computer, a tablet computer, a smart phone, a wearable device, and an Internet of Things (IoT) device. Wherein the console, the user device and the server may interact with each other in order to provide the services required by the software program.
After the program developer develops the software program, the software program can be uploaded to a server of the management system through the console, so that management services such as downloading and upgrading of the software program can be provided through the server. The program developer can also perform management operations such as testing, upgrading, maintaining and the like on the software program through the console. A client of the software program may run in the user device so that the user may use the software program. The software program refers to a program written by software, and includes an operating system and an application program running on the operating system.
And step 102, after the user equipment fails to inquire the target version of the software, the console acquires corresponding software installation parameters from the user equipment.
Wherein the target version of the software comprises: a version of the software to be upgraded and/or a version of the software to be installed. When the user equipment does not install the software program and requests to install the software program, an installation request can be sent out, so that a required version to be installed can be inquired according to the installation request, the version to be installed is usually the latest version of the software program, and if the inquiry of the version to be installed fails, such as the version number of the version is not inquired or an installation package corresponding to the version number is not inquired, the version to be installed can be used as a target version. The user equipment can also perform upgrading operation of the installed software program, determine that the version to be upgraded exists based on prompt, query and the like, send an upgrading request to the server, and determine that the version to be upgraded is the target version if the query of the version to be upgraded fails. The failure of the version query of the software program may refer to that the version number of the version is not queried, or that the software installation package corresponding to the version number is not queried.
The console may determine, actively or based on the report of the user equipment, and the like, an event that the user equipment fails to query the target version of the software program, and may then obtain the software installation parameters of the software program from the user equipment. The software installation parameters refer to parameters required in the software program installation process, such as the device model, the operating system version, the operating system type, and the like of the user equipment. The user equipment may report an event of query failure in the process of installing and upgrading the software program, for example, the user equipment fails to query the online upgrade version, and for example, the test equipment can report the query failure in the test process of the upgrade test version.
In an application scenario of the embodiment of the application, the user equipment includes test equipment, where the test equipment refers to user equipment for testing a software program, and the test equipment may test an issued or unpublished application program in software development and maintenance processes, so that processes of installation, upgrade, and the like of a software program of a target version on the test equipment may be monitored, and thus, the test equipment with a failed query of the target version is determined.
Wherein the obtaining of the corresponding software installation parameters from the user equipment includes: generating a parameter request and sending the parameter request to the user equipment; and receiving a parameter response fed back by the user equipment according to the parameter request, and acquiring software installation parameters from the parameter response.
The console may generate a parameter request for requesting acquisition of software installation parameters of the software program by the user equipment based on the target version, the device identifier, and the like, and may then send the software installation parameters to the terminal device. The console and the user equipment can interact through a message channel, and the message channel of the console and the user equipment is called a first message channel. In an optional embodiment, the generating and sending a parameter request to the ue includes: determining a diagnosis identifier, and generating a parameter request according to the diagnosis identifier; and sending the parameter request to the user equipment through a first message channel. In the embodiment of the present application, a process of detecting a reason for a failure query of a target version by a console may be referred to as a diagnostic process, and a diagnostic identifier is used to uniquely identify a primary diagnostic process to distinguish the primary diagnostic process from other diagnostic processes.
The console may obtain an Identity (ID) of the ue that fails to query the target version, determine a first message channel corresponding to the interaction based on the ID, and then send a parameter request to the ue through the first message channel. In one example, the Message channel may employ a long connection Message channel, such as a Cloud Message Notification Service (CMNS) that implements Message push, and messages of the channel may be referred to as CMNS messages.
In an example of a parameter request message, the following request parameters may be included: the message type (MessageType) is used for identifying the type of the message, such as a diagnosis message and the like; the version type (VersionType) is used for identifying the type of the software program, such as an operating system or an application program; the key information (gateway Access Key Id) can be used for access key identification of the currently diagnosed project and used for data isolation of the business; diagnostic identifier (TraceId), etc.
The user equipment can obtain the software installation parameters required by the software program according to the parameter request, and the software installation parameters can include various parameters required by the normal installation and upgrading processes of the software program. And then generating a parameter response by adopting the software installation parameters, and sending the parameter response to the user equipment through the first message channel.
And 104, the console queries a server by adopting the software installation parameters so as to diagnose the corresponding failure reason through the server.
After the console acquires the software installation parameters, the server can be queried according to the software installation parameters, so that the server can automatically diagnose the reason of the failure of query of the target version based on the software installation parameters. The console can generate diagnosis information according to the diagnosis identifier and the software installation parameters, and send the diagnosis information to the server. The diagnosis information is used for informing the server of parameter information required by diagnosis, wherein the diagnosis identifier can uniquely identify the diagnosis, the software installation parameters can be used for diagnosing the failure reason, and then the diagnosis information is sent to the server so that the server can carry out diagnosis according to the diagnosis information.
The console and the server may also interact through a message channel, which is referred to as a second message channel. Wherein the server may provide a diagnostic interface to the console for the transfer of data required for the diagnostic service. Thereby sending the diagnostic information to a server, including: and accessing a diagnosis interface through a second message channel, and sending the diagnosis message to a server.
In an example of the diagnostic information, the following parameters may be included: a device temporary token (DeviceToken) for confirming the identity of a device, which may be a console or user device, etc.; a diagnostic identifier (TraceId); the service parameters (manageestcommand) refer to service parameters required by the console to access the server-side diagnostic interface, and include software installation parameters, such as device temporary token (DeviceToken), critical information (gatewayacesskeyid), device mode (DeviceModel), and parameters such as device model, operating system type, operating system version, target version, and the like.
After the server acquires the diagnostic information from the diagnostic interface, the server can acquire the service parameters and other parameters from the diagnostic information, and then the server judges the conditions which cause that the query cannot reach the target version according to the parameters and the software installation conditions set by the target version, so that a corresponding diagnostic result is generated and returned to the console. In this embodiment, the software installation condition refers to a condition required for installing a software program, where the software installation condition corresponds to a software version, and the software installation conditions of different software versions may be the same or different, where the software installation condition includes at least one of: version state conditions, equipment model conditions, version number conditions, increment upgrade package conditions, black and white list conditions and custom filtering conditions.
The version state condition refers to a condition for screening a corresponding state of the target version, for example, the state condition for screening a task corresponding to the target version in the test is a test state if the condition is required, or the state of the target version is detected in the installation process and is a release state if the condition is required; the device model condition refers to a condition of screening a model of the user device, in which a model of a device that allows/disallows installation, and the like can be set; the version number condition refers to a condition for screening the version number of the software program, such as allowing/disallowing upgrading to the version number of the target version; the condition of the increment upgrade package refers to the condition of screening the increment upgrade package of the software program, and screening can be carried out according to whether the increment upgrade package between the current version and the target version of the user equipment exists or not; the version self-defined filter condition refers to other filter conditions of the target version, such as the version of an operating system of the user equipment; the black-and-white list condition refers to a black-and-white list correspondingly set by the target version, wherein the items in the black list are items which are not allowed to be installed, and the items in the white list are items which are allowed to be installed.
The black-and-white list condition may include at least one of: black and white list of version number, black and white list of upgrade version range and black and white list of equipment corresponding to version. The version number black-and-white list refers to a black-and-white list set for the version number of the software program, for example, a version number white list set to allow upgrading to a target version, or a version number white list not allowed to upgrade to a target version, and the like. The upgrade version range black-and-white list refers to a black-and-white list of an upgrade range of a target version, such as a version range white list allowing upgrading to the target version, and a version range black list not allowing upgrading to the target version. The black-and-white list of the device corresponding to the version refers to a black-and-white list of the user device corresponding to the target version, and conditions such as the model of the device can be screened, for example, a white list of the user device which is allowed to be upgraded to the target version, and a black list of the user device which is not allowed to be upgraded to the target version, and the like.
In the embodiment of the application, according to the diagnosis logic configured by the diagnosis interface, the condition that the user equipment does not meet can be inquired from the software installation condition of the target version, so that the failure reason can be screened out, and the corresponding diagnosis result can be obtained. The target version to be queried can be determined, the software installation condition of the target version can be obtained, then the software installation parameters and the software installation condition are adopted for matching, the allowed installation condition which is not met in the software installation condition is determined, and/or the installation rejection condition which is met in the software installation condition is determined, so that the reason of query failure is obtained, the diagnostic result is generated, and the diagnostic result is sent to the console.
Step 106, the console receives the diagnostic results.
The console may receive the diagnostic results from the server. The diagnostic results can then also be presented at the console so that the developer can intuitively understand the reasons for the query failure.
And adjusting the software installation condition of the target version according to the diagnosis result, such as changing the software installation condition which causes query failure, so as to normally query the target version and download the corresponding software installation package.
In the embodiment of the application, the diagnosis process can be initiated by the console, then the equipment end receives and reports the parameters, the corresponding console receives the parameters, the server is inquired for diagnosis, and the console receives and displays the diagnosis result. The console queries the server through the diagnosis interface to diagnose, so that the diagnosis interface does not need to be exposed to the outside, the outside cannot be attacked, and the safety is improved. For example, the device of the console and the server of the service end corresponding to the diagnostic interface may be in the same intranet environment, so that the risk of exposing the interface to the outside may be avoided.
In the embodiment of the application, in the process of diagnosing the reason of the failure of the query of the target version, the console can play a role of a pivot for connecting the equipment terminal and the service terminal, the non-perception query and diagnosis of the user equipment can be realized through the console, and the communication between the console and the service terminal is safer. And the server side carries out the step of automatic diagnosis, so that the condition causing the query failure can be directly and definitely diagnosed from a plurality of conditions, excessive manual operation is not needed, and the efficiency is effectively improved.
Referring to fig. 2, a flow chart of steps of an embodiment of a data processing method of the present application is shown.
Step 202, after the user equipment fails to inquire the target version of the software program, acquiring corresponding software installation parameters from the user equipment.
The user equipment can inquire the required target version in the processes of software program installation, upgrading and the like, and if the target version is not inquired, the user equipment can be determined to fail to inquire the target version of the software program. The console may then send a request to the user device to obtain software installation parameters required by the user device to install the software program. So as to diagnose the reason of the failure of the query of the target version based on the software installation parameters.
And step 206, querying a server by using the software installation parameters so as to diagnose the corresponding failure reason through the server.
And step 208, receiving the diagnosis result returned by the server.
The device of the console may send the software installation parameters to the server for diagnostic queries. After receiving the software installation parameters, the service can judge according to the software installation conditions corresponding to the target version so as to determine the failure reason, generate a diagnosis result based on the failure reason and return the diagnosis result to the console. The console can receive the diagnosis result and can also display the diagnosis result, adjust the software installation condition and the like, so that the failure reason can be quickly determined, and the processing efficiency is improved.
In summary, after the user equipment fails to query the target version of the software program, the console may obtain the corresponding software installation parameters from the user equipment, and then query the server using the software installation parameters, so that the server can automatically diagnose the corresponding failure reasons based on the software installation parameters, and then the console obtains the corresponding diagnosis results, so that the processing efficiency can be effectively improved by automatically diagnosing the failure reasons.
Referring to FIG. 3, a flow chart of steps of another data processing method embodiment of the present application is shown.
Step 302, after the user equipment fails to query the target version of the software program, a parameter request is generated and sent to the user equipment.
The user equipment can inquire the required target version in the installation, upgrading and other processes of the software program, and if the target version is not inquired, the failure of the user equipment in inquiring the target version of the software program can be determined. The console then generates a parameter request based on the target version, the device identifier, and the like, where the parameter request is used to request to obtain software installation parameters of the user device for the software program, and then the software installation parameters may be sent to the terminal device.
Wherein the generating a parameter request and sending the parameter request to the user equipment comprises: determining a diagnosis identifier, and generating a parameter request according to the diagnosis identifier; and sending the parameter request to the user equipment through a first message channel. The diagnostic process for the cause of failure may generate a unique diagnostic identifier and may then generate a parameter request based on the diagnostic identifier, the diagnostic request being sent to the user equipment via the first message channel.
The user equipment can obtain the software installation parameters required by the software program according to the parameter request, and the software installation parameters can include various parameters required by the normal installation and upgrading processes of the software program. And then generating a parameter response by adopting the software installation parameters, and sending the parameter response to the user equipment through the first message channel.
And 304, receiving a parameter response fed back by the user equipment according to the parameter request, and acquiring software installation parameters from the parameter response.
The console can receive the parameter response returned by the user equipment through the first message channel, and then obtains the software installation parameters from the lycopene adoption request.
And step 306, generating diagnosis information according to the diagnosis identifier and the software installation parameters, and sending the diagnosis information to a server.
The console may generate diagnostic information based on the diagnostic identifier and the software installation parameters and then access the diagnostic interface through a second message channel to send the diagnostic information to the server.
After the server acquires the diagnostic information from the diagnostic interface, the server can acquire the service parameters and other parameters from the diagnostic information, and then the server judges the conditions which cause that the query cannot reach the target version according to the parameters and the software installation conditions set by the target version, so that a corresponding diagnostic result is generated and returned to the console.
And step 308, receiving the diagnosis result returned by the server.
And 310, displaying the diagnosis result.
The equipment of the console receives the diagnosis result returned by the server, and then the diagnosis result is displayed on the console, so that a developer can intuitively know the reason of the query failure.
Take the scenario of application in software development testing as an example. The console can be used for developing and testing the software program, so that the test task of the software program can be created on the console, the test, online release and other operations can be executed, and diagnosis can be performed if the problems such as inquiry failure exist in the test process.
An interface of a console is shown in fig. 4, in which a list of test tasks and operation controls that have been created are included. The test task list can comprise items such as a task ID, a version number, a state, creation time and the like, wherein the task ID is used for uniquely identifying one test task, the version number is used for identifying the version number of a test version of a software program corresponding to the test task, and the state is used for identifying the state of the test task; the creation time is used to identify the time at which the test task was created. The operation control comprises: the method comprises the steps of creating a control, a test control, a release control, a diagnosis query control, other controls and the like, wherein the created control is used for creating a test task, the test control is used for executing a test of a selected task, the release control is used for releasing a test version corresponding to the test task, the diagnosis query is used for diagnosing problems occurring in the test task, such as the reason that a certain test device fails to query a new version, and other failure problems occurring in a test process can also be diagnosed, and other controls can be one control or a set of a plurality of controls, so that other controls can be set according to the test requirements. The test task list may further include other items such as a latest test time, and the like, and the other controls may include a modification control, a viewing control, a condition management control, and the like, which are not listed one by one and should not be construed as a limitation to the embodiment of the present application.
The task to be tested can be selected on the interface corresponding to the console, then each testing device can be controlled to test a new version according to the task, the new version is a target version, and in the testing process of the task, if a certain testing device does not inquire the target version, a diagnosis process can be initiated through the console. After the task is selected, a diagnosis query control can be triggered, and then a diagnosis query interface is entered. An exemplary diagnostic query interface schematic is shown in FIG. 5, the diagnostic query interface comprising: an ID type selection control, an ID input box, a diagnostics control (such as start diagnostics in FIG. 5), and a diagnostics results display area. In this example, the query failure of the test device is diagnosed, so the option can be selected in the ID type selection control: and then inputting the device ID of the test device in an "original device ID" corresponding input box, wherein the device ID can be input by a developer or automatically obtained based on a test failure result. And then triggering the diagnosis control to diagnose the test equipment. The unique diagnosis identifier can be automatically generated in the diagnosis process, and the parameter request is generated according to parameters such as the version number of the target version, the equipment identifier of the testing equipment and the like. Then the console uses the first message channel of the bottom layer to push the parameter request message to the user equipment, and informs the user equipment that the current console needs to be upgraded and inquired and diagnosed, and the equipment reports the software installation parameters, such as various parameters used in normal inquiry and upgrade, to the console through the first message channel.
After receiving the returned parameter response, the console can acquire the software installation parameters from the parameter response, then generate corresponding diagnostic information through the software installation parameters, and access the diagnostic interface of the server through the second message channel. The server judges the condition which causes that the target version can not be inquired according to the parameters and the software installation condition set by the target version, thereby generating a corresponding diagnosis result and returning the diagnosis result to the console. After the console receives the diagnosis result, the diagnosis result can be displayed in a diagnosis query interface. According to the installation condition of the inquired software, the diagnosis result may have various types, such as invalid model, being in black and white list, inconsistent state, etc., and may also display information such as parameters corresponding to errors, etc.
In one example, the diagnostic result may include one or more of the following:
1. an invalid model;
2. the version can be queried normally by the device, if the version is not found, please check whether the version queried by the device is a higher version or a milestone version;
3. the version is not a test, pre-release or release version, or the device is not in a test group and cannot be queried;
4. the number of the allowed devices of the version pre-release is full and cannot be inquired;
5. error position: checking version number and equipment parameters: 1.0, version configuration: 0.9;
6. error position: checking a version number blacklist, and equipment parameters: 1.0, version configuration: 1.0,1.1,1.2;
7. error position: checking a version number white list, and equipment parameters: 1.0, version configuration: 0.9,1.1;
8. error position: checking a custom filtering condition, cond1, equipment parameters: a, version configuration: b;
9. error position: checking the custom filtering condition, cond3, equipment parameters: 10, version configuration: 11.
according to the diagnosis result, the reason of failure can be found quickly, and for the reason needing to be solved, the condition management control can be selected from other controls based on the diagnosis result to adjust the corresponding software installation condition.
Compared with an artificial parameter mode, the method and the device for detecting the failure cause can automatically detect the failure cause, effectively improve the detection efficiency and have timeliness. And the console is used for carrying out unified control, so that the diagnosis result is not exposed in the automatic query process, the risk caused by the exposure of the interface to the outside is avoided, and the safety is improved. And the user equipment does not sense in the diagnosis process, so that the influence on the user is reduced.
It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the embodiments are not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the embodiments. Further, those skilled in the art will also appreciate that the embodiments described in the specification are presently preferred and that no particular act is required of the embodiments of the application.
On the basis of the above embodiments, the present embodiment further provides a data processing apparatus, which is applied to a device corresponding to a console.
Referring to fig. 6, a block diagram of a data processing apparatus according to an embodiment of the present application is shown, which may specifically include the following modules:
the parameter obtaining module 602 is configured to obtain, after the user equipment fails to query the target version of the software program, a corresponding software installation parameter from the user equipment.
A diagnosis module 604, configured to query a server using the software installation parameter, so as to diagnose a corresponding failure reason by the server.
And a result receiving module 606, configured to receive a diagnosis result returned by the server.
In summary, after the user equipment fails to query the target version of the software program, the console may obtain corresponding software installation parameters from the user equipment, and then query the server using the software installation parameters, so that the server can automatically diagnose the corresponding failure reason based on the software installation parameters, and then the console obtains a corresponding diagnosis result, so that the processing efficiency can be effectively improved by automatically diagnosing the failure reason.
Referring to fig. 7, a block diagram of another data processing apparatus according to an embodiment of the present application is shown, which may specifically include the following modules:
the parameter obtaining module 602 is configured to obtain, from the user equipment, the corresponding software installation parameter after the user equipment fails to query the target version of the software program.
A diagnosis module 604, configured to query a server using the software installation parameter, so as to diagnose a corresponding failure reason by the server.
And a result receiving module 606, configured to receive a diagnosis result returned by the server.
A display module 608, configured to display the diagnosis result.
An adjusting module 610, configured to adjust the software installation condition of the target version according to the diagnosis result.
Wherein the target version of the software comprises: a version of the software to be upgraded and/or a version of the software to be installed; the user equipment comprises test equipment. The software installation condition includes at least one of: version state conditions, equipment model conditions, version number conditions, increment upgrade package conditions, black and white list conditions and custom filtering conditions.
The parameter obtaining module 602 includes: a request generation sub-module 6022, a request sending sub-module 6024, and a request receiving sub-module 6026, wherein:
the request generation submodule 6022 is configured to generate a parameter request.
The request sending submodule 6024 is configured to send a parameter request to the user equipment.
The request receiving submodule 6026 is configured to receive a parameter response fed back by the user equipment according to the parameter request, and acquire a software installation parameter from the parameter response.
The request generation submodule 6022 is configured to determine a diagnostic identifier and generate a parameter request according to the diagnostic identifier; the request sending submodule 6024 is configured to send the parameter request to the user equipment through a first message channel.
The diagnostic module 604, comprising: a diagnostic information generating sub-module 6042 and a diagnostic information transmitting sub-module 6044, wherein:
and a diagnostic information generation sub-module 6042 configured to generate diagnostic information according to the diagnostic identifier and the software installation parameter.
And a diagnostic information sending submodule 6044 configured to send the diagnostic information to the server.
The result receiving module 606 is configured to access the diagnostic interface through the second message channel, and send the diagnostic message to the server.
In the embodiment of the application, the diagnosis process can be initiated by the console, then the equipment end receives and reports the parameters, the corresponding console receives the parameters, then the server is inquired for diagnosis, and the console receives and displays the diagnosis result. The console queries the server through the diagnosis interface to diagnose, so that the diagnosis interface does not need to be exposed to the outside, the outside cannot be attacked, and the safety is improved. For example, the device of the console and the server of the service end corresponding to the diagnostic interface may be in the same intranet environment, so that the risk of exposing the interface to the outside may be avoided.
In the embodiment of the application, in the process of diagnosing the reason of the failure of the query of the target version, the console can play a role of a pivot for connecting the device side and the server side, the non-sensing query and diagnosis of the user equipment can be realized through the console, and the communication between the console and the server side is safer. And the server side carries out automatic diagnosis, so that the conditions causing query failure can be directly and definitely diagnosed from a plurality of conditions, excessive manual operation is not needed, and the efficiency is effectively improved.
Compared with an artificial parameter mode, the method and the device for detecting the failure cause can automatically detect the failure cause, effectively improve the detection efficiency and have timeliness. And the console is used for carrying out unified control, so that the diagnosis result is not exposed in the automatic query process, the risk caused by the exposure of the interface to the outside is avoided, and the safety is improved. And the user equipment does not sense in the diagnosis process, so that the influence on the user is reduced.
The present application further provides a non-transitory, readable storage medium, where one or more modules (programs) are stored, and when the one or more modules are applied to a device, the device may execute instructions (instructions) of method steps in this application.
Embodiments of the present application provide one or more machine-readable media having instructions stored thereon, which when executed by one or more processors, cause an electronic device to perform the methods as described in one or more of the above embodiments. In the embodiment of the present application, the electronic device includes a server, a gateway, a user equipment, and the like.
Embodiments of the present disclosure may be implemented as an apparatus, which may include electronic devices such as servers (clusters), terminal devices such as IoT devices, and the like, using any suitable hardware, firmware, software, or any combination thereof, for a desired configuration. Fig. 8 schematically illustrates an example apparatus 800 that may be used to implement various embodiments described in the present application.
For one embodiment, fig. 8 illustrates an example apparatus 800 having one or more processors 802, a control module (chipset) 804 coupled to at least one of the processor(s) 802, a memory 806 coupled to the control module 804, a non-volatile memory (NVM)/storage 808 coupled to the control module 804, one or more input/output devices 810 coupled to the control module 804, and a network interface 812 coupled to the control module 806.
The processor 802 may include one or more single-core or multi-core processors, and the processor 802 may include any combination of general-purpose or special-purpose processors (e.g., graphics processors, application processors, baseband processors, etc.). In some embodiments, the apparatus 800 can be a server or the like of the transcoding end described in the embodiments of the present application.
In some embodiments, the apparatus 800 may include one or more computer-readable media (e.g., the memory 806 or the NVM/storage 808) having instructions 814 and one or more processors 802 that, in conjunction with the one or more computer-readable media, are configured to execute the instructions 814 to implement modules to perform the actions described in this disclosure.
For one embodiment, the control module 804 may include any suitable interface controller to provide any suitable interface to at least one of the processor(s) 802 and/or any suitable device or component in communication with the control module 804.
The control module 804 may include a memory controller module to provide an interface to the memory 806. The memory controller module may be a hardware module, a software module, and/or a firmware module.
The memory 806 may be used, for example, to load and store data and/or instructions 814 for the apparatus 800. For one embodiment, memory 806 may include any suitable volatile memory, such as suitable DRAM. In some embodiments, the memory 806 may comprise a double data rate type four synchronous dynamic random access memory (DDR 4 SDRAM).
For one embodiment, the control module 804 may include one or more input/output controllers to provide an interface to the NVM/storage 808 and input/output device(s) 810.
For example, the NVM/storage 808 may be used to store data and/or instructions 814. NVM/storage 808 may include any suitable non-volatile memory (e.g., flash memory) and/or may include any suitable non-volatile storage device(s) (e.g., one or more Hard Disk Drives (HDDs), one or more Compact Disc (CD) drives, and/or one or more Digital Versatile Disc (DVD) drives).
The NVM/storage 808 may include storage resources that are physically part of the device on which the apparatus 800 is installed, or it may be accessible by the device and may not necessarily be part of the device. For example, the NVM/storage 808 may be accessible over a network via the input/output device(s) 810.
Input/output device(s) 810 may provide an interface for apparatus 800 to communicate with any other suitable device, input/output devices 810 may include communication components, audio components, sensor components, and so forth. The network interface 812 may provide an interface for the device 800 to communicate over one or more networks, and the device 800 may wirelessly communicate with one or more components of a wireless network according to any of one or more wireless network standards and/or protocols, such as accessing a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G, etc., or a combination thereof.
For one embodiment, at least one of the processor(s) 802 may be packaged together with logic for one or more controller(s) (e.g., memory controller module) of the control module 804. For one embodiment, at least one of the processor(s) 802 may be packaged together with logic for one or more controllers of the control module 804 to form a System In Package (SiP). For one embodiment, at least one of the processor(s) 802 may be integrated on the same die with logic for one or more controller(s) of the control module 804. For one embodiment, at least one of the processor(s) 802 may be integrated on the same die with logic of one or more controllers of the control module 804 to form a system on a chip (SoC).
In various embodiments, the apparatus 800 may be, but is not limited to being: a server, a desktop computing device, or a mobile computing device (e.g., a laptop computing device, a handheld computing device, a tablet, a netbook, etc.), among other terminal devices. In various embodiments, the apparatus 800 may have more or fewer components and/or different architectures. For example, in some embodiments, device 800 includes one or more cameras, a keyboard, a Liquid Crystal Display (LCD) screen (including a touch screen display), a non-volatile memory port, multiple antennas, a graphics chip, an Application Specific Integrated Circuit (ASIC), and speakers.
An embodiment of the present application provides an electronic device, including: one or more processors; and one or more machine readable media having instructions stored thereon, which when executed by the one or more processors, cause the electronic device to perform a data processing method as described in one or more of the embodiments of the present application.
For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
The embodiments in the present specification are all described in a progressive manner, and each embodiment focuses on differences from other embodiments, and portions that are the same and similar between the embodiments may be referred to each other.
Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present application have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the true scope of the embodiments of the application.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising a … …" does not exclude the presence of another identical element in a process, method, article, or terminal apparatus that comprises the element.
The foregoing detailed description has been made of a data processing method, a data processing apparatus, an electronic device, and a storage medium, and specific examples are applied herein to explain the principles and embodiments of the present application, where the descriptions of the foregoing examples are only used to help understand the method and its core ideas of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, the specific implementation manner and the application scope may be changed, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims (18)

1. A method of data processing, the method comprising:
after user equipment fails to inquire a target version of a software program according to a request, acquiring corresponding software installation parameters from the user equipment, wherein the request comprises an installation request or an upgrading request;
generating diagnosis information according to the diagnosis identifier and the software installation parameters, sending the diagnosis information to a server, so that the server determines software installation conditions which cause that the target version cannot be inquired according to the diagnosis information, and determining failure reasons of inquiry failure of the corresponding target version based on the software installation conditions;
and receiving the diagnosis result returned by the server.
2. The method of claim 1, wherein the target version of software comprises: a version of the software to be upgraded and/or a version of the software to be installed; the user equipment comprises test equipment.
3. The method of claim 1, wherein the obtaining corresponding software installation parameters from the user equipment comprises:
generating a parameter request and sending the parameter request to the user equipment;
and receiving a parameter response fed back by the user equipment according to the parameter request, and acquiring software installation parameters from the parameter response.
4. The method of claim 3, wherein generating and sending a parameter request to the UE comprises:
determining a diagnosis identifier, and generating a parameter request according to the diagnosis identifier;
and sending the parameter request to the user equipment through a first message channel.
5. The method of claim 1, wherein said sending the diagnostic information to a server comprises:
and accessing the diagnosis interface through a second message channel, and sending the diagnosis information to the server.
6. The method of claim 1, further comprising:
and displaying the diagnosis result.
7. The method of claim 1, further comprising:
and adjusting the software installation condition of the target version according to the diagnosis result.
8. The method of claim 7, wherein the software installation condition comprises at least one of:
version state conditions, equipment model conditions, version number conditions, increment upgrade package conditions, black and white list conditions and custom filtering conditions.
9. A data processing apparatus, characterized in that said apparatus comprises:
the software upgrading method comprises the steps that a parameter obtaining module is used for obtaining corresponding software installation parameters from user equipment after the user equipment fails to inquire a target version of a software program according to a request, wherein the request comprises an installation request or an upgrading request;
the diagnosis module is used for generating diagnosis information according to the diagnosis identifier and the software installation parameters, sending the diagnosis information to the server, enabling the server to determine the software installation conditions which cause that the target version cannot be inquired according to the diagnosis information, and determining the failure reason of the inquiry failure of the corresponding target version based on the software installation conditions;
and the result receiving module is used for receiving the diagnosis result returned by the server.
10. The apparatus of claim 9, wherein the target version of the software comprises: a version of the software to be upgraded and/or a version of the software to be installed; the user equipment comprises test equipment.
11. The apparatus of claim 9, wherein the parameter obtaining module comprises:
the request generation submodule is used for generating a parameter request;
the request sending submodule is used for sending a parameter request to the user equipment;
and the request receiving submodule is used for receiving the parameter response fed back by the user equipment according to the parameter request and acquiring the software installation parameters from the parameter response.
12. The apparatus of claim 11,
the request generation submodule is used for determining a diagnosis identifier and generating a parameter request according to the diagnosis identifier;
and the request sending submodule is used for sending the parameter request to the user equipment through a first message channel.
13. The apparatus of claim 9,
and the diagnostic information sending submodule is used for accessing the diagnostic interface through a second message channel and sending the diagnostic information to the server.
14. The apparatus of claim 9, further comprising:
and the display module is used for displaying the diagnosis result.
15. The apparatus of claim 9, further comprising:
and the adjusting module is used for adjusting the software installation condition of the target version according to the diagnosis result.
16. The apparatus of claim 15, wherein the software installation condition comprises at least one of:
version state conditions, device model conditions, version number conditions, incremental upgrade package conditions, black and white list conditions, and custom filter conditions.
17. An electronic device, comprising:
a processor; and
memory having stored thereon executable code which, when executed, causes the processor to perform a data processing method as claimed in any one of claims 1-8.
18. One or more machine readable media having executable code stored thereon that when executed cause a processor to perform a data processing method as claimed in any one of claims 1 to 8.
CN201810574783.2A 2018-06-06 2018-06-06 Data processing method, device, equipment and storage medium Active CN110569046B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810574783.2A CN110569046B (en) 2018-06-06 2018-06-06 Data processing method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810574783.2A CN110569046B (en) 2018-06-06 2018-06-06 Data processing method, device, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN110569046A CN110569046A (en) 2019-12-13
CN110569046B true CN110569046B (en) 2023-04-11

Family

ID=68771962

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810574783.2A Active CN110569046B (en) 2018-06-06 2018-06-06 Data processing method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN110569046B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112100070A (en) * 2020-09-15 2020-12-18 北京三快在线科技有限公司 Version defect detection method and device, server and storage medium
CN113157316A (en) * 2021-05-17 2021-07-23 中国银行股份有限公司 Version matching processing method and device
CN116541033A (en) * 2022-01-25 2023-08-04 华为技术有限公司 Software loading method and related device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101695162A (en) * 2009-10-22 2010-04-14 中兴通讯股份有限公司 Method and device for upgrading aerial firmware on mobile terminal
CN101841837A (en) * 2009-03-18 2010-09-22 华为技术有限公司 Information processing method, network diagnosis method, terminal, server and system
CN105549991A (en) * 2015-11-27 2016-05-04 深圳市元征软件开发有限公司 Software upgrading method and system for automobile diagnosis device
CN106406952A (en) * 2016-09-21 2017-02-15 广州爱九游信息技术有限公司 An electronic terminal and an application program management device and method

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3265916B1 (en) * 2015-03-04 2020-12-16 Verifyter AB A method for identifying a cause for a failure of a test

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101841837A (en) * 2009-03-18 2010-09-22 华为技术有限公司 Information processing method, network diagnosis method, terminal, server and system
CN101695162A (en) * 2009-10-22 2010-04-14 中兴通讯股份有限公司 Method and device for upgrading aerial firmware on mobile terminal
CN105549991A (en) * 2015-11-27 2016-05-04 深圳市元征软件开发有限公司 Software upgrading method and system for automobile diagnosis device
CN106406952A (en) * 2016-09-21 2017-02-15 广州爱九游信息技术有限公司 An electronic terminal and an application program management device and method

Also Published As

Publication number Publication date
CN110569046A (en) 2019-12-13

Similar Documents

Publication Publication Date Title
CN110569046B (en) Data processing method, device, equipment and storage medium
US20160291959A1 (en) Remote Embedded Device Update Platform Apparatuses, Methods and Systems
US20160291940A1 (en) Remote Embedded Device Update Platform Apparatuses, Methods and Systems
US20160294614A1 (en) Remote Embedded Device Update Platform Apparatuses, Methods and Systems
US20160196131A1 (en) Remote Embedded Device Update Platform Apparatuses, Methods and Systems
US20160196132A1 (en) Remote Embedded Device Update Platform Apparatuses, Methods and Systems
US20160294605A1 (en) Remote Embedded Device Update Platform Apparatuses, Methods and Systems
CN106909411B (en) File updating method and device
CN106802814B (en) Method and device for upgrading software version
CN112486629B (en) Micro-service state detection method, micro-service state detection device, electronic equipment and storage medium
CN106897095B (en) Method and device for hot repairing application program, readable storage medium and computing equipment
WO2020076382A1 (en) Dependency lock in cicd pipelines
CN110874315B (en) Test method, test device, electronic equipment and storage medium
CN110784374A (en) Method, device, equipment and system for monitoring operation state of service system
CN109324962B (en) Method and equipment for testing application program based on cloud Internet of things technology
CN111506358B (en) Method and device for updating container configuration
CN111712795A (en) Method, apparatus, computer program product and readable medium for evaluating application deployment
US9473874B2 (en) Distribution apparatus and distribution method
CN109766235A (en) Configuration file detection method, system, equipment and medium based on software supervision
CN114328275A (en) System testing method, device, computer equipment and storage medium
CN115437910A (en) Vehicle offline detection method and device, vehicle, management equipment and storage medium
CN114153512A (en) Resource loading method and device, electronic equipment and storage medium
KR20160118190A (en) Method for verifying mobile application and terminal using the same
WO2020147415A1 (en) Snapshot service process management method and apparatus, electronic device, and readable storage medium
CN112650557A (en) Command execution method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20201217

Address after: Room 603, 6 / F, Roche Plaza, 788 Cheung Sha Wan Road, Kowloon, China

Applicant after: Zebra smart travel network (Hong Kong) Ltd.

Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands

Applicant before: Alibaba Group Holding Ltd.

GR01 Patent grant
GR01 Patent grant