CN115776515A

CN115776515A - Software service providing method, device and equipment

Info

Publication number: CN115776515A
Application number: CN202211429767.7A
Authority: CN
Inventors: 林文杰
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2022-11-15
Filing date: 2022-11-15
Publication date: 2023-03-10

Abstract

The embodiment of the specification discloses a software service providing method, a device and equipment. The scheme can comprise the following steps: after receiving a first service acquisition request generated by the internet of things device based on a standard interface protocol provided by the internet of things device, the software service providing platform can generate a second service acquisition request which can be processed by a target service provider according to adaptation condition information between the standard interface protocol and a target interface protocol required by the target service provider, so that the target service provider can process the second service acquisition request to generate a request processing result, and subsequently, the software service providing platform can feed back the request processing result generated by the target service provider to the internet of things device.

Description

Software service providing method, device and equipment

Technical Field

The present application relates to the field of software service technologies, and in particular, to a method, an apparatus, and a device for providing software service.

Background

SaaS is a short term for Software-as-a-service (Software-as-a-service), and is a new Software service providing mode that gradually rises with the development of internet technology and the maturity of application Software. The service provider can manage and maintain the application software in full right, and release the software service corresponding to the application software at the software service providing platform, and the service demander can acquire the software service provided by the service provider through the software service providing platform without maintaining the application software by the service demander, so that the method is convenient and rapid.

At present, because access standards of different software service providing platforms are usually inconsistent, only service providers and service demanders who reside in the same software service providing platform can interact with each other, thereby affecting the universality of software services provided by the service providers.

Therefore, how to improve the universality of software services provided by service providers becomes a technical problem to be solved urgently.

Disclosure of Invention

The software service providing method, device and equipment provided by the embodiment of the specification can improve the universality of software services provided by service providers.

In order to solve the above technical problem, the embodiments of the present specification are implemented as follows:

the software service providing method provided by the embodiment of the present specification may include:

the method comprises the steps that a software service providing platform obtains a first service obtaining request of the Internet of things equipment for software service; the first service acquisition request is a request generated using a standard interface protocol provided by the software service providing platform.

Responding to the first service acquisition request, and generating a second service acquisition request which can be processed by a target service provider according to the adaptation condition 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 providing the software service for the target service provider.

And determining a request processing result generated by the target service provider aiming at the second service acquisition request.

And sending the request processing result to the Internet of things equipment.

A software service providing apparatus provided in an embodiment of the present specification may include:

the first request acquisition module can be used for acquiring a first service acquisition request of the internet of things equipment for the software service; the first service acquisition request is a request generated using a standard interface protocol provided by the software service providing platform.

A second request generating module, configured 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 adaptation condition 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 providing the software service for the target service provider.

A result determination module, configured to determine a request processing result generated by the target service provider for the second service acquisition request.

The result sending module may be configured to send the request processing result to the internet of things device.

The software service providing device provided by the embodiments of the present specification may include:

at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to:

acquiring a first service acquisition request of the Internet of things equipment for the software service; the first service acquisition request is a request generated using a standard interface protocol provided by the software service providing platform.

And sending the request processing result to the Internet of things equipment.

At least one embodiment provided in this specification can achieve the following advantageous effects:

after receiving a first service acquisition request generated by the internet of things device based on a standard interface protocol provided by the internet of things device, the software service providing platform can generate a second service acquisition request which can be processed by a target service provider according to adaptation condition information between the standard interface protocol and a target interface protocol required by the target service provider, so that a request processing result generated by the target service provider processing the second service acquisition request is fed back to the internet of things device. Therefore, each service provider providing the software service based on various non-standard interface protocols can access the same software service providing platform and provide the software service for the service demander obtaining the service based on the standard interface protocols, and therefore the method and the device are beneficial to improving the universality of the software service provided by the service provider, expanding the selection range of the service demander for the software service provider and improving the experience of both parties.

Drawings

In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.

Fig. 1 is a schematic application scenario diagram of a software service providing method provided in an embodiment of this specification.

Fig. 2 is a flowchart illustrating a software service providing method according to an embodiment of the present disclosure.

Fig. 3 is a schematic swim lane flow chart corresponding to the software service providing method in fig. 2 according to an embodiment of the present disclosure.

Fig. 4 is a schematic structural diagram of a software service providing device corresponding to fig. 2 provided in an embodiment of the present disclosure.

Fig. 5 is a schematic structural diagram of a software service providing device corresponding to fig. 2 provided in an embodiment of this specification.

Detailed Description

To make the objects, technical solutions and advantages of one or more embodiments of the present disclosure more apparent, the technical solutions of one or more embodiments of the present disclosure will be described in detail and completely with reference to the specific embodiments of the present disclosure and the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present specification, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of one or more embodiments of the present specification.

The technical solutions provided by the embodiments of the present description are described in detail below with reference to the accompanying drawings.

In the prior art, with the development of internet technology and the maturity of application software, a service demander gradually starts to call software services provided by a service provider through a software service providing platform in the process of processing business so as to reduce the software management burden of the service demander. At present, interface protocols adopted by different software service providing platforms are usually inconsistent, and naming rules, data formats and the like for the same parameter in different interface protocols often have differences, so that if a service provider needs to provide software services to service demanders accessed at different software service providing platforms, a set of application programs for providing the software services needs to be respectively developed according to the interface protocols used at each software service providing platform, so that the application programs consistent with the interface protocols at the software service providing platforms are used for providing the software services to the service demanders residing in the software service providing platforms, and the application programs built based on other interface protocols cannot be used for providing the software services to the service demanders, thereby affecting the universality and convenience of the software services provided by the service provider.

In order to solve the defects in the prior art, the scheme provides the following embodiments:

fig. 1 is a schematic application scenario diagram of a software service providing method provided in an embodiment of the present specification.

As shown in fig. 1, a target service provider 103 may provide software services to an internet of things device 102 (i.e., a service demander) through a software service providing platform 101. Specifically, after the internet of things device 102 sends the first service acquisition request to the software service providing platform 101, the software service providing platform 101 may generate a second service acquisition request that can be processed by the target service provider 103 according to the respective interface protocols 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 may 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 may further receive a 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.

