Methods, devices, equipment, and storage media for handling identifiers when calling middleware services

Abstract

The disclosed embodiment provides an identification processing method for calling a middle office service, which is executed by the middle office, including: allocating a first type of identification; determining a service calling method for a target user group to call the middle office service; determining whether the target user group's call to the middle office service involves a second type of identification based on the service calling method; in the case where it is determined that the middle office service call involves the second type of identification, establishing mapping information between the first type of identification and the second type of identification; and using the mapping information to allow the target user group to call the middle office service. The disclosed embodiment also provides an identification processing device, equipment, and storage medium for calling a middle office service.

Description

Technical Field

[0001] The present disclosure relates to, but is not limited to, the field of data processing technology, and in particular to an identification processing method, device, equipment, and storage medium for calling a middleware service. Background Art

[0002] With the continuous development of terminal and Internet technologies, the platform can provide various technical support for different business forms; currently, some overall office platform services can be provided to external users so that external users can use the overall services of the platform. The middle platform is a further "abstraction" based on the platform, and the relationship between more businesses, data and technologies can be solved through the middle platform. However, currently users cannot integrate the middle platform services of the middle platform into the user's third-party applications through account information, such as integration into applications (APP), web pages and / or desktops, and cannot integrate third-party applications with the capabilities of the middle platform. Summary of the invention

[0003] The present invention provides a method, device, equipment and storage medium for processing an identification for calling a middleware service.

[0004] According to a first aspect of the present disclosure, a method for processing an identification for calling a middle station service is provided, which is executed by the middle station and includes:

[0005] assigning first-class identification;

[0006] Determine the service calling method for the target user group to call the middle office service;

[0007] Determine, according to the service calling mode, whether the target user group calling the middle platform service involves the second type of identification; if it is determined that the middle platform service calling involves the second type of identification, establish mapping information between the first type of identification and the second type of identification;

[0008] The mapping information is used to allow the target user group to call the middle platform service.

[0009] In some embodiments, the second type of identification includes: a third-party application identification;

[0010] The determining, according to the service calling mode, whether the target user group calling the middle platform service involves a second type of identification includes:

[0011] When the service calling method is based on user identification, determine whether the target user group uses the third-party application identification to call the middle office service; the mapping information indicates a first mapping relationship between the first type of identification and the third-party application identification.

[0012] In some embodiments, when the service calling mode is based on user identification calling, determining whether the target user group uses the third-party application identification to call the middle platform service includes:

[0013] In the case where the service calling mode is the calling based on the user identification, determining whether the target user group uses the third-party application identification to call the middle platform service according to the identification application requirement information;

[0014] or,

[0015] In the case where the service calling mode is the user identifier-based calling, it is determined whether the target user group uses the third-party application identifier to call the middle platform service according to the situation of receiving the third-party application identifier in the process of allocating the first type of identifier.

[0016] In some embodiments, determining, according to the service calling mode, whether the target user group calling the middle platform service involves a second type of identification includes:

[0017] In the case where the service calling method is calling SDK, determining that the target user group uses the second type of identifier to call the middle platform service, and the second type of identifier is an identifier of the SDK;

[0018] The mapping information indicates a second mapping relationship between the SDK identifier and the first type of identifier.

[0019] In some embodiments, the method comprises:

[0020] The mapping information is sent to the client; wherein the mapping information is used for the client to call the middle office service based on the first type of identifier, or the mapping information is used for the client to call the middle office service based on the second type of identifier.

[0021] In some embodiments, the method comprises:

[0022] Receive service call request;

[0023] In the case that the service invocation request includes a request identifier, whether to respond to the service invocation request is determined according to the request identifier.

[0024] In some embodiments, when the service invocation request includes a request identifier, determining whether to respond to the service invocation request according to the request identifier includes:

[0025] In a case where the request identifier is the first type of identifier assigned by the middle station, determining to respond to the service call request;

[0026] and / or,

[0027] In the case where the request identifier is not the first type of identifier assigned by the middle station, determine whether a mapping relationship is established between the request identifier and the first type of identifier assigned by the middle station by querying the mapping information; in the case where a mapping relationship is established between the request identifier and the first type of identifier assigned by the middle station, determine to respond to the service call request.

[0028] In some embodiments, the third-party application identifier includes: a third-party enterprise application identifier; the first type of identifier includes: an enterprise application identifier; wherein the mapping information indicates the first mapping relationship between the third-party enterprise application identifier and the enterprise application identifier;

[0029] or,

[0030] The third-party application identifier includes: a third-party enterprise application identifier and a third-party user application identifier; the first category of identifiers includes: an enterprise application identifier and a user application identifier; wherein the mapping information indicates the first mapping relationship between the third-party enterprise application identifier and the enterprise application identifier; and the mapping information indicates the first mapping relationship between the third-party user application identifier and the user application identifier.

[0031] In some embodiments, when the request identifier is the first type identifier assigned by the middle station, the method includes at least one of the following:

[0032] The request identifier is the enterprise application identifier; and / or,

[0033] The request identifier is the user application identifier, and the user application identifier belongs to the enterprise application identifier.

[0034] According to a second aspect of the present disclosure, there is provided a method for processing an identification for calling a middleware service, which is executed by a client and includes:

[0035] Sending a service call request; wherein the service call request includes a request identifier, and the request identifier is used by the middle station to determine whether to respond to the service call request;

[0036] Receive a service call response; wherein the service call response is returned by the middle station in response to the service call request, and the service call response includes the middle station service corresponding to the request identifier.

[0037] In some embodiments, the request identifier is used by the middle station to determine to respond to the service call request when it is the first type of identifier assigned by the middle station;

[0038] or,

[0039] The request identifier is used by the middle station to determine that it is not the first type identifier assigned by the middle station, and the request identifier is used by the middle station to determine that a mapping relationship is established with the first type identifier assigned by the middle station, and determine to respond to the service call request.

[0040] In some embodiments, the method comprises:

[0041] Receive mapping information, wherein the mapping information is established by the middle station to indicate a mapping relationship between a first type of identifier and a second type of identifier; the second type of identifier is an identifier involved in the target group calling the middle station service; the first type of identifier is allocated by the middle station;

[0042] The request identifier includes: the first type identifier.

[0043] In some embodiments, before receiving the mapping information, the process includes:

[0044] Send the second type of identification to the middle station; wherein the second type of identification includes: a third-party application identification or an SDK identification.

[0045] According to a third aspect of the present disclosure, there is provided an identification processing device for calling a middleware service, comprising:

[0046] An allocation module, used for allocating a first type of identification;

[0047] A determination module is used to determine the service calling method for the target user group to call the middle office service;

[0048] The determination module is used to determine whether the target user group's call of the middle platform service involves the second type of identification according to the service call mode; the processing module is used to establish the mapping information between the first type of identification and the second type of identification when it is determined that the middle platform service call involves the second type of identification;

[0049] The processing module is used to enable the target user group to call the middle platform service through the mapping information.

[0050] In some embodiments, the second type of identification includes: a third-party application identification;

[0051] The determination module is used to determine whether the target user group uses the third-party application identifier to call the middle office service when the service calling method is based on the user identifier; the mapping information indicates the first mapping relationship between the first type of identifier and the third-party application identifier.

[0052] In some embodiments, the determination module is used to determine whether the target user group uses the third-party application identifier to call the middle platform service according to the identification application requirement information when the service calling mode is the user identifier-based calling;

[0053] Alternatively, the determination module is used to determine whether the target user group uses the third-party application identifier to call the middle office service based on the receipt of the third-party application identifier in the process of allocating the first type of identifier when the service calling method is the user identifier-based call.

[0054] In some embodiments, the determination module is used to determine whether the target user group uses the second type of identifier to call the middle platform service when the service calling method is calling the SDK, and the second type of identifier is the identifier of the SDK;

[0055] The mapping information indicates a second mapping relationship between the SDK identifier and the first type of identifier.

[0056] In some embodiments, the device includes: a first sending module, used to send the mapping information to the client; wherein the mapping information is used for the client to call the middle office service based on the first type of identifier, or the mapping information is used for the client to call the middle office service based on the second type of identifier.

[0057] In some embodiments, the apparatus includes: a first receiving module, configured to receive a service invocation request;

[0058] The processing module is used to determine whether to respond to the service invocation request according to the request identifier when the service invocation request includes the request identifier.

