A method, device and equipment for providing software services

Abstract

The embodiments of this specification disclose a method, apparatus and device for providing software services. The solution may include: after receiving a first service acquisition request generated by an IoT device based on a standard interface protocol provided by the software service providing platform, the software service providing platform may generate a second service acquisition request that can be processed by the target service provider based on the adaptation information between the standard interface protocol and the target interface protocol required to be used by the target service provider, so that the target service provider can process the second service acquisition request and generate a request processing result. Subsequently, the software service providing platform may feed back the request processing result generated by the target service provider to the IoT device.

Description

Technical Field

[0001] The present application relates to the field of software service technology, and in particular to a method, device and equipment for providing software services. Background Art

[0002] SaaS is the abbreviation of Software-as-a-Service, which is a new software service provision model that has gradually emerged with the development of Internet technology and the maturity of application software. The service provider can fully manage and maintain the application software, and publish the software service corresponding to the application software on the software service provision platform. The service demander can obtain the software service provided by the service provider through the software service provision platform without the need for the service demander to maintain the application software by himself, which is convenient and fast.

[0003] At present, since the access standards of different software service provision platforms are usually inconsistent, only service providers and service demanders who are stationed in the same software service provision platform can interact with each other, which affects the versatility of the software services that the service providers can provide.

[0004] Based on this, how to improve the versatility of software services that service providers can provide has become a technical problem that needs to be solved urgently. Summary of the invention

[0005] The embodiments of this specification provide a method, device, and equipment for providing software services, which can improve the versatility of software services that can be provided by service providers.

[0006] To solve the above technical problems, the embodiments of this specification are implemented as follows:

[0007] A software service providing method provided in an embodiment of this specification may include:

[0008] The software service providing platform obtains a first service obtaining request for a software service from an Internet of Things device; the first service obtaining request is a request generated using a standard interface protocol provided by the software service providing platform.

[0009] In response to the first service acquisition request, a second service acquisition request that can be processed by the target service provider is generated based on the adaptation information between the standard interface protocol and the target interface protocol; the target interface protocol is the interface protocol required to be used by the target service provider in providing the software service.

[0010] Determine a request processing result generated by the target service provider for the second service acquisition request.

[0011] Send the request processing result to the IoT device.

[0012] A software service providing device provided in an embodiment of this specification may include:

[0013] The first request acquisition module can be used to obtain a first service acquisition request of the Internet of Things device for a software service; the first service acquisition request is a request generated by using a standard interface protocol provided by the software service providing platform.

[0014] The second request generation module can be used to respond to the first service acquisition request and generate a second service acquisition request that can be processed by the target service provider based on the adaptation information between the standard interface protocol and the target interface protocol; the target interface protocol is the interface protocol required to be used by the target service provider in the process of providing the software service.

[0015] The result determination module may be configured to determine a request processing result generated by the target service provider in response to the second service acquisition request.

[0016] The result sending module can be used to send the request processing result to the Internet of Things device.

[0017] A software service providing device provided in an embodiment of this specification may include:

[0018] at least one processor; and a memory in communication with the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0019] A first service acquisition request for a software service from an Internet of Things device is obtained; the first service acquisition request is a request generated using a standard interface protocol provided by the software service providing platform.

[0020] In response to the first service acquisition request, a second service acquisition request that can be processed by the target service provider is generated based on the adaptation information between the standard interface protocol and the target interface protocol; the target interface protocol is the interface protocol required to be used by the target service provider in providing the software service.

[0021] Determine a request processing result generated by the target service provider for the second service acquisition request.

[0022] Send the request processing result to the IoT device.

[0023] At least one embodiment provided in this specification can achieve the following beneficial effects:

[0024] After receiving the first service acquisition request generated by the IoT device based on the standard interface protocol it provides, the software service provider platform can generate a second service acquisition request that can be processed by the target service provider based on the adaptation information between the standard interface protocol and the target interface protocol required by the target service provider, so as to feed back the request processing result generated by the target service provider for processing the second service acquisition request to the IoT device. This enables all service providers that provide software services based on various non-standard interface protocols to access the same software service provider platform and provide software services to service demanders that obtain services based on standard interface protocols, which is not only conducive to improving the versatility of software services that can be provided by service providers, but also conducive to expanding the service demander's selection range for software service providers and improving the experience of both parties. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0026] Figure 1 A schematic diagram of an application scenario of a software service providing method provided in an embodiment of this specification.

[0027] Figure 2 A flowchart of a method for providing software services provided in an embodiment of this specification.

[0028] Figure 3 The embodiments of this specification provide corresponding to Figure 2 A swimlane flow diagram of the software service provision method in .

[0029] Figure 4 The embodiments of this specification provide corresponding to Figure 2 A structural diagram of a software service providing device.

[0030] Figure 5 The embodiments of this specification provide corresponding to Figure 2 A structural diagram of a software service providing device. DETAILED DESCRIPTION

[0031] In order to make the purpose, technical solutions and advantages of one or more embodiments of this specification clearer, the technical solutions of one or more embodiments of this specification will be clearly and completely described below in combination with the specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this description, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of one or more embodiments of this specification.

[0032] The technical solutions provided by the embodiments of this specification are described in detail below in conjunction with the accompanying drawings.

[0033] In the prior art, with the development of Internet technology and the maturity of application software, service demanders gradually begin to call the software services provided by service providers through software service provision platforms in the process of handling business, so as to reduce the software management burden of service demanders. At present, the interface protocols adopted by different software service provision platforms are usually inconsistent, and there are often differences in the naming rules and data formats for the same parameters in different interface protocols. As a result, if a service provider needs to provide software services to service demanders connected to different software service provision platforms, it is necessary to develop a set of software service application programs according to the interface protocols used by each software service provision platform, so as to use the application program consistent with the interface protocol of the software service provision platform to provide software services to the service demanders stationed in the software service provision platform, but it is impossible to use the application program built based on other interface protocols to provide software services to the service demanders, thereby affecting the versatility and convenience of the software services that the service provider can provide.

[0034] In order to solve the defects in the prior art, this solution provides the following embodiments:

[0035] Figure 1 A schematic diagram of an application scenario of a software service providing method provided in an embodiment of this specification.

[0036] like Figure 1As shown, the target service provider 103 can provide software services to the Internet of Things device 102 (i.e., the service demander) through the software service providing platform 101. Specifically, after the Internet of Things device 102 sends a first service acquisition request to the software service providing platform 101, the software service providing platform 101 can generate a second service acquisition request that can be processed by the target service provider 103 according to the interface protocol used by the target service provider 103 and the Internet of Things device 102, and send the second service acquisition request to the target service provider 103. After receiving the second service acquisition request, the target service provider 103 can process the second service acquisition request to obtain a request processing result for the second service acquisition request. Subsequently, the software service providing platform 101 can also receive the request processing result of the target service provider 103 for the second service acquisition request, so as to feed back the request processing result to the Internet of Things device 102.

[0037] Figure 1 The solution enables the target service provider 103 to use its application built based on any interface protocol at the software service providing platform 101 to provide software services to the IoT device 102, without having to specially build an application for providing software services that is consistent with the interface protocol used by the software service providing platform 101 and the IoT device 102. This is not only conducive to improving the versatility and convenience of the software services that can be provided by the target service provider 103, but also conducive to reducing the cost of the target service provider 103 when providing software services to the IoT device 102 based on different interface protocols.

