Cross-operator communication method and device, computer equipment, storage medium and computer program product

Abstract

The invention relates to a cross-operator communication method and device, computer equipment, a storage medium and a computer program product. The cross-operator communication method comprises the steps that service capability query requests sent by a first service platform and a second service platform respectively are received; determining a first service capability cooperation state of the first terminal according to a user identifier of the first terminal corresponding to the first service platform; determining a second service capability cooperation state of a second terminal according to a user identifier of the second terminal corresponding to the second service platform; determining target service capabilities called by the first service platform and the second service platform according to the service capability identifier, the first service capability coordination state and the second service capability coordination state; and respectively returning the information of the target service capability to the first service platform and the second service platform, so that the first service platform and the second service platform call the target service capability according to the information of the target service capability. By adopting the method, the cooperative selection of the service capability of the service platform in a cross-operator scene can be realized.

Description

Technical Field

[0001] The present application relates to the field of communication technologies, and in particular, to a cross-operator communication method, apparatus, computer device, storage medium, and computer program product. Background Art

[0002] With the development of services under the service platform, it is an inevitable trend that service scenarios become increasingly complex. Therefore, there is a need for a sufficient number of service capabilities to be called by the service platform to implement corresponding service functions. However, the service capabilities to be called may come from different operators or service capability providers. Moreover, the service capabilities called by the service platforms of different operators may be different, resulting in problems such as unequal service functions between the two parties during cross-operator communication. For example, during cross-operator communication of digital humans, different translation or knowledge base large models are called by the digital humans on both sides, resulting in inconsistent cognitions during communication.

[0003] Therefore, the method of bundling service platforms with service capability calls one by one in related technologies is difficult to meet the communication requirements in cross-operator scenarios. Summary of the Invention

[0004] Based on this, in view of the technical problem that the method of bundling service platforms with service capability calls one by one is difficult to meet the communication requirements in cross-operator scenarios, it is necessary to provide a cross-operator communication method, apparatus, computer device, computer-readable storage medium, and computer program product.

[0005] In a first aspect, the present application provides a cross-operator communication method. Applied to a service capability collaborative decision-making system, the service capability collaborative decision-making system is used for collaborative processing of service capability calls between a first service platform under a first operator and a second service platform under a second operator. The method includes:

[0006] Receiving service capability query requests respectively sent by the first service platform and the second service platform; the service capability query request carries a user identifier of a terminal corresponding to the service platform and a service capability identifier of the service capability to be called;

[0007] Determining a first service capability collaboration status of the first terminal according to the user identifier of the first terminal corresponding to the first service platform; determining a second service capability collaboration status of the second terminal according to the user identifier of the second terminal corresponding to the second service platform;

[0008] Determining target service capabilities called by the first service platform and the second service platform according to the service capability identifier, the first service capability collaboration status, and the second service capability collaboration status;

[0009] Return the information of the target service capabilities to the first service platform and the second service platform respectively, so that the first service platform and the second service platform can invoke the target service capabilities according to the information of the target service capabilities.

[0010] In one embodiment, the determining of the target service capabilities invoked by the first service platform and the second service platform according to the service capability identifier, the first service capability collaboration status, and the second service capability collaboration status includes:

[0011] If both the first service capability collaboration status and the second service capability collaboration status are collaborative, determine the target service capabilities from the service capabilities bound to any service platform according to the service capability identifier;

[0012] If one of the first service capability collaboration status and the second service capability collaboration status is collaborative and the other is non - collaborative, determine the target service capabilities from the service capabilities bound to the service platform corresponding to the terminal with the non - collaborative service capability collaboration status according to the service capability identifier.

[0013] In one embodiment, before determining the first service capability collaboration status of the first terminal corresponding to the first service platform according to the user identifier of the first terminal corresponding to the first service platform, it further includes:

[0014] Receive a first service capability collaboration trigger event reported by a first inter - communication gateway corresponding to the first service platform; the first service capability collaboration trigger event carries the user identifier of the first terminal corresponding to the first service platform;

[0015] Mark the first service capability collaboration status of the first terminal according to the user identifier of the first terminal.

[0016] Before determining the second service capability collaboration status of the second terminal corresponding to the second service platform according to the user identifier of the second terminal corresponding to the second service platform, it further includes:

[0017] Receive a second service capability collaboration trigger event reported by a second inter - communication gateway corresponding to the second service platform; the second service capability collaboration trigger event carries the user identifier of the second terminal corresponding to the second service platform;

[0018] Mark the second service capability collaboration status of the second terminal according to the user identifier of the second terminal.

[0019] In one embodiment, the first service capability collaboration trigger event is sent when the first inter - communication gateway receives a message that the first terminal and the second terminal have successfully established a cross - network call;

[0020] The second service capability collaboration triggering event is sent when the second interworking gateway receives a message that the first terminal and the second terminal have successfully established a cross-network call.

[0021] In one embodiment, before receiving the first service capability collaboration triggering event reported by the first interworking gateway corresponding to the first service platform, it further includes:

[0022] Sending a subscription request for the first service capability collaboration triggering event to the first interworking gateway; receiving a message indicating successful subscription returned by the first interworking gateway;

[0023] Before receiving the second service capability collaboration triggering event reported by the second interworking gateway corresponding to the second service platform, it further includes:

[0024] Sending a subscription request for the second service capability collaboration triggering event to the second interworking gateway; receiving a message indicating successful subscription returned by the second interworking gateway.

[0025] In one embodiment, after respectively returning the information of the target service capability to the first service platform and the second service platform, it further includes:

