Call service processing method and device, equipment, storage medium and product

Abstract

The invention discloses a call service processing method, device and equipment, a storage medium and a product, which can support data channel media for call waiting, polyphonic ringtone and ring back tone services in a negotiation process of complementing service to improve the data channel media; for the call forwarding service, the data channel release of the called user and the data channel media negotiation of the call forwarding user can be realized; for the call hold service, data channel hold is supported, and the data channel does not need to be reconstructed through additional signaling interaction. According to the call service processing method provided by the invention, the supplementary service and data channel interaction can meet service requirements, and the supplementary service and data channel application experience of a user is ensured.

Description

Technical Field

[0001] This invention relates to the field of communications, and more particularly to a call service processing method, apparatus, device, storage medium, and product. Background Technology

[0002] In terms of IMS (IP Multimedia Subsystem) network evolution and service enhancement, to improve the richness and flexibility of multimedia services, a new media type, IMS DC (Data Channel), independent of audio and video media, is defined in user-established MMTELs (Multimedia Telephony). The introduction of IMS DC aims to enhance IMS call capabilities. Its establishment and closure processes are accompanied by IMS session control flows (session establishment, modification, and release), implemented through IMS signaling and media negotiation. For common call services, the calling and called users normally negotiate the DC media to establish it. However, in supplementary services, call forwarding does not consider whether the DC is allowed after call forwarding and how it is used; call hold does not consider the processing of DC media; call waiting, ringback tones, and color vibration services do not consider providing services through DC. This means that the introduction of DC impacts supplementary services, causing the interaction between supplementary services and the data channel to fail to meet service requirements and affecting user experience. Summary of the Invention

[0003] The purpose of this invention is to provide a call service processing method, apparatus, device, storage medium, and product to improve the DC media negotiation process in supplementary services, so that the interaction between supplementary services and data channels meets service requirements and ensures the user's experience in supplementary services and data channel applications.

[0004] To achieve the above objectives, embodiments of the present invention provide a call service processing method applied to the application server AS of the IP Multimedia Subsystem (IMS), the method comprising:

[0005] Notify the Data Channel Signalling Function (DCSF) of session events;

[0006] Reserve DC resources for IMS DC according to the instructions of DCSF.

[0007] As an improvement to the above scheme, the notification of session events to the Data Channel Signalling Function (DCSF) includes one of the following methods:

[0008] Upon receiving a session establishment request from the calling user or the calling network, notify the DCSF of the session establishment request event;

[0009] Upon receiving a call waiting notification from the called user or the called network, notify the DCSF of the call waiting event or media modification event;

[0010] Upon receiving a ringback tone instruction, notify the DCSF of the ringing event;

[0011] When the network decides to prompt the calling user with a call waiting event, it notifies the DCSF of the call waiting event or media modification event.

[0012] Upon receiving a response from the called user, notify the DCSF of the called user's response event or the successful session establishment event;

[0013] Upon receiving a DC establishment request from the Data Channel Application Server (DC AS), notify the DCSF of the media modification event.

[0014] As an improvement to the above scheme, before receiving the DC establishment request from the data channel application server DC AS and notifying the DCSF of the media modification event, the method further includes:

[0015] Upon receiving a session establishment request from the calling user or the calling network, notify the DC AS of the session establishment request event.

[0016] As an improvement to the above scheme, reserving DC resources for IMS DC according to the instructions of DCSF includes one of the following methods:

[0017] Upon receiving a call waiting notification from the called user or the called network, notify the DC AS of the call waiting event or media modification event;

[0018] Upon receiving a ringback tone instruction, notify the DC AS of the ringing event;

[0019] When the network decides to prompt the calling user with a call waiting event, it notifies the DC AS of the call waiting event or media modification event.

[0020] Upon receiving a response from the called user, notify the DC AS of either a called user response event or a successful session establishment event.

[0021] As an improvement to the above scheme, the reporting of call waiting events, media modification events, or ringing events to the DC AS is used to trigger the DC AS to provide call waiting prompts or ringback tones to the calling user through the DC; or, the reporting of call waiting events, media modification events, or ringing events to the DC AS is used to trigger the DC AS to provide ringback tones to the called user through the DC; wherein, the media of the call waiting prompts, ringback tones, or ringback tones is DC media.

[0022] As an improvement to the above scheme, the notification of the called party's response event to the DC AS is used to trigger the DC AS to stop providing DC media to the calling or called user.

[0023] To achieve the above objectives, embodiments of the present invention also provide a call service processing method applied to a DCSF, the method comprising:

[0024] Upon receiving a session event from the IMS AS, check the user's DC subscription or carrier policy;

[0025] Establish IMS DCs for users based on DC contracts or operator policies.

[0026] As an improvement to the above solution, the step of establishing an IMS data channel for users based on DC subscriptions or operator policies includes:

[0027] When the called user's DC subscription or operator policy allows DC applications to be provided before the call is connected, the IMS AS is instructed to establish a bootstrap data channel (BDC) for the user before the call is connected.

[0028] As an improvement to the above solution, the DC application is used to implement call waiting service, ringback tone service, or ringback vibration service.

[0029] As an improvement to the above scheme, after instructing the IMS AS to establish a bootstrap data channel (BDC) for the user before the call is connected, the method further includes:

[0030] DCSF pushes DC applications related to call waiting services, ringback tones services, or ringback vibration services to users through BDC; or, users obtain DC applications related to call waiting services, ringback tones services, or ringback vibration services through BDC.

[0031] As an improvement to the above solution, the method further includes:

[0032] Upon receiving a call waiting event, media modification event, or ringing event, a first instruction is sent to the DC AS; wherein, the first instruction is used to trigger the DC AS to provide a call waiting prompt or ringback tone to the calling user through the DC, or the first instruction is used to trigger the DC AS to provide a ringback tone of the DC media to the called user through the DC; wherein, the media of the call waiting prompt, ringback tone, or ringback tone is the DC media.

[0033] As an improvement to the above solution, the method further includes:

[0034] Upon receiving a called party's response event, a second instruction is sent to the DC AS; wherein the second instruction is used to trigger the DC AS to stop providing DC media to the calling or called user.

[0035] To achieve the above objectives, embodiments of the present invention also provide a call service processing method, applied to the application server AS of the IP Multimedia Subsystem (IMS), the method comprising:

[0036] Notify the DCSF of call forwarding events or call setup failure events;

[0037] Release the DC resources of the IMS DC according to the instructions of DCSF.

[0038] As an improvement to the above scheme, after notifying the DCSF of the call forwarding event or call setup failure event, the method further includes:

[0039] Determine the processing of the IMS DC media description.

[0040] As an improvement to the above scheme, the process of determining the IMS DC media description includes one of the following methods:

[0041] Transmit the IMS DC media description in the received call setup request;

[0042] Generate a new IMS DC media description, send a call setup request to the call forwarding user or the call forwarding user's network, and carry the IMS DC media description;

[0043] Send a call setup request to the call forwarding user or the call forwarding user's network, and pass through the IMS DC media description in the received call setup request according to the DCSF's instructions, or generate a new IMS DC media description according to the DCSF's instructions.

[0044] As instructed by DCSF, IMS DC media descriptions are not carried.

[0045] As an improvement to the above solution, the method further includes:

[0046] When the IMS DC media description in the received call setup request is transparently transmitted or a new IMS DC media description is generated, a call setup request is sent to the call forwarding user or the call forwarding user's network, carrying the IMS DC media description.

[0047] When instructed by the DCSF to send a call setup request to the call forwarding user or the call forwarding user's network without carrying the IMS DC media description, the request is sent without carrying the IMS DC media description.

[0048] As an improvement to the above scheme, the IMS DC media description in the call setup request received through the transparent transmission includes at least one of the following:

[0049] The bootstrap data channel (BDC) between the calling user and the call forwarding user's network;

[0050] The bootstrap data channel (BDC) between the calling network and the call forwarding user.

[0051] To achieve the above objectives, embodiments of the present invention also provide a call service processing method applied to a DCSF, the method comprising:

[0052] Receive IMS AS notifications for call forwarding events or call setup failure events.

[0053] Send an instruction to the IMS AS to release the DC resources of the IMS DC.

[0054] As an improvement to the above solution, the method further includes one of the following steps:

[0055] Instruct the IMS AS to describe the IMS DC media in the received call setup request via transparent transmission;

[0056] Instruct IMS AS to generate a new IMS DC media description;

[0057] Instructs IMS AS not to carry IMS DC media description.

[0058] As an improvement to the above scheme, the IMS DC media description includes at least one of the following:

[0059] The bootstrap data channel (BCD) between the calling user and the call forwarding network;

[0060] The bootstrap data channel (BCD) between the calling network and the call forwarding user.

[0061] As an improvement to the above solution, the method further includes one of the following steps:

[0062] When the called user's DC service subscription includes call forwarding service, determine the called user's call forwarding service logic;

[0063] Whether to allow call forwarding is determined based on call forwarding network capabilities and / or user subscription;

[0064] Determine whether to include an IMS DC media description in the call setup request sent to the call forwarding user or the call forwarding user's network, based on the call forwarding network capabilities and / or the user's subscription.

[0065] To achieve the above objectives, embodiments of the present invention also provide a call service processing method, applied to the application server AS of the IP Multimedia Subsystem (IMS), the method comprising:

[0066] Notify the DCSF of call hold events or media property modification events;

