Information processing method, application node and storage medium

Abstract

The invention provides an information processing method, an application node and a storage medium, and the method comprises the steps that a first application node sends a first media service operation request carrying service operation information corresponding to a target media service operation to a second application node, and the second application node performs dynamic decision by combining with the first service operation in the local second service operation global sensing table. By performing association analysis on the received service operation information and the local real-time service state, the second application node can dynamically judge whether to forward the request to the first terminal, thereby avoiding forced blocking or blind forwarding under a traditional static priority strategy. According to the embodiment of the invention, the dynamic conflict arbitration based on the real-time service state can be realized to avoid the forced service blocking caused by the static priority, the operation main body and intention are clarified through the service operation information to reduce the misjudgment risk, and the media operation request forwarding strategy is dynamically adjusted according to the global perception table to improve the cooperation efficiency.

Description

Technical Field

[0001] The embodiments of the present application relate to, but are not limited to, the field of communications, and in particular to an information processing method, an application node, and a storage medium. Background Art

[0002] In the existing IP Multimedia Subsystem (IMS), the Serving Call Session Control Function (S-CSCF) sequentially triggers multiple service application servers (ASs) using initial filtering rules (iFCs). However, this mechanism has significant flaws. Each AS handles services independently and lacks cross-node state awareness, leading to frequent media operation conflicts. Furthermore, the Session Description Protocol (SDP) can only describe media parameters but cannot clearly define the operator and intent, increasing the risk of misjudgment. In summary, the existing mechanism cannot achieve dynamic coordination based on real-time status and operational intent, and its reliance on static rules makes it difficult to adapt to complex business scenarios. Summary of the Invention

[0003] The embodiments of the present application provide an information processing method, an application node, and a storage medium, which can effectively solve problems such as insufficient service collaboration and conflict arbitration in existing IMS systems.

[0004] In one aspect, an embodiment of the present application provides an information processing method, applied to a first application node, the method comprising:

[0005] Sending a first media service operation request to the second application node, where the first media service operation request includes service operation information corresponding to the target media service operation,

[0006] The service operation information is used by the second application node to determine whether to forward the first media service operation request to the first terminal based on the service operation information and a first service operation, where the first service operation is a service operation being executed by the second application node recorded in a second service operation global perception table.

[0007] On the other hand, an embodiment of the present application provides an information processing method, applied to a second application node, the method comprising:

[0008] receiving a first media service operation request sent by a first application node, where the first media service operation request includes service operation information corresponding to a target media service operation;

[0009] determining whether to forward the first media service operation request to the first terminal according to the service operation information and a first service operation, where the first service operation is a service operation being executed by the second application node and recorded in a second service operation global awareness table;

[0010] In a case where it is determined to forward the first media service operation request to the first terminal, the first media service operation request is forwarded to the first terminal.

[0011] On the other hand, an embodiment of the present application further provides an application node, comprising: at least one processor; at least one memory for storing at least one program; and implementing the above-mentioned information processing method when at least one of the programs is executed by at least one of the processors.

[0012] On the other hand, an embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the information processing method described above.

[0013] On the other hand, an embodiment of the present application also provides a computer program product, including a computer program or computer instructions, wherein the computer program or the computer instructions are stored in a computer-readable storage medium, the processor of the business application reads the computer program or the computer instructions from the computer-readable storage medium, and the processor executes the computer program or the computer instructions, so that the application node executes the information processing method as described above.

[0014] In an embodiment of the present application, the first application node sends a first media business operation request carrying business operation information corresponding to the target media business operation to the second application node, so that the second application node can make a dynamic decision based on the business operation being executed (i.e., the first business operation) recorded in its local second business operation global perception table. By correlating and analyzing the received business operation information with the local real-time business status, the second application node can dynamically determine whether to forward the request to the first terminal, avoiding forced blocking or blind forwarding under the traditional static priority strategy. The embodiment of the present application can implement dynamic conflict arbitration based on real-time business status to avoid forced blocking of business caused by static priority, clarify the operation subject and intention through business operation information to reduce the risk of misjudgment, and dynamically adjust the media operation request forwarding strategy according to the global perception table to improve collaborative efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 This is an IMS system architecture diagram provided by an embodiment of the present application;

[0016] Figure 2 is a flowchart of an information processing method provided by an embodiment of the present application;

[0017] Figure 3 is a flowchart of an information processing method provided by another embodiment of the present application;

[0018] Figure 4 is a flowchart of an information processing method provided by yet another embodiment of the present application;

[0019] Figure 5 This is a flowchart of inter-application business collaboration provided by a specific embodiment of the present application;

[0020] Figure 6 This is a flowchart of inter-application business collaboration provided by another specific embodiment of the present application;

[0021] Figure 7 This is a flow chart of inter-application business collaboration provided by another specific embodiment of the present application;

[0022] Figure 8 This is a flowchart of inter-application business collaboration provided by another specific embodiment of the present application;

[0023] Figure 9 This is a flow chart of inter-application business collaboration provided by another specific embodiment of the present application;

[0024] Figure 10 This is a flowchart of inter-application business collaboration provided by another specific embodiment of the present application;

[0025] Figure 11 This is a flowchart of inter-application business collaboration provided by another specific embodiment of the present application. DETAILED DESCRIPTION

[0026] In order to make the purpose, technical methods and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0027] It should be noted that although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in an order different from that in the flowchart. In the description of the specification, claims and the above-mentioned drawings, the meaning of multiple (or multiple) is more than two, greater than, less than, exceed, etc. are understood to exclude the number itself, and above, below, within, etc. are understood to include the number itself. If there is a description of "first", "second", etc., it is only used for the purpose of distinguishing technical features, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features.

[0028] In the existing IP Multimedia Subsystem (IMS) communication architecture, the Serving Call Session Control Function (S-CSCF) uses initial filtering rules (iFCs) to sequentially trigger multiple service application servers (ASs) to provide services to users. However, this mechanism has the following problems: each AS independently processes service logic and lacks cross-node service status awareness. This can lead to multiple ASs initiating media switching requests simultaneously. Unable to perceive the operating status of other ASs, resource preemption conflicts (such as simultaneous attempts to seize control of the same media stream) can easily occur, leading to session interruption. The existing mechanism relies on preset priorities (such as the Service-Interact-Info field defined in 3GPP TS24.229) to handle service conflicts, but cannot adapt to dynamic scenarios (for example, when the calling AS plays an advertisement video and the called AS plays a prompt tone simultaneously, static rules forcibly block the lower-priority service). Furthermore, after the higher-priority service completes, the lower-priority service cannot automatically continue, reducing service orchestration flexibility.

[0029] At the same time, the Session Description Protocol (SDP) used by IMS can only describe media parameters (such as encoding format and port number) and cannot clearly define the initiator of the operation and the specific intention. When the port number of the video media line is set to 0 (indicating the deletion of the media stream), the receiver cannot distinguish whether the operation is a business logic adjustment of the AS or the end user actively turning off the video function. When the user starts the data channel (DC) application and adds multiple DC media lines to the SDP proposal, the receiver needs to compare the media parameters one by one to interpret the purpose of the operation, which increases processing delay and the risk of misjudgment.

[0030] The core of the above problem lies in the lack of dynamic collaboration capabilities between application nodes based on real-time status and operational intentions. Conflicts can only be handled by relying on static rules, which leads to low system business collaboration efficiency and ineffective conflict arbitration mechanism.

[0031] In order to effectively solve the problems of insufficient service collaboration and conflict arbitration in the existing IMS system, the embodiment of the present application provides an information processing method, an application node and a computer-readable storage medium. When the method is applied to the first application node, a first media service operation request carrying service operation information corresponding to the target media service operation is sent to the second application node, so that the second application node can make a dynamic decision based on the service operation being executed (i.e., the first service operation) recorded in its local second service operation global perception table. By correlating and analyzing the received service operation information with the local real-time service status, the second application node can dynamically determine whether to forward the request to the first terminal, avoiding forced blocking or blind forwarding under the traditional static priority policy. The embodiment of the present application achieves the following technical effects through the collaborative mechanism of service operation information and the global perception table: dynamic conflict arbitration based on real-time service status to avoid forced service blocking caused by traditional static priority; clarifying the operation subject and intention through service operation information to reduce the risk of misjudgment caused by media parameter inference; dynamically adjusting the forwarding strategy of the media operation request based on the real-time service of the node recorded in the global perception table.

[0032] Based on the above analysis, the embodiments of the present application will be further described below in conjunction with the accompanying drawings.