[0059] In some embodiments, the processing module is used to determine to respond to the service call request when the request identifier is the first type identifier assigned by the middle station;

[0060] Alternatively, the processing module is used to determine whether a mapping relationship is established between the request identifier and the first type of identifier assigned by the middle station by querying the mapping information when the request identifier is not the first type of identifier assigned by the middle station; and to determine a response to the service call request when a mapping relationship is established between the request identifier and the first type of identifier assigned by the middle station.

[0061] In some embodiments, the third-party application identifier includes: a third-party enterprise application identifier; the first type of identifier includes: an enterprise application identifier; wherein the mapping information indicates the first mapping relationship between the third-party enterprise application identifier and the enterprise application identifier;

[0062] or,

[0063] The third-party application identifier includes: a third-party enterprise application identifier and a third-party user application identifier; the first type of identifier includes: an enterprise application identifier and a user application identifier; wherein the mapping information indicates the first mapping relationship between the third-party enterprise application identifier and the enterprise application identifier; and the mapping information indicates the first mapping relationship between the third-party user application identifier and the user application identifier.

[0064] In some embodiments, when the request identifier is the first type identifier assigned by the middle station, the method includes at least one of the following:

[0065] The request identifier is the enterprise application identifier; and / or,

[0066] The request identifier is the user application identifier, and the user application identifier belongs to the enterprise application identifier.

[0067] According to a fourth aspect of the present disclosure, there is provided an identification processing device for calling a middleware service, comprising:

[0068] A second sending module is used to send a service call request; wherein the service call request includes a request identifier, and the request identifier is used for the middle station to determine whether to respond to the service call request;

[0069] The second receiving module is used to receive a service call request; wherein the service call response is returned by the middle station in response to the service call request, and the service call response includes the middle station service corresponding to the request identifier.

[0070] In some embodiments, the request identifier is used by the middle station to determine to respond to the service call request when it is the first type of identifier assigned by the middle station;

[0071] Alternatively, the request identifier is used by the middle station to determine that it is not the first type of identifier assigned by the middle station, and the request identifier is used by the middle station to determine that a mapping relationship is established with the first type of identifier assigned by the middle station, and then determine to respond to the service call request.

[0072] In some embodiments, the second receiving module is used to receive mapping information, wherein the mapping information is established by the middle station to indicate a mapping relationship between a first type of identifier and a second type of identifier; the second type of identifier is an identifier involved in the target group calling the middle station service; the first type of identifier is assigned by the middle station; the first type of identifier is different from the first type of identifier;

[0073] The request identifier includes: the first type identifier.

[0074] In some embodiments, the second sending module is used to send the second type of identification to the middle station; wherein the second type of identification includes: a third-party application identification or an SDK identification.

[0075] According to a third aspect of an embodiment of the present disclosure, there is provided a mobile terminal, including:

[0076] processor;

[0077] a memory for storing processor-executable instructions;

[0078] Wherein, the processor is configured to: when running the executable instructions, implement the identification processing method for calling the middle platform service as described in any embodiment of the claims of the present disclosure.

[0079] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, wherein the readable storage medium stores an executable program, wherein when the executable program is executed by a processor, the identification processing method for calling a middleware service described in any embodiment of the present disclosure is implemented.

[0080] The technical solution provided by the embodiments of the present disclosure may have the following beneficial effects:

[0081] The disclosed embodiment is as follows: the middle station allocates a first type of identifier and determines the service calling method for the target user group to call the middle station service; and according to the service calling method, determines whether the target user group's call to the middle station service involves a second type of identifier; when it is determined that the middle station service call involves the second type of identifier, establishes mapping information between the first type of identifier and the second type of identifier; through the mapping information, the target user group can call the middle station service. In this way, the disclosed embodiment can establish mapping information between the second type of identifier that is not configured by the middle station and the first type of identifier configured by the middle station, so that the mapping information can be searched based on the second type of identifier to find the corresponding first type of identifier, and the middle station service can be called using the first type of identifier; that is, the mapping information can be used to make a call to the middle station service using a first type of identifier that is not assigned by the middle station (such as a second type of identifier).

[0082] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0083] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0084] Figure 1The present invention is a flowchart of an identification processing method for calling a middleware service according to an exemplary embodiment.

[0085] Figure 2 It is a schematic diagram of a technical architecture according to an exemplary embodiment.

[0086] Figure 3 The diagram is a schematic diagram of an architecture of mapping information according to an exemplary embodiment.

[0087] Figure 4 The present invention is a flowchart of an identification processing method for calling a middleware service according to an exemplary embodiment.

[0088] Figure 5 The present invention is a schematic diagram of a capability architecture for implementing SDK level according to an exemplary embodiment.

[0089] Figure 6 The present invention is a flowchart of an identification processing method for calling a middleware service according to an exemplary embodiment.

[0090] Figure 7 The present invention is a flowchart of an identification processing method for calling a middleware service according to an exemplary embodiment.

[0091] Figure 8 The figure is a schematic diagram of a processing method for calling a middleware service according to an exemplary embodiment.

[0092] Fig. 9 The present invention is a flowchart of an identification processing method for calling a middleware service according to an exemplary embodiment.

[0093] Fig.10 The present invention is a flowchart of an identification processing method for calling a middleware service according to an exemplary embodiment.

[0094] Fig.11 The present invention is a flowchart of an identification processing method for calling a middleware service according to an exemplary embodiment.

[0095] Fig.12 It is a schematic diagram showing a middle platform service integrated through an APP SDK according to an exemplary embodiment.

[0096] Fig.13 The figure is a schematic diagram showing a method of integrating middle platform services through a web page according to an exemplary embodiment.

[0097] Fig.14 The present invention is a block diagram of an identification processing device for calling a middleware service according to an exemplary embodiment.

[0098] Fig.15The present invention is a block diagram of an identification processing device for calling a middle platform service according to an exemplary embodiment.

[0099] Fig.16 The present invention is a block diagram of an identification processing device for calling a middleware service according to an exemplary embodiment.

[0100] Fig.17 The present invention is a block diagram of an identification processing device for calling a middle platform service according to an exemplary embodiment.

[0101] Fig.18 It is a block diagram of a middle platform according to an exemplary embodiment. DETAILED DESCRIPTION

[0102] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of devices and methods consistent with some aspects of the present invention as detailed in the appended claims.

[0103] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0104] like Figure 1 As shown, the embodiment of the present disclosure provides an identification processing method for calling a middle station service, which is executed by the middle station and includes:

[0105] Step S11: assigning a first type of identification;

[0106] Step S12: Determine the service calling method for the target user group to call the middle platform service;

[0107] Wherein, the target user group includes at least one target user;

[0108] Step S13: determining whether the target user group's calling of the middle platform service involves a second type of identification according to the service calling method;

[0109] wherein the second type of identification is different from the first type of identification;

[0110] Step S14: when it is determined that the middle platform service call involves the second type of identifier, establishing mapping information between the first type of identifier and the second type of identifier;

[0111] Step S15: The mapping information is used to allow the target user group to call the middle platform service.

[0112] Here, the mapping information is used for the target user group to call the middle platform service.

[0113] Here, the middle platform can be a unified interface service platform. For example, the middle platform can be a unified interface service platform formed by integrating or at least integrating at least one of the resources, data, platforms, technologies, tools, and businesses within the enterprise.

[0114] The middle platform can be supported by a platform; for example, the middle platform can provide shareable, reusable data, services, tools and / or components required by the business through various platforms.

[0115] Here, the middle platform can be any type of middle platform. For example, the middle platform can be any type of enterprise collaboration middle platform, which can modularize and process the capabilities of the office platform; for example, the middle platform A can include at least one of the capabilities of instant messaging, audio and video call capabilities, enterprise management background capabilities, enterprise self-built application workbench, and cloud document capabilities.

[0116] Here, the platform can be any platform. For example, the platform can be but not limited to at least one of the following: PaaS platform, IaaS platform, data governance platform, big data platform, data warehouse, message platform, algorithm platform, graphics and image processing platform, machine learning platform, application platform and service platform, etc. For another example, the platform can be a collaboration platform; the collaboration platform can integrate at least one of the capabilities of instant messaging capability, audio and video call capability, cloud document capability, enterprise internal application capability, and external service provider application capability.