[0026] Receiving a first service capability collaboration ending event sent by the first interworking gateway corresponding to the first service platform; the first service capability collaboration ending event carries the user identifier of the first terminal, and the first service capability collaboration ending event is sent by the first interworking gateway when receiving a message indicating the end of a cross-network call;

[0027] Updating the service capability collaboration status of the first terminal according to the user identifier of the first terminal;

[0028] And,

[0029] Receiving a second service capability collaboration ending event sent by the second interworking gateway corresponding to the second service platform; the second service capability collaboration ending event carries the user identifier of the second terminal, and the second service capability collaboration ending event is sent by the second interworking gateway when receiving a message indicating the end of a cross-network call;

[0030] Updating the service capability collaboration status of the second terminal according to the user identifier of the second terminal.

[0031] In a second aspect, the present application further provides a cross-operator communication device. Applied to a service capability collaboration decision-making system, the service capability collaboration decision-making system is used for collaborative processing of service capability invocation between a first service platform under a first operator and a second service platform under a second operator. The device includes:

[0032] A request receiving module, configured to receive service capability query requests respectively sent by a first service platform and a second service platform; the service capability query requests carry user identifiers of terminals corresponding to the service platforms and service capability identifiers of the invoked service capabilities;

[0033] A status determination module, configured to determine a first service capability collaboration status of a first terminal corresponding to the first service platform according to the user identifier of the first terminal; and determine a second service capability collaboration status of a second terminal corresponding to the second service platform according to the user identifier of the second terminal;

[0034] A capability determination module, configured to determine a target service capability invoked by the first service platform and the second service platform according to the service capability identifier, the first service capability collaboration status, and the second service capability collaboration status;

[0035] An information return module, configured to return information of the target service capability to the first service platform and the second service platform respectively, so that the first service platform and the second service platform invoke the target service capability according to the information of the target service capability.

[0036] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and when the processor executes the computer program, the method described in any one of the above is implemented.

[0037] In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, and when the computer program is executed by a processor, the method described in any one of the above is implemented.

[0038] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the method described in any one of the above is implemented.

[0039] The above cross-operator communication method, device, computer equipment, storage medium and computer program product receive service capability query requests sent by a first service platform and a second service platform, determine a first service capability collaboration status of a first terminal corresponding to the first service platform according to a user identifier of the first terminal; determine a second service capability collaboration status of a second terminal corresponding to the second service platform according to a user identifier of the second terminal; determine a target service capability invoked by the first service platform and the second service platform according to a service capability identifier, the first service capability collaboration status and the second service capability collaboration status; and respectively return information of the target service capability to the first service platform and the second service platform, so that the first service platform and the second service platform invoke the target service capability according to the information of the target service capability. By setting up a service capability collaboration decision system, this method can achieve collaborative selection of service capabilities by service platforms in a cross-operator scenario, enable the first service platform and the second service platform to invoke the same service capabilities, solve the problems and defects that in the related technology, service platforms are bundled one by one with service capability invocations and cannot select different service capability providers according to service functions and policies in a cross-operator scenario, and promote the large-scale development of service capability opening and sharing. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 FIG. is an application environment diagram of the cross-operator communication method in an embodiment;

[0041] Figure 2 FIG. is a schematic flowchart of the cross-operator communication method in an embodiment;

[0042] Figure 3 FIG. is a schematic flowchart of the target service capability determination step in an embodiment;

[0043] Figure 4 FIG. is a schematic diagram of a first interaction process of service capability collaborative invocation in a cross-operator scenario in an embodiment;

[0044] Figure 5 FIG. is a schematic diagram of a second interaction process of service capability collaborative invocation in a cross-operator scenario in an embodiment;

[0045] Figure 6 FIG. is a structural block diagram of the cross-operator communication device in an embodiment;

[0046] Figure 7 FIG. is an internal structural diagram of the computer equipment in an embodiment. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0047] In order to make the objectives, technical solutions, and advantages of the present application clearer and more understandable, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0048] It should be noted that the terms "first", "second", etc. in the description and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and do not necessarily need to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein.

[0049] The cross-operator communication method provided by the embodiments of the present application can be applied to, for example, Figure 1 the application environment shown. Among them, the service capability collaborative decision-making system 104 communicates with the first service platform under the first operator 102 and the second service platform under the second operator 106 through the network respectively. There is also a first terminal and a first interworking gateway corresponding to the first operator 102, and a second terminal and a second interworking gateway corresponding to the second operator 106. The first interworking gateway is a bridge for the first terminal to perform cross-network communication, and the second interworking gateway is a bridge for the second terminal to perform cross-network communication. The first terminal establishes cross-network communication with the second terminal through the first interworking gateway and the second interworking gateway. Among them, the service platform represents the core system that provides specific services or applications, such as a video platform, a payment system, etc. An operator represents an entity that provides basic communication network services. The terminal can be, but is not limited to, various personal computers, laptop computers, smart phones, tablet computers, Internet of Things devices, and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. The portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc.

[0050] In one embodiment, as Figure 2 shown, a cross-operator communication method is provided. Taking the method applied to the service capability collaborative decision-making system 104 in Figure 1 as an example for description, the service capability collaborative decision-making system is used for the collaborative processing of service capability invocation between the first service platform under the first operator and the second service platform under the second operator. In this embodiment, the method includes the following steps:

[0051] Step S210, receiving service capability query requests sent by the first service platform and the second service platform respectively; the service capability query request carries the user identifier of the terminal corresponding to the service platform and the service capability identifier of the invoked service capability.

[0052] In a specific implementation, the business platform initiates a business capability query request to the business capability collaborative decision-making system according to the business logic. The business capability query request carries the user identifier of the terminal corresponding to the business platform and the business capability identifier of the called business capability.

