Service integration platform system and method for internet services

• US 20090328181A1
• Filed: 06/22/2009
• Published: 12/31/2009
• Est. Priority Date: 06/26/2008
• Status: Active Grant

• Current Assignee: Alibaba Group Holding Ltd.
• Original Assignee: Alibaba Group Holding Ltd.
• Inventors: Liang, Yueping, Chen, Tingjia, Ye, Wei, Zeng, Yi, Wang, Lin, Zhao, Jin, Zheng, Seshu, Cen, Wenchu
• Granted Patent: US 8,533,799 B2
• Time in Patent Office: Days
• US Class Current: 726/9
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04M 15/49 Connection to several service providers
• CPC Class Codes: H04M 15/51 for resellers, retailers or service providers

Abstract

A service integration platform system includes an interface configured to receive a service request initiated by an Independent Software Vendor (ISV) and one or more processors configured to authenticate the service request and in the event that the service request is authenticated, route the service request to an Internet Service Provider (ISP) providing the service to be further processed. The service request is routed to a deployment environment provided by the ISP in the event that the service request is received on a deployment Universal Resource Identifier (URI) corresponding to the deployment environment; the service request is routed to a test environment provided by the ISP in the event that the service request is received on a test URI corresponding to the test environment.

Claims

1. A service integration platform system comprising:

an interface configured to receive a service request initiated by an Independent Software Vendor (ISV);

one or more processors configured to;

authenticate the service request;

in the event that the service request is authenticated, route the service request to an Internet Service Provider (ISP) providing the service to be further processed;

wherein;

the service request is routed to a deployment environment provided by the ISP in the event that the service request is received on a deployment Universal Resource Identifier (URI) corresponding to the deployment environment; and

the service request is routed to a test environment provided by the ISP in the event that the service request is received on a test URI corresponding to the test environment.

2. The system of claim 1, wherein authenticating includes one or more of the following:

whether a parameter of the ISV initiating the service request is legitimate, whether the service is present, whether a signature is needed, whether authority is possessed, whether the signature is valid, whether a timestamp is overdue and whether a token is valid.

3. The system of claim 1, wherein one or more processors are further configured to:

determine that a service requested by the ISV initiating the service requires login to the ISP;

initiate a login request to the ISP;

generate a token according to the processing of the ISP; and

forward the service request of the ISV to the ISP.

4. The system of claim 1, wherein the one or more processors are further configured to record a log of the work associated with authenticating and routing.

5. The system of claim 4, wherein the one or more processors are further configured to analyze the log.

6. The system of claim 5, wherein the one or more processors are further configured to monitor system access according to the analysis of the log.

7. The system of claim 5, wherein the one or more processors are further configured to account for payment according to the analysis of the log.

8. The system of claim 1, wherein the one or more processors are further configured to link a Sand Box provided the ISP to a test service of the ISV.

9. The system of claim 1, wherein the one or more processors are further configured to test a system debugging procedure in the event that the service request is routed to the test environment.

10. The system of claim 9, wherein the one or more processors are further configured to authenticate the service request initiated by the ISV according to the test result of the system debugging procedure.

11. The system of claim 1, wherein the one or more processors are further configured to test an application interface in the event that the service request is routed to the test environment.

12. The system of claim 1, wherein the one or more processors are further configured to obtain an application interface testing address and a service address of each ISP and route the service request to the application interface testing address in the event that the service request is received on the test URI.

13. The system of claim 1, wherein the one or more processors are further configured to provide service descriptive documents of each ISP to at least one ISV.

14. A method for providing Internet services comprising:

receiving a service request initiated by an Independent Software Vendor (ISV);

authenticating the service request;

in the event that the service request is authenticated, routing the service request to an Internet Service Provider (ISP) providing the service to be further processed;

wherein;

the service request is routed to a deployment environment provided by the ISP in the event that the service request is received on a deployment Universal Resource Identifier (URI) corresponding to the deployment environment; and

the service request is routed to a test environment provided by the ISP in the event that the service request is received on a test URI corresponding to the test environment.

15. The method of claim 14, wherein authenticating includes one or more of the following:

whether a parameter of the ISV initiating the service request is legitimate, whether the service is present, whether a signature is needed, whether authority is possessed, whether the signature is valid, whether a timestamp is overdue and whether a token is valid.

16. The method of claim 14, further comprising:

determining that a service requested by the ISV initiating the service requires login to the ISP;

initiating a login request to the ISP;

generating a token according to the processing of the ISP; and

forwarding the service request of the ISV to the ISP.

17. The method of claim 16, further comprising recording a log associated with authenticating and routing.

18. The method of claim 17, further comprising analyzing the log.

19. The method of claim 18, further comprising monitoring system access according to the analysis of the log.

20. The method of claim 18, further comprising accounting for payment according to the analysis of the log.

21. The method of claim 14, further comprising linking a Sand Boxes provided the ISP to a test service of the ISV.

22. The method of claim 14, further comprising triggering testing of a system debugging procedure in the event that the service request is routed to the test environment.

23. The system of claim 22, further comprising authenticating the service request initiated by the ISV according to the test result of the system debugging procedure.

24. The method of claim 14, further comprising testing an application interface in the event that the service request is routed to the test environment.

25. The method of claim 14, further comprising obtaining an application interface testing address and a service address of each ISP and route the service request to the application interface testing address in the event that the service request is received on the test URI.

26. The method of claim 14, further comprising providing service descriptive documents of each ISP to at least one ISV.

27. A service integration platform system comprising:

an interface configured to receive a service request initiated by an Independent Software Vendor (ISV);

an authentication module configured to authenticate the service request;

a routing module configured to route the service request to an Internet Service Provider (ISP) providing the service to be further processed in the event that the service request is authenticated;

wherein;

the service request is routed to a deployment environment provided by the ISP in the event that the service request is received on a deployment Universal Resource Identifier (URI) corresponding to the deployment environment; and

the service request is routed to a tes environment provided by the ISP in the event that the service request is received on a test URI corresponding to the test environment.