[0117] For example, Figure 2 As shown, a schematic diagram of a technical architecture is provided; the technical architecture generally includes client integration, application layer, service layer, middleware and infrastructure. The middle platform generally includes service layer, middleware and infrastructure. Client integration can be but is not limited to at least one of mobile terminal integration, PC terminal integration and browser.

[0118] The application layer can be but is not limited to an instant messaging software development kit (Software Development Kit, SDK), an audio and video call SDK, document capabilities, an enterprise management background, an open platform, an enterprise management background and an open platform.

[0119] The services in the service layer corresponding to the instant messaging SDK of the application layer may be, but are not limited to: at least one of: multiple message types, group management, message management, and message security; the services in the service layer corresponding to the audio and video call SDK of the application layer may be, but are not limited to: at least one of: one-to-one and one-to-many; the services in the service layer corresponding to the document capabilities in the application may be, but are not limited to, at least one of document creation, interactive collaboration between documents and IM, document circulation, and document storage and management; the services in the service layer corresponding to the enterprise management background of the application layer may be, but are not limited to, at least one of address book management, role management, space management, document management, login security management, and enterprise system management; the services in the service layer corresponding to the open platform of the application layer may be, but are not limited to, at least one of the server-side application programming interface (API) and the client.

[0120] The middleware may be, but is not limited to, at least one of: search, cache, message middleware, operation and maintenance monitoring, storage, gateway, and service.

[0121] The infrastructure may be, but is not limited to, at least one of a physical machine, a virtual machine, and a third-party cloud platform.

[0122] Here, the target user group includes at least one or more target users. In the embodiment of the present disclosure, the plurality may be two or more than two.

[0123] Here, the target user group can be the target user corresponding to one client, or it can be the target user corresponding to the client. In the case where the target user group is the target user corresponding to multiple clients, there is no distinction between master and slave devices for the devices corresponding to the multiple clients. For example, in the case where the service is document collaboration, the instant messaging message is sent to three clients, and the three clients can receive the message synchronously. For another example, three clients that establish a connection and communication with the middle station can open an application at the same time.

[0124] Here, the middle platform service can be a service that the middle platform has. For example, the middle platform service can be, but is not limited to, an instant messaging service, an offline push service, an enterprise account service, an enterprise management service, a cloud document service, and an enterprise self-built application service. For another example, the middle platform service can be a service of any other capability; the capability can be, but is not limited to, the capability of integrating at least one of resources, data, platforms, technologies, tools, and businesses.

[0125] Here, the service calling method may be, but is not limited to, calling based on a user identification and / or calling an SDK.

[0126] Here, the first type of identifier is the identifier assigned by the middle office; the first type of identifier can be an internal account of the middle office.

[0127] In one embodiment, the first type of identification includes: enterprise application identification.

[0128] In yet another embodiment, the first type of identification includes: enterprise application identification and user application identification.

[0129] Here, the second type of identifier is an identifier that is not assigned by the middle platform; the second type of identifier can be an external identifier of the middle platform or an external account of the middle platform.

[0130] In one embodiment, the second type of identification includes a third-party application identification and / or an SDK identification.

[0131] In one embodiment, the mapping information is used for the target user group to call the middle office service based on the identifier. Here, calling the middle office service based on the identifier may be but is not limited to calling the middle office service based on the first type of identifier or the second type of identifier.

[0132] Here, the mapping information includes a first mapping relationship and / or a second mapping relationship.

[0133] In one embodiment, the mapping information indicates a first mapping relationship between the first type of identifier and the third-party application identifier.

[0134] In yet another embodiment, the mapping information indicates a second mapping relationship between the first type of identifier and the identifier of the SDK.

[0135] Exemplarily, the first type of identifier assigned by the middle station may be "company_uuid", the identifier of the SDK may be "SDK_1", and the third-party application identifier of the third-party application may be "app_userid". The first mapping relationship indicates the mapping relationship between "company_uuid" and "app_userid"; and the second mapping relationship indicates the relationship between "company_uuid" and "SDK_1"; the mapping information includes the first mapping relationship and / or the second mapping relationship.

[0136] In some embodiments, step S11 may be: the middle station uses the backend to allocate the first type of identification, wherein the backend is a component of the middle station; and step S14 establishes a mapping relationship between the first type of identification and the second type of identification, including: the middle station establishes mapping information between the first type of identification and the second type of identification. In this way, in the embodiment of the present disclosure, the backend in the middle station may be used to allocate the first type of identification.

[0137] In some embodiments, the third-party application identifier includes: a third-party enterprise application identifier; the first type of identifier includes: an enterprise application identifier; wherein the mapping information indicates the first mapping relationship between the third-party enterprise application identifier and the enterprise application identifier.

[0138] Exemplarily, the third-party application identifier of the third-party application may be “A_gognsi”, and the middle platform may assign an enterprise application identifier “A_company” to the third-party application identifier “A_gognsi”.

[0139] Here, the third-party application can be but is not limited to at least one of the following: any application (APP), mini-program, public account, web page, and desktop application. Here, the desktop application can be but is not limited to PC application and / or cloud desktop application. In one embodiment, the integration terminal can be used to integrate the above third-party applications.

[0140] In this way, in the present disclosed embodiment, the middle platform can assign a corresponding enterprise application identifier to the third-party enterprise application identifier in the third-party application identifier, so that when the client or the target user group logs in to the middle platform based on the enterprise application identifier assigned by the middle platform, the middle platform service corresponding to the enterprise application identifier can be scheduled.

[0141] In some further embodiments, the third-party application identifier includes: a third-party enterprise application identifier and a third-party user application identifier; the first category identifier includes: an enterprise application identifier and a user application identifier; wherein the mapping information indicates the first mapping relationship between the third-party enterprise application identifier and the enterprise application identifier; and the mapping information indicates the first mapping relationship between the third-party user application identifier and the user application identifier.

[0142] For example, the third-party user application identifier of the third-party application may be "app_userid", and the middle platform may assign a user application identifier "company_uuid" to "app_userid". Figure 3 As shown, the middle platform obtains the third-party application identifier "app_userid" in the third-party application, and imports the "app_userid" into the enterprise management backend in the enterprise collaboration middle platform, and generates a user application identifier "company_uuid" for the "app_userid"; the "company_uuid" can correspond to the IM service in the middle platform service. In this example, the middle platform can store the mapping information of the mapping relationship between "app_userid" and "company_uuid".

[0143] Here, the enterprise management backend is an independent management backend; the enterprise management backend already has online capabilities and can be used directly without integration.

[0144] In this way, in the present disclosed embodiment, the middle platform can assign a corresponding enterprise application identifier to the third-party enterprise application identifier in the third-party application identifier and assign a corresponding user application identifier corresponding to the enterprise application identifier to the third user application identifier under the third-party enterprise application identifier, so that when the client or the target user group logs in to the middle platform based on the enterprise application identifier assigned by the middle platform, the middle platform service corresponding to the enterprise application identifier can be scheduled, or when the client or the target user group logs in based on the user application identifier assigned by the middle platform, the middle platform service corresponding to the enterprise application identifier corresponding to the user application identifier can be scheduled.

[0145] In some embodiments, the first type of identification may correspond to at least one middle platform service in the middle platform. Here, the enterprise application identification in the first type of identification may correspond to at least one middle platform service in the middle platform.

[0146] Exemplarily, the middle station establishes and saves mapping information between the first type of identifier and the middle station service identifier; the mapping information indicates a third mapping relationship between the first type of identifier and the middle station service identifier. Here, a middle station service identifier is used to correspond to at least one middle station service; different middle station service identifiers correspond to different middle station services or middle station service combinations, and the middle station service combination is a combination of one or more middle station services.

[0147] Thus, in the disclosed embodiment, the middle station allocates the first type of identifier and determines the service calling method for the target user group to call the middle station service; and according to the service calling method, determines whether the target user group's call to the middle station service involves the second type of identifier; when it is determined that the call to the middle station service involves the second type of identifier, establishes mapping information between the first type of identifier and the second type of identifier; through the mapping information, the target user group can call the middle station service. Thus, the disclosed embodiment can establish mapping information between the second type of identifier that is not configured by the middle station and the first type of identifier configured by the middle station, so that the mapping information can be searched based on the second type of identifier to find the corresponding first type of identifier, and the middle station service can be called using the first type of identifier; that is, through the mapping information, the first type of identifier (such as the second type of identifier) ​​that is not allocated by the middle station can be used to call the middle station service.

