WO2023160715A1 - 一种执行呼叫相关业务的方法、装置及系统 - Google Patents

一种执行呼叫相关业务的方法、装置及系统 Download PDF

Info

Publication number
WO2023160715A1
WO2023160715A1 PCT/CN2023/078561 CN2023078561W WO2023160715A1 WO 2023160715 A1 WO2023160715 A1 WO 2023160715A1 CN 2023078561 W CN2023078561 W CN 2023078561W WO 2023160715 A1 WO2023160715 A1 WO 2023160715A1
Authority
WO
WIPO (PCT)
Prior art keywords
call
instruction
application server
control instruction
call control
Prior art date
Application number
PCT/CN2023/078561
Other languages
English (en)
French (fr)
Inventor
柳亮亮
林霖
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023160715A1 publication Critical patent/WO2023160715A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1046—Call controllers; Call servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers

Definitions

  • the present application relates to the technical field of communications, and in particular to a method, device and system for executing call-related services.
  • IP Multimedia Subsystem IP Multimedia Subsystem
  • Application Server is the device of the application layer in the IMS system.
  • the IMS system usually includes multiple ASs to provide services such as basic services, supplementary services, multimedia conferences, and integrated communications.
  • the service provided by an AS is called AS service.
  • the IMS system includes Multimedia Telephony (MultiMediaTelephony, MMTel) AS, color ring back tone AS, and smart AS.
  • MMTel Multimedia Telephony
  • AS service that the smart AS can provide to the user includes a prepaid reminder service.
  • the AS and the call session control function (Call Session Control Function, CSCF) network element can interact through the session initiation protocol (Session initialization Protocol, SIP) protocol, and then realize the triggering and execution of various network services.
  • SIP Session initialization Protocol
  • AS services include order-sensitive services, also called non-independent AS services or dependent AS services. Specifically, it means that the generation of the call control instruction corresponding to the AS service depends on the call control instruction generated by another AS service. some or all of the information.
  • a user purchases a small number service and a prepaid reminder service.
  • the prepaid reminder service can give voice prompts according to the balance of the user number to control the user's call service.
  • the small number service means that the user can apply for a primary In addition to the number, apply for an additional auxiliary number (also called a small number).
  • the main number and the small number share a Subscriber Identification Module (SIM).
  • SIM Subscriber Identification Module
  • the main number and the small number are regarded as the same User's number. If the small number and the main number are billed separately, the voice prompts generated by the prepaid reminder service are generally different, and the prepaid reminder service is considered to be a dependent AS service.
  • the current AS service parallel triggering mechanism enables call control commands of multiple AS services to be generated or even executed in parallel, so that an AS cannot generate its own call control commands based on call control commands generated by other ASs.
  • the CSCF network element receives the user number change instruction sent by the small AS, which is used to instruct to change the calling number corresponding to the call service to a small number; the CSCF network element also receives the announcement instruction sent by the smart AS (that is, for A call control instruction that instructs the CSCF to play audio content to the user equipment) is used to instruct the calling user to play the prepaid prompt tone corresponding to the main number.
  • the CSCF network element executes the call control command in parallel, that is, executes the number change and plays the prepaid prompt tone corresponding to the main number at the same time.
  • the CSCF network element should play the prepaid prompt tone corresponding to the small number to the calling user instead of the prepaid prompt tone corresponding to the main number, which affects the user experience. .
  • the present application provides a method, device and system for executing call-related services, which reduce the impact of the AS service parallel trigger mechanism on user experience.
  • a method for executing call-related services is provided, which is applied to a call service enabling entity.
  • the method includes: sending call events to a first application server and a second application server in parallel; receiving from the first application server The first call control instruction and the second call control instruction are received from the second application server; the third call control instruction is received from the first application server, and the third call control instruction is used to replace the first call control instruction; and the second call control instruction is executed in parallel. a call control instruction and a third call control instruction.
  • the call service enabling entity can refresh the AS service status by receiving updated call control instructions from the dependent AS service side, reducing the impact of the AS service parallel trigger mechanism on user experience. Influence.
  • the second call control instruction includes associated factor change information
  • the associated factor change information is used to indicate that at least one associated factor of the call service has changed
  • the at least one associated factor is the first application Factors upon which the server determines call control commands.
  • the call service enabling entity can recognize the association with the relying party (the first application server) through the indication that the association factor carried in the call control command sent by the dependent party AS (the second application server) changes. If the factors match, it can report to the relying party AS the instruction update instruction information indicating the change of the correlation factor, thereby triggering the relying party AS to resend a new call control command according to the change of the correlation factor to refresh the service status of the AS, thereby reducing the AS The impact of service parallel trigger mechanism on user experience.
  • the correlation factor includes a parameter corresponding to the call service, and/or a state of the call service.
  • the relevant factors that the relying party is interested in may include a certain parameter corresponding to the call service and/or the running status of the call service, etc.
  • the change of the associated factors in the call control command triggers the relying party AS to resend the call control command, so as to meet the needs of users with dependent AS services and reduce the impact of the AS service parallel trigger mechanism on user experience.
  • the method before sending the call event to the first application server and the second application server in parallel, the method further includes: acquiring at least one correlation factor corresponding to the first application server.
  • the call service enabling entity can perceive in advance the correlation factor that the first application server is interested in, and the correlation factor is one of the inputs used by the first application server to determine the call control instruction, so that the call service enabling entity
  • the functional entity can determine whether to trigger or when to trigger the first application server to resend the call control command according to the associated factors perceived in advance by the first application server.
  • the impact of the AS service parallel trigger mechanism is reduced Impact on user experience.
  • acquiring at least one association factor corresponding to the first application server specifically includes: receiving a subscription request from the first application server, where the subscription request includes at least one association factor corresponding to the first application server, the The subscription request is used to request to subscribe to changes of at least one correlation factor that the first application server is interested in.
  • the call service enabling entity can receive the relevant correlation factors reported by the first application server, so that the call service enabling entity can determine whether it needs to Trigger or when to trigger the first application server to resend the call control command, improve the parallel trigger mechanism of AS services, and realize the service requirements for dependent AS services.
  • the method before receiving the third call control instruction from the first application server, the method further includes: sending instruction update instruction information to the first application server according to the change information of the association factor, so that The instruction update instruction information is used to instruct the first application server to resend the call control instruction.
  • the instruction update instruction information includes change information of associated factors or at least one associated factor.
  • the instruction update indication information sent by the call service enabling entity to the first application server may carry the association factor change information, or carry at least one association factor indicated in the association factor change information, thereby instructing the first application server to change The association factor, so that the first application server can resend a new call control command according to the change of the association factor, so as to refresh the service state of the AS, and reduce the impact of the AS service parallel trigger mechanism on the user experience.
  • sending an instruction to update the instruction information to the first application server according to the change information of the correlation factor specifically includes: querying the correlation factor corresponding to the first application server according to the change information of the correlation factor, if the correlation factor If the correlation factor indicated in the change information matches the correlation factor corresponding to the first application server, an instruction to update the instruction information is sent to the first application server.
  • the call service enabling entity can determine whether the correlation factor corresponding to the pre-perceived first application server matches the correlation factor in the correlation factor change information, so as to send an instruction to the first application server to update the indication information, thereby reducing AS The impact of service parallel trigger mechanism on user experience.
  • the change information of the associated factor includes a change in the first parameter corresponding to the call service
  • the information about the change of the associated factor includes a changed value of the first parameter
  • the relevant factor may specifically be a parameter corresponding to the call service, such as the first parameter.
  • the relevant factor change information may also include the first parameter change. The latter value indicates that the call service enabling entity can trigger the first application server to resend the call control instruction, thereby reducing the impact of the AS service parallel trigger mechanism on user experience.
  • the instruction update instruction information includes a change in the first parameter corresponding to the call service, the instruction update instruction information includes a changed value of the first parameter.
  • the instruction update instruction information is used to indicate that the first parameter has changed, and the instruction update instruction information includes the changed value of the first parameter, so as to indicate that the first application server can The value resends the call control command, thereby reducing the impact of the AS service parallel trigger mechanism on user experience.
  • the third call control instruction is generated by the first application server according to a changed value of the first parameter.
  • the first application server can update the changed value of the first parameter included in the indication information according to the instruction, so as to resend the call control instruction according to the changed value of the first parameter, thereby reducing the impact of the AS service parallel trigger mechanism on the user experience. Impact.
  • the subscription request further includes a user identity.
  • the call service enabling entity is deployed on a call session control function (CSCF) network element or a unified control function (UCF) network element.
  • CSCF call session control function
  • UPF unified control function
  • the method before sending the call event to the first application server and the second application server in parallel, the method further includes: generating the call event based on a call session message of the terminal device.
  • a method for executing call-related services is provided, which is applied to a first application server, and the method includes: receiving a call event from a call service enabling entity; sending a first call control to the call service enabling entity according to the call event Instruction: sending a third call control instruction to the call service enabling entity, where the third call control instruction is used to replace the first call control instruction.
  • the method before sending the third call control instruction to the call service enabling entity, the method further includes: receiving association factor change information from the call service enabling entity, the association factor change information It is used to indicate that at least one associated factor of the call service changes, and the at least one associated factor is a factor on which the application server determines the call control instruction; and the third call control instruction is generated based on the associated factor change information.
  • the associated factors include parameters corresponding to the call service, and/or the state of the call service.
  • the method before receiving the call event from the call service enabling entity, the method further includes: sending at least one correlation factor corresponding to the application server to the call service enabling entity.
  • the method before sending the third call control instruction to the call service enabling entity, the method further includes: receiving instruction update instruction information from the call service enabling entity, the instruction update instruction The information is used to instruct the application server to resend the call control instruction.
  • the instruction update instruction information includes change information of associated factors or at least one associated factor.
  • the instruction update instruction information includes a change in the first parameter corresponding to the call service, the instruction update instruction information includes a changed value of the first parameter.
  • the third call control instruction is generated by the application server according to a changed value of the first parameter.
  • the call service enabling entity is deployed on a call session control function (CSCF) network element or a unified control function (UCF) network element.
  • CSCF call session control function
  • UPF unified control function
  • a communication device which includes: a sending module, configured to send a call event to a first application server and a second application server in parallel; a receiving module, configured to receive a first call control from the first application server instruction and receive the second call control instruction from the second application server; the receiving module is also used to receive the third call control instruction from the first application server, and the third call control instruction is used to replace the first call control instruction; the processing module uses to execute the second call control instruction and the third call control instruction in parallel.
  • the second call control instruction includes associated factor change information
  • the associated factor change information is used to indicate that at least one associated factor of the call service has changed
  • the at least one associated factor is the first application Factors upon which the server determines call control commands.
  • the correlation factor includes a parameter corresponding to the call service, and/or a state of the call service.
  • the receiving module is further configured to acquire the at least one association factor corresponding to the first application server.
  • the sending module is further configured to send instruction update instruction information to the first application server according to the change information of the association factor, and the instruction update instruction information is used to instruct the first application server Resend the call control command.
  • the instruction update indication information includes the change information of the associated factor or the at least one associated factor.
  • the processing module is further configured to query the association factor corresponding to the first application server according to the association factor change information, if the association factor indicated in the association factor change information is the same as the first application server If the association factors corresponding to the application servers match, the sending module is configured to send instruction update instruction information to the first application server.
  • the change information of the associated factor includes a change in the first parameter corresponding to the call service
  • the information about the change of the associated factor includes a changed value of the first parameter
  • the instruction update instruction information includes a change in the first parameter corresponding to the call service, the instruction update instruction information includes a changed value of the first parameter.
  • the third call control instruction is generated by the first application server according to a changed value of the first parameter.
  • the device is deployed on a call session control function (CSCF) network element or a unified control function (UCF) network element.
  • CSCF call session control function
  • UPF unified control function
  • the processing module is further configured to generate the call event based on a call session message of the terminal device.
  • a communication device which includes: a receiving module, configured to receive a call event from the call service enabling entity; a sending module, configured to send the call event to the call service enabling entity according to the call event Sending a first call control instruction; the sending module is further configured to send a third call control instruction to the call service enabling entity, where the third call control instruction is used to replace the first call control instruction.
  • the receiving module is further configured to receive association factor change information from the call service enabling entity, where the association factor change information is used to indicate that at least one association factor of the call service changes, and the at least one The correlation factor is the factor on which the application server determines the call control instruction.
  • the correlation factor includes a parameter corresponding to the call service, and/or a state of the call service.
  • the sending module is further configured to send the at least one association factor corresponding to the device to the call service enabling entity.
  • the method before sending the third call control instruction to the call service enabling entity, the method further includes: receiving instruction update instruction information from the call service enabling entity, the instruction update instruction The information is used to instruct the application server to resend the call control instruction.
  • the instruction update indication information includes the change information of the associated factor or the at least one associated factor.
  • the instruction update instruction information includes a change in the first parameter corresponding to the call service, the instruction update instruction information includes a changed value of the first parameter.
  • the third call control instruction is generated by the device according to a changed value of the first parameter.
  • the call service enabling entity is deployed in a call session control function (CSCF) network element or a unified control function (UCF) network element.
  • CSCF call session control function
  • UPF unified control function
  • a communication device includes: a processor; the processor is configured to be coupled with a memory, and after reading an instruction in the memory, execute the method according to the above first aspect according to the instruction.
  • the communication device may be the call service enabling entity in the above first aspect, or a device including the above call service enabling entity.
  • the communications device further includes a memory, where the memory is configured to store necessary program instructions and data.
  • a communication device includes: a processor; the processor is configured to be coupled with a memory, and after reading an instruction in the memory, execute the method according to the above second aspect according to the instruction.
  • the communication device may be the application server in the above second aspect, or a device including the above application server.
  • the communications device further includes a memory, where the memory is configured to store necessary program instructions and data.
  • a communication device in a seventh aspect, includes: a processor and an interface circuit; the interface circuit is used to receive a computer program or instruction and transmit it to the processor; the processor is used to execute the computer program or instruction, so that The communication device executes the method described in the first aspect above.
  • a communication device in an eighth aspect, includes: a processor and an interface circuit; the interface circuit is used to receive a computer program or instruction and transmit it to the processor; the processor is used to execute the computer program or instruction, so that The communication device executes the method described in the second aspect above.
  • the embodiments of the present application provide a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, the computer can execute the method described in the first aspect above.
  • the embodiments of the present application provide a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, the computer can execute the method described in the second aspect above.
  • the embodiment of the present application provides a computer program product containing instructions, which when run on a computer, enables the computer to execute the method described in the first aspect above.
  • the embodiment of the present application provides a computer program product including instructions, which, when run on a computer, enable the computer to execute the method described in the second aspect above.
  • an embodiment of the present application provides a communication system, where the communication system includes the communication device according to any one of the third aspect and the fourth aspect.
  • the technical effect brought by any possible implementation manner in the second aspect to the thirteenth aspect may refer to the technical effect brought by different possible implementation manners in the above-mentioned first aspect, which will not be repeated here.
  • FIG. 1 is an architecture diagram of a communication system provided by an embodiment of the present application
  • FIG. 2 is an architecture diagram of another communication system provided by an embodiment of the present application.
  • FIG. 3 is a schematic flow diagram of AS service triggering provided by an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a communication device provided in an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a method for executing call-related services provided by an embodiment of the present application
  • FIG. 6 is a schematic flow diagram of a collaborative processing of multiple AS services provided by an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the embodiment of the present application may be applied to an IMS network.
  • the IMS network refers to an IP-based multimedia subsystem, which is a network that provides users with various multimedia services based on IP bearer.
  • FIG. 1 is a schematic diagram of a communication system architecture of an IMS network.
  • the IMS network includes Serving Call Session Control Function (Serving Call Session Control Function, S-CSCF) network elements and multiple application servers AS, such as AS1, AS2 and AS3.
  • S-CSCF Serving Call Session Control Function
  • AS application servers
  • AS such as AS1, AS2 and AS3.
  • the S-CSCF network element performs routing management on the calling side and the called side of the user, and performs AS triggering according to the user's subscription data to realize various AS service functions.
  • the CSCF network element is the core network element, which is mainly responsible for handling the signaling control during the multimedia call session. For example, manage user authentication of IMS network, cooperate with other network entities to control SIP session, service negotiation and resource allocation, etc. Each AS can interact with CSCF network elements through the SIP protocol, thereby realizing the triggering and execution of various network services.
  • CSCF network elements can be divided into: proxy CSCF (Proxy CSCF, P-CSCF) network elements, query CSCF (Interrogating CSCF, I-CSCF) network elements, serving CSCF (Serving CSCF S-CSCF) network elements elements and emergency CSCF (Emergency CSCF, E-CSCF) network elements, etc.
  • proxy CSCF Proxy CSCF, P-CSCF
  • query CSCF Interrogating CSCF, I-CSCF
  • serving CSCF Serving CSCF S-CSCF
  • emergency CSCF Emergency CSCF
  • the call service may refer to a voice call service or a video call service performed between a user equipment (UE) participating in a calling identity or a called identity and connecting with other UEs via a communication network.
  • UE user equipment
  • the call service can be a voice call service or a video call service performed by the UE dialing a mobile phone number, a landline number or a customer service center number; or, the call service can be a real time communication (RTC ) is a voice call service or a video call service for calling other UEs.
  • RTC real time communication
  • the call service can be a voice call service or a video call service for the UE to receive a call from a mobile phone, landline or customer service center; or, the call service can be performed when the UE receives calls from other UEs through the RTC application voice call service or video call service.
  • the calling service may also be referred to as calling service for short.
  • the application server AS is a network element in the IMS network that provides users with various specific multimedia services.
  • the IMS network usually includes multiple ASs for providing various services.
  • the IMS network may include a Multimedia Telephony (MultiMediaTelephony, MMTEL) AS for providing basic multimedia telephony services and supplementary services, a Multimedia Ring Back Tone (Multimedia Ring Back Tone, MRBT) AS for providing users with color ring back tone services, and Various other third-party AS, etc.
  • MMTEL Multimedia Telephony
  • MMTEL Multimedia Ring Back Tone
  • MRBT Multimedia Ring Back Tone
  • MRBT Multimedia Ring Back Tone
  • the IMS network may further include a call service enabler function (Call Service Enabler Functions, CSEF) entity or a service enabler function (Service Enabler Functions, SEF) entity.
  • CSEF Call Service Enabler Functions
  • SEF Service Enabler Functions
  • the CSEF/SEF entity can be independently deployed in the IMS network, or deployed in the S-CSCF network element, as shown in Figure 1, this application Please do not make specific restrictions on this.
  • the IMS network may further include a Home Subscriber Server (Home Subscriber Server, HSS).
  • HSS contains user profiles, which can be used to perform user authentication and authorization.
  • the HSS supports the main user database of the IMS network entities for handling calls or call sessions.
  • the method for executing call-related services provided by this application can also be applied to other communication systems, such as new audio and video architecture, or light IMS (Lite IMS) system, etc.
  • the communication system may at least include a unified control function (Unified Control Functions, UCF) network element shown in the left diagram of FIG. 2, and a service and application function (Service and Application Functions , SAF) network element.
  • UCF Unified Control Functions
  • SAF Service and Application Functions
  • the function of the SAF network element may refer to the function realized by the application server AS in FIG. 1
  • the function of the UCF network element may refer to the function realized by the S-CSCF network element in FIG. 1
  • the UCF network element may also include the aforementioned CSEF entity, which is used to implement the functions implemented by the CSEF entity in the embodiment of the present application.
  • the communication system may also include a Service Enabler Function (Service Enabler Functions, SEF) entity.
  • SEF Service Enabler Functions
  • the SEF entity can be deployed independently, and the functions of the SEF entity can refer to the functions realized by the S-CSCF network element in Figure 1, and the functions realized by the CSEF entity in the embodiment of this application; the UCF network element can be used to realize the aforementioned Functions of I-CSCF or P-CSCF network elements among CSCF network elements in the IMS system.
  • the above-mentioned communication system can trigger AS services in parallel.
  • the CSEF entity can send the same call event to multiple application servers in parallel, and multiple application servers can send call control commands to the CSEF entity in parallel, and the CSEF entity will receive multiple After the call control commands are merged, multiple call control commands are executed in parallel, and the mutually exclusive commands included in them are executed one by one or sequentially, so as to trigger AS services in parallel.
  • the CSEF entity combines the received multiple call control instructions, which means that the CSEF entity does not execute immediately after receiving a call control instruction, but caches or saves it until it receives a preset number of calls.
  • the CSEF entity executes multiple call control instructions in parallel, which means that the CSEF entity does not execute these call control instructions sequentially, but executes these call control instructions at the same time or almost simultaneously, that is, it does not need to wait for the first call control instruction after executing the first call control instruction. After the instruction is executed, the second call control instruction is executed.
  • the processing flow of parallel triggering of AS services by the CSEF entity mainly includes the following steps.
  • Step 301 The CSEF entity sends the call event to multiple ASs in parallel.
  • a call event refers to an event related to a call service.
  • the CSEF entity can notify the AS of various notification messages received during the call service process through the data format of "event". For example, for a ring notification (Ring) received during a call service, the corresponding CSEF entity sends a "ring event" to the AS; for an off-hook notification (Answer) received during a call service, the CSEF entity sends an "off-hook event" to the AS. machine incident”.
  • the CSEF entity provides a service-oriented application programming interface (Application Programming Interface, API) for the AS to call, so as to cooperate with the AS to realize various AS services.
  • API Application Programming Interface
  • the CSEF entity includes the call event subscription API, which is called by the AS, and the AS calls the call event subscription API.
  • the call event subscription API that is, sending a call event subscription request
  • the address of the AS itself can be sent to the CSEF entity as the notification address.
  • the CSEF entity can send the call event to the corresponding AS according to the subscription request and notification address of the previous AS.
  • Call Event may be an enumeration value, listing call events that may notify the AS.
  • parallel sending here refers to sending the same call event to each AS together, that is, after sending a call event to the first AS, there is no need to wait for the call event from the first AS to be received. Instead, the call event may be sent to the second AS, the third AS, . . . Exemplarily, after the CSEF entity sends the call event to AS1, it does not need to wait for a response message from AS1, and then sends the call event to AS2, AS3 and so on.
  • Step 302 the AS receives the call event, generates a call control instruction according to the call event and AS service logic, and sends the call control instruction to the CSEF entity.
  • each call control instruction is used to instruct the CSEF entity to perform an operation related to a call service, for example, an operation related to a call service of a certain user.
  • the operations related to the call service refer to the operations that need to be performed by the CSEF entity based on the service logic of the AS in order to realize the call service or enhance the call service.
  • the call control instruction sent by the CRBT AS to the CSEF entity may be "play the CRBT audio set by the called user to the calling user equipment", which is used to instruct the CSEF entity to perform the playback operation (for example, trigger the Media Resource Function (Media Resource Function) , MRF) entity executes the playback operation).
  • the call control instruction sent by the small AS to the CSEF entity may be "change the calling party number to a small number, such as 123123", which is used to indicate the calling party number that the CSEF entity will display on the called user equipment.
  • the call control command sent to the CSEF entity by the intelligent AS with the prepaid reminder function may be "remind the user to pay", which is used to instruct the CSEF entity to play the audio content corresponding to the payment reminder to the corresponding user equipment.
  • each AS can process the same call event in parallel, that is, each AS processes the call event immediately after receiving it, and is in a parallel state.
  • the AS obtains the call control instruction corresponding to the call event according to its own business logic.
  • Step 303 The CSEF entity executes the received multiple call control instructions in parallel.
  • the CSEF entity receives the call control commands sent by the AS one by one, until it receives multiple call control commands corresponding to the preset number of ASs that subscribe to the call event, then merges and processes multiple call control commands, and identifies the call control commands among the multiple call control commands. Whether there is a mutex indication.
  • the mutually exclusive instruction indicates that there is a service conflict in AS services corresponding to at least two call control instructions. That is to say, for two or more call control commands received in parallel, the CSEF entity cannot execute them in parallel without awareness.
  • the CRBT playback command sent by the CRBT AS and the playback command of the Call Waiting (CW) prompt tone sent by the Multimedia Telephony (MMTEL) AS that provides basic services and supplementary services for multimedia telephony, etc.
  • MMTEL Multimedia Telephony
  • the CSEF entity if the CSEF entity recognizes that there are no mutually exclusive instructions in the multiple call control instructions, the CSEF entity executes the multiple call control instructions in parallel; if the multiple call control instructions include mutually exclusive instructions, such as If at least two mutually exclusive call control instructions are included, the CSEF entity chooses to execute one of the call control instructions in the mutually exclusive instructions, or sequentially executes multiple call control instructions in the mutually exclusive instructions. Among them, the alternative execution is It means that the CSEF entity selects one call control instruction in the mutually exclusive instructions to execute, and discards other call control instructions in the mutually exclusive instructions.
  • the small AS is used to realize the small number service
  • the smart AS is used to realize the prepaid reminder service.
  • the prepaid reminder service of the smart AS can control the user's call service according to the user's tariff status and balance.
  • the smart AS will first calculate the call cost and decide whether to accept or reject the call according to the balance of the prepaid account.
  • the smart AS will play the corresponding voice prompt based on the calling user's number. If the same user corresponds to multiple different numbers, the voice prompts generated by the smart AS based on different numbers are generally different. Therefore, compared to the small number service, the prepaid reminder service is an AS service dependent on the small number service.
  • the prepaid reminder service of the smart AS corresponds to the playback command Generated, it needs to rely on the call control command generated by the small AS to change the user number.
  • the announcement instruction corresponding to the prepaid reminder service is a voice reminder corresponding to the call charge balance of the main number; if The smart AS generates a playback instruction based on the call control instruction for changing the user number generated by the small AS, and the playback instruction corresponding to the prepaid reminder service is a voice reminder corresponding to the phone charge balance of the small number.
  • an AS cannot generate its own call control commands based on the call control commands generated by other ASs, which may affect user experience in some cases;
  • the call control instruction of the user number generates an announcement instruction, and as a result, the announcement instruction corresponding to the prepaid reminder service is a voice reminder corresponding to the call charge balance of the main number, causing the user to confuse the balance of his two accounts; therefore, the existing
  • the parallel triggering mechanism of AS services is in conflict with user experience requirements for dependent AS services, resulting in poor user experience.
  • the present application provides a method, device and system for executing call-related services, which can be applied to communication systems as shown in FIG. 1 and FIG. 2 .
  • the communication system shown in FIG. 1 or FIG. 2 is only used as an example, and is not used to limit the technical solution of the present application.
  • the communication system shown in Figure 1 or Figure 2 may also include other devices, and the number of network elements shown in Figure 1 may also be determined according to specific needs. There are no restrictions on this.
  • each device in FIG. 1 or FIG. 2 in this embodiment of the present application may be a general-purpose device or a special-purpose device, which is not specifically limited in this embodiment of the present application.
  • each device in Figure 1 or Figure 2 in the embodiment of the present application can be realized by one device, or by multiple devices, or by one or more functional modules in one device , which is not specifically limited in this embodiment of the present application. It can be understood that the above functions can be elements in hardware devices, software functions running on dedicated hardware, or a combination of hardware and software, or virtualization functions instantiated on a platform (for example, a cloud platform) .
  • each device in FIG. 1 or FIG. 2 may adopt the composition structure shown in FIG. 4 , or include components shown in FIG. 4 .
  • FIG. 4 is a schematic diagram of a hardware structure of a device applicable to this embodiment of the present application.
  • the device 40 includes at least one processor 401 and at least one communication interface 404, configured to implement the method provided in the embodiment of the present application.
  • the device 40 may also include a communication link 402 and a memory 403 .
  • the processor 401 can be a general central processing unit (central processing unit, CPU), a microprocessor, Application-specific integrated circuit (application-specific integrated circuit, ASIC), or one or more integrated circuits used to control the program execution of the solution of this application.
  • CPU central processing unit
  • ASIC Application-specific integrated circuit
  • Communication line 402 may include a path, such as a bus, for transferring information between the aforementioned components.
  • the communication interface 404 is used for communicating with other devices or communication networks.
  • the communication interface 404 can be any device such as a transceiver, such as an Ethernet interface, a wireless access network (radio access network, RAN) interface, a wireless local area network (wireless local area networks, WLAN) interface, a transceiver, a pin , bus, or transceiver circuits, etc.
  • a transceiver such as an Ethernet interface, a wireless access network (radio access network, RAN) interface, a wireless local area network (wireless local area networks, WLAN) interface, a transceiver, a pin , bus, or transceiver circuits, etc.
  • Memory 403 may be read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and instructions, random access memory (random access memory, RAM) or other types that can store information and instructions It can also be an electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be programmed by a computer Any other medium accessed, but not limited to.
  • the memory may exist independently and be coupled with the processor 401 through the communication line 402 .
  • the memory 403 can also be integrated with the processor 401 .
  • the memory provided by the embodiment of the present application may generally be non-volatile.
  • the memory 403 is used to store computer-executed instructions involved in executing the solutions provided by the embodiments of the present application, and the execution is controlled by the processor 401 .
  • the processor 401 is configured to execute computer-executed instructions stored in the memory 403, so as to implement the method provided in the embodiment of the present application.
  • the processor 401 may also perform processing-related functions in the methods provided in the following embodiments of the application, and the communication interface 404 is responsible for communicating with other devices or communication networks. The example does not specifically limit this.
  • the computer-executed instructions in the embodiments of the present application may also be referred to as application program codes, which is not specifically limited in the embodiments of the present application.
  • the coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 4 .
  • device 40 may include multiple processors, for example, processor 401 and processor 407 in FIG. 4 .
  • processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the device 40 may further include an output device 405 and/or an input device 406 .
  • An output device 405 is coupled to the processor 401 and can display information in a variety of ways.
  • the output device 405 can be a liquid crystal display (liquid crystal display, LCD), a light emitting diode (light emitting diode, LED) display device, a cathode ray tube (cathode ray tube, CRT) display device, or a projector (projector) wait.
  • the input device 406 is coupled to the processor 401 and can receive user input in various ways.
  • the input device 406 may be a mouse, a keyboard, a touch screen device, or a sensing device, among others.
  • composition structure shown in Figure 4 does not constitute a limitation to the device, except for the components shown in Figure 4 Additionally, the device may include more or fewer components than shown, or combine certain components, or have a different arrangement of components.
  • a and/or B can mean: A exists alone, A and B exist simultaneously, and There are three cases of B, where A and B can be singular or plural.
  • expressions like "at least one of A, B, and C" or "at least one of A, B, or C” are generally used to mean any of the following: A alone; B alone; C exists; A and B exist together; A and C exist simultaneously; B and C exist simultaneously; A, B, and C exist simultaneously.
  • the above is an example of the three elements of A, B and C to illustrate the optional items of the item.
  • words such as “first” and “second” may be used to distinguish technical features with the same or similar functions.
  • the words “first” and “second” do not limit the number and execution order, and the words “first” and “second” do not necessarily mean that they must be different.
  • words such as “exemplary” or “for example” are used to represent examples, illustrations or illustrations, and any embodiment or design described as “exemplary” or “for example” should not be interpreted It is more preferred or more advantageous than other embodiments or design solutions.
  • the use of words such as “exemplary” or “for example” is intended to present related concepts in a specific manner for easy understanding.
  • This application provides a method for executing call-related services, which can be applied to S-CSCF network elements, or applied to Call Service Enabler Functions (Call Service Enabler Functions, CSEF) entities or Service Enabler Functions (Service Enabler Functions, SEF) )entity.
  • CSEF Call Service Enabler Functions
  • SEF Service Enabler Functions
  • the CSEF/SEF entity may be independently deployed in the communication system, or may be deployed in the S-CSCF network element, which is not specifically limited in this application.
  • call service enabling entity CSEF entity is used as an example for illustration, but the executed methods can be applied to S-CSCF network elements, SEF entities and so on.
  • Step 501 The CSEF entity sends the call event to the first AS and the second AS in parallel.
  • the CSEF entity after the CSEF entity sends the call event to the first AS, it can then send the call event to the second AS without waiting for the response message from the first AS to be sent to the second AS.
  • the relevant description of the CSEF entity sending the call event to multiple ASs in parallel can refer to the aforementioned step 301 , which will not be repeated here.
  • the method may further include: when the user's call service occurs, the CSEF entity may acquire the call event, or the CSEF entity may obtain the call event based on the call event of the terminal device.
  • Session messages generate call events. That is, CSEF entities can call based on user Various conversation messages in the business generate corresponding call events.
  • the call event may include an initial call event, a notification ringing event Ring, an off-hook event Answer or a release event Release, and the like.
  • the CSEF entity may obtain call events from the CSCF network element, and the call event may be generated by the CSCF network element according to various session messages in the user's call service.
  • the CSEF entity may generate corresponding call events based on various session messages in the user call service.
  • the method may further include:
  • the CSEF entity receives user identities from the multiple ASs and call event subscription information corresponding to the users.
  • the AS can report to the CSEF entity the user identity corresponding to the user subscribing to the AS service and the call event subscription information corresponding to the user through the subscription mechanism.
  • the user identity can be user The identification number of the Subscriber Identification Module (SIM).
  • SIM Subscriber Identification Module
  • the call event subscription information may include the subscription information of the initial call event, and the initial call event may be used as mandatory reporting information, and other call events such as ringing event or off-hook event may be used as optional reporting information. Therefore, during the triggering process of the user's call service, when a specific call event occurs, the CSEF entity can send the specific call event of the specific user to the AS according to the subscription information reported by the previous AS.
  • the call event may also include a subscription type notification event Subscribe, an unsubscribe event UnSubscribe, and the like.
  • each AS that receives the call event can generate a corresponding call control instruction based on the call event according to the service logic of the AS itself, see step 502 and step 503 for details.
  • Step 502 The first AS generates a first call control instruction according to the call event and AS service logic, and sends the first call control instruction to the CSEF entity.
  • the first AS can generate an announcement instruction based on the received ringing call event and based on the CRBT service logic, and send the announcement instruction to the CSEF entity, so
  • the play instruction is used to instruct the CSEF entity to play the CRBT content corresponding to the calling user to the called UE.
  • the CSEF entity may trigger the MRF entity to play the CRBT content corresponding to the calling user to the called UE.
  • Step 503 The second AS generates a second call control instruction according to the call event and the AS service logic, and sends the second call control instruction to the CSEF entity; optionally, the second call control instruction includes the change information of the associated factors.
  • Both of the above two call control instructions are used to instruct the CSEF entity to perform different operations related to call services, specifically operations related to the user's call services.
  • the operation related to the call service refers to the relevant operation performed by the CSEF entity in order to realize the AS service based on the call event received by the AS.
  • the second AS can query the corresponding charging status based on the calling user number according to the logic of the calling user's prepaid reminder service, if it is in arrears Or the state of low balance, then the call control instruction generated by the second AS is an announcement instruction, and the announcement instruction is used to instruct the CSEF entity to play a prompt tone to the calling user equipment.
  • the CSEF entity may trigger the MRF entity to The calling user plays the audio content corresponding to the prepaid reminder.
  • each AS can process the same call event in parallel, that is, each AS can process the same call event in parallel after receiving the same call event, independent of each other.
  • different ASs can obtain the call control instruction corresponding to the call event according to their own business logic.
  • the CRBT AS may generate a PlayVoice call control instruction instructing to play a tone to the calling user according to the CRBT playing service logic of the called user.
  • the call control instruction specifically includes a call new user instruction CallnewUser, a release user instruction ReleaseUser, a playback instruction PlayVoice, an instruction SDPAction for adding, modifying, or deleting an SDP, an instruction ParaAction for adding, modifying, or deleting a call parameter, and the like.
  • the call new user instruction is used to instruct to call a new user
  • the release user instruction is used to instruct to release the user corresponding to the current call event
  • the play instruction is used to instruct the specified user to play the operation
  • the SDPAction instruction is used to instruct the session description protocol
  • the (Session Description Protocol, SDP) parameter is added, modified or deleted
  • the ParaAction command is used to indicate the call parameter to be added, modified or deleted.
  • the service provided by at least one AS among the multiple ASs is the aforementioned dependent AS service.
  • the dependent AS that is, the second AS
  • the relying party AS that is, the first AS
  • the relying party AS that is, the first AS
  • the second call control command sent by the second AS carries associated factor change information, and the associated factor change information is used to indicate that the associated factor of the call service changes.
  • an associated factor is a factor related to the calling service.
  • the associated factor may be one of the factors upon which the first application server determines the call control instruction, or in other words, the associated factor may be one of the inputs for the first application server to determine the call control instruction.
  • the correlation factor can be any one of the calling number, called number, tariff status, or codec used.
  • the association factor may specifically be a certain parameter associated with the call service, such as the calling user caller, the called user called, etc.; or, the association factor may be the operation status associated with the call service, such as the corresponding tariff of the user status etc.
  • the association factor change information may further include a changed value of the first parameter.
  • the call control instruction sent by the trumpet AS according to its own trumpet service logic may specifically be the directive ParaAction for modifying call parameters.
  • the ParaAction instruction may include information indicating that the call parameter caller has changed. That is, the associated factor change information in the ParaAction instruction corresponding to the small AS indicates that the first parameter has changed, that is, the first parameter is caller, and the ParaAction instruction includes parachg:caller.
  • the change information of the associated factor may also include the changed value of the caller, for example, the caller is changed to the calling user's trumpet C, specifically, the ParaAction instruction may include caller:C.
  • the CSEF entity may be locally pre-configured with a possible value of the first parameter, and the CSEF entity may determine the changed value of the first parameter according to the local configuration and associated factor change information.
  • the possible value of the first parameter caller locally configured by the CSEF entity is B or C, and the caller corresponding to the call session is initially B. Then the CSEF entity can determine that the changed value of the first parameter caller is C according to the parachg:caller included in the ParaAction instruction.
  • the information exchange between the AS and the CSEF entity can be exchanged through application layer messages, for example, messages based on HyperText Transfer Protocol (HyperText Transfer Protocol, HTTP), or Simple Mail Transfer Protocol (Simple Mail Transfer Protocol) Mail Transfer Protocol, SMTP) messages or other types of transmission messages.
  • HTTP HyperText Transfer Protocol
  • SMTP Simple Mail Transfer Protocol
  • the embodiment of the present application does not specifically limit the format and type of information interaction.
  • the call event sent by the CSEF entity to the AS may be carried in an HTTP request message, specifically It can be carried in the URL of the HTTP request message, it can also be carried in the header field of the HTTP request message, and it can also be carried in the message body of the HTTP request message.
  • HTTP request message for sending a call event is as follows:
  • the association factor change information sent by the second AS to the CSEF entity may be sent separately, that is, the second AS does not carry the association factor change information in the second call control instruction, but in the Before or after sending the second call control instruction, send association factor change information to the CSEF entity.
  • the second call control instruction in step 503 does not include the association factor change information, so that the CSEF entity has an opportunity to receive the third call control instruction, the CSEF entity can enter a waiting state (the maximum waiting period can be preset), so that during the waiting period, the CSEF entity can skip step 504 and directly execute step 505 to receive the third call control instruction.
  • the CSEF entity may directly execute the first call control instruction and the second call control instruction in parallel.
  • the second call control instruction in step 503 includes the change of associated factors information
  • the CSEF entity may then perform step 504.
  • Step 504 The CSEF entity sends an instruction to update the indication information to the first AS according to the association factor change information.
  • This step is optional.
  • the CSEF entity After the CSEF entity receives call control instructions sent by multiple ASs, such as the first call control instruction and the second call control instruction, it can determine whether to trigger the first AS to resend the call control instruction according to the change information of the correlation factor carried in the second call control instruction.
  • the instruction may be sending an instruction to the first AS to update instruction information, which is used to instruct the first application server to resend the call control instruction, so that the call control instruction resent by the first AS replaces the first AS sent by the first AS. Call the control instruction, so as to complete the execution operation of the updated instruction.
  • the CSEF entity determines whether to trigger the first AS to resend the call control instruction according to the association factor change information, which may be determined according to whether the association factor change information sent by the second AS matches the association factor corresponding to the first AS.
  • the correlation factor corresponding to the first AS refers to the correlation factor that the first AS is interested in, that is, the correlation factor on which the service execution of the first AS depends. That is to say, the correlation factor corresponding to the call service may be used as one of the inputs for the first AS to determine the call control instruction.
  • the CRBT AS determines that the multiple inputs of the call control command, that is, the playback command, may include the number of the calling party, the number of the called party, etc., wherein the associated factors corresponding to the CRBT AS may be Among the multiple inputs, the called number input, that is, the CRBT AS is interested in the change of the related factor of the called user number when sending the playback instruction, and the playback instructions corresponding to different called user numbers are generally different.
  • the CSEF entity determines to trigger the first AS to resend the call control instruction; if the association factor change information sent by the second AS is consistent with the first AS If the association factors corresponding to an AS do not match, the CSEF entity determines not to trigger the first AS to resend the call control instruction.
  • the method further includes: the CSEF entity obtains the first AS corresponding to at least one associated factor.
  • the CSEF entity can obtain the correlation factor for determining the call traffic of one of the inputs of the call control instruction.
  • the correlation factor corresponding to the first AS may specifically be a specific parameter change that the first AS is interested in, for example, it may include modification, deletion, and addition of parameters, etc.; or, the correlation factor may be a service operation status such as a tariff status .
  • the CSEF entity may acquire the association factor corresponding to the first AS in a local configuration manner, that is, in a static manner, or in a dynamic manner.
  • the static configuration refers to that before the call service occurs, the CSEF entity reads the pre-configured association factors associated with the relying party AS from the local or other devices accessible by the CSEF entity.
  • the configuration in a dynamic manner refers to that the CSEF entity obtains the correlation factor corresponding to the first AS from the information dynamically reported by the first AS. Specifically can include:
  • Step 1 The first AS sends a subscription request to the CSEF entity, and the subscription request includes at least one correlation factor on which the first AS determines the call control instruction.
  • the subscription request is used for the first AS to request the CSEF entity to subscribe to the change situation of at least one associated factor If the first AS is interested in the change of the at least one correlation factor, if the CSEF entity determines that the at least one correlation factor has changed, it may send a notification message to the first AS, such as correlation factor change information, so that the first AS A change in the at least one correlation factor is obtained.
  • the subscription request may further include a user identity, which is used to indicate the user corresponding to the call service.
  • Step 2 The CSEF entity receives at least one association factor corresponding to the first AS.
  • the CSEF entity may obtain at least one association factor corresponding to the first AS carried in the subscription request by receiving the subscription request from the first AS.
  • the CSEF entity can receive and store the association factors corresponding to the first AS, and generate correspondences between different ASs and corresponding association factors, so that they can be queried later to identify whether there is an association factor of interest to the first AS.
  • the change Specifically, the CSEF entity may query and identify that the correlation factor matches the correlation factor corresponding to the first AS according to the correlation factor included in the correlation factor change information sent by the second AS.
  • the instruction update instruction information includes change information of the associated factor of the associated factor or the at least one associated factor.
  • the CSEF entity sends an instruction update indication information to the first AS according to the change information of the association factor, so as to trigger the first AS to resend the call control instruction
  • the implementation specifically includes:
  • the CSEF entity sends association factor change information to the first AS, which is used to instruct the first AS to resend the call control instruction.
  • the CSEF entity may extract the association factor change information carried in the second control instruction and forward it to the first AS, thereby instructing the first AS to resend the call control instruction.
  • the CSEF entity sends instruction update instruction information or a change event to the first AS according to the change information of the association factor, for instructing the first AS to resend the call control instruction.
  • the CSEF entity may extract the associated factor change information carried in the second control instruction, and regenerate instruction update instruction information according to the associated factor change information, and the instruction update instruction information may include the associated factor change information The associated factors indicated in .
  • the CSEF entity may generate a corresponding change event according to the change information of the associated factor, so that the instruction update indication information or the change event is used to instruct the first AS to resend the call control instruction.
  • the CSEF entity sends an instruction update indication information or a change event to the first application server according to the change information of the associated factor, which may specifically include:
  • the CSEF entity queries the association factor corresponding to the first AS according to the association factor change information, for example, queries the association factor corresponding to the first AS configured locally or dynamically acquired by the CSEF entity. If the association factor indicated in the association factor change information matches the association factor corresponding to the first AS, an instruction is sent to the first application server to update the indication information or the change event.
  • the CSEF entity sends an instruction update indication information or a change event to the first AS by calling an instruction update request message, that is, the CSEF entity sends an instruction update request message to the first AS, and the request message includes the above instruction update Indicates information or change events.
  • call instruction update request message is exemplary rather than limiting.
  • Step 505 the first AS sends a third call control instruction to the CSEF entity, where the third call control instruction is used to replace the first call control instruction.
  • the third call control instruction is used to replace the first call control instruction, that is, the CSEF entity can replace or overwrite the previous first call control instruction with the third call control instruction, and perform the first call control instruction delete.
  • the first AS may resend the call control instruction to the CSEF entity according to the trigger of the CSEF entity, that is, the third call control instruction.
  • the first AS may update the response message through the call instruction (that is, the response message corresponding to the above-mentioned call instruction update request message) sending a third call control instruction to the CSEF entity, that is, the first AS sends a call instruction update response message to the CSEF entity, and the response message includes the third call control instruction;
  • the response message also includes information related to the first call control command, such as the sending timestamp of the first call control command, the identifier, and even the content of the first call control command itself, so that the CSEF entity can determine that the third call control command is used for replacing the first call control instruction;
  • the first AS may also send a third call control instruction to the CSEF entity and a third call control instruction
  • the first AS may send a third call control instruction to the CSEF entity through a call instruction update notification message, that is, the first AS sends a call instruction update notification message to the CSEF entity, and the notification message includes the third call control instruction;
  • the notification message may also include information about the first call control instruction, such as the timestamp and identifier of the first call control instruction or even the content of the first call control instruction itself, so that the CSEF entity can determine the first call control instruction
  • the third call control command is used to replace the first call control command.
  • call instruction update response message and “call instruction update notification message” are exemplary rather than limiting.
  • the instruction update indication information or the change event is used to indicate that the first parameter has changed, or it also includes the changed value of the first parameter, then the third call control instruction is the first AS after the first parameter is changed. value generated.
  • Step 506 The CSEF entity executes the second call control instruction and the third call control instruction in parallel.
  • the CSEF entity executes the second call control instruction and the third call control instruction in parallel without executing the first call control instruction.
  • the CSEF entity will not immediately execute the first call control instruction and the second call control instruction, Instead, first determine whether the association factor change information carried in the second call control command sent by the second AS matches the association factor corresponding to the first AS stored locally, so that the CSEF entity can decide whether to trigger the first AS according to the matching result Resend the call control command. If the matching result is successful and the CSEF entity determines that it is necessary to trigger the first AS to resend the call control command, the CSEF entity will not execute the first call control command and the second call control command in parallel, but waits for the first AS to send a new call control command.
  • the third call control instruction and the second call control instruction are executed in parallel to meet the user experience requirements of the dependent AS service; if the matching result is failure, the CSEF entity determines that it is not necessary to trigger the second call control instruction An AS resends the call control instruction, and the CSEF entity executes the first call control instruction and the second call control instruction in parallel.
  • the CSEF entity may send a command processing success response to the first AS and the second AS, which is used to indicate to the AS that the corresponding call control command sent by the AS is successfully executed.
  • the following uses the prepaid reminder service and the small number service as examples to illustrate the process of parallel processing by the AS.
  • the first AS is an intelligent AS
  • the second AS is a small AS corresponding to the small service.
  • the method may include the following steps.
  • Step 600 the intelligent AS sends a subscription request to the CSEF entity.
  • the subscription request is used for the smart AS to report the correlation factor that the smart AS is interested in to the CSEF entity, so as to request to subscribe to the change of the correlation factor.
  • the subscription request may specifically be a subscribe request message.
  • the subscription request may carry the association factor parachg indicating that the smart AS is interested in being the calling user identifier caller, that is, the subscribe request includes parachg:caller.
  • the subscription request sent by the AS to the CSEF entity may be carried in an HTTP request message, and the HTTP request message is as follows:
  • Step 601 The CSEF entity sends call events to the small AS and the smart AS in parallel.
  • the call event can be an initial call event (such as initcall request), and the corresponding calling party number of the initial call event is A, and the called party number is B.
  • the initcall request carries call parameters, that is, the calling user number caller, that is, the initcall request includes caller: A, called (called user): B.
  • the calling user has purchased the small number service, that is, the main number of the calling user is 138138, and the small number can be 123123.
  • Step 602 the intelligent AS sends the announcement instruction corresponding to the main number to the CSEF entity.
  • the smart AS generates a call control instruction corresponding to the calling party number, that is, a PlayVoice playback instruction, according to the trigger logic of its own prepaid reminder service.
  • the call control instruction PlayVoice may also include a Uniform Resource Locator (Uniform Resource Locator, URL) of the audio media resource, which is used to instruct the CSEF entity to determine the audio resource corresponding to the main number according to the URL.
  • URL Uniform Resource Locator
  • Step 603 The trumpet AS sends an instruction to modify the call parameters to the CSEF entity.
  • the call control instruction sent by the trumpet AS according to its own trumpet business logic may specifically be the directive ParaAction for modifying call parameters.
  • the ParaAction instruction may include change information of related factors indicating that the call parameter caller changes.
  • the ParaAction command carries association factor change information parachg:caller, which is used to indicate that the association factor caller corresponding to the call service changes.
  • the associated factor change information in the ParaAction instruction corresponding to the small AS indicates that the first parameter caller has changed, and the ParaAction instruction includes parachg:caller.
  • the ParaAction command sent by the AS to the CSEF entity can be carried in the HTTP response message, and the message structure is as follows:
  • the change information of the association factor may also include the changed value of the caller, for example, the caller is changed to the calling user's trumpet number 123123, specifically, the ParaAction instruction may include caller: 123123.
  • the ParaAction directive includes:
  • the CSEF entity may be locally pre-configured with a possible value of the first parameter, and the CSEF entity may determine the changed value of the first parameter according to the local configuration and associated factor change information.
  • the possible value of the first parameter caller locally configured by the CSEF entity is A or C, and the caller corresponding to the call session is initially A. Then the CSEF entity can determine that the changed value of the first parameter caller is C according to the parachg:caller included in the ParaAction instruction.
  • Step 604 The CSEF entity sends a change event to the AS.
  • the CSEF entity can recognize that the parameter caller matches the association factor included in the subscription request sent by the smart AS to the CSEF entity according to the parachg:caller carried in the ParaAction command sent by the small AS, and then generate a change event (ParChg request event), and send the ParaChg request event to the first AS, instructing the intelligent AS to resend the call control instruction.
  • the ParaChg request event carries the associated factor indicating the current change as the first parameter, that is, the caller.
  • change event ParaChg request carries the currently changed first parameter caller, and also includes that the caller is changed to C, that is, caller:C.
  • the CSEF entity sends a call instruction update request message to the smart AS, and the request message includes the above-mentioned change event.
  • Step 605 The smart AS sends the announcement instruction corresponding to the trumpet to the CSEF entity according to the change event.
  • the intelligent AS regenerates the playback instruction corresponding to the trumpet (caller: C) according to the change event, and sends the playback instruction corresponding to the trumpet to the CSEF entity.
  • the announcement instruction is used to replace the announcement instruction generated based on the main number sent by the intelligent AS to the CSEF entity in step 602 before.
  • the intelligent AS sends a call instruction update response message to the CSEF entity, that is, a response message corresponding to the call instruction update request message in step 604, and the response message includes the regenerated playback instruction.
  • Step 606 The CSEF entity executes in parallel the instruction for modifying the call parameters and the instruction for playing the sound corresponding to the trumpet.
  • the CSEF entity executes the instruction for modifying the call parameters.
  • the CSEF entity may change the call parameters in the call control block according to the call parameters indicated in the instruction for modifying the call parameters. For example, if the command ParaAction for modifying the call parameter indicates that the call parameter caller changes, the CSEF entity will change the call parameter caller in the call control block to a preset value, or, according to the changed value C of the caller indicated in the ParaAction command, will call The call parameter caller in the control block is changed to C. Subsequently, the call parameter caller carried in the message sent by the CSEF entity is the changed value.
  • the CSEF entity may send an instruction execution success response to the small AS, which is used to indicate that the instruction for modifying the call parameters is successfully executed.
  • the CSEF entity executes the announcement instruction corresponding to the trumpet, that is, according to the announcement instruction, instructs the MRF entity to play the prepaid prompt audio resource corresponding to the trumpet for the calling user.
  • the reminder audio file generated based on the main number (caller: A) of the prepaid reminder service is audio 1
  • the reminder audio file generated based on the small number (caller: C) is audio 2
  • the URLs corresponding to different audio files are generally different .
  • the playback instruction in step 605 is used to replace the prepaid prompt audio resource played by the smart service to the calling user, so that in the scenario where the calling user uses a small number to call the called user, the CSEF entity instructs the smart AS through a change event Resend the call control command based on the trumpet, so as to play accurate prompt audio for the user, which meets the needs of business implementation.
  • the specific process for the CSEF entity to execute the playback instruction may include:
  • Step 607 The CSEF entity triggers the MRF entity to play a tone to the calling UE.
  • the CSEF entity and the MRF entity perform signaling interaction, trigger the MRF entity to establish an audio media channel between the MRF entity and the calling user equipment, and send the URL of the audio resource to the MRF entity, so that the MRF entity can pass the created
  • the audio media channel plays the audio resource to the calling user equipment.
  • Step 608 The MRF entity interacts with the calling user equipment to perform an announcement operation.
  • the MRF entity pushes the audio resource to the calling user equipment through the created audio media channel, and the calling user equipment plays the audio resource after acquiring the audio resource.
  • the MRF entity may send a playback success response to the CSEF entity, and in addition, the CSEF entity may send a command execution success response corresponding to the PlayVoice command to the smart AS.
  • the CSEF entity can recognize that the association factor matches the relying party's association factor through the indication that the association factor carried in the call control instruction sent by the dependent party AS (such as a small AS)
  • the party AS reports the indication of the change of the correlation factor or a specific change event, thereby triggering the relying party AS to resend a new call control command according to the change of the correlation factor to refresh the business status of the AS, so as to satisfy the user experience for the dependent AS business needs.
  • the above-mentioned call service enabling entity includes corresponding hardware structures and/or software modules for performing various functions.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.
  • the embodiment of the present application may divide the call service enabling entity into functional modules according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation.
  • the present application also provides a communication device for implementing the steps performed by the call service enabling entity CSEF entity in the aforementioned method for performing call-related services.
  • the apparatus 700 includes a sending module 701 and a receiving module 702 .
  • the sending module 701 and the receiving module 702 may also be referred to as an integrated transceiver module to implement a transceiver function, such as a transceiver circuit, a transceiver, a transceiver or a communication interface.
  • the apparatus 700 may also include a processing module 703 .
  • the sending module 701 is used to send the call event to the first application server and the second application server in parallel, and the sending module 701 is also used to send the instruction update indication information to the first application server according to the change information of the correlation factors, etc.
  • the receiving module 702 is used to receive the first call control instruction from the first application server and the second call control instruction from the second application server, and the receiving module 702 is also used to receive the third call control instruction from the first application server, etc.
  • the operation of receiving data/information at the CSEF entity side in the embodiment includes step 502 , step 503 and step 505 .
  • the processing module 703 is configured to execute in parallel the second call control instruction and the third call control instruction and other operations on the CSEF entity side in the above embodiments of the present application except for receiving and sending data or information, as in step 506 .
  • the present application also provides a communication device, which is used to implement the steps performed by the first application server in the aforementioned method for performing call-related services.
  • the apparatus 700 includes a sending module 701 and a receiving module 702 .
  • the sending module 701 and the receiving module 702 may also be referred to as an integrated transceiver module to implement a transceiver function, such as a transceiver circuit, a transceiver, a transceiver or a communication interface.
  • the receiving module 702 is used to receive the call event from the call service enabling entity, and the receiving module 702 It is also used to receive the operation of receiving data/information at the first application server side in the above embodiments of the present application, such as step 501 and step 504, such as the instruction update indication information sent by the call service enabling entity according to the change information of the associated factors.
  • the sending module 701 is used to send the first call control instruction to the call service enabling entity according to the call event, and the sending module 701 is also used to send the third call control instruction to the call service enabling entity, etc.
  • the aforementioned communication device 700 can take the form shown in FIG. 4 .
  • the processor 401 in FIG. 4 may call the computer-executed instructions stored in the memory 403, so that the communication device 700 executes the method performed by the call service enabling entity and the first application server in the above method embodiment.
  • the function/implementation process of the sending module 701 and the receiving module 702 in FIG. 7 can be implemented by the processor 401 in FIG. 4 invoking computer-executed instructions stored in the memory 403 .
  • the function/implementation process of the processing module 703 in FIG. 7 can be realized by the processor 401 in FIG. The process may be implemented through communication interface 404 in FIG. 4 .
  • one or more of the above modules or units may be implemented by software, hardware or a combination of both.
  • the software exists in the form of computer program instructions and is stored in the memory, and the processor can be used to execute the program instructions and realize the above method flow.
  • the processor can be built into a SoC (system on a chip) or ASIC, or it can be an independent semiconductor chip.
  • the core of the processor is used to execute software instructions for calculation or processing, and can further include necessary hardware accelerators, such as field programmable gate array (field programmable gate array, FPGA), PLD (programmable logic device) , or a logic circuit that implements a dedicated logic operation.
  • the hardware can be CPU, microprocessor, digital signal processing (digital signal processing, DSP) chip, microcontroller unit (microcontroller unit, MCU), artificial intelligence processor, ASIC, Any one or any combination of SoC, FPGA, PLD, dedicated digital circuit, hardware accelerator or non-integrated discrete device, which can run necessary software or not depend on software to execute the above method flow.
  • DSP digital signal processing
  • MCU microcontroller unit
  • ASIC artificial intelligence processor
  • an embodiment of the present application further provides a chip system, including: at least one processor and an interface, the at least one processor is coupled to the memory through the interface, and when the at least one processor executes the computer program or instruction in the memory When, the method in any one of the above method embodiments is executed.
  • the chip system further includes a memory.
  • the system-on-a-chip may consist of a chip, or may include a chip and other discrete devices, which is not specifically limited in this embodiment of the present application.
  • the embodiment of the present application further provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be completed by computer programs to instruct related hardware, and the program can be stored in the above computer-readable storage medium. When the program is executed, it can include the processes of the above method embodiments .
  • the computer-readable storage medium may be an internal storage unit of the communication device in any of the foregoing embodiments, such as a hard disk or memory of the communication device.
  • the above-mentioned computer-readable storage medium may also be an external storage device of the above-mentioned communication device, such as a plug-in hard disk equipped on the above-mentioned communication device, a smart memory card (smart media card, SMC), a secure digital (secure digital, SD) card, Flash card (flash card), etc. Further, the above-mentioned computer-readable storage medium may also include both an internal storage unit of the above-mentioned communication device and an external storage device.
  • the above computer can The read storage medium is used to store the above-mentioned computer program and other programs and data required by the communication device.
  • the computer-readable storage medium described above can also be used to temporarily store data that has been output or will be output.
  • the embodiment of the present application further provides a computer program product. All or part of the processes in the above method embodiments can be completed by computer programs instructing related hardware, and the programs can be stored in the above computer program products. When the programs are executed, they can include the processes of the above method embodiments.
  • An optional embodiment of the present application further provides a computer instruction. All or part of the processes in the above method embodiments may be completed by computer instructions to instruct related hardware (such as computers, processors, access network devices, mobility management network elements or session management network elements, etc.).
  • the program may be stored in the above-mentioned computer-readable storage medium or in the above-mentioned computer program product.
  • the disclosed devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be Incorporation or may be integrated into another device, or some features may be omitted, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the unit described as a separate component may or may not be physically separated, and the component displayed as a unit may be one physical unit or multiple physical units, that is, it may be located in one place, or may be distributed to multiple different places . Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请实施例提供一种执行呼叫相关业务的方法、装置及系统，涉及通信技术领域。该方法包括：呼叫业务使能实体将呼叫事件并行发送给第一应用服务器和第二应用服务器；从第一应用服务器接收第一呼叫控制指令并从第二应用服务器接收第二呼叫控制指令，从第一应用服务器接收用于替代第一呼叫控制指令的第三呼叫控制指令；并行执行第二呼叫控制指令和第三呼叫控制指令。从而降低AS业务并行触发机制对用户体验的影响。