[0067] Activate, maintain, or restore the DC according to the instructions of the DCSF, or modify the orientation properties of the DC media according to the instructions of the DCSF.

[0068] As an improvement to the above scheme, in call hold services, the user initiating call hold indicates one of the following to the network or the user whose call is being held through a session modification request and an SDP offer session description protocol proposal:

[0069] DC media deactivation or retention;

[0070] DC media activation or restoration.

[0071] As an improvement to the above scheme, in call hold services, the user whose call is held uses the response to the session modification request and the SDP answer session description protocol response to indicate one of the following to the user who initiated the call hold:

[0072] DC Media has been deactivated or has been retained;

[0073] DC media is either deactivated or retained;

[0074] DC Media has been activated or restored;

[0075] DC media is activated or restored.

[0076] As an improvement to the above scheme, the notification of call hold events to the DCSF includes one of the following:

[0077] When the received SDP offer or SDP answer contains a call hold instruction or a DC media attribute modification to deactivation, notify the DCSF to hold the call or deactivate the DC media attribute.

[0078] When the received SDP offer or SDP answer contains a call recovery instruction or the DC media attribute has been modified, notify the DCSF to activate the call recovery or DC media attribute modification.

[0079] When the received SDP offer or SDP answer contains a call recovery instruction or the DC media attribute is modified to be active, notify the DCSF to resume call recovery or modify the DC media attribute to be active.

[0080] As an improvement to the above scheme, the step of activating / activating DC according to the instruction of DCSF includes:

[0081] According to the instructions of DCSF, filter out all DC media associated with the call hold session;

[0082] Modify the corresponding session description protocol to provide deactivation / activation indications for the associated application data channel ADC.

[0083] As an improvement to the above scheme, the step of activating / activating DC according to the instruction of DCSF includes:

[0084] Modify the session description protocol as instructed by DCSF to indicate deactivation / activation of the associated ADC, or to indicate deactivation / activation of a specified ADC.

[0085] To achieve the above objectives, embodiments of the present invention also provide a call service processing method applied to the Data Channel Signalling Function (DCSF), the method comprising:

[0086] Receive call hold events or media attribute modification events reported by IMS AS;

[0087] Send instructions to deactivate, activate, maintain, or restore the DC to the IMS AS, or send instructions to modify the orientation properties of the DC media to the IMS AS.

[0088] As an improvement to the above solution, the method further includes:

[0089] Based on the call hold / recovery instructions reported by IMS AS, filter out all DC media associated with the call hold session;

[0090] Deactivate / activate the associated application data channel ADC; or, deactivate / activate a specified ADC.

[0091] To achieve the above objectives, embodiments of the present invention also provide a call service processing apparatus, applied to the application server AS of the IP Multimedia Subsystem (IMS), the apparatus comprising:

[0092] The session event notification module is used to notify the Data Channel Signalling Function (DCSF) of session events;

[0093] The DC resource reservation module is used to reserve DC resources for IMS DC according to the instructions of DCSF.

[0094] To achieve the above objectives, embodiments of the present invention also provide a call service processing apparatus applied to the Data Channel Signalling Function (DCSF), the apparatus comprising:

[0095] The inspection module is used to receive session events sent by the IMS AS and inspect the user's DC subscription or carrier policy.

[0096] The IMS DC establishment module is used to establish IMS DCs for users based on DC subscriptions or operator policies.

[0097] To achieve the above objectives, embodiments of the present invention also provide a call service processing apparatus, applied to the application server AS of the IP Multimedia Subsystem (IMS), the apparatus comprising:

[0098] The event notification module is used to notify the DCSF of call forwarding events or call setup failure events.

[0099] The DC resource release module is used to release the DC resources of the IMS DC according to the instructions of the DCSF.

[0100] To achieve the above objectives, embodiments of the present invention also provide a call service processing apparatus applied to the Data Channel Signalling Function (DCSF), the apparatus comprising:

[0101] The event receiving module is used to receive call forwarding events or call setup failure events notified by IMS AS.

[0102] The DC resource release instruction sending module is used to send an instruction to the IMS AS to release the DC resources of the IMS DC.

[0103] To achieve the above objectives, embodiments of the present invention also provide a call service processing apparatus, applied to the application server AS of the IP Multimedia Subsystem (IMS), the apparatus comprising:

[0104] The event notification module is used to notify DCSF of call hold events or media property modification events;

[0105] The data channel modification module is used to activate, maintain, or restore the DC according to the instructions of the DCSF, or to modify the orientation properties of the DC media according to the instructions of the DCSF.

[0106] To achieve the above objectives, embodiments of the present invention also provide a call service processing apparatus applied to the Data Channel Signalling Function (DCSF), the apparatus comprising:

[0107] The event receiving module is used to receive call hold events or media attribute modification events reported by IMS AS;

[0108] The instruction sending module is used to send instructions to the IMS AS to deactivate, activate, maintain, or restore the DC, or to send instructions to the IMS AS to modify the direction properties of the DC media.

[0109] To achieve the above objectives, embodiments of the present invention also provide a call service processing device, including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor. When the processor executes the computer program, it implements the call service processing method as described in any of the above embodiments.

[0110] To achieve the above objectives, embodiments of the present invention also provide a computer-readable storage medium, the computer-readable storage medium including a stored computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform the call service processing method as described in any of the above embodiments.

[0111] To achieve the above objectives, embodiments of the present invention also provide a computer program product, including computer instructions, which, when executed by a processor, implement the call service processing method as described in any of the above embodiments.

[0112] Compared to existing technologies, the call service processing method, apparatus, device, storage medium, and product disclosed in this invention, in the process of supplementing services to improve the negotiation of data channel media, support data channel media for call waiting, ringback tones, and color vibration services; for call forwarding services, it can realize the release of the called user's data channel and the negotiation of the data channel media for the forwarding user; and for call hold services, it supports data channel hold without the need for additional signaling interaction to rebuild the data channel. The call service processing method provided by this invention enables supplementary services and data channel interaction to meet service requirements, ensuring the user's experience in supplementary services and data channel applications. Attached Figure Description

[0113] Figure 1 This is a schematic diagram of the framework of an IP multimedia subsystem provided by existing technology;

[0114] Figure 2 This is a flowchart of the first call service processing method provided in the embodiments of the present invention;

[0115] Figure 3 This is a flowchart of the second call service processing method provided in the embodiments of the present invention;

[0116] Figure 4 This is a flowchart of the third call service processing method provided in the embodiments of the present invention;

[0117] Figure 5 This is a flowchart of the fourth call service processing method provided in the embodiments of the present invention;

[0118] Figure 6 This is a flowchart of the fifth call service processing method provided in the embodiments of the present invention;

[0119] Figure 7 This is a flowchart of the sixth call service processing method provided in the embodiments of the present invention;

[0120] Figure 8 This is a structural block diagram of the first call service processing device provided in the embodiments of the present invention;

[0121] Figure 9 This is a structural block diagram of the second type of call service processing device provided in the embodiments of the present invention;

[0122] Figure 10 This is a structural block diagram of the third type of call service processing device provided in the embodiments of the present invention;

[0123] Figure 11 This is a structural block diagram of the fourth call service processing device provided in the embodiments of the present invention;

[0124] Figure 12 This is a structural block diagram of the fifth type of call service processing device provided in the embodiments of the present invention;

[0125] Figure 13 This is a structural block diagram of the sixth type of call service processing device provided in the embodiments of the present invention;

[0126] Figure 14 This is a structural block diagram of a call service processing device provided in an embodiment of the present invention. Detailed Implementation

[0127] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0128] Enhanced multimedia telephony (EMT) carries accompanying data channel services by overlaying IMS DC on top of audio and video calls within the IP Multimedia Subsystem (IPMS). The data channel can provide users with richer real-time interactive services beyond audio and video calls. For example, terminal devices (such as UE1 and UE2) in the same IMS session can determine the IP addresses and ports used by both terminal devices to transmit data, establish DTLS (Datagram Transport Layer Security) and SCTP (Stream Control Transmission Protocol) associations, and obtain the corresponding description information of the data channel through the IMS SDP (Session Description Protocol) media negotiation process. This allows one or more data channels to be transmitted in parallel with audio (Speech) and video (Video) in the IMS session. Calling and called users can download various applications (i.e., DC Apps) from the network-side DCSF (Data Channel Signaling Function) through the data channel and run these applications before, during, or after audio and video calls. By transmitting various types of application data in the data channel, calling and called users can communicate in ways other than voice or video calls, such as screen sharing, real-time translation, location sharing, overlaying AR effects, and even immersive interactions with synchronized auditory, visual, and tactile senses to enhance the user experience.

[0129] See Figure 1 , Figure 1 This is a schematic diagram of the existing IP Multimedia Subsystem (IMS) framework. To support the actual deployment of IMS Data Center (IMS DC), an IMS architecture supporting IMS DC is defined, introducing DCSF, MF (Media Function), DC application-related servers and a database, and enhancing IMS AS (Application Server), MRF (Media Resource Function), and UE (User Equipment). The specific applications of each module in the framework are as follows:

[0130] 1. Enhanced UE support for DC capabilities, including DC capability negotiation, establishment, release, and application.

[0131] 2. DCSF is a part of the logical functional entity in the data channel server (DCS). DCSF is mainly used to provide data channel signaling control functions, such as providing DC control logic and managing IMS DC.

[0132] 3. P-CSCF (Proxy-Call Session Control Function) is the entry node for UE to access the IMS network. It is mainly responsible for forwarding SIP (session initiation protocol) signaling between IMS users and their home network.