[0148] In some embodiments, the second type of identification includes: a third-party application identification;

[0149] like Figure 4 As shown, the step S13 includes:

[0150] Step S131: when the service calling mode is based on user identification, determining whether the target user group uses the third-party application identification to call the middle platform service;

[0151] The mapping information indicates a first mapping relationship between the first type identifier and the third-party application identifier.

[0152] For example, please see again Figure 3 When the middle platform determines the third-party application identifier "app_userid" in the third-party application, the middle platform and the backend are used to generate the user application identifier "company_uuid" for "app_userid"; the middle platform stores mapping information indicating the first mapping relationship between "app_userid" and "company_uuid".

[0153] Thus, in the embodiment of the present disclosure, when the service call method is based on the user identification call, if it is determined that the target user group calls the middle office service involving a third-party application identification, a first mapping relationship between the first type of identification and the third-party application identification can be established. Thus, the embodiment of the present disclosure can realize the binding of the third-party application identification of the third-party application with the first type of identification allocated by the middle office (i.e., the middle office account system), so that when the client or the target user group calls the middle office service, at least one middle office service can be called to the third-party application for use, that is, the capabilities of the middle office can be directly embedded in the third-party application.

[0154] In some embodiments, the step S131 includes:

[0155] Step S1311: when the service calling mode is the calling based on the user identification, determining whether the target user group uses the third-party application identification to call the middle platform service according to the identification application requirement information;

[0156] or,

[0157] Step S1312: When the service calling method is the user ID-based calling, determine whether the target user group uses the third-party application ID to call the middle office service according to the situation of receiving the third-party application ID in the process of allocating the first type of ID.

[0158] Here, the identification application requirement information can be any information indicating the use of a third-party application identifier. The identification application requirement information can be obtained by the middle station from the client. For example, when the client sends a service call request, it can carry the request identifier and the application identification requirement information; in this way, the middle station can know whether to indicate the use of a third-party application identifier when calling the middle station service based on the user identifier based on the application requirement identification information.

[0159] In one embodiment, the step S1311 includes: when the service calling method is the user identifier-based calling and the identifier application requirement information indicates the use of the third-party application identifier, determining that the target user group uses the third-party application identifier to call the middle office service.

[0160] In another embodiment, the step S1311 includes: when the service calling method is the user identifier-based calling and the identifier application requirement information does not indicate the use of the third-party application identifier, determining that the target user group does not use the third-party application to call the middleware service.

[0161] Thus, in the disclosed embodiment, when the service calling method is based on user identification calling, it is possible to accurately determine whether the target user group uses a third-party application to call the middleware service based on the identification application requirement information to indicate whether to use a third-party application identification.

[0162] In one embodiment, the step S1312 includes: when the service calling method is the user identifier-based call and the third-party application identifier is received during the allocation of the first type of identifier, determining whether the target user group uses the third-party application identifier to call the middle office service.

[0163] In another embodiment, the step S132 includes: when the service calling method is the user identifier-based call and the third-party application identifier is not received during the allocation of the first type of identifier, determining that the target user group does not use the third-party application identifier to call the middle office service.

[0164] Here, the middle station receives the third-party application identifier sent by the client during the process of allocating the first-class identifier; thus, the middle station can allocate the corresponding first-class identifier to the third-party application identifier.

[0165] Thus, in the embodiment of the present disclosure, when the service calling method is based on the user identifier calling, it is possible to determine whether the target user group uses the third-party application identifier to call the middle office service based on whether the third-party application identifier is received during the allocation of the first category identifier. In the case where a third-party application identifier is received during the first category identification process, the corresponding first category identifier can be determined in a timely manner for the third-party application identifier. Thus, the embodiment of the present disclosure can also accurately determine whether the target user group uses the third-party application identifier to call the middle office service, and can effectively establish a mapping relationship between the third-party application identifier and the first category identifier.

[0166] Please see again Figure 4 In some embodiments, the step S13 includes:

[0167] Step S132: when the service calling method is calling SDK, determining that the target user group uses the second type of identifier to call the middle platform service, and the second type of identifier is the identifier of the SDK;

[0168] The mapping information indicates a second mapping relationship between the SDK identifier and the first type of identifier.

[0169] Here, the SDK integrates at least the following middle-office services: instant messaging service, cloud document service, workbench service, offline push service, enterprise account service, enterprise management service, and enterprise self-built applications.

[0170] Here, an SDK identifier corresponds to a third-party application identifier.

[0171] In one embodiment, the SDK identifier corresponds to the third-party user application identifier in the third application identifier. For example, an SDK identifier may correspond to an enterprise application identifier, an enterprise application identifier may correspond to a third-party user application identifier under a third-party enterprise application identifier, and it can be determined that an SDK identifier corresponds to a third-party user application identifier.

[0172] Here, a third-party application can carry at least one SDK. For example, an APP can carry N SDKs, where N is an integer greater than 1.

[0173] For example, Figure 5As shown, the SDK can be an instant messaging SDK (IMSDK), for example, it can be the instant messaging SDK of Company A (Kingsoft Company IM Software Development Kit, KCIM SDK); the IMSDK is used to implement enterprise cloud documents and / or enterprise workstations into an SDK-level capability architecture. The IMSDK mainly includes an instant messaging toolkit (IMKit), a plug-in, and an IMCore. In IMKit, there are several layers of view (View), event or state (Event / State), view controller (ViewController), and business model (Service (Model)). For example, here events can be generated by the event or state layer, data in the business model layer is passed through the formatter to the view controller layer, and the event or state layer outputs data to update the view. The plug-in introduces cloud documents and real-time communication (RTC), etc.; the RTC is real-time audio and video. The IMCore mainly includes IMCore Impl, servicetask, data wrapper, network, websocket, cache, cache bridge and foundation; Impl is used to store the implementation class of the interface. In this way, in the disclosed embodiment, the SDK can easily access cloud documents and real-time audio and video, and of course can also access other capabilities, such as workbench capabilities; the SDK provides multi-machine adaptation rendering and interaction capabilities for business view pages. The SDK can process business data communications through internal logic, and the SDK provides extension protocols to support customers to add customized business process processing.

[0174] For example, please see again Figure 3, a third-party application, such as an APP, can use the SDK identifier "IMSDK" to call the middle platform service; the SDK identifier "IMSDK" has a mapping relationship with the user application identifier "company_uuid". The middle platform can store mapping information indicating the second mapping relationship between "IMSDK" and "company_uuid". After the middle platform receives the identifier of the SDK of the APP sent by the third-party application, it can determine the first type of identifier corresponding to the SDK identifier based on the mapping information; such as determining the enterprise application identifier, and determining to call the corresponding middle platform service based on the enterprise application identifier; or such as determining the user application identifier, determining the enterprise application identifier based on the user application identifier, and determining to call the corresponding middle platform service based on the enterprise application identifier. The middle platform can find the third-party application identifier corresponding to the SDK based on the enterprise user identifier corresponding to the SDK identifier, such as "app_userid"; and return the middle platform service to the third-party application based on the third application identifier "app_userid".

[0175] Thus, in the embodiment of the present disclosure, when the service calling method is to call the SDK, when it is determined that the target user group uses the SDK to call the middle platform service, a second mapping relationship between the first type of identifier and the SDK can be established. In this way, the embodiment of the present disclosure can call the middle platform service of the middle platform by using the independent capabilities in the SDK, so that at least one middle platform service of the middle platform is integrated into the third-party application. And in the embodiment of the present disclosure, the third-party application does not need to use its own account or the account allocated by the middle platform corresponding to its own account to log in to the middle platform, thereby simplifying the processing process of the client or the target user group calling the middle platform service, that is, the middle platform service can be conveniently scheduled through the SDK.

[0176] In some embodiments, the method comprises:

[0177] The mapping information is sent to the client; wherein the mapping information is used for the client to call the middle office service based on the first type of identifier, or the mapping information is used for the client to call the middle office service based on the second type of identifier.

[0178] Here, when the service calling mode is based on user identification, the client can call the middle station service based on the first type of identification. For example, when the middle station receives the first type of identification sent by the client, the middle station service called by the client can be determined based on the first type of identification.