[0033] Reference Figure 1 , Figure 1This is an IMS system architecture diagram provided by an embodiment of the present application. This IMS system architecture is centered around multimedia communication needs, building a four-layer collaborative system of terminal access, core control, service carrying, and media processing: the bottom-level UE-A serves as the user terminal, connecting to the P-CSCF (proxy call session control function) through interfaces 1 and 13. The P-CSCF is the first edge node for the UE to access the IMS, and is generally deployed at the operator's access network (such as the edge of the 5G core network). It is responsible for verifying the legitimacy of the signaling (format, authority, etc.), adding a "routing tag", and forwarding the signaling to the CSCF (call session control function) via interfaces 2 and 12. CSCF contains two types of core nodes, among which S-CSCF serves as the exclusive control anchor point of the user's home network. Each UE is bound to a unique S-CSCF after registration and connected to the SIP AS (Session Initiation Protocol Application Server) through interfaces 3, 4, 5, and 6. It assumes the responsibility of session life cycle management (establishment, maintenance, and release) and service triggering; I / S-CSCF integrates the "I-CSCF's home query" and "S-CSCF's session control" capabilities, implements cross-domain signaling routing through interface 7, and simplifies network element interaction. As a value-added service carrier, SIP AS has global perception capabilities in this application: on the one hand, it connects to CSCF to receive service triggers through interfaces 3 to 11, and on the other hand, it connects to the media plane (including media resource function processors such as MRFP), schedules media processing (such as encoding and decoding, AI processing), and coordinates dynamic conflicts among multiple services (parallel / priority control) based on global perception. The media plane integrates RTP / SRTP protocol processing, DC (Data Channel) protocol stack processing, video processing, voice processing, media resource management, media session management, AI processing, and codec conversion. It responds to SIPAS commands via dedicated connections, completing media stream transcoding, noise reduction, and splicing, ultimately supporting an end-to-end multimedia experience. For example, a typical interaction involves a UE-initiated call signaling signaled by the P-CSCF, which triggers the SIP AS to invoke media plane resources. Cross-domain scenarios utilize relay routing via the I / S-CSCF, achieving a layered, decoupled, and collaborative IMS communication process.

[0034] Reference Figure 2 , Figure 2 This is a flowchart of an information processing method provided by an embodiment of the present application. The execution subject of the method may be a first application node, and the process of the first application node executing the method includes but is not limited to step S210.

[0035] Step S210: Send a first media service operation request to the second application node, wherein the first media service operation request includes service operation information corresponding to the target media service operation, and the service operation information is used by the second application node to determine whether to forward the first media service operation request to the first terminal based on the service operation information and the first service operation, and the first service operation is a service operation being executed by the second application node recorded in the second service operation global perception table.

[0036] It should be noted that in the IP Multimedia Subsystem (IMS), the first and second application nodes can be divided into two types: the first type is the Session Initiation Protocol Application Server (SIP AS), which not only carries SIP-based application service functions but also has global status awareness capabilities, enabling real-time monitoring of the operating status of multiple network elements within the system; the second type is the Application Management Platform, which provides collaborative management of multiple business logic functions through an integrated architecture. In the IMS system, application nodes (including two or more nodes) can exchange business operation information through signaling channels, achieving collaborative linkage of global status awareness capabilities.

[0037] Exemplarily, the business operation information in the first media business operation request sent by the first application node to the second application node may include at least the following types: a business identifier, used to uniquely identify the business; a business operation priority, which clarifies the order of business execution; a business operation type, which includes at least one media operation index to accurately indicate the target media business operation content; a business operation media object, which determines the specific media resources targeted by the operation (such as video, audio, DC operation, etc.); and a business operation target user direction, which indicates the object of the target media business operation (such as the first terminal).

[0038] It should be noted that there is a mapping relationship between the business operation priority and the application node priority, which is specifically manifested as follows: when a media business operation request is initiated by a specific application node, the business operation priority parameter carried in the request can be regarded as the application priority identifier of the initiating node. For example, when the first application node generates and sends a media business operation request, the business operation priority parameter (such as high / medium / low priority value) contained in the request is not only used to identify the execution order of the business operation, but also implicitly represents the priority of the first application node in the business collaboration system. This mapping mechanism enables the downstream application node (such as the second application node) to indirectly obtain the priority information of the initiating node by parsing the business operation priority parameter after receiving the request, so that when executing conflict decisions, not only the priority of the business operation itself is considered, but also the priority of the initiating node is combined for comprehensive judgment. For example, when the second application node simultaneously receives a high-priority business request from the first application node and a low-priority business request from the third application node, it can give priority to the request of the first application node based on the priority mapping relationship, thereby realizing priority scheduling of cross-node business collaboration.

[0039] Illustratively, the media operation index included in the service operation type corresponds to a media operation content that includes at least one of the following: a media path, a service behavior, and a triggering event.

[0040] Exemplarily, the operation types of the media path include at least one of the media path change operation and the media channel management operation. The media path change operation is intended to control whether the media stream passes through the network side device, and does not change the media codec information; the media channel management operation mainly includes: adding or deleting media channels to control the media channel between the application server (i.e., application node) and the terminal, and negotiating media codecs; modifying the media channel direction focuses on changing the media transmission direction without involving codec adjustments; modifying the media channel codec mainly updates the media codec information. In actual operation, providing different types of media channels for different directions can better enhance the user experience.

[0041] Exemplarily, the business behavior operation type includes at least one of a media streaming operation and a specific function execution operation. Media streaming operations include starting and stopping the transmission of audio, video, or data streams in a specified direction; specific function execution operations include starting and stopping the execution of functions such as transcription, translation, audio playback, and video playback in a specified direction.

[0042] For example, trigger events as the starting conditions for business operations can include at least the following three categories: terminal ringing (such as the terminal ringing when a call comes in), terminal answering (the user answers the call) and active initiation by the application node (business startup triggered autonomously by the node).

[0043] Exemplarily, the media operation index included in the service operation type may include at least an audio operation index, a video operation index, and a DC operation index, etc. These indexes can be arranged in a fixed order and carried in the media service operation request and sent to the second application node so that the recipient can perform the corresponding function according to the relevant information. For example, when the media operation index includes the above three categories, it can be arranged and combined in the order of "audio operation index-video operation index-DC operation index". In terms of specific identification methods, the media operation index can be in the form of a letter combination, exemplarily in a group of 2 letters, where "aa" indicates that the service involves the media operation index and "zz" indicates that it does not involve it. In actual applications, the length of the letter combination can be extended as needed (such as "zzz"). Taking a specific scenario as an example, if the combination is "zz-zz-zz", it indicates that the media service operation does not involve audio, video and DC operations; if it is "aa-aa-aa", it indicates that the service involves the above three types of operations. This standardized index arrangement and encoding method ensures the standardization of signaling transmission and the accuracy of parsing through a unified rule system, effectively reduces ambiguity in the service interaction process, and improves system processing efficiency.

[0044] For example, in an IMS network, taking the existing Service-Interact-Info header as an example, the first application node, as an application server of different types such as a ringback tone AS and an insert AS, can clearly indicate the specific content of the media operation by carrying a header field in a specific format in UPDATE, re-INVITE, and other signaling when initiating a media service operation request:

[0045] CRBT AS scenario:

[0046] When audio media anchoring is required (the application node plays audio to side A and allows side A to send DTMF keystrokes), the header format is "Service-Interact-Info:executed-service="9000000A";15;ab-zz-zz". If video media anchoring is also added (one-way video playback to side A), the format can be adjusted to "Service-Interact-Info:executed-service="9000000A";15;ab-aa-zz". Functional expansion is achieved by marking the video operation index as "aa" (involved) instead of the original "zz" (not involved). If DC media anchoring is required alone (two-way interactive media through the DC channel), "Service-Interact-Info:executed-service="9000000A";15;zz-zz-ab" is used to activate only the DC operation index (marked as "ab").

[0047] Insert AS scenario:

[0048] When initiating a cross-end media operation (playing audio simultaneously to both sides A and B, allowing DTMF interaction between them, and playing one-way video to one side), the header format can be expressed as "Service-Interact-Info:executed-service="9000000A";10;an-ai-zz", where "an" and "ai" correspond to bidirectional audio playback and keystroke reception, respectively, and "zz" indicates that DC operation is not involved. This coding combination precisely defines the transmission direction and functional permissions of the cross-end media stream.

[0049] This type of signaling interaction uses standardized header formats and encoding rules to enable the recipient (such as the second application node) to quickly parse the service operation type (audio / video / DC media anchor), transmission direction (one-way / two-way) and interaction permissions (DTMF key presses, media sending), ensuring the consistency of collaborative operations of multiple application servers in an IMS session.

[0050] It should be noted that the media operation index supports a variety of letter combination encoding forms, and is not limited to the examples above. As shown in Table 1 (the "application node" in Table 1 is referred to as "application"), different letter combinations correspond to specific media operation content, forming a standardized mapping relationship: for example, "aa", "ab", "an" and other codes can respectively indicate different subtypes in audio operations (such as one-way playback, two-way interaction), and "zz" and others are used to mark media operations that are not involved or of a specific type. This multi-combination encoding design enables the media operation index to flexibly define various types of operation semantics (such as media transmission direction, etc.), which is compatible with basic scenarios and reserves space for complex business expansion. By matching letter combinations with specific operation content one by one, the system can parse signaling based on unified rules to ensure that multiple application nodes accurately perform differentiated operations in media collaboration, effectively improving business adaptability and cross-network element interaction efficiency.