[0133] 4. The S-CSCF (Serving-Call Session Control Function) is the unified entry point of the IMS user's home network, responsible for allocating or querying the S-CSCF that serves the user.

[0134] 5. IMS-AGW (IMS-Access Media Gateway) can provide IMS network access gateway and media gateway functions.

[0135] 6. MF provides DC media resource reservation, update, and release capabilities.

[0136] 7. Remote IMS is the IMS on the called user's side.

[0137] 8. IMS AS enhances support for interfaces with DCSF and MRF / MF, and determines whether to interact with DCSF and MF / MRF based on the DC subscription;

[0138] 9. The HSS (Home Subscriber Server) is the main user database that supports IMS network entities for handling calls / sessions. It contains user profiles, performs user authentication and authorization, and provides information about the user's physical location.

[0139] 10. NEF (Network Exposure Function) is responsible for managing all external applications that expose network data to the outside world, and provides functions such as opening up external application QoS (Quality of Service) customization capabilities, mobility state event subscription, and AF (Application Function) request distribution.

[0140] 11. DC AS (Data Channel Application Server) is used to manage data channels, such as creating and releasing data channels.

[0141] 12. DCAR (Data Channel Application Repository) is used to store data channel-related applications.

[0142] It is worth noting that, Figure 1 The given IMS system framework is merely an example; this invention can actually be applied to all existing IMS systems, and... Figure 1 The Gm, lq, Mb, Mw, N70, ISC, N71, Sh, N72, Sc, DC1~5, MDC1~3, and N33 mentioned in the document all represent interfaces and are only used as examples. Other interfaces can also be used in actual applications.

[0143] Specifically, based on their different uses, DCs can be divided into BDCs (Bootstrap Data Channels) and ADCs (Application Data Channels). IMS networks support data channel services. After establishing a communication connection, calling and called user terminals with DC services can download available applications from the IMS network and use these applications to send multimedia information to each other via the data channel. BDCs are used by terminal devices to obtain DC applications (Apps) from DCSFs. Terminals supporting data channel capabilities can establish BDCs with the calling network's DCSF and / or the called network's DCSF. The specific establishment method depends on whether each network supports data channel capabilities and the service subscription status of both parties' terminal devices on their respective networks. ADCs are used to transmit application data generated by the running DC Apps of both communicating parties. Application data transmission can occur between terminals or between a terminal and the network.

[0144] To address the issue of incomplete DC media negotiation in existing call services, which leads to insufficient interaction between supplementary services and data channels, this invention provides corresponding embodiments for three call service types. These three call service types include: 1. Supplementary services (such as call waiting, ringback tones, and color ringing); 2. Call forwarding services; and 3. Call waiting services.

[0145] For the first type of supplementary service (such as call waiting, ringback tone, and color ringing), if the supplementary service supports DC media, and provides call waiting, ringback tone, and color ringing services to the calling and called users during the call setup phase in conjunction with DC, the network needs to support the association between supplementary service events and DC service subscriptions. However, there is currently no solution for this in call services. To address the issue that call waiting, ringback tone, and color ringing services in supplementary services do not consider providing services through DC, causing the introduction of DC to affect supplementary services and resulting in the interaction between supplementary services and data channels not meeting service requirements, this invention provides two call service processing methods, which are described in Embodiment 1 and Embodiment 2 respectively.

[0146] Example 1

[0147] This invention provides a first call service processing method, applied to the application server AS of the IP Multimedia Subsystem (INS), see [link to documentation]. Figure 2 The first type of call service processing method includes:

[0148] S11. Notify the session event to the Data Channel Signalling Function (DCSF);

[0149] S12. Reserve DC resources for IMS data channel DC according to the instructions of DCSF.

[0150] The supplementary services include at least one of call waiting service, ringback tone service, and ringback vibration service.

[0151] For example, in this embodiment of the invention, the IMS AS of the called user is implemented. When the called IMS AS detects that an application data channel (ADC) for supplementary services has been established with the calling user, the called IMS AS reports a session event to the called DCSF, and the called DCSF instructs the called IMS AS to reserve ADC resources.

[0152] In this embodiment of the invention, when an ADC is detected to establish a supplementary service with the calling user, DC resources of the ADC are reserved in advance. Thus, when a call prompt event is met, the called DCSF can trigger the DC AS to provide prompt information to the calling user through the ADC, so that call waiting, ringback tone, and ringback services can also support DC media, enabling accurate application of DC and thus improving call quality.

[0153] Specifically, the notification of session events to the Data Channel Signalling Function (DCSF) includes one of the following methods:

[0154] 1.1) Upon receiving a session establishment request from the calling user or the calling network, notify the DCSF of the session establishment request event;

[0155] 1.2) Upon receiving a call waiting notification from the called user or the called network, notify the DCSF of the call waiting event or media modification event;

[0156] 1.3) Upon receiving a ringback tone instruction, notify the DCSF of the ringing event;

[0157] 1.4) When the network decides to notify the calling user of the call waiting event, it notifies the DCSF of the call waiting event or the media modification event;

[0158] 1.5) Upon receiving a response from the called user, notify the DCSF of the called user's response event or the successful session establishment event;

[0159] 1.6) Upon receiving a DC establishment request from the Data Channel Application Server (DC AS), notify the DCSF of the media modification event.

[0160] Furthermore, in 1.6), before receiving a DC establishment request from DC AS and notifying DCSF of a media modification event, the method further includes: receiving a session establishment request from a calling user or calling network and notifying DC AS of a session establishment request event.

[0161] For example, the IMS AS reports a session event to the DC AS, the DC AS requests the IMS AS to establish a DC, and after the DC is established, the IMS AS reports a session event, triggering the DC AS to provide DC applications through the DC.

[0162] Specifically, in step S12, the DC resources of the IMS data channel DC are reserved according to the instructions of DCSF, including one of the following methods:

[0163] 2.1) Upon receiving a call waiting notification from the called user or the called network, notify the DC AS of the call waiting event or media modification event;

[0164] 2.2) Upon receiving a ringback tone instruction, notify the DC AS of the ringing event;

[0165] 2.3) When the network decides to prompt the calling user with a call waiting event, it notifies the DC AS of the call waiting event or media modification event;

[0166] 2.4) Upon receiving the response from the called user, notify the DC AS of the called user's response event or the successful session establishment event.

[0167] Furthermore, the reporting of call waiting events, media modification events, or ringing events to the DC AS is used to trigger the DCAS to provide call waiting prompts or ringback tones to the calling user via the DC; or, the reporting of call waiting events, media modification events, or ringing events to the DC AS is used to trigger the DC AS to provide ringback tones to the called user via the DC; wherein the media for the call waiting prompts, ringback tones, or ringback tones is DC media. The notification of called party answering events to the DC AS is used to trigger the DC AS to stop providing DC media to the calling user or the called user.

[0168] For example, after receiving a session event from the calling network, the called IMS AS reports the session event to the called DCSF. The called DCSF then checks whether the called user has subscribed to call waiting services and ringback tone services provided by the DC. If so, it establishes a BDC between the calling user and the called network and pushes an automatic download program for the supplementary service DC application. The calling user automatically downloads the supplementary service DC application according to the download program. After the download is complete, it automatically establishes a P2A (Person to Application) ADC with the called DC AS. After the DC AS provides a call waiting prompt or DC media ringback tone to the calling user through the supplementary service DC application-related ADC, the called IMS AS reports a called party answer event to the called DCSF, causing the called DCSF to trigger the DC AS to stop DC media. That is, at this point, a prompt has been completed, and DC media can be temporarily stopped.

[0169] Compared to existing technologies, the first call service processing method disclosed in this invention supports DC media in the negotiation process of supplementary services to improve DC media, and can also support DC media for call waiting, ringback tones, and ringback services. This enables supplementary services to interact with the data channel to meet service requirements and ensures the user's supplementary service and DC application experience.

[0170] Example 2

[0171] This invention provides a second call service processing method, applied to the Data Channel Signalling Function (DCSF), see [link to relevant documentation]. Figure 3 The second call service processing method includes:

[0172] S21. Upon receiving a session event from the IMS AS, check the user's DC subscription or carrier policy.

[0173] S22. Establish an IMS DC for the user based on the DC contract or operator policy.

[0174] Specifically, step S22 includes: when the called user's DC subscription or operator policy allows the DC application to be provided before the call is connected, instructing the IMS AS to establish a bootstrap data channel BDC for the user before the call is connected.

[0175] Specifically, the DC application is used to implement call waiting service, ringback tone service, or ringback vibration service.

[0176] Specifically, after instructing the IMS AS to establish a Guided Data Channel (BDC) for the user before the call is connected, the method further includes: the DCSF pushing DC applications related to call waiting service, ringback tone service, or ringback tone service to the user through the BDC; or, the user obtaining DC applications related to call waiting service, ringback tone service, or ringback tone service through the BDC.

[0177] Specifically, the method further includes:

[0178] S23. Upon receiving a call waiting event, media modification event, or ringing event, send a first instruction to the DC AS; wherein, the first instruction is used to trigger the DC AS to provide a call waiting prompt or ringback tone to the calling user through the DC, or the first instruction is used to trigger the DC AS to provide a ringback tone to the called user through the DC; wherein, the media of the call waiting prompt, ringback tone, or ringback tone is DC media.