[0038] Next, a software service providing method provided in the embodiment of the specification will be specifically described with reference to the accompanying drawings:

[0039] Figure 2 The following is a flowchart of a software service providing method provided in an embodiment of this specification. From a program perspective, the execution subject of the process can be a software service providing platform, or an application installed on the software service providing platform. Figure 2 As shown, the process may include the following steps:

[0040] Step 202: The software service providing platform obtains a first service obtaining request from the IoT device for a software service; the first service obtaining request is a request generated using a standard interface protocol provided by the software service providing platform.

[0041] In the embodiments of this specification, the software service providing platform can communicate with the service demander and the service provider for the software service respectively, so that the service provider can provide software services to the service demander. It can be seen that the software service providing platform can realize the function of providing software services through the network of the SaaS platform. Among them, the service demander can usually be an Internet of Things (IoT) device, such as a cash register device, a payment device, etc., which is not specifically limited.

[0042] The first service acquisition request for the software service can be a request generated by the Internet of Things device when it needs to obtain the software service in the process of processing the business. In actual applications, the software service provider platform can provide a standard interface protocol for use by the Internet of Things devices and service providers, so as to facilitate the standardization and management convenience of the software service call process. Based on this, when the Internet of Things device is able to communicate with the software service provider platform and request to obtain the software service, it can usually be said that the Internet of Things device is already equipped with an application that can request to obtain the software service based on the standard interface protocol, so that the first service acquisition request can be a request generated using the standard interface protocol provided by the software service provider platform, so that the software service provider platform can subsequently process the first service acquisition request.

[0043] In the embodiments of this specification, the standard interface protocol may be an interface protocol customized by the software service provider platform, which may refer to the communication method and requirements that need to be followed between interfaces that need to exchange information. In practical applications, the standard interface protocol may not only specify the communication information of the physical layer, but also specify the relevant requirements of the syntax layer and the semantic layer, which is not specifically limited.

[0044] In the embodiments of this specification, the software service may refer to a SaaS service (Software as a Service) that needs to be called by an IoT device. In actual applications, the type of software service is usually related to the business that the IoT device needs to process. For example, when the IoT device is a payment device, the software service called by the IoT device may be a SaaS service for processing user orders, or a SaaS service for marketing products, etc., without specific limitation.

[0045] Step 204: In response to the first service acquisition request, a second service acquisition request that can be processed by the target service provider is generated based on the adaptation information between the standard interface protocol and the target interface protocol; the target interface protocol is the interface protocol required to be used by the target service provider in providing the software service.

[0046] In the embodiments of this specification, the target interface protocol may be an interface protocol required to be used in the process of the target service provider providing the software service, for example, it may be an interface protocol used by the target service provider when building an application for providing the software service. The target interface protocol may be the same interface protocol as the standard interface protocol, or may be an interface protocol different from the standard interface protocol, and this is not specifically limited.

[0047] Among them, the target service provider can usually be an independent software vendor (ISV in English), specifically, it can be an enterprise specializing in software development, production, sales and services; or, the target service provider can also be an existing SaaS platform, and the SaaS platform can forward the second service acquisition request to the settled ISV for processing, thereby generating a request processing result generated for the second service acquisition request, and there is no specific limitation on this.

[0048] In the embodiments of the present specification, the adaptation information can be used to reflect whether the target interface protocol is consistent with the standard interface protocol. When the two are inconsistent, the adaptation information can also be used to reflect whether the target service provider has the protocol conversion information between the target interface protocol and the standard interface protocol. Thus, the software service provision platform can generate a second service acquisition request that can be processed by the target service provider based on the adaptation information. In actual applications, the second service acquisition request can be generated based on the target interface protocol, or it can be generated based on the standard interface protocol. There is no specific limitation on this. It only requires that the target service provider can correctly parse and process the second service acquisition request based on the protocol conversion information it can obtain and / or the application used to provide the software service.

[0049] Step 206: Determine a request processing result generated by the target service provider for the second service acquisition request.

[0050] In the embodiment of the present specification, the request processing result may be generated by the target service provider processing the service request data carried in the second service acquisition request through an application program providing the software service.

[0051] Specifically, the software service providing platform may issue a request to obtain the request processing result to obtain the request processing result from the target service provider. Alternatively, it may be agreed in advance that the target service provider automatically feeds back the request processing result to the software service providing platform after generating it, which is not specifically limited.

[0052] Step 208: Send the request processing result to the IoT device.

[0053] In the embodiments of this specification, the software service providing platform also needs to feed back the request processing result to the IoT device to meet the software service acquisition needs of the IoT device. Specifically, since the IoT device obtains software services based on a standard interface protocol, in order to facilitate the IoT device to parse the request processing result, the software service providing platform can send the request processing result generated based on the standard interface protocol to the IoT device. In actual applications, the request processing result generated based on the standard interface protocol can be generated by the target service provider itself, or it can be generated by the software service providing platform based on the protocol conversion information and the request processing result fed back by the target service provider. There is no specific limitation on this.

[0054] Figure 2 In the method, after receiving the first service acquisition request generated by the IoT device based on the standard interface protocol provided by the software service providing platform, the software service providing platform can generate a second service acquisition request that can be processed by the target service provider according to the adaptation information between the standard interface protocol and the target interface protocol required to be used by the target service provider, so as to feed back the request processing result generated by the target service provider for processing the second service acquisition request to the IoT device. Thus, each service provider that provides software services based on various non-standard interface protocols can access the same software service providing platform and provide software services to service demanders that obtain services based on standard interface protocols, which is not only conducive to improving the versatility of software services that can be provided by service providers, but also conducive to expanding the service demander's selection range for software service providers and improving the experience of both parties.

[0055] In addition, since the target service provider can use existing applications built based on non-standard interface protocols to provide software services to IoT devices using standard interface protocols, without having to specially build applications based on standard interface protocols to prompt software services, it is also beneficial to reduce the cost of the target service provider when providing software services to IoT devices based on different interface protocols.

[0056] based on Figure 2The method in this specification also provides some specific implementation plans of the method, which are described below.

[0057] In the embodiments of this specification, in order to facilitate the protection of the security and rights of the IoT device in the process of obtaining software services, it is usually necessary to authenticate the identity of the target service provider in advance, and only after the identity authentication is passed will the target service provider be allowed to enter the software service provision platform to provide software services to the IoT devices connected to the software service provision platform.

[0058] Based on this, the step 202: before the software service providing platform obtains the first service acquisition request of the Internet of Things device for the software service, may also include:

[0059] The software service providing platform obtains an identity authentication request from the target service provider; the identity authentication request carries the identity authentication information of the target service provider.

[0060] In response to the identity authentication request, a trustworthy verification is performed on the identity authentication information to obtain an identity authentication result.

[0061] If the identity authentication result indicates that the identity authentication information is verified successfully, the unique identity identification information allocated by the software service providing platform to the target service provider is sent to the target service provider; the target service provider can provide the software service to the service demander based on the unique identity identification information.

