Clock-in positioning method, system, device and storage medium compatible with multiple application platforms

Abstract

The application discloses a punch-in positioning method and system compatible with multiple application platforms, a device and a storage medium, judges the type of a current client application, and loads an SDK package of the corresponding client application; in response to a punch-in positioning request of a user, authenticates the user access authority of the client application; if the authentication is passed, calls a positioning interface of the client application to position the user position, and obtains a positioning result, wherein the positioning interface call is realized by encapsulating the positioning interfaces of the multiple application platforms supported and exposing a unified interface; and the data result in a unified coordinate system obtained through coordinate conversion of the positioning result. The positioning interfaces and results of all the application platforms supported are encapsulated, a unified interface is exposed, the positioning results of the platforms are encapsulated and processed, and a result in a unified format is returned, so that the punch-in positioning business is realized by integrating the positioning capabilities of other platforms, and secondary development is not needed.

Description

Technical Field

[0001] This invention relates to the field of attendance tracking technology, specifically to an attendance tracking method, system, device, and storage medium compatible with multiple application platforms. Background Technology

[0002] With the rapid development of technology, the means of implementing attendance systems have evolved from mechanical punch card systems to today's RFID cards, fingerprint recognition, and facial recognition systems. With the widespread adoption of mobile terminals, especially smartphones, more and more companies are using mobile attendance systems, solving the problem of queuing in front of attendance machines during peak hours. Location tracking is a crucial aspect of attendance management, ensuring the accuracy of attendance records by accurately locating employees during check-in. While various application platforms, such as DingTalk, WeChat, and Lark, offer location API calls, inconsistencies in API implementation methods and definitions lead to incompatibility. In practice, businesses need to process and convert the API results from each platform individually to meet their needs, which is inconvenient. Furthermore, secondary development requires significant investment. Summary of the Invention

[0003] To address this issue, the present invention provides a check-in and positioning method, system, device, and storage medium compatible with multiple application platforms, thereby solving the problem that existing multi-application platforms that can realize positioning interface call functions are incompatible, and that in actual use, the interface results of all platforms need to be processed and converted one by one to meet business needs, which is inconvenient to use.

[0004] To achieve the above objectives, the present invention provides the following technical solution:

[0005] According to a first aspect of the present invention, a check-in and location method compatible with multiple application platforms is proposed, the method comprising:

[0006] Determine the type of the current client application and load the corresponding client application's SDK package;

[0007] In response to the user's check-in location request, the user's access permissions for the client application are authenticated;

[0008] If authentication is successful, the location interface of the client application is called to locate the user's location and obtain the location result. The location interface call is achieved by encapsulating the location interfaces of multiple supported application platforms and exposing a unified interface.

[0009] The positioning results are transformed to obtain data results in a unified coordinate system.

[0010] Furthermore, before determining the type of the current client application and loading the corresponding client application's SDK package, the method further includes:

[0011] Download the SDK packages for different application platforms and integrate them into your H5 project.

[0012] Furthermore, in response to the user's check-in location request, the authentication of user access permissions for the client application specifically includes:

[0013] If authentication fails, the browser's location API will be called to locate the device.

[0014] Furthermore, the method also includes:

[0015] The system determines whether the user's location was successfully obtained based on the result of the location interface callback function. If the location is successful, the location result is obtained; if the location fails, a disaster recovery strategy that allows the system to seamlessly try other location methods is triggered.

[0016] Furthermore, the location of the user is determined by calling the location interface of the client application, specifically including:

[0017] Location information is obtained by communicating with the GPS chip of the mobile terminal device.

[0018] Furthermore, the data results obtained by transforming the positioning results into a unified coordinate system specifically include:

[0019] The positioning results from different application platforms use different geographic coordinate systems. By converting the positioning results from different geographic coordinate systems to a unified geographic coordinate system, a unified result can be obtained.

[0020] Furthermore, the geographic coordinate system includes the WGS 84 coordinate system, the GCJ-02 coordinate system, and the BD-09 coordinate system.

[0021] According to a second aspect of the present invention, a check-in and positioning system compatible with multiple application platforms is provided, the system comprising:

[0022] The application loading module is used to determine the type of the current client application and load the corresponding client application's SDK package;

[0023] The application authentication module is used to authenticate the user's access permissions for the client application in response to the user's check-in location request.

[0024] The positioning module is used to call the positioning interface of the client application to locate the user's location and obtain the positioning result if the authentication is successful. The positioning interface call is implemented by encapsulating the positioning interfaces of multiple supported application platforms and exposing a unified interface.