[0179] For example, after receiving a session event from the calling network, the called IMS AS reports the session event to the called DCSF. The called DCSF then checks whether the called user has subscribed to call waiting services and ringback tone services provided by the DC. If so, it establishes a BDC between the calling user and the called network and pushes an automatic download program for the supplementary service DC application. The calling user automatically downloads the supplementary service DC application according to the download program. After the download is complete, it automatically establishes a P2A (Person to Application) ADC with the called DC AS.

[0180] Specifically, the method further includes:

[0181] S24. Upon receiving a called party response event, send a second instruction to the DC AS; wherein the second instruction is used to trigger the DCAS to stop providing DC media to the calling or called user.

[0182] For example, after the DC AS provides the calling user with a call waiting prompt or DC media ringback tone through the supplementary service DC application related ADC, the called IMS AS reports the called party answering event to the called DCSF, causing the called DCSF to trigger the DC AS to stop DC media. That is, at this time, a prompt has been completed, and DC media can be temporarily stopped.

[0183] It is worth noting that the specific working process of the second call service processing method described in this embodiment of the invention can refer to the working process of the first call service processing method described above, and will not be repeated here.

[0184] For the second type of call forwarding service, there are multiple scenarios (busy forwarding, no-answer forwarding, user not registered, etc.). The conditions for busy forwarding and no-answer forwarding are related to the called user's behavior (user decides to be busy, user does not answer). The called user's IMS AS is unaware of the forwarding event until the forwarding conditions are met. When a DC establishment request is made during call setup, the called user's DC resource reservation will still be executed normally. Currently, the DC media negotiation in the call processing method is not perfect, leading to the following two problems: 1) How to release the called user's DC and negotiate the forwarding user's DC media after forwarding; 2) If the called user has not subscribed to DC, can DC media negotiation be performed during call forwarding? To solve the problem that the call forwarding service does not consider whether DC can be used after forwarding and how to use DC when forwarding occurs, resulting in the call forwarding service and data channel interaction not meeting business requirements, this invention provides two call service processing methods, described in Embodiments 3 and 4 respectively.

[0185] Example 3

[0186] This invention provides a third call service processing method, applied to the application server AS of the IP Multimedia Subsystem (IMS), see [link to documentation]. Figure 4 The third call service processing method includes:

[0187] S31. Notify the DCSF of a call forwarding event or a call setup failure event;

[0188] S32. Release the DC resources of IMS DC according to the instructions of DCSF.

[0189] Specifically, after notifying the DCSF of a call forwarding event or a call setup failure event, the method further includes: determining the processing of the IMS DC media description.

[0190] For example, in this embodiment of the invention, the IMS AS on the called user's side is implemented. When the called user's IMS AS detects that the called user meets the call forwarding conditions, if the called user has subscribed to forwarding, the called user's IMS AS will forward the call according to the forwarding number pre-set by the called user. After the call forwarding is executed, a notification message is sent to the called DCSF to inform the called DCSF of the status of this call, so that the called DCSF can instruct the IMS AS to release the DC media resources pre-reserved for the called user. The IMS AS releases the DC media resources and determines the SDP for this call forwarding, thereby negotiating the DC media with the forwarding user and completing the establishment of the DC channel between the calling user and the forwarding user.

[0191] For example, when the called IMS AS receives a call setup request (initial INVITE) from the calling network, if the call setup request carries a DC media description, it determines that the called user has DC capability, that is, the called user has completed the DC service subscription. The IMS AS then reports the call setup request to the called user's DCSF and modifies the DC media description according to the instructions of the called DCSF. If the calling user does not need to establish real-time communication with the called user at this time, the BDC between the calling user and the called network can be deleted, and the BDC between the calling network and the called user can be modified, such as by changing the port number; a BDC between the called network and the called user can be generated, and the DC media resources of the called user can be reserved.

[0192] Specifically, the call transfer conditions include one of the following 1.1 to 1.3:

[0193] 1.1 Receive a busy line notification from the called user.

[0194] For example, if the called user returns a 486 (indicating that the user is busy), it is determined that the called user is currently busy. If the called user has signed up for forwarding, forwarding will be determined based on the forwarding number set by the called user.

[0195] S112, The timer expired and no response was received from the called user.

[0196] For example, if no response is received from the called user before the timer expires, it is determined that the called user has not responded. If the called user has signed up for forwarding, forwarding is determined based on the forwarding number set by the called user.

[0197] S113. Receive a temporary unavailability notification from the called user.

[0198] For example, if a 480 (Temporarily Unavailable) response is received from the called user's S-CSCF, it is determined that the called user is not registered. If the called user has signed up for forwarding, forwarding will be determined based on the forwarding number set by the called user.

[0199] Specifically, embodiments of the present invention also require determining the call forwarding session description protocol. There are two methods: the first is that the called IMS AS decides the call forwarding SDP autonomously, and the second is that the DCSF decides the call forwarding SDP.

[0200] In the first implementation, the IMS AS notifies the DCSF of a call setup failure event; wherein the call setup failure event carries the reason for the called user's call failure. At this time, the DC media description in the call setup request is forwarded in the call forwarding setup request.

[0201] For example, the called IMS AS notifies the called DCSF that it cannot establish a call with the called user during this call process, and sends a notification message to the called DCSF carrying the reason for the call failure, such as a failure response 486 (user busy), 480 (Temporarily Unavailable), or cancellation of the call to B. The called IMS AS releases the resources reserved for the called user (i.e., the IMS DC media resources mentioned in the above steps) according to the instructions of the called DCSF. According to the call forwarding logic, the called IMS AS forwards the IMS DC media description received from the calling network in the call setup request (INVITE) it receives, forwarding it to the call forwarding network and the call forwarding user. The forwarded IMS DC media description is carried in the call setup request itself.

[0202] In this embodiment of the invention, by reporting the reason for the called user's call failure to the called DCSF, the called DCSF can quickly release the IMS DC media resources pre-reserved for the called user. This provides a basis for subsequent IMS DC media negotiation between the calling user and the call forwarding user. Furthermore, the called IMS AS's autonomous call forwarding SDP enables the release of the called user's DC and the DC media negotiation of the call forwarding user after call forwarding. Additionally, even if the called user has not subscribed to DC, IMS DC media negotiation during the call forwarding process can be completed through the called IMSAS's autonomous call forwarding SDP.

[0203] In the second implementation, the IMS AS notifies the DCSF of the call forwarding event. At this time, the IMS DC media description processing method in the call forwarding setup request is determined according to the instructions of the DCSF on the called user's side.

[0204] Specifically, the process of determining the IMS DC media description includes one of the following methods:

[0205] 3.1) Transmit the IMS DC media description in the received call setup request;

[0206] 3.2) Generate a new IMS DC media description, send a call setup request to the call forwarding user or the call forwarding user's network, and carry the IMS DC media description;

[0207] 3.3) Send a call setup request to the call forwarding user or the call forwarding user's network, and transmit the IMS DC media description in the received call setup request according to the DCSF's instructions, or generate a new IMS DC media description according to the DCSF's instructions.

[0208] 3.4) As instructed by DCSF, IMS DC media descriptions are not carried.

[0209] For example, when the IMS DC media description in the received call setup request is transparently transmitted or a new IMS DC media description is generated, a call setup request carrying the IMS DC media description is sent to the call forwarding user or the call forwarding user's network. When the IMS DC media description is not carried according to the DCSF's instruction, a call setup request without carrying the IMS DC media description is sent to the call forwarding user or the call forwarding user's network.

[0210] For example, the called IMS AS notifies the called DCSF that a call forwarding event has occurred. The called DCSF instructs the IMS AS to release resources reserved for the called party. The called IMS AS releases the resources reserved for the called party according to the DCSF's instruction and determines the processing method of the DC media description in the call forwarding setup request (INVITE) according to the DCSF's instruction. The processing method includes one of the following 3.1) to 3.4). The IMS DC media description in the call setup request received through the transparent transmission includes at least one of the following: a bootstrap data channel (BDC) between the calling user's network and the forwarding user's network; or a bootstrap data channel (BDC) between the calling network and the forwarding user.

[0211] Furthermore, the called DCSF determines the DC media description in the call forwarding setup request based on the message reported by the application server.

[0212] For example, the called DCSF determines the DC media description in the call forwarding setup request based on the report from the called IMS AS. When the called DCSF extends the call forwarding service based on the DC, and the DC service subscription includes the call forwarding service, the called DCSF will determine the call forwarding service logic, such as determining whether to allow DC call forwarding based on the forwarding network capabilities and subscription, or determining whether the initial call setup request should carry DC media, etc.

[0213] In this embodiment of the invention, by reporting the call forwarding event to the called party's DCSF, the DC resources of the IMSDC can be released according to the DCSF's instructions, providing a basis for subsequent DC media negotiation between the calling user and the forwarding user. Furthermore, the called party's IMSAS determines the SDP for call forwarding according to the instructions of the called party's DCSF, thus enabling the release of the called party's DC resources and the DC media negotiation of the forwarding user after call forwarding. Additionally, even if the called party has not subscribed to DC, the DC media negotiation during the call forwarding process can be completed by determining the SDP for call forwarding according to the instructions of the called party's DCSF.

[0214] Specifically, after determining the call forwarding session description protocol, the IMS AS forwards the session initiation protocol message and session description protocol message between the calling user and the call forwarding user.