[0062] In an embodiment of the present specification, the identity authentication request may be a request generated by the target service provider when entering the software service providing platform, and the identity authentication request may carry identity authentication information for identifying the identity and qualifications of the target service provider. In practical applications, since the target service provider is usually an enterprise or an institution, the identity authentication information may include information such as the business license of the target service provider, the value-added telecommunications business operation license, and the professional and technical personnel's professional certificates. In addition, the identity authentication request may also carry service description information of the software service that the target service provider expects to provide, such as the type information of the software service, the content information of the software service, etc., so that the software service providing platform can process the identity authentication request more accurately based on the above service description information.

[0063] In the embodiments of the present specification, the identity authentication result may indicate whether the identity authentication information verification has passed. In actual applications, if the identity authentication information of the target service provider meets the qualification requirements and is authentic and valid, an identity authentication result indicating that the identity authentication information verification has passed may be generated; and if the identity authentication information of the target service provider does not meet the qualification requirements or is false information or invalid information, an identity authentication result indicating that the identity authentication information verification has failed may be generated. In addition, if the service description information for the software service in the identity authentication request indicates that the software service is a non-compliant software service, an identity authentication result indicating that the identity authentication information verification has failed may also be generated to prevent the target service provider from providing non-compliant software services to IoT devices.

[0064] In the embodiment of this specification, if the identity authentication information is verified, the software service providing platform can generate unique identity information for uniquely identifying the target service provider. In actual application, the unique identity information can be used as the ID (Identity document) of the target service provider, and the unique identity information can be information in the form of a string.

[0065] In the embodiments of the present specification, by issuing unique identity information to the target service provider after identity authentication, the target service provider can enter the software service provision platform, and subsequently publish and provide software services to IoT devices based on the unique identity information, so that the software service provision platform can manage the service provider and the software services it provides.

[0066] In the embodiment of the present specification, if the identity authentication result indicates that the identity authentication information verification failed, information indicating that the identity authentication failed can also be sent to the target service provider, and the reason why the identity authentication information verification failed can be informed, so that the target service provider can modify the identity authentication information and use the modified identity authentication information to continue to try to enter the software service provision platform, which is beneficial to improving the experience of the target service provider.

[0067] In the embodiment of this specification, before providing the software service, the target service provider also needs to publish the software service on the software service providing platform so that the software service is visible and available to the service demander.

[0068] Based on this, after sending the unique identity information allocated by the software service providing platform to the target service provider to the target service provider, the method may further include:

[0069] A software service publishing instruction of the target service provider is obtained; the software service publishing instruction may be used to instruct the software service to be published at the software service providing platform.

[0070] In response to the software service publishing instruction, association relationship information between the software service and the unique identity information is established; the association relationship information can be used to indicate that the target service provider is the provider of the software service.

[0071] In the embodiments of this specification, after the target service provider has built the application and other required resources for providing software services, the target service provider can send a software service publishing instruction to the software service providing platform. In actual applications, the software service publishing instruction can carry the unique identity information obtained by the target service provider after identity authentication, so as to establish the association relationship information between the unique identity information and the software service, so that the software service providing platform can identify the target service provider based on the association relationship information to provide the software service, and then the Internet of Things device can call the target service provider to provide the software service.

[0072] In actual applications, the same target service provider may need to publish multiple different software services. Therefore, in order to distinguish the specific software service at the target service provider called by the user, different service unique identification information can be assigned to different software services published by the target service provider, or different service call interfaces can be configured in the IoT device for different software services to distinguish them. Based on this, the first service acquisition request in step 202 can carry the service unique identification information of the software service, or the first service acquisition request in step 202 can also be a request generated by the service call interface corresponding to the software service, which is convenient and fast.

[0073] In actual applications, the software service publishing instruction may also carry service description information, service charge information, service call condition information, etc. for the software service, which is not specifically limited.

[0074] In the embodiments of this specification, since the software service providing platform can identify whether the target service provider is the provider of the software service through the association relationship information between the unique identity information of the target service provider and the software service, based on this, the first service acquisition request sent by the IoT device can carry the target unique identity information of the service provider specified by the IoT device and used to provide the software service. That is, the service provider with the target unique identity information is the service provider that the IoT device expects to provide software services to it.

[0075] Correspondingly, step 204: generating a second service acquisition request that can be processed by the target service provider may specifically include:

[0076] If the target unique identity information is consistent with the unique identity information of the target service provider, a second service acquisition request that can be processed by the target service provider is generated.

[0077] In an embodiment of the present specification, based on the target unique identity information carried in the first service acquisition request, and the association relationship information between the software service and the unique identity information, the target service provider targeted by the first service acquisition request can be accurately determined, and then the adaptation information between the standard interface protocol and the target interface protocol of the target service provider can be determined, so that a second service acquisition request that can be processed by the target service provider can be generated.

[0078] In the embodiments of the present specification, since the first service acquisition request sent by the IoT device may carry the target unique identity information of the service provider designated by it and used to provide the software service, before the IoT device generates the first service acquisition request, the unique identity information of each service provider and the association relationship information between the software services they can provide need to be sent to the IoT device for selection by the user of the IoT device.

[0079] Based on this, after establishing the association relationship information between the software service and the unique identity information, the following may also be included:

[0080] Sending the association relationship information between the software service and the unique identity information to the Internet of Things device; the Internet of Things device can be used to generate the first service acquisition request based on the association relationship information.

[0081] In the embodiments of this specification, since the software service providing platform has the ability to communicate with the IoT device, the software service providing platform can send the association relationship information between the software service and the unique identity information of the service provider to the IoT device. Alternatively, since the IoT device usually needs to deploy an application for obtaining software services (i.e., a target application, such as a payment application, a shopping application, etc.), based on this, the software service providing platform can also send the association relationship information between the software service and the unique identity information of the service provider to the IoT device through the server of the above-mentioned target application, and this is not specifically limited.

[0082] In actual applications, when the target application program carried by the IoT device needs to obtain software services, the IoT device can select the target unique identity information carried in the first service acquisition request based on the association relationship information between the software service and the unique identity information of the service provider based on manual operation or preset information. The preset information can be the target unique identity information of the service provider for providing the software service pre-set by the administrator of the IoT device to ensure the user's willingness to obtain software services.

[0083] In actual applications, the target application program installed in the IoT device is usually generated based on the standard interface protocol of the software service provider platform. In actual applications, there are many ways to use the target unique identity information to build the target application program based on the target unique identity information.

[0084] Method 1: The target application developer may directly write the target application according to the standard interface protocol.

[0085] Specifically, before obtaining the first service acquisition request of the IoT device for the software service, the following may also be included:

[0086] The standard interface protocol is sent to the device of the target application developer; the IoT device carries the target application generated by the target application developer based on the standard interface protocol, so as to generate the first service acquisition request by using the target application.

[0087] In an embodiment of the present specification, when developing or updating the target application, the target application developer can obtain the standard interface protocol from the software service provider platform in advance, and write the part of the target application used to obtain software services based on the software service provider platform based on the standard interface protocol, so that when the generated target application runs on the Internet of Things device, it can generate a first service acquisition request based on the standard interface protocol.

[0088] Method 2: The target application developer may use the components written based on the standard interface protocol provided by the software service provider platform to generate the target application.

