WO2012041046A1 - 应用商店系统及使用该应用商店系统进行开发的方法 - Google Patents

应用商店系统及使用该应用商店系统进行开发的方法 Download PDF

Info

Publication number
WO2012041046A1
WO2012041046A1 PCT/CN2011/072058 CN2011072058W WO2012041046A1 WO 2012041046 A1 WO2012041046 A1 WO 2012041046A1 CN 2011072058 W CN2011072058 W CN 2011072058W WO 2012041046 A1 WO2012041046 A1 WO 2012041046A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
application
capability
module
telecommunications
Prior art date
Application number
PCT/CN2011/072058
Other languages
English (en)
French (fr)
Inventor
巫妍
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to JP2013530532A priority Critical patent/JP5751561B2/ja
Priority to EP11827942.1A priority patent/EP2624517A4/en
Priority to US13/876,503 priority patent/US9173050B2/en
Publication of WO2012041046A1 publication Critical patent/WO2012041046A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/31Programming languages or programming paradigms
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/18Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals

Definitions

  • the present invention relates to the field of communications, and in particular to an application store system and a method of developing using the same.
  • 3G the 3 Rd Generation
  • Apple began offering iPhone applications through an application delivery system (called a mobile app store) in 2008, and achieved nearly 1 billion downloads in the short term.
  • the use of this mobile app store has created a large number of independent developers of applications.
  • Major operators, mobile phone manufacturers and Internet vendors will also launch their own online app stores on the agenda, or they will have to go out to the online app store.
  • the main functional entities are the app store online store and the developer community.
  • the two functional entities can be combined together, as shown in Figure 1, this common application store does not have telecommunications Capability docking capabilities, applications developed by developers cannot use telecommunications capabilities.
  • the main functional modules of the existing application store online store include: portal, authentication module, application distribution module, supply sales module, business support module and operation support module.
  • the portal mainly provides access to the WEB portal, WAP portal, mobile client or PC client. Through this portal, the mobile terminal user can easily search and download the application.
  • the authentication module provides authentication of the user and authentication of the application.
  • the application distribution module provides functions for various application distribution channels, such as downloading to a computer, WAP PUSH to mobile phone, SMS sending address, or direct download and installation of the client, and other functions related to application distribution.
  • the Supply Sales module provides management of applications sold in the App Store, including: store and shelf management, application downline management, and recommended ranking management. Key features of the existing developer community include: app uploads, app management features, forum features, developer wikis. It can be seen that in the current system, only the common application is supported, and the execution of the service with the telecommunications capability cannot be supported, so that the application for executing the service cannot implement the telecom capability.
  • a telecommunications capability resource functional entity comprising: a service execution module, configured to invoke a telecommunications capability in an capability open gateway to perform telecommunications capability through an interface
  • the service is used to be embedded in the application.
  • the telecommunication capability resource functional entity further comprises: a service development module, configured to provide a development environment of the telecommunication capable service.
  • the telecommunication capability resource functional entity The method further includes: a service test module, configured to provide a telecommunication capability simulation running environment for testing the service, and returning a simulation execution result when the service is executed in the environment.
  • the telecommunication capability resource functional entity further includes: an authorization module, configured to be authorized business Using the telecommunication capability invoked by the service; the first binding module is configured to accept the operation of binding the service with the telecommunication capability invoked by the service when the authorization module completes the authorization; the service execution module is further configured to determine Whether there is a binding relationship between the currently executed service and the telecommunication capability it uses, and if so, continuing to perform the service, if not, ending the process.
  • an application store system including: The community function entity is configured to accept the upload of the application and review the uploaded application; the application store online store function entity is set to be used by the end user to download the application audited by the developer community module; the telecom capability resource functional entity, including: An execution module, configured to invoke a telecommunications capability in the capability open gateway through the interface to perform a telecommunications capable service, where the service is used to be embedded in the application; and the telecommunications capability resource functional entity is embedded in the application uploaded in the developer community functional entity
  • the telecommunications capability resource functional entity further comprises: a service development module, configured to provide a development environment with telecommunications capable services.
  • the telecommunication capability resource functional entity further comprises: a service test module, configured to provide a telecommunication capability simulation running environment for testing the service, and returning a simulation execution result when the service is executed in the environment.
  • the telecommunication capability resource function entity further includes: an authorization module, configured to authorize the service to use the telecommunication capability invoked by the service; and the first binding module, configured to accept the service and the service when the authorization module completes the authorization The invoked telecommunication capability performs the binding operation; the service execution module is further configured to determine whether there is a binding relationship between the currently executed service and the telecommunication capability used thereby, and if so, continue to perform the service; otherwise, the process ends.
  • the developer community function entity comprises: a second binding module, configured to accept an operation of binding an application with a service embedded in the application; a binding validation module, configured to notify the service execution module of the bound information
  • the service execution module is further configured to determine whether there is a binding relationship between the application currently calling the service and the service invoked by the service, and if so, continue to execute the service, and if not, end the processing.
  • the service execution module is further configured to: after receiving the bound information, determine whether the bound application is authorized to use the bound service, and if yes, return the binding effective information to the binding validation module.
  • the application uploaded in the developer community functional entity invokes the service through a calling interface corresponding to the business embedded in the application.
  • a method for developing the above application store system including: embedding a telecommunications capable service executed in a service execution module in an application, wherein the embedded service in the application passes The interface invokes the ability to open telecommunications capabilities in the gateway.
  • the method further comprises: developing a telecommunications capable service in a development environment of the telecommunications capable service provided by the service development module.
  • the method further includes: performing a service in the telecommunication capability simulation running environment provided for the test service provided by the service test module, and obtaining a simulation execution result when the service is executed to complete the service Test.
  • the method before the embedding the service in the application, the method further includes: obtaining, by the authorization module, the authorization of the telecommunication capability invoked by the service, using the service; and the service and the service by using the first binding module
  • the called telecommunications capability is bound so that the service execution module can authenticate the validity of the telecommunications capability before performing the service.
  • the method further includes: binding, in the developer community functional entity, the service and the application embedded by the service by using the second binding module, and the developer community function entity notifying the binding relationship to the binding relationship The business execution module, so that the business execution module performs authentication of the legality of the calling relationship between the application and the service before executing the business.
  • the method further includes: executing a service embedded in the application by calling a service test module, obtaining a simulation execution result to implement testing of the application; or, by invoking a service execution module to execute a service embedded in the application, obtaining an execution result to implement the application Test.
  • the telecom capability in the capability opening gateway is invoked through the interface to execute the telecom-capable service, and the service is embedded in the application, thereby solving the problem that the telecommunications capable application cannot be provided, and the telecom capability is realized.
  • the development of the application of capabilities thereby protecting the interests of operators and improving the survivability of operators in the future.
  • FIG. 1 is a structural block diagram of an application store system according to the prior art
  • FIG. 2 is a structural block diagram of a telecommunication capability resource functional entity according to an embodiment of the present invention
  • FIG. 3 is a telecommunication capability resource according to an embodiment of the present invention.
  • FIG. 4 is a block diagram of a preferred structure of a telecommunications capability resource functional entity according to an embodiment of the present invention.
  • FIG. 5 is a block diagram 3 of a preferred structure of a telecommunications capability resource functional entity according to an embodiment of the present invention
  • FIG. 7 is a block diagram showing a preferred structure of an application store system according to an embodiment of the present invention
  • FIG. 8 is a block diagram of an application service test/execution module according to an embodiment of the present invention
  • 9 is a structural block diagram of a system for implementing a mobile phone application store according to Embodiment 1 of the present invention
  • FIG. 10 is a flowchart showing a process for developing a general application using an application store system according to Embodiment 2 of the present invention
  • FIG. 12 is a flowchart of a process for uploading a general application using the application store system according to Embodiment 3 of the present invention
  • FIG. 13 is a process diagram for developing an application having a telecommunication capability using an application store system according to Embodiment 3 of the present invention
  • the telecommunications capability resource functional entity 22 includes: a service execution module 24 configured to invoke a telecommunications capability in an capability open gateway through an interface to perform the telecommunications capability.
  • the business where the business is used to embed in the application.
  • the service execution time service execution module 26 performs the service by using the telecommunications capability in the interface to enable the capability to open the gateway, thereby providing a service with telecommunications capabilities.
  • FIG. 3 is a block diagram of a preferred structure of a telecommunications capability resource functional entity in an embodiment of the present invention.
  • the functional entity 22 may further include: a service development module 32, configured to provide a telecommunications capable service development environment.
  • the business development module 24 provides a development environment for telecommunications-capable services, and developers can implement telecommunications-enabled services in the telecommunications capability resource functional entity 22.
  • the telecommunication capability resource function entity 22 can also implement a test function for the developed service in addition to the development function
  • FIG. 4 is a telecommunication capability resource function entity according to an embodiment of the present invention.
  • the telecommunications capability resource functional entity 22 as shown in FIG.
  • a service testing module 42 configured to provide telecommunications capabilities for testing services Simulate the runtime environment and return the results of the simulation execution when the business is executed in the environment.
  • This embodiment enhances the functions of the telecommunications capability resource functional entity, provides functions such as development, testing, and operation, and improves the practicability of the functional entity.
  • the telecommunication capability resource functional entity can further provide the function of authorizing the application developed by the developer to use the telecommunication capability, and the service can be used only when the system authorizes the service to have the permission to use the service.
  • the telecommunications capability and can also be authenticated by binding the service with the telecommunications capabilities it uses.
  • the telecommunications capability resource function entity 22 may further include: an authorization module 52, configured to be authorized.
  • a service uses the telecommunication capability invoked by the service;
  • the first binding module 54 is configured to accept, when the authorization module 52 completes the authorization, an operation of binding the service with the telecommunication capability invoked by the service;
  • the module 24 is further configured to determine whether there is a binding relationship between the currently executed service and the telecommunication capability it uses, and if so, continue to perform the service, otherwise, the process ends, preferably, the corresponding error message can also be returned.
  • FIG. 6 is a structural block diagram of an application store system according to an embodiment of the present invention.
  • the application store system includes: a developer community function entity 62. , set to accept the upload of the application, and review the uploaded application; the application store online store function entity 64, set for the end user to download the application audited by the developer community module; the above telecommunications capability resource functional entity 22, developer
  • the telecommunications capable service executed by the telecommunication capability resource function entity 22 is embedded in the application uploaded in the community function entity 62.
  • FIG. 7 is a block diagram showing a preferred structure of the application store system according to the embodiment of the present invention, as shown in FIG.
  • the developer community function entity 62 can include: a second binding module 72, configured to accept an operation of binding an application with a service embedded in the application; a binding validation module 74, configured to bind the information
  • the service execution module 24 is further configured to determine whether there is a binding relationship between the application currently calling the service and the service invoked by the service, and if yes, continue to perform the service; otherwise, the process ends, preferably, may also return The corresponding error message.
  • the service execution module 24 can also verify the binding relationship between the application and the service, and if the service obtains the authorization to use the telecommunications capability, the binding is allowed. Specifically, After receiving the bound information, the service execution module 24 determines that the binding should be Whether the service of the binding is authorized or not is used, and if so, the information of the binding validity is returned to the binding validation module 74. This embodiment prevents binding of an application to an unlicensed service, reducing the operational failure of the application.
  • the above application may invoke the service by using a call interface corresponding to the service embedded in the application, and the service returns a service execution return result to the application
  • the interface may be an internal custom interface, and the form is not limited, and may be SOAP can also be REST, in order to facilitate the application of the call as a criterion, the specific implementation is relatively simple, and will not be described here. It should be noted that each module in the above system is used to implement different functions, and developers can call different modules to implement service/application development.
  • the interaction between the binding validation module 74 and the second binding module 72 and the service execution module 24 may have an automatic signal (specifically, the binding information and the binding effective information), which is only used to implement The function is fed back to the developer, and which module is executed by the user is completely determined by the user. That is to say, the logic execution order of these modules is completely determined by the order of the developer, and the order of the developer may be specific. It is necessary to change, and it is not even possible to use all the modules. Therefore, in the drawings, the relationship between the modules is not indicated by a line.
  • the telecommunications capability resource functional entity 22 provided by the above embodiments is intended to provide functions such as execution/development/testing of telecommunications capable services, the telecommunications capability resource functional entity 22 and the developer community functional entity 62 and the application store online store functional entity
  • the 64 are integrated to form an application store system that enables the development, management and sale of telecom-capable applications.
  • the embodiment further provides a method for developing using the above application store system, the method comprising: embedding a telecommunications capable service executed in a service execution module in an application, where the embedded service in the application passes The interface invokes the ability to open telecommunications capabilities in the gateway.
  • the telecommunications-capable service Before embedding the business in the application, the telecommunications-capable service can be developed in the development environment of the telecommunications-capable service provided by the business development module. In this way, developers can design their own business to develop more personalized applications.
  • the method may further include: executing, in the telecommunication capability simulation running environment for testing the service provided by the service testing module, when performing the service Simulate the execution results to complete the testing of the business. This method enhances the functions of the development system, provides functions such as development, testing, and operation, and improves the practicability of the system.
  • the service embedded in the application may be executed by calling the service testing module 42 to obtain the simulation execution result to implement testing of the application; or, by calling a service execution Module 24 executes the services embedded in the application, obtaining execution results to enable testing of the applications.
  • FIG. 8 is a schematic diagram of testing an application by an application service test/execution module according to an embodiment of the present invention. As shown in FIG. 8, the service is tested by using the service test module 42, or the service is executed by the service execution module 24.
  • the method may further include: obtaining, by the ⁇ authorized module, the authorization of the telecommunication capability invoked by the service using the service; binding the service and the telecommunication capability invoked by the service, so that the service is executed.
  • the module performs authentication of the legality of the use of telecommunications capabilities before performing the service.
  • the method further includes: binding the service and the application embedded in the service in the developer community functional entity, and the developer community function entity notifying the binding execution relationship to the service execution module, so as to The execution module authenticates the legality of the calling relationship between the application and the service before executing the service.
  • the embodiment 1-3 described below combines the technical solutions of the above-described plurality of preferred embodiments.
  • Embodiment 1 This embodiment provides a system for implementing a mobile application store, and a method for application development on the system.
  • 9 is a structural block diagram of a system for implementing a mobile phone application store according to Embodiment 1 of the present invention. As shown in FIG.
  • the system includes the following functional entities: an application store online store, which provides a WEB accessed by a mobile terminal user.
  • Portals, WAP portals, and mobile clients allow users to query applications, purchase apps, and download apps.
  • carrier administrators also manage the mobile app's shelf-up process in the store;
  • the developer community the functional entity provides developers with the ability to upload applications, manage applications, test applications, and forums.
  • the operator administrator can also publish SDKs, provide technical support, and review and test applications. Management; Telecommunications Capability Resource Functional Entity, which provides developers with telecommunications-capable business development environments, business test environments, and business execution environments, provides access to open gateway interfaces, and provides developers with business development wikis. .
  • the telecom capability resource functional entity Using the business development environment provided by the functional entity, developers can use the business development tools provided by the system to develop telecom-capable services and embed them into their own applications; the telecom capability resource functional entity also provides an access capability open gateway. Interfaces, which are running in a business execution environment, can use this interface to invoke telecommunications capabilities. In addition, it provides functions such as capability management, service management, service authentication, and application authentication. Developers can learn how to develop a business in a business development wiki and conduct business development in a business development environment. When the business development is complete, the developer can deploy the business to the business test environment for testing. If a service needs to use one or more telecommunications capabilities, it must also purchase the corresponding telecommunications capabilities or atomic services in the functional entity.
  • Step 1 The developer develops the service in the business development environment provided by the telecom capability resource function entity.
  • the resource function entity test service in the business test environment.
  • Step 2 The developer develops the application, invokes the business in the business test environment, and tests the application.
  • Step 3 The developer purchases the capability in the telecom capability resource functional entity, binds the purchased capability and the service, and applies for the service to go online.
  • Step 4 After the auditing of the telecommunications capability resource function entity administrator, the service is deployed in the service execution environment to perform online operations.
  • the business execution environment can invoke capability resources, which include capability open gateways and Internet capabilities.
  • the interface protocol for the service invocation capability resources in the business execution environment can be SOAP or REST.
  • Step 5 The developer fills in the application information in the developer community functional entity, uploads the application package, and applies for application and business binding.
  • Step 6. The developer community administrator reviews the application. After the audit is passed, the application status is to be put on the shelf.
  • Step S1001 Developers develop applications in the mobile operating system development environment and generate application packages (development environments, development tools, package formats and suffixes for different mobile applications).
  • the development environment is provided by the development tools of the mobile operating system. For example, if the developer needs to develop an application for the android operating system, then the android mobile application needs to be used. If the developer needs to develop an iPhone mobile application, then the development tool xtool of Apple needs to be used in the development environment of the MAC operating system.
  • Step S1001 Developers develop applications in the mobile operating system development environment and generate application packages (development environments, development tools, package formats and suffixes for different mobile applications).
  • the development environment is provided by the development tools of the mobile operating system. For example, if the developer needs to develop an application for the android operating system, then the android mobile application needs to be used. If the developer needs to develop an iPhone mobile application, then the development tool xtool of Apple needs to be used in the development environment of the MAC operating system.
  • step S1002 the developer fills in the application information in the developer community and uploads the package, and the developer community administrator reviews and tests the application, and the application is to be put on the shelf after the verification test is completed.
  • step S1003 the application store online store administrator performs the shelf-up operation on the application that is put on the shelf, and the application is successfully put on the shelf, and starts to sell to the terminal user.
  • FIG. 11 is a flowchart of a process for uploading a normal application according to Embodiment 2 of the present invention. As shown in FIG. 11, the process of uploading a common application in step 1002 includes the following steps: Step S 1101, the developer fills in the application information and uploads the application package in the developer community.
  • step S1102 the developer community administrator reviews the application information and tests the application package.
  • step S 1103 after the developer community administrator reviews and tests, the application status is to be put on the shelf.
  • Step 4 S 1104 the application store administrator can query the application to be put on the shelf.
  • App Store Online Store Administrators can take on shelves for processing.
  • Step S 1105 the application takes effect after being put on the shelf, and can be inquired and purchased by the terminal user in the online shop portal or the online store client.
  • the primary operation that developers do in the app store system is to upload the app package. The uploaded mobile app is available for end-user sales through a series of online store review and testing processes.
  • a server For a normal application, if a server is required to serve it, the developer can interact with its own server using the private interface inside the application. For example, suppose the developer needs to develop a mobile app A, A is the mobile app client of web site B. Application A can obtain the updated news and buddy list of Site B when it is connected to the Internet. When the end user uses the application A to browse a certain news, he can choose to send a text message or a multimedia message to the buddy in the station. According to the development principle of the common application, the mobile application A can be understood as a client of the web site B, and the web site B can be understood as a server of the mobile application A. Mobile App A can get updated news.
  • Embodiment 1 can enable small and medium-sized independent developers to develop applications with telecommunications capabilities provided by operators.
  • the following describes the development and uploading of the telecommunications-capable application/service by the developer using the system of Embodiment 1 through the embodiment 3, until the entire process of application sales.
  • Embodiment 3 FIG. 12 is a flowchart showing a process of developing an application having telecommunications capabilities using an application store system according to Embodiment 3 of the present invention. As shown in FIG. 12, a developer develops a service having telecommunications capabilities and a service using telecommunications capabilities.
  • Step S1201 The developer develops a telecommunications-capable service by using a service development environment provided by the telecommunications capability resource function entity, and performs testing in the service online test environment.
  • Step S1202 the developer develops an application that uses an interface to invoke a service with telecommunications capabilities.
  • the application can invoke the services deployed in the business test environment for testing.
  • step S1203 the developer purchases the capability in the telecommunications capability resource functional entity, and applies for the service to go online. After the administrator approves and tests, the service is brought online and deployed into the business execution environment. When the business is online and the ability to purchase is successful, developers can apply for binding of business and telecommunications capabilities.
  • step S1204 the developer changes the application 4 ⁇ to invoke the business in the formal business execution environment to perform the test.
  • step S1205 the developer uploads the developed application in the developer community and binds the application to the already deployed service, and the administrator reviews and tests the application and the binding relationship between the application and the service. Only when an application is bound to a service, the application has permission to use the service.
  • Step S 1206 after the developer community administrator reviews and tests the application, the application store online store administrator can query all the applications that are in the state to be put on the shelf, and the administrator can sell the application in the application store online store.
  • the service having the telecommunication capability refers to a service flow composed of one or more telecommunication capabilities.
  • a simple service can be a service that sends a text message to a mobile phone.
  • the development process of the business is as follows: 1. The developer downloads the business development tool and learns the use of the development tool; 2. The developer develops the business using the development tool, and designs the calling interface of the business as the entry parameter for the mobile phone number and the short message content, and returns the parameter.
  • the result of the success or failure of sending is 3;
  • the business process of development is: The user reads the mobile phone number and the SMS content, sends the short message using the atomic service of the short message capability provided in the development tool, reads the atomic service and returns the result and The result is returned to the business caller as a business call return parameter.
  • a combined service can be a slightly more complex service consisting of one or more telecommunications capabilities. For example, the service may be to determine whether a mobile terminal is in a geographical area, and if so, send an advertisement message to the mobile phone.
  • the development process of the business is as follows: 1. The developer downloads the business development tool and learns the use of the development tool; 2.
  • the developer designs the call interface of the service as the user mobile phone number, the main location of the advertisement store, the advertisement message content, and the return parameter is The result of the successful sending of the short message, the user is not in the area or the sending of the short message fails; 3, the business development process is: the business reads the mobile phone number of the user and the main geographic location of the advertising store, the business mobile phone number and the main geographic location of the advertising store call the positioning month.
  • the atomic monthly service the atomic monthly service returns the relative distance, the service is judged according to the relative distance, if the relative distance is less than 1 km, an advertising message is sent to the mobile phone user, if the relative distance is greater than 1 km, then nothing is done. Operation, the business returns the result of the business operation back to the business caller.
  • the above business development tools are tools provided by the business development environment to developers, and the methods for calling telecommunications capability resources are encapsulated. For developers, what they need to do is to use a small amount of script control logic to provide atomic services in the tools. Assemble. But from the bottom up, the service call telecommunications capability is ultimately still achieved by calling the interface of the capability open gateway. For operators, providing business development tools reduces the developer's development threshold and creates better conditions for developers to develop their business quickly and easily. The specific functions and implementations of the business development tools in the above business development environment are not within the scope of the present invention.
  • the business development tool is aimed at developers and SPs.
  • a business developed using a business development tool can use an interface to invoke a service, and the caller invokes the call interface of the service to trigger.
  • the service test environment in the foregoing step S1202 refers to an environment in which the operator needs to provide the developer for service test in the telecommunication capability resource function entity. After the developer completes the development of the business, uploads his own business and applies for testing in the telecom capability management portal. The test environment only provides the telecommunications capability simulation running environment, so the developer does not need the developer to purchase the telecommunications capability when testing the business. You only need to wait for the telecom ability administrator to review and deploy the business into the business test environment to test.
  • both the call interface and the return interface are the same as those invoked in the formal environment. The difference is that when the service is running in the business test environment, it does not actually call the telecom capability, but simulates a return result.
  • the management process of the telecommunication capability/atomic service is described in the above step S1203. Developers can purchase telecommunications capabilities/atomic services in the telecommunications capability resource functional entity (by purchasing the license to use the telecommunications capability/atomic service).
  • atomic services mean that developers can develop in business.
  • the binding process is to authenticate the application of the calling service in the telecommunications capability resource functional entity.
  • the binding of the service and the telecommunication capability is described in the above step S1203.
  • the binding of the service and the telecommunication capability requires the developer to first purchase the telecommunication capability and upload the service in the telecommunication capability resource portal.
  • the service execution environment authenticates the binding relationship between the service and the telecommunication capabilities. For example, the developer uploaded the services S 1 and S2, purchased the short message capability A1 and the positioning capability A2, and the service S 1 used the two communication capabilities A1 and A2.
  • the service execution environment queries whether the service S1 and the telecommunication capability A1 are bound when using A1. Relationship, if there is telecommunications capability A1 will be executed, otherwise the business will fail to execute. The same is true for telecommunications capabilities A2.
  • the binding relationship between service and telecommunication capabilities is many-to-many. That is, S 1 can be bound to A1 and A2, and S2 can also be bound to A1 and A2. The purpose of the binding is to judge whether the service has the right to use the telecommunications capability during the execution of the service.
  • step 4 S 1205 describes the tampering application business call interface to call the formal environment.
  • the same is true for the service execution environment and the service test environment. The difference is that the service execution environment is actually connected to the telecom capability, and the specific telecommunication capability needs to be authenticated.
  • the service test environment does not need to be called. Telecommunications capabilities, only need to simulate the success or failure of telecom capability calls. For an application calling service, the interfaces are the same and the addresses are different.
  • the service test environment address is ADDRESS 1
  • the address of the service invoked by the application is ADDRESS 1.
  • the service execution environment address is ADDRESS2
  • the application needs to modify its call address to ADDRESS2 to test the service it invokes.
  • 13 is a flowchart of processing an application for uploading a telecommunications capable according to Embodiment 3 of the present invention.
  • a process for a developer to upload an application having telecommunications capabilities includes the following steps: Step S1301, a developer uses telecommunications capabilities.
  • the business development environment provided by the resource function entity develops its own business and uploads it to the telecom capability resource function entity to apply for testing.
  • Step S1302 The telecommunications capability resource administrator reviews the service test application.
  • Step 4 S 1303. After the business test application is approved, the service can be deployed and tested in the business test environment.
  • the developer can use the service in the service test environment when developing the application that invokes the service. Services running in a business test environment are analog calls when calling telecommunications capabilities, not real calls.
  • Step S1305 The developer needs to use the telecom capability in the telecommunication capability resource portal to purchase the service, bind the application service and the capability, register the service information, and apply for the service to go online.
  • Step S1306 The telecommunications capability resource administrator reviews the service information and the online application for the service. After the audit is passed, the administrator deploys the business in the business execution environment.
  • Step 4 S S307 the business is officially running in the business execution environment.
  • Step S 1309 the developer fills in the application information in the developer community, uploads the application package, and applies the application and business binding.
  • Step S 1310 the developer community administrator reviews the application information, tests the application package, and approves the application and business binding application.
  • Step S 1311 After the application and the service binding information are approved, the developer community needs to send the request to the telecommunication capability resource functional entity.
  • the request can be an internal private real-time response interface, and the interface form is not limited.
  • step S 1312 the telecommunication capability resource function entity needs to determine the service state when receiving the application and service binding request sent by the developer community, and only the service in the state in the service license can be bound to the application.
  • the state Can be online.
  • the telecom capability resource function entity receives the binding request from the developer community, it judges according to the business logic. After confirming that the binding is successful, the binding takes effect.
  • Step 4 gathers S 1313. After the binding is officially effective, the entire signing process is successful.
  • Step 4 S 1314 the mobile app store manager can query the list of apps to be uploaded by developers in all developer communities. The administrator can sell the app to the app store online store. The application was successfully launched and began to be sold to end users.
  • the solution provided in this embodiment implements the development of an application with telecommunications capabilities, thereby ensuring the interests of operators and improving the survivability of operators in the future.
  • the steps shown in the flowchart of the accompanying drawings may be performed in a computer system such as a set of computer executable instructions, and, although the logical order is shown in the flowchart, in some cases, The steps shown or described may be performed in an order different than that herein.
  • the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices.
  • the invention is not limited to any particular combination of hardware and software.
  • the above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Stored Programmes (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Description

应用商店系统及使用该应用商店系统进行开发的方法 技术领域 本发明涉及通信领域, 具体而言, 涉及一种应用商店系统及使用该应用 商店系统进行开发的方法。 背景技术 随着第三代 (the 3rd Generation, 简称为 3G ) 移动通信的发展和智能手 机的发展, 手机互联网 (internet ) 的应用越来越广泛。 在这样的环境下, 苹 果从 2008年开始通过应用提供系统(称为手机应用商店)提供 iPhone应用, 在短期内取得了接近 10亿的下载量。 这种手机应用商店的使用, 造就了一大批应用的独立开发者。 各大运营 商、 手机制造商以及互联网厂商也将推出各自的在线应用商店提上日程, 或 业已 ·ί舞出在线应用商店。 在普通的应用商店系统中, 主要的功能实体为应用商店网店以及开发者 社区, 当然, 这两个功能实体可以合设在一起, 如图 1所示, 这种普通的应 用商店没有与电信能力对接的功能, 开发者开发的应用无法使用电信能力。 现有的应用商店网店的主要功能模块包括: 门户, 鉴权模块, 应用分发 模块, 供应销售模块, 业务支撑模块和运营支撑模块。 门户主要提供 WEB 门户、 WAP门户、 手机客户端或者 PC客户端的访问入口, 通过该入口, 手 机终端用户可以方便的搜索和下载应用。 鉴权模块提供对用户的鉴权以及应 用的鉴权。 应用分发模块提供各种应用分发途径的功能, 比如下载到电脑、 WAP PUSH到手机、 短信发送地址或者客户端直接下载安装等与应用分发相 关的功能。 供应销售模块提供对应用商店中销售的应用的管理包括: 店铺和 货架的管理、 应用上线下线的管理以及推荐排行的管理。 现有的开发者社区的主要功能包括: 应用上传, 应用管理功能, 论坛功 能, 开发者 wiki。 可见, 目前的这种系统中, 仅仅支持普通的应用, 而无法支持对具有电 信能力的业务的执行, 从而使得执行该业务的应用也无法实现电信能力的接 入, 这势必将运营商下降到 "管道,, 的地位, 严重影响了运营商的利益和未 来的生存能力。 发明内容 本发明的主要目的在于提供一种应用商店系统及使用该应用商店系统进 行开发的方法, 以至少解决上述问题。 根据本发明的一个方面, 提供了一种电信能力资源功能实体, 包括: 业 务执行模块, 设置为通过接口调用能力开放网关中的电信能力来执行具有电 信能力的业务, 其中, 该业务用于嵌入在应用中。 优选地, 该电信能力资源功能实体还包括: 业务开发模块, 设置为提供 具有电信能力的业务的开发环境。 优选地, 电信能力资源功能实体还包括: 业务测试模块, 设置为提供用 于测试业务的电信能力模拟运行环境, 返回在环境中执行业务时的模拟执行 结果。 优选地, 电信能力资源功能实体还包括: 授权模块, 设置为授权业务使 用该业务所调用的电信能力; 第一绑定模块, 设置为在授权模块完成授权的 情况下, 接受将业务与该业务所调用的电信能力进行绑定的操作; 业务执行 模块还设置为判断当前执行的业务与其使用的电信能力之间是否具有绑定关 系, 若是, 则继续执行业务, 若不是, 结束处理。 根据本发明的另一个方面, 提供了一种应用商店系统, 包括: 开发者社 区功能实体, 设置为接受应用的上传, 并对上传的应用进行审核; 应用商店 网店功能实体, 设置为供终端用户下载通过开发者社区模块审核的应用; 电 信能力资源功能实体, 包括: 业务执行模块, 设置为通过接口调用能力开放 网关中的电信能力来执行具有电信能力的业务, 其中, 业务用于嵌入在应用 中; 开发者社区功能实体中上传的应用中嵌入电信能力资源功能实体的业务 执行模块执行的具有电信能力的业务。 优选地, 电信能力资源功能实体还包括: 业务开发模块, 设置为提供具 有电信能力的业务的开发环境。 优选地, 电信能力资源功能实体还包括: 业务测试模块, 设置为提供用 于测试业务的电信能力模拟运行环境, 返回在环境中执行业务时的模拟执行 结果。 优选地, 电信能力资源功能实体还包括: 授权模块, 设置为授权业务使 用该业务所调用的电信能力; 第一绑定模块, 设置为在授权模块完成授权的 情况下, 接受将业务与该业务所调用的电信能力进行绑定的操作; 业务执行 模块还设置为判断当前执行的业务与其使用的电信能力之间是否具有绑定关 系, 若是, 则继续执行业务, 否则, 结束处理。 优选地, 开发者社区功能实体包括: 第二绑定模块, 设置为接受将应用 与该应用中嵌入的业务进行绑定的操作; 绑定生效模块, 设置为将绑定的信 息通知业务执行模块; 业务执行模块还设置为判断当前调用业务的应用与其 所调用的业务之间是否具有绑定关系, 若是, 则继续执行业务, 若不是, 结 束处理。 优选地, 业务执行模块还设置为在接收到绑定的信息之后, 判断绑定的 应用是否被授权使用绑定的业务, 若是, 则向绑定生效模块返回绑定生效的 信息。 优选地, 开发者社区功能实体中上传的应用通过与嵌入在应用中的业务 相对应的调用接口调用业务。 根据本发明的又一个方面, 提供了一种应用以上应用商店系统进行开发 的方法, 包括: 将在业务执行模块中执行的具有电信能力的业务嵌入在应用 中, 其中, 应用中嵌入的业务通过接口调用能力开放网关中的电信能力。 优选地, 在将业务嵌入在应用中之前, 还包括: 在业务开发模块提供的 具有电信能力的业务的开发环境中开发具有电信能力的业务。 优选地, 在将业务嵌入在应用中之前, 还包括: 在业务测试模块提供的 用于设置为测试业务的电信能力模拟运行环境中, 执行业务, 获得执行业务 时的模拟执行结果来完成对业务的测试。 优选地, 在将业务嵌入在应用中之前, 还包括: 通过授权模块获得业务 使用该业务所调用的电信能力的授权; 通过第一绑定模块将业务和该业务所 调用的电信能力绑定, 以便业务执行模块在执行业务之前进行电信能力使用 合法性的鉴权。 优选地, 在将业务嵌入在应用中之后, 还包括: 在开发者社区功能实体 中通过第二绑定模块将业务和该业务嵌入的应用绑定, 开发者社区功能实体 将绑定关系通知给业务执行模块, 以便业务执行模块在执行业务之前进行应 用和业务之间的调用关系的合法性的鉴权。 优选地, 还包括: 通过调用业务测试模块执行应用中嵌入的业务, 获得 模拟执行结果以实现对应用的测试; 或者, 通过调用业务执行模块执行应用 中嵌入的业务, 获得执行结果以实现对应用的测试。 通过本发明, 釆用通过接口调用能力开放网关中的电信能力来执行具有 电信能力的业务, 再将该业务嵌入到应用中, 解决了无法提供具有电信能力 的应用的问题, 实现了对具备电信能力的应用的开发, 从而保障了运营商的 利益, 提高了运营商在未来的生存能力。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部 分, 本发明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的 不当限定。 在附图中: 图 1是根据现有技术的应用商店系统的结构框图; 图 2是根据本发明实施例的电信能力资源功能实体的结构框图; 图 3是根据本发明实施例的电信能力资源功能实体的优选结构框图; 图 4是根据本发明实施例的电信能力资源功能实体的优选结构框图二; 图 5是根据本发明实施例的电信能力资源功能实体的优选结构框图三; 图 6是才艮据本发明实施例的应用商店系统的结构框图; 图 7是才艮据本发明实施例的应用商店系统的优选结构框图; 图 8是根据本发明实施例的应用业务测试 /执行模块对应用进行测试的 示意图; 图 9是根据本发明实施例 1的实现手机应用商店的系统的结构框图; 图 10是才艮据本发明实施例 2的使用应用商店系统开发普通应用的处理 流程图; 图 11是才艮据本发明实施例 2的上传普通应用的处理流程图; 图 12是根据本发明实施例 3的使用应用商店系统开发具有电信能力的 应用的处理 ¾ϊ程图; 图 13是根据本发明实施例 3的上传具备电信能力的应用的处理流程图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是, 在 不冲突的情况下, 本申请中的实施例及实施例中的特征可以相互组合。 图 2是根据本发明实施例的电信能力资源功能实体的结构框图, 该电信 能力资源功能实体 22包括: 业务执行模块 24 , 设置为通过接口调用能力开 放网关中的电信能力来执行具有该电信能力的业务, 其中, 该业务用于嵌入 在应用中。 该电信能力资源功能实体中, 业务执行时业务执行模块 26通过接口调 用能力开放网关中的电信能力来执行该业务, 从而能够提供具有电信能力的 业务。 通过该电信能力资源功能实体, 能够实现具有电信能力的业务, 从而 使得开发具有电信能力的应用成为了可能, 保障了运营商的利益, 提高了运 营商在未来的生存能力。 图 3是 居本发明实施例的电信能力资源功能实体的优选结构框图, 如 图 3所示, 该功能实体 22还可以包括: 业务开发模块 32 , 设置为提供具有 电信能力的业务的开发环境。 通过业务开发模块 24提供了具有电信能力的 业务的开发环境, 开发者就可以在电信能力资源功能实体 22中实现具备电 信能力的业务的开发。 作为一种优选的改进方案, 该电信能力资源功能实体 22在实现开发功 能之外, 还可以实现对开发的业务的测试功能, 图 4是才艮据本发明实施例的 电信能力资源功能实体的优选结构框图二, 如图 4所示电信能力资源功能实 体 22还可以包括: 业务测试模块 42 , 设置为提供用于测试业务的电信能力 模拟运行环境, 返回在环境中执行业务时的模拟执行结果。 该实施例增强了 电信能力资源功能实体的功能, 提供了具有开发、 测试、 运行等功能, 提高 了该功能实体的实用性。 在开发者开发了业务后, 该电信能力资源功能实体还可以进一步提供对 开发者开发的应用使用电信能力进行授权的功能, 只有在系统授权该业务具 有使用权限的情况下, 该业务才能够使用该电信能力, 并且, 还可以在通过 将业务和其使用的电信能力进行绑定, 来实现对业务的鉴权。 图 5是根据本 发明实施例的电信能力资源功能实体的优选结构框图三, 如图 5所示, 在图 2的基础上, 电信能力资源功能实体 22还可以包括: 授权模块 52 , 设置为 授权某个业务使用该业务所调用的电信能力; 第一绑定模块 54 , 设置为在授 权模块 52完成授权的情况下, 接受将业务与该业务所调用的电信能力进行 绑定的操作; 业务执行模块 24还设置为判断当前执行的业务与其使用的电 信能力之间是否具有绑定关系, 若是, 则继续执行业务, 否则, 结束处理, 优选地, 还可以返回相应的错误信息。 通过以上的结构, 电信能力资源功能 实体能够对开发者开发的业务进行授权和鉴权, 提高了系统的安全性。 本实施例还提供了一种改进的应用商店系统, 图 6是才艮据本发明实施例 的应用商店系统的结构框图, 如图 6所示, 该应用商店系统包括: 开发者社 区功能实体 62 , 设置为接受应用的上传, 并对上传的应用进行审核; 应用商 店网店功能实体 64 , 设置为供终端用户下载通过开发者社区模块审核的应 用; 以上的电信能力资源功能实体 22 , 开发者社区功能实体 62中上传的应 用中嵌入电信能力资源功能实体 22所执行的具有电信能力的业务。 另外,该应用商店系统还可以提供对应用是否能够使用某个业务的鉴权, 图 7是才艮据本发明实施例的应用商店系统的优选结构框图, 如图 7所示, 在 图 6的基础上, 开发者社区功能实体 62可以包括: 第二绑定模块 72 , 设置 为接受将应用与该应用中嵌入的业务进行绑定的操作; 绑定生效模块 74 , 设 置为将绑定的信息通知业务执行模块 24; 业务执行模块 24还设置为判断当 前调用业务的应用与其所调用的业务之间是否具有绑定关系, 若是, 则继续 执行业务, 否则, 结束处理, 优选地, 还可以返回相应的错误信息。 通过以 上的结构, 进一步提高了系统的安全性。 在图 7所示的网络结构中, 业务执行模块 24还可以对应用和业务的绑 定关系进行校验, 在业务获得了使用电信能力的授权的情况下, 才允许进行 绑定, 具体地, 业务执行模块 24在接收到绑定的信息之后, 判断绑定的应 用是否被授权使用该绑定的业务, 若是, 则向绑定生效模块 74返回绑定生 效的信息。 该实施例防止将应用绑定到未获授权的业务上, 降低了应用的运 行失败 4既率。 优选地, 以上的应用可以通过与嵌入在该应用中的业务相对应的调用接 口来调用该业务, 业务返回业务执行返回结果给应用, 该接口可以是内部自 定义接口, 形式不限, 可以是 SOAP, 也可以是 REST, 以方便应用的调用 为准则, 具体实现比较简单, 在此不再赘述。 需要说明的是, 以上系统中的各个模块分别用于实现不同的功能, 开发 者可以调用不同的模块来实现业务 /应用的开发, 这些模块之间, 一般不存在 主动的信号交互 (作为一种优选的结构, 绑定生效模块 74与第二绑定模块 72和业务执行模块 24之间可以存在自动的信号 (具体为绑定信息和绑定生 效的信息)的交互), 其仅用于实现自身的功能后反馈给开发者, 后续执行哪 个模块完全是用户决定的, 也就是说, 这些模块的逻辑执行顺序完全是由开 发者的调用顺序来决定的, 而开发者的调用顺序可能因具体需要而改变, 甚 至可能并不使用所有的模块, 因此, 在附图中, 并没有用连线表示模块之间 的关系。 以上实施例所提供的电信能力资源功能实体 22 旨在提供具有电信能力 的业务的执行 /开发 /测试等功能, 该电信能力资源功能实体 22和开发者社区 功能实体 62以及应用商店网店功能实体 64集成在一起构成应用商店系统, 能够实现具有电信能力的应用的开发、 管理和售卖。 本实施例还提供了一种使用以上的应用商店系统进行开发的方法, 该方 法包括: 将在业务执行模块中执行的具有电信能力的业务嵌入在应用中, 其 中, 该应用中嵌入的业务通过接口调用能力开放网关中的电信能力。 通过该方法, 使得开发具有电信能力的应用成为了可能, 从而保障了运 营商的利益, 提高了运营商在未来的生存能力。 在将业务嵌入在应用中之前, 可以在业务开发模块提供的具有电信能力 的业务的开发环境中开发具有电信能力的业务。 通过这种方式, 开发者可以 自行设计业务, 从而开发更加个性化的应用。 优选地, 在将业务嵌入在应用中之前, 还可以包括: 在业务测试模块提 供的用于测试业务的电信能力模拟运行环境中, 执行业务, 获得执行业务时 的模拟执行结果来完成对业务的测试。 该方法增强了开发系统的功能, 提供 了开发、 测试、 运行等功能, 提高了系统的实用性。 优选地, 为了实现对应用的测试, 还可以通过调用业务测试模块 42执 行所述应用中嵌入的所述业务, 获得所述模拟执行结果以实现对所述应用的 测试; 或者, 通过调用业务执行模块 24执行所述应用中嵌入的业务, 获得 执行结果以实现对所述应用的测试。 图 8是 居本发明实施例的应用业务测 试 /执行模块对应用进行测试的示意图, 如图 8所示, 通过釆用业务测试模块 42对业务进行测试, 或通过业务执行模块 24对业务进行执行, 可以提供对 应用的测试功能, 也就是说, 对应用的测试可以基于对业务的测试, 也可以 基于对业务的正式执行, 开发者在现有的开发流程中,在对应用进行测试时, 只需获取业务的模拟或实际执行结果进而得到应用的测试结果, 对原有的系 统改动较小, 容易实现。 优选地, 在将业务嵌入在应用中之前, 还可以包括: 通过 ·ί受权模块获得 业务使用该业务所调用的电信能力的授权; 将业务和该业务所调用的电信能 力绑定,以便业务执行模块在执行业务之前进行电信能力使用合法性的鉴权。 优选地, 在将业务嵌入在应用中之后, 还包括: 在开发者社区功能实体 中将业务和该业务嵌入的应用绑定, 开发者社区功能实体将绑定关系通知给 业务执行模块, 以便业务执行模块在执行业务之前进行应用和业务之间的调 用关系的合法性的鉴权。 下面描述的实施例 1-3 , 综合了上述多个优选实施例的技术方案。 实施例 1 该实施例提供了一种实现手机应用商店的系统, 以及在该系统上进行应 用开发的方法。 图 9是根据本发明实施例 1的实现手机应用商店的系统的结构框图, 如 图 9所示, 该系统包括以下几个功能实体: 应用商店网店, 该功能实体提供手机终端用户访问的 WEB门户、 WAP 门户和手机客户端, 用户可以查询应用、 购买应用和下载应用, 同时, 运营 商管理员也在该网店中对手机应用的上架流程进行管理; 开发者社区, 该功能实体提供开发者上传应用、 管理应用、 测试应用以 及论坛等功能, 同时运营商管理员也可以在该功能实体中发布 SDK、 进行技 术支持, 对应用进行审核、 测试等流程管理; 电信能力资源功能实体, 该功能实体对开发者提供了电信能力的业务开 发环境、业务测试环境以及业务执行环境,提供了接入能力开放网关的接口, 还为开发者提供了业务开发 wiki。 使用该功能实体提供的业务开发环境, 开 发者可以使用系统提供的业务开发工具开发出具备电信能力的业务, 并嵌入 到自己的应用中;电信能力资源功能实体还提供了接入能力开放网关的接口, 业务执行环境中正在运行的业务可以使用该接口调用电信能力。 除此之外, 还提供了能力管理、 业务管理、 业务鉴权、 应用鉴权等相关功能。 开发者可 以在业务开发 wiki中学习开发业务的方法, 在业务开发环境中进行业务开 发。 当业务开发完成, 开发者可以将业务部署到业务测试环境中进行测试。 一个业务如果需要使用到一个或多个电信能力, 还必须在该功能实体中购买 相应的电信能力或者原子服务。 开发者可以对自己的业务进行管理, 并且还 需要购买业务使用到的相应的电信能力或系统提供的原子服务才能让自己的 业务正常使用, 这一系列流程需要管理员对整个流程进行审核或测试, 审核 测试通过后业务才能正式的部署到业务执行环境中。 使用上述的应用商店系统, 开发者可以开发和上传一个具备电信能力的 业务和应用, 其主要流程包括: 步骤 1 , 开发者在电信能力资源功能实体提供的业务开发环境中开发业 务, 在电信能力资源功能实体业务测试环境中测试业务。 步骤 2, 开发者开发应用, 调用业务测试环境中的业务, 对应用进行测 试。 步骤 3 , 开发者在电信能力资源功能实体中购买能力, 并将已购买的能 力和业务进行绑定, 并申请业务上线。 步骤 4, 电信能力资源功能实体管理员审核通过后, 将业务部署到业务 执行环境中, 对业务进行上线操作。 业务执行环境可以调用能力资源, 能力 资源包括能力开放网关以及互联网能力。 业务执行环境中的业务调用能力资 源的接口协议可以是 SOAP, 也可以是 REST。 步骤 5 , 开发者在开发者社区功能实体中填写应用信息, 上传应用程序 包, 并申请应用和业务绑定。 步骤 6, 开发者社区管理员对应用进行审核, 审核通过后, 应用状态为 待上架 (待上架的应用需要由网店管理员进行上架操作后才能在网店中正式 进行售卖)。 步骤 7, 应用商店网店管理员对待上架的应用进行上架处理。 应用正式 在应用商店网店功能实体中对外销售。 使用本实施例的应用商店系统, 不但可以开发普通的应用, 也可以开发 具备电信能力的业务和应用。 为了详细的描述该系统的各功能实体功能, 以 下的实施例 2和 3分别描述了开发者使用该系统进行普通应用和具备电信能 力的应用 /业务的开发, 应用上传, 一直到应用上架销售的整个流程。 实施例 2 图 10是才艮据本发明实施例 2的使用应用商店系统开发普通应用的处理 流程图, 如图 10所示, 开发者使用该系统开发普通应用的流程包括以下步 骤: 步骤 S 1001 , 开发者在手机操作系统开发环境中开发应用, 生成应用程 序包 (不同的手机应用程序的开发环境, 开发工具, 程序包格式和后缀都各 不相同)。 该开发环境由手机操作系统的开发工具提供。 举例说明, 如果开发 者需要开发一个 android操作系统的应用, 那么需要使用 android手机应用开 而如果开发者需要开发一个 iphone手机应用, 那么需要使用苹果的开发工具 xtool在 MAC操作系统的开发环境中来进行开发。 步骤 S 1002, 开发者在开发者社区中填写应用信息并将程序包上传, 开 发者社区管理员对应用进行审核和测试, 审核测试完成后该应用待上架。 步骤 S 1003 , 应用商店网店管理员对待上架的应用进行上架操作, 应用 上架成功, 开始面向终端用户销售。 图 11是才艮据本发明实施例 2的上传普通应用的处理流程图, 如图 11所 示, 步骤 1002中上传普通应用的流程包括以下步骤: 步骤 S 1101 , 开发者在开发者社区填写应用信息、 上传应用程序包。 步骤 S 1102 , 开发者社区管理员对应用信息进行审核, 对应用程序包进 行测试。 步骤 S 1103 , 开发者社区管理员审核和测试通过后, 应用状态为待上架。 步 4聚 S 1104, 应用商店管理员可以查询到待上架的应用。 应用商店网店 管理员可以对待上架应用进行上架处理。 步骤 S 1105 , 应用上架后即生效, 可在网店门户或网店客户端中被终端 用户查询和购买。 对于普通的应用程序开发, 开发者在应用商店系统中所做的最主要的操 作就是对应用程序包进行上传。 上传的手机应用程序经过一系列的网店审核 和测试流程处理即可上架面向终端用户进行销售。 对于普通应用如果需要一个服务端对其提供服务, 那么开发者可以在应 用程序的内部使用私有接口与自己的服务器进行交互。 举例说明, 假设开发 者需要开发一个手机应用程序 A, A是网页站点 B的手机应用客户端。 应用 程序 A可以在联网的时候获取站点 B的更新新闻和好友列表,当终端用户使 用应用程序 A浏览某则新闻的时候可以选择向站内好友发送一条短信或彩 信。 按照普通应用程序的开发原理, 手机应用程序 A可以理解为网页站点 B 的一个 client, 网页站点 B可以理解为手机应用程序 A的一个 server。 手机 应用程序 A获取更新的新闻可以使用私有接口(也可以是网页站点 B提供相 应的 REST开放接口)直接向 B发起请求, 当需要发送短信 /彩信时也需要向 B通过相应的接口发起请求。 需要注意的是, 发送短信 /彩信或者新闻内容的 提供是 B使用相应接口提供给 A调用的功能。 按照传统的运营和开发模式, 当网页站点 B在运营过程中需要使用运营 商提供的电信能力, B需要作为一个 SP向运营商申请和购买相应的能力。 对于企业或大型网站来说, 是可行的, 但是对于普通的中小开发者来说, 因 为他们没有相应的 SP资质, 所以无法实现在自己的程序中使用运营商提供 的电信能力。 而釆用实施例 1提供的系统可以使得中小型独立开发者也有能 力开发具备运营商提供的电信能力的应用。 以下通过实施例 3描述开发者使 用实施例 1的系统进行具备电信能力的应用 /业务的开发、 上传, 一直到应用 上架销售的整个流程。 实施例 3 图 12是根据本发明实施例 3的使用应用商店系统开发具有电信能力的 应用的处理流程图, 如图 12所示, 开发者开发具备电信能力的应用以及使 用电信能力的业务的流程包括以下步骤: 步骤 S 1201 , 开发者使用电信能力资源功能实体提供的业务开发环境开 发具备电信能力的业务, 并在业务在线测试环境中进行测试。 步骤 S 1202, 开发者开发应用, 该应用使用接口调用具备电信能力的业 务。 该应用可以调用部署在业务测试环境中的业务进行测试。 步骤 S 1203 , 开发者在电信能力资源功能实体中购买能力, 并申请业务 上线。 管理员审批和测试通过后将业务上线, 部署到业务执行环境中。 当业 务上线和能力购买成功后, 开发者可以申请业务和电信能力的绑定。 只有当 某业务和某电信能力绑定后该业务才有使用该电信能力的权限。 步骤 S 1204, 开发者将应用 4爹改为调用正式的业务执行环境中的业务, 进行测试。 步骤 S 1205 , 开发者在开发者社区中上传开发好的应用并将应用与已经 部署好的业务进行绑定,管理员对应用以及应用与业务的绑定关系进行审核、 测试。 只有当应用和某业务绑定时, 该应用才有使用该业务的权限。 步骤 S 1206, 开发者社区管理员审核和测试应用通过后, 应用商店网店 管理员可以查询到所有状态为待上架的应用, 管理员可以在应用商店网店中 将该应用上架销售。 应用上架成功后, 开始面向终端用户销售。 在上述步骤 S 1201中, 具备电信能力的业务指的是使用一个或多个电信 能力组成的业务流程。 举例说明, 一个简单的业务可以是一个发送一条短信 内容到某一个手机上的业务。 该业务的开发过程为: 1 , 开发者下载业务开 发工具并学习开发工具的使用; 2, 开发者使用开发工具开发业务, 将业务 的调用接口设计为入口参数为手机号码和短信内容, 返回参数为发送成功或 失败的返回结果; 3 , 开发的业务流程为: 用户读取手机号码和短信内容, 使用开发工具中提供的发送短信能力的原子服务发送短信, 读取原子服务返 回结果并将该结果作为业务调用返回参数返回给业务调用者。 一个组合的业务可以是一个由一个或多个电信能力组成的略为复杂的业 务。 举例说明, 该业务可以是判断一个手机终端是否在一个地理区域内, 如 果是, 则给这个手机发送一条广告短信。 该业务的开发过程为: 1 , 开发者 下载业务开发工具并学习开发工具的使用; 2, 开发者设计该业务的调用接 口为用户手机号码, 广告商店主地理位置, 广告短信内容, 返回参数为短信 发送成功、 用户不在区域内或者短信发送失败的返回结果; 3 , 业务开发流 程为: 业务读取用户手机号码和广告商店主地理位置, 业务 居手机号码和 广告商店主地理位置调用定位月艮务原子月艮务, 该原子月艮务返回相对距离, 业 务根据相对距离进行判断, 如果相对距离小于 1公里, 则向该手机用户发送 一条广告短信, 如果相对距离大于 1公里, 则不做任何操作, 业务将业务操 作返回结果返回给业务调用者。 以上业务开发工具是业务开发环境提供给开发者使用的工具, 对调用电 信能力资源的方法进行了封装, 对开发者来说他们要做的就是用少量的脚本 控制逻辑对工具中提供的原子服务进行组装。 但从底层来说, 业务调用电信 能力最终仍然是通过调用能力开放网关的接口来实现的。 对于运营商来说, 提供业务开发工具是降低了开发者的开发门槛, 为开发者快速、 便捷的开发 业务创造了更好的条件。 对于上述业务开发环境中的业务开发工具, 其具体 功能和实现并不属于本发明的范围。 该业务开发工具面向开发者和 SP, 主要 功能是利用工具中提供的各种电信能力以及原子服务实现一些具有逻辑的电 信能力业务。 使用业务开发工具开发出来的业务可以使用接口对业务进行调 用, 由调用者调用该业务的调用接口来触发。 上述步骤 S 1202中的业务测试环境指的是运营商在电信能力资源功能实 体中需要提供开发者进行业务测试的环境。 开发者完成业务的开发之后, 在 电信能力管理门户中上传自己的业务并申请测试, 该测试环境仅仅是提供电 信能力模拟运行环境, 所以开发者测试业务的时候并不需要开发者去购买电 信能力, 只需要等待电信能力管理员审核通过并将业务部署到业务测试环境 中即可进行测试。 业务在业务测试环境中测试的时候, 调用接口和返回接口 都与正式环境中的调用方式相同。 不同的是, 业务在业务测试环境中运行的 时候并不会真实的调用电信能力, 而是模拟一个返回结果。 上述步骤 S 1203中描述了电信能力 /原子服务的管理过程。开发者可以在 电信能力资源功能实体中购买电信能力 /原子服务(通过购买获得使用该电信 能力 /原子服务的授权)。 在这里, 原子服务指的是可以供开发者在业务开发 环境中调用的, 或者说可以购买的电信能力组件, 比如说发送短信的原子月艮 务, 发送彩信的原子服务, 也可以是定位的原子服务等等。 开发者在购买了 电信能力 /原子服务后需要将自己的业务和电信能力做一个绑定的操作。该绑 定过程是为了在电信能力资源功能实体中对调用业务的应用做鉴权。 上述步骤 S 1203中描述了业务和电信能力的绑定, 业务和电信能力的绑 定需要开发者首先在电信能力资源门户中购买电信能力并上传业务。 业务在 使用电信能力的时候,业务执行环境会对业务和电信能力的绑定关系作鉴权。 举例说明,开发者上传了业务 S 1和 S2,购买了短信能力 A1和定位能力 A2, 业务 S 1使用了 A1和 A2两种电信能力。 如果开发者将业务 S 1和自己购买 的短信能力 A1和 A2进行绑定, 在业务 S 1执行过程中, 业务执行环境会在 使用到 A1的时候查询业务 S 1和电信能力 A1是否有绑定关系, 如果有电信 能力 A1才会被执行, 否则业务会执行失败。 对于电信能力 A2也相同。 其中 业务和电信能力的绑定关系为多对多。 也就是说, S 1可以绑定 A1和 A2, S2也可以绑定 A1和 A2。 绑定的目的是在业务执行过程中, 对业务是否有 使用电信能力的权限作判断, 如果业务没有绑定某个电信能力, 那么执行该 电信能力的调用时就会报错。 上述步 4聚 S 1205描述了 4爹改应用的业务调用接口为调用正式环境。 业务 执行环境和业务测试环境的相同点是业务的调用接口相同, 不同点是, 业务 执行环境真正的和电信能力对接, 需要对具体的电信能力进行鉴权, 而业务 测试环境不需要真实的调用电信能力, 只需要模拟电信能力调用的成功或失 败即可。 对于应用调用业务来说, 接口相同, 调用的地址不同。 在业务开发 完毕后, 开发者首先申请业务在测试环境中运行, 业务测试环境地址为 ADDRESS 1 , 应用调用的业务的地址为 ADDRESS 1。 当业务正式上线并在业 务执行环境中运行时, 业务执行环境地址为 ADDRESS2, 应用需要修改其调 用地址为 ADDRESS2来测试其调用的业务。 图 13是根据本发明实施例 3的上传具备电信能力的应用的处理流程图, 如图 13所示, 开发者上传具备电信能力的应用的流程包括以下步骤: 步骤 S 1301 , 开发者使用电信能力资源功能实体提供的业务开发环境开 发自己的业务, 并上传到电信能力资源功能实体, 申请进行测试。 步骤 S 1302, 电信能力资源管理员对业务测试申请进行审核。 步 4聚 S 1303 , 业务测试申请审核通过后, 该业务可以在业务测试环境中 部署和测试。 步骤 S 1304, 开发者开发调用业务的应用时可以使用业务测试环境中的 业务。 在业务测试环境中运行的业务在调用电信能力的时候都是模拟调用, 并非真实的调用。 步骤 S 1305 , 开发者在电信能力资源门户中购买业务需要使用的电信能 力, 申请业务和能力绑定, 注册业务信息并申请业务上线。 步骤 S 1306, 电信能力资源管理员对业务信息和业务上线申请进行审核。 审核通过后, 管理员将业务部署在业务执行环境中。 步 4聚 S 1307, 业务正式在业务执行环境中运行。 步骤 S 1308, 开发者 4爹改开发的应用为调用正式环境中的业务, 对应用 进行测试。 步骤 S 1309, 开发者在开发者社区中填写应用信息, 上传应用程序包, 申请应用与业务绑定。 步骤 S 1310, 开发者社区管理员对应用信息进行审核, 对应用程序包进 行测试, 对应用与业务绑定申请进行审批。 步骤 S 1311 , 应用与业务绑定信息审批通过后, 开发者社区需要将请求 发送到电信能力资源功能实体中。 该请求可以是内部的私有实时响应接口, 接口形式不限。 步骤 S 1312, 电信能力资源功能实体收到开发者社区发送的应用和业务 绑定请求时需要判断业务状态, 只有在业务许可内的状态中的业务才可以与 应用绑定, 举例说明, 该状态可以是已上线。 电信能力资源功能实体接收到 开发者社区发来的绑定请求时按照业务逻辑判断, 确认绑定成功后, 该绑定 才正式生效。 步 4聚 S 1313 , 绑定正式生效后, 整个签约过程成功。 步 4聚 S 1314, 手机应用网店管理员可以查询到所有开发者社区中开发者 上传的待上架的应用列表。管理员可以在应用商店网店中将该应用上架销售。 应用上架成功, 开始面向终端用户销售。 综上所述, 本实施例提供的方案实现了对具备电信能力的应用的开发, 从而保障了运营商的利益, 提高了运营商在未来的生存能力。 需要说明的是, 在附图的流程图示出的步骤可以在诸如一组计算机可执 行指令的计算机系统中执行, 并且, 虽然在流程图中示出了逻辑顺序, 但是 在某些情况下, 可以以不同于此处的顺序执行所示出或描述的步骤。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布 在多个计算装置所组成的网络上, 可选地, 它们可以用计算装置可执行的程 序代码来实现, 从而, 可以将它们存储在存储装置中由计算装置来执行, 或 者将它们分别制作成各个集成电路模块, 或者将它们中的多个模块或步骤制 作成单个集成电路模块来实现。 这样, 本发明不限制于任何特定的硬件和软 件结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本 领域的技术人员来说, 本发明可以有各种更改和变化。 凡在本发明的^"神和 原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护 范围之内。

Claims

权 利 要 求 书
1. 一种电信能力资源功能实体, 包括:
业务执行模块, 设置为通过接口调用能力开放网关中的电信能力 来执行具有所述电信能力的业务, 其中, 所述业务用于嵌入在应用中。
2. 根据权利要求 1所述的电信能力资源功能实体, 其中, 还包括:
业务开发模块, 设置为提供具有所述电信能力的所述业务的开发 环境。
3. 根据权利要求 1所述的电信能力资源功能实体, 其中, 还包括:
业务测试模块, 设置为提供用于测试所述业务的电信能力模拟运 行环境, 返回在所述环境中执行所述业务时的模拟执行结果。
4. 根据权利要求 1所述的电信能力资源功能实体, 其中,
所述电信能力资源功能实体还包括: 授权模块, 设置为授权所述 业务使用该业务所调用的电信能力; 第一绑定模块, 设置为在所述授 权模块完成授权的情况下, 接受将所述业务与该业务所调用的电信能 力进行绑定的操作;
所述业务执行模块还设置为判断当前执行的所述业务与其使用的 所述电信能力之间是否具有绑定关系, 若是, 则继续执行所述业务, 否则, 结束处理。
5. —种应用商店系统, 包括:
开发者社区功能实体, 设置为接受应用的上传, 并对所述上传的 应用进行审核;
应用商店网店功能实体, 设置为供终端用户下载通过所述开发者 社区模块审核的应用;
电信能力资源功能实体, 包括:
业务执行模块, 设置为通过接口调用能力开放网关中的电信能力 来执行具有所述电信能力的业务, 其中, 所述业务用于嵌入在应用中; 所述开发者社区功能实体中上传的应用中嵌入所述电信能力资源 功能实体的所述业务执行模块执行的具有所述电信能力的业务。
6. 根据权利要求 5所述的系统, 其中, 所述电信能力资源功能实体还包 括:
业务开发模块, 设置为提供具有所述电信能力的所述业务的开发 环境。
7. 根据权利要求 5所述的系统, 其中, 所述电信能力资源功能实体还包 括:
业务测试模块, 设置为提供用于测试所述业务的电信能力模拟运 行环境, 返回在所述环境中执行所述业务时的模拟执行结果。
8. 根据权利要求 5所述的系统, 其中,
所述电信能力资源功能实体还包括: 授权模块, 设置为授权所述 业务使用该业务所调用的电信能力; 第一绑定模块, 设置为在所述授 权模块完成授权的情况下, 接受将所述业务与该业务所调用的电信能 力进行绑定的操作;
所述业务执行模块还设置为判断当前执行的所述业务与其使用的 所述电信能力之间是否具有绑定关系, 若是, 则继续执行所述业务, 否则, 结束处理。
9. 根据权利要求 5所述的系统, 其中,
所述开发者社区功能实体包括: 第二绑定模块, 设置为接受将所 述应用与该应用中嵌入的业务进行绑定的操作; 绑定生效模块, 设置 为将绑定的信息通知所述业务执行模块;
所述业务执行模块还设置为判断当前调用业务的应用与其所调用 的业务之间是否具有绑定关系, 若是, 则继续执行所述业务, 否则, 结束处理。
10. 根据权利要求 9所述的系统, 其中,
所述业务执行模块还设置为在接收到所述绑定的信息之后, 判断 绑定的所述应用是否被授权使用绑定的所述业务, 若是, 则向所述绑 定生效模块返回绑定生效的信息。
11. 根据权利要求 5所述的系统, 其中, 所述开发者社区功能实体中上传 的应用通过与嵌入在所述应用中的所述业务相对应的调用接口调用所 述业务。
12. 一种应用权利要求 5-11中任一项所述的应用商店系统进行开发的方 法, 包括:
将在所述业务执行模块中执行的具有电信能力的业务嵌入在应用 中, 其中, 所述应用中嵌入的所述业务通过所述接口调用所述能力开 放网关中的电信能力。
13. 才艮据权利要求 12所述的方法, 其中, 在将所述业务嵌入在所述应用中 之前, 还包括: 在业务开发模块提供的具有电信能力的业务的开发环境中开发具 有所述电信能力的业务。
14. 才艮据权利要求 12所述的方法, 其中, 在将所述业务嵌入在所述应用中 之前, 还包括:
在业务测试模块提供的用于测试所述业务的电信能力模拟运行环 境中, 执行所述业务, 获得执行所述业务时的模拟执行结果来完成对 所述业务的测试。
15. 才艮据权利要求 12所述的方法, 其中, 在将所述业务嵌入在所述应用中 之前, 还包括:
通过授权模块获得所述业务使用该业务所调用的电信能力的授 权;
通过第一绑定模块将所述业务和该业务所调用的电信能力绑定, 以便所述业务执行模块在执行所述业务之前进行电信能力使用合法性 的鉴权。
16. 才艮据权利要求 12所述的方法, 其中, 在将所述业务嵌入在所述应用中 之后, 还包括:
在所述开发者社区功能实体中通过第二绑定模块将所述业务和该 业务嵌入的应用绑定, 所述开发者社区功能实体将绑定关系通知给所 述业务执行模块, 以便所述业务执行模块在执行所述业务之前进行应 用和业务之间的调用关系的合法性的鉴权。
17. 根据权利要求 12所述的方法, 其中, 还包括:
通过调用业务测试模块执行所述应用中嵌入的所述业务, 获得所 述模拟执行结果以实现对所述应用的测试; 或者,
通过调用业务执行模块执行所述应用中嵌入的业务, 获得执行结 果以实现对所述应用的测试。
PCT/CN2011/072058 2010-09-29 2011-03-22 应用商店系统及使用该应用商店系统进行开发的方法 WO2012041046A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2013530532A JP5751561B2 (ja) 2010-09-29 2011-03-22 アプリケーションストアシステム及び当該アプリケーションストアシステムによる開発方法
EP11827942.1A EP2624517A4 (en) 2010-09-29 2011-03-22 APPLICATION STORE SYSTEM AND DEVELOPMENT METHOD USING THE APPLICATION STORE SYSTEM
US13/876,503 US9173050B2 (en) 2010-09-29 2011-03-22 Application store system and development method using the application store system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010505953.5 2010-09-29
CN201010505953.5A CN102437998B (zh) 2010-09-29 2010-09-29 应用商店系统及使用该应用商店系统进行开发的方法

Publications (1)

Publication Number Publication Date
WO2012041046A1 true WO2012041046A1 (zh) 2012-04-05

Family

ID=45891872

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/072058 WO2012041046A1 (zh) 2010-09-29 2011-03-22 应用商店系统及使用该应用商店系统进行开发的方法

Country Status (5)

Country Link
US (1) US9173050B2 (zh)
EP (1) EP2624517A4 (zh)
JP (1) JP5751561B2 (zh)
CN (1) CN102437998B (zh)
WO (1) WO2012041046A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103139695B (zh) * 2011-12-05 2015-11-25 中国电信股份有限公司 面向客户端的电信能力调用方法和网络设备
CN102710753B (zh) * 2012-05-15 2015-09-09 华为技术有限公司 一种互联网应用的发布方法、装置及系统
CN104038381B (zh) * 2013-03-07 2018-11-09 腾讯科技(深圳)有限公司 应用的云测试方法、系统、客户端及服务器
CN104834602B (zh) * 2015-05-20 2019-02-22 广州华多网络科技有限公司 一种程序发布方法、装置和程序发布系统
CN107222524B (zh) * 2017-05-08 2020-07-31 广州智淘信息科技有限公司 一种开放式应用服务集成框架
CN107911235B (zh) * 2017-10-30 2019-08-09 中国联合网络通信集团有限公司 一种电信能力开放动态授权方法及服务器
CN107832380B (zh) * 2017-10-30 2021-06-11 北京博瑞彤芸科技股份有限公司 一种数据记录方法
CN107862207A (zh) * 2017-12-01 2018-03-30 四川精工伟达智能技术股份有限公司 应用可信管理系统及方法
CN109754144A (zh) * 2018-01-23 2019-05-14 启迪云控(北京)科技有限公司 面向云控的智能网联汽车数据及应用管理方法和装置
CN108805678A (zh) * 2018-06-14 2018-11-13 安徽鼎龙网络传媒有限公司 一种微场景管理后台微信商城综合测定系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101014051A (zh) * 2007-02-28 2007-08-08 华为技术有限公司 实现网络游戏中用户间通信的方法、系统及装置
CN101299862A (zh) * 2008-06-11 2008-11-05 中国电信股份有限公司 一种电信业务生成环境系统
WO2010002490A2 (en) * 2008-06-08 2010-01-07 Apple Inc. Techniques for acquiring updates for application programs
CN101686253A (zh) * 2008-09-23 2010-03-31 华为技术有限公司 服务选择方法、装置和系统

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2399720C (en) * 2000-02-11 2013-07-09 Convergent Networks, Inc. Service level executable environment for integrated pstn and ip networks and call processing language therefor
CA2399715C (en) * 2000-02-11 2009-08-04 Convergent Networks, Inc. Methods and systems for creating, distributing and executing multimedia telecommunications applications over circuit and packet switched networks
JP2004078448A (ja) * 2002-08-14 2004-03-11 Nippon Telegr & Teleph Corp <Ntt> プログラム自動生成装置
US8554916B2 (en) * 2005-04-11 2013-10-08 Accenture Global Services Gmbh Service delivery platform and development of new client business models
CN101025808A (zh) * 2006-02-18 2007-08-29 黄建国 一种信息交易的方法
US20070264985A1 (en) * 2006-04-17 2007-11-15 Flextronics Software Systems Method and system for rapid creation of applications in communication devices
KR101029425B1 (ko) * 2008-11-20 2011-04-14 엔에이치엔(주) 멀티 유저 네트워크 게임의 제작 시스템 및 방법
US8745153B2 (en) * 2009-02-09 2014-06-03 Apple Inc. Intelligent download of application programs
EP2244435B1 (en) * 2009-04-20 2015-07-22 Accenture Global Services Limited IMS application server, network, method, and computer program product for executing services, particularly IP contact center services

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101014051A (zh) * 2007-02-28 2007-08-08 华为技术有限公司 实现网络游戏中用户间通信的方法、系统及装置
WO2010002490A2 (en) * 2008-06-08 2010-01-07 Apple Inc. Techniques for acquiring updates for application programs
CN101299862A (zh) * 2008-06-11 2008-11-05 中国电信股份有限公司 一种电信业务生成环境系统
CN101686253A (zh) * 2008-09-23 2010-03-31 华为技术有限公司 服务选择方法、装置和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2624517A4 *

Also Published As

Publication number Publication date
US9173050B2 (en) 2015-10-27
US20130183948A1 (en) 2013-07-18
CN102437998A (zh) 2012-05-02
CN102437998B (zh) 2015-11-25
JP2013542504A (ja) 2013-11-21
JP5751561B2 (ja) 2015-07-22
EP2624517A4 (en) 2016-05-11
EP2624517A1 (en) 2013-08-07

Similar Documents

Publication Publication Date Title
WO2012041046A1 (zh) 应用商店系统及使用该应用商店系统进行开发的方法
US20210271472A1 (en) Application Wrapping for Application Management Framework
JP5838218B2 (ja) アプリストアシステム及び当該アプリストアシステムを用いたアプリケーションの開発方法
US20040093595A1 (en) Software application framework for network-connected devices
CN106550033A (zh) 基于云计算系统实现模拟全网能力开放平台的系统和方法
JP2015216664A (ja) 無線加入者ネットワークにおけるアプリケーションをベースにした価値課金
WO2014194774A1 (zh) 创建移动应用商店的系统及方法
US9838869B1 (en) Delivering digital content to a mobile device via a digital rights clearing house
CN101771993A (zh) 基于移动网络实现聚合应用的系统及其方法
CN102024124B (zh) 移动微件处理方法、装置及客户端
CN109462600A (zh) 访问应用的方法、用户设备、登录服务器和存储介质
CN113569166A (zh) 一种数据处理方法、装置、电子设备及存储介质
Kirkman et al. Using smart contracts and blockchains to support consumer trust across distributed clouds
Dragoni et al. Security-by-Contract (S x C) for Software and Services of Mobile Systems
Janczukowicz Firefox os overview
US20230289472A1 (en) Privacy as a Service
CN113626398B (zh) 一种应用于政务服务事项网上申报的材料共享实现方法
Kruger Cellphone banking at the bottom of the pyramid
Fridh eSIM Re-Selling on Mobile App
Inacio Lemes et al. An Analysis of Mobile Application Update Strategies via Cordova
Janczukowicz et al. Firefox OS Ecosystem: Ambitions and Limits of an Open Source Operating System for Mobile Devices
Hamer et al. Security and Selling Your Game
TW201344472A (zh) 查詢應用程式下載記錄之方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11827942

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2013530532

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 13876503

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2011827942

Country of ref document: EP