[0179] Here, when the service calling method is to call SDK, the client can call the middle platform service based on the second type of identifier. For example, when the middle platform receives the SDK identifier sent by the client, it can determine the first type of identifier corresponding to the SDK identifier based on the SDK identifier and mapping information; the mapping information is the second mapping relationship between the SDK identifier and the first type of identifier; the middle platform determines the middle platform service called by the client based on the first type of identifier.

[0180] Thus, in the disclosed embodiment, the middle station sends the mapping information to the client, so that the client can call the middle station service based on the first type of identifier or the second type of identifier in the mapping information. For example, the service calling method based on the user identifier can be used to call the middle station service using the first type of identifier; or the service calling method of the SDK can be called, such as calling the middle station service using the second type of identifier. In this way, the service calling method and the corresponding identifier can be used to call the service based on different service calling methods.

[0181] like Figure 6 As shown, in some embodiments, the method includes:

[0182] Step S21: receiving a service call request;

[0183] Step S22: When the service invocation request includes a request identifier, determining whether to respond to the service invocation request according to the request identifier.

[0184] In one embodiment, the request identifier may be a first type identifier. For example, the request identifier may be, but is not limited to, an enterprise application identifier and / or a user application identifier.

[0185] In another embodiment, the request identifier may be a second type identifier. For example, the request identifier may be an identifier of an SDK. At this time, the middle station may determine the second type identifier having mapping information with the first type identifier based on the second type identifier and mapping information, thereby responding to the service call request.

[0186] In another embodiment, the request identifier may also be a third-party application identifier in the second category of identifiers. For example, the request identifier may be a third-party enterprise application identifier and / or a third-party user application identifier.

[0187] Of course, in other embodiments, the request identifier may be other intended identifiers other than the first type identifier and the second type identifier. At this time, the middle station may not respond to the service call request.

[0188] Here, determining whether to respond to the service call request according to the request identifier in step S22 includes: determining to respond to the service call request according to the request identifier; or determining not to respond to the service call request according to the request identifier.

[0189] Here, determining to respond to the service call request according to the request identifier may be: determining to allow the call of the middle station service corresponding to the request identifier. Alternatively, determining to respond to the service call request according to the request identifier may be: determining to allow the call of the middle station service corresponding to the request identifier; and sending a service call response, wherein the service call response includes: the middle station service corresponding to the request identifier.

[0190] Thus, in the disclosed embodiment, the middle platform can accurately determine whether to respond to the service call request based on the request identifier contained in the received service call request; if it is determined to respond to the service call request, the call to the middle platform service can be realized. This can solve the problem that the third-party application itself cannot integrate the capabilities of the middle platform at the enterprise level of the middle platform, and can make at least one middle platform service in the middle platform freely integrated with the third-party application; thereby realizing the integration of enterprise-level capabilities.

[0191] like Figure 7 As shown, in some embodiments, the S22 includes:

[0192] Step S221: when the request identifier is the first type identifier assigned by the middle station, determine to respond to the service call request;

[0193] or,

[0194] Step S222: When the request identifier is not the first type of identifier assigned by the middle station, determine whether a mapping relationship is established between the request identifier and the first type of identifier assigned by the middle station by querying the mapping information; when a mapping relationship is established between the request identifier and the first type of identifier assigned by the middle station, determine to respond to the service call request.

[0195] In some embodiments, in step S221, when the request identifier is the first type identifier assigned by the middle station, the step includes at least one of the following:

[0196] The request identifier is the enterprise application identifier; and / or,

[0197] The request identifier is the user application identifier, and the user application identifier belongs to the enterprise application identifier.

[0198] Exemplarily, the middle station receives a service call request sent by the client, and when it is determined that the service call request includes an enterprise application identifier, determines to respond to the service call request. The middle station returns a service call response to the client, and the service call response includes the middle station service corresponding to the enterprise application identifier.

[0199] Exemplarily, the middle station receives a service call request sent by the client, and when it is determined that the service call request contains a user application identifier, it queries the corresponding enterprise application identifier based on the user application identifier, and determines to respond to the service call request based on the enterprise application identifier. The middle station returns a service call response to the client, and the service call response includes the middle station service corresponding to the enterprise application identifier.

[0200] Thus, in the embodiment of the present disclosure, when the service request identifier is a first-class identifier assigned by the middle station, the response to the service call request can be determined directly based on the first-class identifier.

[0201] Exemplarily, the middle station receives a service call request sent by the client, and when it is determined that the service call request contains the identification information of the SDK, the first type of identification information is determined based on the SDK identification information and the mapping information indicating the second mapping relationship between the SDK and the first type of identification; the middle station determines to respond to the service call request based on the first type of identification. The middle station returns the service call response to the client, and the service call response includes the middle station service corresponding to the enterprise application identification.

[0202] Exemplarily, the middle station receives a service call request sent by the client, and when it is determined that the service call request includes a third-party application identifier, the middle station determines the first type of identifier information based on the third-party application identifier and the mapping information indicating the first mapping relationship between the third-party application identifier and the first type of identifier; the middle station determines to respond to the service call request based on the first type of identifier. The middle station returns the service call response to the client, and the service call response includes the middle station service corresponding to the enterprise application identifier.

[0203] Thus, in the embodiment of the present disclosure, when the service call request is not a first-class identifier assigned by the middle station and is a second-class identifier having a mapping relationship with the first-class identifier, the first-class identifier can be determined based on the second-class identifier and the mapping information indicating the mapping relationship; thereby determining a response to the service call request.

[0204] Here, the middle station will also perform authorization verification on the first type of identification before determining to respond to the service call request based on the first type of identification. For example, it is determined by a whitelist whether the first type of identification is an authorization identification for authorizing the call of the middle station service.

[0205] In some embodiments, determining to respond to the service call request in step S22 includes: if it is determined that the first type of identifier is an authorization identifier, determining to respond to the service call request.

[0206] In some embodiments, determining that the first type of identification is an authorization identification includes:

[0207] If the first type of identifier in the service call request is the enterprise application identifier present in the whitelist of the middle station, determine the enterprise user identifier as an authorized identifier, wherein the whitelist stores at least one enterprise application identifier authorized to call the middle station service;

[0208] If the first type of identifier included in the service call belongs to the enterprise application identifier in the whitelist, the user application identifier is determined to be an authorized identifier.

[0209] In this way, in the disclosed example, verification of the enterprise application identifier and verification of the user application identifier under the enterprise application identifier can be achieved; thereby accurately determining whether the received first-class identifier including the enterprise application identifier and / or the user application identifier is the first-class identifier in the whitelist authorized to call the middle office service.

[0210] like Figure 8 As shown, the embodiment of the present disclosure provides a schematic diagram of a method for processing a middle platform service call, and the method for processing a middle platform service call may be: first, the enterprise version capabilities are integrated, such as enterprise documents, enterprise management backends, enterprise workbenches, and open capabilities; secondly, a mapping relationship is established, a mapping relationship between the first type of identifier and the second type of identifier is established, and it is determined whether the user application identifier is restricted to the enterprise application identifier; then, when it is determined that the user application identifier is restricted to the enterprise application identifier, the enterprise collaboration middle platform instant messaging service is called. Here, the execution of calling the enterprise collaboration middle platform instant messaging service may include but is not limited to: the enterprise collaboration middle platform receives HTTP sent by a third-party business, and the HTTP carries the requested instant messaging service; the middle platform pushes the instant messaging service; the middle platform integrates the instant messaging service into a third application for use, and the third-party application may be but is not limited to mobile phone, PC, browser and other applications.

[0211] In the embodiment of the present disclosure, the execution of calling the middle platform service instant messaging service can refer to any of the above embodiments. In addition, in other embodiments, calling any middle platform service in the middle platform can also be implemented.

[0212] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0213] The following identification processing method for calling the middle office service is executed by the client, and is similar to the description of the identification processing method for calling the middle office service executed by the middle office. Moreover, for technical details not disclosed in the embodiment of the identification processing method for calling the middle office service executed by the client, please refer to the description of the example of the identification processing method for calling the middle office service executed by the middle office, and no detailed description is given here.

[0214] like Fig. 9 As shown, a method for processing an identification for calling a middle platform service is provided, which is executed by a client and includes:

[0215] Step S31: Send a service call request; wherein the service call request includes a request identifier, and the request identifier is used by the middle station to determine whether to respond to the service call request;