[0089] Specifically, the standard interface protocol may include a Service Provider Interface (SPI) protocol; the software service providing platform has a program file generated based on the Service Provider Interface protocol and used to request the component of the software service.

[0090] Correspondingly, before obtaining the first service acquisition request of the IoT device for the software service, the following may also be included:

[0091] The program file of the component is sent to the device of the target application developer; the IoT device carries the target application generated by the target application developer based on the program file of the component, so as to generate the first service acquisition request by utilizing the component in the target application.

[0092] In the embodiments of the present specification, the organization to which the software service provider platform belongs can pre-build a component that can be used to request the software service based on the service provider program interface protocol (i.e., the standard interface protocol), and provide the program file of the above component to the target application developer through the software service provider platform. At this time, when the target application developer develops or updates the target application, he can use the program file of the above component to build this part of the application for obtaining the software service based on the software service provider platform, so that when the target application generated by it runs at the Internet of Things device, it can generate a first service acquisition request based on the standard interface protocol based on the program file of the above component contained therein, so as to simplify the process of building the target application.

[0093] Among them, the component provided by the software service providing platform for requesting to obtain the software service can be an SPI component. The SPI component is a set of APIs provided by Java for implementation or extension by a third party. It can be used to enable framework extension and replacement components with good flexibility.

[0094] In the embodiments of the present specification, before the software service is released, it is also necessary to determine the adaptation information between the target interface protocol used by the target service provider when providing the software service and the standard interface protocol at the software service providing platform, so as to ensure that the target service provider can provide the software service to the Internet of Things device based on the adaptation information.

[0095] Based on this, before establishing the association relationship information between the software service and the unique identity information, the following may also be included:

[0096] It is determined whether the target interface protocol is consistent with the standard interface protocol to obtain a first determination result.

[0097] If the first judgment result indicates that the target interface protocol is consistent with the standard interface protocol, first adaptation status information is generated that can be used to reflect that the target interface protocol is consistent with the standard interface protocol.

[0098] Correspondingly, the step 204: in response to the first service acquisition request, generating a second service acquisition request that can be processed by the target service provider according to the adaptation information between the standard interface protocol and the target interface protocol, may specifically include:

[0099] A second service acquisition request based on the standard interface protocol is generated according to the first adaptation situation information and the first service acquisition request; the second service acquisition request carries the service request data generated based on the standard interface protocol in the first service acquisition request.

[0100] In an embodiment of the present specification, if the first judgment result indicates that the target interface protocol at the target service provider is consistent with the standard interface protocol, it may indicate that the application used by the target service provider when providing software services is built based on the standard interface protocol. At this time, since the target service provider and the Internet of Things device both interact with each other based on the standard interface protocol, there is no need to generate protocol conversion information. Therefore, the first adaptation status information reflecting the consistency of the target interface protocol with the standard interface protocol may be generated.

[0101] Correspondingly, after receiving the first service acquisition request, if the first adaptation status information reflects that the target interface protocol is consistent with the standard interface protocol, it means that the application providing software services at the target service provider is also generated based on the standard interface protocol, so that it can be determined that the target service provider is able to process the first service acquisition request generated based on the standard interface protocol. At this time, the first service acquisition request can be directly used as the second service acquisition request sent to the target service provider, or the service request data generated based on the standard interface protocol in the first service acquisition request can be extracted, and a second service acquisition request carrying the service request data can be generated. There is no specific limitation on this.

[0102] Among them, the service request data in the first service acquisition request is usually the input parameters that the target service provider needs to obtain when providing software services. For example, when the software service is a marketing service for a product, the service request data may include product information, marketing activity content information, etc., and when the software service is a payment service for a purchase order for a product, the service request data may include product unit price information, purchase quantity information, preferential marketing activity content discount information, etc., without specific limitation.

[0103] In the embodiments of this specification, in order to facilitate the target service provider to generate an application program based on a standard interface protocol to provide software services, it is also necessary to provide the target service provider with a standard interface protocol before the target service provider builds the application program.

[0104] Specifically, if the first judgment result indicates that the target interface protocol is consistent with the standard interface protocol, before establishing the association relationship information between the software service and the unique identity information, the following may also be included:

[0105] The standard interface protocol is sent to the target service provider; the target service provider can be used to generate an application program for providing the software service based on the standard interface protocol.

[0106] In the embodiment of this specification, after the target service provider settles in the software service providing platform, it can obtain the standard interface protocol from the software service providing platform and develop an application for providing the software service based on the standard interface protocol, which is convenient and fast.

[0107] In actual applications, since the target service provider may have built an application for providing software services based on a non-standard interface protocol before entering the software service provision platform, there is a situation where the target interface protocol used by the target service provider is inconsistent with the standard interface protocol used by the IoT device. At this time, protocol conversion information can be created so that the target service provider can provide software services to the IoT device based on the protocol conversion information.

[0108] Based on this, the determining whether the target interface protocol is consistent with the standard interface protocol, after obtaining the first determination result, may further include:

[0109] If the first judgment result indicates that the target interface protocol is inconsistent with the standard interface protocol, it is determined whether the target service provider has protocol conversion information between the target interface protocol and the standard interface protocol to obtain a second judgment result.

[0110] If the second judgment result indicates that the target service provider has the protocol conversion information, second adaptation information is generated to indicate that the target service provider has the protocol conversion information; the second adaptation information can be used to reflect that the target interface protocol is inconsistent with the standard interface protocol.

[0111] Correspondingly, the step 204: in response to the first service acquisition request, generating a second service acquisition request that can be processed by the target service provider according to the adaptation information between the standard interface protocol and the target interface protocol, may specifically include:

[0112] A second service acquisition request based on the standard interface protocol is generated according to the second adaptation situation information and the first service acquisition request.

[0113] In the embodiment of the present specification, the protocol conversion information can be used to convert a request generated based on the standard interface protocol into a request generated based on the target interface protocol. Specifically, the protocol conversion information can record the corresponding relationship between the parameters in the target interface protocol and the standard interface protocol, for example, the corresponding relationship between the parameter name, the parameter data format, etc. For example, assuming that the user name is recorded as "UID" in the standard interface protocol and as "UserID" in the target interface protocol; then the protocol conversion information can include the corresponding relationship between "UID" in the standard interface protocol and "UserID" in the target interface protocol. Or, assuming that the numerical unit for the unit price of the commodity in the standard interface protocol is "yuan", and the numerical unit for the unit price of the commodity in the target interface protocol is "jiao"; then the protocol conversion information can include the corresponding relationship reflecting that the numerical units of the unit price of the commodity in the standard interface protocol and the target interface protocol are "yuan" and "jiao" respectively, or the protocol conversion information can include the corresponding relationship reflecting that the numerical value of the unit price of the commodity in the target interface protocol is 10 times the numerical value of the unit price of the commodity in the standard interface protocol, which is not specifically limited.

[0114] In actual applications, the protocol conversion information can be stored either at the software service provider platform or at the target service provider, without specific limitation. If the second adaptation status information indicates that the target service provider has the protocol conversion information, the software service provider platform can directly send the first service acquisition request based on the standard interface protocol as the second service acquisition request to the target service provider. The target service provider needs to use the protocol conversion information to perform protocol conversion on the service request data generated based on the standard interface protocol in the second service acquisition request to obtain service request data based on the target interface protocol, thereby generating a request processing result for the service request data based on the target interface protocol.

