CN115633082A - Identification processing method, device, equipment and storage medium for calling middlebox service - Google Patents

Abstract

An embodiment of the present disclosure provides an identification processing method for invoking a middle platform service, which is executed by the middle platform, including: allocating the first type of identification; determining the service calling method for the target user group to call the middle platform service; determining the service calling method according to the service calling method Whether the target user group calls the middle station service involves a second type of identification; if it is determined that the middle station service call involves the second type of identification, establish the first type of identification and the second type Mapping information between identifiers; through the mapping information, the target user group can call the middle station service. Embodiments of the present disclosure also provide an identification processing device, equipment, and storage medium for invoking a middle platform service.

Description

Identification processing method, device, equipment and storage medium for invoking middle platform services

technical field

The present disclosure relates to but is not limited to the technical field of data processing, and in particular relates to an identification processing method, device, equipment and storage medium for invoking middle platform services.

Background technique

With the continuous development of terminals and Internet technologies, the platform can provide various technical support for different business forms; at present, some overall services of the office platform 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 can solve more business, data and technology relationships through the middle platform. However, at present, users cannot realize the integration of middle-end middle-end services into third-party applications of users through account information, such as integration into applications such as applications (APP), web pages, and/or desktops. If third-party applications cannot be integrated The ability of China Taiwan.

Contents of the invention

The present disclosure provides an identification processing method, device, equipment and storage medium for invoking middle platform services.

According to the first aspect of the present disclosure, there is provided an identification processing method for invoking a middle platform service, which is executed by the middle platform, including:

Assignment of first-class identification;

Determine the service calling method for the target user group to call the middle platform service;

According to the service invocation method, it is determined whether the target user group calls the middle station service involving the second type of identification; when it is determined that the middle station service call involves the second type of identification, establish the first type mapping information between the identifier and the second type of identifier;

The mapping information is used for the target user group to call the middle station service.

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

According to the service invocation method, determining whether the target user group invoking the middle station service involves a second type of identification includes:

In the case that the service invocation method is invoking based on the user identifier, determine whether the target user group uses the third-party application identifier to invoke the middle platform service; the mapping information indicates the first type of identifier and A first mapping relationship between the third-party application identifiers.

In some embodiments, the determining whether the target user group uses the third-party application identifier to invoke the middle platform service in the case that the service invocation method is invocation based on a user identifier includes:

In the case where the service invocation method is the invocation based on the user identifier, determine whether the target user group uses the third-party application identifier to invoke the middle platform service according to the identifier application requirement information;

or,

In the case where the service invocation method is the invocation based on the user identifier, according to receiving the third-party application identifier in the process of allocating the first-type identifier, determine whether the target user group uses the second-party application identifier The third-party application identifier calls the middle platform service.

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

In the case that the service calling method is to call the SDK, it is determined that the target user group uses the second type of identification to call the middle platform service, and the second type of identification is the identification of the SDK;

The mapping information indicates a second mapping relationship between the SDK identifier and the first type identifier.

In some embodiments, the method includes:

Send the mapping information to the client; wherein, the mapping information is used for the client to call the middle platform service based on the first type of identification, or the mapping information is used for the client Invoking the middle platform service based on the second type identifier.

In some embodiments, the method includes:

Receive service call request;

If the service invocation request includes a request identifier, determine whether to respond to the service invocation request according to the request identifier.

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:

If the request identifier is the first type identifier assigned by the middle station, determine to respond to the service invocation request;

and / or,

In the case that the request identifier is not the first-type identifier assigned by the middle station, by querying the mapping information, determine whether the request identifier establishes a mapping relationship with the first-type identifier assigned by the middle station; When a mapping relationship is established between the request identifier and the first-type identifier assigned by the middle station, it is determined to respond to the service invocation request.

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 third-party enterprise application identifier and the enterprise application identifier The first mapping relationship between;

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 that the third-party enterprise application the first mapping relationship between an 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.

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

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

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

According to the second aspect of the present disclosure, there is provided an identification processing method for invoking a middle platform service, which is executed by a client, including:

Sending 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;

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.

In some embodiments, the request identifier is used for determining to respond to the service invocation request when the middle station determines that it is the first type of identifier assigned by the middle station;

or,

The request identifier is used for 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 for the middle station to determine that it is the first type of identifier assigned by the middle station In the case of identifying the establishment of the mapping relationship, it is determined to respond to the service invocation request.

In some embodiments, the method includes:

receiving mapping information, wherein the mapping information is used to indicate the mapping relationship between the first type of identification and the second type of identification established by the middle station; the second type of identification is for the target group to call the middle station The identification involved in the service; the first type of identification is allocated by the middle station;

The request identifier includes: the first type identifier.

In some embodiments, before receiving the mapping information, it includes:

Sending the second-type identifier to the middle station; wherein, the second-type identifier includes: a third-party application identifier or an SDK identifier.

According to a third aspect of the present disclosure, an identification processing device for invoking a middle platform service is provided, including:

an allocation module, configured to allocate the first type of identification;

A determination module, configured to determine the service invocation method for the target user group to invoke the middle platform service;

The determining module is configured to determine whether the target user group calls the middle station service involves a second type of identification according to the service calling method; the processing module is used to determine whether the middle station service call involves the second type of identification. In the case of a class identifier, establishing mapping information between the first class identifier and the second class identifier;

The processing module is configured to use the mapping information for the target user group to call the middle platform service.

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

The determining module is configured to determine whether the target user group uses the third-party application identifier to invoke the middle platform service when the service invocation method is based on the user identifier; the mapping information indicates A first mapping relationship between the first type identifier and the third-party application identifier.

In some embodiments, the determination module is configured to determine whether the target user group uses the third-party application according to the identification application requirement information when the service invocation method is the user identification-based invocation Identify and call the middle platform service;

Alternatively, the determining module is configured to determine the third-party application identifier received during the process of allocating the first type of identifier when the service invocation method is the invocation based on the user identifier. Whether the target user group uses the third-party application identifier to call the middle platform service.

In some embodiments, the determining module is configured to determine whether the target user group uses the second type of identification to call the middle platform service when the service calling method is calling the SDK, and the second The second type of identification is the identification of the SDK;

The mapping information indicates a second mapping relationship between the SDK identifier and the first type identifier.

In some embodiments, the apparatus includes: a first sending module, configured to send the mapping information to the client; wherein the mapping information is used for the client to call the The middle platform service, or the mapping information is used for the client to call the middle platform service based on the second type identifier.