[0025] The result unification module is used to transform the positioning results into data results in a unified coordinate system.

[0026] According to a third aspect of the present invention, an electronic device is provided, the device comprising: a processor and a memory;

[0027] The memory is used to store one or more program instructions;

[0028] The processor is configured to run one or more program instructions to perform the steps of a multi-application platform compatible check-in and positioning method as described in any of the preceding claims.

[0029] According to a fourth aspect of the present invention, a computer-readable storage medium is provided, on which a computer program is stored, wherein when the computer program is executed by a processor, the computer program implements the steps of the check-in and positioning method compatible with multiple application platforms as described in any of the preceding claims.

[0030] This invention proposes a check-in and location tracking method, system, device, and storage medium compatible with multiple application platforms. It determines the type of the current client application and loads the corresponding SDK package. In response to a user's check-in and location tracking request, it authenticates the user's access permissions for the client application. If authentication is successful, it calls the client application's location interface to locate the user's position and obtains the location result. This is achieved by encapsulating the location interfaces of multiple supported application platforms and exposing a unified interface for location interface calls. The location result is then transformed to obtain data in a unified coordinate system. This invention integrates the introduction and loading of SDK packages dependent on various applications. Based on the current calling environment, the corresponding SDK package is loaded. The caller does not need to concern themselves with the method names and usage methods exposed by the SDK in the current environment; they can directly call the integrated interface. Since the location tracking methods implemented by different clients vary, and the result formats and coordinate systems of the location locations also differ, this invention integrates the results and coordinate systems, and then packages them into a unified format and coordinate system for return. The caller does not need to perform compatibility processing. By integrating the location capabilities of other platforms, the check-in and location tracking service is implemented without secondary development. Attached Figure Description

[0031] To more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are merely exemplary, and those skilled in the art can derive other embodiments based on the provided drawings without creative effort.

[0032] The structures, proportions, sizes, etc. illustrated in this specification are only for the purpose of assisting those skilled in the art in understanding and reading the content disclosed herein, and are not intended to limit the conditions under which the present invention can be implemented. Therefore, they have no substantial technical significance. Any modifications to the structure, changes in the proportions, or adjustments to the size, without affecting the effects and objectives that the present invention can produce, should still fall within the scope of the technical content disclosed in the present invention.

[0033] Figure 1 A flowchart illustrating a check-in and location method compatible with multiple application platforms, provided as an embodiment of the present invention;

[0034] Figure 2 A flowchart illustrating the specific implementation of a check-in and location method compatible with multiple application platforms, provided by an embodiment of the present invention;

[0035] Figure 3 This is a schematic diagram of the logical structure of a check-in and positioning system compatible with multiple application platforms, provided as an embodiment of the present invention. Detailed Implementation

[0036] The following specific embodiments illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0037] The first embodiment of the present invention provides a check-in and positioning method compatible with multiple application platforms. The following is in conjunction with... Figure 1 and Figure 2 Please provide an explanation.

[0038] like Figure 1 As shown, in step S100, the type of the current client application is determined, and the SDK package of the corresponding client application is loaded.

[0039] Before step S100, the method further includes: downloading and obtaining SDK packages for different application platforms and integrating them into the H5 project.

[0040] By integrating the import and loading of SDK packages required by various applications, the system loads the corresponding SDK package based on the current calling environment. This embodiment's multi-application platform compatible check-in and location method is an H5-based check-in service method. To achieve compatibility with mainstream application platforms with location capabilities (such as DingTalk, WeChat, Lark, etc.), the SDK package provided by the application open platform can be downloaded, including related JavaScript files and resource files. Integrating the downloaded SDK files into the H5 project involves importing the relevant JavaScript files into the HTML file and placing the relevant resource files in an appropriate directory. Therefore, the location function provided by the application SDK can be called from the H5 page.

[0041] Upon entering the H5 page, the system first determines the type of the current client application and loads the corresponding SDK package. It then analyzes which host application is currently running; for example, if it's running WeChat, it loads WeChat's JSSDK; if it's running DingTalk, it loads DingTalk's JSSDK.

[0042] Additionally, the current host application can be determined by checking `window.navigator.userAgent`. Based on the platform identifiers, it's possible to identify whether the current host application is WeChat, DingTalk, or a browser. If it's in WeChat, this can be determined by checking if `window.navigator.userAgent` contains WeChat-specific keywords. If it's in DingTalk, this can be determined by checking if `window.navigator.userAgent` contains DingTalk-specific keywords. If it's in a browser, a standard location API can be loaded directly without needing to load a specific JSSDK.

