![]() |
MapLink Pro 11.1.1.0.
Envitia MapLink Pro: The Ultimate Mapping Application Toolkit
|
This utility class is used to generate User Permits that the OEM should send to the Data Server (DS) when requesting Cell Permits for a set of ENC cells.
Static Public Member Functions | |
static TSLS63UserPermitGeneratorResult | generateUserPermit (const TSLS63HWID *user_HW_ID, const char *oem_M_KEY, const char *oem_M_ID, TSLSimpleString &result) |
static TSLS63UserPermitGeneratorResult | generateUserPermitWithoutMIDRestrictions (const TSLS63HWID *user_HW_ID, const char *oem_M_KEY, const char *oem_M_ID, TSLSimpleString &result) |
|
static |
Generates a user permit that can then be used by data clients to request cell permits for a particular system. Each user permit is tied to a unique machine via the OEM-assigned HW_ID. The Scheme Administrator assigned M_KEY and M_ID are combined to create these permits, which can then be provided to the data client. The data client then provides this permit to a data server who will then issue cell permits for the client's system for the cells they have purchased.
user_HW_ID | The hardware ID of the data client's system to generate a user permit for. |
oem_M_KEY | The Scheme Administrator supplied M_KEY for the OEM issuing the user permit. |
oem_M_ID | The Scheme Administrator supplied M_ID for the OEM issuing the user permit. This must consist of 2 alphanumeric characters, and will be converted to hexadecimal before being appended to the rest of the user permit. |
result | The user permit generated. |
|
static |
Generates a user permit that can then be used by data clients to request cell permits for a particular system. Each user permit is tied to a unique machine via the OEM-assigned HW_ID. The Scheme Administrator assigned M_KEY and M_ID are combined to create these permits, which can then be provided to the data client. The data client then provides this permit to a data server who will then issue cell permits for the client's system for the cells they have purchased.
S-63 edition 1.2 states that: 'In April 2012, small changes were made to Edition 1.1 to remove the hexadecimal limitation of M_ID in order to extend the number of possible M_ ID values that the scheme is able to accommodate.This resulted in the publication of edition 1.1.1 of S-63'
Elsewhere in the specification it refers to M_ID as being 2 alphanumeric characters, and that it should be converted to hexadecimal before being appended to the end of the generated user permit. As the specification is not clear, this method will not modify the 'oem_M_ ID' argument.
The required structure of M_ID will depend on the application, and the data provider.
user_HW_ID | The hardware ID of the data client's system to generate a user permit for. |
oem_M_KEY | The Scheme Administrator supplied M_KEY for the OEM issuing the user permit. |
oem_M_ID | The Scheme Administrator supplied M_ID for the OEM issuing the user permit. No restrictions are placed on this ID. It will be appended to the rest of the user permit without any modifications. |