In some embodiments, the device includes: a first receiving module, configured to receive a service invocation request;

The processing module is configured to determine whether to respond to the service invocation request according to the request identifier when the service invocation request includes a request identifier.

In some embodiments, the processing module is configured to determine to respond to the service invocation request when the request identifier is the first type identifier assigned by the middle station;

Or, the processing module is configured to determine whether the request identifier is the same as that assigned by the intermediate station by querying the mapping information when the request identifier is not the first type identifier assigned by the intermediate station. Establish a mapping relationship with the first type of identification; in the case of establishing a mapping relationship between the request identification and the first type of identification assigned by the middle station, determine to respond to the service invocation request.

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 third-party enterprise application identifier and the enterprise application identifier The first mapping relationship between;

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 third-party enterprise application identifier the first mapping relationship with 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.

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

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

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

According to a fourth aspect of the present disclosure, there is provided an identification processing device for invoking a middle platform service, including:

The 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;

The second receiving module is configured 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.

In some embodiments, the request identifier is used for determining to respond to the service invocation request when the middle station determines that it is the first type of identifier assigned by the middle station;

Alternatively, the request identifier is used for 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 for the middle station to determine that it is the first type of identifier assigned by the middle station. In the case of establishing a mapping relationship with a class identifier, it is determined to respond to the service invocation request.

In some embodiments, the second receiving module is configured to receive mapping information, wherein the mapping information is established by the middle station to indicate the mapping relationship between the first type of identifier and the second type of identifier; The second type of identification is the identification involved in calling the middle station service by the target group; the first type of identification is allocated by the middle station; the first type of identification is different from the first type of identification;

The request identifier includes: the first type identifier.

In some embodiments, the second sending module is configured 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.

According to a third aspect of the embodiments of the present disclosure, a mobile terminal is provided, including:

processor;

memory for storing processor-executable instructions;

Wherein, the processor is configured to: when running the executable instruction, implement the identification processing method for invoking a middle platform service described in any embodiment of the present disclosure.

According to a fourth aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium, the readable storage medium stores an executable program, wherein, when the executable program is executed by a processor, the implementation of any embodiment of the present disclosure can be implemented. The identification processing method for invoking the middle platform service described above.

The technical solutions provided by the embodiments of the present disclosure may include the following beneficial effects:

According to the embodiment of the present disclosure, the middle station assigns the first type of identification and determines the service invocation method for the target user group to call the middle station service; and according to the service invocation method, determines whether the target user group calls the middle station service involves the second The second type of identification; in the case of determining 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; through the mapping information, with For the target user group to call the middle platform service. In this way, the embodiment of the present disclosure can establish the mapping information between the second-type identifier configured by the middle station and the first-type identifier configured by the middle station, so that the mapping information can be searched based on the second-type identifier to find the corresponding first-type identifier, and Use the first type of identification to call the middle platform service; that is, the mapping information can be used to make the first type of identification (such as the second type of identification) not allocated by the middle platform to call the middle platform service.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure.

Description of drawings

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

Fig. 1 is a flow chart showing a method for identifying an invocation middle station service according to an exemplary embodiment.

Fig. 2 is a schematic diagram showing a technical architecture according to an exemplary embodiment.

Fig. 3 is a schematic structural diagram of mapping information according to an exemplary embodiment.

Fig. 4 is a flow chart showing a method for processing identification of invoking middle platform services according to an exemplary embodiment.

Fig. 5 is a schematic diagram of a capability framework for implementing an SDK level according to an exemplary embodiment.

Fig. 6 is a flow chart showing an identification processing method for invoking a middle platform service according to an exemplary embodiment.

Fig. 7 is a flow chart showing an identification processing method for invoking a middle platform service according to an exemplary embodiment.

Fig. 8 is a schematic diagram showing a processing method for invoking a middle platform service according to an exemplary embodiment.

Fig. 9 is a flow chart showing an identification processing method for invoking a middle platform service according to an exemplary embodiment.

Fig. 10 is a flow chart showing an identification processing method for invoking a middle platform service according to an exemplary embodiment.

Fig. 11 is a flow chart showing an identification processing method for invoking a middle platform service according to an exemplary embodiment.

Fig. 12 is a schematic diagram showing a middle platform service integrated through an APP's SDK according to an exemplary embodiment.

Fig. 13 is a schematic diagram showing a middle platform service integrated through a web page according to an exemplary embodiment.

Fig. 14 is a block diagram of an identification processing device for invoking a middle platform service according to an exemplary embodiment.

Fig. 15 is a block diagram of an identification processing device for invoking a middle platform service according to an exemplary embodiment.

Fig. 16 is a block diagram of an identification processing device for invoking a middle platform service according to an exemplary embodiment.

Fig. 17 is a block diagram of an identification processing device for invoking a middle platform service according to an exemplary embodiment.

Fig. 18 is a block diagram of a middle station according to an exemplary embodiment.

Detailed ways

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with aspects of the invention as recited in the appended claims.

Regarding the apparatus in the foregoing embodiments, the specific manner in which each module executes operations has been described in detail in the embodiments related to the method, and will not be described in detail here.

As shown in FIG. 1 , the embodiment of the present disclosure provides an identification processing method for invoking a middle platform service, which is executed by the middle platform, including:

Step S11: assigning the first type of identification;

Step S12: Determine the service calling method for the target user group to call the middle station service;

Wherein, the target user group includes at least one target user;

Step S13: According to the service invocation method, determine whether the invocation of the middle platform service by the target user group involves a second type of identification;

Wherein, the second type of identification is different from the first type of identification;

Step S14: Establishing 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;

Step S15: Use the mapping information for the target user group to call the middle platform service.

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

Here, the middle platform can be a unified interface service platform. For example, the middle station can form a unified interface service platform through integration or at least through integration of at least one of resources, data, platforms, technologies, tools, and services within the enterprise.

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

Here, the middle station can be any kind of middle station. For example, the middle platform can be any kind of enterprise collaboration middle platform, which can modularize and process the capabilities of the office platform; for example, the middle platform A can cover instant messaging capabilities, audio and video call capabilities, enterprise management background capabilities, and enterprise self-built applications At least one of the capabilities of the workbench and cloud document capabilities.

Here, the platform may be any kind of 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 wait. For another example, the platform may be a collaboration platform; the collaboration platform may integrate at least one of instant messaging capabilities, audio and video call capabilities, cloud document capabilities, internal enterprise application capabilities, and external service provider application capabilities.