[0216] Step S32: receiving a service call response; wherein the service call response is returned by the middle station in response to the service call request, and the service call response includes the middle station service corresponding to the request identifier.

[0217] In some embodiments, the request identifier is used by the middle station to determine to respond to the service call request when it is the first type of identifier assigned by the middle station;

[0218] or,

[0219] The request identifier is used by the middle station to determine that it is not the first type of identifier assigned by the middle station, and the request identifier is used by the middle station service to determine that a mapping relationship is established with the first type of identifier assigned by the middle station, and determine to respond to the service call request.

[0220] Here, a middle platform service can be represented by a middle platform service identifier. If the request identifier is a first-class identifier, it can be based on the middle platform service identifier corresponding to the first-class identifier; here, the middle platform establishes and saves the third mapping relationship between the first-class identifier and the middle platform service identifier. If the request identifier is not a first-class identifier, the second-class identifier can be determined based on the first-class identifier and the mapping information; wherein, if the second-class identifier is a third-party application identifier, the middle platform service identifier corresponding to the third application identifier can be determined based on the third application identifier, and / or, if the second-class identifier is an SKD identifier, the middle platform service identifier corresponding to the SDK identifier can be determined based on the SDK identifier; here, the middle platform establishes and saves the third mapping relationship between the third-party application identifier and the middle platform service identifier, and / or, the middle platform establishes and saves the third mapping relationship between the SDK identifier and the middle platform service identifier. In this way, the middle platform service indicated by the corresponding middle platform service identifier can be called through the request identifier.

[0221] In some embodiments of the present disclosure, the first type of identification and the second type of identification may be the first type of identification and the second type of identification in the above embodiments, respectively. Exemplarily, here, the first type of identification is an identification assigned by the middle station.

[0222] In one embodiment, the first type of identification includes: enterprise application identification.

[0223] In yet another embodiment, the first type of identification includes: enterprise application identification and user application identification.

[0224] Here, the second type of identifier is an identifier that is not allocated by the middle station.

[0225] In one embodiment, the second type of identification includes a third-party application identification and / or an SDK identification.

[0226] In some embodiments, the method comprises:

[0227] Step S30: receiving mapping information; wherein the mapping information is established by the middle station to indicate a mapping relationship between a first type of identifier and a second type of identifier; the second type of identifier is an identifier involved in the target group calling the middle station service; the first type of identifier is allocated by the middle station; the first type of identifier is different from the first type of identifier; the target user group includes at least one target user;

[0228] The request identifier includes: the first type identifier.

[0229] In some embodiments of the present disclosure, the mapping information may be the mapping information in the above embodiments.

[0230] In one embodiment, the mapping information indicates a first mapping relationship between the first type of identifier and the third-party application identifier.

[0231] In yet another embodiment, the mapping information indicates a second mapping relationship between the first type of identifier and the identifier of the SDK.

[0232] In one embodiment, the third-party application identifier includes: a third-party enterprise application identifier; the first type of identifier includes: an enterprise application identifier; wherein the mapping information indicates the first mapping relationship between the third-party enterprise application identifier and the enterprise application identifier.

[0233] In another embodiment, the third-party application identifier includes: a third-party enterprise application identifier and a third-party user application identifier; the first type of identifier includes: an enterprise application identifier and a user application identifier; wherein the mapping information indicates the first mapping relationship between the third-party enterprise application identifier and the enterprise application identifier; and the mapping information indicates the first mapping relationship between the third-party user application identifier and the user application identifier.

[0234] Here, after receiving the mapping information, a service call request including a first type identifier may be sent based on the mapping information. The first type identifier is the request identifier in step S31.

[0235] Of course, in other embodiments, after receiving the mapping information, a service call request carrying the second type of identifier may be sent based on the mapping information; the second type of identifier is the request identifier in step S31.

[0236] In some embodiments, before receiving the mapping information in step S30, the process includes:

[0237] Send the second type of identification to the middle station; wherein the second type of identification includes: a third-party application identification or an SDK identification.

[0238] Here, before receiving the mapping information, the client sends the second type of identifier to the middle station, which is beneficial for the middle station to allocate the first type of identifier based on the second type of identifier and establish a mapping relationship between the first type of identifier and the second type of identifier.

[0239] For the above implementation methods, please refer to the description on the middle platform side, which will not be repeated here.

[0240] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0241] In order to further explain any embodiment of the present disclosure, several specific embodiments are provided below.

[0242] Example 1

[0243] like Fig.10 As shown, the embodiment of the present disclosure provides a method for processing a middle station service call, which is executed by a device, and the device includes a middle station and a client; and includes the following steps:

[0244] Step S41: the client sends the second type of identification to the middle station;

[0245] In an optional embodiment, the second type of identification may be a third-party application identification.

[0246] In another optional embodiment, the second type of identification may be an identification of a SDK.

[0247] Step S42: the middle station allocates the first type of identification;

[0248] In an optional embodiment, the middle station allocates the first type of identifier to the second type of identifier.

[0249] Step S43: The middle station determines the service calling method for calling the main station service;

[0250] In an optional embodiment, the middle platform determines a service calling method for the target user group to call the middle platform service.

[0251] Step S44: The middle platform determines whether calling the middle platform service involves the second type of identification according to the service calling method;

[0252] In an optional embodiment, the middle platform determines whether the target user group's call to the middle platform service involves the second type of identification based on the service call method.

[0253] Step S45: When the middle station determines that the middle station service call involves the second type of identification, the middle station establishes mapping information between the first type of identification and the second type of identification;

[0254] Step S46: The middle station sends the mapping information to the client;

[0255] Step S47: the client sends a service call request, wherein the service call request includes a request identifier;

[0256] Step S48: If the middle station determines the request identifier, it determines whether to respond to the service call request;

[0257] In an optional embodiment, if the middle station determines that the request identifier is a first type of identifier assigned by the middle station, it determines to respond to the service call request.

[0258] In another optional embodiment, if the middle station determines that the request identifier is not the first type of identifier assigned by the middle station, and determines whether the request identifier has a mapping relationship with the first type of identifier assigned by the middle station by querying the mapping information; if the request identifier has a mapping relationship with the first type of identifier assigned by the middle station, determine to respond to the service call request.

[0259] Step S49: Send a service call response, wherein the service call response includes the middle platform service corresponding to the first type of identifier.

[0260] In this way, in the present disclosed embodiment, the client can send the first type of identification (the third-party application identification of the third-party application or the identification of the SDK in the APP of the third-party application) to the middle platform to be assigned the first type of identification under the middle platform; thereby, the middle platform service of the middle platform can be scheduled based on the first type of identification, thereby realizing the free integration of enterprise-level middle platform services and third-party applications.

[0261] Furthermore, in the disclosed embodiment, the service calling method based on the user identifier can be used, such as directly calling the middle platform service based on the first type of identifier corresponding to the third application identifier or based on the first type of identifier. Alternatively, the middle platform service of the middle platform can be integrated into the SDK through the service calling method based on the SDK, so that the middle platform service of the middle platform can also be called.

[0262] Example 2

[0263] like Fig.11As shown, the embodiment of the present disclosure provides a schematic diagram of integrating the middle-end service through the SDK of the APP. Target user A (such as a field staff) conducts instant messaging with at least one target user B (such as an office staff); the instant messaging service can be integrated into the predetermined page entrance in the APP through the APP in the mobile phone of the target user A and / or the target user B; if the mobile phone detects a click operation acting on the predetermined page entrance, the login process is triggered. After the mobile phone detects that the login process has passed, it presents the chat page developed by the instant messaging SDK, and determines the single chat or group chat session based on the input SDK identifier.

[0264] Here, the toolbars of "Chat", "Cloud Document", and "Application" can be displayed on the instant messaging page respectively. Among them, "Cloud Document" can quickly generate sharing links; for example, one-click sharing to a group chat or a single chat session. "Application" corresponds to the enterprise's self-built application; the enterprise's self-built application can realize the business scenario of process communication to people through the push API provided by KCIM SDK.

[0265] In this way, the embodiments of the present disclosure can realize middle-office services such as instant messaging services, cloud document services, and enterprise self-built application services through APP integration.

[0266] Example 3