[0051] Table 1 Media operations corresponding to media operation indexes

[0052]

[0053]

[0054] It should be noted that in the IMS network architecture, application nodes can implement the transmission of service operation information by means of SIP protocol methods such as re-INVITE, UPDATE, and INFO (including but not limited to the above types).

[0055] Exemplarily, the first business operation global awareness table maintained locally by the first application node can be used to record business operations being executed in the IMS session path. These business operations being executed may include at least one of the following: business operations that have entered the execution process of the first application node; business operations recorded in the first business operation global awareness table, which are executed by other application nodes and synchronized to the first application node through business awareness interaction.

[0056] For example, before sending a first media service operation request carrying service operation information corresponding to a target media service operation to a second application node, the first application node may first check a local service operation global awareness table and may send the request if any of the following conditions are met:

[0057] (1) There is no record of the business operation being executed in the global awareness table of the first business operation. In other words, there is no execution record in the global awareness table of the first business operation (i.e., the local is in an idle state), indicating that there is no possibility of business conflict, and the request can be sent directly without additional judgment.

[0058] (2) There is a record of an ongoing business operation in the first business operation global perception table, and the media object of the ongoing business operation is the same as the media object of the target media business operation, but the priority of the ongoing business operation is lower than the priority of the target media business operation. In other words, if there is an ongoing operation locally and the media object is consistent with the target media business operation (for example, the local operation is editing video C, and the target media business operation is also for video C), the priority needs to be compared: if the priority of the local operation is lower than the target media business operation (for example, the requester is a high-priority application node), then the request is sent.

[0059] (3) There is a record of an ongoing business operation in the global perception table for the first business operation, but the media object of the ongoing business operation is different from the media object of the target media business operation. In other words, if the media object of the local operation is unrelated to the media object of the target media business operation (for example, the local operation is for audio D, and the target media business operation is for video E), then no conflict will occur regardless of their priority, and the request can be sent directly.

[0060] Exemplarily, the business operation information carried by the media business operation request may include parameters such as business operation priority, business operation type, business operation media object, and business operation target user direction. When the business operation target user direction parameter points to the first terminal, that is, by parsing the business operation information, it can be determined that the target media business operation is the first terminal. In the process of determining whether to forward the first media business operation request to the first terminal based on the received business operation information and the business operation being executed (i.e., the first business operation) recorded in the local second business operation global perception table, the second application node can first analyze the position of this application node in this session path based on the received business operation information and the operation information in the business operation response. Specifically, the second application node determines whether it is the last application node in the session path by parsing the routing information (such as the Via header field, the Record-Route header field) in the request / response message and the target user direction in the business operation information, combined with the information recorded in the local global perception table. Based on the analysis results, the second application node performs the following operation logic: If the analysis determines that this is the last application node in the non-session path of this application node, the second application node can combine the business operation information and the local business operation global perception table (i.e., the second business operation global perception table) to decide whether to forward the request: If the local business logic allows forwarding and there is no priority conflict, the request will be forwarded to the next application node, so that the next application node can recursively execute the same forwarding decision process based on its own global perception table and the received business operation information until the request reaches the first terminal or is terminated due to a business conflict; if the local business logic prohibits forwarding or there is a priority conflict (such as the currently executed first business operation has a higher priority), a response message carrying the reason for failure is returned to the first application node. The response must include information about the local business operation being executed (such as business identification, operation type, etc.) so that the first application node can perceive the conflict. If the analysis determines that this application node is the last application node in the session path, the second application node can further execute the following logic based on the business operation information and the local second business operation global perception table: If the business operation information does not conflict with the business operation being executed locally, the request is forwarded to the first terminal and a successful response is returned; if there is a conflict or it does not comply with the policy (such as insufficient resources, priority conflict), a response message carrying the reason for the failure is returned to the first application node. The response must include the business operation information being executed locally so that the first application node can handle the conflict. If the second application node cannot clearly determine its own position through existing information, it can directly perform the forwarding operation and record the business perception capability of the forward application node so that subsequent nodes can backtrack.

[0061] Exemplarily, when the first application node receives a response message carrying a failure reason from the second application node, the first application node can perform the following operations based on the failure information carried in the response result (including the business operation information being locally executed by the second application node): stop sending the first media business operation request, and update the first business operation global perception table according to the failure reason, thereby achieving information perception collaboration with the second application node.

[0062] Exemplarily, after the first application node sends a request carrying business operation information corresponding to the target media business operation to the second application node, it can receive a first operation response result from the second application node. After the first terminal receives the first media business operation request and completes the target media business operation, the response result is fed back to the second application node, and then forwarded to the first application node by the second application node. When the first application node receives the response result and it indicates that the first terminal has successfully received and completed the target operation, the first application node can update the local first business operation global perception table according to the business operation information. Specifically, key information such as the business identifier, operation priority, media object, etc. corresponding to the target media business operation is recorded in the perception table. Through the updated first business operation global perception table, the first application node can, in the subsequent information processing process, realize information coordination and conflict avoidance of business operations with other application nodes based on the perception table status.

[0063] For example, after the first application node updates the local first service operation global awareness table based on the service operation information, the first application node may send a first media service termination operation request to the second application node. The request carries termination operation information corresponding to the media service termination operation, which is used by the second application node to determine whether to forward the first media service termination operation request to the first terminal in conjunction with the ongoing service operation (i.e., the first service operation) recorded in the local second service operation global awareness table.

[0064] For example, after the first application node sends a first media service termination operation request to the second application node, it may receive a first termination operation response result forwarded by the second application node. After receiving the first media service termination operation request and completing the media service termination operation, the first terminal feeds back the response result to the second application node, which then forwards it to the first application node.

[0065] For example, after receiving the first end operation response and confirming that the response indicates that the first terminal has successfully received and completed the media service end operation, the first application node may update the local first service operation global perception table based on the end service operation information. Specifically, key information corresponding to the target media service operation, such as the service identifier, operation priority, and media object, is cleared from the perception table. Using the updated first service operation global perception table, the first application node can collaborate with other application nodes on information and avoid conflicts during subsequent information processing based on the state of the perception table.

[0066] It should be noted that before forwarding the first end-operation response to the first application node, the second application node can simultaneously update its local global perception table for the second service operation based on the end-of-service operation information. Specifically, this operation involves clearing the service operation information corresponding to the target media service operation from the perception table. This operation ensures the consistency of the perception table state across multiple nodes, providing an accurate basis for conflict verification for subsequent service interactions.

[0067] For example, in a scenario where the target media service operation is associated with the first terminal and the second terminal at the same time, if there is a direct communication link between the first application node and the second terminal, the first application node may send a second media service operation request for the target media service operation to the second terminal separately before updating the first service operation global perception table according to the service operation information (this request does not carry service operation information). After the second terminal receives and completes the target media service operation, it returns the second operation response result to the first application node through the direct link. Similarly, before updating the first service operation global perception table according to the end service operation information, the first application node may send a second media service end operation request for the media service end operation to the second terminal. After the second terminal completes the end operation, it feeds back the second end operation response result to the first application node through the direct link.

[0068] Reference Figure 3 , Figure 3 This is a flowchart of an information processing method provided by another embodiment of the present application. The execution subject of the method may be a second application node, and the process of the second application node executing the method includes but is not limited to steps S310 to S330.

[0069] Step S310: receiving a first media service operation request sent by a first application node, wherein the first media service operation request includes service operation information corresponding to a target media service operation;

[0070] Step S320: determining whether to forward the first media service operation request to the first terminal based on the service operation information and the first service operation, wherein the first service operation is a service operation being executed by the second application node and recorded in the second service operation global awareness table;

[0071] Step S330: if it is determined to forward the first media service operation request to the first terminal, forward the first media service operation request to the first terminal.

[0072] Exemplarily, the business operation information received by the second application node is consistent with the content described above. The specific elements covered, such as business operation priority, type, media object and target user direction, can be referred to the detailed description of the business operation information above and will not be repeated here.

[0073] Exemplarily, the second business operation global awareness table maintained locally by the second application node can be used to record business operations being executed in the IMS session path. These business operations being executed include at least one of the following: business operations that have entered the execution process of the second application node; business operations recorded in the second business operation global awareness table, which are executed by other application nodes and synchronized to the second application node through business awareness interaction.

[0074] For example, before forwarding the first media service operation request to the first terminal, the second application node may first check the local service operation global awareness table (i.e., the second service operation global awareness table) to achieve dynamic coordination of multi-service operations of the node. When the table meets one of the following conditions, the first media service operation request may be forwarded to the first terminal:

[0075] (1) There is no record of the business operation being executed in the second business operation global awareness table. In other words, there is no execution record in the second business operation global awareness table (i.e., the local terminal is in an idle state), indicating that there is no possibility of business conflict. The request can be forwarded directly to the first terminal without additional judgment.