Exemplarily, as shown in FIG. 2 , a schematic diagram of a technical architecture is provided; the technical architecture generally includes customer integration, application layer, service layer, middleware, and infrastructure. The middle platform can usually include the service layer, middleware and infrastructure. Customer integration may be, but not limited to, at least one of mobile terminal integration, PC terminal integration and browser integration.

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

The service corresponding to the instant messaging SDK of the application layer in the service layer may be, but not limited to: at least one of multiple message types, group management, message management, and message security; audio and video calls between the service layer and the application layer The service corresponding to the SDK can be but not limited to: at least one of one-to-one and one-to-many; the service corresponding to the document capability in the application in the service layer can be but not limited to document creation, interaction and collaboration between documents and IM at least one of document transfer, document storage and management; the services corresponding to the enterprise management background of the application layer in the service layer may be, but not limited to, address book management, role management, space management, document management, login security management, and At least one of enterprise system management; the service corresponding to the open platform of the application layer in the service layer may be but not limited to at least one of a server application programming interface (Application Programming Interface, API) and a client.

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

The infrastructure may be, but not limited to, at least one of physical machines, virtual machines, and third-party cloud platforms.

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.

Here, the target user group may be a target user corresponding to a client, or may also be a target user corresponding to a client. In the case that the target user group is the target user corresponding to multiple clients, the devices corresponding to the multiple clients have no distinction between primary and secondary devices. For example, when the service is document collaboration, instant messaging messages are delivered to three clients, and the three clients can receive the messages synchronously. For another example, three clients establishing connection and communication with the middle platform can simultaneously open an application.

Here, the mid-stage service may be a service provided by the mid-stage. For example, middle-end services may be, but are not limited to, instant messaging services, offline push services, enterprise account services, enterprise management services, cloud document services, and enterprise self-built application services. For another example, the middle platform service may be a service of any other capability; the capability may be, but not limited to, the capability of integrating at least one of resources, data, platforms, technologies, tools, and services.

Here, the method of invoking the service may be, but not limited to: invoking and/or invoking the SDK based on the user ID.

Here, the first type of identification is an identification assigned by the middle station; the first type of identification may be an internal account of the middle station.

In an embodiment, the first type of identifier includes: an enterprise application identifier.

In yet another embodiment, the first type of identifier includes: an enterprise application identifier and a user application identifier.

Here, the second type of identification is an identification that is not assigned by the central platform; the second type of identification can be an external identification of the central platform or an external account of the central platform.

In an embodiment, the second type of identifier includes a third-party application identifier and/or an SDK identifier.

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

Here, the mapping information includes the first mapping relationship and/or the second mapping relationship.

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

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

Exemplarily, the first type of identifier allocated by the middle station may be "company_uuid", the SDK identifier 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.

In some embodiments, step S11 may be: the middle station assigns the first type of identification using the background, wherein the background is a component of the middle station; in step S14, the first type of identification and the first type of identification are established. The mapping relationship between the two types of identities includes: the middle station establishes mapping information between the first type of identities and the second type of identities. In this way, in the embodiment of the present disclosure, the background in the middle platform can be used to assign the first type of identifier.

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 relationship between the third-party enterprise application identifier and the enterprise application identifier The first mapping relationship of .

Exemplarily, the third-party application identifier of the third-party application may be "A_gognsi", and the middle station may assign the enterprise application identifier "A_company" to the third-party application identifier "A_gognsi".

Here, the third-party application may be but not limited to at least one of the following: any application program (APP), applet, official account, web page, and desktop application. Here, the desktop application may be, but not limited to, a PC application and/or a cloud desktop application. In one embodiment, the integration terminal can be used to integrate the aforementioned third-party applications.

In this way, in the embodiment of the present disclosure, the middle station can assign a corresponding enterprise application identifier to the third-party enterprise application identifier in the third-party application identifier, so that the client or target user group can log in based on the enterprise application identifier assigned by the middle station When the platform is used, the middle platform service corresponding to the enterprise application identifier can be scheduled.

In some other embodiments, 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 that the third-party 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.

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

Here, the enterprise management background is an independent management background; the enterprise management background is an existing online capability, which can be used directly without integration.

In this way, in the embodiment of the present disclosure, the middle station can assign a corresponding enterprise application identifier to the third-party enterprise application identifier in the third-party application identifier and assign a corresponding enterprise application identifier to the third user application identifier under the third-party enterprise application identifier. User application ID, so that the client or target user group can schedule the middle platform service corresponding to the enterprise application ID when logging in to the middle platform based on the enterprise application ID assigned by the middle platform, or make the client or target user group based on the When the user application ID assigned by the middle platform logs in, the middle platform service corresponding to the enterprise application ID corresponding to the user application ID is scheduled.

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

Exemplarily, the middle station establishes and saves the mapping information between the first type identifier and the middle station service identifier; the mapping information indicates the third mapping relationship between the first type identifier and the middle station service identifier. Here, one 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.

In this way, in the embodiment of the present disclosure, the middle station assigns the first type of identification and determines the service invocation method for the target user group to call the middle station service; and according to the service invocation method, determines whether the target user group calls the middle station service. The second type of identification; when it is determined that the middle station service call involves the second type of identification, establish mapping information between the first type of identification and the second type of identification; through the mapping information, for The target user group calls the middle platform service. In this way, the embodiment of the present disclosure can establish the mapping information between the second-type identifier configured by the middle station and the first-type identifier configured by the middle station, so that the mapping information can be searched based on the second-type identifier to find the corresponding first-type identifier, and Use the first type of identification to call the middle platform service; that is, the mapping information can be used to make the first type of identification (such as the second type of identification) not allocated by the middle platform to call the middle platform service.

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

As shown in Figure 4, the step S13 includes:

Step S131: In the case that the service invocation method is invoking based on the user ID, determine whether the target user group uses the third-party application ID to invoke the middle platform service;

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

For example, please refer to Figure 3 again. In the case that the middle platform determines the third-party application identifier "app_userid" in the third-party application, the middle platform uses the middle platform to generate the user application identifier "company_uuid" for "app_userid"; the middle platform stores the indication " The mapping information of the first mapping relationship between "app_userid" and "company_uuid".