[0267] like Fig.12 and Fig.13 As shown, an embodiment of the present disclosure provides a schematic diagram of integrating middle-end services through a web page. The client of the target user C has a web version of an enterprise application platform; the instant messaging service of the enterprise collaboration platform and the enterprise's self-built applications and other services are embedded in the application of the predetermined web page of the computer of the target user C. For example, the computer detects a click on the predetermined web page and triggers the login process. After the computer detects that the login process has passed, it can determine the instant messaging dialog box based on the first type of identifier input; the dialog box in the instant messaging includes application name message content, person name message content, and group name message content, etc. If it is detected that the message content acts on the application name, the columns of the application name and the message content can be displayed respectively.

[0268] In this way, the disclosed embodiment can realize the middle-office instant messaging service and the middle-office service of the enterprise self-built application through the web page integration. Moreover, in the terminal, if you do not want to install a new APP, in order to realize the middle-office services such as instant messaging, you can embed these middle-office services inside the application on the web page for calling; in this way, you can directly embed the use of the middle-office service through the web page, thereby saving data sending and receiving time and improving calling efficiency.

[0269] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0270] like Fig.14 The present disclosure provides an identification processing device for calling a middleware service, including:

[0271] An allocation module 51, configured to allocate a first type of identification;

[0272] A determination module 52 is used to determine the service calling method for the target user group to call the middle platform service;

[0273] The determination module 52 is used to determine whether the target user group calling the middle platform service involves a second type of identification according to the service calling method;

[0274] A processing module 53 is used to establish mapping information between the first type of identification and the second type of identification when it is determined that the middle station service call involves the second type of identification;

[0275] The processing module 53 is used to enable the target user group to call the middle platform service through the mapping information.

[0276] Here, the target user group includes at least one target user.

[0277] Here, the second type of identification is different from the first type of identification.

[0278] In some embodiments, the second type of identification includes: a third-party application identification;

[0279] The determination module 52 is used to determine whether the target user group uses the third-party application identifier to call the middle platform service when the service calling method is based on the user identifier; the mapping information indicates the first mapping relationship between the first type of identifier and the third-party application identifier.

[0280] In some embodiments, the determination module 52 is used to determine whether the target user group uses the third-party application identifier to call the middle platform service according to the identification application requirement information when the service calling mode is the user identifier-based calling;

[0281] Alternatively, the determination module 52 is used to determine whether the target user group uses the third-party application identifier to call the middle office service based on the receipt of the third-party application identifier in the process of allocating the first type of identifier when the service calling method is the user identifier-based call.

[0282] In some embodiments, the determination module 52 is used to determine that the target user group uses the third-party application identifier to call the middle platform service when the service calling mode is the user identifier-based calling and the identifier application requirement information indicates the use of the third-party application identifier;

[0283] Alternatively, the determination module 52 is used to determine that the target user group does not use the third-party application identifier to call the middle platform service when the service calling mode is the user identifier-based calling and the identifier application requirement information does not indicate the use of the third-party application identifier.

[0284] In some embodiments, the determination module 52 is used to determine that the target user group uses the third-party application identifier to call the middle platform service when the service calling mode is the user identifier-based calling and the third-party application identifier is received during the allocation of the first type of identifier;

[0285] Alternatively, the determination module 52 is used to determine that the target user group does not use the third-party application identifier to call the middle platform service when the service calling method is the user identifier-based call and the third-party application identifier is not received during the allocation of the first type of identifier.

[0286] In some embodiments, the determination module 52 is used to determine that the target user group uses the second type of identification information to call the middle platform service when the service calling method is calling the SDK, and the second type of identification is the identification of the SDK;

[0287] The mapping information indicates a second mapping relationship between the SDK identifier and the first type of identifier.

[0288] like Fig.15 As shown, in some embodiments, the device includes: a first sending module 54, used to send the mapping information to the client; wherein the mapping information is used for the client to call the middle office service based on the first type of identifier, or the mapping information is used for the client to call the middle office service based on the second type of identifier.

[0289] like Fig.16 As shown, in some embodiments, the apparatus includes: a first receiving module 55, configured to receive a service invocation request;

[0290] The processing module 53 is used to determine whether to respond to the service invocation request according to the request identifier when the service invocation request includes the request identifier.

[0291] In some embodiments, the processing module 53 is used to determine to respond to the service call request when the request identifier is the first type identifier assigned by the middle station;

[0292] Alternatively, the processing module 53 is used to determine whether a mapping relationship is established between the request identifier and the first type of identifier assigned by the middle station by querying the mapping information when the request identifier is not the first type of identifier assigned by the middle station; and to determine a response to the service call request when a mapping relationship is established between the request identifier and the first type of identifier assigned by the middle station.

[0293] In some embodiments, the third-party application identifier includes: a third-party enterprise application identifier; the first type of identifier includes: an enterprise application identifier; wherein the mapping information indicates the first mapping relationship between the third-party enterprise application identifier and the enterprise application identifier;

[0294] or,

[0295] The third-party application identifier includes: a third-party enterprise application identifier and a third-party user application identifier; the first category of identifiers includes: an enterprise application identifier and a user application identifier; wherein the mapping information indicates the first mapping relationship between the third-party enterprise application identifier and the enterprise application identifier; and the mapping information indicates the first mapping relationship between the third-party user application identifier and the user application identifier.

[0296] In some embodiments, when the request identifier is the first type identifier assigned by the middle station, the method includes at least one of the following:

[0297] The request identifier is the enterprise application identifier; and / or,

[0298] The request identifier is the user application identifier, and the user application identifier belongs to the enterprise application identifier.

[0299] like Fig.17 As shown, the embodiment of the present disclosure provides an identification processing device for calling a middle platform service, including:

[0300] The second sending module 61 is used to send a service call request; wherein the service call request includes a request identifier, and the request identifier is used for the middle station to determine whether to respond to the service call request;

[0301] The second receiving module 62 is used to receive a service call response; wherein the service call response is returned by the middle station in response to the service call request, and the service call response includes the middle station service corresponding to the request identifier.

[0302] In some embodiments, the request identifier is used by the middle station to determine to respond to the service call request when it is the first type of identifier assigned by the middle station;

[0303] Alternatively, the request identifier is used by the middle station to determine that it is not the first type of identifier assigned by the middle station, and the request identifier is used by the middle station to determine that a mapping relationship is established with the first type of identifier assigned by the middle station, and then determine to respond to the service call request.

[0304] In some embodiments, the second receiving module 62 is used to receive mapping information, wherein the mapping information is established by the middle station to indicate a mapping relationship between a first type of identifier and a second type of identifier; the second type of identifier is an identifier involved in the target group calling the middle station service; the first type of identifier is allocated by the middle station;

[0305] The request identifier includes: the first type identifier.

[0306] Here, the first type of identification is different from the first type of identification; the target user group includes at least one target user;

[0307] In some embodiments, the second sending module 61 is used to send the second type of identification to the middle station; wherein the second type of identification includes: a third-party application identification or an SDK identification.

[0308] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0309] The embodiment of the present disclosure further provides a device, characterized in that it includes:

[0310] processor;

[0311] a memory for storing processor-executable instructions;

[0312] The processor is configured to: when running the executable instructions, implement the identification processing of calling the middleware service as described in any embodiment of the present disclosure.

[0313] The device may be, but is not limited to, a terminal and / or a middle station.

[0314] The memory may include various types of storage media, which are non-transitory computer storage media that can continue to memorize information stored thereon after the communication device loses power.

[0315] The processor may be connected to the memory through a bus or the like, and is used to read the executable program stored in the memory, for example, to implement the following Figure 1 , Figure 4 , Figure 6 , Figure 7 , Figures 9 to 11 At least one of the methods shown.

[0316] The embodiment of the present disclosure further provides a computer-readable storage medium, wherein the readable storage medium stores an executable program, wherein the executable program, when executed by a processor, implements the identification processing of calling the middle platform service described in any embodiment of the present disclosure. Figure 1 , Figure 4 , Figure 6 , Figure 7 , Figures 9 to 11 At least one of the methods shown.

[0317] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0318] like Fig.18 FIG. 1 is a diagram showing a structure of a middle station 70 according to an exemplary embodiment. For example, the middle station 70 may be provided as a network side device. Fig.18 The middle station 70 includes a processing component 71, which further includes one or more processors, and a memory resource represented by a memory 72 for storing instructions executable by the processing component 71, such as an application. The application stored in the memory 72 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 71 is configured to execute instructions to perform any method of the aforementioned method applied to the base station.