[0115] For example, if the second service acquisition request includes the parameter "UID", the target service provider can determine the parameter value of "UID" in the second service acquisition request based on the direct correspondence between "UID" and "UserID" in the protocol conversion information to obtain the parameter value of "UserID" corresponding to the target interface protocol. Alternatively, if the parameter value of the parameter "unit price of goods" included in the second service acquisition request is 10, the target service provider can determine that the parameter value of the parameter "unit price of goods" corresponding to the target interface protocol is 100 based on the correspondence in the protocol conversion information that reflects that the value of the unit price of goods in the target interface protocol is 10 times the value of the unit price of goods in the standard interface protocol, which is convenient and quick.

[0116] In the embodiment of the present specification, since the target service provider can obtain the standard interface protocol from the software service provider platform after entering the software service provider platform, the target service provider can generate the protocol conversion information based on the obtained standard interface protocol and the target interface protocol it uses.

[0117] Based on this, if the second judgment result indicates that the target service provider has the protocol conversion information, before establishing the association relationship information between the software service and the unique identity information, the following may also be included:

[0118] The standard interface protocol is sent to the target service provider; the target service provider can be used to generate the protocol conversion information based on the standard interface protocol and the target interface protocol; the target interface protocol is the interface protocol required to be used by the application program providing the software service at the target service provider.

[0119] In the embodiments of the present specification, for the target service provider that has already written the application for providing software services before entering the software service provision platform, these application programs may not be generated based on the standard interface protocol. In this case, by allowing the target service provider to generate the protocol conversion information based on the standard interface protocol and the target interface protocol, the target service provider can process the service acquisition request generated by the Internet of Things device based on the standard interface protocol based on the protocol conversion information, without the need to specially build an application for providing software services that is consistent with the standard interface protocol, which is beneficial to reducing the cost of the target service provider when providing software services to Internet of Things devices based on different interface protocols.

[0120] In actual applications, in order to facilitate the target service provider to generate the protocol conversion information by itself, the software service providing platform can provide the target service provider with an application interface for generating the protocol conversion information. The application interface usually displays the name information and parameter introduction information of each parameter in the standard interface protocol, so as to facilitate the target service provider to parse the standard interface protocol. In addition, the application interface can also be provided with controls for filling in the parameters in the target interface protocol corresponding to the various parameters in the standard interface protocol, so that the target service provider can use these controls to conveniently establish the protocol conversion information.

[0121] In an embodiment of the present specification, the protocol conversion information can also be stored in the software service providing platform, so that the software service providing platform can convert the first service acquisition request based on the standard interface protocol into a second service acquisition request based on the target interface protocol based on the protocol conversion information, thereby simplifying the processing process of the target service provider for the second service acquisition request.

[0122] Based on this, the step of determining whether the target service provider has protocol conversion information between the target interface protocol and the standard interface protocol, after obtaining the second determination result, may further include:

[0123] If the second judgment result indicates that the target service provider does not have the protocol conversion information, third adaptation status information is generated to indicate that the target service provider does not have the protocol conversion information; the third adaptation status information can be used to reflect that the target interface protocol is inconsistent with the standard interface protocol.

[0124] Correspondingly, the step 204: in response to the first service acquisition request, generating a second service acquisition request that can be processed by the target service provider according to the adaptation information between the standard interface protocol and the target interface protocol, may specifically include:

[0125] A second service acquisition request based on the target interface protocol is generated according to the third adaptation situation information, the first service acquisition request and the pre-stored protocol conversion information; the second service acquisition request based on the target interface protocol carries target service request data, and the target service request data is data obtained by performing protocol conversion processing on the service request data in the first service acquisition request.

[0126] In an embodiment of the present specification, if the protocol conversion information is stored at the software service provider platform, third adaptation information can be generated to indicate that the protocol conversion information is pre-stored at the software service provider platform. Subsequently, if a first service acquisition request generated based on a standard interface protocol is received, the software service provider platform can be used to convert the first service acquisition request into a second service acquisition request based on the target interface protocol based on the protocol conversion information, so that the target service provider can process the second service acquisition request. It can be seen that at this time, the target service provider provides software services to IoT devices based on different interface protocols, and there is no need to specially build an application for providing software services that is consistent with the interface protocol, which is conducive to improving the versatility, convenience and implementation cost of the software services that can be provided by the target service provider.

[0127] In the embodiment of the present specification, the software service providing platform may also be used to generate the protocol conversion information. Based on this, if the second judgment result indicates that the target service provider does not have the protocol conversion information, before establishing the association relationship information between the software service and the unique identity information, the following may also be included:

[0128] The software service providing platform obtains the target interface protocol.

[0129] The protocol conversion information is generated based on the target interface protocol and the standard interface protocol.

[0130] The protocol conversion information is stored.

[0131] In the embodiments of this specification, the principles for the software service providing platform and the target service provider to generate the protocol conversion information may be the same, which will not be elaborated herein.

[0132] Figure 3 The embodiments of this specification provide corresponding to Figure 2 A swim lane flow diagram of the software service provision method in . Figure 3 As shown, the software service provision process may involve execution entities such as IoT devices, software service provision platforms, and target service providers.

[0133] During the platform entry phase, the software service provider platform obtains the identity authentication request of the target service provider; the identity authentication request carries the identity authentication information of the target service provider; in response to the identity authentication request, the identity authentication information is trusted for verification to obtain an identity authentication result; if the identity authentication result indicates that the identity authentication information is verified, the unique identity identification information assigned by the software service provider platform to the target service provider is sent to the target service provider; so that the target service provider can provide software services to the service demander based on the unique identity identification information. If the identity authentication result indicates that the identity authentication information is not verified, it can jump to the end.

[0134] In the service publishing stage, the software service providing platform obtains the software service publishing instruction of the target service provider; the software service publishing instruction can be used to instruct the software service to be published at the software service providing platform.

[0135] The software service providing platform determines whether the target interface protocol at the target service provider is consistent with the standard interface protocol provided by the software service providing platform, and obtains a first judgment result; wherein, the target interface protocol is the interface protocol required to be used by the target service provider in the process of providing the software service.

[0136] If the first judgment result indicates that the target interface protocol is consistent with the standard interface protocol, it means that the application of the software service is generated based on the standard interface protocol, and then the first adaptation status information is generated to reflect that the target interface protocol is consistent with the standard interface protocol.

[0137] If the first judgment result indicates that the target interface protocol is inconsistent with the standard interface protocol, it is determined whether the target service provider has protocol conversion information between the target interface protocol and the standard interface protocol to obtain a second judgment result.

[0138] If the second judgment result indicates that the target service provider has the protocol conversion information, then the second adaptation information is generated to indicate that the target service provider has the protocol conversion information. If the second judgment result indicates that the target service provider does not have the protocol conversion information, and the software service provider platform has the protocol conversion information, then the third adaptation information is generated to indicate that the target service provider does not have the protocol conversion information; in this case, the third adaptation information may also reflect the specific protocol conversion information at the software service provider platform.