[0076] (2) There is a record of an ongoing business operation in the second business operation global perception table, and the media object of the ongoing business operation is the same as the media object of the target media business operation, but the priority of the ongoing business operation is lower than the priority of the target media business operation. In other words, if there is an ongoing operation locally and the media object is consistent with the target media business operation (for example, the business operation being executed locally is for video C, and the target media business operation is also for video C), the priorities need to be compared at this time: if the priority of the business operation being executed locally is lower than the target media business operation (for example, the requester is a high-priority application node, and the requester in this case is the first application node), the request is forwarded to the first terminal.

[0077] (3) There is a record of an ongoing service operation in the global perception table for the second service operation, but the media object of the ongoing service operation is different from the media object of the target media service operation. In other words, if the media object of the local operation is unrelated to the media object of the target media service operation (e.g., the local service operation is for audio D, and the target media service operation is for video E), then no conflict will arise regardless of their priorities, and the request can be forwarded directly to the first terminal.

[0078] For example, after the second application node forwards the media service operation request to the first terminal, it may receive a first operation response result from the first terminal. This response result is fed back to the second application node by the first terminal after receiving the first media service operation request and completing the target media service operation. After receiving the first operation response result returned by the first terminal, the second application node may forward the result to the first application node, so that the first application node can update its first service operation global perception table based on the indication of the response result, thereby achieving synchronous maintenance of service status among multiple nodes.

[0079] For example, before forwarding the first operation response result to the first application node, the second application node may update its local second business operation global awareness table based on the business operation information. Specifically, the awareness table records key information corresponding to the target media business operation, such as the business identifier, operation priority, and media object. Using this updated second business operation global awareness table, the second application node can coordinate business operation information and avoid conflicts with other application nodes based on the state of the awareness table during subsequent information processing.

[0080] For example, after the second application node sends the first operation response result to the first application node, if the first application node confirms based on the result that the first terminal has received and completed the target media service operation, the first application node may send a first media service end operation request to the second application node, and the request carries the end service operation information corresponding to the media service end operation. Specifically, after the second application node feeds back the first operation response result, it will execute the following Figure 4 The processing flow shown includes but is not limited to steps S410 to S430.

[0081] Step S410: receiving a first media service end operation request sent by a first application node, wherein the first media service end operation request includes end service operation information corresponding to the media service end operation;

[0082] Step S420: Determine whether to forward the first media service end operation request to the first terminal based on the end service operation information and the first service operation; if it is determined that the first media service end operation request is to be forwarded to the first terminal, forward the first media service end operation request to the first terminal;

[0083] Step S430: Receive the first end operation response result sent by the first terminal, and send the first end operation response result to the first application node. The first end operation response result is sent by the first terminal after receiving the first media service end operation request and completing the media service end operation.

[0084] For example, after receiving the first media service termination operation request, the second application node can make a decision based on the termination service operation information and the service operation being executed (i.e., the first service operation) in the second service operation global perception table. When it is determined that the forwarding conditions are met, the first media service termination operation request is forwarded to the first terminal to achieve closed-loop control of the service process.

[0085] For example, when the second application node forwards the first media service end operation request to the first terminal and receives the first end operation response result fed back by the first terminal based on the request, the response result can be forwarded to the first application node so that the first application node updates its first service operation global perception table according to the indication of the end operation response result, thereby realizing synchronous maintenance of service operation status among multiple nodes.

[0086] Illustratively, before forwarding the first end operation response result to the first application node, the second application node may simultaneously clear the service operation information corresponding to the target media service operation in the perception table according to the end service operation information.

[0087] It should be noted that this application does not limit the number of application nodes participating in service collaboration. In addition to the first and second application nodes mentioned above, other application nodes can be expanded and connected based on service needs. Each newly added node must locally maintain a global service operation awareness table to record the service operations being executed in the IMS session path, thereby enabling awareness and collaborative interaction between multiple nodes based on this awareness table.

[0088] For example, in a scenario where an IMS session path includes a first application node, a second application node, and a third application node, and a communication link is formed between the nodes, the second application node may simultaneously receive two types of requests: a first media service operation request sent by the first application node carrying first service operation information corresponding to a first target media service operation; and a second third media service operation request sent by the third application node carrying third service operation information corresponding to a third target media service operation. In this case, the second application node can perform the same processing flow for both types of requests based on the first service operation information, the third service operation information, and a locally maintained second service operation global awareness table: first, determining its own logical position in the session path. If it is not the end node of the session path, it checks for service conflicts based on the local service operation global awareness table and then decides whether to forward the operation request to the next application node or return a failure response carrying information about the locally executed service operation. If it is the end node of the session path, it either directly forwards the operation request to the target terminal (i.e., the target object of the operation request) or rejects the operation request and carries information about the locally executed service operation in the failure response.

[0089] For example, in the information interaction scenario between the application node and the terminal device (such as a smart phone, IP phone, etc.), the request initiated by the terminal may not carry business operation information (such as business identification, priority, type and other parameters). The application node can quickly identify the terminal source of the request through this feature and implement a differentiated processing strategy. Take cross-terminal business interaction as an example: when the first terminal sends a media operation request directed to the second terminal to the first application node, if the first application node analyzes and finds that the request does not contain business operation information, it can be determined to be a request initiated by the terminal. At this time, the first application node gives priority to the request and stops the conflicting business based on the local business operation global perception table. If it needs to be forwarded to the second application node, the request will remain in a state without business operation information. After receiving the request, the second application node identifies it as a request initiated by the terminal through the same feature, and also gives priority to and stops the local conflicting business, and finally forwards the request to the second terminal for execution. This mechanism uses the request parameter feature to clearly distinguish between terminal and application node operations, which can ensure that the business initiated by the terminal is given priority processing.

[0090] Exemplarily, when the target media service operations of multiple application nodes are all directed to the first terminal (i.e., multiple application nodes perform media operations on it at the same time), conflict resolution can be performed based on the application node priority. For example, assuming that in an IMS session path scenario, the first application node (high priority), the second application node (medium priority), the third application node (low priority) and the first terminal are connected in sequence through communication links. When the first application node and the third application node simultaneously initiate media service operations on the second terminal, the priority-based conflict resolution process is as follows: First, the third application node (low priority) and the first application node (high priority) each check their local service operation global perception table to confirm that the current state meets the conditions for initiating media service operations, such as there are no conflicting services being executed; then, the third application node first sends a third media service operation request to the first terminal without carrying its own service operation information, which is only used for initial connection verification to establish the communication link. The first terminal returns a success result without carrying service operation information to confirm that the link is unobstructed and has the basic conditions for receiving the operation. Next, the third application node and the first application node each send a request to the second application node (intermediate node) carrying the business operation information corresponding to their respective target media business operations. Specifically, the third application node sends a third media business operation request containing the business operation information corresponding to the third target media business operation, and the first application node sends a first media business operation request containing the business operation information corresponding to the first target media business operation. The business operation information of both clearly points to the first terminal as the operation object. When the second application node receives both requests simultaneously, it queries the local business operation global perception table to determine whether there is a conflict between the target media business operation and the currently executing business recorded in the table (such as mutually exclusive business operation types). If it is confirmed that there is no conflict and the business operation forwarding conditions are met, the following forwarding strategy is executed: forward the third media business operation request of the third application node (carrying the business operation information of the third application node) to the first application node, and simultaneously forward the first media business operation request of the first application node (carrying the business operation information of the first application node) to the third application node, so that both parties can obtain each other's operation intentions and priority information. After receiving the first media service operation request from the first application node, the third application node compares the operation object in the request and finds that it is consistent with its own operation object (both are the first terminal), and detects that the priority of the initiator's first application node is higher than that of this node. It immediately stops the current media service operation of this node and returns a successful result with the information that this node has ended the service operation to the second application node (this result only indicates that the message has been received and the actual operation has been actively terminated). Subsequently, the second application node updates the local service operation global perception table, deletes the service operation record of the third application node, and records the service operation information of the first application node; then returns a successful result with the information that the third application node has ended the service operation to the first application node.After receiving the feedback, the first application node synchronously updates the local perception table to confirm that its own operation is effective, and then returns the business operation failure result of the third application node carrying the information that the node ends the business operation to the second application node, clearly stating that the low-priority operation is rejected. The second application node forwards the failure result to the third application node to complete the status synchronization of the entire link.