[0053] For example, a first service capability query request sent by a first service platform is received, and the first service capability query request carries the user identifier of the first terminal and the service capability identifier of the service capability called by the first service platform. A second service capability query request sent by a second service platform is received, and the second service capability query request carries the user identifier of the second terminal and the service capability identifier of the service capability called by the second service platform.

[0054] It should be noted that the present application is applied to a scenario of cross-operator communication, and the service capability identifiers of the service capabilities called by the first service platform and the second service platform are the same.

[0055] In some embodiments, a business capability collaborative query module is provided in both the first business platform and the second business platform. Receiving a business capability query request sent by the business platform specifically includes receiving a business capability query request sent by the business capability collaborative query module in the business platform.

[0056] Step S220, determining a first service capability coordination state of the first terminal according to a user identifier of the first terminal corresponding to the first service platform; determining a second service capability coordination state of the second terminal according to a user identifier of the second terminal corresponding to the second service platform.

[0057] The business capability collaboration status includes collaboration and non-collaboration.

[0058] Specifically, the business capability collaborative decision system pre-stores the business capability collaborative contract information (including business capability identification, business capability address, whether it is cross-operator, etc.) of different users issued by the business support acceptance system. The business capability collaborative status is determined according to the user identification, which can be determined by querying the business capability collaborative contract information. That is, according to the user identification of the first terminal corresponding to the first business platform, the business capability collaborative contract information is queried to obtain the first business capability collaborative status of the first terminal; according to the user identification of the second terminal corresponding to the second business platform, the business capability collaborative contract information is queried to obtain the second business capability collaborative status of the second terminal.

[0059] Step S230: determining the target business capability to be called by the first business platform and the second business platform according to the business capability identifier, the first business capability coordination state and the second business capability coordination state.

[0060] In specific implementation, the service capability identifiers of the service capabilities invoked by the first service platform and the second service platform are the same. Based on the first service capability collaboration status and the second service capability collaboration status, the target service capability invoked by the first service platform and the second service platform is determined, that is, to select whether to invoke the service capability bound by the first service platform or the service capability bound by the second service platform.

[0061] If the service capability bound by the first service platform is selected as the target service capability, for the first service platform, it belongs to the service capability invocation for in-network communication, while for the second service platform, it belongs to the service capability invocation across operators.

[0062] Similarly, if the service capability bound by the second service platform is selected as the target service capability, for the first service platform, it belongs to the service capability invocation across operators, while for the second service platform, it belongs to the service capability invocation for in-network communication.

[0063] Step S240: Return the information of the target service capability to the first service platform and the second service platform respectively, so that the first service platform and the second service platform can invoke the target service capability according to the information of the target service capability.

[0064] Among them, the information of the target service capability includes the identifier and address of the target service capability.

[0065] In specific implementation, after determining the target service capability invoked by the first service platform and the second service platform, the identifier and address of the target service capability can be obtained as the information of the target service capability, and then returned to the first service platform and the second service platform respectively. The first service platform and the second service platform can invoke the corresponding service capabilities according to the identifier and address of the target service capability, thereby enabling the first service platform and the second service platform to invoke the same service capability.

[0066] In the above cross-operator communication method, a service capability query request sent by a first service platform and a second service platform is received. According to the user identifier of a first terminal corresponding to the first service platform, a first service capability collaboration status of the first terminal is determined; according to the user identifier of a second terminal corresponding to the second service platform, a second service capability collaboration status of the second terminal is determined; according to a service capability identifier, the first service capability collaboration status, and the second service capability collaboration status, a target service capability invoked by the first service platform and the second service platform is determined; information about the target service capability is respectively returned to the first service platform and the second service platform, so that the first service platform and the second service platform can invoke the target service capability according to the information about the target service capability. By setting up a service capability collaboration decision-making system, this method can realize the collaborative selection of service capabilities by service platforms in a cross-operator scenario, enabling the first service platform and the second service platform to invoke the same service capability, and solving the problems and defects in the related technology where the service platform and service capability invocation are bundled one by one and it is impossible to select different service capability providers according to service functions and policies in a cross-operator scenario, thus promoting the large-scale development of service capability opening and sharing.

[0067] In an exemplary embodiment, as Figure 3 shown, the above step S230 determines the target service capability invoked by the first service platform and the second service platform according to the service capability identifier, the first service capability collaboration status, and the second service capability collaboration status, including:

[0068] Step S231, if both the first service capability collaboration status and the second service capability collaboration status are collaborative, then according to the service capability identifier, determine the target service capability from the service capabilities bound by any one of the service platforms;

[0069] Step S232, if one of the first service capability collaboration status and the second service capability collaboration status is collaborative and the other is non-collaborative, then according to the service capability identifier, determine the target service capability from the service capabilities bound by the service platform corresponding to the terminal with the non-collaborative service capability collaboration status.

[0070] In specific implementation, the service capability collaboration decision-making system determines the service capability invoked this time according to information such as the service capability identifier and the service capability collaboration statuses corresponding to the two service platforms. Specifically, if both the first service capability collaboration status and the second service capability collaboration status are collaborative, then according to the service capability identifier, determine the target service capability from the service capabilities bound by any one of the service platforms, that is, either determine the service capability corresponding to the service capability identifier from the service capabilities bound by the first service platform as the target service capability; or determine the service capability corresponding to the service capability identifier from the service capabilities bound by the second service platform as the target service capability, as long as the target service capabilities invoked by the two service platforms are the same.