The scheme in fig. 1 enables the target service provider 103 to use an application program built based on any one interface protocol to provide software services to the internet of things device 102 at the software service providing platform 101, and does not need to specially build an application program for providing software services consistent with the interface protocols used by the software service providing platform 101 and the internet of things device 102, which is not only beneficial to improving the universality and convenience of the software services provided by the target service provider 103, but also beneficial to reducing the cost when the target service provider 103 provides software services to the internet of things device 102 based on different interface protocols.

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

fig. 2 is a flowchart illustrating a software service providing method according to an embodiment of the present disclosure. From a program perspective, the execution subject of the process may provide a platform for the software service, or an application program loaded on the platform for providing the software service. As shown in fig. 2, the process may include the following steps:

step 202: the method comprises the steps that a software service providing platform obtains a first service obtaining request of the Internet of things equipment for software service; the first service acquisition request is a request generated using a standard interface protocol provided by the software service providing platform.

In this embodiment, the software service providing platform may communicate with a service demander and a service provider for software service, respectively, so that the service provider may provide software service to the service demander, and thus, the software service providing platform may implement a function of providing software service through a network, which is possessed by the SaaS platform. The service demander may be internet of things (IOT) equipment, such as a cash register, a payment device, and the like, but is not limited thereto.

The first service acquisition request for the software service may be a request generated when the internet of things device needs to acquire the software service in the process of processing the service. In practical application, the software service providing platform can provide a standard interface protocol for the use of the internet of things equipment and the service provider, so that the standardization and the management convenience of the software service calling process are improved. Based on this, when the internet of things device can communicate with the software service providing platform to request to obtain the software service, it may generally indicate that the internet of things device has already loaded an application program capable of requesting to obtain the software service based on the standard interface protocol, so that the first service obtaining request may be a request generated by using the standard interface protocol provided by the software service providing platform, so that the software service providing platform can subsequently process the first service obtaining request.

In this embodiment, the standard interface protocol may be an interface protocol (interface protocol) customized by the software service providing platform, which may refer to a communication manner and a requirement to be complied with between interfaces that need to exchange information. In practical applications, the standard interface protocol may specify not only communication information of a physical layer, but also related requirements of a syntax layer and a semantic layer, which is not particularly limited.

In this embodiment of the present specification, the software service may refer to a SaaS service (software as a service) that needs to be invoked by an internet of things device, and in an actual application, a type of the software service generally relates to a service that needs to be processed by the internet of things device, for example, when the internet of things device is a payment device, the software service invoked by the internet of things device may be a SaaS service that processes a user order or a SaaS service that performs marketing on a commodity, and the like, which is not specifically limited.

Step 204: responding to the first service acquisition request, and generating a second service acquisition request which can be processed by a target service provider according to the adaptation condition 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 providing the software service for the target service provider.

In this embodiment of the specification, the target interface protocol may be an interface protocol that is required to be used in the process of providing the software service for the target service provider, for example, specifically, the interface protocol may be an interface protocol that is used when the target service provider builds an application program 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, which is not limited in particular.

The target service provider may generally be an independent software developer (ISV), and specifically, may be an enterprise dedicated to development, production, sale, and service of software; or the target service provider may also be an existing SaaS platform, and the SaaS platform may forward the second service acquisition request to an existing ISV for processing, so as to generate a request processing result generated for the second service acquisition request, which is not specifically limited.

In this embodiment, the adaptation condition information may be used to reflect whether the target interface protocol is consistent with the standard interface protocol, and when the target interface protocol is inconsistent with the standard interface protocol, the adaptation condition information may also be used to reflect whether the target service provider has protocol conversion information between the target interface protocol and the standard interface protocol. And the software service providing platform can generate a second service acquisition request which can be processed by the target service provider based on the adaptation condition information. In practical applications, the second service acquisition request may be generated based on the target interface protocol, or may also be generated based on the standard interface protocol, which is not specifically limited, and only needs to enable the target service provider to correctly parse and process the second service acquisition request based on the protocol conversion information that the target service provider can acquire and/or the application program used to provide the software service.

Step 206: and determining a request processing result generated by the target service provider aiming at the second service acquisition request.

In this embodiment, the request processing result may be generated by the target service provider processing the service request data through an application program providing the software service, based on the service request data carried in the second service acquisition request.

Specifically, the software service providing platform may issue a request for obtaining a request processing result, so as to obtain the request processing result from the target service provider. Alternatively, the target service provider may also agree in advance, and automatically feed back the request processing result to the software service providing platform after generating the request processing result, which is not particularly limited.

Step 208: and sending the request processing result to the Internet of things equipment.

In an embodiment of this specification, the software service providing platform further needs to feed back the request processing result to the internet of things device, so as to meet a software service acquisition requirement of the internet of things device. Specifically, since the internet of things device is based on the standard interface protocol to acquire the software service, in order to facilitate the internet of things device to analyze the request processing result, the software service providing platform may send the request processing result generated based on the standard interface protocol to the internet of things device. In practical applications, the request processing result generated based on the standard interface protocol may be generated by the target service provider itself, or may be generated by the software service providing platform performing protocol conversion on the request processing result fed back by the target service provider based on the protocol conversion information, which is not particularly limited.

In the method in fig. 2, after receiving a first service acquisition request generated by the internet of things device based on the standard interface protocol provided by the internet of things device, the software service providing platform may generate a second service acquisition request that can be processed by the target service provider according to the adaptation condition information between the standard interface protocol and the target interface protocol that is required by the target service provider, so as to feed back a request processing result generated by the target service provider for processing the second service acquisition request to the internet of things device. Therefore, each service provider providing the software service based on various non-standard interface protocols can access the same software service providing platform and provide the software service for the service demander obtaining the service based on the standard interface protocols, and therefore the method and the device are beneficial to improving the universality of the software service provided by the service provider, expanding the selection range of the service demander for the software service provider and improving the experience of both parties.

In addition, the target service provider can provide the software service to the internet of things equipment using the standard interface protocol by using the existing application program built based on the non-standard interface protocol, and does not need to specially build the application program for prompting the software service based on the standard interface protocol, so that the cost of providing the software service to the internet of things equipment based on different interface protocols by using the target service provider is reduced.