In this way, in the embodiment of the present disclosure, in the case that the service calling method is called based on the user ID, if it is determined that the target user group calls the middle platform service that involves a third-party application ID, a relationship between the first type of ID and the third-party application ID can be established. The first mapping relationship between. In this way, the embodiment of the present disclosure can realize the binding of the third-party application identifier of the third-party application and the first type of identifier (ie, the account system of the middle platform) assigned by the middle platform, so that when the client or the target user group calls the middle platform service , you can call at least one middle platform service to a third-party application for use, that is, you can directly embed the middle platform capabilities into the third-party application.

In some embodiments, the step S131 includes:

Step S1311: When the service invocation method is the invocation based on the user identifier, determine whether the target user group uses the third-party application identifier to invoke the middle platform service according to the identifier application requirement information;

or,

Step S1312: In the case that the service invocation method is the invocation based on the user identification, according to the receiving of the third-party application identification in the process of allocating the first type of identification, determine whether the target user group uses The third-party application identifier calls the middle platform service.

Here, the identification application requirement information may be any kind of information indicating the use of a third-party application identification. The identification application requirement information may be obtained by the middle station from the client. For example, when the client sends a service invocation request, it can carry the first request identifier and application identifier requirement information; in this way, based on the application requirement identifier information, the middle platform can know whether to instruct the use of a third-party application identifier when invoking the middle platform service based on the user identifier. transfer.

In one embodiment, the step S1311 includes: determining the target user group when the service calling method is the calling based on the user ID, and the ID application requirement information indicates the use of the third-party application ID The group uses the third-party application identification to call the middle platform service.

In another embodiment, the step S1311 includes: determining the target when the service calling method is the calling based on the user ID and the ID application requirement information does not indicate the use of the third-party application ID The user group does not use the third-party application to call the middle platform service.

In this way, in the embodiment of the present disclosure, in the case that the service invocation method is based on the user identification, it can be accurately determined whether the target user group uses the third-party application invocation when the identification application requirement information indicates whether to use the third-party application identification. Middle-end service.

In one embodiment, the step S1312 includes: when the service invocation method is the invocation based on user identification and the third-party application identification is received during the process of allocating the first type of identification, Determine whether the target user group uses the third-party application identifier to call the middle platform service.

In another embodiment, the step S132 includes: when the method of invoking the service is the invocation based on the user identifier and the third-party application identifier is not received during the process of assigning the first type of identifier Next, it is determined that the target user group does not use the third-party application identifier to call the middle platform service.

Here, during the process of assigning the first-type identifier, the middle station receives the third-party application identifier sent by the client; thus, the middle station can assign the corresponding first-type identifier to the third-party application identifier.

In this way, in the embodiment of the present disclosure, in the case that the service invocation method is based on user identification, it may be determined based on whether a third-party application identification is received during the process of allocating the first type of identification to determine whether the target user group uses the second type of application identification. The third-party application identification calls the middle platform service. In the case that a third-party application identifier is received during the first-type identification process, the corresponding first-type identifier can be determined in time for the third-party application identifier. In this way, the embodiments of the present disclosure can also accurately determine whether the target user group uses the third-party application identifier to call the middle platform service, and can effectively establish a mapping relationship between the third-party application identifier and the first-type identifier.

Please refer to FIG. 4 again, in some embodiments, the step S13 includes:

Step S132: In the case that the service calling method is to call the SDK, determine that the target user group uses the second type of identification to call the middle platform service, and the second type of identification is the identification of the SDK;

The mapping information indicates a second mapping relationship between the SDK identifier and the first type identifier.

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

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

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 may be determined that an SDK identifier corresponds to a third-party user application identifier.

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

Exemplary, as shown in Figure 5, SDK can be Instant Messenger SDK (IMSDK), for example can be Company A's Instant Messenger SDK (Kingsoft Company IM Software Development Kit, KCIM SDK); This IMSDK is used for enterprise cloud document and/or The enterprise workbench is implemented as an SDK-level capability architecture. The IMSDK mainly includes an instant messaging toolkit (IMKit), a plug-in (plugin), and a honeycomb core (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, events can be generated by the event or state layer, data from the business model layer passes 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 (Real time communication, RTC), etc.; the RTC is real-time audio and video. The IMCore mainly includes IMCore Impl, business task (servicetask), data wrapper (data wrapper), network (Networking), network socket (Websocket), cache (Cache), cache bridge (cache bridge) and basic components (Foundation); Among them, Impl is used to store the implementation class of the interface. In this way, in the embodiment of the present disclosure, the SDK can easily access cloud documents, real-time audio and video, etc., of course, it can also access other capabilities, such as workbench capabilities; the SDK provides multi-model adaptive rendering of business view pages and interactive capabilities. The SDK can process business data communication through internal logic, and the SDK provides extended protocols to support customers to add custom business process processing.

For example, please refer to Fig. 3 again. A third-party application, such as 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 station may store mapping information indicating the second mapping relationship between "IMSDK" and "company_uuid". After the middle platform receives the APP SDK ID sent by the third-party application, it can determine the first type of ID corresponding to the SDK ID based on the mapping information; if the enterprise application ID is determined, and based on the enterprise application ID, it can determine the corresponding middle platform service; or if the user application identifier is determined, the enterprise application identifier is determined based on the user application identifier, and the corresponding middle-end service is called based on the enterprise application identifier. The middle platform can find the third-party application identification corresponding to the SDK based on the enterprise user identification corresponding to the SDK identification, such as "app_userid"; and return the middle platform service to the third-party application according to the third application identification "app_userid".

In this way, in the embodiment of the present disclosure, when the method of calling the service is to call the SDK, if it is determined that the target user group uses the SDK to call the middle platform service, a second mapping between the first type of identifier and the SDK can be established relation. In this way, the embodiment of the present disclosure can use the independent capability in the SDK to call the middle platform service of the middle platform, so that at least one middle platform service of the middle platform can be integrated into the third-party application. Moreover, in the embodiments of the present disclosure, the third-party application does not need to use its own account or the account assigned by the middle platform corresponding to its own account to log in to the middle platform, so that the process of calling the middle platform service by the client or the target user group can be simplified, that is, it can Conveniently dispatch middle-end services through SDK.

In some embodiments, the method includes:

Send the mapping information to the client; wherein, the mapping information is used for the client to call the middle platform service based on the first type of identification, or the mapping information is used for the client Invoking the middle platform service based on the second type identifier.