[0071] If one of the first service capability collaboration status and the second service capability collaboration status is collaboration and the other is non - collaboration, it indicates that one service platform cannot perform cross - carrier service capability invocation but can only perform in - network service capability invocation. Therefore, the target service capability can be determined from the service capabilities bound to the service platform corresponding to the terminal with the non - collaborative service capability collaboration status according to the service capability identifier, so that the two service platforms can invoke the same target service capability.

[0072] In another case, if both the first service capability collaboration status and the second service capability collaboration status are non - collaborative, that is, neither of the two service platforms can perform cross - carrier service capability invocation but can only perform in - network service capability invocation, then only the two service platforms can each invoke the service capabilities bound to themselves.

[0073] In this embodiment, the service capabilities to be invoked this time are determined based on information such as the service capability collaboration status corresponding to the two service platforms. When the service capability collaboration statuses corresponding to the two are different or the same, different service capability selection strategies are adopted respectively to ensure that the two service platforms can invoke the same target service capability, achieving the goal of selecting different service capability providers according to service functions and policies in the cross - carrier scenario, and solving the problem that in the related technology, the service platform and service capability invocation are bundled one by one and it is impossible to select different service capability providers according to service functions and policies in the cross - carrier scenario.

[0074] In an exemplary embodiment, before the above step S220 determines the first service capability collaboration status of the first terminal corresponding to the first service platform according to the user identifier of the first terminal, it further includes: receiving a first service capability collaboration trigger event reported by the first inter - working gateway corresponding to the first service platform; the first service capability collaboration trigger event carries the user identifier of the first terminal corresponding to the first service platform; marking the first service capability collaboration status of the first terminal according to the user identifier of the first terminal.

[0075] Before determining the second service capability collaboration status of the second terminal corresponding to the second service platform according to the user identifier of the second terminal, it further includes: receiving a second service capability collaboration trigger event reported by the second inter - working gateway corresponding to the second service platform; the second service capability collaboration trigger event carries the user identifier of the second terminal corresponding to the second service platform; marking the second service capability collaboration status of the second terminal according to the user identifier of the second terminal.

[0076] Specifically, the business capability collaboration status of the terminal is determined by the business capability collaboration decision system according to the user ID of the terminal, and the user ID of the terminal is extracted from the business capability collaboration trigger event reported by the intercommunication gateway. Specifically, the business capability collaboration contract information (including business capability ID, business capability address, whether it is cross-operator, etc.) issued by the pre-stored business support acceptance system can be queried according to the user ID to determine whether the business capability collaboration status of the terminal is collaborative or not, and then mark it.

[0077] For example, for the first business platform, the first intercommunication gateway corresponding to the first business platform reports the first business capability collaboration trigger event to the business capability collaboration decision system. The business capability collaboration trigger event carries the user identifier of the first terminal. The business capability collaboration decision system determines the business capability collaboration status of the first terminal as collaborative or non-collaborative based on the user identifier of the first terminal, and marks it.

[0078] Similarly, for the second business platform, the second intercommunication gateway corresponding to the second business platform reports the second business capability collaboration trigger event to the business capability collaboration decision system. The business capability collaboration trigger event carries the user identifier of the second terminal. The business capability collaboration decision system determines the business capability collaboration status of the second terminal as collaborative or non-collaborative based on the user identifier of the second terminal, and marks it.

[0079] In some embodiments, the first service capability collaboration triggering event is sent when the first intercommunication gateway receives a message that the first terminal and the second terminal have successfully established a cross-network call; the second service capability collaboration triggering event is sent when the second intercommunication gateway receives a message that the first terminal and the second terminal have successfully established a cross-network call.

[0080] Specifically, when the intercommunication gateway corresponding to the service platform receives a message that the first terminal and the second terminal have successfully established an inter-network call, the service capability collaboration triggering event is sent to the service capability collaborative decision-making system.

[0081] Taking the user of the first terminal as the calling user and the user of the second terminal as the called user as an example, the process of successfully establishing an inter-network call between the first terminal and the second terminal is as follows: the first terminal initiates an inter-network call request to the second terminal, the call request is sent to the second terminal via the first intercommunication gateway and the second intercommunication gateway, and the second terminal returns a call success message to the second intercommunication gateway.

[0082] The second interworking gateway reports the service capability collaborative triggering event carrying the called user ID to the service capability collaborative decision system according to the call success message. The call success message is forwarded to the first interworking gateway. The first interworking gateway reports the service capability collaborative triggering event carrying the calling user ID to the service capability collaborative decision system according to the call success message. At the same time, the first interworking gateway forwards the call success message to the first terminal.

[0083] In some embodiments, a service capability collaboration notification module is provided in the first interworking gateway and the second interworking gateway, and the call success message forwards and reports the service capability collaboration trigger event through the service capability collaboration notification module.

[0084] In the above embodiments, when the interworking gateways corresponding to the first service platform and the second service platform receive the message that the first terminal and the second terminal have successfully established a cross-network call, they send a service capability collaboration trigger event carrying the user identifier of the corresponding terminal to the service capability collaboration decision-making system, so that the service capability collaboration decision-making system marks the service capability collaboration status of the corresponding terminal according to the user identifier, so as to facilitate the selection of service capabilities according to the marked service capability collaboration status in the future.

[0085] In an exemplary embodiment, before receiving the first service capability collaboration trigger event reported by the first interworking gateway corresponding to the first service platform, it further includes: sending a first service capability collaboration trigger event subscription request to the first interworking gateway; receiving a message indicating successful subscription returned by the first interworking gateway;