Based on the method in fig. 2, some specific embodiments of the method are also provided in the examples of the present specification, which are described below.

In the embodiment of the present specification, in order to ensure the security and the rights of the internet of things device in the process of acquiring the software service, generally, the identity authentication is performed on the target service provider in advance, and after the identity authentication is passed, the target service provider is allowed to enter the software service providing platform, so as to provide the software service for the internet of things device accessing the software service providing platform.

Based on this, the step 202: before the software service providing platform obtains the first service obtaining request of the internet of things device for the software service, the method may further include:

the software service providing platform acquires an identity authentication request of the target service provider; the identity authentication request carries identity authentication information of the target service provider.

And responding to the identity authentication request, and performing credible verification aiming at the identity authentication information to obtain an identity authentication result.

If the identity authentication result shows that the identity authentication information passes verification, unique identity identification information which is distributed by the software service providing platform aiming at the target service provider is sent to the target service provider; the target service provider may be configured to provide the software service to a service demander based on the unique identification information.

In this embodiment of the present specification, the identity authentication request may be a request generated by the target service provider when the target service provider hosts the software service providing platform, and the identity authentication request may carry identity authentication information for identifying an identity and a qualification of the target service provider. In practical applications, since the target service provider is usually a business or an organization, the identity authentication information may include information such as a business license of the target service provider, a value added telecommunication business license, a job title certificate of a professional technician, and the like. In addition, the identity authentication request may also carry service description information of the software service that the target service provider desires to provide, for example, type information of the software service, content information of the software service, and the like, so that the software service providing platform can more accurately process the identity authentication request based on the service description information.

In this embodiment, the identity authentication result may indicate whether the identity authentication information is verified. In practical application, if the identity authentication information of the target service provider meets qualification requirements and is real and effective, an identity authentication result indicating that the identity authentication information passes verification can be generated; and if the identity authentication information of the target service provider does not meet qualification requirements or is false information or failure information, generating an identity authentication result indicating that the identity authentication information fails to be verified. 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 is not verified can also be generated, so as to prevent the target service provider from providing the non-compliant software service to the internet of things device.

In this embodiment, if the identity authentication information is verified, the software service providing platform may generate unique identity information for uniquely identifying the target service provider. In practical applications, the unique ID information may be used as an ID (identity) of the target service provider, and the unique ID information may be information in a form of a character string.

In the embodiment of the specification, the target service provider after identity authentication is issued with the unique identity information, so that the target service provider can reside in the software service providing platform, and subsequently issue and provide software services to the internet of things equipment based on the unique identity information, so that the software service providing platform can manage the service provider and the software services provided by the service provider.

In this embodiment of the present specification, if the identity authentication result indicates that the authentication of the identity authentication information fails, the target service provider may further send information indicating that the authentication fails to the target service provider, and notify the reason that the authentication of the identity authentication information fails, so that the target service provider modifies the identity authentication information, and continues to try to log in the software service providing platform using the modified identity authentication information, which is beneficial to improving the experience of the target service provider.

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

Based on this, after the sending the unique identification information allocated by the software service providing platform for the target service provider to the target service provider, the method may further include:

acquiring a software service issuing instruction of the target service provider; the software service publishing instructions may be for instructing the software service to be published at the software service providing platform.

Responding to the software service issuing instruction, and establishing incidence relation information between the software service and the unique identity identification information; the incidence relation information may be used to indicate that the target service provider is the provider of the software service.

In this embodiment, after the target service provider builds an application program for providing the software service and other required resources, the target service provider may send a software service issuing instruction to the software service providing platform. In practical application, the software service issuing instruction may carry unique identification information obtained by the target service provider after identity authentication, so that the software service providing platform may identify, based on the association relationship information, that the target service provider may be used to provide the software service by establishing association relationship information between the unique identification information and the software service, and further, the internet of things device may invoke the target service provider to provide the software service.

In practical application, the same target service provider may have a need to publish a plurality of different software services, and therefore, to distinguish a specific software service at the target service provider called by a user, different service unique identification information may be allocated for different software services published by the target service provider, or different service calling interfaces may be configured for different software services at the internet of things device to distinguish. Based on this, the first service acquisition request in step 202 may carry the service unique identification information of the software service, or the first service acquisition request in step 202 may also be a request generated for a service call interface corresponding to the software service, which is convenient and fast.

In practical application, the software service issuing instruction may also carry service description information, service charging information, service invocation condition information, and the like for the software service, which is not limited specifically.

In this embodiment of the specification, since the software service providing platform may identify whether the target service provider is a provider of the software service by using the association relationship information between the unique identification information of the target service provider and the software service, based on this, the first service acquisition request sent by the internet of things device may carry the target unique identification information of the service provider, which is specified by the internet of things device and may be used to provide the software service, of the service provider. That is, the service provider with the target unique identification information is the service provider for which the internet of things device desires to provide software services.

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

and if the target unique identity information is consistent with the unique identity information of the target service provider, generating a second service acquisition request which can be processed by the target service provider.

In this embodiment of the present specification, based on target unique identity information carried in the first service acquisition request and association relationship information between the software service and the unique identity information, the target service provider to which the first service acquisition request is directed may be accurately determined, and then adaptation condition information between the standard interface protocol and a target interface protocol of the target service provider may be determined, so that a second service acquisition request that may be processed by the target service provider may be generated.

In this embodiment of the specification, since the first service acquisition request sent by the internet of things device may carry target unique identification information of a service provider that is specified by the first service acquisition request and can be used for providing a software service, before the internet of things device generates the first service acquisition request, the unique identification information of each service provider and association relationship information between software services that can be provided by the service provider need to be sent to the internet of things device, so that a user of the internet of things device can select the unique identification information.

Based on this, after the establishing the association relationship information between the software service and the unique identification information, the method may further include:

sending incidence relation information between the software service and the unique identity identification information to the Internet of things equipment; the internet of things device may be configured to generate the first service acquisition request based on the association relationship information.

In this embodiment of the present description, since the software service providing platform has a capability of communicating with the internet of things device, the software service providing platform may send association relationship information between the software service and the unique identification information of the service provider to the internet of things device by itself. Or, since an application program (i.e., a target application program, for example, a payment application, a shopping application, or the like) for acquiring a software service generally needs to be deployed at the device of the internet of things, based on this, the software service providing platform may also send, through the server of the target application program, association relationship information between the software service and unique identification information of the service provider to the device of the internet of things, which is not particularly limited.