[0215] For example, after completing the DC media negotiation between the calling user and the call forwarding user, the called IMS AS forwards the SIP and SDP messages between the calling user and the call forwarding user. SIP is described as being used to create, modify, and terminate a session between one or more participants, and SDP is used in the message body of SIP to describe the media information of the multimedia session. By forwarding the SIP and SDP messages, the session between the calling user and the call forwarding user can be completed.

[0216] Compared to existing technologies, the third call service processing method disclosed in this invention, in the negotiation process of supplementary services to improve DC media, for call forwarding services, can realize the DC release of the called user and the DC media negotiation of the forwarding user, which enables the supplementary service to interact with the data channel to meet service requirements and ensure the user's supplementary service and DC application experience.

[0217] Example 4

[0218] This invention provides a fourth call service processing method, applied to DCSF, see [link / reference]. Figure 5 The fourth call service processing method includes:

[0219] S41. Receive IMS AS notification of call forwarding event or call setup failure event.

[0220] S42. Send an instruction to the IMS AS to release the DC resources of the IMS DC.

[0221] Specifically, the method further includes one of the following steps:

[0222] Instruct the IMS AS to describe the IMS DC media in the received call setup request via transparent transmission;

[0223] Instruct IMS AS to generate a new IMS DC media description;

[0224] Instructs IMS AS not to carry IMS DC media description.

[0225] Specifically, the IMS DC media description includes at least one of the following:

[0226] The bootstrap data channel (BCD) between the calling user and the call forwarding network;

[0227] The bootstrap data channel (BCD) between the calling network and the call forwarding user.

[0228] Specifically, the method further includes one of the following steps:

[0229] When the called user's DC service subscription includes call forwarding service, determine the called user's call forwarding service logic;

[0230] Whether to allow call forwarding is determined based on call forwarding network capabilities and / or user subscription;

[0231] Determine whether to include an IMS DC media description in the call setup request sent to the call forwarding user or the call forwarding user's network, based on the call forwarding network capabilities and / or the user's subscription.

[0232] It is worth noting that the working process of the fourth call service processing method described in the embodiments of the present invention can refer to the working process of the third call service processing method described in the above embodiments, and will not be repeated here.

[0233] For the third type of call hold service, where the call hold service occurs during a call, the mobile user currently in a call (the call hold user) can temporarily interrupt the original user's (the call hold user) call and make a new call while maintaining contact with the original user's phone. When audio / video media is held, if the DC (Data Center) is not held, it affects new calls. Existing call hold services do not support DC holding, requiring the UE to disable all ADCs (Analog and Digitized Controllers) during the hold call. Thus, when audio / video media resumes, the UE needs additional signaling interaction to rebuild the ADCs; furthermore, the DCSF (Data Center Default Switch) is unaware of the call hold, and the BDC (Browser Data Center) is not held, yet the network still pushes application lists or information to the UE, impacting user experience. To address the issue of the lack of consideration for DC media processing in call hold services, leading to inadequate interaction between the call hold service and data channels, this invention provides two call service processing methods, illustrated in Embodiments 5 and 6.

[0234] Example 5

[0235] The fifth call service processing method provided in this embodiment of the invention is applied to the application server AS of the IP Multimedia Subsystem (IMS). See [link to relevant documentation]. Figure 6 The fifth call service processing method includes:

[0236] S51. Notify the DCSF of a call hold event or media property modification event;

[0237] S52. Activate, maintain, or restore the DC according to the instructions of the DCSF, or modify the orientation properties of the DC media according to the instructions of the DCSF.

[0238] For example, this embodiment of the invention is implemented by the IMS AS of the call-holding user and the call-held user. During a call-holding service, the IMS AS of the call-holding user notifies the DCSF of the call-held user of a call-holding event or a media attribute modification event. Similarly, the IMS AS of the call-held user also notifies the DCSF of the call-holding user of a call-holding event or a media attribute modification event. The call-held user and the DCSF of the call-held user send instructions, causing the IMS AS of the call-holding user and the call-held user to process the DC according to their respective instructions, to deactivate, activate, hold, or restore the DC, or modify the direction attributes of the DC media.

[0239] Specifically, in call hold services, the user initiating the call hold instructs the network or the user whose call is being held to do one of the following through a session modification request and an SDP offer session description protocol proposal:

[0240] DC media deactivation or retention;

[0241] DC media activation or restoration.

[0242] For example, for a call-on-call user, when a call-on-call event occurs, since the call-on-call user needs to establish a call with a new user, the audio and video media with the called-on-call user can be retained, and the DC media can be deactivated, but the DC media resources are still retained. At this time, the call-on-call user uses a session modification request and an SDP offer to instruct the network and the called-on-call user to retain the audio and video media and deactivate the DC media (BDC and ADC). When the call-on-call event ends, since the call-on-call user needs to return to the call with the called-on-call user, the audio and video media needs to be restored and the DC media needs to be activated. At this time, the call-on-call user uses a session modification request and an SDP offer to instruct the network and the called-on-call user to restore the audio and video media and activate the DC media (BDC and ADC).

[0243] Specifically, in call hold services, the user whose call is held uses the response to the session modification request and the SDP answer session description protocol response to indicate one of the following to the user who initiated the call hold:

[0244] DC Media has been deactivated or has been maintained;

[0245] DC media is either deactivated or retained;

[0246] DC Media has been activated or restored;

[0247] DC media is activated or restored.

[0248] For example, for a user whose call is held, when a call hold event occurs, the user is informed via a session modification response and an SDP answer that the audio / video media and DC media (ADC) have been held. At the end of the call hold event, the user is informed via the session modification response and an SDP answer that the audio / video media has been restored, and the DC media (ADC) is to be held or to be restored.

[0249] In this embodiment of the invention, when a call hold event occurs, the call hold user uses a session modification request to instruct the network and the call hold user to deactivate the DC media, thus preserving the reserved DC media resources. This allows the DC to be maintained even in the call hold service, improving the DC media resource negotiation process.

[0250] Specifically, when a call hold service occurs, there are two ways to notify the DCSF for both the call hold user and the call held user's IMS AS: the first is to directly notify the DCSF of the call hold event, and the second is to notify the DCSF of the media attribute modification event.

[0251] In the first implementation, the call hold event notification to the DCSF in step S51 includes one of the following:

[0252] When the received SDP offer or SDP answer contains a call hold instruction or a DC media attribute modification to deactivation, notify the DCSF to hold the call or deactivate the DC media attribute.

[0253] When the received SDP offer or SDP answer contains a call recovery instruction or the DC media attribute has been modified, notify the DCSF to activate the call recovery or DC media attribute modification.

[0254] When the received SDP offer or SDP answer contains a call recovery instruction or a DC media attribute modification to be active, notify the DCSF to resume call recovery or activate the DC media attribute modification.

[0255] For example, the Session Description Protocol (SDP) offer carries a call hold indication, a call resumption indication, or a modification of DC media attributes (including activation, deactivation, hold, or resumption). The SDP offer is applied to the IMS AS of the call-held user. Similarly, the SDP answer carries a call hold indication, a call resumption indication, or a modification of DC media attributes. The SDP answer is applied to the IMS AS of the call-held user. Taking the IMS AS of the call-held user as an example (the IMS AS of the call-held user uses the same method): When the IMS AS of the call-held user receives the SDP offer, if it parses a call hold indication, it reports the call hold indication to the DCSF of the call-held user (indicating that the call hold event has occurred and the DC needs to be deactivated); if it parses a call resumption indication, it reports the call resumption indication to the DCSF of the call-held user (indicating that the call hold event has ended and the DC needs to be activated).

[0256] Corresponding to the first implementation, step S52, which involves deactivating / activating the DC according to the DCSF's instruction, includes: filtering out all DC media associated with the call holding session according to the DCSF's instruction; and modifying the corresponding session description protocol to provide a deactivation / activation instruction for the associated application data channel ADC.

[0257] Furthermore, the DCSF filters out all DC media associated with the call hold / recovery session based on the call hold / recovery indication reported by the application server, and deactivates / activates the associated ADC and BDC.

[0258] For example, when the DCSF of a call holding user receives a call holding instruction, it sends an instruction to the IMS AS of the call holding user. The IMS AS of the call holding user, based on the instruction from the DCSF, evaluates all DC media associated with the call holding session, selects the SDP associated with the current holding session, and modifies the SDP to deactivate the relevant BDC and ADC. At this time, the BDC and ADC are still held. Similarly, when the DCSF of a call holding user receives a call recovery instruction, it sends an instruction to the IMS AS of the call holding user. The IMS AS of the call holding user, based on the instruction from the DCSF, evaluates all DC media associated with the call holding session, selects the SDP associated with the current holding session, and modifies the SDP to activate the relevant BDC and ADC.

[0259] In the second implementation, the notification of the media attribute modification event to the DCSF in step S51 includes: when the received session description protocol proposal / response carries a DC media attribute deactivation / activation indication, reporting the DC media attribute deactivation / activation indication to the DCSF.

[0260] For example, the Session Description Protocol (SDP) offer carries either a DC media attribute deactivation instruction or a DC media attribute activation instruction, and the SDP offer is applied to the IMS AS of the call-held user. Similarly, the SDP answer carries either a DC media attribute deactivation instruction or a DC media attribute activation instruction, and the SDP answer is applied to the IMS AS of the call-held user. Taking the IMS AS of the call-held user as an example (the IMS AS of the call-held user adopts the same method): When the IMS AS of the call-held user receives the SDP offer, if it parses out the DC media attribute deactivation instruction, it reports the DC media attribute deactivation instruction to the DCSF of the call-held user (indicating that the call-held event has occurred and the DC needs to be deactivated); if it parses out the DC media attribute activation instruction, it reports the DC media attribute activation instruction to the DCSF of the call-held user (indicating that the call-held event has ended and the DC needs to be activated).