[0091] Exemplarily, when the target media service operations of multiple application nodes are all directed to the second terminal (i.e., multiple application nodes perform media operations on it at the same time), conflict resolution can be performed based on the application node priority. For example, assuming that in an IMS session path scenario, the first application node (high priority), the second application node (medium priority), and the third application node (low priority) are connected to the second terminal in sequence through communication links. When the first application node and the third application node initiate media service operations on the second terminal at the same time, the priority-based conflict resolution process is as follows: First, the third application node and the first application node each check the local service operation global perception table to confirm that the current state meets the conditions for initiating media service operations, such as there is no conflicting service being executed; then, the third application node first sends a third media service operation request to the second terminal that does not carry its own service operation information, which is only used to establish a communication connection. The second terminal returns a successful result that does not carry service operation information to confirm that the link is unobstructed. Then, the third application node and the first application node each send a request to the second application node, each carrying the business operation information corresponding to their respective target media business operations. That is, the third application node sends a third media business operation request containing the business operation information corresponding to the third target media business operation, and the first application node sends a first media business operation request containing the business operation information corresponding to the first target media business operation. The business operation information of both requests indicates that the target media business operations are both directed to the second terminal. When the second application node receives both requests simultaneously, it queries the local business operation global perception table to determine whether there is a conflict between the target media business operation and the currently executing business recorded in the table. If it is confirmed that there is no conflict and the business operation forwarding conditions are met, it forwards the third media business operation request of the third application node (carrying the business operation information of the third application node) to the first application node, and simultaneously forwards the first media business operation request of the first application node (carrying the business operation information of the first application node) to the third application node, so that both parties can understand each other's operation intentions. After receiving the first media service operation request from the first application node, the third application node compares the operation object in the request and finds that it is consistent with its own operation object. It also detects that the first application node has a higher priority than this node. It immediately stops its current operation and returns a successful result to the second application node, including information about the end of the service operation. This result only indicates that the message has been received and the actual operation has been terminated. The state synchronization and result feedback phase then begins. Specifically, the second application node first updates the local service operation global perception table, deletes the service operation information of the third application node, and records the service operation information of the first application node. It then returns a successful result to the first application node, including information about the end of the service operation of the third application node.After receiving the feedback, the first application node synchronously updates the local perception table to confirm that its own operation is effective, and then returns the business operation failure result of the third application node carrying the information that the node ends the business operation to the second application node, clearly stating that the low-priority operation is rejected. The second application node forwards the failure result to the third application node to complete the status synchronization of the entire link.

[0092] For example, assuming that in an IMS session path scenario, the first terminal, the first application node, and the second terminal are connected through a communication link, when the first application node performs media service operations on the first terminal and the second terminal respectively, the collaborative process of the first application node and the two terminals is as follows: Assuming that the first application node has created a one-way video channel to the first terminal and the first terminal is playing a one-way video, the second terminal initiates an audio-to-video switching operation. The specific process is as follows: First, the second terminal sends an audio-to-video switching request (such as a re-INVITE request) to the first application node (or relayed through an intermediate application node). The request does not carry service operation information and is identified as an operation initiated by the terminal. After receiving the request, the first application node analyzes and finds that the request comes from the terminal and does not contain service operation information. It responds to the terminal's needs first and suspends the current one-way video service operation output to the first terminal (or prepares to adjust the media channel). Then, the first application node forwards the switching request to the first terminal, requesting that the one-way video channel be adjusted to a mode that supports two-way video. The request also does not carry service operation information to indicate that the operation is triggered by the terminal. After receiving the request, the first terminal performs a media channel reconfiguration operation, switching from one-way video playback to two-way video communication mode. After the operation is complete, the first terminal returns a confirmation response to the first application node, confirming the successful two-way video switch. The response does not include service collaboration parameters. Upon receiving the confirmation response from the first terminal, the first application node immediately updates the local service operation global awareness table, clears the original one-way video service operation record, and marks the current two-way video state as valid. Subsequently, the first application node returns a confirmation response to the second terminal, informing it that the video switch request has been completed and the first terminal has entered two-way video mode. After receiving the response, the second terminal sends a confirmation message to the first application node, completing the closed-loop confirmation of the signaling link. Simultaneously, the first application node establishes the media channel required for two-way video with the second terminal, ensuring that the second terminal's video stream can be transmitted to the first terminal. Throughout the collaborative process, the first application node, acting as the scheduling core for the media service, dynamically adjusts the media connection status with both terminals based on the terminal-initiated requests, prioritizes terminal operation requests through signaling exchanges, and ensures synchronization of all node states by updating the global awareness table, ultimately enabling a two-way video call between the first and second terminals.

[0093] For example, assuming that in an IMS session path scenario, the first terminal, the first application node (low priority), the second application node (high priority) and the second terminal are connected in sequence through communication links, and the first application node and the second application node have completed global service awareness through their respective service operation global awareness tables before initiating media service operations. During the process of the second application node (low priority) performing media service operations on the first terminal, when the first application node (high priority) initiates a media service operation request to the second terminal, the collaborative processing between the application nodes is as follows: First, the first application node checks the local service operation global awareness table to confirm that the second application node's current one-way video operation to the first terminal does not conflict with the service operation it is currently performing (such as the operation objects are different). After the initiation conditions are met, the first application node can initiate a media service operation request including the service operation information corresponding to the target media service operation to the second application node through a re-INVITE request. Specifically, the specific service operation information (for example, "play a one-way video to the second terminal") can be carried in the Service-Interact-Info header to clarify the media operation content and the target terminal. After receiving the request, the second application node parses the business operation information in the Service-Interact-Info header, and simultaneously checks the local business operation global perception table. It determines that the one-way video playback operation of the first application node (high priority) is for the second terminal, and there is no object conflict with its own operation for the first terminal. It then executes the forwarding strategy of the low-priority node for the high-priority request. Specifically: forwards the re-INVITE request to the second terminal (without carrying business operation information to identify terminal behavior). After the second terminal returns a confirmation response result, the second application node updates the local business operation global perception table, records the one-way video playback information from the first application node to the second terminal, and returns a confirmation response to the first application node. After receiving the confirmation response, the first application node updates the local business operation global perception table, records the one-way video playback information from the first application node to the second terminal, and sends a confirmation message to the second application node. Subsequently, the second application node sends a confirmation message to the second terminal. When the second application node subsequently completes video playback for the first terminal and notifies the first application node via a re-INVITE request carrying business operation information that the video media playback is complete, the first application node analyzes the information and confirms that the video channel of the first terminal needs to be closed. It sends a close request to the first terminal and obtains a response. It then simultaneously updates the local business operation global perception table, deletes the information about the second application node playing the video for the first terminal, and returns a confirmation response to the second application node. Subsequently, the second application node updates the local business operation global perception table, deletes the information about the second application playing the video for the first terminal, and sends a confirmation to the first application node. Finally, the first application node continues to independently perform the video playback operation for the second terminal.During the entire collaborative process, the low-priority second application node gives way to the high-priority first application node's request by parsing business operation information and checking the global perception table. The two parties realize the transmission of operation intentions and status synchronization through signaling interactions carrying specific headers, ensuring that application nodes of different priorities execute media business operations on different terminals in an orderly manner.

[0094] The information processing method of the present application is described below with reference to some specific embodiments.

[0095] Example 1:

[0096] like Figure 5 As shown, in an IMS session communication scenario including a first terminal, a second terminal, a first application node (illustrated as a first application), a second application node (illustrated as a second application), and a third application node (illustrated as a third application), communication links have been established between each node and the terminal. When the first application node initiates a target media service operation (the service operation requests association between the first terminal and the second terminal), the method for achieving inter-application service collaboration includes the following steps:

[0097] Step 501: The first application node checks the local service operation global awareness table to determine that the current state meets the conditions for initiating a media service operation.

[0098] Step 502: The first application node sends a service operation request to the second application node, wherein the request carries service operation information corresponding to the target media service operation of the first application node (including service identifier, service operation priority, service operation type, service operation media object and service operation target user direction).

[0099] Step 503: The second application node checks the local service operation global awareness table to determine that the target media service operation does not conflict with the currently executed service operation recorded in the table, satisfies the service operation forwarding conditions, and the application node is not the end node of the session path.

[0100] Step 504: The second application node forwards the service operation request to the third application node, wherein the service operation request carries the service operation information of the first application node.

[0101] Step 505: The third application node checks the local service operation global awareness table, determines that the target media service operation has no conflict with the currently executed service operation recorded in the table, satisfies the service operation forwarding condition, and is the last node.

[0102] Step 506: The third application node forwards the service operation request to the second terminal, wherein the request does not carry the service operation information of the first application node.

[0103] Step 507: The second terminal returns a service operation success result to the third application node, wherein the result does not carry the service operation information of the first application node.

[0104] Step 508: The third application node updates the local service operation global awareness table to record the service operation information of the first application node.

[0105] Step 509: The third application node forwards the service operation success result to the second application node, wherein the result does not carry the service operation information of the first application node.

[0106] Step 510: The second application node updates the local service operation global awareness table to record the service operation information of the first application node in the operation request.

[0107] Step 511: The second application node forwards the successful service operation result to the first application node, wherein the result does not carry the service operation information of the first application node.

[0108] Step 512: The first application node initiates a service operation request to the first terminal. The request does not carry service operation information.

[0109] Step 513: The first terminal returns an operation response result to the first application node, where the result is a successful service operation result.

[0110] Step 514: The first application node updates the local service operation global awareness table to record the service operation information of the first application node in the operation request.

[0111] Step 515: After completing the target media service operation, the first application node initiates a service end operation request to the second application node. The request carries end service operation information corresponding to the media service end operation.

