CN101339508B - Java2 miniature edition application operation method and device - Google Patents
Java2 miniature edition application operation method and device Download PDFInfo
- Publication number
- CN101339508B CN101339508B CN2008101474550A CN200810147455A CN101339508B CN 101339508 B CN101339508 B CN 101339508B CN 2008101474550 A CN2008101474550 A CN 2008101474550A CN 200810147455 A CN200810147455 A CN 200810147455A CN 101339508 B CN101339508 B CN 101339508B
- Authority
- CN
- China
- Prior art keywords
- interface
- jsr
- j2me
- cldc
- platform
- 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
Landscapes
- Telephonic Communication Services (AREA)
Abstract
The invention discloses an operation method of J2ME application, including the following steps: the J2ME application is transplanted to an Android platform; the J2ME application is operated on the Android platform. The invention discloses a terminal which operates the J2ME application, comprising a transplanting module which is used for transplanting the J2ME application to the Android platform and an operating module which is used for operating the J2ME application which is transplanted by the transplanting module on the Android platform. The embodiment of the invention transplants the J2ME application to the Android platform and can effectively reduce occupancy of memory resource.
Description
Technical field
The present invention relates to communication technical field, particularly relate to operation method and device that a kind of Java 2 miniature editions are used.
Background technology
Along with the continuous enhancing of mobile hand-held device platform processes ability, nowadays cell phone apparatus can carry various application.And J2ME (Java 2 Micro Edition, Java 2 miniature editions) has obtained utilization widely as a kind of cross-platform computing technique based on Java in mobile phone, uses thereby produced numerous J2ME mobile phone.As long as in mobile phone, transplant J2ME JVM (Java VirtualMachine, Java Virtual Machine) and corresponding Runtime Library, JTWI (Java Technology for theWireless Industry for example, the Java technical manual of wireless domain) and MSA (Mobile ServiceArchitecture, mobile service architecture) etc., the J2ME mobile phone is used and be need not to transplant, and promptly may operate on the mobile phone of different hardware platforms framework.
Android is as the smart mobile phone middleware platform of the opening of OHA (Open Handset Alliance, open mobile phone alliance), and its operating system is based on Linux, and its application structure ApplicationFramework application interface is based on Java's.It is incompatible fully with the API of J2ME that but Android is API (ApplicationProgramming Interface, application programming interface), makes can not run on the Android platform based on the J2ME application of developing on the J2ME platform.
For making the Android mobile phone support existing J2ME to use, existing solution is: the JVM that transplants J2ME on the (SuSE) Linux OS of Android mobile phone and local handset middleware, simultaneously with required Runtime Library, for example JTWI and MSA etc. transplant accordingly, and all J2ME use and operate in based on the J2ME JVM on (SuSE) Linux OS and the local handset middleware.
The inventor is in realizing process of the present invention, and there are the following problems at least to find prior art:
In above-mentioned technical scheme, J2ME uses for operation, need move two different JVM simultaneously, and one is original JVM of Android (being Delvik JVM), and another is the JVM of J2ME.Thereby can take sizable memory source and Flash storage resources, in the comparatively nervous equipment of this memory source of mobile phone, this contradiction is particularly outstanding.In addition, Android uses and uses with J2ME is the discrete systems of two covers, switches to an other cover system from a cover system, needs comparatively complicated operations, and user experience is friendly inadequately.Because the different JVM of employing two covers, the J2ME application is used with Android and is difficult to carry out alternately.
Summary of the invention
Operation method and device that the embodiment of the invention provides a kind of J2ME to use have reduced when operation J2ME uses effectively to the taking of memory source, and have strengthened user's experience.
For achieving the above object, the embodiment of the invention proposes the operation method that a kind of J2ME uses on the one hand, comprising:
Call J2ME and use corresponding JSR; Judge whether described Android platform supports described J2ME to use the interface among the corresponding described JSR, if described Android platform supports described J2ME to use the interface among the corresponding described JSR, then call described Android platform, virtual machine Delvik VM and local platform Native Platform and realize described JSR;
Moving described J2ME at described Android platform uses.
On the other hand, the embodiment of the invention also proposes the terminal that a kind of J2ME of operation uses, and comprising:
Transplant module, be used to call J2ME and use corresponding JSR; Judge whether described Android platform supports described J2ME to use the interface among the corresponding described JSR, if described Android platform supports described J2ME to use the interface among the corresponding described JSR, then call described Android platform, Delvik virtual machine VM and local platform Native Platform and realize described JSR;
The operation module is used for moving the described J2ME application that described transplanting module is transplanted at described Android platform.
The technical scheme of the embodiment of the invention has the following advantages, be applied to the Android platform because transplant J2ME, can make full use of existing a large amount of J2ME uses, and need not to move two cover JVM, J2ME uses the Android platform JVM (being Delvik JVM) that places one's entire reliance upon and strengthen, taking memory source in the time of can effectively reducing operation J2ME application.
Description of drawings
In order to be illustrated more clearly in the embodiment of the invention or technical scheme of the prior art, to do to introduce simply to the accompanying drawing of required use in embodiment or the description of the Prior Art below, apparently, accompanying drawing in describing below only is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to these accompanying drawings.
Fig. 1 is the operation method process flow diagram that a kind of J2ME in the embodiment of the invention uses;
Fig. 2 is a kind of specific implementation process flow diagram that the operation J2ME in the embodiment of the invention uses;
Fig. 3 is a kind of terminal structure figure that moves the J2ME application in the embodiment of the invention;
Fig. 4 is a kind of terminal concrete structure figure that moves the J2ME application in the embodiment of the invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the invention, the technical scheme in the embodiment of the invention is clearly and completely described, obviously, described embodiment is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment among the present invention, those of ordinary skills belong to the scope of protection of the invention not making the every other embodiment that is obtained under the creative work prerequisite.
As shown in Figure 1, the operation method process flow diagram for a kind of J2ME in the embodiment of the invention uses may further comprise the steps:
The embodiment of the invention realizes J2ME graft layers Porting Layer based on the Delvik VM of Android platform self, J2ME is used be transplanted to the Android platform.According to the difference of device hardware ability, and upper layer application is to the requirement difference of J2ME API, and J2ME Porting Layer can realize the difference in functionality set of J2ME, for example JTWI, MSA, MSA subclass Subset etc.But the minimum function of J2ME PortingLayer realizes comprising the function of CLDC and MIDP (Mobile Information DeviceProfile, mobile information apparatus configuration file).Function to Android Application Framework strengthens, and on the basis of J2ME Porting Layer, realizes J2ME API, finally provides support for J2ME Application.Different according to the function set that J2ME Porting Layer realizes, the J2ME API that Application Framework provides also can be different, but the minimal set of its J2ME API should comprise the API of CLDC and MIDP at least.
With J2ME use be transplanted to the Android platform after, when Android platform operation J2ME uses, do not need JVM integral transplanting with J2ME to the Android platform, but make full use of the function of the Application Framework of the Delvik VM of Android platform and Android, on this basis, realize the business interface of J2ME, for the application of J2ME provides support.
As shown in Figure 2, a kind of specific implementation process flow diagram for the operation J2ME in the embodiment of the invention uses may further comprise the steps:
For supporting dissimilar application, J2ME has defined different JSR, each JSR standard one class J2ME business interface, JSR118 (MIDP) etc. for example.With gathering together of different JSR, some J2ME business interfaces commonly used set have been constituted, JTWI for example, MSA, and MSA Subset.Usually J2ME uses just be based on the corresponding business set of interfaces and makes up.Therefore, use, must realize corresponding JSR for supporting J2ME.
For supporting J2ME to use, need make amendment to the realization of JVM layer, to support the basic JSR:CLDC of J2ME JVM.
According to analysis, the interface among the CLDC more than 90% can carry out simple package based on the interface of Delvik and obtain, even wherein part interface Delvik directly supports.Remaining 10% interface can not be based on realizing on the Delvik that this part interface can directly be realized based on Native Platform.
Because the business interface of many JSR is overlapping with Android on function, therefore, the realization of this JSR interface can be based on the interface of Android, and remaining interface realizes being divided into the interface that can realize based on CLDC, and the interface that must realize based on Native Platform.
With J2ME use be transplanted to the Android platform after, when Android platform operation J2ME uses, do not need JVM integral transplanting with J2ME to the Android platform, but make full use of the function of the Application Framework of the Delvik VM of Android platform and Android, on this basis, realize the business interface of J2ME, for the application of J2ME provides support.
As shown in Figure 3, a kind of terminal structure figure that moves the J2ME application in the embodiment of the invention comprises:
The embodiment of the invention realizes J2ME graft layers Porting Layer based on the Delvik VM of Android platform self, J2ME is used be transplanted to the Android platform.According to the difference of device hardware ability, and upper layer application is to the requirement difference of J2ME API, and J2ME Porting Layer can realize the difference in functionality set of J2ME, for example JTWI, MSA, MSA subclass Subset etc.But the minimum function of J2ME PortingLayer realizes comprising the function of CLDC and MIDP (Mobile Information DeviceProfile, mobile information apparatus configuration file).Function to Android Application Framework strengthens, and on the basis of J2ME Porting Layer, realizes J2ME API, finally provides support for J2ME Application.Different according to the function set that J2ME Porting Layer realizes, the J2ME API that Application Framework provides also can be different, but the minimal set of its J2ME API should comprise the API of CLDC and MIDP at least.
With J2ME use be transplanted to the Android platform after, when Android platform operation J2ME uses, do not need JVM integral transplanting with J2ME to the Android platform, but make full use of the function of the Application Framework of the Delvik VM of Android platform and Android, on this basis, realize the business interface of J2ME, for the application of J2ME provides support.
As shown in Figure 4, a kind of terminal concrete structure figure that moves the J2ME application in the embodiment of the invention comprises:
The embodiment of the invention realizes J2ME graft layers Porting Layer based on the Delvik VM of Android platform self, J2ME is used be transplanted to the Android platform.According to the difference of device hardware ability, and upper layer application is to the requirement difference of J2ME API, and J2ME Porting Layer can realize the difference in functionality set of J2ME, for example JTWI, MSA, MSA subclass Subset etc.But the minimum function of J2ME PortingLayer realizes comprising the function of CLDC and MIDP (Mobile Information DeviceProfile, mobile information apparatus configuration file).Function to Android Application Framework strengthens, and on the basis of J2ME Porting Layer, realizes J2ME API, finally provides support for J2ME Application.Different according to the function set that J2ME Porting Layer realizes, the J2ME API that Application Framework provides also can be different, but the minimal set of its J2ME API should comprise the API of CLDC and MIDP at least.
With J2ME use be transplanted to the Android platform after, when Android platform operation J2ME uses, do not need JVM integral transplanting with J2ME to the Android platform, but make full use of the function of the Application Framework of the Delvik VM of Android platform and Android, on this basis, realize the business interface of J2ME, for the application of J2ME provides support.
Above-mentioned transplanting module 400 specifically comprises:
For supporting dissimilar application, J2ME has defined different JSR, each JSR standard one class J2ME business interface, JSR 118 (MIDP) etc. for example.With gathering together of different JSR, some J2ME business interfaces commonly used set have been constituted, JTWI for example, MSA, and MSA Subset.Usually J2ME uses just be based on the corresponding business set of interfaces and makes up.Therefore, use, must realize corresponding JSR for supporting J2ME.Because the business interface of many JSR is overlapping with Android on function, therefore, the realization of this JSR interface can be based on the interface of Android, and remaining interface realizes being divided into the interface that can realize based on CLDC, and the interface that must realize based on Native Platform.
Second judges submodule 402, does not support J2ME to use the interface of corresponding JSR if be used for the first judgement submodule, 401 judgement Android platforms, judges that can the interface among the JSR be converted into the interface of Android platform support.
The 3rd judges submodule 403, judges that the interface of submodule 402 judgement JSR can not be converted into the interface that the Android platform is supported, judges whether CLDC supports the interface among the JSR if be used for second.
First calls submodule 404, judges that submodule 403 judgement CLDC support the interface of JSR, call CLDC and Native Platform and realize JSR if be used for the 3rd.
For supporting J2ME to use, need make amendment to the realization of JVM layer, to support the basic JSR:CLDC of J2ME JVM.According to analysis, the interface among the CLDC more than 90% can carry out simple package based on the interface of Delvik and obtain, even wherein part interface Delvik directly supports.Remaining 10% interface can not be based on realizing on the Delvik that this part interface can directly be realized based on Native Platform.
Second calls submodule 405, judges that submodule 401 judgement Android platforms support J2ME use the interface of corresponding JSR, call Android platform, DelvikVM and NativePlatform and realize JSR if be used for first.
The first conversion submodule 406 judges that the interface of submodule 403 judgement JSR can be converted into the interface that the Android platform is supported, becomes the interface conversion among the JSR interface of Android platform support if be used for the described the 3rd.
The second conversion submodule 407 judges that submodule 403 judgement CLDC do not support the interface of JSR, become the interface conversion among the JSR interface of Native Platform support if be used for the 3rd.
The 4th judges submodule 408, is used for judging whether Delvik VM supports the interface of CLDC.
The 5th judges submodule 409, judges that submodule 408 judgement Delvik VM do not support the interface of CLDC, judge that can the interface among the CLDC be converted into the interface that Delvik VM supports if be used for the 4th.
The 3rd conversion submodule 410 judges that the interface of submodule 409 judgement CLDC can be converted into the interface that Delvik VM supports, becomes the interface conversion among the CLDC interface of Delvik VM support if be used for the 5th.
The 3rd calls submodule 411, judges that submodule 408 judgement Delvik VM support the interface of CLDC, call Delvik VM and Native Platform and realize CLDC if be used for the 4th.
The 4th conversion submodule 412 judges that submodule 409 judgement CLDC do not support the interface of JSR, become the interface conversion among the JSR interface of described Native Platform support if be used for the 5th.
The technical scheme of the embodiment of the invention has the following advantages, and is applied to the Android platform because transplant J2ME, can make full use of existing a large amount of J2ME and use; Need not to move two cover JVM, J2ME uses the Android platform JVM (being Delvik JVM) that places one's entire reliance upon and strengthen, and can effectively reduce taking of memory source; In UI (User Interface, user interface) design, J2ME uses and can be fully integratible among the UI of Android, need not to switch, and has strengthened user's experience; For J2ME application and providing alternately of Android application may; The JVM of J2ME and the realization of JSR make full use of Delvik and Android, have reduced the redundancy of code, have reduced the requirement of storage space.
Through the above description of the embodiments, those skilled in the art can be well understood to the present invention and can realize by the mode that software adds essential general hardware platform, can certainly pass through hardware, but the former is better embodiment under a lot of situation.Based on such understanding, the part that technical scheme of the present invention contributes to prior art in essence in other words can embody with the form of software product, this computer software product is stored in the storage medium, comprise that some instructions are with so that a station terminal equipment (can be mobile phone, personal computer, server, the perhaps network equipment etc.) carry out the described method of each embodiment of the present invention.
The above only is a preferred implementation of the present invention; should be pointed out that for those skilled in the art, under the prerequisite that does not break away from the principle of the invention; can also make some improvements and modifications, these improvements and modifications also should be looked protection scope of the present invention.
Claims (15)
1. the operation method that Java 2 miniature edition J2ME use is characterized in that, comprising:
Call J2ME and use corresponding JSR; Judge whether the Android platform supports described J2ME to use the interface among the corresponding described JSR, if described Android platform supports described J2ME to use the interface among the corresponding described JSR, then call described Android platform, virtual machine Delvik VM and local platform Native Platform and realize described JSR;
Moving described J2ME at described Android platform uses.
2. the operation method used of J2ME according to claim 1, it is characterized in that, described method also comprises: if described Android platform is not supported the interface among the described JSR, judge that then can the interface among the described JSR be converted into the interface that described Android platform is supported;
If the interface among the described JSR can not be converted into the interface that the Android platform is supported, judge then whether constrained devices configuration CLDC supports the interface among the described JSR, if described CLDC supports the interface among the described JSR, then call described CLDC and described Native Platform realizes described JSR.
3. the operation method of using as J2ME as described in the claim 2 is characterized in that, can the interface among the described judgement JSR be converted into after the interface that the Android platform supports, also comprises:
If the interface among the described JSR can be converted into the interface that described Android platform is supported, the interface that then interface conversion among the described JSR is become described Android platform to support calls described Android platform and described Native Platform realizes described JSR.
4. the operation method of using as J2ME as described in the claim 2 is characterized in that, whether the described CLDC of judgement supports also comprises after the interface among the JSR:
If described CLDC does not support the interface among the described JSR, the interface that then interface conversion among the described JSR is become described Native Platform to support calls described Native Platform and realizes described JSR.
5. the operation method of using as J2ME as described in the claim 2, it is characterized in that, described calling after the CLDC, also comprise: judge whether described Delvik VM supports the interface among the described CLDC, if described Delvik VM does not support the interface among the described CLDC, judge that then can the interface among the described CLDC be converted into the interface that described Delvik VM supports, if the interface among the described CLDC can be converted into the interface that described Delvik VM supports, the interface that then interface conversion among the described CLDC is become described Delvik VM to support calls described Delvik VM and described Native Platform realizes described CLDC.
6. the operation method of using as J2ME as described in the claim 5 is characterized in that, whether the described Delvik of judgement VM supports also comprises after the interface among the CLDC:
If described Delvik VM supports the interface among the described CLDC, then call described Delvik VM and described Native Platform realizes described CLDC.
7. the operation method of using as J2ME as described in the claim 5 is characterized in that, can the interface among the described judgement CLDC be converted into after the interface that Delvik VM supports, also comprises:
If the interface among the described CLDC can not be converted into the interface that described Delvik VM supports, the interface that then interface conversion among the described CLDC is become described Native Platform to support calls described Native Platform and realizes described CLDC.
8. one kind is moved the terminal that J2ME uses, and it is characterized in that, comprising:
Transplant module, be used to call J2ME and use corresponding JSR; Judge whether the Android platform supports described J2ME to use the interface among the corresponding described JSR, if described Android platform supports described J2ME to use the interface among the corresponding described JSR, then call described Android platform, Delvik virtual machine VM and local platform Native Platform and realize described JSR;
The operation module is used for moving the described J2ME application that described transplanting module is transplanted at described Android platform.
9. as described in claim 8, move the terminal that J2ME uses, it is characterized in that described transplanting module comprises:
First judges submodule, is used for judging whether the Android platform supports J2ME to use the interface of corresponding JSR;
Second calls submodule, judge that submodule judges that described Android platform supports described J2ME to use the interface of corresponding JSR if be used for described first, call described Android platform, described Delvik virtual machine VM and described Native Platform and realize described JSR.
10. as described in claim 9, move the terminal that J2ME uses, it is characterized in that described transplanting module also comprises:
Second judges submodule, does not support described J2ME to use the interface of corresponding JSR if be used for described Android platform, judges that can the interface among the described JSR be converted into the interface that described Android platform is supported;
The 3rd judges submodule, can not be converted into the interface that the Android platform is supported if be used for the interface of described JSR, judges then whether CLDC supports the interface among the described JSR;
First calls submodule, if be used for the interface that described CLDC supports described JSR, then calls described CLDC and Native Platform realizes described JSR.
11. as described in claim 10, move the terminal that J2ME uses, it is characterized in that described transplanting module also comprises:
The first conversion submodule, judge that the interface of described JSR can be converted into the interface that the Android platform is supported if be used for the described second judgement submodule, with the interface that the interface conversion among the described JSR becomes described Android platform to support, call described Android platform and described Native Platform realizes described JSR.
12. as described in claim 10, move the terminal that J2ME uses, it is characterized in that described transplanting module also comprises:
The second conversion submodule, judge that described CLDC does not support the interface of described JSR if be used for described the 3rd judgement submodule, the interface that then interface conversion among the described JSR is become described Native Platform to support calls described Native Platform and realizes described JSR.
13. as described in claim 10, move the terminal that J2ME uses, it is characterized in that described transplanting module also comprises:
The 4th judges submodule, is used for judging whether described Delvik VM supports the interface of described CLDC;
The 5th judges submodule, judges that described Delvik VM does not support the interface of described CLDC if be used for described the 4th judgement submodule, judges that then can the interface among the described CLDC be converted into the interface that described Delvik VM supports;
The 3rd conversion submodule, judge that the interface of described CLDC can be converted into the interface that described Delvik VM supports if be used for described the 5th judgement submodule, the interface that then interface conversion among the described CLDC is become described Delvik VM to support calls described Delvik VM and described Native Platform realizes described CLDC.
14. as described in claim 13, move the terminal that J2ME uses, it is characterized in that described transplanting module also comprises:
The 3rd calls submodule, judges that submodule judges that described Delvik VM supports the interface of described CLDC if be used for the described the 4th, calls described Delvik VM and described Native Platform realizes described CLDC.
15. as described in claim 13, move the terminal that J2ME uses, it is characterized in that described transplanting module also comprises:
The 4th conversion submodule, judge that described CLDC does not support the interface of described JSR if be used for described the 3rd judgement submodule, interface with the interface conversion among the described JSR becomes described Native Platform to support calls described Native Platform and realizes described JSR.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101474550A CN101339508B (en) | 2008-08-18 | 2008-08-18 | Java2 miniature edition application operation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101474550A CN101339508B (en) | 2008-08-18 | 2008-08-18 | Java2 miniature edition application operation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101339508A CN101339508A (en) | 2009-01-07 |
| CN101339508B true CN101339508B (en) | 2011-11-02 |
Family
ID=40213584
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008101474550A Active CN101339508B (en) | 2008-08-18 | 2008-08-18 | Java2 miniature edition application operation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101339508B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101895441B (en) * | 2010-07-21 | 2014-03-12 | 中兴通讯股份有限公司 | Service debugging device and method for JAVA application of terminal of Internet of things |
| CN101957793B (en) * | 2010-09-03 | 2013-02-13 | 中国科学院软件研究所 | Android and android derivative system-oriented method for playing back software operation record |
| CN102419708B (en) * | 2011-12-19 | 2014-04-09 | 广州杰赛科技股份有限公司 | Method and device for operating Java 2 micro edition (J2ME) games |
| CN103473096A (en) * | 2013-09-10 | 2013-12-25 | 浙江大学城市学院 | Method and system for loading java class on virtual machine of android system |
| CN103870316B (en) * | 2014-04-11 | 2016-09-07 | 烽火通信科技股份有限公司 | A kind of JAVA virtual machine realization method in intelligent operating system |
| CN105224330B (en) * | 2015-10-13 | 2018-12-04 | 东信和平科技股份有限公司 | A method of fast implementing android system HCE service |
-
2008
- 2008-08-18 CN CN2008101474550A patent/CN101339508B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN101339508A (en) | 2009-01-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101339508B (en) | Java2 miniature edition application operation method and device | |
| US9204239B1 (en) | Segmented customization package within distributed server architecture | |
| CA2600503C (en) | Method and system for executing a container-managed application on a processing device | |
| KR100700171B1 (en) | Sub display expression device of the mobile communication terminal and controlling method therefore | |
| CN102769937B (en) | A kind of multi-standby terminal of Android system and terminal realize the method treated more | |
| CN102054173B (en) | Smart card and method for integrating multiple telecom applications on same | |
| CN105580392A (en) | Seamless call transitions | |
| CN101778169B (en) | Dynamic display method of application program interface and device | |
| CN103488466A (en) | Method and device for executing application program | |
| CN102799444B (en) | The method of cross-platform packing program and device | |
| CN111797173B (en) | Alliance chain sharing system, method and device, electronic equipment and storage medium | |
| CN100481852C (en) | Terminal for mobile communications | |
| US8924987B2 (en) | Flat or extended architecture using an integrated application and operating system component for computing systems and environments | |
| CN113296742A (en) | APP data processing method and device and mobile terminal | |
| US8700018B2 (en) | Method and apparatus for adapting a telephony component to operate in a different telephony | |
| CN101932145A (en) | Device and method for managing software versions in wireless communication system | |
| CN106792206A (en) | A kind of TV menu adaptive updates method and system | |
| CN114944971B (en) | Method and device for deploying network by using Kubernetes, electronic equipment and storage medium | |
| CN111726453A (en) | System switching method, device and terminal | |
| KR100627819B1 (en) | Method for Controlling Application by Using Functions of WAP Browser | |
| KR101196838B1 (en) | Common Communication Manager Corded in Source Code of Android Layer Architecture | |
| CN114816351A (en) | Method for supporting different ecological systems by mobile phone | |
| CN112948021B (en) | Android mobile terminal development method for configuratively accessing SDK of the same type | |
| CN103577177A (en) | Method and equipment for invoking graphics libraries | |
| US8572561B1 (en) | Multiple java ME MIDlet execution in single-instance CLDC JVM |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20171113 Address after: Metro Songshan Lake high tech Industrial Development Zone, Guangdong Province, Dongguan City Road 523808 No. 2 South Factory (1) project B2 -5 production workshop Patentee after: HUAWEI terminal (Dongguan) Co., Ltd. Address before: 518129 Longgang District, Guangdong, Bantian HUAWEI base B District, building 2, building No. Patentee before: Huawei Device Co., Ltd. |
|
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 523808 Southern Factory Building (Phase I) Project B2 Production Plant-5, New Town Avenue, Songshan Lake High-tech Industrial Development Zone, Dongguan City, Guangdong Province Patentee after: Huawei Device Co., Ltd. Address before: 523808 Southern Factory Building (Phase I) Project B2 Production Plant-5, New Town Avenue, Songshan Lake High-tech Industrial Development Zone, Dongguan City, Guangdong Province Patentee before: HUAWEI terminal (Dongguan) Co., Ltd. |