In practical application, when a target application program carried by the internet of things device needs to acquire a software service, the target unique identification information carried in the first service acquisition request can be selected by the internet of things device based on manual operation or preset information and based on the association relationship information between the software service and the unique identification information of the service provider. The preset information may be target unique identification information of a service provider for providing the software service, which is preset by a manager of the internet of things device, so as to ensure the software service acquisition will of the user.

In practical applications, the target application program loaded at the internet of things device is usually generated based on a standard interface protocol at a software service providing platform. In practical applications, there are various ways for the target unique identification information to build a target application program based on the target unique identification information.

First, the target application can be written by the target application developer directly according to the standard interface protocol.

Specifically, before acquiring a first service acquisition request of the internet of things device for the software service, the method may further include:

sending the standard interface protocol to a device of a target application developer; the internet of things equipment loads a target application program 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 program.

In this embodiment of the specification, when a target application developer develops or updates a target application, the target application developer may obtain the standard interface protocol from the software service providing platform in advance, and write the part of the target application used for obtaining the software service based on the software service providing platform based on the standard interface protocol, so that when the generated target application runs at the internet of things device, a first service obtaining request based on the standard interface protocol may be generated.

In a second mode, the target application program can be generated by the target application program developer by using a component which is provided by the software service providing platform and is written based on the standard interface protocol.

Specifically, the standard interface protocol may include a service provider interface (SPI, acronym for short) protocol; the software service providing platform is provided with a program file which is generated based on the service providing program interface protocol and can be used for requesting to obtain the components of the software service.

Correspondingly, before the obtaining of the first service obtaining request of the internet of things device for the software service, the method may further include:

sending the program file of the component to the device of the target application developer; the IOT equipment generates the first service acquisition request by using the component in the target application program by carrying the target application program generated by the target application developer based on the program file of the component.

In this embodiment of the present specification, an affiliated mechanism of the software service providing platform may pre-build a component that is generated based on the service providing program interface protocol (i.e., standard interface protocol) and may be used to request to acquire the software service, and provide a program file of the above component for a target application developer to use through the software service providing platform. At this time, when the target application developer develops or updates the target application program, the application program for acquiring the software service based on the software service providing platform can be built by using the program file of the component, so that when the generated target application program runs at the internet of things device, the first service acquisition request based on the standard interface protocol can be generated based on the program file of the component included in the target application program, and the building process of the target application program is simplified.

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 API provided by Java and used for being realized or expanded by a third party, and the API can be used for enabling framework expansion and replacing components and has good flexibility.

In this embodiment of the present specification, before the software service is released, it is further necessary to determine adaptation condition information between a target interface protocol used by the target service provider when providing the software service and a 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 condition information.

Based on this, before the establishing the association relationship information between the software service and the unique identification information, the method may further include:

and judging whether the target interface protocol is consistent with the standard interface protocol or not to obtain a first judgment result.

And if the first judgment result shows that the target interface protocol is consistent with the standard interface protocol, generating first adaptation condition information which can be used for reflecting the consistency of the target interface protocol and the standard interface protocol.

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

generating a second service acquisition request based on the standard interface protocol according to the first adaptation condition information and the first service acquisition request; the second service acquisition request carries service request data generated based on the standard interface protocol in the first service acquisition request.

In this embodiment of the specification, if the first determination result indicates that a target interface protocol at a target service provider is consistent with a standard interface protocol, it may be indicated that an application program used by the target service provider for providing a software service is set up based on the standard interface protocol, and at this time, since the target service provider and the internet of things device perform service interaction based on the standard interface protocol, it is not necessary to generate protocol conversion information, and therefore, first adaptation condition information that reflects that the target interface protocol is consistent with the standard interface protocol may be generated.

Correspondingly, after receiving the first service acquisition request, if the first adaptation condition information reflects that the target interface protocol is consistent with the standard interface protocol, the application program that provides the software service 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 can process the first service acquisition request generated based on the standard interface protocol, at this time, the first service acquisition request may 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 may be extracted, and the second service acquisition request carrying the service request data is generated, which is not specifically limited.

The service request data in the first service acquisition request is input parameters that are generally required to be acquired when the target service provider provides software service, for example, when the software service is a marketing service for goods, the service request data may include goods information, marketing activity content information, and the like, and when the software service is a payment service for a purchase order for goods, the service request data may include goods unit price information, purchase quantity information, discount information on content of a preferential marketing activity, and the like, which is not particularly limited.

In the embodiment of the present specification, in order to facilitate the target service provider to generate an application program that provides a software service based on a standard interface protocol, the standard interface protocol needs to be provided to the target service provider before the target service provider builds the application program.

Specifically, if the first determination result indicates that the target interface protocol is consistent with the standard interface protocol, before the establishing of the association relationship information between the software service and the unique identification information, the method may further include:

sending the standard interface protocol to the target service provider; the target service provider may be operable to generate an application that provides the software service based on the standard interface protocol.

In this embodiment of the present specification, after the target service provider is hosted in the software service providing platform, the target service provider may obtain the standard interface protocol from the software service providing platform, and develop an application program for providing the software service based on the standard interface protocol, which is convenient and fast.

In practical application, because the target service provider often builds an application program for providing software service based on a non-standard interface protocol before entering the software service providing platform, a target interface protocol used by the target service provider is inconsistent with a standard interface protocol used by the internet of things device, and at this time, protocol conversion information may be created so that the target service provider can provide software service to the internet of things device based on the protocol conversion information.

Based on this, after the determining whether the target interface protocol is consistent with the standard interface protocol and obtaining a first determination result, the method may further include:

and if the first judgment result shows that the target interface protocol is inconsistent with the standard interface protocol, 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 shows that the target service provider has the protocol conversion information, generating second adaptation situation information which can be used for showing that the target service provider has the protocol conversion information; the second adaptation situation information may be used to reflect that the target interface protocol is not consistent with the standard interface protocol.