[0043] When the SDK loads, it first determines the current calling environment (such as WeChat, DingTalk, browser, etc.). Based on the environment, it loads the corresponding SDK package. This can be done dynamically by creating... <script>标签或使用import()函数动态加载SDK包。

[0044] 在加载完成JSSDK后，需要进行JSSDK的初始化操作，以便使用开放接口提供的功能。根据不同的JSSDK，可以调用相应的初始化方法，并进行配置和授权等操作。

[0045] 如图1所示，在步骤S200中，响应于用户的打卡定位请求，对所述客户端应用的用户访问权限进行鉴权。

[0046] 上述步骤具体还包括：若鉴权失败，则调用浏览器的定位接口进行定位。

[0047] 用户在H5页面点击实际打卡业务按钮时，首先对所述客户端应用的用户访问权限进行鉴权，验证用户的登录名和密码。若鉴权通过，则继续调用对应的开放接口，若鉴权失败，则调用浏览器的定位接口定位。

[0048] 要实现浏览器定位，可以使用HTML5中的Geolocation API。该API允许网页向用户请求其当前位置，并提供相关的位置信息。示例性的，先使用navigator.geolocation对象来检测浏览器是否支持定位功能。如果支持，则调用getCurrentPosition()方法来获取当前位置，该方法接受一个回调函数。在回调函数showPosition()中，可以处理位置信息，例如获取纬度和经度，并在弹窗中显示出来。浏览器在请求用户位置之前通常会弹出一个权限请求窗口，询问用户是否允许网页获取其位置。用户同意后，浏览器将根据用户设备的定位方式(如基于GPS、Wi-Fi或IP地址)来获得位置信息。

[0049] 如图1所示，在步骤S300中，若鉴权通过，则调用所述客户端应用的定位接口对用户位置进行定位，并获取定位结果，其中通过对支持的多个应用平台的定位接口进行封装并暴露统一的接口实现定位接口调用。

[0050] 鉴权成功后，调用当前客户端应用暴露的定位接口，各客户端实现和定义定位接口不一致，需要根据当前环境进行对应的业务开发。

[0051] 比如钉钉和微信都提供了定位接口，可以用于获取用户的地理位置信息。钉钉定位接口：钉钉提供了JSAPI中的dd.device.geolocation.get()方法来获取用户的地理位置信息。可以通过调用该方法来获取用户的经纬度、定位精度等信息。微信定位接口：微信提供了JSAPI中的wx.getLocation()方法来获取用户的地理位置信息。可以通过调用该方法来获取用户的经纬度、定位精度等信息。

[0052] 本发明对所有支持的平台的定位接口和结果进行封装，暴露统一的接口。通过创建一个封装的定位接口，该接口调用各平台的定位接口，并将结果进行封装和处理。这个封装的接口可以定义为统一的命名和参数，方便开发者调用和使用。调用者无需关注当前环境的SDK暴露的方法名称和方法的使用方法，通过本方案整合调用的接口直接调用即可。

[0053] 上述步骤具体还包括：根据定位接口回调函数的结果判断获取用户位置是否成功，若定位成功，则获取定位结果，若定位失败，则会触发无感尝试其他定位方式的容灾策略。

[0054] 通常，在定位接口回调函数中，会返回一个位置对象，其中包含了获取到的位置信息。开发者可以根据这个位置对象判断定位是否成功。

[0055] 在Geolocation API中，可以使用getCurrentPosition()方法获取位置信息。该方法接受两个回调函数作为参数：一个成功回调函数和一个失败回调函数。成功回调函数会在获取位置成功时调用，而失败回调函数会在获取位置失败时调用。

[0056] 在成功回调函数中，可以通过函数的参数来获取位置对象。位置对象通常包含以下属性：

[0057] coords.latitude:纬度值

[0058] coords.longitude:经度值

[0059] coords.accuracy:位置精度(以米为单位)

[0060] coords.altitude:海拔信息(如果可用)

[0061] coords.altitudeAccuracy:海拔信息的精度(如果可用)

[0062] coords.heading:方向(以度为单位，如果可用)

[0063] coords.speed:速度(以米 / 秒为单位，如果可用)