[0139] In response to the software service publishing instruction, the software service providing platform may establish association relationship information between the software service and the unique identity information of the target service provider; the association relationship information may be used to indicate that the target service provider is the provider of the software service. Furthermore, the software service providing platform may also send the association relationship information between the software service and the unique identity information to the Internet of Things device; the Internet of Things device may be used to generate the first service acquisition request based on the association relationship information.

[0140] In the service provision stage, the IoT device can generate a first service acquisition request based on the standard interface protocol through the target application generated based on the standard interface protocol carried by it. The first service acquisition request usually carries the target unique identity information of the service provider that can be used to provide the software service.

[0141] After the software service providing platform obtains the first service acquisition request for the software service from the Internet of Things device, if the target unique identity information is consistent with the unique identity information of the target service provider, the software service providing platform determines the adaptation status information between the standard interface protocol and the target interface protocol at the target service provider in response to the first service acquisition request.

[0142] If the adaptation situation information is the first adaptation situation information, a second service acquisition request based on the standard interface protocol is generated according to the first adaptation situation information and the first service acquisition request.

[0143] If the adaptation situation information is the second adaptation situation information, a second service acquisition request based on the standard interface protocol is generated according to the second adaptation situation information and the first service acquisition request.

[0144] If the adaptation situation information is the third adaptation situation information, a second service acquisition request based on the target interface protocol is generated according to the third adaptation situation information, the first service acquisition request and the pre-stored protocol conversion information.

[0145] After the software service providing platform generates a second service acquisition request that can be processed by the target service provider according to the adaptation situation information, the second service acquisition request is sent to the target service provider. The target service provider generates a request processing result for the second service acquisition request, and feeds the request processing result back to the software service providing platform, so that the software service providing platform can send the request processing result to the Internet of Things device, thereby realizing software service interaction between the Internet of Things device and the target service provider.

[0146] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method. Figure 4 The embodiments of this specification provide corresponding to Figure 2 A structural diagram of a software service providing device. Figure 4 As shown, the device may include:

[0147] The first request acquisition module 402 may be used to acquire a first service acquisition request of the IoT device for a software service; the first service acquisition request is a request generated using a standard interface protocol provided by the software service providing platform.

[0148] The second request generation module 404 can be used to respond to the first service acquisition request and generate a second service acquisition request that can be processed by the target service provider based on the adaptation information between the standard interface protocol and the target interface protocol; the target interface protocol is the interface protocol required to be used by the target service provider in the process of providing the software service.

[0149] The result determination module 406 may be used to determine a request processing result generated by the target service provider for the second service acquisition request.

[0150] The result sending module 408 may be used to send the request processing result to the IoT device.

[0151] based on Figure 4 The present specification also provides some specific implementation schemes of the device, which are described below.

[0152] Optionally, the device may further include:

[0153] The authentication request acquisition module can be used to obtain the identity authentication request of the target service provider; the identity authentication request carries the identity authentication information of the target service provider.

[0154] The identity authentication module can be used to respond to the identity authentication request, perform trustworthy verification on the identity authentication information, and obtain an identity authentication result.

[0155] The identity identification sending module can be used to send the unique identity identification information allocated by the software service providing platform to the target service provider to the target service provider if the identity authentication result indicates that the identity authentication information verification is passed; the target service provider can be used to provide the software service to the service demander based on the unique identity identification information.

[0156] Optionally, the device may further include:

[0157] The publishing instruction acquisition module can be used to acquire the software service publishing instruction of the target service provider; the software service publishing instruction can be used to instruct the software service to be published at the software service providing platform.

[0158] The association relationship establishment module can be used to establish association relationship information between the software service and the unique identity information in response to the software service publishing instruction; the association relationship information can be used to indicate that the target service provider is the provider of the software service.

[0159] Optionally, the first service acquisition request carries target unique identity information of a service provider specified by the Internet of Things device that can be used to provide the software service.

[0160] Correspondingly, the second request generating module 404 may be specifically configured to generate a second service acquisition request processable by the target service provider if the target unique identity information is consistent with the unique identity information of the target service provider.

[0161] Optionally, the device may further include:

[0162] The interface protocol judgment module can be used to judge whether the target interface protocol is consistent with the standard interface protocol to obtain a first judgment result.

[0163] The first adaptation information generating module may be configured to generate first adaptation information reflecting that the target interface protocol is consistent with the standard interface protocol if the first judgment result indicates that the target interface protocol is consistent with the standard interface protocol.

[0164] Correspondingly, the second request generation module 404 can be specifically used to: generate a second service acquisition request based on the standard interface protocol according to the first adaptation situation information and the first service acquisition request; the second service acquisition request carries the service request data generated based on the standard interface protocol in the first service acquisition request.

[0165] Optionally, the device may further include:

[0166] The first protocol sending module may be used to send the standard interface protocol to the target service provider; the target service provider may be used to generate an application program that provides the software service based on the standard interface protocol.

[0167] Optionally, the device may further include:

[0168] The conversion information judgment module can be used to judge whether the target service provider has protocol conversion information between the target interface protocol and the standard interface protocol if the first judgment result indicates that the target interface protocol is inconsistent with the standard interface protocol, and obtain a second judgment result.

[0169] The second adaptation information generation module can be used to generate second adaptation status information that can be used to indicate that the target service provider has the protocol conversion information if the second judgment result indicates that the target service provider has the protocol conversion information; the second adaptation status information can be used to reflect that the target interface protocol is inconsistent with the standard interface protocol.

[0170] Correspondingly, the second request generating module 404 may be specifically used for:

[0171] A second service acquisition request based on the standard interface protocol is generated according to the second adaptation situation information and the first service acquisition request.

[0172] Optionally, the device may further include.

[0173] The second protocol sending module can be used to send the standard interface protocol to the target service provider; the target service provider can be used to generate the protocol conversion information based on the standard interface protocol and the target interface protocol; the target interface protocol is the interface protocol required to be used by the application program at the target service provider that provides the software service.

[0174] Optionally, the device may further include:

[0175] The third adaptation information generation module can be used to generate third adaptation status information that can be used to indicate that the target service provider does not have the protocol conversion information if the second judgment result indicates that the target service provider does not have the protocol conversion information; the third adaptation status information can be used to reflect that the target interface protocol is inconsistent with the standard interface protocol.

[0176] Correspondingly, the second request generating module 404 may be specifically used for:

[0177] A second service acquisition request based on the target interface protocol is generated according to the third adaptation situation information, the first service acquisition request and the pre-stored protocol conversion information; the second service acquisition request based on the target interface protocol carries target service request data, and the target service request data is data obtained by performing protocol conversion processing on the service request data in the first service acquisition request.

[0178] Optionally, the device may further include:

[0179] The conversion information generation module can be used to:

[0180] Obtain the target interface protocol.

[0181] The protocol conversion information is generated based on the target interface protocol and the standard interface protocol.

[0182] The protocol conversion information is stored.

[0183] Optionally, the device may further include:

[0184] The association relationship sending module can be used to send the association relationship information between the software service and the unique identity information to the Internet of Things device; the Internet of Things device can be used to generate the first service acquisition request based on the association relationship information.

[0185] Optionally, the device may further include:

[0186] The standard protocol sending module can be used to send the standard interface protocol to the device of the target application developer; the Internet of Things device carries the target application generated by the target application developer based on the standard interface protocol, so as to use the target application to generate the first service acquisition request.

