Abstract: The embodiments of the present invention provide a method of establishing IP security tunnel, server and client, the method comprising: receiving a CA certificate, a local certificate and address information from a client; wherein the CA certificate includes one or more security association proposal; establishing the IP security runnel with the client according to the CA certificate, the local certificate and the address information. Through the embodiments of the present invention, IP security tunnel will be established using certificate, while the size of IPSEC configuration will be reduced and this solution is interoperable.
FIELD OF THE INVENTION
This application relates to IP Security (IPSEC) processing and in particular, to a method of establishing IP security tunnel, server and client.
BACKGROUND
IPSEC (Internet Protocol Security) is a set of protocols defined by IETF (the Internet Engineering Taskforce). IPSEC provides a security mechanism for IP and certain upper layer protocols such as UDP (User Datagram Protocol) and TCP (Transmission Control Protocol). IPSEC protects IP packets (or more specifically IPSEC packets) and upper layer protocols during transmission between peer nodes by introducing proof of origin and encryption.
One of the IPSEC protocols is known as "Encapsulating Security Payload" (ESP) and ESP provides confidentiality, data integrity, and data source authentication of IP packets. This requires the insertion of an ESP header after the IP header of an IP packet but in front of the data to be protected. An ESP trailer is inserted after the data to be protected. An ESP packet is identified in the protocol field of the IP header. An alternative protocol to ESP is known as "Authentication Header" (AH).
In order to allow IPSEC packets to be properly encapsulated and decapsulated, associate security services/a key with the traffic to be protected, a construct named as a "Security Association" (SA) is adopted. An SA is negotiated between network entities using a mechanism known as "Internet Key Exchange" (IKE). The SA is allocated an identifier known as a "Security Parameter Index" (SPI). The appropriate SA is identified to the receiving node by including the corresponding SPI in an ESP header or an AH header.
On the other hand, IPSEC is being used for secure communication between two IP devices connected via an un-secure network. IPSEC VPN (Virtual Private Network) clients are being used for secure communication for end users to their corporate network. But for IPSEC, it is difficult to manage configuration by end users to establish IPSEC tunnel which involved lots of configurations, as the configurations also need to match with gateway side.
Now, as known in one solution, all possible configurations are sent to a server, and the server selects one set of the configurations to install.
However, this wastes bandwidth resource and needs lots of processing of pay loads. In order to establish one secure tunnel, many IPSEC configurations need to be archieved. Also this solution is not interoperable as it is a private solution.
SUMMARY
Embodiments of the present invention pertain to a method of establishing IP security tunnel. The aim is to reduce the size of IPSEC configuration and establish IPSEC tunnel by using the minimum cost.
According to a first aspect of the embodiments of the present invention, a method of establishing IP security tunnel, includes: receiving a CA certificate, a local certificate and address information from a client; wherein the CA certificate includes one or more security association proposal;
establishing the IP security tunnel with the client according to the CA certificate, the local certificate and the address information.
According to a second aspect of the embodiments of the present invention, a method of establishing IP security tunnel, includes:
sending a CA certificate, a local certificate and address information to a server; wherein the CA certificate includes one or more security association proposal.
According to a third aspect of the embodiments of the present invention, a server includes:
a receiving device, configured to receive a CA certificate, a local certificate and address information from a client; wherein the CA certificate includes one or more security association proposal;
an establishing device, configured to establish the IP security tunnel with the client according to the CA certificate, the local certificate and the address information.
According to a fourth aspect of the embodiments of the present invention, a client includes:
a sending device, configured to send a CA certificate, a local certificate and address information to a server; wherein the CA certificate includes one or more security association proposal.
According to a fifth aspect of the embodiments of the present invention, there is provided a computer-readable program, wherein when the program is executed in a server, the program enables the computer to carry out the method as above in the server.
According to a sixth aspect of the embodiments of the present invention, there is provided a storage medium in which a computer-readable program is stored, wherein the computer-readable program enables the computer to
carry out the method as above in the server.
According to a seventh aspect of the embodiments of the present invention, there is provided a computer-readable program, wherein when the program is executed in a client, the program enables the computer to carry out the method as above in the client.
According to a eighth aspect of the embodiments of the present invention, there is provided a storage medium in which a computer-readable program is stored, wherein the computer-readable program enables the computer to carry out the method as above in the client.
The advantages of the present invention exist in that IP security tunnel will be established using certificate, while the size of IPSEC configuration will be reduced and this solution is interoperable.
These and further aspects and features of the present invention will be apparent with reference to the following description and attached drawings. In the description and drawings, particular embodiments of the invention have been descibed in detail as being indicative of some of the ways in which the principles of the invention may be employed, but it is understood that the invention is not limited correspondingly in scope. Rather, the invention includes all changes, modifications and equivalents coming within the spirit and terms of the appended claims.
Features that are described and/or illustrated with respect to one embodiment may be used in the same way or in a similar way in one or more other embodiments and/or in combination with or instead of the features of the other embodiments.
It should be emphasized that the term "comprises/comprising" when used in this specification is taken to specify the presence of stated features, integers, steps or components but does not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof.
Many aspects of the invention can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. To facilitate illustrating and describing some parts of the invention, corresponding portions of the drawings may be exaggerated in size, e.g., made larger in relation to other parts than in an exemplary device actually made according to the invention. Elements and features depicted in one drawing or embodiment of the invention may be combined with elements and features depicted in one or more additional drawings or embodiments. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views and may be used to designate like or similar parts in more than one embodiment.
BRIEF DESCRIPTION OF THE DRAWING
The drawings are included to provide further understanding of the present invention, which constitute a part of the specification and illustrate the preferred embodiments of the present invention, and are used for setting forth the principles of the present invention together with the description. The same element is represented with the same reference number throughout the drawings.
In the drawings:
Figure 1 is a topology diagram showing IPSEC processing in one scenario.
Figure 2 is a flowchart of the method in an embodiment of the present invention.
Figure 3 is a schematic diagram of the proposal in an embodiment of the present invention.
Figure 4 is another flowchart of the method in an embodiment of the present invention.
Figure 5 is a schematic diagram of the server in an embodiment of the present invention.
Figure 6 is a schematic diagram of the client in an embodiment of the present invention.
DETAILED DESCRIPTION
The many features and advantages of the embodiments are apparent from the detailed specification and, thus, it is intended by the appended claims to cover all such features and advantages of the embodiments that fall within the true spirit and scope thereof. Further, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the inventive embodiments to the exact construction and operation illustrated and described, and accordingly all suitable modifications and equivalents may be resorted to, falling within the scope thereof.
In the present application, embodiments of the invention are described primarily in the context of IPSEC. However, it shall be appreciated that the invention is not limited to the context of IPSEC, and may relate to any type of appropriate electronic apparatus having the function of IPSEC.
Figure 1' is a topology diagram showing IPSEC processing in one scenario. As shown in Fig.l, many nodes outside Head Office communicate with the nodes in Head Office through IPsec-Tunnel. The nodes outside Head Office include Branch office, Home user Easy-vpn, Mobile user-Easy VPN, Franchises/Partner, etc. It is assumed that all nodes in this Figure support IPSEC/IKE with CERT (Certificate) based on an authentication method (such as RSA-Signature, DSS- signature).
As shown in Fig.l, there is one or more common CA (Certificate Authority) server in Head Office, and all nodes outside Head Office have common trust point. The common CA server assigns device certificates to all the nodes, and CA certificate is installed into all the devices, and device local CERT is installed.
The preferred embodiments of the present invention are described as follows in reference to the drawings.
The embodiments of the present invention provide a method of establishing IPSEC tunnel. Figure 2 is a flowchart of the method in an embodiment of the present invention. As shown in Figure 2, in server side, the method including:
201, the server receives a CA certificate, a local certificate and address information from a client; wherein the CA certificate includes one or more security association proposal;
202, the server establishes the IP security tunnel with the client according to the CA certificate, the local certificate and the address information.
In the embodiements of the present invention, the security association proposal may be stored in the CA certificate in extension format, and is represented by 32 bit. The security association proposal may be IPSEC proposal or IKE proposal.
In an embodiment of the present invention, the security association proposal is IKE proposal. The IKE proposal may be stored in CA Certificate private Extension fields, and more than one IKE proposal can be stored in CA cert extensions.
In this embodiment, IKE proposal information is stored in a 32 bit encoded format to save space in cert. Figure 3 is a schematic diagram of the proposal in an embodiment of the present invention.
As shown in Fig.3, there is "protocol" field, and it is 2 bit. Table 1 illustrates the content of the protocol field as an example.
Table 1
As shown in Fig.3, there is "DH" field, and it is 6 bit. Table 2 illustrates the content of the DH field as an example.
Table 2
As shown in Fig.3, there is "INTEG" field, and it is 4 bit. Table 3 illustrates the content of the INTEG field as an example.
Table 3
As shown in Fig.3, there is "PRF" field, and it is 4 bit. Table 4 illustrates the content of the PRF field as an example.
Table 4
As shown in Fig.3, there is "ENCR" field, and it is 8 bit. Table 5 illustrates the content of the ENCR field as an example.
Table 5
In this embodiment, The IKE proposal may be stored in CA Certificate private Extension fields as follows:
Where numOfProposal will specify how many IKE Proposals exist, ikeProposals will be a set on Integer, each set will represent on an IKE proposal in encoded format as specified in Fig.3. In another embodiment of the present invention, the security association proposal is IPSEC proposal. The IPSEC proposal may be stored in CA Certificate private Extension fields, and more than one IPSEC proposal can be stored in CA cert extensions.
In this embodiment, IPSEC proposal information is stored in a 32 bit encoded format to save space in cert, the structure of the IPSEC proposal may be the same as the structure shown in Fig. 3, which shall not be described any further.
In this embodiment, The IPSEC proposal may be stored in CA Certificate private Extension fields as follows:
Where numOfProposal will specify how many IPSEC Proposals exist, ikeProposals will be a set on Integer, each set will represent on an IPSEC proposal in encoded format as specified in Fig.3.
In an embodiment of the present invention, the address information includes a peer IP address or a domain name.
And the method further includes: the server resolves the domain name so as to get IP address if the address information includes a domain name.
In an embodiment of the present invention, the method further includes: the server retrieves the security association proposal from the CA certificate, and retrieves local ID from the local certificate.
In an embodiment of the present invention, IPSEC ISAKMP Policy will be used with Mode-configuration to get
Internal IP Address from Server, and no traffic selector is needed.
In another embodiment of the present invention, if Traffic selector information is needed, it can be stored in CA Cert extension, IPSEC will retrieve Traffic selector from CA Cert.
Specifically, in this embodiment, the CA certificate further includes traffic selector information; and the method further includes: the server retrieves the traffic selector information from the CA certificate.
In 202, the server establishes the IP security tunnel with the client. Specifically, the server may establish the IP security tunnel through loaded CA cert, local cert and Peer address; alternatively, the server may establish the IP security tunnel through loaded CA cert, local cert and domain name. Furthermore, other configurations may be required in 202, and please refer to the prior art, which shall not be described any further.
Table 6 illustrates the comparision result between the present invention and the normal method as an example.
Table 6
As shown in Table 6, host (client) will be able to established IPSEC tunnel with gateway (server) using the minimum configuration, the host only need to have CA cert, local cert, and Gateway address to establish IPSEC Tunnel with Gateway.
The embodiments of the present invention further provide a method of establishing IPSEC tunnel. "Figure 4 is
another flowchart of the method in an embodiment of the present invention. As shown in Figure 4, in client side, the method includes: 401, the client sends a CA certificate, a local certificate and address information to a server; wherein the CA certificate includes one or more security association proposal.
In the present invention, the security association proposal may be stored in the CA certificate in extension format, and the security association proposal may be represented by 32 bit.
In the present invention, the security association proposal is IPSEC proposal or IKE proposal.
In the present invention, the address information includes a peer IP address or domain name.
It can be seen from the above embodiments that IP security tunnel will be established using certificate, while the size of IPSEC configuration will be reduced and this solution is interoperable.
The embodiments of the present invention further provide a server. Figure 5 is a schematic diagram of the server in an embodiment of the present invention.
As shown in Fig.5, the server includes a receiving device 501 and an establishing device 502.
Where the receiving device 501 is configured to receive a CA certificate, a local certificate and address information from a client; wherein the CA certificate includes one or more security association proposal.
The establishing device 502 is configured to establish the IP security tunnel with the client according to the CA certificate, the local certificate and the address information.
In the embodiments of the present invention, the security association proposal is stored in the CA certificate in extension format, and is represented by 32 bit.
In the embodiments of the present invention, the security association proposal is IPSEC proposal or IKE proposal.
In the embodiments of the present invention, the address information includes a peer IP address or a domain name.
In an embodiment of the present invention, wherein the server further includes: a retrieving device, the retrieving device is configured to retrieve the security association proposal from the CA certificate, and retrieve local ID from the local certificate.
In this embodiment, furthermore, the C A certificate may further include traffic selector information; and the retrieving device is further used to retrieve the traffic selector information from the CA certificate.
In an embodiment of the present invention, the server may further include a resolving device. The resolving device is configured to resolve the domain name so as to get IP address if the address information includes a domain name.
The embodiments of the present invention may further provide a client. Figure 6 is a schematic diagram of the client in an embodiment of the present invention.
As shown in Fig.6, the client may include a sending device 601. The sending device 601 is configured to send a CA certificate, a local certificate and address information to a server; wherein the CA certificate includes one or more security association proposal.
In the embodiments of the present invention, the security association proposal is stored in the CA certificate in extension format, and is represented by 32 bit.
In the embodiments of the present invention, the security association proposal is IPSEC proposal or IKE proposal.
In the embodiments of the present invention, the address information includes a peer IP address or domain name.
It can be seen from the above embodiments that IP security tunnel will be established using certificate, while the size of IPSEC configuration will be reduced and this solution is interoperable.
The embodiments of the present invention further provide a computer- readable program, wherein when the program is executed in a server; the program enables the computer to carry out the method of establishing IP security tunnel.
The embodiments of the present invention further provide a storage medium in which a computer-readable program is stored in a server, wherein the computer-readable program enables the computer to carry out the method of establishing IP security tunnel.
The embodiments of the present invention further provide a computer- readable program, wherein when the program is executed in a client; the program enables the computer to carry out the method of establishing IP security tunnel.
The embodiments of the present invention further provide a storage medium in which a computer-readable program is stored in a client, wherein the computer-readable program enables the computer to carry out the method of establishing IP security tunnel.
It should be understood that each of the parts of the present invention may be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods may be realized by software or firmware that is stored in the memory and executed by an appropriate instruction executing system. For example, if it is realized by hardware, it may be realized by any one of the following technologies known in the art or a combination thereof as in another embodiment: a discrete logic circuit having a logic gate circuit for realizing logic functions of data signals, application-specific integrated circuit having an appropriate combined logic gate circuit, a programmable gate array (PGA), and a field programmable gate array (FPGA), etc.
The description or blocks in the flowcharts or of any process or method in other manners may be understood as being indicative of comprising one or more modules, segments or parts for realizing the codes of executable instructions of the steps in specific logic functions or processes, and that the scope of the preferred embodiments of the present invention comprise other implementations, wherein the functions may be executed in manners different from those shown or discussed, including executing the functions according to the related functions in a substantially simultaneous manner or in a reverse order, which should be understood by those skilled in the art to which the present invention pertains.
The logic and/or steps shown in the flowcharts or described in other manners here may be, for example, understood as a sequencing list of executable instructions for realizing logic functions, which may be implemented in any computer readable medium, for use by an instruction executing system, device or apparatus (such as a system including a computer, a system including a processor, or other systems capable of extracting instructions from an instruction executing system, device or apparatus and executing the instructions), or for use in combination with the instruction executing system, device or apparatus.
The above literal description and drawings show various features of the present invention. It should be understood that those skilled in the art may prepare appropriate computer codes to carry out each of the steps and processes as described above and shown in the drawings. It should be also understood that all the terminals, computers, servers, and networks may be any type, and the computer codes may be prepared according to the disclosure to carry out the present invention by using the apparatus.
Particular embodiments of the present invention have been disclosed herein. Those skilled in the art will readily recognize that the present invention is applicable in other environments. In practice, there exist many embodiments and implementations. The appended claims are by no means intended to limit the scope of the present invention to the above particular embodiments. Furthermore, any reference to "a device to..." is an explanation of device plus function for describing elements and claims, and it is not desired that any element using no reference to "a device to..." is understood as an element of device plus function, even though the wording of "device" is included in that claim.
Although a particular preferred embodiment or embodiments have been shown and the present invention has been described, it is obvious that equivalent modifications and variants are conceivable to those skilled in the art in reading and understanding the description and drawings. Especially for various functions executed by the above elements (portions, assemblies, apparatus, and compositions, etc.), except otherwise specified, it is desirable that the terms (including the reference to "device") describing these elements correspond to any element executing particular functions of these elements (i.e. functional equivalents), even though the element is different from that executing the function of an exemplary embodiment or embodiments illustrated in the present invention with respect to structure. Furthermore, although the a particular feature of the present invention is described with respect to only one or more of the illustrated embodiments, such a feature may be combined with one or more other features of other embodiments as desired and in consideration of advantageous aspects of any given or particular application.
WE CLAIM:
1. A method of establishing IP security tunnel, the method comprising:
receiving a CA certificate, a local certificate and address information from a client; wherein the CA certificate includes one or more security association proposal;
establishing the IP security tunnel with the client according to the CA certificate, the local certificate and the address information.
2. The method according to claim 1, wherein the security association proposal is stored in the CA certificate in extension format, and is represented by 32 bit.
3. The method according to claim 1, wherein the security association proposal is IPSEC proposal or IKE proposal.
4. The method according to claim 1, wherein the address information includes a peer IP address or domain name.
5. The method according to claim 1, wherein the method further comprising:
retrieving the security association proposal from the CA certificate; retrieving local ID from the local certificate.
6. The method according to claim 5, wherein the CA certificate further includes traffic
selector information;
and the method further comprising: retrieving the traffic selector information from the CA certificate.
7. The method according to claim 4, wherein the method further comprising:
resolving the domain name so as to get IP address if the address information includes a domain name.
8. A method of establishing IP security tunnel, the method comprising:
sending a CA certificate, a local certificate and address information to a server; wherein the CA certificate includes one or more security association proposal.
9. The method according to claim 8, wherein the security association proposal is stored in the CA certificate in extension format, and is represented by 32 bit.
10. The method according to claim 8, wherein the security association proposal is IPSEC proposal or IKE proposal.
11 . The method according to claim 8, wherein the address information includes a peer IP address or domain name.
12.A server, the server comprising:
a receiving device, configured to receive a CA certificate, a local certificate and address information from a client; wherein the CA certificate includes one or more security association proposal;
an establishing device, configured to establish the IP security tunnel with the client according to the C A certificate, the local certificate and the address information.
13. The server according to claim 12, wherein the security association proposal is stored in the CA certificate in extension format, and is represented by 32 bit.
14. The server according to claim 12, wherein the security association proposal is IPSEC proposal or IKE proposal.
15. The server according to claim 12, wherein the address information includes a peer IP address or domain name.
16. The server according to claim 12, wherein the server further comprising:
a retrieving device, configured to retrieve the security association proposal from the CA certificate, and retrieve local ID from the local certificate.
17. The server according to claim 16, wherein the CA certificate further includes traffic
selector information;
and the retrieving device is further used to retrieve the traffic selector information from the CA certificate.
18. The server according to claim 15, wherein the server further comprising:
a resolving device, configured to resolve the domain name so as to get IP address if the address information includes a domain name.
19. A client, the client comprising:
a sending device, configured to send a CA certificate, a local certificate and address information to a server; wherein the CA certificate includes one or more security association proposal.
20. The client according to claim 19, wherein the security association proposal is stored
in the CA certificate in extension format, and is represented by 32 bit.
21. The client according to claim 19, wherein the security association proposal is IPSEC proposal or IKE proposal.
22. The client according to claim 19, wherein the address information includes a peer
IP address or domain name.
23. A computer-readable program, wherein when the program is executed in a server, the program enables the computer to carry out the method as claimed in any of claims 1-7 in the server.
24. A storage medium in which a computer-readable program is stored, wherein the computer-readable program enables the computer to carry out the method as claimed in any of claims 1-7 in the server.
25. A computer-readable program, wherein when the program is executed in a client, the program enables the computer to carry out the method as claimed in any of claims 8-11 in the client.
26. A storage medium in which a computer-readable program is stored, wherein the computer-readable program enables the computer to carry out the method as claimed in any of claims 8-11 in the client.
| Section | Controller | Decision Date |
|---|---|---|
| # | Name | Date |
|---|---|---|
| 1 | 4041-CHE-2012 FORM-3 28-09-2012.pdf | 2012-09-28 |
| 1 | 4041-CHE-2012-FORM-26 [03-02-2025(online)].pdf | 2025-02-03 |
| 1 | 4041-CHE-2012-FORM-27 [30-09-2024(online)].pdf | 2024-09-30 |
| 2 | 4041-CHE-2012 FORM-2 28-09-2012.pdf | 2012-09-28 |
| 2 | 4041-CHE-2012-FORM-27 [30-09-2024(online)].pdf | 2024-09-30 |
| 2 | 4041-CHE-2012-RELEVANT DOCUMENTS [25-09-2022(online)].pdf | 2022-09-25 |
| 3 | 4041-CHE-2012 FORM-1 28-09-2012.pdf | 2012-09-28 |
| 3 | 4041-CHE-2012-Abstract_Granted 346612_11-09-2020.pdf | 2020-09-11 |
| 3 | 4041-CHE-2012-RELEVANT DOCUMENTS [25-09-2022(online)].pdf | 2022-09-25 |
| 4 | 4041-CHE-2012-Claims_Granted 346612_11-09-2020.pdf | 2020-09-11 |
| 4 | 4041-CHE-2012-Abstract_Granted 346612_11-09-2020.pdf | 2020-09-11 |
| 4 | 4041-CHE-2012 DRAWINGS 28-09-2012.pdf | 2012-09-28 |
| 5 | 4041-CHE-2012-Description_Granted 346612_11-09-2020.pdf | 2020-09-11 |
| 5 | 4041-CHE-2012-Claims_Granted 346612_11-09-2020.pdf | 2020-09-11 |
| 5 | 4041-CHE-2012 DESCRIPTION (PROVISIONAL) 28-09-2012.pdf | 2012-09-28 |
| 6 | 4041-CHE-2012-Drawings_Granted 346612_11-09-2020.pdf | 2020-09-11 |
| 6 | 4041-CHE-2012-Description_Granted 346612_11-09-2020.pdf | 2020-09-11 |
| 6 | 4041-CHE-2012 CORRESPONDENCE OTHERS 28-09-2012.pdf | 2012-09-28 |
| 7 | 4041-CHE-2012-IntimationOfGrant11-09-2020.pdf | 2020-09-11 |
| 7 | 4041-CHE-2012-Drawings_Granted 346612_11-09-2020.pdf | 2020-09-11 |
| 7 | 4041-CHE-2012 ABSTRACT 28-09-2012.pdf | 2012-09-28 |
| 8 | 4041-CHE-2012 FORM-18 17-10-2012.pdf | 2012-10-17 |
| 8 | 4041-CHE-2012-IntimationOfGrant11-09-2020.pdf | 2020-09-11 |
| 8 | 4041-CHE-2012-Marked up Claims_Granted 346612_11-09-2020.pdf | 2020-09-11 |
| 9 | 4041-CHE-2012 CORRESPONDENCE OTHERS 17-10-2012.pdf | 2012-10-17 |
| 9 | 4041-CHE-2012-Marked up Claims_Granted 346612_11-09-2020.pdf | 2020-09-11 |
| 9 | 4041-CHE-2012-PatentCertificate11-09-2020.pdf | 2020-09-11 |
| 10 | 4041-CHE-2012 CORRESPONDENCE OTHERS 24-12-2012.pdf | 2012-12-24 |
| 10 | 4041-CHE-2012-PatentCertificate11-09-2020.pdf | 2020-09-11 |
| 10 | 4041-CHE-2012-PETITION UNDER RULE 137 [12-08-2020(online)].pdf | 2020-08-12 |
| 11 | 4041-CHE-2012 FORM-13 31-12-2012..pdf | 2012-12-31 |
| 11 | 4041-CHE-2012-PETITION UNDER RULE 137 [12-08-2020(online)].pdf | 2020-08-12 |
| 11 | 4041-CHE-2012-Written submissions and relevant documents [12-08-2020(online)].pdf | 2020-08-12 |
| 12 | 4041-CHE-2012 CORRESPONDENCE OTHERS 31-12-2012.pdf | 2012-12-31 |
| 12 | 4041-CHE-2012-Correspondence to notify the Controller [30-07-2020(online)].pdf | 2020-07-30 |
| 12 | 4041-CHE-2012-Written submissions and relevant documents [12-08-2020(online)].pdf | 2020-08-12 |
| 13 | 4041-CHE-2012-FORM-26 [30-07-2020(online)].pdf | 2020-07-30 |
| 13 | 4041-CHE-2012-Correspondence to notify the Controller [30-07-2020(online)].pdf | 2020-07-30 |
| 13 | 4041-CHE-2012 FORM-2 01-01-2013.pdf | 2013-01-01 |
| 14 | 4041-CHE-2012 CORRESPONDENCE OTHERS 01-01-2013.pdf | 2013-01-01 |
| 14 | 4041-CHE-2012-FORM-26 [30-07-2020(online)].pdf | 2020-07-30 |
| 14 | 4041-CHE-2012-US(14)-HearingNotice-(HearingDate-06-08-2020).pdf | 2020-07-14 |
| 15 | 4041-CHE-2012 FORM-5 01-01-2013.pdf | 2013-01-01 |
| 15 | 4041-CHE-2012-CLAIMS [02-02-2019(online)].pdf | 2019-02-02 |
| 15 | 4041-CHE-2012-US(14)-HearingNotice-(HearingDate-06-08-2020).pdf | 2020-07-14 |
| 16 | 4041-CHE-2012 DRAWINGS 01-01-2013.pdf | 2013-01-01 |
| 16 | 4041-CHE-2012-CLAIMS [02-02-2019(online)].pdf | 2019-02-02 |
| 16 | 4041-CHE-2012-FER_SER_REPLY [02-02-2019(online)].pdf | 2019-02-02 |
| 17 | 4041-CHE-2012 DESCRIPTION (COMPLETE) 01-01-2013.pdf | 2013-01-01 |
| 17 | 4041-CHE-2012-FER_SER_REPLY [02-02-2019(online)].pdf | 2019-02-02 |
| 17 | 4041-CHE-2012-OTHERS [02-02-2019(online)].pdf | 2019-02-02 |
| 18 | 4041-CHE-2012 CLAIMS 01-01-2013.pdf | 2013-01-01 |
| 18 | 4041-CHE-2012-FER.pdf | 2018-11-09 |
| 18 | 4041-CHE-2012-OTHERS [02-02-2019(online)].pdf | 2019-02-02 |
| 19 | 4041-CHE-2012 ABSTRACT 01-01-2013.pdf | 2013-01-01 |
| 19 | 4041-CHE-2012-FER.pdf | 2018-11-09 |
| 19 | Correspondence by Agent_Assignment_17-04-2018.pdf | 2018-04-17 |
| 20 | 4041-CHE-2012 FORM-1 26-03-2013.pdf | 2013-03-26 |
| 20 | 4041-CHE-2012-8(i)-Substitution-Change Of Applicant - Form 6 [06-04-2018(online)].pdf | 2018-04-06 |
| 20 | Correspondence by Agent_Assignment_17-04-2018.pdf | 2018-04-17 |
| 21 | 4041-CHE-2012-ASSIGNMENT DOCUMENTS [06-04-2018(online)].pdf | 2018-04-06 |
| 21 | 4041-CHE-2012-8(i)-Substitution-Change Of Applicant - Form 6 [06-04-2018(online)].pdf | 2018-04-06 |
| 21 | 4041-CHE-2012 CORRESPONDENCE OTHERS 26-03-2013.pdf | 2013-03-26 |
| 22 | 4041-CHE-2012 FORM-13 20-02-2015.pdf | 2015-02-20 |
| 22 | 4041-CHE-2012-ASSIGNMENT DOCUMENTS [06-04-2018(online)].pdf | 2018-04-06 |
| 22 | 4041-CHE-2012-PA [06-04-2018(online)].pdf | 2018-04-06 |
| 23 | 4041-CHE-2012-PA [06-04-2018(online)].pdf | 2018-04-06 |
| 23 | FORM 13 _Applicant Address Change_.pdf | 2015-03-13 |
| 23 | FORM NO. INC-22.pdf ONLINE | 2015-02-25 |
| 24 | FORM 13 _Applicant Address Change_.pdf | 2015-03-13 |
| 24 | FORM 13 _Applicant Address Change_.pdf ONLINE | 2015-02-25 |
| 24 | FORM NO. INC-22.pdf | 2015-03-13 |
| 25 | FORM 13 _Applicant Address Change_.pdf ONLINE | 2015-02-25 |
| 25 | FORM NO. INC-22.pdf | 2015-03-13 |
| 26 | FORM 13 _Applicant Address Change_.pdf | 2015-03-13 |
| 26 | FORM 13 _Applicant Address Change_.pdf ONLINE | 2015-02-25 |
| 26 | FORM NO. INC-22.pdf ONLINE | 2015-02-25 |
| 27 | 4041-CHE-2012 FORM-13 20-02-2015.pdf | 2015-02-20 |
| 27 | 4041-CHE-2012-PA [06-04-2018(online)].pdf | 2018-04-06 |
| 27 | FORM NO. INC-22.pdf ONLINE | 2015-02-25 |
| 28 | 4041-CHE-2012-ASSIGNMENT DOCUMENTS [06-04-2018(online)].pdf | 2018-04-06 |
| 28 | 4041-CHE-2012 FORM-13 20-02-2015.pdf | 2015-02-20 |
| 28 | 4041-CHE-2012 CORRESPONDENCE OTHERS 26-03-2013.pdf | 2013-03-26 |
| 29 | 4041-CHE-2012 CORRESPONDENCE OTHERS 26-03-2013.pdf | 2013-03-26 |
| 29 | 4041-CHE-2012 FORM-1 26-03-2013.pdf | 2013-03-26 |
| 29 | 4041-CHE-2012-8(i)-Substitution-Change Of Applicant - Form 6 [06-04-2018(online)].pdf | 2018-04-06 |
| 30 | 4041-CHE-2012 ABSTRACT 01-01-2013.pdf | 2013-01-01 |
| 30 | 4041-CHE-2012 FORM-1 26-03-2013.pdf | 2013-03-26 |
| 30 | Correspondence by Agent_Assignment_17-04-2018.pdf | 2018-04-17 |
| 31 | 4041-CHE-2012 ABSTRACT 01-01-2013.pdf | 2013-01-01 |
| 31 | 4041-CHE-2012 CLAIMS 01-01-2013.pdf | 2013-01-01 |
| 31 | 4041-CHE-2012-FER.pdf | 2018-11-09 |
| 32 | 4041-CHE-2012 CLAIMS 01-01-2013.pdf | 2013-01-01 |
| 32 | 4041-CHE-2012 DESCRIPTION (COMPLETE) 01-01-2013.pdf | 2013-01-01 |
| 32 | 4041-CHE-2012-OTHERS [02-02-2019(online)].pdf | 2019-02-02 |
| 33 | 4041-CHE-2012-FER_SER_REPLY [02-02-2019(online)].pdf | 2019-02-02 |
| 33 | 4041-CHE-2012 DRAWINGS 01-01-2013.pdf | 2013-01-01 |
| 33 | 4041-CHE-2012 DESCRIPTION (COMPLETE) 01-01-2013.pdf | 2013-01-01 |
| 34 | 4041-CHE-2012 DRAWINGS 01-01-2013.pdf | 2013-01-01 |
| 34 | 4041-CHE-2012 FORM-5 01-01-2013.pdf | 2013-01-01 |
| 34 | 4041-CHE-2012-CLAIMS [02-02-2019(online)].pdf | 2019-02-02 |
| 35 | 4041-CHE-2012-US(14)-HearingNotice-(HearingDate-06-08-2020).pdf | 2020-07-14 |
| 35 | 4041-CHE-2012 CORRESPONDENCE OTHERS 01-01-2013.pdf | 2013-01-01 |
| 35 | 4041-CHE-2012 FORM-5 01-01-2013.pdf | 2013-01-01 |
| 36 | 4041-CHE-2012 FORM-2 01-01-2013.pdf | 2013-01-01 |
| 36 | 4041-CHE-2012-FORM-26 [30-07-2020(online)].pdf | 2020-07-30 |
| 36 | 4041-CHE-2012 CORRESPONDENCE OTHERS 01-01-2013.pdf | 2013-01-01 |
| 37 | 4041-CHE-2012 CORRESPONDENCE OTHERS 31-12-2012.pdf | 2012-12-31 |
| 37 | 4041-CHE-2012 FORM-2 01-01-2013.pdf | 2013-01-01 |
| 37 | 4041-CHE-2012-Correspondence to notify the Controller [30-07-2020(online)].pdf | 2020-07-30 |
| 38 | 4041-CHE-2012 CORRESPONDENCE OTHERS 31-12-2012.pdf | 2012-12-31 |
| 38 | 4041-CHE-2012 FORM-13 31-12-2012..pdf | 2012-12-31 |
| 38 | 4041-CHE-2012-Written submissions and relevant documents [12-08-2020(online)].pdf | 2020-08-12 |
| 39 | 4041-CHE-2012 CORRESPONDENCE OTHERS 24-12-2012.pdf | 2012-12-24 |
| 39 | 4041-CHE-2012 FORM-13 31-12-2012..pdf | 2012-12-31 |
| 39 | 4041-CHE-2012-PETITION UNDER RULE 137 [12-08-2020(online)].pdf | 2020-08-12 |
| 40 | 4041-CHE-2012 CORRESPONDENCE OTHERS 24-12-2012.pdf | 2012-12-24 |
| 40 | 4041-CHE-2012 CORRESPONDENCE OTHERS 17-10-2012.pdf | 2012-10-17 |
| 40 | 4041-CHE-2012-PatentCertificate11-09-2020.pdf | 2020-09-11 |
| 41 | 4041-CHE-2012 CORRESPONDENCE OTHERS 17-10-2012.pdf | 2012-10-17 |
| 41 | 4041-CHE-2012 FORM-18 17-10-2012.pdf | 2012-10-17 |
| 41 | 4041-CHE-2012-Marked up Claims_Granted 346612_11-09-2020.pdf | 2020-09-11 |
| 42 | 4041-CHE-2012 ABSTRACT 28-09-2012.pdf | 2012-09-28 |
| 42 | 4041-CHE-2012 FORM-18 17-10-2012.pdf | 2012-10-17 |
| 42 | 4041-CHE-2012-IntimationOfGrant11-09-2020.pdf | 2020-09-11 |
| 43 | 4041-CHE-2012 ABSTRACT 28-09-2012.pdf | 2012-09-28 |
| 43 | 4041-CHE-2012 CORRESPONDENCE OTHERS 28-09-2012.pdf | 2012-09-28 |
| 43 | 4041-CHE-2012-Drawings_Granted 346612_11-09-2020.pdf | 2020-09-11 |
| 44 | 4041-CHE-2012 CORRESPONDENCE OTHERS 28-09-2012.pdf | 2012-09-28 |
| 44 | 4041-CHE-2012 DESCRIPTION (PROVISIONAL) 28-09-2012.pdf | 2012-09-28 |
| 44 | 4041-CHE-2012-Description_Granted 346612_11-09-2020.pdf | 2020-09-11 |
| 45 | 4041-CHE-2012 DESCRIPTION (PROVISIONAL) 28-09-2012.pdf | 2012-09-28 |
| 45 | 4041-CHE-2012 DRAWINGS 28-09-2012.pdf | 2012-09-28 |
| 45 | 4041-CHE-2012-Claims_Granted 346612_11-09-2020.pdf | 2020-09-11 |
| 46 | 4041-CHE-2012-Abstract_Granted 346612_11-09-2020.pdf | 2020-09-11 |
| 46 | 4041-CHE-2012 FORM-1 28-09-2012.pdf | 2012-09-28 |
| 46 | 4041-CHE-2012 DRAWINGS 28-09-2012.pdf | 2012-09-28 |
| 47 | 4041-CHE-2012-RELEVANT DOCUMENTS [25-09-2022(online)].pdf | 2022-09-25 |
| 47 | 4041-CHE-2012 FORM-2 28-09-2012.pdf | 2012-09-28 |
| 47 | 4041-CHE-2012 FORM-1 28-09-2012.pdf | 2012-09-28 |
| 48 | 4041-CHE-2012-FORM-27 [30-09-2024(online)].pdf | 2024-09-30 |
| 48 | 4041-CHE-2012 FORM-3 28-09-2012.pdf | 2012-09-28 |
| 48 | 4041-CHE-2012 FORM-2 28-09-2012.pdf | 2012-09-28 |
| 49 | 4041-CHE-2012-FORM-26 [03-02-2025(online)].pdf | 2025-02-03 |
| 49 | 4041-CHE-2012 FORM-3 28-09-2012.pdf | 2012-09-28 |
| 1 | searchstrategy_09-11-2018.pdf |