Here, in the case that the service invocation mode is invoking based on the user identifier, the client may invoke the middle office service based on the first type of identifier. For example, in the case that the middle station receives the first type of identification sent by the client, the middle platform service invoked by the client may be determined based on the first type of identification.

Here, in the case that the service calling method is calling the SDK, the client can call the middle platform service based on the second type of identification. For example, when the middle station receives the SDK ID sent by the client, it can determine the first type of ID corresponding to the SDK ID based on the SDK ID and the mapping information; the mapping information is the ID indicating the SDK and the first type of ID The second mapping relationship among them; the middle platform determines the middle platform service invoked by the client based on the first type identifier.

In this way, in the embodiment of the present disclosure, 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 identifier or the second type identifier in the mapping information. For example, the service invocation method can be invoked based on the user identification, and the first type of identification can be used to invoke the middle platform service; or the service invocation method of the SDK can be invoked, for example, the second type of identification can be used to invoke the middle platform service. In this way, applicability can be invoked based on different service invocation methods and corresponding identifiers.

As shown in Figure 6, in some embodiments, the method includes:

Step S21: receiving a service call request;

Step S22: In the case that the service invocation request includes a request identifier, determine whether to respond to the service invocation request according to the request identifier.

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

In another embodiment, the request identifier may be a second-type identifier. For example, the request identifier may be an SDK identifier. At this time, the middle station can determine the second-type identifier that has mapping information with the first-type identifier based on the second-type identifier and the mapping information, so as to respond to the service call request.

In yet another embodiment, the request identifier may also be a third-party application identifier in the second type of identifier. For example, the request identifier may be a third-party enterprise application identifier and/or a third-party user application identifier.

Certainly, in other embodiments, the request identifier may be other arbitrary identifiers except the first type identifier and the second type identifier. At this time, the middle station may not respond to the service call request.

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

Here, determining to respond to the service invocation request according to the request identifier may be: determining that the middle office service corresponding to the invocation request identifier is allowed. Alternatively, determining to respond to the service invocation request according to the request identifier may be: determining that the invocation of the middle platform service corresponding to the request identifier is allowed; and sending a service invocation response, wherein the service invocation response includes: the middle office service corresponding to the request identifier.

In this way, in the embodiment of the present disclosure, the middle station can accurately determine whether to respond to the service call request based on the request identifier contained in the received service call request; service call. This can solve the problem that the third-party application itself cannot integrate the capabilities of the enterprise-level mid-platform, and can freely integrate at least one of the mid-platform services with the third-party application; thus realizing the integration of enterprise-level capabilities.

As shown in Figure 7, in some embodiments, the S22 includes:

Step S221: If the request identifier is the first type identifier assigned by the middle station, determine to respond to the service invocation request;

or,

Step S222: In the case that the request identifier is not the first-type identifier assigned by the middle station, determine whether the request identifier is established with the first-type identifier assigned by the middle station by querying the mapping information Mapping relationship: in the case that the request identifier establishes a mapping relationship with the first-type identifier allocated by the middle station, determine to respond to the service invocation request.

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

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

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

Exemplarily, the middle station receives the service invocation request sent by the client, and determines to respond to the service invocation request when it is determined that the service invocation request contains the enterprise application identifier. The middle platform returns a service invocation response to the client, and the service invocation response includes the middle platform service corresponding to the enterprise application identifier.

Exemplarily, the middle station receives the service invocation request sent by the client, and if it is determined that the service invocation request contains the user application identifier, it queries the corresponding enterprise application identifier based on the user application identifier; and determines the response based on the enterprise application identifier Service call request. The middle platform returns a service invocation response to the client, and the service invocation response includes the middle platform service corresponding to the enterprise application identifier.

In this way, in the embodiment of the present disclosure, in the case that the service request identifier is a first-type identifier assigned by the middle station, it can be directly determined based on the first-type identifier to respond to the service invocation request.

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

Exemplarily, the middle station receives the service invocation request sent by the client, and when it is determined that the service invocation request contains a third-party application identifier, based on the third-party application identifier and the first-class identifier between the third-party application identifier and the first-type identifier The mapping information of the mapping relationship determines the first type of identification information; the middle station determines and responds to the service call request based on the first type of identification. The middle platform returns a service invocation response to the client, and the service invocation response includes the middle platform service corresponding to the enterprise application identifier.

In this way, in the embodiment of the present disclosure, in the case that the service invocation request is not the first type identifier assigned by the middle station and is a second type identifier that has a mapping relationship with the first type identifier, it can be indicated based on the second type identifier and the The mapping information of the mapping relationship determines the first type of identifier; thereby determining the response to the service invocation request.

Here, before the middle station determines to respond to the service invocation request based on the first type of identification, it will also perform authorization verification on the first type of identification. For example, it is determined by means of a white list whether the first type of identification is an authorization identification authorized to call the middle platform service.

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

In some embodiments, the determining that the first type of identification is an authorized identification includes:

If the first type of identifier in the service invocation request is the enterprise application identifier existing in the whitelist of the middle station, determine that the enterprise user identifier is an authorization identifier, wherein the whitelist stores at least one authorized calling middle station the Enterprise Application Identifier for the Service;

If the first type of identifier included in the service call belongs to the enterprise application identifier in the whitelist, determine that the user application identifier is an authorized identifier.

In this way, in the disclosed example, the verification of the enterprise application identification and the verification of the user application identification under the enterprise application identification can be realized; thereby accurately determining whether the first type of identification including the enterprise application identification and/or user application identification is received It is the first type of identification authorized to call the middle office service in the white list.

As shown in FIG. 8 , an embodiment of the present disclosure provides a schematic diagram of a processing method for invoking middle-end services. The processing method for invoking middle-end services may be as follows: first, integrate enterprise version capabilities, such as enterprise documents, enterprise management background , enterprise workbench, and open capabilities; secondly, establish a mapping relationship, establish a mapping relationship between the first type of identification and the second type of identification, and determine whether the user application identification is limited to the enterprise application identification; and then determine whether the user application identification is limited to In the case of an enterprise application identifier, the instant messaging service of the enterprise collaboration platform is executed. Here, calling the instant messaging service of the enterprise collaboration center may include, but is not limited to: the enterprise collaboration center receives the HTTP sent by the third-party business, and the HTTP carries the requested instant messaging service; the middle stage pushes the instant messaging service; the middle stage The instant messaging service is integrated into a third application for use, and the third-party application may be, but not limited to, applications such as mobile phone terminals, PC terminals, and browsers.