[0086] Before receiving the second service capability collaboration trigger event reported by the second interworking gateway corresponding to the second service platform, it further includes: sending a second service capability collaboration trigger event subscription request to the second interworking gateway; receiving a message indicating successful subscription returned by the second interworking gateway.

[0087] Specifically, the service capability collaboration decision-making system stores the service capability collaboration subscription information issued by the service support acceptance system, including information such as service capability identifier, service capability address, and whether it is cross-operator. The service capability collaboration decision-making system initiates a subscription to the service capability collaboration trigger event for the interworking gateways corresponding to each service platform, that is, it initiates a subscription to the service capability collaboration trigger event for the first interworking gateway corresponding to the first service platform and the second interworking gateway corresponding to the second service platform respectively, so as to receive the service capability collaboration trigger events sent by each service platform in the future to execute the call decision of the collaboration capability.

[0088] In some embodiments, a service capability collaboration notification module is provided in the first interworking gateway and the second interworking gateway. Sending a service capability collaboration trigger event subscription request to the interworking gateway corresponding to the service platform specifically means initiating a service capability collaboration trigger event subscription request to the service capability collaboration notification module in the interworking gateway.

[0089] In this embodiment, by sending a service capability collaboration trigger event subscription to the interworking gateways corresponding to the two service platforms, it is convenient to receive the service capability collaboration trigger events reported by the first interworking gateway or the second interworking gateway in the future.

[0090] In an exemplary embodiment, after the step S240 returns the information of the target service capability to the first service platform and the second service platform respectively, it also includes: receiving a first service capability collaboration end event sent by a first intercommunication gateway corresponding to the first service platform; the first service capability collaboration end event carries a user identifier of the first terminal, and the first service capability collaboration end event is sent by the first intercommunication gateway when receiving a message indicating that a cross-network call has ended; updating the service capability collaboration state of the first terminal according to the user identifier of the first terminal;

[0091] And, receiving a second business capability collaboration end event sent by a second intercommunication gateway corresponding to the second business platform; the second business capability collaboration end event carries the user identifier of the second terminal, and the second business capability collaboration end event is sent by the second intercommunication gateway when receiving a message that the cross-network call ends; according to the user identifier of the second terminal, updating the business capability collaboration status of the second terminal.

[0092] Specifically, after the inter-network call ends, the first terminal initiates an inter-network call end request to the second terminal, the call end request is sent to the second terminal via the first intercommunication gateway and the second intercommunication gateway, and the second terminal returns a call end message to the second intercommunication gateway.

[0093] The second intercommunication gateway reports a service capability collaboration end event to the service capability collaboration decision system based on the call end message. The service capability collaboration end event carries the called user ID. The service capability collaboration decision system updates the service capability collaboration status of the called user to uncollaborated based on the user ID.

[0094] The first interworking gateway receives the call end message forwarded from the second interworking gateway, and reports a service capability collaborative end event to the service capability collaborative decision system according to the call end message, and the service capability collaborative end event carries the calling user ID. The service capability collaborative decision system marks the service capability collaborative state of the calling user as uncollaborated according to the user ID.

[0095] In some embodiments, a business capability collaborative notification module is provided in the first intercommunication gateway and the second intercommunication gateway to report the business capability collaborative termination event to the business capability collaborative decision-making system. Specifically, the business capability collaborative notification module in the first intercommunication gateway and the second intercommunication gateway reports the business capability collaborative termination event to the business capability collaborative decision-making system.

[0096] In this embodiment, by enabling the intercommunication gateway to send a service capability collaboration end event to the service capability collaboration decision system upon receiving a message indicating the end of a cross-network call, the service capability collaboration decision system can timely update the service capability collaboration status of the corresponding terminal according to the user identifier to ensure the real-time and accurate service capability collaboration status of the terminal.

[0097] In one embodiment, to more clearly illustrate the cross-operator communication method provided by the embodiments of the present application, the following will be described in conjunction with specific examples of the accompanying drawings. The present application can be applied to mobile network services and network capability open, OTT (Over The Top, referring to Internet companies providing various services through the Internet) service capability open, and provide mobile networks and service capabilities for operator self-operated and third-party service platforms.

[0098] The main implementation means of the cross-operator communication method provided by the present application include:

[0099] 1. Add a service capability collaboration notification module to the interworking gateway: responsible for reporting service capability call collaboration trigger events and end events in cross-operator communication scenarios. Specifically, it includes: receiving service capability collaboration trigger event subscriptions initiated by the service capability collaboration decision system. After a cross-operator call is successfully established, reporting the service capability collaboration trigger event to the service capability collaboration decision system, carrying information such as the calling and called user identifiers. After the cross-operator call ends, reporting the service capability collaboration end event to the service capability collaboration decision system, carrying information such as the calling and called user identifiers.

[0100] 2. Add a service capability collaboration decision system: responsible for storing, managing service capability collaboration and call information in cross-operator communication scenarios, and selecting collaboration strategies for service capability calls. Specifically, it includes: subscribing to service capability collaboration trigger events from the service capability collaboration notification module. Receiving the service capability collaboration trigger events reported by the service capability collaboration notification module, and marking the service capability collaboration status according to the user identifier. Receiving service capability query requests initiated by the service capability collaboration query module, determining the service capabilities to be called this time based on information such as service capability identifiers, user identifiers, and service capability collaboration status (querying the service capability collaboration status according to the user identifier, if the service capability collaboration status is collaborative, select the service capabilities for cross-operator communication calls; if the service capability status is non-collaborative, select the service capabilities for in-network communication calls), and returning information such as the service capability identifier and address to be called this time to the service capability collaboration query module. Receiving the service capability collaboration end events reported by the service capability collaboration notification module, and marking the service capability collaboration status according to the user identifier.