[0112] Step 516: The second application node updates the local business operation global perception table based on the business termination operation information and clears the business operation information of the first application node; by checking the local business operation global perception table, it is determined that the media business termination operation does not conflict with the business operation being executed recorded in the table, the business termination operation forwarding conditions are met, and this application node is not the last node.

[0113] Step 517: The second application node forwards the service termination operation request to the third application node, wherein the request carries termination operation information corresponding to the media service termination operation;

[0114] Step 518: The third application node updates the local business operation global perception table based on the end business operation information and clears the business operation information of the first application node; by checking the local business operation global perception table, it is determined that the media business end operation has no conflict with the business operation being executed recorded in the table, the business end operation forwarding conditions are met and this application node is the last node.

[0115] Step 519: The third application node forwards the service termination operation request to the second terminal, wherein the request does not carry the service termination operation information of the first application node.

[0116] Step 520: The second terminal returns an end-of-operation response result to the third application node.

[0117] Step 521: The third application node forwards the end operation response result to the second application node.

[0118] Step 522: The second application node forwards the end operation response result to the first application node.

[0119] Step 523: The first application node initiates a service termination operation request to the first terminal.

[0120] Step 524: The first terminal returns an end-of-operation response result to the first application node.

[0121] Step 525: The first application node updates the local service operation global awareness table according to the service operation termination information, and clears the service operation information of the first application node.

[0122] Example 2:

[0123] like Figure 6 As shown, in an IMS session path scenario including a first terminal, a first application node (illustrated as the first application), a second application node (illustrated as the second application), a third application node (illustrated as the third application) and a second terminal, and a communication link has been established between each node and the terminal, the third application node initiates a service operation first, and then the first application node initiates a service operation, and the target user direction in the service operation information of both points to the second terminal. The application node priorities are in descending order: the first application node, the second application node, and the third application node. It should be noted that when a high-priority application node is executing a service operation, the low-priority application node can actively suppress the initiation of new service operations after obtaining the execution status of the high-priority service through the local service operation perception table, so as to avoid the occurrence of multi-node service conflicts. The method for realizing service collaboration between the above-mentioned application nodes includes the following steps:

[0124] Step 601: The third application node checks the local service operation global awareness table to determine whether the current state meets the service operation initiation condition.

[0125] Step 602: The third application node sends a first service operation request to the second terminal. The request does not carry service operation information of the third application node.

[0126] Step 603: The second terminal returns a service operation success result to the third application node, without carrying the service operation information of the third application node.

[0127] Step 604: The third application node sends a first service operation request to the second application node. The request carries service operation information corresponding to the target media service operation of the third application node.

[0128] Step 605: The second application node checks the local service operation global awareness table to determine whether the target media service operation has no conflict with the currently executed service operation recorded in the table, satisfies the service operation forwarding condition, and the application node is not the last node.

[0129] Step 606: The second application node forwards the first service operation request to the first application node. The request carries service operation information of the third application node.

[0130] Step 607: The first application node checks the local service operation global awareness table, determines that the target media service operation does not conflict with the currently executed service operation recorded in the table, satisfies the service operation forwarding condition, and is the last node.

[0131] Step 608: The first application node forwards the first service operation request to the first terminal. The request does not carry the service operation information of the third application node.

[0132] Step 609: The first terminal returns a service operation success result to the first application node. The result does not carry service operation information of the third application node.

[0133] Step 610: The first application node updates the local business operation global awareness table to record the business operation information of the third application node.

[0134] Step 611: The first application node forwards a successful service operation result to the second application node. The result does not carry service operation information of the third application node.

[0135] Step 612: The second application node updates the local service operation global awareness table to record the service operation information of the third application node.

[0136] Step 613: The second application node forwards the service operation success result to the third application node. The result does not carry the service operation information of the third application node.

[0137] Step 614: The third application node updates the local business operation global awareness table to record the business operation information of the third application node.

[0138] Step 615: The first application node checks the local service operation global awareness table and determines that the priority of the application node is higher than that of the third application node, and the service operation initiation condition is met.

[0139] Step 616: The first application node sends a second service operation request to the second application node. The request carries service operation information corresponding to the target media service operation of the first application node.

[0140] Step 617: The second application node checks the local service operation global awareness table to determine whether the target media service operation has no conflict with the currently executed service operation recorded in the table, satisfies the service operation forwarding condition, and the application node is not the last node.

[0141] Step 618: The second application node sends a second service operation request to the third application node, carrying the service operation information of the first application node.

[0142] Step 619: The third application node checks the global awareness table of local business operations. If there is a conflict with the current application node, the third application node stops the business operation of the current application node and records the business operation information of the first application node.

[0143] Step 620: The third application node returns a successful service operation result to the second application node, carrying information indicating that the third application node has completed the service operation.

[0144] Step 621: The second application node updates the local business operation global awareness table, records the business operation information of the first application node, and clears the business operation information of the third application node.

[0145] Step 622: The second application node returns a successful service operation result to the first application node, carrying the service operation termination information of the third application node.

[0146] Step 623: The first application node updates the local business operation global awareness table, records the business operation information of the first application node, and clears the business operation information of the third application node.

[0147] Step 624: The first application node sends a second service operation request to the first terminal, which does not carry the service operation information of the first application node.

[0148] Step 625: The first terminal returns a successful service operation result to the first application node.

[0149] At this point, the business conflicts between application nodes are resolved.

[0150] Example 3:

[0151] like Figure 7 As shown, in an IMS session path scenario including a first terminal, a first application node (illustrated as a first application), a second application node (illustrated as a second application), a third application node (illustrated as a third application) and a second terminal, and a communication link has been established between each node and the terminal, the third application node and the first application node simultaneously initiate a service operation for the second terminal. The application node priorities are from high to low: first application node, second application node, and third application node. In this embodiment, the method for a high-priority application node to reject a low-priority application node includes the following steps:

[0152] Step 701: The third application node checks the local service operation global awareness table to determine whether the current state meets the service operation initiation condition.

[0153] Step 702: The first application node checks the local service operation global awareness table to determine whether the current state satisfies the service operation initiation condition.

[0154] Step 703: The third application node sends a first service operation request for a target media service operation to the second terminal. The request does not carry service operation information of the third application node.

[0155] Step 704: The second terminal returns a service operation success result to the third application node. The result does not carry service operation information.

[0156] Step 705: The third application node sends a first service operation request to the second application node. The request carries service operation information corresponding to the target media service operation of the third application node.

[0157] Step 706: The first application node sends a second service operation request to the second application node. The request carries service operation information corresponding to the target media service operation of the first application node.

[0158] Step 707: The second application node receives two service operation requests simultaneously, checks the local service operation global awareness table, and determines that the target media service operation has no conflict with the service operation being executed recorded in the table, and satisfies the service operation forwarding condition.

[0159] Step 708: The second application node forwards the first service operation request to the first application node, where the request carries service operation information of the third application node.

[0160] Step 709: The second application node forwards the second service operation request to the third application node. The request carries the service operation information of the first application node.

[0161] Step 710: The third application node determines that the operation object in the received business operation request is the same as that of the current application node, and the priority of the first application node is higher than that of the current application node, and stops the operation of the current application node.

[0162] Step 711: the third application node returns a successful service operation result corresponding to the second service operation request to the third application node, and the result carries information about the end of the service operation of the third application node.

[0163] Step 712: The second application node updates the local service operation global awareness table to record the service operation information of the first application node.

[0164] Step 713: The second application node returns a successful service operation result corresponding to the second service operation request to the first application node. The result carries the service operation termination information of the third application node.

[0165] Step 714: The first application node updates the local service operation global awareness table to record the service operation information of the first application node.

[0166] Step 715: The first application node returns a service operation failure result of the third application node to the second application node, carrying service operation termination information of the first application node.

[0167] Step 716: The second application node forwards the service operation failure result to the third application node, carrying the service operation termination information of the first application node.

[0168] Step 717: The first application node sends a service operation request to the first terminal. The request does not carry service operation information.

[0169] Step 718: The first terminal returns a successful service operation result to the first application node. This structure does not carry service operation information. At this point, the service conflict is handled.

[0170] Example 4:

[0171] like Figure 8 As shown, in this embodiment, the collaborative conflict handling mechanism of multiple application nodes is explained based on the SIP protocol, mainly in the scenario where a high-priority application node rejects a low-priority application node: when a second application node (shown as the second application) is playing a video stream to a first terminal via SIP signaling, a lower-priority first application node (shown as the first application) also initiates a video playback request to the same terminal. At this time, because the first application node has not obtained the execution status of the second application node through the service perception table (in an abnormal unaware scenario), the following processing logic will be executed:

[0172] It should be noted that, in order to highlight the core process, this embodiment omits the signaling forwarding details of logical network elements such as P-CSCF and I / S-CSCF. The standard interaction of the above network elements does not affect the priority-based conflict handling logic between multiple application nodes.