In the embodiments of the present disclosure, reference may be made to any of the foregoing embodiments for executing the instant messaging service for invoking the middle platform service. Moreover, in other embodiments, it is also possible to call any middle platform service in the middle platform.

It should be noted that those skilled in the art can understand that the methods provided in the embodiments of the present disclosure may be executed independently, or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

The following identification processing method for invoking the middle platform service is executed by the client, which is similar to the above description of the identification processing method for invoking the middle platform service performed by the middle platform; and, for the invocation performed by the client For the technical details not disclosed in the embodiment of the identification processing method of the platform service, please refer to the description of the example of the identification processing method for invoking the service of the platform performed by the platform, and no detailed description will be given here.

As shown in Figure 9, an identification processing method for invoking middle-end services is provided, which is executed by the client, including:

Step S31: 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;

Step S32: 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.

In some embodiments, the request identifier is used for determining to respond to the service invocation request when the middle station determines that it is the first type of identifier assigned by the middle station;

or,

The request identifier is used for 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 for the middle station service to determine that it is the first type of identifier assigned by the middle station. In the case of establishing a mapping relationship with class identifiers, it is determined to respond to the service invocation request.

Here, a mid-stage service can be represented by a mid-stage service identifier. If the request identifier is a first-type identifier, it may be based on the middle station service identifier corresponding to the first-type identifier; here, the middle station establishes and saves a third mapping relationship between the first-type identifier and the middle station service identifier. If the request identifier is not the first-type identifier, the second-type identifier can be determined based on the first-type identifier and mapping information; wherein, if the second-type identifier is a third-party application identifier, the third-party application identifier can be determined based on the third application identifier. The mid-platform service logo corresponding to the application logo, and/or, if the second type of logo is the SKD logo, the mid-platform service logo corresponding to the SDK logo can be determined based on the SDK logo; here, the mid-platform establishes and saves the third-party The third mapping relationship between the 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 invoked through the request identifier.

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 foregoing embodiments, respectively. Exemplarily, here, the first type of identification is the identification assigned by the middle station.

In an embodiment, the first type of identifier includes: an enterprise application identifier.

In yet another embodiment, the first type of identifier includes: an enterprise application identifier and a user application identifier.

Here, the second type of identifier is an identifier not assigned by the middle station.

In an embodiment, the second type of identifier includes a third-party application identifier and/or an SDK identifier.

In some embodiments, the method includes:

Step S30: Receive mapping information; wherein, the mapping information is established by the middle station to indicate the mapping relationship between the first type of identification and the second type of identification; the second type of identification is the target group call The identity involved in the middle station service; the first type of identity is allocated by the middle station; the first type of identity is different from the first type of identity; the target user group includes at least one target user;

The request identifier includes: the first type identifier.

In some embodiments of the present disclosure, the mapping information may be the mapping information in the foregoing embodiments.

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

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

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 relationship between the third-party enterprise application identifier and the enterprise application identifier The first mapping relationship of .

In yet 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 that the third-party The first mapping relationship between an 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.

Here, after the mapping information is received, a service invocation request including a first type of identifier may be sent based on the mapping information, and the first type of identifier is the request identifier in step S31.

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

In some embodiments, before receiving the mapping information in step S30, it includes:

Sending the second-type identifier to the middle station; wherein, the second-type identifier includes: a third-party application identifier or an SDK identifier.

Here, before receiving the mapping information, the client sends the second type of identification to the middle station, which is beneficial for the middle station to allocate the first type of identification based on the second type of identification, and establish the relationship between the first type of identification and the second type of identification. Mapping relations.

For the above implementation manner, for details, refer to the description on the side of the middle platform, and details are not repeated here.

It should be noted that those skilled in the art can understand that the methods provided in the embodiments of the present disclosure may be executed independently, or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

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

example one

As shown in FIG. 10 , an embodiment of the present disclosure provides a method for processing a service call of a middle platform, which is executed by a device, and the device includes a middle platform and a client; including the following steps:

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

In an optional embodiment, the second type of identifier may be a third-party application identifier.

In another optional embodiment, the second type of identifier may be an SDK identifier.

Step S42: the middle station assigns the first type of identification;

In an optional embodiment, the middle station assigns the first-type identifier to the second-type identifier.

Step S43: the middle station determines the service invocation method for invoking the main station service;

In an optional embodiment, the middle platform determines the service invocation method for the target user group to call the middle platform service.

Step S44: The middle station determines whether calling the middle station service involves the second type of identification according to the service calling method;

In an optional embodiment, the middle platform determines whether the call of the middle platform service by the target user group involves the second type of identification according to the service calling method.

Step S45: In the case that the middle station determines that the service call of the middle station involves the second type of identification, the mapping information before the first type of identification and the second type of identification is established;

Step S46: the middle station sends the mapping information to the client;

Step S47: the client sends a service invocation request, wherein the service invocation request includes a request identifier;

Step S48: If the middle station determines the request identifier, determine whether to respond to the service invocation request;

In an optional embodiment, if the middle station determines that the request identifier is a first-type identifier assigned by the middle station, it determines to respond to the service invocation request.

In another optional embodiment, if the middle station determines that the request identifier is not the first-type identifier assigned by the middle station, and determines whether the request identifier has a mapping relationship with the first-type identifier assigned by the middle station by querying the mapping information; If the identification has a mapping relationship with the first type of identification assigned by the middle station, it is determined to respond to the service call request.

Step S49: Sending a service invocation response, wherein the service invocation response includes the middle platform service corresponding to the first type of identifier.

In this way, in the embodiment of the present disclosure, 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, so as to be assigned to the first type of identification under the middle platform. One type of identification; thus, the middle platform services of the middle platform can be scheduled based on the first type of identification, so as to realize the free integration of enterprise level middle platform services and third-party applications.

Moreover, in the embodiment of the present disclosure, the service invocation method based on the user identification can be used, for example, based on the first type of identification corresponding to the third application identification or directly invoking the middle platform service based on the first type of identification. Alternatively, the middle platform services of the middle platform can be integrated into the SDK through the SDK-based service calling method, so that the middle platform services of the middle platform can also be called.

Example two

As shown in FIG. 11 , an embodiment of the present disclosure provides a schematic diagram of integrating a middle platform service through an SDK of an APP. The target user A (such as field staff) conducts instant messaging with at least one target user B (such as internal staff); the instant messaging service can be integrated into the APP through the APP in the mobile phone of target user A and/or target user B to enter the predetermined page; If the mobile phone detects a click operation on the entry of the predetermined page, etc., the login process is triggered. After the mobile phone detects that the login process has passed, it presents the instant messaging SDK development chat page, and determines the single chat or group chat session based on the input SDK identifier.

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

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