[0187] Optionally, the standard interface protocol may include a service provider interface protocol; the software service providing platform has a program file generated based on the service provider interface protocol and used to request the component of the software service.

[0188] Correspondingly, the device may further include:

[0189] The program sending module can be used to send the program file of the component to the device of the target application developer; the Internet of Things device carries the target application generated by the target application developer based on the program file of the component, so as to generate the first service acquisition request by utilizing the component in the target application.

[0190] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method.

[0191] Figure 5 The embodiments of this specification provide corresponding to Figure 2 A schematic diagram of the structure of a software service providing device. Figure 5 As shown, the device 500 may include:

[0192] at least one processor 510; and,

[0193] A memory 530 in communication with the at least one processor; wherein,

[0194] The memory 530 stores instructions 520 executable by the at least one processor 510. The instructions are executed by the at least one processor 510 to enable the at least one processor 510 to:

[0195] A first service acquisition request for a software service from an Internet of Things device is obtained; the first service acquisition request is a request generated using a standard interface protocol provided by the software service providing platform.

[0196] In response to the first service acquisition request, a second service acquisition request that can be processed by the target service provider is generated based on the adaptation information between the standard interface protocol and the target interface protocol; the target interface protocol is the interface protocol required to be used by the target service provider in providing the software service.

[0197] Determine a request processing result generated by the target service provider for the second service acquisition request.

[0198] Send the request processing result to the IoT device.

[0199] Each embodiment in this specification is described in a progressive manner. The same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. Figure 5 As for the device shown, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0200] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented with "logic compiler" software, which is similar to the software compiler used when developing and writing programs. The original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also be aware that it is easy to obtain a hardware circuit that implements the logical method flow by simply performing some logic programming on the method flow using the above-mentioned hardware description languages ​​and programming it into an integrated circuit.

[0201] The controller can be implemented in any appropriate manner. For example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, AtmelAT91SAM, MicrochipPIC18F26K20, and SiliconeLabsC8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules for implementing the method and structures within the hardware component.

[0202] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0203] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0204] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0205] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0206] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0207] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0208] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0209] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0210] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0211] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0212] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0213] The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0214] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A method for providing software services, comprising: The software service providing platform obtains a first service acquisition request for the software service from the IoT device; The first service acquisition request is a request generated by using a standard interface protocol provided by the software service providing platform; In response to the first service acquisition request, a second service acquisition request that can be processed by the target service provider is generated according to the adaptation information between the standard interface protocol and the target interface protocol; the target interface protocol is an interface protocol required to be used in the process of the target service provider providing the software service; the adaptation information includes first adaptation information or second adaptation information, the first adaptation information is used to reflect that the standard interface protocol is consistent with the target interface protocol, and the second adaptation information is used to reflect that the target service provider has protocol conversion information between the standard interface protocol and the target interface protocol; Determine a request processing result generated by the target service provider for the second service acquisition request; Send the request processing result to the IoT device.

2. The method according to claim 1, before the software service providing platform obtains the first service acquisition request of the IoT device for the software service, further comprising: The software service providing platform obtains an identity authentication request from the target service provider; The identity authentication request carries the identity authentication information of the target service provider; In response to the identity authentication request, performing trustworthy verification on the identity authentication information to obtain an identity authentication result; If the identity authentication result indicates that the identity authentication information is verified successfully, sending the unique identity identification information allocated by the software service providing platform to the target service provider to the target service provider; The target service provider is used to provide the software service to the service demander based on the unique identity information.

3. The method according to claim 2, after sending the unique identity information assigned by the software service providing platform to the target service provider to the target service provider, further comprising: Obtaining a software service publishing instruction from the target service provider; The software service publishing instruction is used to instruct to publish the software service at the software service providing platform; In response to the software service publishing instruction, establishing association relationship information between the software service and the unique identity information; The association relationship information is used to indicate that the target service provider is the provider of the software service.

4. The method according to claim 3, wherein the first service acquisition request carries target unique identity information of a service provider specified by the IoT device for providing the software service; The generating a second service acquisition request that can be processed by the target service provider specifically includes: If the target unique identity information is consistent with the unique identity information of the target service provider, a second service acquisition request that can be processed by the target service provider is generated.

5. The method according to claim 3, before establishing the association relationship information between the software service and the unique identity information, further comprising: Determine whether the target interface protocol is consistent with the standard interface protocol to obtain a first determination result; If the first judgment result indicates that the target interface protocol is consistent with the standard interface protocol, generating first adaptation status information reflecting that the target interface protocol is consistent with the standard interface protocol; The step of generating, in response to the first service acquisition request, a second service acquisition request processable by a target service provider according to the adaptation information between the standard interface protocol and the target interface protocol specifically includes: Generate a second service acquisition request based on the standard interface protocol according to the first adaptation situation information and the first service acquisition request; The second service acquisition request carries the service request data in the first service acquisition request that is generated based on the standard interface protocol.

6. The method according to claim 5, if the first judgment result indicates that the target interface protocol is consistent with the standard interface protocol, before establishing the association relationship information between the software service and the unique identity information, the method further comprises: Sending the standard interface protocol to the target service provider; The target service provider is used to generate an application program that provides the software service based on the standard interface protocol.

7. The method according to claim 5, wherein after the step of determining whether the target interface protocol is consistent with the standard interface protocol and obtaining a first determination result, further comprises: If the first judgment result indicates that the target interface protocol is inconsistent with the standard interface protocol, then judging whether the target service provider has protocol conversion information between the target interface protocol and the standard interface protocol, and obtaining a second judgment result; If the second judgment result indicates that the target service provider has the protocol conversion information, then generating second adaptation information for indicating that the target service provider has the protocol conversion information; the second adaptation information is used to reflect that the target interface protocol is inconsistent with the standard interface protocol; The step of generating, in response to the first service acquisition request, a second service acquisition request processable by a target service provider according to the adaptation information between the standard interface protocol and the target interface protocol specifically includes: A second service acquisition request based on the standard interface protocol is generated according to the second adaptation situation information and the first service acquisition request.

8. The method according to claim 7, if the second judgment result indicates that the target service provider has the protocol conversion information, before establishing the association relationship information between the software service and the unique identity information, the method further comprises: Sending the standard interface protocol to the target service provider; The target service provider is used to generate the protocol conversion information based on the standard interface protocol and the target interface protocol; the target interface protocol is an interface protocol required to be used by an application program at the target service provider that provides the software service.

9. The method according to claim 7, wherein the step of determining whether the target service provider has protocol conversion information between the target interface protocol and the standard interface protocol, after obtaining a second determination result, further comprises: If the second judgment result indicates that the target service provider does not have the protocol conversion information, generating third adaptation information for indicating that the target service provider does not have the protocol conversion information; the third adaptation information is used to reflect that the target interface protocol is inconsistent with the standard interface protocol; The step of generating, in response to the first service acquisition request, a second service acquisition request processable by a target service provider according to the adaptation information between the standard interface protocol and the target interface protocol specifically includes: Generate a second service acquisition request based on the target interface protocol according to the third adaptation situation information, the first service acquisition request and the pre-stored protocol conversion information; The second service acquisition request based on the target interface protocol carries target service request data, and the target service request data is data obtained by performing protocol conversion processing on the service request data in the first service acquisition request.