[0101] 3. Add a service capability collaboration query module to the service platform: responsible for querying service capabilities to be called. According to the service logic, initiate a service capability query request to the service capability collaboration decision system, carrying information such as user identifiers and service capability identifiers. Receiving information such as the service capability identifier and address returned by the service capability collaboration decision system.

[0102] Reference Figure 4, a schematic diagram of the first interaction process for collaborative invocation of service capabilities in a cross-operator scenario shown in an embodiment. The steps are as follows:

[0103] / / Steps 1-3 are the processes of storing service capability subscription information and subscribing to collaborative events.

[0104] Step 1. The service capability collaborative decision-making system stores the service capability collaborative subscription information sent by the service support acceptance system, including service capability identifier, service capability address, whether it is cross-operator, and other information.

[0105] Steps 2-3. The service capability collaborative decision-making system initiates a subscription to the service capability collaborative trigger event to the service capability collaborative notification module of the interworking gateway.

[0106] / / Steps 4-15 are the processes of successful cross-network call establishment and reporting of the service capability collaborative trigger event.

[0107] Steps 4-7. Terminal 1 initiates a cross-network call request to Terminal 2. The call request is sent to Terminal 2 through Interworking Gateway 1 and Interworking Gateway 2. Terminal 2 returns a call success message to Interworking Gateway 2.

[0108] Steps 8-9. The service capability collaborative notification module of Interworking Gateway 2 reports the service capability collaborative trigger event to the service capability collaborative decision-making system according to the call success establishment message. The service capability collaborative trigger event carries information such as the called user identifier.

[0109] Step 10. The service capability collaborative decision-making system marks the service capability collaborative status according to the user identifier. For example, it marks the service capability collaborative status of the called user as collaborative.

[0110] Step 11. Interworking Gateway 1 receives the call success message forwarded from Interworking Gateway 2.

[0111] Steps 12-13. The service capability collaborative notification module of Interworking Gateway 1 reports the service capability collaborative trigger event to the service capability collaborative decision-making system according to the call success establishment message. The service capability collaborative trigger event carries information such as the calling user identifier.

[0112] Step 14. The service capability collaborative decision-making system marks the service capability collaborative status according to the user identifier. For example, it marks the service capability collaborative status of the calling user as collaborative.

[0113] Step 15. Terminal 1 receives the call success message forwarded from Interworking Gateway 1. Terminal 1 and Terminal 2 establish a cross-network call.

[0114] Reference Figure 5 , a schematic diagram of the second interaction process for collaborative invocation of service capabilities in a cross-operator scenario shown in an embodiment. The steps are as follows:

[0115] / / Steps 16-23 are the service capability call selection process during the cross-network call.

[0116] Steps 16-17: The business capability collaborative query module of business platform 1 initiates a business capability query request to the business capability collaborative decision-making system according to the business logic. The business capability query request carries information such as the calling user ID and the business capability ID.

[0117] Step 18. The business capability collaborative decision system determines the business capability being called this time based on the business capability ID, user ID, business capability collaborative status and other information: for example, if the business capability collaborative status is queried based on the calling user ID, and the business capability collaborative status is collaborative, the business capability called for cross-operator communication is selected; if the business capability status is uncoordinated, the business capability called for intra-network communication is selected.

[0118] Step 19: The business capability collaborative decision system returns information such as the business capability identifier and address to the business capability collaborative query module of business platform 1.

[0119] Steps 20-21: The business capability collaborative query module of business platform 2 initiates a business capability query request to the business capability collaborative decision-making system according to the business logic. The business capability query request carries information such as the called user ID and the business capability ID.

[0120] Step 22, the business capability collaborative decision system determines the business capability being called this time based on the business capability ID, user ID, business capability collaborative status and other information: if the business capability collaborative status is queried based on the called user ID, and the business capability collaborative status is collaborative, then the business capability called for cross-operator communication is selected; if the business capability status is uncoordinated, then the business capability called for intra-network communication is selected.

[0121] Step 23: The business capability collaborative decision system returns information such as the business capability identifier and address to the business capability collaborative query module of the business platform 2.

[0122] / / Steps 24-34 are the process of reporting the cross-network call end and business capability collaborative end event.

[0123] Steps 24-27, Terminal 1 initiates an inter-network call termination request to Terminal 2, the call termination request is sent to Terminal 2 via Interworking Gateway 1 and Interworking Gateway 2, and Terminal 2 returns a call termination message to Interworking Gateway 2.

[0124] Steps 28-29: The service capability coordination notification module of the interworking gateway 2 reports a service capability coordination end event to the service capability coordination decision system according to the call end message. The service capability coordination end event carries information such as the called user ID.

[0125] Step 30: The service capability collaboration decision system marks the service capability collaboration status according to the user identifier, for example, marks the service capability collaboration status of the called user as non-collaborative.

[0126] Step 31: The interworking gateway 1 receives the call end message forwarded from the interworking gateway 2.

[0127] Steps 32 - 33: The service capability collaboration notification module of the interworking gateway 1 reports the service capability collaboration end event to the service capability collaboration decision system according to the call end message. The service capability collaboration end event carries information such as the calling user identifier.

[0128] Step 34: The service capability collaboration decision system marks the service capability collaboration status according to the user identifier, for example, marks the service capability collaboration status of the calling user as non-collaborative.

[0129] The method for service capability collaboration invocation provided by this application supports the collaboration of service capability invocation in the cross-operator scenario of the service platform, solves the problems and defects in the prior art that the service platform is bundled with service capability invocation one by one and cannot select different service capability providers according to service functions and policies in the cross-operator scenario, and promotes the large-scale development of service capability opening and sharing.