Description

一种执行呼叫相关业务的方法、装置及系统
本申请要求于2022年02月28日提交国家知识产权局、申请号为202210212015.9、申请名称为“一种执行呼叫相关业务的方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种执行呼叫相关业务的方法、装置及系统。
背景技术
一种基于网际互连协议(Internet Protocol，IP)网络上提供多媒体业务的通用网络架构，即多媒体子系统(IP Multimedia Subsystem，IMS)，是通信运营商可提供的一种全新的多媒体业务形式，能够满足终端客户新颖、多样化的多媒体业务需求。
应用服务器(Application Server，AS)是IMS系统中应用层的设备，如图1所示，IMS系统通常包括多个AS，用于提供基本业务、补充业务、多媒体会议以及融合通讯等业务，通常可以将某个AS提供的业务称为AS业务。例如，IMS系统包括多媒体电话设备(MultiMediaTelephony，MMTel)AS、彩铃AS以及智能AS等，示例性的，智能AS可以为用户提供的AS业务包括预付费提醒业务。AS与呼叫会话控制功能(Call Session Control Function，CSCF)网元之间可以通过会话初始协议(Session initialization Protocol，SIP)协议进行交互，进而实现各种网络业务的触发和执行。
目前，AS业务中包括次序敏感型业务，也称非独立的AS业务或者有依赖的AS业务，具体是指该AS业务对应的呼叫控制指令的生成依赖于另一AS业务生成的呼叫控制指令中的部分或全部信息。
示例性的，某用户购买了小号业务和预付费提醒业务，其中，预付费提醒业务可以根据用户号码的余额进行语音提示以控制该用户的通话业务，小号业务是指用户可以申请一个主号码之外，额外申请一个辅助号码(也叫小号)，主号和小号共用一张用户身份识别卡(Subscriber Identification Module，SIM)，在IMS系统中主号和小号被视为同一个用户的号码。若小号和主号是分别计费的，则预付费提醒业务生成的语音提示一般不同，则认为预付费提醒业务是有依赖的AS业务。
而目前的AS业务并行触发机制，使多个AS业务的呼叫控制指令被并行地产生，乃至被并行地执行，从而一个AS无法基于其他AS产生的呼叫控制指令生成自己的呼叫控制指令。例如，CSCF网元接收小号AS发送的用户号码变更指令，用于指示将该呼叫业务对应的主叫号码变更为小号号码；CSCF网元还接收智能AS发送的放音指令(即用于指示CSCF向用户设备播放音频内容的呼叫控制指令)，用于指示向主叫用户播放主号对应的预付费提示音。此时，CSCF网元并行执行呼叫控制指令，即同时执行号码变更和播放主号对应的预付费提示音。但是从这两个业务的用户体验需求来说，CSCF网元向主叫用户播放的应该是小号对应的预付费提示音，而不是主号对应的预付费提示音，这就影响了用户体验。
如何降低AS业务并行触发机制对用户体验的影响，是亟需解决的问题。
发明内容
本申请提供一种执行呼叫相关业务的方法、装置及系统，降低AS业务并行触发机制对用户体验的影响。
为达到上述目的，本申请采用如下技术方案：
第一方面，提供一种执行呼叫相关业务的方法，应用于呼叫业务使能实体，该方法包括：将呼叫事件并行发送给第一应用服务器和第二应用服务器；从所述第一应用服务器接收第一呼叫控制指令以及从所述第二应用服务器接收第二呼叫控制指令；从第一应用服务器接收第三呼叫控制指令，第三呼叫控制指令用于替代第一呼叫控制指令；并行执行第二呼叫控制指令和第三呼叫控制指令。
基于上述方法，在AS业务并行触发机制下，呼叫业务使能实体可以通过从有依赖的AS业务侧接收更新的呼叫控制指令，从而刷新AS的业务状态，降低AS业务并行触发机制对用户体验的影响。
在一种实施方式中，第二呼叫控制指令中包括关联因素变化信息，所述关联因素变化信息用于指示呼叫业务的至少一个关联因素发生变化，所述至少一个关联因素为所述第一应用服务器确定呼叫控制指令所依赖的因素。
基于上述方法，呼叫业务使能实体可以通过被依赖方AS(第二应用服务器)在发送的呼叫控制指令中，携带的关联因素发生变化的指示，识别出与依赖方(第一应用服务器)关联因素匹配，则可以向依赖方AS上报指示关联因素发生变化的指令更新指示信息，从而触发依赖方AS根据关联因素的变化，重新发送新的呼叫控制指令，以刷新AS的业务状态，从而降低AS业务并行触发机制对用户体验的影响。
在一种实施方式中，关联因素包括所述呼叫业务对应的参数，和/或所述呼叫业务的状态。
基于上述方法，依赖方感兴趣的关联因素可以包括呼叫业务对应的某一参数和/或呼叫业务的运行状态等，从而呼叫业务使能实体可以根据被依赖方AS(第二应用服务器)发送的呼叫控制指令中关联因素的变化，触发依赖方AS重新发送呼叫控制指令，从而满足有依赖的AS业务的用户需求，降低AS业务并行触发机制对用户体验的影响。
在一种实施方式中，将呼叫事件并行发送给第一应用服务器和第二应用服务器之前，所述方法还包括：获取第一应用服务器对应的至少一个关联因素。
基于上述方法，呼叫事件发生之前，呼叫业务使能实体可以提前感知第一应用服务器感兴趣的关联因素，该关联因素是第一应用服务器用于确定呼叫控制指令的输入之一，从而呼叫业务使能实体可以根据提前感知的第一应用服务器感兴趣的关联因素确定是否需要触发或者什么时候触发第一应用服务器重新发送呼叫控制指令，在AS业务并行触发机制下，从而降低AS业务并行触发机制对用户体验的影响。
在一种实施方式中，获取第一应用服务器对应的至少一个关联因素，具体包括：接收来自第一应用服务器的订阅请求，所述订阅请求包括第一应用服务器对应的至少一个关联因素，所述订阅请求用于请求订阅第一应用服务器感兴趣的至少一个关联因素的变化。
基于上述方法，呼叫事件发生之前，呼叫业务使能实体可以接收来自第一应用服务器上报的感兴趣的关联因素，从而使得呼叫业务使能实体可以根据第一应用服务器感兴趣的关联因素确定是否需要触发或者什么时候触发第一应用服务器重新发送呼叫控制指令，提高AS业务并行触发机制下，对于有依赖的AS业务实现其业务需求。
在一种实施方式中，在从所述第一应用服务器接收第三呼叫控制指令之前，所述方法还包括：根据所述关联因素变化信息向所述第一应用服务器发送指令更新指示信息，所述指令更新指示信息用于指示所述第一应用服务器重新发送呼叫控制指令。
在一种实施方式中，指令更新指示信息包括关联因素变化信息或至少一个关联因素。
基于上述方法，呼叫业务使能实体向第一应用服务器发送的指令更新指示信息中可以携带关联因素变化信息，或者携带关联因素变化信息中指示的至少一个关联因素，从而指示第一应用服务器发生变化的关联因素，使得第一应用服务器可以根据关联因素的变化，重新发送新的呼叫控制指令，以刷新AS的业务状态，降低AS业务并行触发机制对用户体验的影响。
在一种实施方式中，根据关联因素变化信息向第一应用服务器发送指令更新指示信息，具体包括：根据所述关联因素变化信息查询所述第一应用服务器对应的关联因素，若所述关联因素变化信息中指示的关联因素与所述第一应用服务器对应的关联因素相匹配，则向所述第一应用服务器发送指令更新指示信息。
基于上述方法，呼叫业务使能实体可以根据预先感知的第一应用服务器对应的关联因素与关联因素变化信息中的关联因素确定是否匹配，从而向第一应用服务器发送指令更新指示信息，从而降低AS业务并行触发机制对用户体验的影响。
在一种实施方式中，若所述关联因素变化信息中包括所述呼叫业务对应的第一参数发生变化，则所述关联因素变化信息包括所述第一参数变化后的值。
基于上述方法，关联因素具体可以为呼叫业务对应的参数，例如第一参数，当第二呼叫控制指令中包括第一参数发生变化的指示信息，则关联因素变化信息还可以包括该第一参数变化后的值，以指示呼叫业务使能实体可以触发第一应用服务器重新发送呼叫控制指令，从而降低AS业务并行触发机制对用户体验的影响。
在一种实施方式中，若所述指令更新指示信息中包括所述呼叫业务对应的第一参数发生变化，则所述指令更新指示信息中包括所述第一参数变化后的值。
基于上述方法，指令更新指示信息用于指示第一参数发生变化，且指令更新指示信息中包括所述第一参数变化后的值，从而用于指示第一应用服务器可以根据第一参数变化后的值重新发送呼叫控制指令，从而降低AS业务并行触发机制对用户体验的影响。
在一种实施方式中，第三呼叫控制指令是第一应用服务器根据第一参数变化后的值生成的。
基于上述方法，第一应用服务器可以根据指令更新指示信息中包括的第一参数变化后的值，从而根据第一参数变化后的值重新发送呼叫控制指令，从而降低AS业务并行触发机制对用户体验的影响。
在一种实施方式中，订阅请求中还包括用户身份标识。
在一种实施方式中，呼叫业务使能实体部署于呼叫会话控制功能CSCF网元或者统一控制功能UCF网元。
在一种实施方式中，将呼叫事件并行发送给第一应用服务器和第二应用服务器之前，所述方法还包括：基于终端设备的呼叫会话消息生成所述呼叫事件。
第二方面，提供一种执行呼叫相关业务的方法，应用于第一应用服务器，该方法包括：接收来自呼叫业务使能实体的呼叫事件；根据呼叫事件向呼叫业务使能实体发送第一呼叫控制指令；向呼叫业务使能实体发送第三呼叫控制指令，第三呼叫控制指令用于替代第一呼叫控制指令。
在一种实施方式中，在向所述呼叫业务使能实体发送第三呼叫控制指令之前，所述方法还包括：从所述呼叫业务使能实体接收关联因素变化信息，所述关联因素变化信息用于指示呼叫业务的至少一个关联因素发生变化，所述至少一个关联因素为所述应用服务器确定呼叫控制指令所依赖的因素；基于所述关联因素变化信息生成所述第三呼叫控制指令。
在一种实施方式中，关联因素包括呼叫业务对应的参数，和/或呼叫业务的状态。
在一种实施方式中，接收来自所述呼叫业务使能实体的呼叫事件之前，所述方法还包括：向所述呼叫业务使能实体发送应用服务器对应的至少一个关联因素。
在一种实施方式中，在向所述呼叫业务使能实体发送第三呼叫控制指令之前，所述方法还包括：接收来自所述呼叫业务使能实体的指令更新指示信息，所述指令更新指示信息用于指示所述应用服务器重新发送呼叫控制指令。
在一种实施方式中，指令更新指示信息包括关联因素变化信息或至少一个关联因素。
在一种实施方式中，若所述指令更新指示信息中包括所述呼叫业务对应的第一参数发生变化，则所述指令更新指示信息中包括所述第一参数变化后的值。
在一种实施方式中，第三呼叫控制指令是所述应用服务器根据第一参数变化后的值生成的。
在一种实施方式中，呼叫业务使能实体部署于呼叫会话控制功能CSCF网元或者统一控制功能UCF网元。
第三方面，提供一种通信装置，该装置包括：发送模块，用于将呼叫事件并行发送给第一应用服务器和第二应用服务器；接收模块，用于从第一应用服务器接收第一呼叫控制指令以及从第二应用服务器接收第二呼叫控制指令；接收模块，还用于从第一应用服务器接收第三呼叫控制指令，第三呼叫控制指令用于替代第一呼叫控制指令；处理模块，用于并行执行第二呼叫控制指令和第三呼叫控制指令。
在一种实施方式中，第二呼叫控制指令中包括关联因素变化信息，所述关联因素变化信息用于指示呼叫业务的至少一个关联因素发生变化，所述至少一个关联因素为所述第一应用服务器确定呼叫控制指令所依赖的因素。
在一种实施方式中，所述关联因素包括所述呼叫业务对应的参数，和/或所述呼叫业务的状态。
在一种实施方式中，接收模块，还用于获取所述第一应用服务器对应的所述至少一个关联因素。
在一种实施方式中，所述发送模块，还用于根据所述关联因素变化信息向所述第一应用服务器发送指令更新指示信息，所述指令更新指示信息用于指示所述第一应用服务器重新发送呼叫控制指令。
在一种实施方式中，指令更新指示信息包括所述关联因素变化信息或所述至少一个关联因素。
在一种实施方式中，所述处理模块还用于根据所述关联因素变化信息查询所述第一应用服务器对应的关联因素，若所述关联因素变化信息中指示的关联因素与所述第一应用服务器对应的关联因素相匹配，则所述发送模块，用于向所述第一应用服务器发送指令更新指示信息。
在一种实施方式中，若所述关联因素变化信息中包括所述呼叫业务对应的第一参数发生变化，则所述关联因素变化信息包括所述第一参数变化后的值。
在一种实施方式中，若所述指令更新指示信息中包括所述呼叫业务对应的第一参数发生变化，则所述指令更新指示信息中包括所述第一参数变化后的值。
在一种实施方式中，第三呼叫控制指令是所述第一应用服务器根据所述第一参数变化后的值生成的。
在一种实施方式中，所述装置部署于呼叫会话控制功能CSCF网元或者统一控制功能UCF网元。
在一种实施方式中，处理模块还用于基于终端设备的呼叫会话消息生成所述呼叫事件。
第四方面，提供一种通信装置，该装置包括：接收模块，用于接收来自所述呼叫业务使能实体的呼叫事件；发送模块，用于根据所述呼叫事件向所述呼叫业务使能实体发送第一呼叫控制指令；所述发送模块，还用于向所述呼叫业务使能实体发送第三呼叫控制指令，所述第三呼叫控制指令用于替代所述第一呼叫控制指令。
在一种实施方式中，接收模块，还用于从所述呼叫业务使能实体接收关联因素变化信息，所述关联因素变化信息用于指示呼叫业务的至少一个关联因素发生变化，所述至少一个关联因素为所述应用服务器确定呼叫控制指令所依赖的因素。
在一种实施方式中，关联因素包括所述呼叫业务对应的参数，和/或所述呼叫业务的状态。
在一种实施方式中，发送模块还用于向所述呼叫业务使能实体发送所述装置对应的所述至少一个关联因素。
在一种实施方式中，在向所述呼叫业务使能实体发送第三呼叫控制指令之前，所述方法还包括：接收来自所述呼叫业务使能实体的指令更新指示信息，所述指令更新指示信息用于指示所述应用服务器重新发送呼叫控制指令。
在一种实施方式中，指令更新指示信息包括所述关联因素变化信息或所述至少一个关联因素。
在一种实施方式中，若所述指令更新指示信息中包括所述呼叫业务对应的第一参数发生变化，则所述指令更新指示信息中包括所述第一参数变化后的值。
在一种实施方式中，第三呼叫控制指令是所述装置根据所述第一参数变化后的值生成的。
在一种实施方式中，所述呼叫业务使能实体部署于呼叫会话控制功能CSCF网元或者统一控制功能UCF网元。
第五方面，提供一种通信装置，该通信装置包括：处理器；该处理器用于与存储器耦合，并读取存储器中的指令之后，根据该指令执行如上述第一方面所述的方法。该通信装置可以为上述第一方面中的呼叫业务使能实体，或者包含上述呼叫业务使能实体的装置。
结合上述第五方面，在一种可能的实现方式中，该通信装置还包括存储器，该存储器，用于保存必要的程序指令和数据。
第六方面，提供一种通信装置，该通信装置包括：处理器；该处理器用于与存储器耦合，并读取存储器中的指令之后，根据该指令执行如上述第二方面所述的方法。该通信装置可以为上述第二方面中的应用服务器，或者包含上述应用服务器的装置。
结合上述第五方面，在一种可能的实现方式中，该通信装置还包括存储器，该存储器，用于保存必要的程序指令和数据。
第七方面，提供一种通信装置，该通信装置包括：处理器和接口电路；接口电路，用于接收计算机程序或指令并传输至处理器；处理器用于执行所述计算机程序或指令，以使该通信装置执行如上述第一方面所述的方法。
第八方面，提供一种通信装置，该通信装置包括：处理器和接口电路；接口电路，用于接收计算机程序或指令并传输至处理器；处理器用于执行所述计算机程序或指令，以使该通信装置执行如上述第二方面所述的方法。
第九方面，本申请实施例提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第一方面所述的方法。
第十方面，本申请实施例提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第二方面所述的方法。
第十一方面，本申请实施例提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面所述的方法。
第十二方面，本申请实施例提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第二方面所述的方法。
第十三方面，本申请实施例提供一种通信系统，该通信系统包括上述第三方面和上述第四方面中任一项所述的通信装置。
其中，第二方面至第十三方面中任一种可能的实现方式所带来的技术效果可参见上述第一方面中不同可能的实现方式所带来的技术效果，此处不再赘述。
附图说明
图1为本申请实施例提供的一种通信系统的架构图；
图2为本申请实施例提供的另一种通信系统的架构图；
图3为本申请实施例提供的一种AS业务触发的流程示意图；
图4为本申请实施例提供的一种通信装置的结构示意图；
图5为本申请实施例提供的一种执行呼叫相关业务的方法的流程示意图；
图6为本申请实施例提供的一种多个AS业务协同处理的流程示意图；
图7为本申请实施例提供的一种通信装置的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
首先，对本申请实施例的实施环境和应用场景进行简单介绍。
本申请实施例可以应用于IMS网络，IMS网络是指基于IP的多媒体子系统，是基于IP承载并向用户提供各种多媒体服务的网络。
图1是IMS网络的一种通信系统架构示意图。如图1所示，IMS网络包括服务呼叫会话控制功能(Serving Call Session Control Function，S-CSCF)网元和多个应用服务器AS，如AS1、AS2和AS3。S-CSCF网元对于用户主叫侧及被叫侧进行路由管理，并根据用户的签约数据进行AS触发，实现各种AS业务的功能。
在IMS网络中，CSCF网元是核心网元，主要负责处理多媒体呼叫会话过程中的信令控制。例如，管理IMS网络的用户鉴权、与其它网络实体配合进行SIP会话的控制，以及业务协商和资源分配等。每个AS与CSCF网元之间可以通过SIP协议进行交互，进而实现各种网络业务的触发和执行。
根据负责功能的不同，可以将CSCF网元分为：代理CSCF(Proxy CSCF，P-CSCF)网元、查询CSCF(Interrogating CSCF，I-CSCF)网元、服务CSCF(Serving CSCF S-CSCF)网元和紧急CSCF(Emergency CSCF，E-CSCF)网元等。上述不同的CSCF网元本质上都是SIP服务器，用于处理通信过程中的SIP信令。
其中，呼叫业务可以指用户设备(user equipment，UE)以主叫身份或者被叫身份参与，经通信网络接续与其他UE之间进行的语音通话业务或视频通话业务。以UE为主叫为例，呼叫业务可以为UE拨打手机号码、座机号码或客服中心号码而进行的语音通话业务或者视频通话业务；或者，呼叫业务可以为UE通过即时通讯(real time communication，RTC)应用呼叫其他UE而进行的语音通话业务或者视频通话业务。以UE为被叫为例，呼叫业务可以为UE接收手机、座机或客服中心的呼叫而进行的语音通话业务或者视频通话业务；或者，呼叫业务可以为UE通过RTC应用接收其他UE的呼叫而进行的语音通话业务或者视频通话业务。在本申请的实施例中呼叫业务也可以简称为呼叫业务。
应用服务器AS是IMS网络中为用户提供各种特定的多媒体服务的网元，IMS网络中通常包括多个AS，用于提供多种不同的业务。例如，IMS网络中可以包括用于提供多媒体电话基本业务及补充业务的多媒体电话(MultiMediaTelephony，MMTEL)AS，用于为用户提供彩铃业务的多媒体回铃音(Multimedia Ring Back Tone，MRBT)AS，以及其他各种第三方的AS等。
另外，IMS网络中还可以包括呼叫业务使能功能(Call Service Enabler Functions，CSEF)实体或业务使能功能(Service Enabler Functions，SEF)实体。其中，CSEF/SEF实体可以在IMS网络中独立部署，也可以部署于S-CSCF网元中，如图1所示，本申 请对此不做具体限定。
此外，如图1所示，IMS网络中还可以包括归属用户服务器(Home Subscriber Server，HSS)。HSS包含用户配置文件，可以用于执行用户的身份验证和授权。另外，HSS支持用于处理调用或呼叫会话的IMS网络实体的主要用户数据库。
随着通信技术的更新发展，本申请提供的执行呼叫相关业务的方法还可以应用于其他的通信系统，例如音视频新架构，或轻型IMS(Lite IMS)系统等。
参考图2示出了通信系统的结构示意图，该通信系统至少可以包括图2左图中所示的统一控制功能(Unified Control Functions，UCF)网元，以及服务和应用程序功能(Service and Application Functions，SAF)网元。其中，SAF网元的功能可以参考如图1中的应用服务器AS实现的功能，UCF网元的功能可以参考如图1中S-CSCF网元实现的功能。另外，UCF网元中还可以包括前述的CSEF实体，用于实现本申请实施例中CSEF实体实现的功能。
或者，如图2右图中所示，该通信系统还可以包括业务使能功能(Service Enabler Functions，SEF)实体。其中，SEF实体可以独立部署，SEF实体的功能可以参考如图1中S-CSCF网元实现的功能，以及用于实现本申请实施例中CSEF实体实现的功能；UCF网元可以用于实现前述IMS系统中CSCF网元中I-CSCF或P-CSCF网元等的功能。
目前，上述通信系统能够实现并行触发AS业务。示例性的，以图1所示的IMS网络为例，CSEF实体可以并行向多个应用服务器发送同一呼叫事件，多个应用服务器向CSEF实体并行发送呼叫控制指令，CSEF实体将接收到的多个呼叫控制指令进行合并处理之后，并行执行多个呼叫控制指令，对于其中包括的互斥指令采用择一执行或者依次执行的机制，从而实现并行触发AS业务。
其中，CSEF实体将接收到的多个呼叫控制指令进行合并处理，是指CSEF实体每接收到一个呼叫控制指令之后并不立即执行，而是先缓存或保存起来，直至收到预设个数的AS发送的预设个数的呼叫控制指令；可选地，合并处理还包括识别其中是否存在互斥指令。CSEF实体并行执行多个呼叫控制指令，是指CSEF实体不是依次执行这些呼叫控制指令，而是同时或者几乎同时执行这些呼叫控制指令，即在执行第一个呼叫控制指令之后不用等第一呼叫控制指令执行完成之后再执行第二个呼叫控制指令。
示例性的，如图3所示，CSEF实体并行触发AS业务的处理流程主要包括如下步骤。
步骤301：CSEF实体将呼叫事件并行发送给多个AS。
也就是，CSEF实体并行化向多个AS发送呼叫事件。其中，呼叫事件(Call Event)，是指呼叫业务有关的事件。具体的，CSEF实体可以将呼叫业务过程中接收的各种通知消息通过“事件”这一数据格式通知给AS。例如，呼叫业务过程中接收的振铃通知(Ring)，对应地CSEF实体向AS发送“振铃事件”；呼叫业务过程中接收的摘机通知(Answer)，对应地CSEF实体向AS发送“摘机事件”。
在一种具体的实现方式中，CSEF实体提供服务化的应用程序接口(Application Programming Interface，API)供AS调用，从而与AS配合实现各类AS业务。
具体的，CSEF实体上包括呼叫事件订阅API，供AS调用，AS调用呼叫事件订 阅API(即发送呼叫事件订阅请求)时，可以将AS自身的地址作为通知地址发给CSEF实体。当呼叫业务过程中有某个呼叫事件发生时，CSEF实体可以根据之前AS的订阅请求和通知地址，将该呼叫事件发送至对应的AS。
在一种可能的实施方式中，Call Event可以是一个枚举值，列出可能通知AS的调用事件。
需要说明的是，此处的“并行发送”是指将同一个呼叫事件一起发送给各个AS，也就是说，将一个呼叫事件发送给第一个AS后，不需要等接收到来自第一个AS的响应消息，而是可以紧接着向第二个AS、第三AS……发送该呼叫事件。示例性的，CSEF实体将呼叫事件发送至AS1之后，无需等待来自AS1的响应消息，紧接着将该呼叫事件发送至AS2和AS3等。
步骤302：AS接收呼叫事件，根据呼叫事件和AS业务逻辑生成呼叫控制指令，向CSEF实体发送呼叫控制指令。
其中，每一个呼叫控制指令用于指示CSEF实体执行与呼叫业务有关的操作，例如，与某一用户的呼叫业务有关的操作。
具体地，与呼叫业务有关的操作是指，由CSEF实体为实现呼叫业务或增强呼叫业务而基于AS的业务逻辑所需要执行的操作。例如，彩铃AS发送给CSEF实体的呼叫控制指令可以为“向主叫用户设备播放被叫用户设置的彩铃音频”，用于指示CSEF实体执行放音操作(例如，触发媒体资源功能(Media Resource Function，MRF)实体执行放音操作)。再如，小号AS发送给CSEF实体的呼叫控制指令可以为“将主叫用户号码更改为小号，如123123”，用于指示CSEF实体将在被叫用户设备上显示的主叫用户号码的显示为123123。具有预付费提醒功能的智能AS发送给CSEF实体的呼叫控制指令可以为“提醒用户付费”，用于指示CSEF实体向对应的用户设备播放付费提醒对应的音频内容。
也就是，各个AS可以并行化处理同一呼叫事件，即各个AS收到该呼叫事件后立即处理，处于并行状态。
其中，AS根据自身的业务逻辑，得到该呼叫事件对应的呼叫控制指令。
步骤303：CSEF实体并行执行接收的多个呼叫控制指令。
CSEF实体逐个接收AS发送的呼叫控制指令，直至接收到订阅该呼叫事件的预设个数的AS对应的多个呼叫控制指令之后，合并处理多个呼叫控制指令，识别出多个呼叫控制指令中是否存在互斥指示。
其中，互斥指令表示至少两个呼叫控制指令对应的AS业务存在业务冲突。也就是说，CSEF实体对于并行收到的两条或者两条以上的呼叫控制指令，不能无感知的并行执行。例如，彩铃AS发送的彩铃放音指令，和提供多媒体电话基本业务及补充业务的多媒体电话(MultiMediaTelephony，MMTEL)AS发送的呼叫等待(Call Waiting，CW)提示音的放音指令等，CSEF实体无法并行执行两条不同的放音指令。
在一种实施方式中，如果CSEF实体识别出多个呼叫控制指令中不存在互斥指令，则CSEF实体并行执行所述多个呼叫控制指令；如果多个呼叫控制指令中包括互斥指令，如包含至少两个互相排斥的呼叫控制指令，则CSEF实体择一执行互斥指令中的呼叫控制指令，或者，依次执行互斥指令中的多个呼叫控制指令。其中，择一执行是 指CSEF实体选择互斥指令中的一个呼叫控制指令执行，舍弃互斥指令中其他的呼叫控制指令。
以小号业务和预付费提醒业务为例，示例性的，小号AS用于实现小号业务，智能AS用于实现预付费提醒业务。其中，智能AS的预付费提醒业务可以根据用户的资费状态、余额控制用户的通话业务。当用户需要进行通话时，智能AS会先计算通话费用并根据预付费账户的余额情况决定接受还是拒绝通话。另外，当用户预存的话费余额不足或者欠费时，智能AS将会基于主叫用户的号码播放对应的语音提示。如果同一用户对应多个不同的号码，则智能AS基于不同的号码生成的语音提示一般不同。因此，相对于小号业务，预付费提醒业务为对小号业务有依赖的AS业务。
在一种可能的实施场景中，当用户的主号与小号是独立计费的，也就说，主号与小号话费余额可以不同，智能AS的预付费提醒业务对应的放音指令的生成，需要依赖于小号AS生成的更改用户号码的呼叫控制指令。若智能AS直接生成(即不根据小号AS生成的更改用户号码的呼叫控制指令生成)放音指令，则预付费提醒业务对应的放音指令为根据主号的话费余额对应的语音提醒；若智能AS根据小号AS生成的更改用户号码的呼叫控制指令生成放音指令，则预付费提醒业务对应的放音指令为根据小号的话费余额对应的语音提醒。
然而，在AS业务并行触发机制下，一个AS无法基于其他AS生成的呼叫控制指令生成自己的呼叫控制指令，在有些场合下会影响用户体验；例如，上述智能AS无法根据小号AS生成的更改用户号码的呼叫控制指令生成放音指令，结果导致预付费提醒业务对应的放音指令为根据主号的话费余额对应的语音提醒，导致用户混淆了自己的两个账号的余额；因此，现有AS业务并行触发机制与用户体验对于有依赖的AS业务的需求是矛盾的，导致用户体验不好。
针对上述问题，本申请提供一种执行呼叫相关业务的方法、装置及系统，可以应用于如图1、图2等所示的通信系统。可以理解的，图1或图2所示的通信系统仅用于举例，并非用于限制本申请的技术方案。本领域的技术人员应当明白，在具体实现过程中，图1或图2所示的通信系统还可以包括其他设备，同时也可根据具体需要来确定图1中所示网元的数量，本申请对此不予限制。
可选的，本申请实施例图1或图2中的各设备可以是一个通用设备或者是一个专用设备，本申请实施例对此不作具体限定。
可选的，本申请实施例图1或图2中的各设备的相关功能可以由一个设备实现，也可以由多个设备共同实现，还可以是由一个设备内的一个或多个功能模块实现，本申请实施例对此不作具体限定。可以理解的是，上述功能既可以是硬件设备中的元件，也可以是在专用硬件上运行的软件功能，或者硬件与软件的结合，或者平台(例如，云平台)上实例化的虚拟化功能。
在具体实现时，图1或图2中的各设备都可以采用图4所示的组成结构，或者包括图4所示的部件。图4所示为可适用于本申请实施例的设备的硬件结构示意图。该设备40包括至少一个处理器401和至少一个通信接口404，用于实现本申请实施例提供的方法。该设备40还可以包括通信线路402和存储器403。
处理器401可以是一个通用中央处理器(central processing unit，CPU)，微处理器， 特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路402可包括一通路，在上述组件之间传送信息，例如总线。
通信接口404，用于与其他设备或通信网络通信。通信接口404可以是任何收发器一类的装置，如可以是以太网接口、无线接入网(radio access network，RAN)接口、无线局域网(wireless local area networks，WLAN)接口、收发器、管脚、总线、或收发电路等。
存储器403可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路402与处理器401相耦合。存储器403也可以和处理器401集成在一起。本申请实施例提供的存储器通常可以具有非易失性。
其中，存储器403用于存储执行本申请实施例提供的方案所涉及的计算机执行指令，并由处理器401来控制执行。处理器401用于执行存储器403中存储的计算机执行指令，从而实现本申请实施例提供的方法。或者，可选的，本申请实施例中，也可以是处理器401执行本申请下述实施例提供的方法中的处理相关的功能，通信接口404负责与其他设备或通信网络通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。
作为一种实施例，处理器401可以包括一个或多个CPU，例如图4中的CPU0和CPU1。
作为一种实施例，设备40可以包括多个处理器，例如图4中的处理器401和处理器407。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
作为一种实施例，设备40还可以包括输出设备405和/或输入设备406。输出设备405和处理器401耦合，可以以多种方式来显示信息。例如，输出设备405可以是液晶显示器(liquid crystal display，LCD)，发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备406和处理器401耦合，可以以多种方式接收用户的输入。例如，输入设备406可以是鼠标、键盘、触摸屏设备或传感设备等。
可以理解的，图4中示出的组成结构并不构成对该设备的限定，除图4所示部件 之外，该设备可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
下面将结合附图，对本申请实施例提供的媒体内容的投放方法进行描述。下述实施例中的各设备可以具备图4所示部件，不予赘述。
需要说明的是，本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字，本申请实施例对此不作具体限定。
需要说明的是，在本申请实施例中，“和/或”可以用于描述关联对象存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A，B可以是单数或者复数。此外，类似于“A、B和C中的至少一项”或“A、B或C中的至少一项”的表述通常用于表示如下中任一项：单独存在A；单独存在B；单独存在C；同时存在A和B；同时存在A和C；同时存在B和C；同时存在A、B和C。以上是以A、B和C共三个元素进行举例来说明该项目的可选用条目，当表述中具有更多元素时，该表述的含义可以按照前述规则获得。
为了便于描述本申请实施例的技术方案，在本申请实施例中，可以采用“第一”、“第二”等字样对功能相同或相似的技术特征进行区分。该“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。在本申请实施例中，“示例性的”或者“例如”等词用于表示例子、例证或说明，被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
可以理解的，本申请实施例中同一个步骤或者具有相同功能的步骤或者技术特征在不同实施例之间可以互相参考借鉴。
本申请提供一种执行呼叫相关业务的方法，可以应用于S-CSCF网元，或者，应用于呼叫业务使能功能(Call Service Enabler Functions，CSEF)实体或业务使能功能(Service Enabler Functions，SEF)实体。其中，CSEF/SEF实体可以在通信系统中独立部署，也可以部署于S-CSCF网元中，本申请对此不做具体限定。
下述的实施例中仅以呼叫业务使能实体CSEF实体作为示例进行说明，但所执行的方法均可应用于S-CSCF网元、SEF实体等。
下面将结合附图，详细说明本申请的实施方式。如图5所示，该方法包括如下步骤。
步骤501：CSEF实体将呼叫事件并行发送给第一AS和第二AS。
具体的，CSEF实体将呼叫事件发送给第一AS后，可以接着向第二AS发送该呼叫事件，而不需要等接收到来自第一AS的响应消息之后再发送给第二AS。
其中，CSEF实体将呼叫事件并行发送给多个AS的相关说明可以参照前述的步骤301，此处不再赘述。
在一种实施方式中，CSEF实体将呼叫事件并行发送给多个AS之前，该方法还可以包括：在用户的呼叫业务发生时，CSEF实体可以获取呼叫事件，或者，CSEF实体基于终端设备的呼叫会话消息生成呼叫事件。也就是说，CSEF实体可以基于用户呼叫 业务中的各种会话消息生成对应的呼叫事件。
示例性的，呼叫事件可以包括初始呼叫事件、通知振铃事件Ring、摘机事件Answer或释放事件Release等。
例如，在IMS网络中将CSEF实体独立部署时，CSEF实体可以从CSCF网元获取呼叫事件，该呼叫事件可以是CSCF网元根据用户的呼叫业务中的各种会话消息生成的。或者，IMS网络中将CSEF实体部署于CSCF网元中时，CSEF实体可以基于用户呼叫业务中的各种会话消息生成对应的呼叫事件。
在一种实施方式中，在用户的呼叫业务发生之前，该方法还可以包括：
CSEF实体接收来自所述多个AS的用户身份标识以及所述用户对应的呼叫事件订阅信息。
也就是说，呼叫业务发生之前，AS可以通过订阅机制，向CSEF实体上报订阅该AS业务的用户对应的用户身份标识，以及该用户对应的呼叫事件订阅信息，例如，用户身份标识具体可以为用户身份识别卡(Subscriber Identification Module，SIM)的标识号。其中，呼叫事件订阅信息可以包括初始呼叫事件的订阅信息，初始呼叫事件作为必选的上报信息，其他的呼叫事件例如振铃事件或摘机事件等可以作为可选的上报信息。从而后续在用户的呼叫业务触发的过程中，当特定的呼叫事件发生时，CSEF实体可以根据之前AS上报的订阅信息，将特定用户的特定呼叫事件发送给该AS。
示例性的，呼叫事件还可以包括订阅类型通知事件Subscribe和取消订阅事件UnSubscribe等。
具体的，接收呼叫事件的每个AS可以根据AS自身的业务逻辑，基于呼叫事件生成对应的呼叫控制指令，具体参见步骤502和步骤503。
步骤502：第一AS根据呼叫事件和AS业务逻辑生成第一呼叫控制指令，向CSEF实体发送第一呼叫控制指令。
例如，假设主叫用户购买了第一AS上的彩铃业务，则第一AS可以根据接收的振铃呼叫事件，基于彩铃业务逻辑，生成放音指令，并向CSEF实体发送该放音指令，所述放音指令用于指示CSEF实体向被叫用户设备播放主叫用户对应的彩铃内容，示例性地，CSEF实体可以触发MRF实体向被叫用户设备播放主叫用户对应的彩铃内容。
步骤503：第二AS根据呼叫事件和AS业务逻辑生成第二呼叫控制指令，向CSEF实体发送第二呼叫控制指令；可选地，第二呼叫控制指令包括关联因素变化信息。
上述两个呼叫控制指令都用于指示CSEF实体执行与呼叫业务有关的不同操作，具体是与该用户的呼叫业务有关的操作。其中，呼叫业务有关的操作是指AS基于收到的呼叫事件，为了AS业务的实现而需要CSEF实体执行的相关操作。
例如，假设主叫用户购买了第二AS上的预付费提醒业务，第二AS可以根据主叫用户的预付费提醒业务的逻辑，基于主叫用户号码查询对应的资费状态，若为欠费状态或者低余额的状态，则第二AS生成的呼叫控制指令为放音指令，所述放音指令用于指示CSEF实体向主叫用户设备播放提示音，示例性地，CSEF实体可以触发MRF实体向主叫用户播放预付费提醒对应的音频内容。
也就是，各个AS可以并行化处理同一呼叫事件，即各个AS收到同一呼叫事件后并行处理，互不依赖。
其中，不同的AS可以根据自身的业务逻辑，得到该呼叫事件对应的呼叫控制指令。例如，彩铃AS可以根据被叫用户自身的彩铃播放业务逻辑，生成指示对主叫用户放音的PlayVoice呼叫控制指令。
示例性的，呼叫控制指令具体包括呼叫新用户指令CallnewUser、释放用户指令ReleaseUser、放音指令PlayVoice、增加、修改或者删除SDP的指令SDPAction、增加、修改或者删除呼叫参数的指令ParaAction等。其中，呼叫新用户指令用于指示呼叫新用户，释放用户指令用于指示释放当前呼叫事件对应的用户，放音指令用于指示对指定用户进行放音操作，SDPAction指令用于指示对会话描述协议(Session Description Protocol，SDP)参数进行增加、修改或删除操作，ParaAction指令用于指示对呼叫参数进行增加、修改或删除操作。
需要说明的是，在本申请的实施例中，多个AS之中包括至少一个AS所提供的业务是前述的有依赖的AS业务。示例性的，被依赖方AS即第二AS，可以为小号AS，用于实现小号业务，依赖方AS即第一AS可以为智能AS，用于实现预付费提醒业务。
进一步的，第二AS发送的第二呼叫控制指令中携带关联因素变化信息，所述关联因素变化信息用于指示所述呼叫业务的关联因素发生变化。
其中，关联因素(associated factor)，即与所述呼叫业务相关的因素。在一种实施方式中，关联因素可以为第一应用服务器确定呼叫控制指令所依赖的因素之一，或者说，关联因素可以为第一应用服务器确定呼叫控制指令的输入之一。关联因素可以是主叫号码、被叫号码、资费状态或使用编解码等中的任一个。示例性的，关联因素具体的可以是呼叫业务相关联的某一参数，如主叫用户caller，被叫用户called等；或者，关联因素可以是呼叫业务相关联的运行状态，如用户对应的资费状态等。
在一种实施方式中，若关联因素变化信息中包括所述呼叫业务对应的第一参数发生变化的指示，则关联因素变化信息还可以包括所述第一参数变化后的值。
例如，小号AS可以根据自身的小号业务逻辑，发送的呼叫控制指令具体可以为修改呼叫参数的指令ParaAction。其中，ParaAction指令中可以包括指示呼叫参数caller发生变化的信息。即小号AS对应的ParaAction指令中的关联因素变化信息指示第一参数发生变化，即第一参数为caller，ParaAction指令中包括parachg：caller。则关联因素变化信息还可以包括caller变化后的值，例如caller变更为主叫用户的小号C，具体可以为ParaAction指令中包括caller：C。
或者，在另一种实施方式中，CSEF实体可以本地预先配置有第一参数可能的值，则CSEF实体可以根据本地配置以及关联因素变化信息确定第一参数变化后的值。例如，CSEF实体本地配置的第一参数caller的可能值为B或C，呼叫会话对应的caller一开始为B。则CSEF实体根据ParaAction指令中包括parachg：caller，可以确定第一参数caller变化后的值为C。
在一种实施方式中，AS与CSEF实体之间的信息交互，可以通过应用层的消息进行交互，例如，基于超文本传输协议(HyperText Transfer Protocol，HTTP)的消息，或者简单邮件传输协议(Simple Mail Transfer Protocol，SMTP)的消息或者其他类型的传输消息等。本申请的实施例对信息交互的格式和类型不做具体限定。
示例性的，CSEF实体向AS发送的呼叫事件，可以承载于HTTP请求消息，具体 可以承载于HTTP请求消息的URL中，也可以承载于HTTP请求消息的头字段，还可以承载于HTTP请求消息的消息体。以承载于HTTP请求消息的消息体为例，用于发送呼叫事件的示例性HTTP请求消息如下：
另外，在一种可能的实施例中，第二AS向CSEF实体发送的关联因素变化信息可以是单独发送的，即第二AS不是在第二呼叫控制指令中携带关联因素变化信息，而是在发送第二呼叫控制指令之前或之后，向CSEF实体发送关联因素变化信息。
至此，CSEF实体接收了两个呼叫控制指令。
在一种可能的实施方式中，步骤503中的第二呼叫控制指令不包括关联因素变化信息，为使CSEF实体有机会接收第三呼叫控制指令，CSEF实体可以进入等待状态(最大等待时长可以是预先设置的)，这样在等待期间，CSEF实体可以跳过步骤504直接执行步骤505，以接收第三呼叫控制指令。可选地，如果等待超过预先设置的等待时长未收到第三呼叫控制指令，CSEF实体可以直接并行执行第一呼叫控制指令和第二呼叫控制指令。
在另一种可能的实施方式中，步骤503中的第二呼叫控制指令包含关联因素变化 信息，则CSEF实体可接着执行步骤504。
步骤504：CSEF实体根据关联因素变化信息向第一AS发送指令更新指示信息。
该步骤为可选。CSEF实体接收到多个AS发送的呼叫控制指令如第一呼叫控制指令和第二呼叫控制指令之后，可以根据第二呼叫控制指令中携带的关联因素变化信息确定是否触发第一AS重新发送呼叫控制指令，具体的，可以为向第一AS发送指令更新指示信息，用于指示第一应用服务器重新发送呼叫控制指令，以便将第一AS重新发送的呼叫控制指令替换之前第一AS发送的第一呼叫控制指令，从而再完成更新后指令的执行操作。
具体的，CSEF实体根据关联因素变化信息确定是否触发第一AS重新发送呼叫控制指令，可以根据第二AS发送的关联因素变化信息与第一AS对应的关联因素是否匹配来确定。
其中，第一AS对应的关联因素是指第一AS感兴趣的关联因素，即第一AS的业务执行所依赖的关联因素。也就是说，该呼叫业务对应的关联因素可以作为第一AS确定呼叫控制指令的输入之一。示例性的，若第一AS为彩铃AS，则彩铃AS确定呼叫控制指令即放音指令的多个输入可以包括主叫用户号码、被叫用户号码等，其中，彩铃AS对应的关联因素可以为多个输入中的被叫号码这一输入，即彩铃AS发送放音指令时对于被叫用户号码这一关联因素的变化是感兴趣的，不同的被叫用户号码对应的放音指令一般不同。
具体的，若第二AS发送的关联因素变化信息与第一AS对应的关联因素相匹配，则CSEF实体确定触发第一AS重新发送呼叫控制指令；若第二AS发送的关联因素变化信息与第一AS对应的关联因素不匹配，则CSEF实体确定不触发第一AS重新发送呼叫控制指令。
在一种实施方式中，为了让CSEF实体提前感知依赖方AS所感兴趣的关联因素，CSEF实体将呼叫事件并行发送给第一AS和第二AS之前，该方法还包括：CSEF实体获取第一AS对应的至少一个关联因素。
也就是说，CSEF实体可以获取确定呼叫控制指令的输入之一的呼叫业务的关联因素。
示例性的，第一AS对应的关联因素具体可以为第一AS感兴趣的特定参数变化，例如可以包括参数的修改、删除和新增等；或者，关联因素可以为业务运行状态如资费状态等。
在一种实施方式中，CSEF实体获取第一AS对应的关联因素可以通过本地配置的方式即静态方式，或者可以通过动态方式配置。
其中，静态配置即指在呼叫业务发生前，CSEF实体从本地或其他CSEF实体可以访问的设备读取预先配置的依赖方AS相关联的关联因素。
其中，动态方式配置是指，CSEF实体通过第一AS动态上报的信息中获取第一AS对应的关联因素。具体可以包括：
Step 1：第一AS向CSEF实体发送订阅请求，订阅请求包括第一AS确定呼叫控制指令所依赖的至少一个关联因素。
其中，订阅请求用于第一AS向CSEF实体请求订阅至少一个关联因素的变化情 况，即第一AS对于该至少一个关联因素的变化感兴趣，若CSEF实体确定该至少一个关联因素有变化，则可以向第一AS发送通知消息，例如关联因素变化信息，以使得第一AS获得所述至少一个关联因素的变化。
在一种实施方式中，订阅请求中还可以包括用户身份标识，用于指示该呼叫业务对应的用户。
Step 2：CSEF实体接收第一AS对应的至少一个关联因素。
具体的，CSEF实体可以通过接收来自第一AS的订阅请求，获取订阅请求中携带的第一AS对应的至少一个关联因素。
在一种实施方式中，CSEF实体可以接收第一AS对应的关联因素并存储，生成不同AS与对应关联因素的对应关系，以便后续可以查询，识别出是否存在第一AS感兴趣的关联因素对应的变化。具体的，CSEF实体可以根据第二AS发送的关联因素变化信息中包括的关联因素，查询并识别出该关联因素与第一AS对应的关联因素相匹配。
在一种实现方式中，指令更新指示信息包括所述关联因素的关联因素变化信息或所述至少一个关联因素。
其中，CSEF实体根据关联因素变化信息向第一AS发送指令更新指示信息，以触发第一AS重新发送呼叫控制指令的实现方式具体包括：
方式1、CSEF实体向第一AS发送关联因素变化信息，用于指示第一AS重新发送呼叫控制指令。
也就是说，CSEF实体可以将第二控制指令中携带的关联因素变化信息提取出来并转发至第一AS，从而指示第一AS重新发送呼叫控制指令。
方式2、CSEF实体根据关联因素变化信息向第一AS发送指令更新指示信息或者变化事件，用于指示第一AS重新发送呼叫控制指令。
也就是说，CSEF实体可以将第二控制指令中携带的关联因素变化信息提取出来，并根据关联因素变化信息重新生成指令更新指示信息，所述指令更新指示信息中可以包括所述关联因素变化信息中指示的关联因素。或者，CSEF实体可以根据关联因素变化信息生成对应的变化事件，从而所述指令更新指示信息或者变化事件用于指示第一AS重新发送呼叫控制指令。
在一种具体的实施方式中，CSEF实体根据关联因素变化信息向第一应用服务器发送指令更新指示信息或变化事件，具体可以包括：
CSEF实体根据关联因素变化信息查询第一AS对应的关联因素，例如，查询CSEF实体本地静态配置的或者动态获取的第一AS对应的关联因素。若关联因素变化信息中指示的关联因素与所述第一AS对应的关联因素相匹配，则向第一应用服务器发送指令更新指示信息或变化事件。
在一种可能的实施方式中，CSEF实体通过呼叫指令更新请求消息向第一AS发送指令更新指示信息或变化事件，即CSEF实体向第一AS发送指令更新请求消息，该请求消息包含上述指令更新指示信息或者变化事件。
可以理解，上述消息名称“呼叫指令更新请求消息”是示例性的，而非限定。
步骤505：第一AS向CSEF实体发送第三呼叫控制指令，第三呼叫控制指令用于替代第一呼叫控制指令。
其中，第三呼叫控制指令用于替代第一呼叫控制指令，也就是说，CSEF实体可以将第三呼叫控制指令替换掉或者覆盖掉之前的第一呼叫控制指令，并将第一呼叫控制指令进行删除。
在一种可能的实施方式中，第一AS可以根据CSEF实体的触发，向CSEF实体重新发送呼叫控制指令，即第三呼叫控制指令，这种情况下，第一AS可以通过呼叫指令更新响应消息(即上述呼叫指令更新请求消息对应的响应消息)向CSEF实体发送第三呼叫控制指令，即第一AS向CSEF实体发送呼叫指令更新响应消息，该响应消息包含第三呼叫控制指令；可选地，该响应消息还包含第一呼叫控制指令的相关信息，如第一呼叫控制指令的发送时间戳、标识甚至是第一呼叫控制指令的内容本身，以使CSEF实体确定第三呼叫控制指令是用于替换第一呼叫控制指令的；
在另一种可能的实施方式中，第一AS也可以根据其他因素(例如，从第二AS接收到关联因素变化信息)的触发向CSEF实体发送第三呼叫控制指令，向CSEF实体发送第三呼叫控制指令，这种情况下，第一AS可以通过呼叫指令更新通知消息向CSEF实体发送第三呼叫控制指令，即第一AS向CSEF实体发送呼叫指令更新通知消息，该通知消息包含第三呼叫控制指令；可选地，该通知消息还可以包含第一呼叫控制指令的有关信息，如第一呼叫控制指令的时间戳、标识甚至是第一呼叫控制指令的内容本身，以使CSEF实体确定第三呼叫控制指令是用于替换第一呼叫控制指令的。
可以理解，上述消息名称“呼叫指令更新响应消息”、“呼叫指令更新通知消息”是示例性的，而非限定。
示例性的，指令更新指示信息或者变化事件用于指示第一参数发生变化，或者，其中还包括第一参数变化后的值，则第三呼叫控制指令是第一AS根据第一参数变化后的值生成的。
步骤506：CSEF实体并行执行第二呼叫控制指令和第三呼叫控制指令。
也就是说，CSEF实体并行执行第二呼叫控制指令和第三呼叫控制指令，而不执行第一呼叫控制指令。
需要说明的是，CSEF实体接收到第一AS发送的第一呼叫控制指令和第二AS发送的第二呼叫控制指令之后，CSEF实体不会立即执行第一呼叫控制指令和第二呼叫控制指令，而是先判断第二AS发送的第二呼叫控制指令中携带的关联因素变化信息是否与本地存储的第一AS对应的关联因素进行匹配，从而CSEF实体可以根据匹配结果决策是否需要触发第一AS重新发送呼叫控制指令。若匹配结果为成功，CSEF实体确定需要触发第一AS重新发送呼叫控制指令，则CSEF实体不会并行执行第一呼叫控制指令和第二呼叫控制指令，而是等待第一AS发送新的呼叫控制指令即第三呼叫控制指令之后，再并行执行第三呼叫控制指令和第二呼叫控制指令，从而满足有依赖的AS业务的用户体验需求；若匹配结果为失败，则CSEF实体确定不需要触发第一AS重新发送呼叫控制指令，CSEF实体并行执行第一呼叫控制指令和第二呼叫控制指令。
在一种实施方式中，CSEF实体可以向第一AS及第二AS发送指令处理成功响应，用于向AS指示该AS对应发送的呼叫控制指令执行成功。
示例性的，下面以预付费提醒业务与小号业务作为示例说明AS并行处理的流程。如图6所示，第一AS为智能AS，第二AS为小号业务对应的小号AS。该方法可以包括如下步骤。
步骤600：智能AS向CSEF实体发送订阅请求。
订阅请求用于智能AS向CSEF实体上报智能AS感兴趣的关联因素，以请求订阅该关联因素的变化。例如，订阅请求具体可以为subscribe request消息。
其中，该订阅请求中可以携带指示智能AS感兴趣的关联因素parachg为主叫用户标识caller，即subscribe request包括parachg：caller。
示例性的，AS向CSEF实体发送的订阅请求可以承载于HTTP请求消息，HTTP请求消息如下：
步骤601：CSEF实体并行向小号AS和智能AS发送呼叫事件。
其中，呼叫事件可以是初始呼叫事件(如initcall request)，所述初始呼叫事件对应的主叫用户号码为A，被叫用户号码为B。例如，initcall request中携带呼叫参数，即主叫用户号码caller，即initcall request中包括caller：A，called(被叫用户)：B。其中主叫用户购买了小号业务，即主叫用户的主号为138138，小号可以为123123。
步骤602：智能AS向CSEF实体发送主号对应的放音指令。
其中，智能AS根据自身的预付费提醒业务的触发逻辑，生成基于主叫用户号码对应的呼叫控制指令，即PlayVoice放音指令。进一步的，该呼叫控制指令PlayVoice中还可以包括音频媒体资源的统一资源定位符(Uniform Resource Locator，URL)，用于指示CSEF实体根据该URL确定主号对应的音频资源。
步骤603：小号AS向CSEF实体发送修改呼叫参数的指令。
相应的，小号AS根据自身的小号业务逻辑，发送的呼叫控制指令具体可以为修改呼叫参数的指令ParaAction。其中，ParaAction指令中可以包括指示呼叫参数caller发生变化的关联因素变化信息。例如，ParaAction指令中携带关联因素变化信息parachg：caller，用于指示呼叫业务对应的关联因素caller发生变化。
其中，小号AS对应的ParaAction指令中的关联因素变化信息指示第一参数caller发生变化，ParaAction指令中包括parachg：caller。
例如，AS向CSEF实体发送的ParaAction指令可以承载于HTTP响应消息，消息结构如下：
进一步的，关联因素变化信息还可以包括caller变化后的值，例如caller变更为主叫用户的小号123123，具体可以为ParaAction指令中包括caller：123123。
例如，ParaAction指令中包括：
或者，在另一种实施方式中，CSEF实体可以本地预先配置有第一参数可能的值，则CSEF实体可以根据本地配置以及关联因素变化信息确定第一参数变化后的值。例如，CSEF实体本地配置的第一参数caller的可能值为A或C，呼叫会话对应的caller一开始为A。则CSEF实体根据ParaAction指令中包括parachg：caller，可以确定第一参数caller变化后的值为C。
步骤604：CSEF实体向智能AS发送变化事件。
其中，CSEF实体可以根据小号AS发送的ParaAction指令中携带的parachg：caller，识别到该参数caller与步骤600中智能AS向CSEF实体发送订阅请求中包括的关联因素相匹配，则生成变化事件(ParaChg request事件)，并向第一AS发送ParaChg request事件，指示智能AS重新发送呼叫控制指令。其中，ParaChg request事件中携带指示当前发生变化的关联因素为第一参数，即caller。
进一步的，变化事件ParaChg request中携带当前发生变化的第一参数caller，还包括caller变化为C，即caller：C。
示例性地，CSEF实体向智能AS发送呼叫指令更新请求消息，该请求消息包含上述变化事件。
步骤605：智能AS根据变化事件向CSEF实体发送小号对应的放音指令。
智能AS根据变化事件重新生成小号(caller：C)对应的放音指令，并向CSEF实体发送该小号对应的放音指令。
其中，该放音指令用于替换之前步骤602中智能AS向CSEF实体发送的基于主号号码生成的放音指令。
示例性地，智能AS向CSEF实体发送呼叫指令更新响应消息，即步骤604呼叫指令更新请求消息对应的响应消息，该响应消息包含上述重新生成的放音指令。
步骤606：CSEF实体并行执行修改呼叫参数的指令以及小号对应的放音指令。
在一种实施方式中，CSEF实体执行修改呼叫参数的指令，具体可以为CSEF实体根据修改呼叫参数的指令中指示的呼叫参数，将呼叫控制块中的所述呼叫参数进行变更。例如，修改呼叫参数的指令ParaAction指示呼叫参数caller发生变化，则CSEF实体将呼叫控制块中的呼叫参数caller变更为预设值，或者，根据ParaAction指令中指示的caller变化后的值C，将呼叫控制块中的呼叫参数caller变更为C。后续，CSEF实体发送消息中携带的呼叫参数caller即为变更后的值。
具体的，CSEF实体执行修改呼叫参数的指令完成之后，可以向小号AS发送指令执行成功响应，用于指示修改呼叫参数的指令成功执行。
另外，CSEF实体执行小号对应的放音指令，即根据放音指令，指示MRF实体为主叫用户播放小号对应的预付费提示音频资源。
例如，预付费提醒业务基于主号号码(caller：A)生成的提示音频文件为音频1，基于小号号码(caller：C)生成的提示音频文件为音频2，不同音频文件对应的URL一般不同。则步骤605中的放音指令用于替换智能业务为主叫用户播放的预付费提示音频资源，从而在主叫用户用小号号码呼叫被叫用户的场景中，CSEF实体通过变化事件指示智能AS重新发送基于小号的呼叫控制指令，从而为用户播放准确的提示音频，符合业务实现的需求。
在一种实施方式中，CSEF实体执行放音指令的具体过程可以包括：
步骤607：CSEF实体触发MRF实体向主叫用户设备放音。
具体地，CSEF实体与MRF实体之间进行信令交互，触发MRF实体建立MRF实体与主叫用户设备之间的音频媒体通道，向MRF实体发送音频资源的URL，以使MRF实体通过所创建的音频媒体通道向主叫用户设备播放该音频资源。
步骤608：MRF实体与主叫用户设备进行交互，执行放音操作。
MRF实体通过所创建的音频媒体通道向主叫用户设备推送音频资源，主叫用户设备在获取到该音频资源后，播放该音频资源。
在一种实施方式中，放音指令成功开始执行后，MRF实体可以向CSEF实体发送放音成功响应，另外，CSEF实体可以向智能AS发送PlayVoice指令对应的指令执行成功响应。
上述实施方式，CSEF实体可以通过被依赖方AS(比如小号AS)在发送的呼叫控制指令中，携带的关联因素发生变化的指示，识别出与依赖方关联因素匹配，则CSEF实体可以向依赖方AS上报关联因素发生变化的指示或者特定的变化事件，从而触发依赖方AS根据关联因素的变化，重新发送新的呼叫控制指令，以刷新AS的业务状态，从而满足用户体验对有依赖的AS业务的需求。
上述主要从各个设备之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的，上述的呼叫业务使能实体为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法操作，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对呼叫业务使能实体进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，以采用集成的方式划分各个功能模块的情况下，本申请还提供一种通信装置，用于实现前述的执行呼叫相关业务的方法中呼叫业务使能实体CSEF实体所述执行的步骤。
如图7所示，该装置700包括发送模块701和接收模块702。发送模块701和接收模块702也可以称集成为收发模块，用以实现收发功能，例如可以是收发电路，收发机，收发器或者通信接口。
进一步的，该装置700还可以包括处理模块703。
其中，发送模块701用于将呼叫事件并行发送给第一应用服务器和第二应用服务器，发送模块701还用于根据关联因素变化信息向第一应用服务器发送指令更新指示信息等本申请上述实施例中CSEF实体侧发送数据/信息的操作，如步骤501、步骤504。
接收模块702用于从第一应用服务器接收第一呼叫控制指令以及从第二应用服务器接收第二呼叫控制指令，接收模块702还用于从第一应用服务器接收第三呼叫控制指令等本申请上述实施例中CSEF实体侧接收数据/信息的操作，如步骤502、步骤503和步骤505。
处理模块703用于并行执行第二呼叫控制指令和第三呼叫控制指令等本申请上述实施例中CSEF实体侧除接收和发送数据或信息之外的操作，如步骤506。
相对应的，本申请还提供一种通信装置，用于实现前述的执行呼叫相关业务的方法中第一应用服务器所述执行的步骤。
如图7所示，该装置700包括发送模块701和接收模块702。发送模块701和接收模块702也可以称集成为收发模块，用以实现收发功能，例如可以是收发电路，收发机，收发器或者通信接口。
其中，接收模块702用于接收来自呼叫业务使能实体的呼叫事件，接收模块702 还用于接收所述呼叫业务使能实体根据关联因素变化信息发送的指令更新指示信息等本申请上述实施例中第一应用服务器侧接收数据/信息的操作，如步骤501和步骤504。
发送模块701用于根据呼叫事件向呼叫业务使能实体发送第一呼叫控制指令，发送模块701还用于向呼叫业务使能实体发送第三呼叫控制指令等本申请上述实施例中第一应用服务器侧发送数据/信息的操作，如步骤502、步骤505。
在一个简单的实施例中，本领域的技术人员可以想到上述的通信装置700可以采用图4所示的形式。比如，图4中的处理器401可以通过调用存储器403中存储的计算机执行指令，使得通信装置700执行上述方法实施例中呼叫业务使能实体与第一应用服务器执行的所述的方法。
示例性的，图7中的发送模块701和接收模块702的功能/实现过程可以通过图4中的处理器401调用存储器403中存储的计算机执行指令来实现。或者，图7中的处理模块703的功能/实现过程可以通过图4中的处理器401调用存储器403中存储的计算机执行指令来实现，图7中的发送模块701和接收模块702的功能/实现过程可以通过图4中的通信接口404来实现。
需要说明的是，以上模块或单元的一个或多个可以软件、硬件或二者结合来实现。当以上任一模块或单元以软件实现的时候，所述软件以计算机程序指令的方式存在，并被存储在存储器中，处理器可以用于执行所述程序指令并实现以上方法流程。该处理器可以内置于SoC(片上系统)或ASIC，也可是一个独立的半导体芯片。该处理器内处理用于执行软件指令以进行运算或处理的核外，还可进一步包括必要的硬件加速器，如现场可编程门阵列(field programmable gate array，FPGA)、PLD(可编程逻辑器件)、或者实现专用逻辑运算的逻辑电路。
当以上模块或单元以硬件实现的时候，该硬件可以是CPU、微处理器、数字信号处理(digital signal processing，DSP)芯片、微控制单元(microcontroller unit，MCU)、人工智能处理器、ASIC、SoC、FPGA、PLD、专用数字电路、硬件加速器或非集成的分立器件中的任一个或任一组合，其可以运行必要的软件或不依赖于软件以执行以上方法流程。
可选的，本申请实施例还提供了一种芯片系统，包括：至少一个处理器和接口，该至少一个处理器通过接口与存储器耦合，当该至少一个处理器执行存储器中的计算机程序或指令时，使得上述任一方法实施例中的方法被执行。在一种可能的实现方式中，该芯片系统还包括存储器。可选的，该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
可选的，本申请实施例还提供了一种计算机可读存储介质。上述方法实施例中的全部或者部分流程可以由计算机程序来指令相关的硬件完成，该程序可存储于上述计算机可读存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。计算机可读存储介质可以是前述任一实施例的通信装置的内部存储单元，例如通信装置的硬盘或内存。上述计算机可读存储介质也可以是上述通信装置的外部存储设备，例如上述通信装置上配备的插接式硬盘，智能存储卡(smart media card，SMC)，安全数字(secure digital，SD)卡，闪存卡(flash card)等。进一步地，上述计算机可读存储介质还可以既包括上述通信装置的内部存储单元也包括外部存储设备。上述计算机可 读存储介质用于存储上述计算机程序以及通信装置所需的其他程序和数据。上述计算机可读存储介质还可以用于暂时地存储已经输出或者将要输出的数据。
可选的，本申请实施例还提供了一种计算机程序产品。上述方法实施例中的全部或者部分流程可以由计算机程序来指令相关的硬件完成，该程序可存储于上述计算机程序产品中，该程序在执行时，可包括如上述各方法实施例的流程。
可选的本申请实施例还提供了一种计算机指令。上述方法实施例中的全部或者部分流程可以由计算机指令来指令相关的硬件(如计算机、处理器、接入网设备、移动性管理网元或会话管理网元等)完成。该程序可被存储于上述计算机可读存储介质中或上述计算机程序产品中。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (39)

  1. 一种执行呼叫相关业务的方法，应用于呼叫业务使能实体，其特征在于，所述方法包括：
    将呼叫事件并行发送给第一应用服务器和第二应用服务器；
    从所述第一应用服务器接收第一呼叫控制指令以及从所述第二应用服务器接收第二呼叫控制指令；
    从所述第一应用服务器接收第三呼叫控制指令，所述第三呼叫控制指令用于替代所述第一呼叫控制指令；
    并行执行所述第二呼叫控制指令和所述第三呼叫控制指令。
  2. 根据权利要求1所述的方法，其特征在于，所述第二呼叫控制指令中包括关联因素变化信息，所述关联因素变化信息用于指示呼叫业务的至少一个关联因素发生变化，所述至少一个关联因素为所述第一应用服务器确定呼叫控制指令所依赖的因素。
  3. 根据权利要求2所述的方法，其特征在于，所述关联因素包括所述呼叫业务对应的参数，和/或所述呼叫业务的状态。
  4. 根据权利要求2或3所述的方法，其特征在于，所述将呼叫事件并行发送给第一应用服务器和第二应用服务器之前，所述方法还包括：
    获取所述第一应用服务器对应的所述至少一个关联因素。
  5. 根据权利要求2-4任一项所述的方法，其特征在于，在从所述第一应用服务器接收第三呼叫控制指令之前，所述方法还包括：
    根据所述关联因素变化信息向所述第一应用服务器发送指令更新指示信息，所述指令更新指示信息用于指示所述第一应用服务器重新发送呼叫控制指令。
  6. 根据权利要求5所述的方法，其特征在于：所述指令更新指示信息包括所述关联因素变化信息或所述至少一个关联因素。
  7. 根据权利要求5或6所述的方法，其特征在于，根据所述关联因素变化信息向所述第一应用服务器发送指令更新指示信息，具体包括：
    根据所述关联因素变化信息查询所述第一应用服务器对应的关联因素，若所述关联因素变化信息中指示的关联因素与所述第一应用服务器对应的关联因素相匹配，则向所述第一应用服务器发送指令更新指示信息。
  8. 根据权利要求5-7任一项所述的方法，其特征在于，若所述关联因素变化信息中包括所述呼叫业务对应的第一参数发生变化，则所述关联因素变化信息包括所述第一参数变化后的值。
  9. 根据权利要求5-8任一项所述的方法，其特征在于，若所述指令更新指示信息中包括所述呼叫业务对应的第一参数发生变化，则所述指令更新指示信息中包括所述第一参数变化后的值。
  10. 根据权利要求9所述的方法，其特征在于，所述第三呼叫控制指令是所述第一应用服务器根据所述第一参数变化后的值生成的。
  11. 根据权利要求1-10任一项所述的方法，其特征在于，所述呼叫业务使能实体部署于呼叫会话控制功能CSCF网元或者统一控制功能UCF网元。
  12. 根据权利要求1-11任一项所述的方法，其特征在于，将呼叫事件并行发送给第 一应用服务器和第二应用服务器之前，所述方法还包括：
    基于终端设备的呼叫会话消息生成所述呼叫事件。
  13. 一种执行呼叫相关业务的方法，应用于应用服务器，其特征在于，所述方法包括：
    接收来自呼叫业务使能实体的呼叫事件；
    根据所述呼叫事件向所述呼叫业务使能实体发送第一呼叫控制指令；
    向所述呼叫业务使能实体发送第三呼叫控制指令，所述第三呼叫控制指令用于替代所述第一呼叫控制指令。
  14. 根据权利要求13所述的方法，其特征在于，在向所述呼叫业务使能实体发送第三呼叫控制指令之前，所述方法还包括：
    从所述呼叫业务使能实体接收关联因素变化信息，所述关联因素变化信息用于指示呼叫业务的至少一个关联因素发生变化，所述至少一个关联因素为所述应用服务器确定呼叫控制指令所依赖的因素。
  15. 根据权利要求14所述的方法，其特征在于，所述关联因素包括所述呼叫业务对应的参数，和/或所述呼叫业务的状态。
  16. 根据权利要求14或15所述的方法，其特征在于，接收来自所述呼叫业务使能实体的呼叫事件之前，所述方法还包括：
    向所述呼叫业务使能实体发送所述应用服务器对应的所述至少一个关联因素。
  17. 根据权利要求13-16任一项所述的方法，其特征在于，在向所述呼叫业务使能实体发送第三呼叫控制指令之前，所述方法还包括：
    接收来自所述呼叫业务使能实体的指令更新指示信息，所述指令更新指示信息用于指示所述应用服务器重新发送呼叫控制指令。
  18. 根据权利要求17所述的方法，其特征在于，所述指令更新指示信息包括关联因素变化信息或至少一个关联因素。
  19. 根据权利要求17或18所述的方法，其特征在于，若所述指令更新指示信息中包括所述呼叫业务对应的第一参数发生变化，则所述指令更新指示信息中包括所述第一参数变化后的值。
  20. 根据权利要求19所述的方法，其特征在于，所述第三呼叫控制指令是所述应用服务器根据所述第一参数变化后的值生成的。
  21. 根据权利要求13-20任一项所述的方法，其特征在于，所述呼叫业务使能实体部署于呼叫会话控制功能CSCF网元或者统一控制功能UCF网元。
  22. 一种通信装置，其特征在于，所述装置包括用于执行如权利要求1-12中任一项所述的方法的模块。
  23. 一种通信装置，其特征在于，所述装置包括用于执行如权利要求13-21中任一项所述的方法的模块。
  24. 一种通信装置，其特征在于，所述装置包括处理器，所述处理器用于执行如权利要求1-12或者13-21中任意一项所述的方法。
  25. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机程序，当所述计算机程序被计算机执行时使得所述计算机执行权利要求1-12或者 13-21中任一项所述的方法。
  26. 一种计算机程序产品，其特征在于，所述计算机程序产品存储有指令，当所述指令被计算机执行，使得如权利要求1-12或者13-21中任一项所述的方法被实现。
  27. 一种通信系统，其特征在于，所述通信系统包括如权利要求22所述的通信装置和权利要求23所述的通信装置。
  28. 一种执行呼叫相关业务的方法，其特征在于，所述方法包括：
    呼叫业务使能实体将呼叫事件并行发送给第一应用服务器和第二应用服务器；
    所述第一应用服务器根据所述呼叫事件向所述呼叫业务使能实体发送第一呼叫控制指令，所述第二应用服务器根据所述呼叫事件向所述呼叫业务使能实体发送第二呼叫控制指令；
    所述第一应用服务器向所述呼叫业务使能实体发送第三呼叫控制指令，所述第三呼叫控制指令用于替代所述第一呼叫控制指令；
    所述呼叫业务使能实体并行执行所述第二呼叫控制指令和所述第三呼叫控制指令。
  29. 根据权利要求28所述的方法，其特征在于，所述第二呼叫控制指令中包括关联因素变化信息，所述关联因素变化信息用于指示呼叫业务的至少一个关联因素发生变化，所述至少一个关联因素为所述第一应用服务器确定呼叫控制指令所依赖的因素。
  30. 根据权利要求29所述的方法，其特征在于，所述关联因素包括所述呼叫业务对应的参数，和/或所述呼叫业务的状态。
  31. 根据权利要求29或30所述的方法，其特征在于，所述呼叫业务使能实体将呼叫事件并行发送给第一应用服务器和第二应用服务器之前，所述方法还包括：
    所述呼叫业务使能实体获取所述第一应用服务器对应的所述至少一个关联因素。
  32. 根据权利要求29-31任一项所述的方法，其特征在于，所述第一应用服务器向所述呼叫业务使能实体发送第三呼叫控制指令之前，所述方法还包括：
    所述呼叫业务使能实体根据所述关联因素变化信息向所述第一应用服务器发送指令更新指示信息，所述指令更新指示信息用于指示所述第一应用服务器重新发送呼叫控制指令。
  33. 根据权利要求32所述的方法，其特征在于：所述指令更新指示信息包括所述关联因素变化信息或所述至少一个关联因素。
  34. 根据权利要求32或33所述的方法，其特征在于，所述呼叫业务使能实体根据所述关联因素变化信息向所述第一应用服务器发送指令更新指示信息，具体包括：
    所述呼叫业务使能实体根据所述关联因素变化信息查询所述第一应用服务器对应的关联因素，若所述关联因素变化信息中指示的关联因素与所述第一应用服务器对应的关联因素相匹配，则向所述第一应用服务器发送指令更新指示信息。
  35. 根据权利要求32-34任一项所述的方法，其特征在于，若所述关联因素变化信息中包括所述呼叫业务对应的第一参数发生变化，则所述关联因素变化信息包括所述第一参数变化后的值。
  36. 根据权利要求32-35任一项所述的方法，其特征在于，若所述指令更新指示信息中包括所述呼叫业务对应的第一参数发生变化，则所述指令更新指示信息中包括所述第一参数变化后的值。
  37. 根据权利要求36所述的方法，其特征在于，所述第三呼叫控制指令是所述第一应用服务器根据所述第一参数变化后的值生成的。
  38. 根据权利要求28-37任一项所述的方法，其特征在于，所述呼叫业务使能实体部署于呼叫会话控制功能CSCF网元或者统一控制功能UCF网元。
  39. 根据权利要求28-38任一项所述的方法，其特征在于，所述呼叫业务使能实体将呼叫事件并行发送给第一应用服务器和第二应用服务器之前，所述方法还包括：
    所述呼叫业务使能实体基于终端设备的呼叫会话消息生成所述呼叫事件。