10. The method according to claim 9, if the second judgment result indicates that the target service provider does not have the protocol conversion information, before establishing the association relationship information between the software service and the unique identity information, the method further comprises: Obtaining the target interface protocol; Generate the protocol conversion information based on the target interface protocol and the standard interface protocol; The protocol conversion information is stored.

11. The method according to claim 4, after establishing the association relationship information between the software service and the unique identity information, further comprising: Sending the association relationship information between the software service and the unique identity information to the Internet of Things device; The Internet of Things device is used to generate the first service acquisition request based on the association relationship information.

12. The method according to claim 11, before obtaining the first service acquisition request of the IoT device for the software service, further comprising: Sending the standard interface protocol to a device of a target application developer; The Internet of Things device carries the target application generated by the target application developer based on the standard interface protocol, so as to generate the first service acquisition request by using the target application.

13. The method according to claim 11, wherein the standard interface protocol comprises a service provider interface protocol; the software service providing platform has a program file generated based on the service provider interface protocol and used to request the component of the software service; Before obtaining the first service acquisition request of the Internet of Things device for the software service, the method further includes: Sending the program file of the component to a device of a target application developer; The IoT device carries a target application generated by the target application developer based on the program file of the component, so as to generate the first service acquisition request by utilizing the component in the target application.

14. A software service providing device, comprising: A first request acquisition module, used to acquire a first service acquisition request of the Internet of Things device for the software service; The first service acquisition request is a request generated by using a standard interface protocol provided by the software service providing platform; A second request generation module is used to generate, in response to the first service acquisition request, a second service acquisition request that can be processed by a target service provider according to the adaptation information between the standard interface protocol and the target interface protocol; the target interface protocol is an interface protocol required to be used in the process of the target service provider providing the software service; the adaptation information includes first adaptation information or second adaptation information, the first adaptation information is used to reflect that the standard interface protocol is consistent with the target interface protocol, and the second adaptation information is used to reflect that the target service provider has protocol conversion information between the standard interface protocol and the target interface protocol; A result determination module, used to determine a request processing result generated by the target service provider for the second service acquisition request; The result sending module is used to send the request processing result to the Internet of Things device.

15. The apparatus of claim 14, further comprising: An authentication request acquisition module, used to acquire an identity authentication request from the target service provider; The identity authentication request carries the identity authentication information of the target service provider; An identity authentication module, configured to respond to the identity authentication request, perform trustworthy verification on the identity authentication information, and obtain an identity authentication result; An identity identification sending module, configured to send the unique identity identification information allocated by the software service providing platform to the target service provider to the target service provider if the identity authentication result indicates that the identity authentication information has been verified; The target service provider is used to provide the software service to the service demander based on the unique identity information.

16. The apparatus of claim 15, further comprising: A publishing instruction acquisition module, used to acquire the software service publishing instruction of the target service provider; The software service publishing instruction is used to instruct to publish the software service at the software service providing platform; An association relationship establishing module, used to establish association relationship information between the software service and the unique identity information in response to the software service publishing instruction; The association relationship information is used to indicate that the target service provider is the provider of the software service.

17. The apparatus according to claim 16, wherein the first service acquisition request carries target unique identity information of a service provider specified by the IoT device for providing the software service; The second request generating module is specifically used for: If the target unique identity information is consistent with the unique identity information of the target service provider, a second service acquisition request that can be processed by the target service provider is generated.

18. The apparatus of claim 16, further comprising: An interface protocol judgment module, used to judge whether the target interface protocol is consistent with the standard interface protocol, and obtain a first judgment result; A first adaptation information generating module, configured to generate first adaptation information reflecting that the target interface protocol is consistent with the standard interface protocol if the first judgment result indicates that the target interface protocol is consistent with the standard interface protocol; The second request generating module is specifically used for: A second service acquisition request based on the standard interface protocol is generated according to the first adaptation situation information and the first service acquisition request; the second service acquisition request carries the service request data generated based on the standard interface protocol in the first service acquisition request.

19. The apparatus of claim 18, further comprising: a conversion information determination module, configured to determine whether the target service provider has protocol conversion information between the target interface protocol and the standard interface protocol if the first determination result indicates that the target interface protocol is inconsistent with the standard interface protocol, and obtain a second determination result; A second adaptation information generating module, configured to generate second adaptation information indicating that the target service provider has the protocol conversion information if the second judgment result indicates that the target service provider has the protocol conversion information; the second adaptation information is used to reflect that the target interface protocol is inconsistent with the standard interface protocol; The second request generating module is specifically used for: A second service acquisition request based on the standard interface protocol is generated according to the second adaptation situation information and the first service acquisition request.

20. The device of claim 19, further comprising: a third adaptation information generating module, configured to generate third adaptation information indicating that the target service provider does not have the protocol conversion information if the second judgment result indicates that the target service provider does not have the protocol conversion information; the third adaptation information is used to reflect that the target interface protocol is inconsistent with the standard interface protocol; The second request generating module is specifically used for: A second service acquisition request based on the target interface protocol is generated according to the third adaptation situation information, the first service acquisition request and the pre-stored protocol conversion information; the second service acquisition request based on the target interface protocol carries target service request data, and the target service request data is data obtained by performing protocol conversion processing on the service request data in the first service acquisition request.

21. The apparatus of claim 20, further comprising: The conversion information generation module is used to: Obtaining the target interface protocol; Generate the protocol conversion information based on the target interface protocol and the standard interface protocol; The protocol conversion information is stored.

22. The apparatus of claim 17, further comprising: An association relationship sending module, used for sending the association relationship information between the software service and the unique identity information to the Internet of Things device; The Internet of Things device is used to generate the first service acquisition request based on the association relationship information.

23. The apparatus of claim 22, further comprising: A standard protocol sending module, used for sending the standard interface protocol to the device of the target application developer; The Internet of Things device carries the target application generated by the target application developer based on the standard interface protocol, so as to generate the first service acquisition request by using the target application.

24. The device according to claim 22, wherein the standard interface protocol comprises a service provider interface protocol; the software service providing platform has a program file generated based on the service provider interface protocol and used to request to obtain the component of the software service; The device also includes: A program sending module, used for sending the program file of the component to the device of the target application developer; The IoT device carries a target application generated by the target application developer based on the program file of the component, so as to generate the first service acquisition request by utilizing the component in the target application.

25. A software service providing device, comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: Obtaining a first service acquisition request for a software service from an Internet of Things device; the first service acquisition request is a request generated using a standard interface protocol provided by the software service providing platform; In response to the first service acquisition request, a second service acquisition request that can be processed by the target service provider is generated according to the adaptation information between the standard interface protocol and the target interface protocol; the target interface protocol is an interface protocol required to be used in the process of the target service provider providing the software service; the adaptation information includes first adaptation information or second adaptation information, the first adaptation information is used to reflect that the standard interface protocol is consistent with the target interface protocol, and the second adaptation information is used to reflect that the target service provider has protocol conversion information between the standard interface protocol and the target interface protocol; Determine a request processing result generated by the target service provider for the second service acquisition request; Send the request processing result to the IoT device.

Images