Example three

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

In this way, in the embodiment of the present disclosure, the instant messaging service of the middle platform and the middle platform service such as the self-built application of the enterprise can be realized through the webpage integration. Moreover, on the premise that you do not want to install a new APP in the terminal, in order to realize instant messaging and other middle-end services, you can call these middle-end services by embedding them inside the application on the webpage; in this way, you can directly embed the middle-end services through the webpage It can also save data sending and receiving time, improve calling efficiency, etc.

It should be noted that those skilled in the art can understand that the methods provided in the embodiments of the present disclosure may be executed independently, or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

As shown in Figure 14, the embodiment of the present disclosure provides an identification processing device for invoking middle platform services, including:

An allocation module 51, configured to allocate the first type of identification;

Determining module 52, is used for determining the service invocation mode that the target user group invokes the middle platform service;

The determining module 52 is configured to determine whether the target user group calls the middle platform service involves a second type of identification according to the service calling method;

A processing module 53, configured 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;

The processing module 53 is configured to use the mapping information for the target user group to call the middle station service.

Here, the target user group includes at least one target user.

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

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

The determining module 52 is configured to determine whether the target user group uses the third-party application identifier to invoke the middle platform service when the service invocation method is based on the user identifier; the mapping information indicates A first mapping relationship between the first type identifier and the third-party application identifier.

In some embodiments, the determining module 52 is configured to determine whether the target user group uses the third-party The application identification calls the middle platform service;

Alternatively, the determining module 52 is configured to determine the third-party application identifier received during the process of allocating the first type of identifier when the service invocation method is the invocation based on the user identifier. Whether the target user group uses the third-party application identifier to call the middle platform service.

In some embodiments, the determination module 52 is configured to determine the target user when the service invocation method is the user identification-based invocation and the identification application requirement information indicates the use of the third-party application identification The group uses the third-party application identifier to call the middle platform service;

Alternatively, the determining module 52 is configured to determine that the target user group does not Use the third-party application identifier to call the middle platform service.

In some embodiments, the determining module 52 is configured to use the method of invoking the service based on the user identification and receiving the third-party application identification during the process of allocating the first type of identification , determining that the target user group uses the third-party application identifier to call the middle platform service;

Alternatively, the determination module 52 is configured to determine the target when the service invocation method is the invocation based on the user identification and the third-party application identification is not received during the process of allocating the first type of identification. The user group does not use the third-party application identifier to call the middle platform service.

In some embodiments, the determining module 52 is configured 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 an SDK, and The second type of identification is the identification of the SDK;

The mapping information indicates a second mapping relationship between the SDK identifier and the first type identifier.

As shown in FIG. 15, in some embodiments, the apparatus includes: a first sending module 54, configured to send the mapping information to the client; wherein the mapping information is used by the client based on the The first type of identifier calls the middle platform service, or the mapping information is used for the client to call the middle platform service based on the second type of identifier.

As shown in FIG. 16, in some embodiments, the device includes: a first receiving module 55, configured to receive a service invocation request;

The processing module 53 is configured to determine whether to respond to the service invocation request according to the request identifier when the service invocation request includes a request identifier.

In some embodiments, the processing module 53 is configured to determine to respond to the service invocation request when the request identifier is the first type identifier assigned by the middle station;

Alternatively, the processing module 53 is configured to determine whether the request identifier is consistent with the middle station by querying the mapping information when the request identifier is not the first type identifier assigned by the middle station Establish a mapping relationship with the assigned first-type identifier; and determine to respond to the service invocation request when the mapping relationship is established between the request identifier and the first-type identifier assigned by the middle station.

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 third-party enterprise application identifier and the enterprise application identifier The first mapping relationship between;

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 that the third-party enterprise application the first mapping relationship between an 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.

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

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

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

As shown in FIG. 17 , an embodiment of the present disclosure provides an identification processing device for invoking a middle platform service, including:

The second sending module 61 is configured 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;

The second receiving module 62 is configured 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 corresponding to the request identifier desk service.

In some embodiments, the request identifier is used for determining to respond to the service invocation request when the middle station determines that it is the first type of identifier assigned by the middle station;

Alternatively, the request identifier is used for 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 for the middle station to determine that it is the first type of identifier assigned by the middle station. In the case of establishing a mapping relationship with a class identifier, it is determined to respond to the service invocation request.

In some embodiments, the second receiving module 62 is configured to receive mapping information, wherein the mapping information is used to indicate the mapping relationship between the first type of identification and the second type of identification established by the middle station ; The second type of identification is the identification involved in calling the middle station service by the target group; the first type of identification is allocated by the middle station;

The request identifier includes: the first type identifier.

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

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

Regarding the apparatus in the foregoing embodiments, the specific manner in which each module executes operations has been described in detail in the embodiments related to the method, and will not be described in detail here.

An embodiment of the present disclosure also provides a device, characterized in that it includes:

processor;

memory for storing processor-executable instructions;

Wherein, the processor is configured to: when executing the executable instruction, realize the identification process of invoking the middle platform service described in any embodiment of the present disclosure.

The device may be, but not limited to: a terminal and/or a middle station.

The memory may include various types of storage media, which are non-transitory computer storage media, and can continue to memorize and store information thereon after the communication device is powered off.

The processor can be connected to the memory through a bus, etc., and is used to read the executable program stored on the memory, for example, to realize the method shown in Fig. 1, Fig. 4, Fig. 6, Fig. 7, Fig. 9 to Fig. 11 at least one of them.

Embodiments of the present disclosure also provide a computer-readable storage medium, where an executable program is stored in the readable storage medium, wherein when the executable program is executed by a processor, the call described in any embodiment of the present disclosure is implemented. Identification processing of middle-end services. For example, implement at least one of the methods shown in FIG. 1 , FIG. 4 , FIG. 6 , FIG. 7 , and FIG. 9 to FIG. 11 .

Regarding the apparatus in the foregoing embodiments, the specific manner in which each module executes operations has been described in detail in the embodiments related to the method, and will not be described in detail here.

As shown in FIG. 18 , it shows 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. Referring to 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 application programs. The application program stored in 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, so as to perform any of the aforementioned methods applied to the base station.

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