PCT/CN2023/078561 2022-02-28 2023-02-27 一种执行呼叫相关业务的方法、装置及系统 WO2023160715A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210212015.9A CN116708380A (zh) 2022-02-28 2022-02-28 一种执行呼叫相关业务的方法、装置及系统
CN202210212015.9 2022-02-28

Publications (1)

Publication Number Publication Date
WO2023160715A1 true WO2023160715A1 (zh) 2023-08-31

Family

ID=87764897

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/078561 WO2023160715A1 (zh) 2022-02-28 2023-02-27 一种执行呼叫相关业务的方法、装置及系统

Country Status (2)

Country Link
CN (1) CN116708380A (zh)
WO (1) WO2023160715A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070118662A1 (en) * 2005-11-23 2007-05-24 Vishwanathan Kumar K Systems and methods for providing concurrent mobile applications to mobile communication devices
CN101330449A (zh) * 2007-07-02 2008-12-24 中兴通讯股份有限公司 一种ip多媒体子系统业务交互的实现方法
CN102651732A (zh) * 2011-02-24 2012-08-29 中国移动通信集团公司 一种ims网络中的业务触发方法和系统
CN110062118A (zh) * 2019-04-23 2019-07-26 深圳市大众通信技术有限公司 一种小号并发呼出多个不同用户方法及系统
CN112887496A (zh) * 2019-11-30 2021-06-01 华为技术有限公司 一种呼叫处理系统、呼叫处理方法以及通信装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070118662A1 (en) * 2005-11-23 2007-05-24 Vishwanathan Kumar K Systems and methods for providing concurrent mobile applications to mobile communication devices
CN101330449A (zh) * 2007-07-02 2008-12-24 中兴通讯股份有限公司 一种ip多媒体子系统业务交互的实现方法
CN102651732A (zh) * 2011-02-24 2012-08-29 中国移动通信集团公司 一种ims网络中的业务触发方法和系统
CN110062118A (zh) * 2019-04-23 2019-07-26 深圳市大众通信技术有限公司 一种小号并发呼出多个不同用户方法及系统
CN112887496A (zh) * 2019-11-30 2021-06-01 华为技术有限公司 一种呼叫处理系统、呼叫处理方法以及通信装置