[0064] 如果成功获取到位置对象，并且其中的位置信息符合预期，则可以判断获取用户位置成功。否则，如果获取位置失败或返回的位置信息不符合预期，则可以判断获取用户位置失败。

[0065] 在失败回调函数中，可以根据错误信息来判断获取位置失败的原因。常见的错误信息包括：

[0066] PERMISSION_DENIED:用户拒绝提供位置信息的权限

[0067] POSITION_UNAVAILABLE:无法获取位置信息

[0068] TIMEOUT:获取位置信息超时

[0069] 通过对回调函数参数的判断，可以根据定位接口回调的结果来确定获取用户位置是否成功。

[0070] 根据定位接口回调判断获取用户位置是否成功，若定位成功，则流程结束，若定位失败，则会触发无感尝试其他定位方式的容灾策略，这样是为了保证在第三方定位能力出现故障时，能够最大程度上保证定位的稳定性。

[0071] 具体的容灾策略可能因浏览器和设备的不同而有所差异。以下是一些常见的容灾策略：

[0072] 切换定位方式：浏览器可能会依次尝试使用不同的定位方式，如GPS、Wi-Fi、IP地址等，直到定位成功或尝试完所有方式。

[0073] 增加定位时长：当定位失败时，浏览器可能会延长定位的时间，继续尝试定位，以增加成功的机会。

[0074] 错误处理：如果定位失败，浏览器会在回调函数中返回错误信息，开发者可以根据错误类型进行相应的处理，如提示用户重新尝试、提供备选方案等。

[0075] 进一步地，调用所述客户端应用的定位接口对用户位置进行定位，具体包括：通过与移动终端设备的GPS芯片通信获取位置信息。

[0076] 客户端应用定位能力一般是基于手机GPS硬件的定位，浏览器定位能力较弱，成功率相对较低。

[0077] 当应用调用定位接口时，它会与手机的GPS芯片进行交互，请求获取位置信息。GPS芯片会向卫星发送信号，并接收卫星返回的信号，然后计算出设备的位置信息。最终，定位接口会将获取到的位置信息返回给应用，以便应用进行相应的处理。

[0078] 如图1所示，在步骤S400中，将所述定位结果进行坐标转换得的统一坐标系下的数据结果。

[0079] 上述步骤具体包括：不同应用平台的定位结果采用不同的地理坐标系，将不同地理坐标系的定位结果转换至统一的地理坐标系下，得到统一的结果。

[0080] 定位完成后，是将不同平台返回的定位结果进行统一的处理和转化，具体为进行地理坐标系的转换。不同地图坐标系的转换：不同地图供应商可能使用不同的坐标系，如百度地图使用百度坐标系(BD-09)，高德地图使用火星坐标系(GCJ-02)等。可以使用相应的转换算法将不同地图的坐标进行转换。

[0081] 当前常用的地理坐标系有：WGS 84(World Geodetic System 1984)：WGS 84是全球定位系统(GPS)的基准坐标系统，广泛应用于全球定位和导航，它采用十进制度表示经度和纬度；GCJ-02(国测局加密坐标)：中国采用的加密坐标系，也称为火星坐标系，对WGS 84坐标进行加密偏移；BD-09(百度坐标)：百度地图使用的加密坐标系，对GCJ-02坐标进行加密偏移。

[0082] 各个应用平台使用的地理坐标系不同，且各业务中需要使用的地理坐标系也各不相同，本实施例支持了地理坐标系相互转换的能力。基于地理坐标转换理论公式，实现转换代码。本实施例通过对各平台的定位结果进行封装和处理，可返回统一格式的结果，无需再进行兼容处理。

[0083] 针对于各应用实现的定位方式各不相同，且结果格式和定位位置的坐标系也各不相同，本方案将结果和坐标系进行整合，再包装为统一格式和坐标系返回，调用者无需再进行兼容处理。

[0084] 与现有技术相比，本申请实施例提供的一种兼容多应用平台的打卡定位方法，判断当前客户端应用的类型，并加载对应客户端应用的SDK包；响应于用户的打卡定位请求，对所述客户端应用的用户访问权限进行鉴权；若鉴权通过，则调用所述客户端应用的定位接口对用户位置进行定位，并获取定位结果，其中通过对支持的多个应用平台的定位接口进行封装并暴露统一的接口实现定位接口调用；将所述定位结果进行坐标转换得的统一坐标系下的数据结果。本发明通过对各应用依赖sdk包的引入和加载的整合，根据当前调用环境加载对应的sdk包，调用者无需关注当前环境的SDK暴露的方法名称和方法的使用方法，通过本发明整合调用的接口直接调用即可，各客户端实现的定位方式各不相同，且结果格式和定位位置的坐标系也各不相同，本发明将结果和坐标系进行整合，再包装为统一格式和坐标系返回，调用者无需再进行兼容处理，通过整合其他平台的定位能力实现打卡定位业务，无需二次开发。