[0173] Step 801: The first application node sends a re-INVITE request to the second application node to initiate a service operation. The Service-Interact-Info header is used as a delivery carrier for service operation collaboration, indicating that the audio media will pass through the first media plane and the one-way video will be played to the first terminal using the first media plane. For example:

[0174] Service-Interact-Info:executed-service="9000000A"; 15; ap-ao-zz

[0175] Step 802: The second application node analyzes the service operation information in the request and determines that the one-way video playback operation of the second application node conflicts with the one-way video playback operation of the first application node. Since the second application node has a higher priority than the first application node, the one-way video is still played by the second application node to the first terminal.

[0176] Step 803: The second application node returns a 480 response to the first application node, using the Service-Interact-Info header to carry the service operation collaboration parameter, indicating that the second application node is playing a one-way video to the first terminal, for example:

[0177] Service-Interact-Info:executed-service="9000000B";10;ap-ao-zz;

[0178] Step 804: The first application node analyzes the service operation information in the response and does not perform the one-way video playback operation.

[0179] The first application node returns an ACK (Acknowledgment) confirmation to the second application node.

[0180] Step 805: Assuming the first application node is the receiver of the message and the second application node is the sender of the message, when the second application node sends a message (such as a request, instruction, or data) to the first application, if the first application successfully receives and processes the message, it will return an ACK message to the second application.

[0181] Embodiment 5:

[0182] like Figure 9As shown, in this embodiment, taking the SIP protocol as an example, a method for implementing conflict management between application nodes is described. The first application node (illustrated as the first application) is playing a video to the first terminal, and the second application node (illustrated as the second application) also needs to play a video to the first terminal. The second application node has a higher priority than the first application node. It should be noted that, in order to highlight the key points, this embodiment omits the interaction process of logical network elements such as P-CSCF and I / S-CSCF in IMS. The behavior of these logical network elements does not affect the business process. The process of this embodiment includes the following steps:

[0183] Step 901: The second application node checks the local service operation global perception table and determines that the first application node is playing a one-way video to the first terminal. However, the priority of this application node is higher than that of the first application node and the service operation can be initiated.

[0184] Step 902: The second application node sends a re-INVITE request to the second terminal, changes the media path, and does not carry service operation information.

[0185] Step 903: The second terminal returns a 200 OK response, agreeing to change the media path without carrying service operation information.

[0186] Step 904: The second application node sends an ACK completion confirmation to the second terminal.

[0187] Step 905: The second application node sends a re-INVITE request to the first application node to initiate a service operation. The Service-Interact-Info header carries a service operation type parameter, indicating that the audio media will pass through the second media plane and the one-way video will be played to the first terminal using the second media plane. For example:

[0188] Service-Interact-Info:executed-service="9000000B"; 10; ap-ao-zz

[0189] Step 906: The first application node analyzes the service operation information, determines that the one-way video playback operation of the second application node conflicts with the one-way video playback operation of the first application node, and that the second application node has a higher priority than the first application node, and decides to have the second application node play the one-way video to the first terminal.

[0190] Step 907: The first application node returns a 200 OK response to the second application node, using the Service-Interact-Info header to carry the service operation collaboration parameter, indicating that the first application node has stopped playing the one-way video to the first terminal. For example:

[0191] Service-Interact-Info:executed-service="9000000A";15;au-au-zz;

[0192] Step 908: The first application node sends an ACK confirmation to the second application node.

[0193] Step 909: The second application node analyzes the business operation information, updates the local business operation global awareness table, clears the business operation information record of the first application node, and adds the business operation information record of the second application node.

[0194] Step 910: After the second application node finishes playing the video to the first terminal, it notifies the first application node.

[0195] Step 911: The second application node sends a re-INVITE request to the first application node, carrying the service operation coordination parameter Service-Interact-Info, indicating that the second application node has no data to transmit and closes the video channel. For example: Service-Interact-Info: executed-service = "9000000B"; 10; au-av-zz.

[0196] Step 912: The first application node analyzes the service operation information in the request and determines that the second application node has stopped playing. Therefore, the first application node can continue playing the video. The first application node returns a 200OK response to the second application node, using the Service-Interact-Info header to carry the service operation collaboration parameter, indicating that the first application node is playing a one-way video to the first terminal. For example: Service-Interact-Info: executed-service = "9000000A"; 15; ap-ao-zz

[0197] Step 913: The second application node sends an ACK confirmation to the first application node.

[0198] Step 914: The first application node updates the business operation global awareness table, clears the business operation information record of the second application node, and adds the business operation information record of the first application node.

[0199] Step 915: The second application node updates the business operation global awareness table, clears the business operation information record of the second application node, and adds the business operation information record of the first application node.

[0200] At this point, the first application node starts playing the video to the first terminal.

[0201] Example 6:

[0202] like Figure 10 As shown, in this embodiment, taking the SIP protocol as an example, the service collaboration between the SIP application node and the SIP terminal is explained. The second application node (shown as the second application) creates a one-way video channel to the first terminal and is playing a one-way video. The second terminal initiates the operation of switching the audio to the video. It should be noted that in order to highlight the key points, this embodiment omits the interaction process of logical network elements such as P-CSCF and I / S-CSCF in IMS. The behavior of these logical network elements does not affect the service process. The process of this embodiment includes the following steps:

[0203] Step 1001: The second terminal sends a re-INVITE request to the second application node, requesting that the audio be switched to the video;

[0204] Step 1002: The second application node analyzes the service request and finds that it does not carry any service operation information. It determines that the operation is initiated by the terminal, processes the request according to the terminal first, and stops the service operation of the second application node.

[0205] Step 1003: The second application node forwards a re-INVITE request to the first application node (shown as the first application), requesting that the one-way video be switched to a two-way video, and does not carry service operation information, indicating a terminal behavior;

[0206] Step 1004: The first application node analyzes the service request and finds that it does not carry any service operation information. It determines that the operation is initiated by the terminal and processes the request according to the terminal first.

[0207] Step 1005: The first application node forwards a re-INVITE request to the first terminal, requesting that the one-way video be switched to a two-way video, and does not carry service operation information, indicating that it is a terminal behavior;

[0208] Step 1006: The first terminal switches the one-way video to a two-way video;

[0209] Step 1007: The first terminal returns a 200OK response to the first application node, indicating that the one-way video is successfully switched to the two-way video, and does not carry the service operation coordination parameter;

[0210] Step 1008: The first application node updates the local business operation global awareness table and clears the business operation information of the second application node;

[0211] Step 1009: The first application node returns a 200 OK response to the second application node, without carrying the service operation coordination parameters;

[0212] Step 1010: The second application node returns a 200OK response to the second terminal. The response does not carry the service operation coordination parameter, indicating that the operation of the first terminal is successful.

[0213] Step 1011: The second application node updates the local service operation global awareness table and clears the service operation information of the second application node;

[0214] Step 1012: The second terminal sends an ACK confirmation message to the second application node;

[0215] Step 1013: The second application node forwards the ACK confirmation message to the first application node;

[0216] Step 1014: The first application node forwards the ACK confirmation message to the first terminal.

[0217] At this point, the first terminal and the second terminal realize a two-way video call.

[0218] Embodiment seven:

[0219] like Figure 11 As shown, in this embodiment, taking the SIP protocol as an example, a method for implementing conflict management between application nodes is described. Before initiating a business operation, the first application node (illustrated as the first application) and the second application node (illustrated as the second application) have completed the full business perception operation and use the Service-Interact-Info header as a transmission carrier for business operation collaboration. In the process of the second application node playing a one-way video to the first terminal, the first application node creates a one-way video channel to the second terminal, and the priority of the first application node is lower than that of the second application node. The process of this embodiment includes the following steps:

[0220] It should be noted that, in order to highlight the key points, this embodiment omits the interaction process of logical network elements such as P-CSCF and I / S-CSCF in IMS. The behavior of these logical network elements does not affect the service process.

[0221] Step 1101: The first application node checks the local service operation global perception table and determines that the one-way video operation from the second application node to the first terminal does not conflict with the service operation initiated by the application node, thus satisfying the service operation initiation request;

[0222] Step 1102: The first application node sends a re-INVITE request to the second application node to initiate a service operation. The Service-Interact-Info header carries service operation information, indicating that the audio media will pass through the first media plane and a one-way video will be played to the second terminal. For example:

[0223] Service-Interact-Info:executed-service="9000000A";15;ar-aq-zz

[0224] Step 1103: The second application node checks the local service operation global awareness table, analyzes the service operation information, and determines that the one-way video playback operation of the first application node does not conflict with the one-way video playback operation of the current application node.

[0225] Step 1104: The second application node forwards the re-INVITE request to the second terminal without carrying the service operation information;

[0226] Step 1105: The second terminal returns a 200 OK response to the second application node, which does not carry service operation information;

[0227] Step 1106: The second application node updates the local service operation global awareness table to record the one-way video playback information from the first application node to the second terminal;

[0228] Step 1107: The second application node returns a 200 OK response to the first application node;

[0229] Step 1108: The first application node updates the local service operation global awareness table to record the one-way video playback information performed by the first application node to the second terminal;