and generating a second service acquisition request based on the standard interface protocol according to the second adaptation condition information and the first service acquisition request.

In this embodiment, the protocol conversion information may be used to convert a request generated based on a standard interface protocol into a request generated based on a target interface protocol. Specifically, the protocol conversion information may describe a correspondence between parameters in the target interface protocol and the standard interface protocol, for example, a correspondence between a parameter name and a parameter data format. For example, assume that the username is noted as "UID" in the standard interface protocol and "UserID" in the target interface protocol; the protocol conversion information may include a correspondence between a "UID" in the standard interface protocol and a "UserID" in the target interface protocol. Alternatively, it is assumed that the numerical unit for the unit price of the commodity in the standard interface protocol is "element", and the numerical unit for the unit price of the commodity in the target interface protocol is "angle"; the protocol conversion information may include a corresponding relationship that the numerical units reflecting the unit prices of the commodities in the standard interface protocol and the target interface protocol are "element" and "angle", respectively, or the protocol conversion information may include a corresponding relationship that the numerical unit reflecting the unit price of the commodity in the target interface protocol is 10 times the numerical unit of the unit price of the commodity in the standard interface protocol, which is not limited specifically.

In practical applications, the protocol conversion information may be stored in the software service providing platform, or may be stored in the target service provider, which is not particularly limited. If the second adaptation condition information indicates that the target service provider has the protocol conversion information, the software service providing platform may 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 performs protocol conversion on the service request data generated based on the standard interface protocol in the second service acquisition request by using the protocol conversion information to obtain the service request data based on the target interface protocol, so as to generate a request processing result for the service request data based on the target interface protocol.

For example, if the second service acquisition request includes the parameter "UID", the target service provider may determine the parameter value of the "UID" in the second service acquisition request according to the direct correspondence between the "UID" and the "UserID" in the protocol conversion information, so as to obtain the parameter value of the "UserID" corresponding to the target interface protocol. Or, if the parameter value of the parameter "unit price of goods" included in the second service acquisition request is 10, the target service provider may determine that the parameter value of the parameter "unit price of goods" corresponding to the target interface protocol is 100 according to the correspondence that the value reflecting the unit price of goods in the target interface protocol in the protocol conversion information is 10 times the value of the unit price of goods in the standard interface protocol, which is convenient and fast.

In this embodiment, since the target service provider may obtain the standard interface protocol from the software service providing platform after entering the software service providing platform, the target service provider may generate the protocol conversion information based on the obtained standard interface protocol and the target interface protocol used by the target service provider.

Based on this, if the second determination result indicates that the target service provider has the protocol conversion information, before the establishing the association relationship information between the software service and the unique identification information, the method may further include:

sending the standard interface protocol to the target service provider; the target service provider may be configured 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 by an application program at the target service provider for providing the software service.

In this embodiment, for the target service provider, as far as the application programs for providing the software service are written before the target service provider is hosted in the software service providing platform, the application programs may not be generated based on the standard interface protocol, in this case, by enabling the target service provider to generate the protocol conversion information according to the standard interface protocol and the target interface protocol by itself, the target service provider may process, based on the protocol conversion information, the service acquisition request generated by the internet of things device based on the standard interface protocol, without specially building an application program for providing the software service in accordance with the standard interface protocol, which is beneficial to reducing the cost for the target service provider to provide the software service to the internet of things device based on different interface protocols.

In practical application, in order to facilitate a target service provider to generate the protocol conversion information by itself, the software service providing platform may provide an application interface for generating the protocol conversion information to the target service provider, where name information and parameter introduction information of each parameter in a standard interface protocol are usually displayed in the application interface, so that the target service provider can analyze the standard interface protocol conveniently, and in addition, the application interface may further be provided with controls for filling in parameters in the target interface protocol corresponding to each parameter in the standard interface protocol, so that the target service provider can conveniently establish the protocol conversion information by using the controls.

In this embodiment, the protocol conversion information may also be stored in the software service providing platform, so that the software service providing platform converts the first service obtaining request based on the standard interface protocol into the second service obtaining request based on the target interface protocol based on the protocol conversion information, thereby simplifying a processing procedure of the target service provider for the second service obtaining request.

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

if the second judgment result indicates that the target service provider does not have the protocol conversion information, generating third adaptation situation information which can be used for indicating that the target service provider does not have the protocol conversion information; the third adaptation situation information may be used to reflect that the target interface protocol is not consistent with the standard interface protocol.

generating a second service acquisition request based on the target interface protocol according to the third adaptation condition 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.

In this embodiment, if the protocol conversion information is stored in the software service providing platform, third adaptation situation information indicating that the protocol conversion information is stored in the software service providing platform in advance may be generated. Subsequently, if a first service acquisition request generated based on a standard interface protocol is received, the software service providing platform can be used for converting 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.

In the embodiment of the present specification, a software service providing platform may also be used to generate the protocol conversion information. Based on this, if the second determination result indicates that the target service provider does not have the protocol conversion information, before the establishing the association relationship information between the software service and the unique identification information, the method may further include:

and the software service providing platform acquires the target interface protocol.

Generating the protocol conversion information based on the target interface protocol and the standard interface protocol.

And storing the protocol conversion information.

In the embodiment of the present specification, the principle that the software service providing platform and the target service provider generate the protocol conversion information may be the same, and details thereof are not described herein.

FIG. 3 is a schematic swimlane flow chart corresponding to the software service providing method in FIG. 2 according to an embodiment of the present disclosure. As shown in fig. 3, the software service providing process may involve executing a subject by an internet of things device, a software service providing platform, a target service provider, and the like.

In the stage of platform entrance, the software service providing platform obtains the identity authentication request of the target service provider; the identity authentication request carries identity authentication information of the target service provider; responding to the identity authentication request, and performing trusted verification on the identity authentication information to obtain an identity authentication result; if the identity authentication result shows that the identity authentication information passes verification, unique identity identification information which is distributed by the software service providing platform aiming at the target service provider is sent to the target service provider; so that the target service provider provides software services to the service demander based on the unique identification information. And if the identity authentication result shows that the identity authentication information is not verified, the process can skip to the end.

In a service release stage, the software service providing platform obtains a software service release instruction of the target service provider; the software service publishing instructions may be for instructing the software service to be published at the software service providing platform.