Other embodiments of the invention will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any modification, use or adaptation of the present invention, these modifications, uses or adaptations follow the general principles of the present invention and include common knowledge or conventional technical means in the technical field not disclosed in this disclosure . The specification and examples are to be considered exemplary only, with a true scope and spirit of the invention being indicated by the following claims.

It should be understood that the present invention is not limited to the precise constructions which have been described above and shown in the accompanying drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the invention is limited only by the appended claims.

Claims (17)

1. An identification processing method for calling a middle station service, which is executed by a middle station, comprises the following steps:

allocating a first type identification;

determining a service calling mode of a target user group calling a middle station service;

determining whether the calling of the middle station service by the target user group relates to a second type of identification or not according to a service calling mode;

under the condition that the middle station service call is determined to relate to the second type identification, establishing mapping information between the first type identification and the second type identification;

and the mapping information is used for the target user group to call the middle station service.

2. The method of claim 1, wherein the second class identification comprises: a third party application identification;

the determining whether the calling of the middle station service by the target user group involves a second type identifier according to the service calling mode comprises:

determining whether the target user group uses the third-party application identifier to call the middle station service or not under the condition that the service calling mode is based on user identifier calling; the mapping information indicates a first mapping relation between the first type identifier and the third party application identifier.

3. The method according to claim 2, wherein the determining whether the target user group invokes the middlebox service using the third party application identifier if the service invocation mode is based on user identifier invocation comprises:

under the condition that the service calling mode is based on the user identification calling, determining whether the target user group uses the third party application identification to call the middle station service or not according to identification application demand information;

or,

and under the condition that the service calling mode is based on the user identification calling, determining whether the target user group uses the third-party application identification to call the middle station service or not according to the condition of receiving the third-party application identification in the process of distributing the first-class identification.

4. The method of claim 1, wherein the determining whether the calling of the middlebox by the target user group involves a second type of identifier according to a service calling manner comprises:

when the service calling mode is to call the SDK, determining that the target user group uses the second type identifier to call the middle station service, wherein the second type identifier is the identifier of the SDK;

the mapping information indicates a second mapping relationship between the identifier of the SDK and the first type identifier.

5. The method according to claim 1, characterized in that it comprises:

sending the mapping information to a client; the mapping information is used for the client to call the middle station service based on the first type identifier, or the mapping information is used for the client to call the middle station service based on the second type identifier.

6. The method according to claim 1, characterized in that it comprises:

receiving a service calling request;

and under the condition that the service calling request contains a request identifier, determining whether to respond to the service calling request according to the request identifier.

7. The method according to claim 6, wherein, in the case that the service invocation request includes a request identifier, determining whether to respond to the service invocation request according to the request identifier comprises:

determining to respond to the service calling request under the condition that the request identifier is the first type identifier allocated by the middle station;

and/or the presence of a gas in the gas,

under the condition that the request identifier is not the first type identifier distributed by the middle station, determining whether the request identifier establishes a mapping relation with the first type identifier distributed by the middle station or not by inquiring the mapping information; and determining to respond to the service calling request under the condition that the request identifier establishes a mapping relation with the first class identifier allocated by the middle station.

8. The method of claim 6,

the third party application identification comprises: a third party enterprise application identity; the first type identification comprises: an enterprise application identifier; wherein the mapping information indicates a first mapping relationship between the third party enterprise application identity and the enterprise application identity;

or,

the third party application identification comprises: a third party enterprise application identifier and a third party user application identifier; the first type identification comprises: an enterprise application identifier and a user application identifier; wherein the mapping information indicates the third party enterprise application identity and the first mapping relationship of the enterprise application identity; and the mapping information indicates the third party user application identifier and the first mapping relationship of the user application identifier.

9. The method according to claim 7, wherein, in case that the request identifier is the first type identifier allocated by the middlebox, the method comprises at least one of the following:

the request identification is the enterprise application identification; and/or the presence of a gas in the gas,

the request identification is the user application identification, and the user application identification belongs to the enterprise application identification.

10. An identification processing method for calling a middle station service, which is executed by a client and comprises the following steps:

sending a service calling request; the service calling request comprises a request identifier, and the request identifier is used for the middle station to determine whether to respond to the service calling request;

receiving a service invocation response; the service calling response is returned by the middle station in response to the service calling request, and the service calling response comprises the middle station service corresponding to the request identifier.

11. The method of claim 10,

the request identifier is used for determining to respond to the service calling request under the condition that the middle station determines that the request identifier is the first type identifier distributed by the middle station;

or,

and the request identifier is used for determining to respond to the service invocation request under the condition that the middling station determines that the request identifier is not the first type identifier allocated by the middling station and the request identifier is used for determining that the middling station establishes a mapping relation with the first type identifier allocated by the middling station.

12. The method according to claim 10 or 11, characterized in that the method comprises:

receiving mapping information, wherein the mapping information is established for the middle station and used for indicating a mapping relation between a first type identifier and a second type identifier; the second type of identification is identification related to a target group calling the middle station service; the first type identification is allocated by the middle station; the request identification comprises: the first class identification.

13. The method of claim 12, wherein prior to receiving the mapping information, the method further comprises:

sending the second type identification to the middle station; wherein the second type identifier comprises: a third party application identity or an identity of the SDK.

14. An identification processing apparatus for invoking a midlet service, comprising:

the distribution module is used for distributing the first type identification;

the determining module is used for determining a service calling mode of calling the middle station service by the target user group;

the determining module is used for determining whether the calling of the middle station service by the target user group relates to a second type of identification or not according to a service calling mode;

the processing module is used for establishing mapping information between the first class identification and the second class identification under the condition that the middle station service call is determined to relate to the second class identification;

and the processing module is used for enabling the target user group to call the middle station service through the mapping information.

15. An identification processing apparatus for invoking a midlet service, comprising:

the second sending module is used for sending the service calling request; the service calling request comprises a request identifier, and the request identifier is used for the central station to determine whether to respond to the service calling request;

the second receiving module is used for receiving the service calling response; the service calling response is returned by the middle station in response to the service calling request, and the service calling response comprises the middle station service corresponding to the request identifier.

16. An apparatus, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to: an identity handling method for invoking a midrange service as claimed in any of claims 1-9 or claims 10-13 when executing said executable instructions.

17. 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 identity handling method of invoking a midrange service of any one of claims 1-9 or claims 10-13.

Images