[0261] Corresponding to the second implementation, the step S52 of deactivating / activating the DC according to the instruction of the DCSF includes: modifying the session description protocol according to the instruction of the DCSF to deactivate / activate the associated ADC or to deactivate / activate the specified ADC.

[0262] Furthermore, the DCSF filters out all DC media associated with the call keep-alive session based on the DC media attribute deactivation / activation instruction notified by the application server, and deactivates / activates relevant DC media not indicated by the user.

[0263] For example, when the DCSF of the call-holding user receives a DC media attribute deactivation instruction, it sends an instruction to the IMS AS of the call-holding user. The IMS AS of the call-holding user, based on the instruction from the DCSF, determines all DC media associated with the call-holding session and deactivates relevant DCs not indicated by the UE (such as BDCs between the call-holding user / the network of the call-held user and the call-held user, and ADCs between the platform of the call-holding network / the platform of the call-held network and the call-held user). At this time, these specified BDCs and ADCs are still maintained. Similarly, when the DCSF of the call-holding user receives a DC media attribute activation instruction, it sends an instruction to the IMS AS of the call-holding user. The IMS AS of the call-holding user, based on the instruction from the DCSF, determines all DC media associated with the call-holding session and activates relevant DCs not indicated by the UE.

[0264] Specifically, when the Proxy Call Session Control Function (P-CSCF) of the IP Multimedia Subsystem receives a Session Description Protocol (STP) response, it reports the STP response to the Policy Control Function (PCF) / Policy and Charging Rules Function (PCRF) of the IP Multimedia Subsystem. This allows the Policy Control Function or the PPCRF to notify the Policy and Charging Enforcement Function (PCEF) to disable or enable network protocol flows associated with the DC media based on the attributes of the DC media.

[0265] For example, after the P-CSCF of the call-holding user and the call-held user receives the Session Description Protocol (SDP) answer, it will report the SDP answer to its respective PCF / PCRF. At this time, the reported DC media attributes should include the DC flow establishment direction, such as calling user → called network BDC, calling network → called user BDC, etc. The PCF / PCRF, based on the inactive / active attributes of the DC media, notifies the PCEF to disable / enable the DC-related IP flow.

[0266] Compared to existing technologies, the fifth call service processing method disclosed in this invention, in the negotiation process of supplementary services to improve DC media, supports DC holding for call hold services, without the need for additional signaling interaction to rebuild DC, and enables supplementary services to interact with DC to meet service requirements, ensuring the user's supplementary service and DC application experience.

[0267] Example 6

[0268] The sixth call service processing method provided in this embodiment of the invention is applied to the Data Channel Signalling Function (DCSF). See [link / reference]. Figure 7 The sixth call service processing method includes:

[0269] S61. Receive call hold events or media attribute modification events reported by IMS AS;

[0270] S62. Send an instruction to the IMS AS to deactivate, activate, maintain, or restore the DC, or send an instruction to the IMS AS to modify the orientation properties of the DC media.

[0271] Specifically, the method further includes:

[0272] S63. Based on the call hold / recovery instructions reported by IMS AS, filter out all DC media associated with the call hold session;

[0273] S64. Deactivate / activate the associated application data channel ADC; or, deactivate / activate the specified ADC.

[0274] It is worth noting that the working process of the sixth call service processing method described in the embodiments of the present invention can refer to the working process of the fifth call service processing method described in the above embodiments, and will not be repeated here.

[0275] Example 7

[0276] See Figure 8 , Figure 8 This is a structural block diagram of a first type of call service processing device 100 provided in an embodiment of the present invention. The call service processing device 100 is applied to the application server AS of the IP Multimedia Subsystem (IMS) and includes:

[0277] Session event notification module 11 is used to notify session events to the Data Channel Signalling Function (DCSF).

[0278] DC resource reservation module 12 is used to reserve DC resources for IMS DC according to the instructions of DCSF.

[0279] Specifically, the notification of session events to the Data Channel Signalling Function (DCSF) includes one of the following methods:

[0280] Upon receiving a session establishment request from the calling user or the calling network, notify the DCSF of the session establishment request event;

[0281] Upon receiving a call waiting notification from the called user or the called network, notify the DCSF of the call waiting event or media modification event;

[0282] Upon receiving a ringback tone instruction, notify the DCSF of the ringing event;

[0283] When the network decides to prompt the calling user with a call waiting event, it notifies the DCSF of the call waiting event or media modification event.

[0284] Upon receiving a response from the called user, notify the DCSF of the called user's response event or the successful session establishment event;

[0285] Upon receiving a DC establishment request from the Data Channel Application Server (DC AS), the DCSF is notified of the media modification event.

[0286] Specifically, the call service processing device 100 further includes:

[0287] The Session Establishment Request Event Notification Module is used to notify the DC AS of a session establishment request event when it receives a session establishment request from a calling user or calling network.

[0288] Specifically, reserving DC resources for IMS DC according to the instructions of DCSF includes one of the following methods:

[0289] Upon receiving a call waiting notification from the called user or the called network, notify the DC AS of the call waiting event or media modification event;

[0290] Upon receiving a ringback tone instruction, notify the DC AS of the ringing event;

[0291] When the network decides to prompt the calling user with a call waiting event, it notifies the DC AS of the call waiting event or media modification event.

[0292] Upon receiving a response from the called user, notify the DC AS of either a called user response event or a successful session establishment event.

[0293] Specifically, the reporting of call waiting events, media modification events, or ringing events to the DC AS is used to trigger the DCAS to provide call waiting prompts or ringback tones to the calling user through the DC; or, the reporting of call waiting events, media modification events, or ringing events to the DC AS is used to trigger the DC AS to provide ringback tones to the called user through the DC; wherein, the media of the call waiting prompts, ringback tones, or ringback tones is DC media.

[0294] Specifically, the notification of the called party's response event to the DC AS is used to trigger the DC AS to stop providing DC media to the calling or called user.

[0295] It is worth noting that the working process of each module in the call service processing device 100 described in the embodiments of the present invention can refer to the working process of the first call service processing method described in the above embodiments, and will not be repeated here.

[0296] Example 8

[0297] See Figure 9 , Figure 9 This is a structural block diagram of a second type of call service processing device 200 provided in an embodiment of the present invention. The call service processing device 200 is applied to the Data Channel Signalling Function (DCSF) and includes:

[0298] Inspection module 21 is used to receive session events sent by IMS AS and check the user's DC subscription or operator policy;

[0299] IMS DC establishment module 22 is used to establish IMS DC for users based on DC subscription or operator policies.

[0300] Specifically, the IMS DC establishment module 22 is used to: when the called user's DC subscription or operator policy allows the DC application to be provided before the call is connected, instruct the IMS AS to establish a bootstrap data channel (BDC) for the user before the call is connected.

[0301] Specifically, the DC application is used to implement call waiting service, ringback tone service, or ringback vibration service.

[0302] Specifically, the call service processing device 200 further includes:

[0303] The DC application acquisition module is used to push DC applications related to call waiting service, ringback tone service, or ringback tone service to users through BDC; or, users can obtain DC applications related to call waiting service, ringback tone service, or ringback tone service through BDC.

[0304] Specifically, the call service processing device 200 further includes:

[0305] The first instruction sending module is used to send a first instruction to the DC AS upon receiving a call waiting event, a media modification event, or a ringing event; wherein, the first instruction is used to trigger the DC AS to provide a call waiting prompt or a ringback tone to the calling user through the DC, or the first instruction is used to trigger the DC AS to provide a ringback tone to the called user through the DC; wherein, the media of the call waiting prompt, ringback tone, or ringback tone is DC media.

[0306] Specifically, the call service processing device 200 further includes:

[0307] The second instruction sending module is used to send a second instruction to the DC AS upon receiving a called party response event; wherein the second instruction is used to trigger the DC AS to stop providing DC media to the calling or called party.

[0308] It is worth noting that the working process of each module in the call service processing device 200 described in the embodiments of the present invention can refer to the working process of the second call service processing method described in the above embodiments, and will not be repeated here.

[0309] Example 9

[0310] See Figure 10 , Figure 10 This is a structural block diagram of a third type of call service processing device 300 provided in an embodiment of the present invention. The call service processing device 300 is applied to the application server AS of the IP Multimedia Subsystem (IMS) and includes:

[0311] Event notification module 31 is used to notify DCSF of call forwarding events or call setup failure events;

[0312] DC resource release module 32 is used to release the DC resources of IMS DC according to the instructions of DCSF.

[0313] Specifically, the call service processing device 300 further includes:

[0314] The IMS DC media description processing module is used to determine the processing of IMS DC media descriptions.

[0315] Specifically, the process of determining the IMS DC media description includes one of the following methods:

[0316] Transmit the IMS DC media description in the received call setup request;

[0317] Generate a new IMS DC media description, send a call setup request to the call forwarding user or the call forwarding user's network, and carry the IMS DC media description;

[0318] Send a call setup request to the call forwarding user or the call forwarding user's network, and pass through the IMS DC media description in the received call setup request according to the DCSF's instructions, or generate a new IMS DC media description according to the DCSF's instructions.

[0319] As instructed by DCSF, IMS DC media descriptions are not carried.