The software service providing platform judges whether a target interface protocol at a target service provider is consistent with a standard interface protocol provided by the software service providing platform or not to obtain a first judgment result; the target interface protocol is an interface protocol required to be used in the process of providing the software service for the target service provider.

And if the first judgment result shows that the target interface protocol is consistent with the standard interface protocol, the application program of the software service is generated based on the standard interface protocol, and then first adaptation condition information which can be used for reflecting the consistency of the target interface protocol and the standard interface protocol is generated.

And if the second judgment result shows that the target service provider has the protocol conversion information, generating second adaptation situation information which can be used for showing 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 providing platform has the protocol conversion information, generating third adaptation condition information which can be used for indicating that the target service provider does not have the protocol conversion information; in this case, the third adaptation situation information may also reflect the specific protocol conversion information at the software service providing platform.

The software service providing platform responds to the software service issuing instruction and can establish incidence relation information between the software service and the unique identification information of the target service provider; the incidence relation information may be used to indicate that the target service provider is the provider of the software service. The software service providing platform can also send incidence relation information between the software service and the unique identity information to the Internet of things equipment; the internet of things device may be configured to generate the first service acquisition request based on the association relationship information.

In the service providing stage, the internet of things device may generate a first service acquisition request based on the standard interface protocol through a target application program generated based on the standard interface protocol and loaded by the internet of things device. The first service acquisition request typically carries target unique identification information of a service provider that can be used for providing the software service.

After the software service providing platform obtains a first service obtaining request of the internet of things equipment for software service, if the target unique identification information is consistent with the unique identification information of the target service provider, the software service providing platform responds to the first service obtaining request and determines adaptation condition information between the standard interface protocol and a target interface protocol at the target service provider.

And if the adaptation condition information is first adaptation condition information, generating a second service acquisition request based on the standard interface protocol according to the first adaptation condition information and the first service acquisition request.

And if the adaptation condition information is second adaptation condition information, generating a second service acquisition request based on the standard interface protocol according to the second adaptation condition information and the first service acquisition request.

And if the adaptation condition information is third adaptation condition information, generating a second service acquisition request based on the target interface protocol according to the third adaptation condition information, the first service acquisition request and the pre-stored protocol conversion information.

And after the software service providing platform generates a second service obtaining request which can be processed by a target service provider according to the adaptation condition information, the second service obtaining request is sent to the target service provider. And the target service provider generates a request processing result aiming at 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 equipment, and the software service interaction between the Internet of things equipment and the target service provider is realized.

Based on the same idea, the embodiment of the present specification further provides a device corresponding to the method. Fig. 4 is a schematic structural diagram of a software service providing device corresponding to fig. 2 provided in an embodiment of the present disclosure. As shown in fig. 4, the apparatus may include:

a first request obtaining module 402, configured to obtain a first service obtaining request for a software service by 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.

A second request generating module 404, configured 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 adaptation condition 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 providing the software service for the target service provider.

A result determination module 406, which may be configured to determine a request processing result generated by the target service provider for the second service acquisition request.

The result sending module 408 may be configured to send the request processing result to the internet of things device.

Based on the apparatus of fig. 4, some specific embodiments of the apparatus are also provided in the examples of the present specification, which are described below.

Optionally, the apparatus may further include:

the authentication request acquisition module can be used for acquiring the identity authentication request of the target service provider; the identity authentication request carries identity authentication information of the target service provider.

The identity authentication module may be configured to perform trusted authentication on the identity authentication information in response to the identity authentication request, so as to obtain an identity authentication result.

The identity identification sending module may be configured to send, to the target service provider, unique identity identification information allocated by the software service providing platform for the target service provider if the identity authentication result indicates that the identity authentication information passes verification; the target service provider may be configured to provide the software service to a service demander based on the unique identification information.

Optionally, the apparatus may further include:

the issuing instruction acquisition module can be used for acquiring a software service issuing instruction of the target service provider; the software service publishing instructions may be for instructing the software service to be published at the software service providing platform.

The incidence relation establishing module can be used for responding to the software service issuing instruction and establishing incidence relation information between the software service and the unique identity identification information; the incidence relation information may be used to indicate that the target service provider is the provider of the software service.

Optionally, the first service acquisition request carries target unique identity information of a service provider, which is specified by the internet of things device and can be used for providing the software service.

Correspondingly, the second request generating module 404 may be specifically configured to: and if the target unique identity information is consistent with the unique identity information of the target service provider, generating a second service acquisition request which can be processed by the target service provider.

Optionally, the apparatus may further include:

and the interface protocol judging module can be used for judging whether the target interface protocol is consistent with the standard interface protocol or not to obtain a first judgment result.

The first adaptation information generating module may be configured to generate first adaptation condition information for reflecting that the target interface protocol is consistent with the standard interface protocol, if the first determination result indicates that the target interface protocol is consistent with the standard interface protocol.

Correspondingly, the second request generating module 404 may be specifically configured to: generating a second service acquisition request based on the standard interface protocol according to the first adaptation condition information and the first service acquisition request; the second service acquisition request carries service request data generated based on the standard interface protocol in the first service acquisition request.

Optionally, the apparatus may further include:

a first protocol sending module, configured to send the standard interface protocol to the target service provider; the target service provider may be operable to generate an application that provides the software service based on the standard interface protocol.

Optionally, the apparatus may further include:

the conversion information determining module may be 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 situation information that may be used to indicate that the target service provider has the protocol conversion information if the second determination result indicates that the target service provider has the protocol conversion information; the second adaptation condition information may be used to reflect that the target interface protocol is inconsistent with the standard interface protocol.

Correspondingly, the second request generating module 404 may be specifically configured to:

Optionally, the apparatus may further comprise.

A second protocol sending module, configured to send the standard interface protocol to the target service provider; the target service provider may be configured 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 providing the software service at the target service provider.

Optionally, the apparatus may further include:

a third adaptation information generating module, configured to generate third adaptation situation information that may be used to indicate that the target service provider does not have the protocol conversion information if the second determination result indicates that the target service provider does not have the protocol conversion information; the third adaptation condition information may be used to reflect that the target interface protocol is inconsistent with the standard interface protocol.