Also Published As

Publication number Publication date
CN116708380A (zh) 2023-09-05

Similar Documents

Publication Publication Date Title
KR100899756B1 (ko) 통신 시스템에서 멀티미디어 포탈 컨텐츠 제공 방법 및시스템
US8565267B2 (en) Web based unified communication system and method, and web communication manager
US20100190478A1 (en) System and method for push-to-share file distribution with previews
US20070223462A1 (en) Enhanced service delivery platform that provides a common framework for use by IMS and Web applications in delivering services
US8612568B2 (en) Method, system and network server for recording use of network service capability by applications
CN109617990B (zh) 一种融合通信资源云共享方法及系统
CN101217533B (zh) 同步大头像的方法及实现该方法的群组服务器和终端
CN111510414A (zh) 一种内容发送方法、接收方法和装置
CN109314947A (zh) 设备和/或线路事件感知和智能同步
CN109246301A (zh) 多sim卡管理方法、装置、计算机装置及计算机存储介质
WO2012113331A1 (zh) 一种ims网络中的业务触发方法、系统、计算机程序和存储介质
CN101159910B (zh) 同步呈现状态的方法及实现该方法的群组服务器和终端
CN113556783B (zh) 媒体资源传输方法、相关装置及系统
US20130122872A1 (en) Apparatus and method for push-to-share file distribution with previews
US20070220162A1 (en) Media processing abstraction model
WO2023160715A1 (zh) 一种执行呼叫相关业务的方法、装置及系统
EP2941856A1 (en) Apparatus and method for push-to-share file distribution with previews
US9049310B2 (en) Data communication
WO2023109897A1 (zh) 一种执行呼叫相关业务的方法及装置
WO2024066541A1 (zh) 通信方法、装置及系统
CN112261490B (zh) 视频分享方法及装置、应用功能实体、拨号软件系统
US20140189795A1 (en) Method and Apparatus for Conducting Service by Service Delivery Platform
WO2023011024A1 (zh) 不良电话的举报方法、终端、电子设备及存储介质
WO2024109582A1 (zh) 多媒体处理方法、媒体服务器和存储介质
CN115529375B (zh) 界面显示方法、装置和电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23759336

Country of ref document: EP

Kind code of ref document: A1