[0320] Specifically, the call service processing device 300 further includes a call setup request sending module. When the IMS DC media description in the received call setup request is transparently transmitted or a new IMS DC media description is generated, the setup request sending module is used to send a call setup request to the call forwarding user or the call forwarding user's network, carrying the IMS DC media description. When the IMS DC media description is not carried according to the DCSF's instruction, the setup request sending module is used to send a call setup request to the call forwarding user or the call forwarding user's network, without carrying the IMS DC media description.

[0321] Specifically, the IMS DC media description in the received call setup request includes at least one of the following:

[0322] The bootstrap data channel (BDC) between the calling user and the call forwarding user's network;

[0323] The bootstrap data channel (BDC) between the calling network and the call forwarding user.

[0324] It is worth noting that the working process of each module in the call service processing device 300 described in the embodiments of the present invention can refer to the working process of the third call service processing method described in the above embodiments, and will not be repeated here.

[0325] Example 10

[0326] See Figure 11 , Figure 11 This is a structural block diagram of the fourth call service processing device 400 provided in this embodiment of the invention. The call service processing device 400 is applied to the Data Channel Signalling Function (DCSF) and includes:

[0327] Event receiving module 41 is used to receive call forwarding events or call setup failure events notified by IMS AS;

[0328] DC resource release instruction sending module 42 is used to send an instruction to the IMS AS to release the CD resources of the IMS DC.

[0329] Specifically, the call service processing device 400 further includes an IMS DC media description indication module, which is used to indicate at least one of the following information:

[0330] Instruct the IMS AS to describe the IMS DC media in the received call setup request via transparent transmission;

[0331] Instruct IMS AS to generate a new IMS DC media description;

[0332] Instructs IMS AS not to carry IMS DC media description.

[0333] Specifically, the IMS DC media description includes at least one of the following:

[0334] The bootstrap data channel (BCD) between the calling user and the call forwarding network;

[0335] The bootstrap data channel (BCD) between the calling network and the call forwarding user.

[0336] Specifically, the call service processing device 400 further includes a call forwarding processing module, which is used to perform one of the following steps:

[0337] When the called user's DC service subscription includes call forwarding service, determine the called user's call forwarding service logic;

[0338] Whether to allow call forwarding is determined based on call forwarding network capabilities and / or user subscription;

[0339] Determine whether to include an IMS DC media description in the call setup request sent to the call forwarding user or the call forwarding user's network, based on the call forwarding network capabilities and / or the user's subscription.

[0340] It is worth noting that the working process of each module in the call service processing device 400 described in the embodiments of the present invention can refer to the working process of the fourth call service processing method described in the above embodiments, and will not be repeated here.

[0341] Example 11

[0342] See Figure 12 , Figure 12 This is a structural block diagram of the fifth type of call service processing device 500 provided in this embodiment of the invention. The call service processing device 500 is applied to the application server AS of the IP Multimedia Subsystem (IMS) and includes:

[0343] Event notification module 51 is used to notify DCSF of call hold events or media property modification events;

[0344] DC modification module 52 is used to activate, maintain, or restore DC according to the instructions of DCSF, or to modify the orientation properties of DC media according to the instructions of DCSF.

[0345] Specifically, in call hold services, the user initiating the call hold instructs the network or the user whose call is being held to do one of the following through a session modification request and an SDP offer session description protocol proposal:

[0346] DC media deactivation or retention;

[0347] DC media activation or restoration.

[0348] Specifically, in call hold services, the user whose call is held uses the response to the session modification request and the SDPanswer session description protocol response to indicate one of the following to the user who initiated the call hold:

[0349] DC Media has been deactivated or has been maintained;

[0350] DC media is either deactivated or retained;

[0351] DC Media has been activated or restored;

[0352] DC media is activated or restored.

[0353] Specifically, the notification of the call hold event to the DCSF includes the call-held user instructing the user who initiated the call hold to indicate one of the following using a response to a session modification request and an SDP answer session description protocol response:

[0354] DC Media has been deactivated or has been maintained;

[0355] DC media is either deactivated or retained;

[0356] DC Media has been activated or restored;

[0357] DC media is activated or restored.

[0358] Specifically, activating / activating the DC according to the DCSF's instruction includes:

[0359] According to the instructions of DCSF, filter out all DC media associated with the call hold session;

[0360] Modify the corresponding session description protocol to provide deactivation / activation indications for the associated application data channel ADC.

[0361] Specifically, activating / activating the DC according to the DCSF's instruction includes:

[0362] Modify the session description protocol as instructed by DCSF to indicate deactivation / activation of the associated ADC, or to indicate deactivation / activation of a specified ADC.

[0363] It is worth noting that the working process of each module in the call service processing device 500 described in the embodiments of the present invention can refer to the working process of the fifth call service processing method described in the above embodiments, and will not be repeated here.

[0364] Example 12

[0365] See Figure 13 , Figure 13This is a structural block diagram of the sixth call service processing device 600 provided in this embodiment of the invention. The call service processing device 600 is applied to the Data Channel Signalling Function (DCSF) and includes:

[0366] Event receiving module 61 is used to receive call hold events or media attribute modification events reported by IMS AS;

[0367] Instruction sending module 62 is used to send instructions to the IMS AS to deactivate, activate, maintain or restore the DC, or to send instructions to the IMS AS to modify the direction attributes of the DC media.

[0368] Specifically, the call service processing device 600 further includes:

[0369] The DC media filtering module is used to filter out all DC media associated with the call hold-up session based on the call hold-up / recovery instructions reported by the IMS AS.

[0370] The DC processing module is used to deactivate / activate the associated application data channel ADC; or, to deactivate / activate a specified ADC.

[0371] It is worth noting that the working process of each module in the call service processing device 600 described in the embodiments of the present invention can refer to the working process of the sixth call service processing method described in the above embodiments, and will not be repeated here.

[0372] Example 13

[0373] See Figure 14 , Figure 14 This is a structural block diagram of a call service processing device 700 provided in an embodiment of the present invention. The call service processing device 700 includes a processor 71, a memory 72, and a computer program stored in the memory 72 and executable on the processor 71. When the processor 71 executes the computer program, it implements the steps in the above-described call service processing method embodiments, such as steps S11-S12, S21-S22, S31-S32, S41-S42, S51-S52, S61-S62, etc.

[0374] For example, the computer program may be divided into one or more modules / units, which are stored in the memory 72 and executed by the processor 71 to complete the present invention. The one or more modules / units may be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program in the call service processing device 700.

[0375] The call service processing device 700 may include, but is not limited to, a processor 71 and a memory 72. Those skilled in the art will understand that the schematic diagram is merely an example of the call service processing device 700 and does not constitute a limitation on the call service processing device 700. It may include more or fewer components than illustrated, or combine certain components, or different components. For example, the call service processing device 700 may also include input / output devices, network access devices, buses, etc.

[0376] The processor 71 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor. The processor 71 is the control center of the call service processing equipment 700, connecting all parts of the call service processing equipment 700 via various interfaces and lines.

[0377] The memory 72 can be used to store the computer programs and / or modules. The processor 71 implements various functions of the call service processing device 700 by running or executing the computer programs and / or modules stored in the memory 72 and calling the data stored in the memory 72. The memory 72 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the mobile phone (such as audio data, phonebook, etc.). In addition, the memory 72 may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, memory, plug-in hard disk, smart media card (SMC), secure digital card (SD) card, flash card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0378] If the modules / units integrated in the call service processing equipment 700 are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by the processor 71, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc.

[0379] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications are also considered to be within the scope of protection of the present invention.

Claims

1. A call service processing method characterized by comprising: An application server (AS) applied to an IP multimedia subsystem (IMS), the method comprising: informing a data channel signaling function (DCSF) of a session event; reserving DC resources of an IMS data channel (DC) according to an indication of the DCSF.

2. The call service processing method of claim 1, wherein, The informing of the DCSF of the session event comprises one of the following: receiving a session establishment request from a calling user or a calling network, informing the DCSF of a session establishment request event; receiving a call waiting prompt from a called user or a called network, informing the DCSF of a call waiting event or a media modification event; receiving a ring back tone indication, informing the DCSF of a ringing event; when the network decides to prompt the calling user of call waiting, informing the DCSF of a call waiting event or a media modification event; receiving a response of the called user, informing the DCSF of a called response event or a session establishment success event; receiving a DC establishment request from a DC application server (DC AS), informing the DCSF of a media modification event.

3. The call service processing method of claim 2, wherein, Before the receiving of the DC establishment request from the DC AS, the method further comprises: receiving a session establishment request from a calling user or a calling network, informing the DC AS of a session establishment request event.

4. The call service processing method of claim 1, wherein, The reserving of the DC resources of the IMS DC according to the indication of the DCSF comprises one of the following: receiving a call waiting prompt from a called user or a called network, informing the DC AS of a call waiting event or a media modification event; receiving a ring back tone indication, informing the DC AS of a ringing event; when the network decides to prompt the calling user of call waiting, informing the DC AS of a call waiting event or a media modification event; receiving a response of the called user, informing the DC AS of a called response event or a session establishment success event.

5. The call service processing method of claim 4, wherein, The reporting of the call waiting event, the media modification event or the ringing event to the DC AS is used to trigger the DC AS to provide a call waiting prompt or a ring back tone to the calling user through the DC; or, the reporting of the call waiting event, the media modification event or the ringing event to the DC AS is used to trigger the DC AS to provide a ring back tone to the called user through the DC; wherein, the media of the call waiting prompt, the ring back tone or the ring back tone is DC media.