generating a second service acquisition request based on the target interface protocol according to the third adaptation condition 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 obtained by performing protocol conversion processing on the service request data in the first service acquisition request.

Optionally, the apparatus may further include:

a conversion information generation module operable to:

and acquiring the target interface protocol.

And generating the protocol conversion information based on the target interface protocol and the standard interface protocol.

And storing the protocol conversion information.

Optionally, the apparatus may further include:

the incidence relation sending module can be used for sending incidence relation information between the software service and the unique identity information to the internet of things equipment; the internet of things device may be configured to generate the first service acquisition request based on the association relationship information.

Optionally, the apparatus may further include:

the standard protocol sending module can be used for sending the standard interface protocol to equipment of a target application developer; the internet of things device loads a target application program 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 program.

Optionally, the standard interface protocol may include a service provider interface protocol; the software service providing platform is provided with a program file which is generated based on the service providing program interface protocol and can be used for requesting to obtain the components of the software service.

Correspondingly, the apparatus may further include:

the program sending module can be used for sending the program file of the component to the equipment of a target application developer; the internet of things device loads a target application program 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 program.

Based on the same idea, the embodiment of the present specification further provides a device corresponding to the above method.

Fig. 5 is a schematic structural diagram of a software service providing device corresponding to fig. 2 provided in an embodiment of this specification. As shown in fig. 5, the apparatus 500 may include:

at least one processor 510; and (c) a second step of,

a memory 530 communicatively coupled to the at least one processor; wherein, the first and the second end of the pipe are connected with each other,

the memory 530 stores instructions 520 executable by the at least one processor 510 to cause the at least one processor 510 to:

And sending the request processing result to the Internet of things equipment.

All the embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, as for the apparatus shown in fig. 5, since it is substantially similar to the method embodiment, the description is relatively simple, and reference may be made to the partial description of the method embodiment for relevant points.

In the 90's of the 20 th century, improvements to a technology could clearly distinguish between improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements to process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose logic functions are determined by programming the device by a user. A digital character system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate a dedicated integrated circuit chip. Furthermore, today, instead of manually manufacturing integrated circuit chips, such programming is most often implemented using "logic compiler" software, which is similar to the software compiler used in program development, but the original code before compilation is written in a specific programming language, which is called Hardware Description Language (HDL), and HDL is not just one, but many, such as abll (advanced library expression language), AHDL (alternate language description language), fluorescence, CUPL (connected universal programming language), HDCal, java (java description language), language, HDL, laser, hardware description language (hardware description language), and vhh-language (hardware description language), which are currently used most commonly. It will also be apparent to those skilled in the art that hardware circuitry for implementing the logical method flows can be readily obtained by a mere need to program the method flows with some of the hardware description languages described above and into an integrated circuit.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium that stores computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC625D, atmel at91SAM, microchip pic18F26K20, and silicon labsc8051F320, the memory controller may also be implemented as part of the control logic of the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller in purely computer readable program code means, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be conceived to be both a software module implementing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, 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.

For convenience of description, the above devices are described as being divided into various units by function, respectively. Of course, the functionality of the various elements may be implemented in the same one or more pieces of software and/or hardware in the practice of the present application.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

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

The memory may include forms of volatile memory in a computer readable medium, random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both permanent and non-permanent, removable and non-removable media, may implement the information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 disc read only memory (CD-ROM), digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include transitory computer readable media (transmyedia) such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of other like elements in a process, method, article, or apparatus comprising the element.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.

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

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement or the like made within the spirit and principle of the present application shall be included in the scope of the claims of the present application.

Claims

1. A software service providing method, comprising:

the method comprises the steps that a software service providing platform obtains a first service obtaining request of the Internet of things equipment for software service; the first service acquisition request is a request generated by using a standard interface protocol provided by the software service providing platform;

responding to the first service acquisition request, and generating a second service acquisition request which can be processed by a target service provider according to the adaptation condition 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 providing the software service for the target service provider;

determining a request processing result generated by the target service provider aiming at the second service acquisition request;

and sending the request processing result to the Internet of things equipment.

2. The method of claim 1, wherein before the software service providing platform obtains the first service obtaining request of the internet of things device for the software service, the method further comprises:

the software service providing platform acquires an identity authentication request of the target service provider; the identity authentication request carries identity authentication information of the target service provider;

responding to the identity authentication request, and performing trusted verification on the identity authentication information to obtain an identity authentication result;

if the identity authentication result shows that the identity authentication information passes verification, unique identity identification information which is distributed by the software service providing platform aiming at the target service provider is sent to the target service provider; the target service provider is used for providing the software service to the service demander based on the unique identification information.

3. The method of claim 2, after sending the unique identification information assigned by the software service providing platform for the target service provider to the target service provider, further comprising:

acquiring a software service issuing instruction of the target service provider; the software service publishing instruction is used for instructing the software service to be published at the software service providing platform;

responding to the software service issuing instruction, and establishing incidence relation information between the software service and the unique identity identification information; and the incidence relation information is used for indicating 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 identification information of a service provider specified by the internet of things device and used for providing the software service;

the generating of the second service acquisition request that can be processed by the target service provider specifically includes:

5. The method of claim 3, prior to establishing the association information between the software service and the unique identification information, further comprising:

judging whether the target interface protocol is consistent with the standard interface protocol or not to obtain a first judgment result;

if the first judgment result shows that the target interface protocol is consistent with the standard interface protocol, generating first adaptation condition information for reflecting the consistency of the target interface protocol and the standard interface protocol;

the generating, in response to the first service acquisition request, a second service acquisition request that can be processed by a target service provider according to adaptation condition information between the standard interface protocol and the target interface protocol specifically includes:

6. The method according to claim 5, further comprising, before the establishing the association relationship information between the software service and the unique identification information, if the first determination result indicates that the target interface protocol is consistent with the standard interface protocol:

sending the standard interface protocol to the target service provider; the target service provider is configured to generate an application that provides the software service based on the standard interface protocol.

7. The method as claimed in claim 5, wherein said determining whether the target interface protocol is consistent with the standard interface protocol, and after obtaining the first determination result, further comprises:

if the first judgment result shows that the target interface protocol is inconsistent with the standard interface protocol, judging 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;

if the second judgment result indicates that the target service provider has the protocol conversion information, generating second adaptation condition information for indicating that the target service provider has the protocol conversion information; the second adaptation condition information is used for reflecting that the target interface protocol is inconsistent with the standard interface protocol;

8. The method of claim 7, wherein if the second determination result indicates that the protocol conversion information is available at the target service provider, before the establishing the association relationship information between the software service and the unique identification information, further comprising:

sending the standard interface protocol to the target service provider; the target service provider is used for generating 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 providing the software service at the target service provider.

9. The method of claim 7, said 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 comprising;

if the second judgment result shows that the target service provider does not have the protocol conversion information, generating third adaptation situation information for showing that the target service provider does not have the protocol conversion information; the third adaptation condition information is used for reflecting that the target interface protocol is inconsistent with the standard interface protocol;

10. The method of claim 9, wherein before the establishing the association relationship information between the software service and the unique identification information, if the second determination result indicates that the target service provider does not have the protocol conversion information, further comprises:

acquiring the target interface protocol;

generating the protocol conversion information based on the target interface protocol and the standard interface protocol;

and storing the protocol conversion information.

11. The method of claim 4, after establishing the association relationship information between the software service and the unique identification information, further comprising:

sending incidence relation information between the software service and the unique identity identification information to the Internet of things equipment; the internet of things equipment is used for generating the first service acquisition request based on the incidence relation information.

12. The method of claim 11, prior to obtaining the first service acquisition request for the software service by the internet of things device, further comprising:

sending the standard interface protocol to a device of a target application developer; the internet of things device loads a target application program 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 program.

13. The method of claim 11, the standard interface protocol comprising a service provider interface protocol; the software service providing platform is provided with a program file which is generated based on the service providing program interface protocol and used for requesting to obtain the components of the software service;

before the obtaining of the first service obtaining request of the internet of things device for the software service, the method further includes:

sending the program file of the component to the device of the target application developer; the internet of things device loads a target application program 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 program.

14. A software service providing apparatus comprising:

the first request acquisition module is used for acquiring a first service acquisition request of the Internet of things equipment 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 generating module, configured 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 adaptation condition 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 providing the software service for the target service provider;

a result determination module, configured to determine a request processing result generated by the target service provider for the second service acquisition request;

and the result sending module is used for sending the request processing result to the Internet of things equipment.

15. The apparatus of claim 14, the apparatus further comprising:

the authentication request acquisition module is used for acquiring the identity authentication request of the target service provider; the identity authentication request carries identity authentication information of the target service provider;

the identity authentication module is used for responding to the identity authentication request and performing credible authentication aiming at the identity authentication information to obtain an identity authentication result;

the identity identification sending module is used for sending the unique identity identification information which is distributed by the software service providing platform aiming at the target service provider to the target service provider if the identity authentication result shows that the identity authentication information passes the verification; the target service provider is used for providing the software service to the service demander based on the unique identification information.

16. The apparatus of claim 15, the apparatus further comprising:

the issuing instruction acquisition module is used for acquiring a software service issuing instruction of the target service provider; the software service publishing instruction is used for instructing the software service to be published at the software service providing platform;

the incidence relation establishing module is used for responding to the software service issuing instruction and establishing incidence relation information between the software service and the unique identity identification information; and the incidence relation information is used for indicating 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 identification information of a service provider specified by the internet of things device for providing the software service;

the second request generation module is specifically configured to:

and if the target unique identification information is consistent with the unique identification information of the target service provider, generating a second service acquisition request which can be processed by the target service provider.

18. The apparatus of claim 16, the apparatus further comprising:

the interface protocol judging module is used for judging whether the target interface protocol is consistent with the standard interface protocol or not to obtain a first judging result;

a first adaptation information generating module, configured to generate first adaptation condition information for reflecting that the target interface protocol is consistent with the standard interface protocol, if the first determination result indicates that the target interface protocol is consistent with the standard interface protocol;

the second request generating module is specifically configured to:

19. The apparatus of claim 18, the apparatus further comprising:

a conversion information determining 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 condition information indicating that the target service provider has the protocol conversion information if the second determination result indicates that the target service provider has the protocol conversion information; the second adaptation condition information is used for reflecting that the target interface protocol is inconsistent with the standard interface protocol;

the second request generation module is specifically configured to:

20. The apparatus of claim 19, further comprising;

a third adaptation information generating module, configured to generate third adaptation condition information indicating that the target service provider does not have the protocol conversion information if the second determination result indicates that the target service provider does not have the protocol conversion information; the third adaptation condition information is used for reflecting that the target interface protocol is inconsistent with the standard interface protocol;

the second request generation module is specifically configured to:

21. The apparatus of claim 20, the apparatus further comprising:

a conversion information generation module to:

acquiring the target interface protocol;

and storing the protocol conversion information.

22. The apparatus of claim 17, the apparatus further comprising:

the incidence relation sending module is used for sending incidence relation information between the software service and the unique identity information to the Internet of things equipment; the internet of things equipment is used for generating the first service acquisition request based on the incidence relation information.

23. The apparatus of claim 22, the apparatus further comprising:

the standard protocol sending module is used for sending the standard interface protocol to equipment of a target application developer; the internet of things device loads a target application program 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 program.

24. The apparatus of claim 22, the standard interface protocol comprising a service provider interface protocol; the software service providing platform is provided with a program file which is generated based on the service providing program interface protocol and used for requesting to obtain the components of the software service;

the device further comprises:

the program sending module is used for sending the program file of the component to the equipment of the target application developer; the IOT equipment generates the first service acquisition request by using the component in the target application program by carrying the target application program generated by the target application developer based on the program file of the component.

25. A software service providing apparatus comprising:

at least one processor; and the number of the first and second groups,

a memory communicatively coupled to the at least one processor; wherein, the first and the second end of the pipe are connected with each other,

the memory stores instructions executable by the at least one processor to enable the at least one processor to:

acquiring a first service acquisition request of the Internet of things equipment for the software service; the first service acquisition request is a request generated by utilizing a standard interface protocol provided by the software service providing platform;

and sending the request processing result to the Internet of things equipment.