CN109150951B - Method and device for starting Activity of Android system - Google Patents
Method and device for starting Activity of Android system Download PDFInfo
- Publication number
- CN109150951B CN109150951B CN201810596983.8A CN201810596983A CN109150951B CN 109150951 B CN109150951 B CN 109150951B CN 201810596983 A CN201810596983 A CN 201810596983A CN 109150951 B CN109150951 B CN 109150951B
- Authority
- CN
- China
- Prior art keywords
- push message
- activity
- starting
- pendingintent
- intent
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The specification discloses a method and a device for starting Activity of an Android system. The method comprises the following steps: responding to a push message from a server, and analyzing the push message based on a preset Activity starting rule; if the analysis fails, converting the starting character string carried by the push message into Intent; creating a PendingIntent based on the Intent; and when the notification bar message corresponding to the PendingIntent is triggered, starting Activity corresponding to the push message.
Description
Technical Field
The specification relates to the technical field of terminals, in particular to a method and a device for starting Activity of an Android system.
Background
Activity is one of the four most basic and common components of the Android system. Activity provides a screen that provides interactive interface functionality to the user. In the Android system, the launching of Activity can be realized by Intent based on Activity launch rules.
Disclosure of Invention
In view of this, the present specification provides a method and a device for starting Activity of an Android system.
Specifically, the description is realized by the following technical scheme:
a starting method of Android system Activity comprises the following steps:
responding to a push message from a server, and analyzing the push message based on a preset Activity starting rule;
if the analysis fails, converting the starting character string carried by the push message into Intent;
creating a PendingIntent based on the Intent;
and when the notification bar message corresponding to the PendingIntent is triggered, starting Activity corresponding to the push message.
An Android system Activity initiating device, comprising:
the analysis unit is used for responding to the push message from the server and analyzing the push message based on a preset Activity starting rule;
the conversion unit is used for converting the starting character string carried by the push message into Intent if the analysis fails;
a creation unit that creates a PendingIntent based on the Intent;
and the starting unit is used for starting the Activity corresponding to the push message when the notification bar message corresponding to the PendingIntent is triggered.
An Android system Activity initiating device, comprising:
a processor;
a memory for storing machine executable instructions;
wherein, by reading and executing machine-executable instructions stored by the memory that correspond to the Android system Activity launch logic, the processor is caused to:
responding to a push message from a server, and analyzing the push message based on a preset Activity starting rule;
if the analysis fails, converting the starting character string carried by the push message into Intent;
creating a PendingIntent based on the Intent;
and when the notification bar message corresponding to the PendingIntent is triggered, starting Activity corresponding to the push message.
As can be seen from the above description, in the present specification, by using conversion between a character string and an Intent, when an Activity start rule is not configured at a client, the Intent for starting the Activity is converted into a start character string and configured in a push message of a server, so as to implement cloud-end of the Activity start function. When the Activity is newly added, the Activity can be started without configuring a corresponding Activity starting rule in the client, and the method is simple and convenient. For the user, the client does not need to be upgraded frequently, and the experience is better.
Drawings
Fig. 1 is a flowchart illustrating a method for starting Android system Activity according to an exemplary embodiment of the present specification.
Fig. 2 is a flowchart illustrating another method for starting Android system Activity according to an exemplary embodiment of the present specification.
Fig. 3 is a schematic structural diagram of an initiating device for Android system Activity according to an exemplary embodiment of the present disclosure.
Fig. 4 is a block diagram of an Android system Activity initiating device according to an exemplary embodiment of the present disclosure.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.
The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the present specification. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
Fig. 1 is a flowchart illustrating a method for starting Android system Activity according to an exemplary embodiment of the present specification.
The starting method of the Android system Activity can be applied to client software loaded on an intelligent terminal, and the intelligent terminal can comprise: tablet computers, smart phones, PDAs (Personal Digital assistants), and the like, which are not limited in this specification.
Referring to fig. 1, the method for starting Activity of the Android system may include the following steps:
step 102, responding to a push message from a server, and analyzing the push message based on a preset Activity starting rule.
And step 104, if the analysis fails, converting the starting character string carried by the push message into Intent.
In this embodiment, the start string is typically pre-configured in the push message by the developer.
For example, a developer may start Activity corresponding to a push message locally through Intent, and then convert Intent into a character string through conversion between Intent and the character string, for convenience of distinction, the character string obtained after Intent conversion may be referred to as a conversion character string, and then configure the conversion character string into the push message of the server.
And 106, creating PendingIntent based on the Intent.
And step 108, when the notification bar message corresponding to the PendingIntent is triggered, starting Activity corresponding to the push message.
As can be seen from the above description, in the embodiment, by using the conversion between the character string and the Intent, when the Activity start rule is not configured at the client, the Intent for starting the Activity is converted into the start character string and configured in the push message of the server, so that the cloud-end of the Activity start function is realized. When the Activity is newly added, the Activity can be started without configuring a corresponding Activity starting rule in the client, and the method is simple and convenient. For the user, the client does not need to be upgraded frequently, and the experience is better.
Fig. 2 is a flowchart illustrating another method for starting Android system Activity according to an exemplary embodiment of the present specification.
Referring to fig. 2, the method for starting Activity of the Android system may include the following steps:
step 202, responding to a push message from a server, and analyzing the push message based on a predetermined Activity starting rule.
In this embodiment, the predetermined Activity launching rule is usually configured in the client software in advance by a developer, and can be used to implement launching of the corresponding Activity.
In this embodiment, after receiving the push message sent by the server, the client may parse the push message according to the configured Activity initiation rule.
If the analysis is successful, the Activity corresponding to the push message can be started.
For example, the client may create a PendingIntent based on the Activity launch rule and present the push message to the user via a notification bar message. And the jumping behavior of the notification bar message after being clicked by the user depends on the created PendingIntent. For example, after the user clicks the push message displayed in the notification bar, the client may call an Intent of the PendingIntent, and then display the Activity corresponding to the push message.
If the parsing fails, step 204 is executed. In other words, if the push message cannot be parsed based on the predetermined Activity launching rule, step 204 is executed.
And step 204, converting the starting character string carried by the push message into Intent.
Based on the analysis result in step 202, if the analysis fails, it usually indicates that the client does not configure the Activity start rule corresponding to the push message.
In this embodiment, for an Activity for which a start rule is not configured on a client, a developer may start the Activity locally in advance, and after the Activity is successfully started, a string _ Intent may be used to convert the Intent into a start string, and the start string is configured in a server push message corresponding to the Activity.
For example, the launch string may be configured into a push message as a Key value.
For another example, the start character string may be configured in a designated field of the push message, which is not particularly limited in this specification.
In this embodiment, for a push message that fails to be parsed, the client may convert, according to the configuration location of the start string, the start string carried in the push message into an Intent through Intent.
For example, the Value corresponding to the specified Key Value in the push message may be converted to Intent.
For another example, the string of the specified field in the push message may be converted into Intent, which is not limited in this specification.
In this embodiment, if the start character string carried in the push message cannot be converted into Intent, the processing flow may be ended.
At step 206, a PendingIntent is created based on the Intent.
Based on the foregoing step 204, after the start character string carried by the push message is converted into Intent, a PendingIntent may be created based on the Intent, and the push message is displayed to the user through the notification bar.
And step 208, when the notification bar message corresponding to the PendingIntent is triggered, starting Activity corresponding to the push message.
In this embodiment, when the user clicks the displayed notification bar message, the client may call an Intent of the PendingIntent, and further display the Activity corresponding to the push message.
As can be seen from the above description, in the present specification, by using conversion between a character string and an Intent, when an Activity start rule is not configured at a client, the Intent for starting the Activity is converted into a start character string and configured in a push message of a server, so as to implement cloud-end of the Activity start function. When the Activity is newly added, the Activity can be started without configuring a corresponding Activity starting rule in the client, and the method is simple and convenient. For the user, the client does not need to be upgraded frequently, and the experience is better.
Corresponding to the embodiment of the starting method of the Android system Activity, the specification further provides an embodiment of a starting device of the Android system Activity.
The embodiment of the starting device of the Android system Activity in the specification can be applied to client software loaded on a terminal. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and as a logical device, the device is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor of the terminal where the device is located. From a hardware aspect, as shown in fig. 3, the hardware structure diagram of the terminal where the Android system Activity initiating device is located in this specification is a diagram, except for the processor, the memory, the network interface, and the nonvolatile memory shown in fig. 3, the terminal where the device is located in the embodiment may also include other hardware according to the actual function of the terminal, which is not described again.
Fig. 4 is a block diagram of an Android system Activity initiating device according to an exemplary embodiment of the present disclosure.
Referring to fig. 4, the Android Activity initiator 300 may be applied to the terminal shown in fig. 3, and includes: parsing unit 301, converting unit 302, creating unit 303 and initiating unit 304.
The analysis unit 301 analyzes, in response to a push message from a server, the push message based on a predetermined Activity start rule;
a conversion unit 302, configured to convert the start character string carried by the push message into Intent if the parsing fails;
a creating unit 303 that creates PendingIntent based on the Intent;
and the starting unit 304 is configured to start Activity corresponding to the push message when the notification bar message corresponding to the PendingIntent is triggered.
Optionally, the start character string is located in a designated field of the push message.
Optionally, the conversion unit 302 ends the processing flow when the start character string carried in the push message cannot be converted into Intent.
Optionally, the starting character string carried by the push message is configured in advance based on the Activity corresponding to the push message.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
Corresponding to the embodiment of the method for starting the Android system Activity, the present specification further provides a device for starting the Android system Activity, where the device for starting the Android system Activity includes: a processor and a memory for storing machine executable instructions. Wherein the processor and the memory are typically interconnected by means of an internal bus. In other possible implementations, the device may also include an external interface to enable communication with other devices or components.
In this embodiment, by reading and executing the machine executable instructions stored in the memory corresponding to the Android system Activity launch logic, the processor is caused to:
responding to a push message from a server, and analyzing the push message based on a preset Activity starting rule;
if the analysis fails, converting the starting character string carried by the push message into Intent;
creating a PendingIntent based on the Intent;
and when the notification bar message corresponding to the PendingIntent is triggered, starting Activity corresponding to the push message.
Optionally, the start character string is located in a designated field of the push message.
Optionally, the method further includes:
and when the starting character string carried by the push message cannot be converted into Intent, ending the processing flow.
Optionally, the starting character string carried by the push message is configured in advance based on the Activity corresponding to the push message.
Corresponding to the foregoing embodiment of the method for starting the Activity of the Android system, this specification further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements the following steps:
responding to a push message from a server, and analyzing the push message based on a preset Activity starting rule;
if the analysis fails, converting the starting character string carried by the push message into Intent;
creating a PendingIntent based on the Intent;
and when the notification bar message corresponding to the PendingIntent is triggered, starting Activity corresponding to the push message.
Optionally, the start character string is located in a designated field of the push message.
Optionally, the method further includes:
and when the starting character string carried by the push message cannot be converted into Intent, ending the processing flow.
Optionally, the starting character string carried by the push message is configured in advance based on the Activity corresponding to the push message.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.
Claims (9)
1. A method for starting Activity of an Android system is applied to a client and comprises the following steps:
responding to a push message from a server, and analyzing the push message based on a preset Activity starting rule; the server is deployed at the cloud end;
if the analysis is failed, determining that the Activity starting rule is not configured at the client side, and converting the starting character string carried by the push message into Intent;
creating a PendingIntent based on the Intent;
when the notification bar message corresponding to the PendingIntent is triggered, starting Activity corresponding to the push message;
and if the analysis is successful, creating PendingIntent based on the Activity starting rule, and starting the Activity corresponding to the push message when the notification bar message corresponding to the PendingIntent is triggered.
2. The method of claim 1, wherein the first and second light sources are selected from the group consisting of,
the start string is located in a designated field of the push message.
3. The method of claim 1, further comprising:
and when the starting character string carried by the push message cannot be converted into Intent, ending the processing flow.
4. The method of claim 1, wherein the first and second light sources are selected from the group consisting of,
and the starting character string carried by the push message is configured in advance based on the Activity corresponding to the push message.
5. An Android system Activity starting device applied to a client side comprises:
the analysis unit is used for responding to the push message from the server and analyzing the push message based on a preset Activity starting rule; the server is deployed at the cloud end;
the conversion unit is used for converting the starting character string carried by the push message into Intent if the client is determined not to be configured with the Activity starting rule if the analysis fails;
a creation unit that creates a PendingIntent based on the Intent;
the starting unit is used for starting the Activity corresponding to the push message when the notification bar message corresponding to the PendingIntent is triggered;
and if the analysis is successful, creating PendingIntent based on the Activity starting rule, and starting the Activity corresponding to the push message when the notification bar message corresponding to the PendingIntent is triggered.
6. The apparatus of claim 5, wherein the first and second electrodes are disposed in a common plane,
the start string is located in a designated field of the push message.
7. The apparatus of claim 5, wherein the first and second electrodes are disposed in a common plane,
and the conversion unit is used for finishing the processing flow when the starting character string carried by the push message cannot be converted into Intent.
8. The apparatus of claim 5, wherein the first and second electrodes are disposed in a common plane,
and the starting character string carried by the push message is configured in advance based on the Activity corresponding to the push message.
9. An Android system Activity initiating device, comprising:
a processor;
a memory for storing machine executable instructions;
wherein, by reading and executing machine-executable instructions stored by the memory that correspond to the Android system Activity launch logic, the processor is caused to:
responding to a push message from a server, and analyzing the push message based on a preset Activity starting rule; the server is deployed at the cloud end;
if the analysis is failed, determining that the Activity startup rule is not configured at the client side, and converting the startup character string carried by the push message into Intent;
creating a PendingIntent based on the Intent;
when the notification bar message corresponding to the PendingIntent is triggered, starting Activity corresponding to the push message;
and if the analysis is successful, creating PendingIntent based on the Activity starting rule, and starting the Activity corresponding to the push message when the notification bar message corresponding to the PendingIntent is triggered.
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810596983.8A CN109150951B (en) | 2018-06-11 | 2018-06-11 | Method and device for starting Activity of Android system |
| TW108107051A TWI714006B (en) | 2018-06-11 | 2019-03-04 | Method and device for starting Active system of Android system |
| PCT/CN2019/078090 WO2019237780A1 (en) | 2018-06-11 | 2019-03-14 | Android system activity launching method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810596983.8A CN109150951B (en) | 2018-06-11 | 2018-06-11 | Method and device for starting Activity of Android system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109150951A CN109150951A (en) | 2019-01-04 |
| CN109150951B true CN109150951B (en) | 2020-05-29 |
Family
ID=64801892
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810596983.8A Active CN109150951B (en) | 2018-06-11 | 2018-06-11 | Method and device for starting Activity of Android system |
Country Status (3)
| Country | Link |
|---|---|
| CN (1) | CN109150951B (en) |
| TW (1) | TWI714006B (en) |
| WO (1) | WO2019237780A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109150951B (en) * | 2018-06-11 | 2020-05-29 | 阿里巴巴集团控股有限公司 | Method and device for starting Activity of Android system |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106897057A (en) * | 2017-01-20 | 2017-06-27 | 北京奇虎科技有限公司 | The method and device on plug-in unit call notification column |
| CN107193674A (en) * | 2017-06-29 | 2017-09-22 | 武汉斗鱼网络科技有限公司 | The processing method and processing device of online PUSH message |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103593605B (en) * | 2013-10-24 | 2016-11-09 | 复旦大学 | A kind of Android platform application program dynamic analysis system based on authority usage behavior |
| CN105700896B (en) * | 2014-11-24 | 2019-03-08 | 阿里巴巴集团控股有限公司 | A kind of starting method and apparatus of App |
| CN104486389B (en) * | 2014-12-04 | 2018-02-13 | 上海斐讯数据通信技术有限公司 | Communication port method for building up and system between a kind of window management service and APP |
| US20180017403A1 (en) * | 2016-07-12 | 2018-01-18 | Google Inc. | Navigation API for Linking Software Applications |
| CN106775817A (en) * | 2016-11-23 | 2017-05-31 | 深圳铂睿智恒科技有限公司 | Intelligent terminal is spread its tail control method, system and the intelligent terminal of advertisement |
| US20180160252A1 (en) * | 2016-12-05 | 2018-06-07 | Microsoft Technology Licensing, Llc | Pre-provisioning of a device |
| CN109150951B (en) * | 2018-06-11 | 2020-05-29 | 阿里巴巴集团控股有限公司 | Method and device for starting Activity of Android system |
-
2018
- 2018-06-11 CN CN201810596983.8A patent/CN109150951B/en active Active
-
2019
- 2019-03-04 TW TW108107051A patent/TWI714006B/en active
- 2019-03-14 WO PCT/CN2019/078090 patent/WO2019237780A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106897057A (en) * | 2017-01-20 | 2017-06-27 | 北京奇虎科技有限公司 | The method and device on plug-in unit call notification column |
| CN107193674A (en) * | 2017-06-29 | 2017-09-22 | 武汉斗鱼网络科技有限公司 | The processing method and processing device of online PUSH message |
Non-Patent Citations (2)
| Title |
|---|
| "Android Notification的使用";叶应是叶;《https://yq.aliyun.com/articles/649735》;20170217;第1-2页 * |
| "将Intent序列化，像Uri一样传递Intent!!!";承香墨影;《https://www.cnblogs.com/plokmju/p/7660825.html》;20171013;第1-7页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109150951A (en) | 2019-01-04 |
| TW202001554A (en) | 2020-01-01 |
| WO2019237780A1 (en) | 2019-12-19 |
| TWI714006B (en) | 2020-12-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109951547B (en) | Transaction request parallel processing method, device, equipment and medium | |
| CN109901881B (en) | Plug-in loading method and device of application program, computer equipment and storage medium | |
| CN108228444B (en) | Test method and device | |
| CN108776587B (en) | Data acquisition method and device, computer equipment and storage medium | |
| US10579837B2 (en) | Method, device and electronic apparatus for testing capability of analyzing a two-dimensional code | |
| CN105094777B (en) | Realize the method and device for applying screenshotss | |
| CN107479868B (en) | Interface loading method, device and equipment | |
| US20170163787A1 (en) | Method and electronic device for upgrading or downgrading system | |
| CN109542878B (en) | List creation method and device | |
| CN110007936B (en) | Data processing method and device | |
| JP2019509567A (en) | Resource loading method, service function implementing method and apparatus for application (APP) | |
| CN114374703B (en) | Cloud mobile phone information acquisition method, device, equipment and storage medium | |
| CN105119944A (en) | Application starting method and related device | |
| US20170188214A1 (en) | Method and electronic device for sharing multimedia information | |
| CN106874020B (en) | Method and device for starting plug-in | |
| CN109150951B (en) | Method and device for starting Activity of Android system | |
| CN105791514B (en) | Application starting monitoring method and device | |
| CN107357481B (en) | Message display method and message display device | |
| CN108446144B (en) | Application program starting method and device, terminal and storage medium | |
| CN112667255B (en) | Updating method, updating device, electronic equipment and storage medium | |
| CN108829824B (en) | Resource processing method and device in internet operation activity | |
| CN105025482B (en) | Communication information processing method and equipment thereof | |
| CN111414190B (en) | Request processing method and device | |
| CN114764335A (en) | Method, device, terminal and storage medium for generating mirror image | |
| CN111324386B (en) | Method and device for starting split application program, electronic equipment and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200924 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200924 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Patentee before: Alibaba Group Holding Ltd. |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220415 Address after: Room 602, No. 618, Wai Road, Huangpu District, Shanghai 200010 Patentee after: Ant fortune (Shanghai) Financial Information Service Co.,Ltd. Address before: Ky1-9008 Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands, ky1-9008 Patentee before: Innovative advanced technology Co.,Ltd. |