[0085] 与上述公开的一种兼容多应用平台的打卡定位方法相对应，本发明实施例还公开了一种兼容多应用平台的打卡定位系统，如图3所示，其具体包括：

[0086] 应用加载模块，用于判断当前客户端应用的类型，并加载对应客户端应用的SDK包；

[0087] 应用鉴权模块，用于响应于用户的打卡定位请求，对所述客户端应用的用户访问权限进行鉴权；

[0088] 定位模块，用于若鉴权通过，则调用所述客户端应用的定位接口对用户位置进行定位，并获取定位结果，其中通过对支持的多个应用平台的定位接口进行封装并暴露统一的接口实现定位接口调用；

[0089] 结果统一模块，用于将所述定位结果进行坐标转换得的统一坐标系下的数据结果。

[0090] 进一步地，所述系统还包括集成模块，用于下载获取不同应用平台的SDK包，并集成到H5项目中。

[0091] 进一步地，所述定位模块，具体还用于若鉴权失败，则调用浏览器的定位接口进行定位。

[0092] 进一步地，所述定位模块，具体用于根据定位接口回调函数的结果判断获取用户位置是否成功，若定位成功，则获取定位结果，若定位失败，则会触发无感尝试其他定位方式的容灾策略。

[0093] 进一步地，所述定位模块，具体用于通过与移动终端设备的GPS芯片通信获取位置信息。

[0094] 进一步地，所述结果统一模块，具体用于，不同应用平台的定位结果采用不同的地理坐标系，将不同地理坐标系的定位结果转换至统一的地理坐标系下，得到统一的结果。

[0095] 进一步地，所述地理坐标系包括WGS 84坐标系、GCJ-02坐标系、BD-09坐标系。

[0096] 需要说明的是，对于本发明实施例提供的一种兼容多应用平台的打卡定位系统的详细描述可以参考对本申请实施例提供的一种兼容多应用平台的打卡定位方法的相关描述，这里不再赘述。

[0097] 与现有技术相比，本申请实施例提供的一种兼容多应用平台的打卡定位系统，判断当前客户端应用的类型，并加载对应客户端应用的SDK包；响应于用户的打卡定位请求，对所述客户端应用的用户访问权限进行鉴权；若鉴权通过，则调用所述客户端应用的定位接口对用户位置进行定位，并获取定位结果，其中通过对支持的多个应用平台的定位接口进行封装并暴露统一的接口实现定位接口调用；将所述定位结果进行坐标转换得的统一坐标系下的数据结果。本发明通过对各应用依赖sdk包的引入和加载的整合，根据当前调用环境加载对应的sdk包，调用者无需关注当前环境的SDK暴露的方法名称和方法的使用方法，通过本发明整合调用的接口直接调用即可，各客户端实现的定位方式各不相同，且结果格式和定位位置的坐标系也各不相同，本发明将结果和坐标系进行整合，再包装为统一格式和坐标系返回，调用者无需再进行兼容处理，通过整合其他平台的定位能力实现打卡定位业务，无需二次开发。

[0098] 另外，本发明实施例还提供了一种电子设备，所述设备包括：处理器和存储器；所述存储器用于存储一个或多个程序指令；所述处理器，用于运行一个或多个程序指令，用以执行如上任一项所述的一种兼容多应用平台的打卡定位方法的步骤。

[0099] 需要说明的是，对于本发明实施例提供的一种电子设备的详细描述可以参考对本申请实施例提供的一种兼容多应用平台的打卡定位方法的相关描述，这里不再赘述。

[0100] 另外，本发明实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如上任一项所述一种兼容多应用平台的打卡定位方法的步骤。

[0101] 需要说明的是，对于本发明实施例提供的一种计算机可读存储介质的详细描述可以参考对本申请实施例提供的一种兼容多应用平台的打卡定位方法的相关描述，这里不再赘述。