[0319] The middle platform 70 may also include a power component 73 configured to perform power management of the middle platform 70, a wired or wireless network interface 74 configured to connect the middle platform 70 to a network, and an input / output (I / O) interface 75. The middle platform 70 may operate based on an operating system stored in the memory 72, such as Windows Server TM, Mac OS X TM, Unix TM, Linux TM, FreeBSD TM or the like.

[0320] Those skilled in the art will readily appreciate other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses or adaptations of the present invention that follow the general principles of the present invention and include common knowledge or customary techniques in the art that are not disclosed in this disclosure. The specification and examples are to be considered exemplary only, and the true scope and spirit of the present invention are indicated by the following claims.

[0321] It should be understood that the present invention is not limited to the exact construction that has been described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A method for processing an identification for calling a middle office service, characterized in that: Executed by the middle office, including: assigning first-class identification; Determine the service calling method for the target user group to call the middle office service; Determining whether the target user group's calling of the middle station service involves the second type of identification according to the service calling method; the second type of identification is not an identification assigned by the middle station; determining whether the target user group's calling of the middle station service involves the second type of identification according to the service calling method includes: when the service calling method is calling SDK, determining that the target user group uses the second type of identification to call the middle station service, and the second type of identification is the identification of the SDK; In the case where it is determined that the middle station service call involves the second type of identification, establishing mapping information between the first type of identification and the second type of identification; the mapping information indicates a second mapping relationship between the identification of the SDK and the first type of identification; The mapping information is used by the target user group to call the middle platform service.

2. The method according to claim 1, characterized in that The second category of identification includes: third-party application identification; The determining, according to the service calling mode, whether the target user group calling the middle platform service involves a second type of identification includes: When the service calling method is based on user identification, determine whether the target user group uses the third-party application identification to call the middle office service; the mapping information indicates a first mapping relationship between the first type of identification and the third-party application identification.

3. The method according to claim 2, characterized in that When the service calling mode is based on user identification calling, determining whether the target user group uses the third-party application identification to call the middle platform service includes: In the case where the service calling mode is the calling based on the user identification, determining whether the target user group uses the third-party application identification to call the middle platform service according to the identification application requirement information; or, In the case where the service calling mode is the user identifier-based calling, it is determined whether the target user group uses the third-party application identifier to call the middle platform service according to the situation of receiving the third-party application identifier in the process of allocating the first type of identifier.

4. The method according to claim 1, characterized in that The method comprises: The mapping information is sent to the client; wherein the mapping information is used for the client to call the middle office service based on the first type of identifier, or the mapping information is used for the client to call the middle office service based on the second type of identifier.

5. The method according to claim 1, characterized in that The method comprises: Receive service call request; In the case that the service invocation request includes a request identifier, whether to respond to the service invocation request is determined according to the request identifier.

6. The method according to claim 5, characterized in that When the service call request includes a request identifier, determining whether to respond to the service call request according to the request identifier includes: In a case where the request identifier is the first type of identifier assigned by the middle station, determining to respond to the service call request; and / or, In the case where the request identifier is not the first type of identifier assigned by the middle station, determine whether a mapping relationship is established between the request identifier and the first type of identifier assigned by the middle station by querying the mapping information; in the case where a mapping relationship is established between the request identifier and the first type of identifier assigned by the middle station, determine to respond to the service call request.

7. The method according to claim 6, characterized in that When the request identifier is the first type of identifier assigned by the middle station, the method includes at least one of the following: The request identifier is an enterprise application identifier; and / or, The request identifier is a user application identifier, and the user application identifier belongs to the enterprise application identifier.

8. The method according to claim 2, characterized in that: The third-party application identifier includes: a third-party enterprise application identifier; the first type of identifier includes: an enterprise application identifier; wherein the mapping information indicates a first mapping relationship between the third-party enterprise application identifier and the enterprise application identifier; or, The third-party application identifier includes: a third-party enterprise application identifier and a third-party user application identifier; the first type of identifier includes: an enterprise application identifier and a user application identifier; wherein the mapping information indicates the first mapping relationship between the third-party enterprise application identifier and the enterprise application identifier; and the mapping information indicates the first mapping relationship between the third-party user application identifier and the user application identifier.

9. A method for processing an identification for calling a middle office service, characterized in that: Executed by the client, including: Send a service call request; wherein the service call request includes a request identifier, and the request identifier is used for the middle station to determine whether to respond to the service call request when the first type of identifier is assigned by the middle station; the first type of identifier is used for the middle station to establish mapping information between the first type of identifier and the second type of identifier when it is determined that the middle station service call involves the second type of identifier; whether the middle station service call involves the second type of identifier is determined by the middle station based on the service call method of the target user group calling the middle station service, and when the service call method is to call the SDK, the middle station is used to determine that the target user group uses the second type of identifier to call the middle station service, and the second type of identifier is the identifier of the SDK; the mapping information is used for the target user group to call the middle station service, and the mapping information indicates the second mapping relationship between the SDK identifier and the first type of identifier; the second type of identifier is not an identifier assigned by the middle station; Receive a service call response; wherein the service call response is returned by the middle station in response to the service call request, and the service call response includes the middle station service corresponding to the request identifier.

10. The method according to claim 9, characterized in that The request identifier is used by the middle station to determine to respond to the service call request when it is the first type of identifier assigned by the middle station; or, The request identifier is used by the middle station to determine that it is not the first type identifier assigned by the middle station, and the request identifier is used by the middle station to determine that a mapping relationship is established with the first type identifier assigned by the middle station, and determine to respond to the service call request.

11. The method according to claim 9 or 10, characterized in that: The method comprises: Receive mapping information, wherein the mapping information is established by the middle station to indicate a mapping relationship between a first type of identifier and a second type of identifier; the second type of identifier is an identifier involved in the target user group calling the middle station service; the first type of identifier is allocated by the middle station; the request identifier includes: the first type of identifier.

12. The method according to claim 11, characterized in that Before receiving the mapping information, the method includes: Send the second type of identification to the middle station; wherein the second type of identification includes: a third-party application identification or an SDK identification.

13. An identification processing device for calling a middle platform service, characterized in that: include: An allocation module, used for allocating a first type of identification; A determination module is used to determine the service calling method for the target user group to call the middle office service; The determination module is used to determine whether the target user group's call to the middle station service involves a second type of identifier according to the service call method; the second type of identifier is not an identifier assigned by the middle station; wherein the determination module is specifically used to determine that the target user group uses the second type of identifier to call the middle station service when the service call method is to call the SDK, and the second type of identifier is the identifier of the SDK; A processing module, configured to establish mapping information between the first type of identification and the second type of identification when it is determined that the middle station service call involves the second type of identification; the mapping information indicates a second mapping relationship between the identification of the SDK and the first type of identification; The processing module is used to enable the target user group to call the middle platform service through the mapping information.

14. An identification processing device for calling a middle platform service, characterized in that: include: A second sending module is used to send a service call request; wherein, the service call request includes a request identifier, and the request identifier is used for the middle station to determine whether to respond to the service call request when the first type of identifier is assigned by the middle station; the first type of identifier is used for the middle station to establish mapping information between the first type of identifier and the second type of identifier when it is determined that the middle station service call involves the second type of identifier; whether the middle station service call involves the second type of identifier is determined by the middle station based on the service call method of the target user group calling the middle station service, and when the service call method is to call the SDK, the middle station is used to determine that the target user group uses the second type of identifier to call the middle station service, and the second type of identifier is the identifier of the SDK; the mapping information is used for the target user group to call the middle station service, and the mapping information indicates the second mapping relationship between the SDK identifier and the first type of identifier; the second type of identifier is not an identifier assigned by the middle station; The second receiving module is used to receive a service call response; wherein the service call response is returned by the middle station in response to the service call request, and the service call response includes the middle station service corresponding to the request identifier.

15. A device, characterized in that include: processor; a memory for storing processor-executable instructions; Wherein, the processor is configured to: when running the executable instructions, implement the identification processing method for calling the middle platform service as described in any one of claims 1-8 or claims 9-12.

16. A computer-readable storage medium, characterized in that: The readable storage medium stores an executable program, wherein the executable program, when executed by a processor, implements the identification processing method for calling the middle platform service as described in any one of claims 1-8 or claims 9-12.

Images