[0130] It should be understood that although the steps in the flowcharts involved in the above-described embodiments are shown in sequence according to the arrows, these steps do not necessarily execute in the order indicated by the arrows. Unless there is a clear indication in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-described embodiments may include multiple steps or multiple stages. These steps or stages do not necessarily execute at the same moment, but can execute at different moments, and the execution order of these steps or stages is not necessarily sequential, but can be executed alternately or in turn with at least a part of other steps or steps or stages in other steps.

[0131] Based on the same inventive concept, the embodiments of this application also provide a cross-operator communication device for implementing the above-mentioned cross-operator communication method. The solution for solving problems provided by this device is similar to the solution described in the above method. Therefore, the specific limitations in one or more cross-operator communication device embodiments provided below can refer to the limitations on the cross-operator communication method in the above text, and will not be repeated here.

[0132] In one embodiment, as Figure 6 shown, a cross-operator communication device is provided, including:

[0133] A request receiving module 610, configured to receive service capability query requests respectively sent by a first service platform and a second service platform; the service capability query requests carry user identifiers of terminals corresponding to the service platforms and service capability identifiers of the invoked service capabilities.

[0134] A status determination module 620, configured to determine a first service capability collaboration status of a first terminal corresponding to the first service platform according to the user identifier of the first terminal; and determine a second service capability collaboration status of a second terminal corresponding to the second service platform according to the user identifier of the second terminal.

[0135] A capability determination module 630, configured to determine a target service capability invoked by the first service platform and the second service platform according to the service capability identifier, the first service capability collaboration status, and the second service capability collaboration status.

[0136] An information return module 640, configured to return information of the target service capability to the first service platform and the second service platform respectively, so that the first service platform and the second service platform can invoke the target service capability according to the information of the target service capability.

[0137] In one embodiment, the capability determination module 630 is further configured to, if both the first service capability collaboration status and the second service capability collaboration status are collaborative, determine the target service capability from the service capabilities bound by any one of the service platforms according to the service capability identifier; if one of the first service capability collaboration status and the second service capability collaboration status is collaborative and the other is non - collaborative, determine the target service capability from the service capabilities bound by the service platform corresponding to the terminal with the non - collaborative service capability collaboration status according to the service capability identifier.

[0138] In one embodiment, the apparatus further includes a marking module, configured to receive a first service capability collaboration trigger event reported by a first inter - working gateway corresponding to the first service platform; the first service capability collaboration trigger event carries the user identifier of the first terminal corresponding to the first service platform; mark the first service capability collaboration status of the first terminal according to the user identifier of the first terminal; and receive a second service capability collaboration trigger event reported by a second inter - working gateway corresponding to the second service platform; the second service capability collaboration trigger event carries the user identifier of the second terminal corresponding to the second service platform; mark the second service capability collaboration status of the second terminal according to the user identifier of the second terminal.

[0139] In one embodiment, the first service capability collaboration trigger event is sent when the first inter - working gateway receives a message that the first terminal and the second terminal have successfully established a cross - network call; the second service capability collaboration trigger event is sent when the second inter - working gateway receives a message that the first terminal and the second terminal have successfully established a cross - network call.

[0140] In one embodiment, the device further includes a subscription module, configured to send a first service capability coordination trigger event subscription request to a first interworking gateway; receive a message indicating successful subscription returned by the first interworking gateway; and send a second service capability coordination trigger event subscription request to a second interworking gateway; receive a message indicating successful subscription returned by the second interworking gateway.

[0141] In one embodiment, the marking module is further configured to receive a first service capability coordination end event sent by the first interworking gateway corresponding to the first service platform; the first service capability coordination end event carries the user identifier of the first terminal, and the first service capability coordination end event is sent by the first interworking gateway when receiving a message indicating the end of a cross-network call; update the service capability coordination status of the first terminal according to the user identifier of the first terminal; and receive a second service capability coordination end event sent by the second interworking gateway corresponding to the second service platform; the second service capability coordination end event carries the user identifier of the second terminal, and the second service capability coordination end event is sent by the second interworking gateway when receiving a message indicating the end of a cross-network call; update the service capability coordination status of the second terminal according to the user identifier of the second terminal.

[0142] Each module in the above cross-operator communication device can be implemented in whole or in part by software, hardware, or a combination thereof. The above modules can be embedded in the processor of the computer device in hardware form or be independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to the above respective modules.

[0143] In one embodiment, a computer device is provided. The computer device can be a terminal, and its internal structure diagram can be as Figure 7 shown. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operating system and the computer program stored in the non-volatile storage medium to run. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a cross-operator communication method. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, a trackball, or a touchpad provided on the housing of the computer device, or an external keyboard, touchpad, or mouse, etc.

[0144] Those skilled in the art can understand that Figure 7 The structure shown in Figure 7 is only a block diagram of some structures related to the solution of this application, and does not constitute a limitation on the computer device to which the solution of this application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine some components, or have different component arrangements.

[0145] In one embodiment, a computer device is further provided, including a memory and a processor. A computer program is stored in the memory, and when the processor executes the computer program, the steps in the above method embodiments are implemented.

[0146] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the steps in the above method embodiments are implemented.

[0147] In one embodiment, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the steps in the above method embodiments are implemented.

[0148] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data that have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data need to comply with the relevant laws, regulations, and standards of relevant countries and regions.

[0149] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, database, or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memories. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The databases involved in the embodiments provided in this application can include at least one of relational databases and non-relational databases. Non-relational databases can include distributed databases based on blockchain, etc., without limitation. The processors involved in the embodiments provided in this application can be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, data processing logics based on quantum computing, etc., without limitation.