[0102] 在本发明实施例中，处理器可以是一种集成电路芯片，具有信号的处理能力。处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，简称DSP)、专用集成电路(Application Specific Integrated Circuit，简称ASIC)、现场可编程门阵列(FieldProgrammable Gate Array，简称FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。

[0103] 可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。处理器读取存储介质中的信息，结合其硬件完成上述方法的步骤。

[0104] 存储介质可以是存储器，例如可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。

[0105] 其中，非易失性存储器可以是只读存储器(Read-Only Memory，简称ROM)、可编程只读存储器(Programmable ROM，简称PROM)、可擦除可编程只读存储器(Erasable PROM，简称EPROM)、电可擦除可编程只读存储器(Electrically EPROM，简称EEPROM)或闪存。

[0106] 易失性存储器可以是随机存取存储器(Random Access Memory，简称RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，简称SRAM)、动态随机存取存储器(Dynamic RAM，简称DRAM)、同步动态随机存取存储器(Synchronous DRAM，简称SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data RateSDRAM，简称DDRSDRAM)、增强型同步动态随机存取存储器(EnhancedSDRAM，简称ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，简称SLDRAM)和直接内存总线随机存取存储器(DirectRambus RAM，简称DRRAM)。

[0107] 本发明实施例描述的存储介质旨在包括但不限于这些和任意其它适合类型的存储器。

[0108] 本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明所描述的功能可以用硬件与软件组合来实现。当应用软件时，可以将相应功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。

[0109] 虽然，上文中已经用一般性说明及具体实施例对本发明作了详尽的描述，但在本发明基础上，可以对之作一些修改或改进，这对本领域技术人员而言是显而易见的。因此，在不偏离本发明精神的基础上所做的这些修改或改进，均属于本发明要求保护的范围。< / script>

Claims

1. A check-in and location method compatible with multiple application platforms, characterized in that, The method includes: determining the type of the current client application and loading the corresponding client application's SDK package; authenticating the user access permissions of the client application in response to the user's check-in location request; if authentication is successful, calling the client application's location interface to locate the user's location and obtaining the location result, wherein the location interface call is implemented by encapsulating the location interfaces of multiple supported application platforms and exposing a unified interface; converting the location result to obtain data results in a unified coordinate system; before determining the type of the current client application and loading the corresponding client application's SDK package, the method further includes: downloading and obtaining SDK packages for different application platforms and integrating them into the H5 project; authenticating the user access permissions of the client application in response to the user's check-in location request, specifically further including: if authentication fails, calling the browser's location interface to locate the user.

2. The check-in and positioning method compatible with multiple application platforms according to claim 1, characterized in that, The method further includes: determining whether the user's location was successfully obtained based on the result of the location interface callback function; if the location is successful, the location result is obtained; if the location fails, a disaster recovery strategy of seamlessly trying other location methods is triggered.

3. The check-in and positioning method compatible with multiple application platforms according to claim 1, characterized in that, The location of the user is determined by calling the location interface of the client application, specifically by obtaining location information through communication with the GPS chip of the mobile terminal device.

4. The check-in and positioning method compatible with multiple application platforms according to claim 1, characterized in that, The data results obtained by transforming the positioning results into a unified coordinate system specifically include: positioning results from different application platforms use different geographic coordinate systems, and the positioning results from different geographic coordinate systems are transformed into a unified geographic coordinate system to obtain a unified result.

5. The check-in and positioning method compatible with multiple application platforms according to claim 4, characterized in that, The geographic coordinate systems include the WGS 84 coordinate system, the GCJ-02 coordinate system, and the BD-09 coordinate system.

6. A check-in and positioning system compatible with multiple application platforms, characterized in that, The system includes: an application loading module, used to determine the type of the current client application and load the corresponding client application's SDK package; an application authentication module, used to authenticate the user's access permissions for the client application in response to the user's check-in location request; a location module, used to call the client application's location interface to locate the user's location and obtain the location result if authentication is successful, wherein the location interface call is implemented by encapsulating the location interfaces of multiple supported application platforms and exposing a unified interface; a result unification module, used to transform the location result to obtain data results in a unified coordinate system; the system also includes an integration module, used to download and obtain SDK packages of different application platforms and integrate them into the H5 project; the location module is also used to call the browser's location interface to locate if authentication fails.

7. An electronic device, characterized in that, The device includes: a processor and a memory; the memory is used to store one or more program instructions; the processor is used to run one or more program instructions to perform the steps of the check-in and positioning method compatible with multiple application platforms as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the check-in and positioning method compatible with multiple application platforms as described in any one of claims 1 to 5.

Images