6. The call service processing method of claim 4, wherein, The informing of the DC AS of the called response event is used to trigger the DC AS to stop providing the DC media to the calling user or the called user.

7. A call service processing method characterized by comprising: A method applied to a DCSF, the method comprising: receiving a session event sent by an IMS AS, checking a DC subscription or an operator policy of a user; establishing an IMS DC for the user according to the DC subscription or the operator policy.

8. The call service processing method of claim 7, wherein, The establishing of the IMS DC for the user according to the DC subscription or the operator policy comprises: when the DC subscription or the operator policy of the called user allows a DC application to be provided before call connection, instructing the IMS AS to establish a BDC for the user before the call connection.

9. The call service processing method of claim 8, wherein, The DC application is used to implement a call waiting service, a ring back tone service or a ring back tone service.

10. The call service processing method of claim 8, wherein, After the instructing of the IMS AS to establish the BDC for the user before the call connection, the method further comprises: The DCSF pushes a DC application related to the call waiting service, the color ring service or the color vibration service to the user through the BDC; or the user acquires the DC application related to the call waiting service, the color ring service or the color vibration service through the BDC.

11. The call service processing method of claim 7, wherein, The method further comprises: Upon receiving a call waiting event or a media modification event or a ring event, sending a first indication to the DC AS; wherein the first indication is used to trigger the DC AS to provide a call waiting prompt or a color ring to a calling user through the DC, or the first indication is used to trigger the DC AS to provide a color vibration to a called user through the DC; wherein the media of the call waiting prompt or the color ring or the color vibration is DC media.

12. The call service processing method of claim 7, wherein, The method further comprises: Upon receiving a called answer event, sending a second indication to the DC AS; wherein the second indication is used to trigger the DC AS to stop the DC media to the calling user or the called user.

13. A call service processing method characterized by comprising: An application server AS applied to an IP multimedia subsystem IMS, the method comprising: Notifying a call forwarding event or a call establishment failure event to a DCSF; Releasing DC resources of the IMS DC according to an indication of the DCSF.

14. The call service processing method of claim 13, wherein, After the call forwarding event or the call establishment failure event is notified to the DCSF, the method further comprises: Determining a processing of an IMS DC media description.

15. The call service processing method of claim 14, wherein, The determining of the processing of the IMS DC media description comprises one of the following ways: Transmitting the received IMS DC media description in a call establishment request in a transparent manner; Generating a new IMS DC media description, sending a call establishment request to a call forwarding user or a network of the call forwarding user, and carrying the IMS DC media description; Sending a call establishment request to a call forwarding user or a network of the call forwarding user, transmitting the received IMS DC media description in a call establishment request in a transparent manner according to an indication of the DCSF, or generating a new IMS DC media description according to the indication of the DCSF; Not carrying the IMS DC media description according to an indication of the DCSF.

16. The call service processing method of claim 15, wherein, The method further comprises: When the received IMS DC media description in the call establishment request is transmitted in a transparent manner or the new IMS DC media description is generated, sending a call establishment request to a call forwarding user or a network of the call forwarding user, and carrying the IMS DC media description; When the IMS DC media description is not carried according to an indication of the DCSF, sending a call establishment request to a call forwarding user or a network of the call forwarding user, and not carrying the IMS DC media description.

17. The call processing method of claim 15 or 16, wherein, The transmitting of the received IMS data channel media description in the call establishment request comprises at least one of the following ways: A bootstrap data channel BDC between a calling user and a network of a call forwarding user; A bootstrap data channel BDC between a calling network and a call forwarding user.

18. A call service processing method characterized by comprising: The method applied to the DCSF comprises: Receiving a call forwarding event or a call establishment failure event notified by an IMS AS, Sending an indication to the IMS AS to release DC resources of the IMS DC.

19. The call service processing method of claim 18, wherein, The method further comprises one of the following steps: Indicating the IMS AS to transmit the received IMS DC media description in a call establishment request in a transparent manner; Indicating the IMS AS to generate a new IMS DC media description; Indicating the IMS AS to not carry the IMS DC media description.

20. The call processing method of claim 19 wherein, The IMSDC media description comprises at least one of the following: a BCD between the calling user and the transit network; a BCD between the calling network and the transit user.

21. The call processing method of claim 18 wherein, The method further comprises one of the following steps: determining the transit service logic of the called user when the DC service subscription of the called user comprises a transit service; determining whether to allow the call to transit according to the transit network capability and / or the user subscription; determining whether to carry the IMSDC media description in the call setup request sent to the transit user or the network of the transit user according to the transit network capability and / or the user subscription.

22. A call service processing method characterized by comprising: An application server AS applied to an IP multimedia subsystem IMS, the method comprising: informing the DCSF of a call hold event or a media attribute modification event; deactivating, activating, holding or resuming the DC according to the indication of the DCSF, or modifying the direction attribute of the DC media according to the indication of the DCSF.

23. The call processing method of claim 22 wherein, In the call hold service, the user initiating the call hold indicates to the network or the called user held in the call one of the following through a session modification request and an SDP offer session description protocol proposal: deactivation or holding of the DC media; activation or resumption of the DC media.

24. The call processing method of claim 22 wherein, In the call hold service, the called user held in the call indicates to the user initiating the call hold one of the following through a response to the session modification request and an SDP answer session description protocol response: ​ deactivation or holding of the DC media; deactivation or holding of the DC media; activation or resumption of the DC media; activation or resumption of the DC media.

25. The call processing method of claim 22 wherein, The informing of the DCSF of the call hold event comprises one of the following: when the received SDP offer or SDP answer carries a call hold indication or a DC media attribute modification to deactivation, informing the DCSF of the call hold or the DC media attribute modification to deactivation; when the received SDP offer or SDP answer carries a call resume indication or a DC media attribute modification, informing the DCSF of the call resume or the DC media attribute modification to activation; when the received SDP offer or SDP answer carries a call resume indication or a DC media attribute modification to activation, informing the DCSF of the call resume or the DC media attribute modification to activation.

26. The call processing method of claim 22 wherein, The deactivation / activation of the DC according to the indication of the DCSF comprises: screening all DC media associated with the call hold session according to the indication of the DCSF; modifying the corresponding session description protocol to indicate deactivation / activation of the associated application data channel ADC.

27. The call processing method of claim 22 wherein, The deactivation / activation of the DC according to the indication of the DCSF comprises: modifying the session description protocol to indicate deactivation / activation of the associated ADC or deactivation / activation of the specified ADC according to the indication of the DCSF.

28. A call service processing method characterized by comprising: A data channel signaling function DCSF, the method comprising: receiving a call hold event or a media attribute modification event reported by an IMS AS; sending an indication of deactivation, activation, holding or resumption of the DC to the IMS AS, or sending an indication of modification of the direction attribute of the DC media to the IMS AS.

29. The call processing method of claim 28 wherein, The method further comprises: screening all DC media associated with the call hold session according to the call hold / resume indication reported by the IMS AS; deactivating / activating the associated application data channel ADC, or deactivating / activating the specified ADC.

30. A referral processing apparatus, comprising: An application server AS applied to an IP multimedia subsystem IMS, the device comprising: a session event notification module configured to notify a data channel signaling function DCSF of a session event; a DC resource reservation module configured to reserve DC resources of IMS DC according to an indication of the DCSF.

31. A handover processing apparatus, characterized by comprising: A data channel signaling function DCSF, the device comprising: a checking module configured to check a DC subscription or an operator policy of a user upon receiving a session event sent by an IMS AS; an IMS DC establishment module configured to establish IMS DC for the user according to the DC subscription or the operator policy.

32. A call transfer processing device, characterized in that, An application server AS applied to an IP multimedia subsystem IMS, the device comprising: an event notification module configured to notify a DCSF of a call forwarding event or a call setup failure event; a DC resource release module configured to release DC resources of IMS DC according to an indication of the DCSF.

33. A referral processing apparatus, comprising: A data channel signaling function DCSF, the device comprising: an event receiving module configured to receive a call forwarding event or a call setup failure event notified by an IMS AS; a DC resource release indication sending module configured to send an indication to release DC resources of IMS DC to the IMS AS.

34. A referral processing apparatus, comprising: An application server AS applied to an IP multimedia subsystem IMS, the device comprising: an event notification module configured to notify a DCSF of a call hold event or a media attribute modification event; a DC modification module configured to deactivate, activate, hold or resume DC according to an indication of the DCSF, or to modify a direction attribute of DC media according to an indication of the DCSF.

35. A referral processing apparatus, comprising: A data channel signaling function DCSF, the device comprising: an event receiving module configured to receive a call hold event or a media attribute modification event reported by an IMS AS; an indication sending module configured to send an indication to deactivate, activate, hold or resume DC to the IMS AS, or to send an indication to modify a direction attribute of DC media to the IMS AS.

36. A call service processing apparatus characterized by comprising: A computer program product comprising a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, the processor executing the computer program to implement the call service processing method according to any one of claims 1 to 29.

37. A computer-readable storage medium, characterized in that, The computer readable storage medium comprises a stored computer program, wherein the computer readable storage medium controls a device where the computer readable storage medium is located to execute the call service processing method according to any one of claims 1 to 29 when the computer program runs.

38. A computer program product, characterised in that, The computer program product comprises computer instructions, the computer instructions being executed by a processor to implement the call service processing method according to any one of claims 1 to 29.

Images