[0230] Step 1109: The first application node sends an ACK confirmation to the second application node;

[0231] Step 1110: The second application node sends an ACK confirmation to the second terminal;

[0232] Step 1111: The first application node sends a re-INVITE request to the first terminal, changing the media path without carrying service operation information;

[0233] Step 1112: The first terminal returns a 200 OK response without carrying service operation information;

[0234] Step 1113: The first application node sends an ACK confirmation to the first terminal.

[0235] Step 1114: The second application node sends a re-INVITE request to the first application node, carrying service operation information, indicating that the second application node has completed playing the video media to the first terminal;

[0236] Step 1115: The first application node analyzes the service operation information and determines that the second application node has finished playing the video to the first terminal and needs to close the video channel with the first terminal.

[0237] Step 1116: The first application node sends a re-INVITE request to the first terminal, closing the video channel without carrying service operation information;

[0238] Step 1117: The first terminal returns a 200 OK response to the first application node;

[0239] Step 1118: The first application node updates the local service operation global awareness table and deletes the information about the second application node playing the video to the first terminal;

[0240] Step 1119: The first application node returns a 200 OK response to the second application node;

[0241] Step 1120: The second application node updates the local service operation global awareness table and deletes the information about the second application node playing the video to the first terminal;

[0242] Step 1121: The second application node sends an ACK confirmation to the first application node;

[0243] Step 1122: The first application node sends an ACK confirmation to the first terminal.

[0244] At this point, the first application node continues to play the video to the second terminal.

[0245] It should be noted that this embodiment provides key instructions in a basic call. There may be changes in SIP signaling in the actual process, which are all within the scope of protection of this application.

[0246] In addition, an embodiment of the present application further discloses an application node, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, an information processing method as in any of the previous embodiments is implemented.

[0247] In addition, an embodiment of the present application further discloses a computer-readable storage medium, which stores computer-executable instructions for executing the information processing method in any of the previous embodiments.

[0248] In addition, an embodiment of the present application also discloses a computer program product, including a computer program or computer instructions, which are stored in a computer-readable storage medium. The processor of the device reads the computer program or computer instructions from the computer-readable storage medium, and the processor executes the computer program or computer instructions, so that the device performs the information processing method as in any of the previous embodiments.

[0249] Those skilled in the art will appreciate that all or some of the steps and systems in the method disclosed above can be implemented as software, firmware, hardware, and appropriate combinations thereof. Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, and the computer-readable medium can include computer storage media (or non-transitory media) and communication media (or temporary media). As known to those skilled in the art, the term computer storage media is included in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data) and is volatile and non-volatile, removable, and non-removable. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory, or other memory technology, CD-ROM, digital versatile disks (DVD), or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage, or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, as is well known to those skilled in the art, communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0250] The above is a specific description of the preferred implementation of the present application, but the present application is not limited to the above implementation mode. Technical personnel familiar with the field can also make various equivalent modifications or substitutions without violating the spirit of the present application. These equivalent modifications or substitutions are all included in the scope defined by the claims of the present application.

Claims

1. An information processing method, applied to a first application node, comprising: Sending a first media service operation request to the second application node, where the first media service operation request includes service operation information corresponding to the target media service operation, The service operation information is used by the second application node to determine whether to forward the first media service operation request to the first terminal based on the service operation information and a first service operation, where the first service operation is a service operation being executed by the second application node recorded in a second service operation global perception table.

2. The information processing method according to claim 1, wherein: Before sending the first media service operation request to the second application node, the method further includes: In response to satisfying one of the following conditions, determining to perform an operation of sending the first media service operation request to the second application node: There is no record of the business operation being executed in the first business operation global awareness table of the first application node; In the first service operation global awareness table of the first application node, there is a record of a service operation being executed, and a media object of the service operation being executed is the same as a media object of the target media service operation, but a priority of the service operation being executed is lower than a priority of the target media service operation; In the first service operation global awareness table of the first application node, there is a record of a service operation being executed, but the media object of the service operation being executed is different from the media object of the target media service operation.

3. The information processing method according to claim 1, wherein: After sending the first media service operation request to the second application node, the method further includes: A first operation response result sent by the second application node is received, where the first operation response result is sent by the first terminal to the second application node after the first terminal receives the first media service operation request and completes the target media service operation.

4. The information processing method according to claim 3, wherein: After receiving the first operation response result sent by the second application node, the method further includes: A first business operation global awareness table is updated according to the business operation information, where the first business operation global awareness table is used to record the business operation being executed by the first application node.

5. The information processing method according to claim 4, characterized in that The target media service operation is associated with both the first terminal and the second terminal. Before updating the first service operation global awareness table according to the service operation information, the method further includes: Sending a second media service operation request for the target media service operation to the second terminal; A second operation response result sent by the second terminal is received, where the second operation response result is sent by the second terminal after receiving the second media service operation request and completing the target media service operation.

6. The information processing method according to claim 4, wherein: After updating the first business operation global awareness table according to the business operation information, the method further includes: Sending a first media service end operation request to the second application node, where the first media service end operation request includes end service operation information corresponding to the media service end operation, where the end service operation information is used by the second application node to determine whether to forward the first media service end operation request to the first terminal based on the end service operation information and the first service operation; A first end operation response result sent by the second application node is received, where the first terminal sends the first end operation response result to the second application node after receiving the first media service end operation request and completing the media service end operation.

7. The information processing method according to claim 6, characterized in that: After receiving the first end operation response result sent by the second application node, the method further includes: The first service operation global awareness table is updated according to the service operation end information.

8. The information processing method according to claim 7, wherein: The target media service operation is associated with both the first terminal and the second terminal. Before updating the first service operation global awareness table according to the end service operation information, the method further includes: Sending a second media service end operation request for the media service end operation to the second terminal; A second end operation response result sent by the second terminal is received, where the second end operation response result is sent by the second terminal after receiving the second media service end operation request and completing the media service end operation.

9. The information processing method according to claim 2, wherein: The business operation being performed includes at least one of the following: The first application node has entered the first business operation of the execution process; The second business operation recorded in the first business operation global awareness table is executed by other application nodes and synchronized to the first application node through business awareness interaction.

10. An information processing method, applied to a second application node, comprising: receiving a first media service operation request sent by a first application node, where the first media service operation request includes service operation information corresponding to a target media service operation; determining whether to forward the first media service operation request to the first terminal according to the service operation information and a first service operation, where the first service operation is a service operation being executed by the second application node and recorded in a second service operation global awareness table; In a case where it is determined to forward the first media service operation request to the first terminal, the first media service operation request is forwarded to the first terminal.

11. The information processing method according to claim 10, wherein: Before forwarding the first media service operation request to the first terminal, the method further includes: In response to satisfying one of the following conditions, determining to execute an operation of forwarding the media service operation request to the first terminal: There is no record of the business operation being executed in the second business operation global awareness table; In the second service operation global perception table, there is a record of a service operation being executed, and the media object of the service operation being executed is the same as the media object of the target media service operation, but the priority of the service operation being executed is lower than the priority of the target media service operation; In the second service operation global awareness table, there is a record of the service operation being executed, but the media object of the service operation being executed is different from the media object of the target media service operation.

12. The information processing method according to claim 10, wherein: After forwarding the first media service operation request to the first terminal, the method further includes: Receive a first operation response result sent by the first terminal, and send the first operation response result to the first application node, where the first operation response result is sent by the first terminal after receiving the first media service operation request and completing the target media service operation.

13. The information processing method according to claim 12, wherein: Before sending the first operation response result to the first application node, the method further includes: The second business operation global awareness table is updated according to the business operation information.

14. The information processing method according to claim 12, wherein: After sending the first operation response result to the first application node, the method further includes: receiving a first media service end operation request sent by the first application node, where the first media service end operation request includes end service operation information corresponding to the media service end operation; determining whether to forward the first media service end operation request to the first terminal according to the end service operation information and the first service operation; If it is determined that the first media service end operation request is to be forwarded to the first terminal, forwarding the first media service end operation request to the first terminal; Receive a first end operation response result sent by the first terminal, and send the first end operation response result to the first application node, where the first end operation response result is sent by the first terminal after receiving the first media service end operation request and completing the media service end operation.

15. The information processing method according to claim 14, wherein: Before sending the first end operation response result to the first application node, the method further includes: The second service operation global awareness table is updated according to the service operation end information.

16. The information processing method according to claim 11, wherein: The business operation being performed includes at least one of the following: The second application node has entered the first business operation of the execution process; The second business operation recorded in the second business operation global awareness table is executed by other application nodes and synchronized to the second application node through business awareness interaction.

17. An application node, characterized in that: include: at least one processor; at least one memory for storing at least one program; When at least one of the programs is executed by at least one of the processors, the information processing method according to any one of claims 1 to 16 is implemented.

18. A computer-readable storage medium storing computer-executable instructions, characterized in that: The computer-executable instructions are used to execute the information processing method according to any one of claims 1 to 16.

Images