[0150] The technical features of the above embodiments can be combined arbitrarily. For the sake of concise description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope recorded in this specification.

[0151] The above-described embodiments merely represent several implementation manners of this application. Their descriptions are relatively specific and detailed, but they should not be construed as limiting the patent scope of this application. It should be noted that for those of ordinary skill in the art, without departing from the concept of this application, several modifications and improvements can still be made, and these all belong to the protection scope of this application. Therefore, the protection scope of this application should be subject to the appended claims.

Claims

1. A cross-operator communication method, characterized in that: Applied to a business capability collaborative decision system, the business capability collaborative decision system is used for collaborative processing of business capability calls between a first business platform under a first operator and a second business platform under a second operator, the method comprising: Receiving service capability query requests respectively sent by the first service platform and the second service platform; the service capability query request carries a user identifier of a terminal corresponding to the service platform and a service capability identifier of the called service capability; Determine, according to a user identifier of a first terminal corresponding to the first service platform, a first service capability collaboration state of the first terminal; and determine, according to a user identifier of a second terminal corresponding to the second service platform, a second service capability collaboration state of the second terminal; Determining a target business capability called by the first business platform and the second business platform according to the business capability identifier, the first business capability collaboration state, and the second business capability collaboration state; The information of the target service capability is returned to the first service platform and the second service platform respectively, so that the first service platform and the second service platform call the target service capability according to the information of the target service capability.

2. The method according to claim 1, characterized in that The determining, according to the business capability identifier, the first business capability collaboration state, and the second business capability collaboration state, the target business capability invoked by the first business platform and the second business platform includes: If the first business capability collaboration state and the second business capability collaboration state are both collaboration, determining the target business capability from the business capabilities bound to any business platform according to the business capability identifier; If one of the first service capability collaboration state and the second service capability collaboration state is collaboration and the other is non-collaboration, the target service capability is determined from the service capabilities bound to the service platform corresponding to the terminal with the non-collaboration service capability collaboration state according to the service capability identifier.

3. The method according to claim 1, characterized in that Before determining the first service capability collaboration state of the first terminal according to the user identifier of the first terminal corresponding to the first service platform, the method further includes: receiving a first service capability collaboration triggering event reported by a first intercommunication gateway corresponding to the first service platform; the first service capability collaboration triggering event carries a user identifier of a first terminal corresponding to the first service platform; Marking a first service capability collaboration state of the first terminal according to a user identifier of the first terminal; Before determining the second service capability collaboration state of the second terminal according to the user identifier of the second terminal corresponding to the second service platform, the method further includes: receiving a second service capability collaboration triggering event reported by a second intercommunication gateway corresponding to the second service platform; the second service capability collaboration triggering event carries a user identifier of a second terminal corresponding to the second service platform; The second service capability collaboration state of the second terminal is marked according to the user identifier of the second terminal.

4. The method according to claim 3, characterized in that The first service capability collaboration triggering event is sent when the first interworking gateway receives a message that the first terminal and the second terminal have successfully established an inter-network call; The second service capability coordination triggering event is sent when the second interworking gateway receives a message indicating that a cross-network call is successfully established between the first terminal and the second terminal.

5. The method according to claim 3, characterized in that: Before receiving the first service capability coordination triggering event reported by the first intercommunication gateway corresponding to the first service platform, the method further includes: Sending a subscription request for a first service capability collaborative triggering event to the first intercommunication gateway; and receiving a subscription success message returned by the first intercommunication gateway; Before receiving the second service capability coordination triggering event reported by the second intercommunication gateway corresponding to the second service platform, the method further includes: Send a second service capability collaboration triggering event subscription request to the second intercommunication gateway; and receive a subscription success message returned by the second intercommunication gateway.

6. The method according to claim 1, characterized in that After returning the information of the target service capability to the first service platform and the second service platform respectively, the method further includes: receiving a first service capability collaboration end event sent by a first interworking gateway corresponding to the first service platform; the first service capability collaboration end event carries a user identifier of the first terminal, and the first service capability collaboration end event is sent by the first interworking gateway when receiving a message indicating that a cross-network call has ended; updating the service capability collaboration state of the first terminal according to the user identifier of the first terminal; as well as, receiving a second service capability collaboration end event sent by a second interworking gateway corresponding to the second service platform; the second service capability collaboration end event carries a user identifier of the second terminal, and the second service capability collaboration end event is sent by the second interworking gateway when receiving a message indicating that the cross-network call has ended; The service capability collaboration state of the second terminal is updated according to the user identifier of the second terminal.

7. A cross-operator communication device, characterized in that: Applied to a business capability collaborative decision system, the business capability collaborative decision system is used for collaborative processing of business capability calls between a first business platform under a first operator and a second business platform under a second operator, the device includes: A request receiving module, configured to receive service capability query requests respectively sent by the first service platform and the second service platform; the service capability query request carries a user identifier of a terminal corresponding to the service platform and a service capability identifier of the called service capability; a state determination module, configured to determine a first service capability collaboration state of the first terminal according to a user identifier of the first terminal corresponding to the first service platform; and determine a second service capability collaboration state of the second terminal according to a user identifier of the second terminal corresponding to the second service platform; A capability determination module, configured to determine a target business capability called by the first business platform and the second business platform according to the business capability identifier, the first business capability collaboration state, and the second business capability collaboration state; The information return module is used to return the information of the target business capability to the first business platform and the second business platform respectively, so that the first business platform and the second business platform call the target business capability according to the information of the target business capability.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images