Call control method and device

Abstract

The invention discloses a call control method and device. The method comprises the following steps: receiving a session request message sent by a calling terminal; obtaining a first proxy access network information field from the session request message, and determining whether the calling terminal is in a controlled area according to the first proxy access network information field; and under the condition that the calling terminal is not in the controlled area, establishing a voice bearer between the calling terminal and the called terminal. According to the method and the device, the technical problem that the call control type is relatively single due to the fact that only call control can be carried out on users among different networks in the prior art is solved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a call control method and device. Background Art

[0002] With the increasing complexity and diversification of mobile communication networks, network operators are facing new challenges, and the need for real-time control of operator networks and related business applications has become particularly urgent. Traditional network control technologies are mainly concentrated in circuit-switched networks, while for IP-based IMS (IP Multimedia Subsystem) networks, especially for VoLTE / VoNR (Voice over LTE / Voice over New Radio) services, the control means are relatively insufficient. In related technologies, the switching device to which the called user belongs receives a control message sent by the switching device to which the calling user belongs, which carries the control area identification information of the area to which the calling user currently belongs, and determines whether to restrict the call based on the control area identification information of the area to which the calling user currently belongs and / or the control area identification information of the called user. The control area identification information of the area to which the calling user currently belongs and the control area identification information of the called user are uniformly coded, so that calls between users can be controlled between different networks. However, it is impossible to control calls in specific areas, resulting in a relatively single type of call control. Summary of the Invention

[0003] The embodiments of the present application provide a call control method and apparatus to at least solve the technical problem in the related art that call control is relatively single in type because only call control can be performed on users between different networks.

[0004] According to one aspect of an embodiment of the present application, a call management method is provided, including: receiving a session request message sent by a calling terminal; obtaining a first proxy access network information field from the session request message, and determining whether the calling terminal is in a controlled area based on the first proxy access network information field; and establishing a voice bearer between the calling terminal and the called terminal if the calling terminal is not in the controlled area.

[0005] Optionally, determining whether the calling terminal is in a controlled area according to the first proxy access network information field includes: obtaining the cell identifier accessed by the calling terminal from the first proxy access network information field; and determining that the calling terminal is in the controlled area when the cell identifier accessed by the calling terminal belongs to the controlled area.

[0006] Optionally, the method further includes: when the calling terminal is not within the controlled area, sending a first response message to the calling terminal, wherein the first response message is used to indicate that the calling terminal is allowed to call the called terminal; and when the calling terminal is within the controlled area, sending a second response message to the calling terminal, wherein the second response message is used to indicate that the calling terminal is denied from calling the called terminal.

[0007] Optionally, establishing a voice bearer between the calling terminal and the called terminal includes: after receiving a reply message sent by the called terminal forwarded by the service call session control function network element, sending a first authorization application request message to the policy and charging rules function network element, wherein the first authorization application request message is used to instruct the policy and charging rules function network element to send a first resource allocation request message to the packet data network gateway, and the first resource allocation request message is used to request the packet data network gateway to establish a voice bearer between the calling terminal and the called terminal.

[0008] Optionally, the method also includes: sending a second authorization application request message to the policy and charging rules function network element, the second authorization application request message is used to instruct the policy and charging rules function network element to generate service quality rules, and send the service quality rules to the packet data network gateway through a second resource allocation request message, the second resource allocation request message is used to request the service quality rules to update the voice bearer between the calling terminal and the called terminal.

[0009] Optionally, after the call ends, the method further includes: receiving a farewell message sent by the calling terminal, and sending the farewell message to the policy and charging rules function network element, wherein the farewell message is used to instruct the policy and charging rules function network element to send a third resource allocation request message to the packet data network gateway, and the third resource allocation request message is used to instruct the packet data network gateway to release the voice bearer.

[0010] Optionally, the method further includes: receiving a third response message to the session request message sent by the called terminal; obtaining a second proxy access network information field from the third response message of the session request message, and obtaining an identifier of a cell accessed by the called terminal from the second proxy access network information field; if the identifier of the cell accessed by the called terminal belongs to the controlled area, determining that the called terminal is within the controlled area; and terminating the call when the called terminal is within the controlled area.

[0011] According to another aspect of an embodiment of the present application, another call management method is provided, including: receiving a fourth response message to a session request message sent by a proxy call session control function network element, wherein the fourth response message is used to indicate whether the calling terminal is allowed to call the called terminal, and the fourth response message is determined based on whether the calling terminal is in a controlled area. When the calling terminal is in the controlled area, it is determined that the fourth response message indicates that the calling terminal is denied from calling the called terminal; when the fourth response message indicates that the calling terminal is allowed to call the called terminal, a bearer is established with the called terminal.

[0012] According to another aspect of an embodiment of the present application, a call management device is also provided, including: a receiving module for receiving a session request message sent by a calling terminal; a determining module for obtaining a first proxy access network information field from the session request message, and determining whether the calling terminal is in a controlled area based on the first proxy access network information field; and an establishing module for establishing a voice bearer between the calling terminal and the called terminal when the calling terminal is not in the controlled area.

[0013] According to another aspect of an embodiment of the present application, a communication device is also provided, including: a memory and a processor, wherein the memory is used to store program instructions; the processor is connected to the memory and is used to execute the above-mentioned call management method.

[0014] According to another aspect of the embodiments of the present application, a computer program product is provided, including computer instructions, which implement the above-mentioned call management method when executed by a processor.

[0015] In an embodiment of the present application, a session request message sent by a calling terminal is received; a first proxy access network information field is obtained from the session request message, and whether the calling terminal is in a controlled area is determined based on the first proxy access network information field; if the calling terminal is not in the controlled area, a voice bearer is established between the calling terminal and the called terminal. By determining whether the calling terminal is in a controlled area based on the first proxy access network information field in the session request message, the purpose of call control is achieved for user terminals in the controlled area, thereby achieving the technical effect of enriching call control types, and further solving the technical problem in the related art that call control types are relatively single because call control can only be performed on users between different networks. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0017] Figure 1 This is a hardware structure block diagram of a computer terminal for implementing a call control method according to an embodiment of the present application;

[0018] Figure 2 is a flow chart of a call control method according to an embodiment of the present application;

[0019] Figure 3 is a flowchart of another call control method according to an embodiment of the present application;

[0020] Figure 4 is a flowchart of another call control method according to an embodiment of the present application;

[0021] Figure 5 is a flowchart of another call control method according to an embodiment of the present application;

[0022] Figure 6 This is a structural diagram of a call control device according to an embodiment of the present application. DETAILED DESCRIPTION

[0023] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0024] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0025] In order to better understand the embodiments of the present application, the technical terms involved in the embodiments of the present application are explained as follows:

[0026] Application Server (AS): The top-level application layer device in the IMS system, providing basic and supplementary services, multimedia conferencing, converged communications, SMS gateways, and standard attendant consoles. The IMS network is an open system based on IP bearer technology that provides users with various multimedia services. AS network elements interact with CSCFs using the standard SIP protocol to trigger and execute various network services.

[0027] BAC (Border Access Controller): also known as SBC (Session Border Controller), or Session Border Controller SBC, has gradually become a standard configuration product in IMS networks. Positioned as the ABG (access border gateway) of IMS networks, it solves problems such as NAT / FW traversal, security, interoperability, and QoS.

[0028] HSS (Home Subscriber Server): The HSS supports the primary user database for IMS network entities used to handle calls / sessions. It contains user profiles, performs user authentication and authorization, and provides information about the user's physical location. The entities that communicate with the HSS are application servers (ASs), which host and execute services within the IMS environment, and call session control function servers (CSCFs). The user profile contains information about the current user—typically, the S-CSCF (Service-Call Session Control Function) downloads and uses this file when the user registers with the network.

[0029] I-CSCF (Interrogating Call Session Control Function): The first entry point into the user's home network, responsible for assigning S-CSCFs, routing queries, and inter-domain topology hiding.

[0030] IMPU (IMS Public User Identity): The public user identity is used for SIP message routing. An IMS user can be assigned one or more public user identities. The public user identity can be in the format of a SIP URI or Tel URL. Before using an IMPU to initiate a session or terminate a session, the IMPU must first be registered.

[0031] IMS (IP Multimedia Subsystem) is a new multimedia service that meets end-user demands for newer and more diverse multimedia services. Considered a core technology for next-generation networks, IMS is a key solution for the convergence of mobile and fixed networks, introducing differentiated services such as triple-play voice, data, and video.

[0032] iFC (Initial Filter Criteria): Part of the user subscription data stored in the HSS, it is downloaded to the user's assigned S-CSCF during registration. iFC defines the service triggering conditions and target ASs according to different priorities. When processing user service requests, the S-CSCF performs iFC matching detection. If the triggering conditions are met, it triggers the specified AS, allowing the AS to control the service according to the established service logic within the AS.

[0033] The P-CSCF (Proxy Call Session Control Function) is the unified entry point into the IMS visited network. All session messages originating from and terminating within IMS terminals must pass through the P-CSCF. As a SIP proxy, the P-CSCF is responsible for user authentication and IPSec management independent of the access network, network attack prevention and security protection, SIP signaling compression and decompression to conserve wireless network resources, user roaming control, and bearer-plane NAT and QoS (QoS) via the PDF (Policy Decision Function).

[0034] Rx is an interface defined in 3GPP standards, primarily used in IMS networks supporting VoLTE / VoNR. This interface lies between the P-CSCF and the PCRF. Through the Rx interface, the P-CSCF provides session information to the PCRF, which in turn uses this information to notify the P-CSCF of service plane events. Furthermore, the PCRF verifies that the service information provided by the P-CSCF is consistent with operator-defined policy rules. This service information is used to derive the QoS for media services. The Rx interface, defined in 3GPP TS 29.213 and 29.214, supports the transmission of application-level session information from the P-CSCF to the PCRF. This information includes IP information filtering, media / application bandwidth requirements for QoS control, and provider IDs and usage thresholds for connections with service providers. The Rx interface also enables the P-CSCF to subscribe to notifications on the IP-CAN bearer, such as the signaling path status of the P-CSCF session. The PCRF obtains session and media information from the P-CSCF over the Rx reference point for PCC / QoS policy decisions. These rules are then provided to the P / SGW over the Gx / Gxx reference points. In general, the Rx port plays a key role in the IMS network of VoLTE / VoNR, ensuring service quality and effective network management.

[0035] S-CSCF (Serving Call Session Control Function): The core of the serving CSCF multimedia module, responsible for terminal registration and authentication, session control, and service triggering.

[0036] SIP (Session Initiation Protocol): An application-layer control protocol for multimedia communications over IP networks. It is used to create, modify, and terminate sessions involving one or more participants. It works with protocols such as SDP, RTP / RTCP, RTSP, and DNS to complete session establishment and media negotiation in the IMS.

[0037] Precondition: In a mobile communication network, media streams transmitted between UEs are based on PDP contexts. The process of establishing a media PDP context is called resource reservation.

[0038] UE (User Equipment): Various user devices that access the network. The most common is a mobile phone. Others include SIP phones, IP phones, and call centers. It generally refers to user communication devices that can access the IMS network.

[0039] The information collected in the embodiments of the present application is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with the relevant laws, regulations and standards of the relevant regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or reject the automated decision results; if the user chooses to reject, the expert decision-making process will be entered.

[0040] In order to solve the problems existing in the related art, the embodiment of the present application provides a call control method, which can be run on Figure 1 In the computer terminal shown, the computer terminal is explained below.

[0041] The call control method embodiment provided in the embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 FIG1 shows a hardware structure block diagram of a computer terminal for implementing a call control method. Figure 1 As shown, the computer terminal 10 may include one or more (illustrated by 102a, 102b, ..., 102n in the figure) processors (the processor may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission module 106 for communication functions connected via a wired and / or wireless network. In addition, it may also include: a display, a keyboard, a cursor control device, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, and a BUS bus. It will be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components than shown, or with Figure 1 Different configurations shown.

[0042] It should be noted that the one or more processors and / or other data processing circuits described above may generally be referred to herein as "data processing circuitry." The data processing circuitry may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuitry may be a single, independent processing module, or may be incorporated in whole or in part into any of the other components of the computer terminal 10. As described in the embodiments of the present application, the data processing circuitry serves as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0043] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the call control method in the embodiment of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, implementing the above-mentioned call control method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely located relative to the processor, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0044] The transmission module 106 is configured to receive or transmit data via a network. A specific example of the aforementioned network may include a wireless network provided by the communications provider of the computer terminal 10. In one embodiment, the transmission module 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission module 106 may be a radio frequency (RF) module, which is configured to communicate with the Internet wirelessly.

[0045] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 .

[0046] It should be noted that, in some optional embodiments, the above Figure 1 The computer terminal shown may include hardware elements (including circuits), software elements (including computer code stored on a computer-readable medium), or a combination of hardware elements and software elements. Figure 1 This is merely one example of a particular embodiment and is intended to illustrate the types of components that may be present in the computer terminal described above.

[0047] In the above-mentioned operating environment, an embodiment of the present application provides an embodiment of a call management method. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0048] Figure 2 Flowchart of a call control method according to an embodiment of the present application. Figure 2 As shown, the method includes the following steps:

[0049] Step S202: receiving a session request message sent by the calling terminal;

[0050] In step S202, before receiving the session request message sent by the calling terminal, it is necessary to determine whether the calling terminal is in EMM-UNREGISTERED (mobility management unregistered state). If it is in this state, a service request is first initiated to reestablish the air interface.

[0051] Step S204: Acquire a first proxy access network information field from the session request message, and determine whether the calling terminal is in a controlled area based on the first proxy access network information field;

[0052] Step S206: When the calling terminal is not in the controlled area, a voice bearer is established between the calling terminal and the called terminal.

[0053] It should be noted that the execution entity of the above method is the P-CSCF network element.

[0054] Through the above steps S202 to S206, a session request message sent by a calling terminal is received; a first proxy access network information field is obtained from the session request message, and whether the calling terminal is in a controlled area is determined based on the first proxy access network information field; if the calling terminal is not in the controlled area, a voice bearer is established between the calling terminal and the called terminal. By determining whether the calling terminal is in a controlled area based on the first proxy access network information field in the session request message, the purpose of call control for user terminals in the controlled area is achieved, thereby achieving the technical effect of enriching call control types, and further solving the technical problem in the related art of relatively single call control type due to the fact that call control can only be performed on users between different networks. The following is a detailed description.

[0055] In step S204, the specific steps of determining whether the calling terminal is in a controlled area according to the first proxy access network information field are as follows: obtaining the identifier of the cell accessed by the calling terminal from the first proxy access network information field; and determining that the calling terminal is within the controlled area if the identifier of the cell accessed by the calling terminal belongs to the controlled area.

[0056] Wherein, when the calling terminal is not within the controlled area, a first response message is sent to the calling terminal, wherein the first response message is used to indicate that the calling terminal is allowed to call the called terminal; and when the calling terminal is within the controlled area, a second response message is sent to the calling terminal, wherein the second response message is used to indicate that the calling terminal is denied from calling the called terminal.

[0057] Specifically, when the calling terminal is not in the controlled area, the P-CSCF network element sends a first response message to the calling terminal, instructing the calling terminal to continue the call. When the calling terminal is in the controlled area, the P-CSCF network element sends a 503 service unavailable (second response message) to the calling terminal, refusing the calling terminal to call the called terminal.

[0058] In some embodiments of the present application, the specific steps for establishing a voice bearer between the calling terminal and the called terminal are as follows: after receiving a reply message sent by the called terminal forwarded by the service call session control function network element, sending a first authorization application request message to the policy and charging rules function network element, wherein the first authorization application request message is used to instruct the policy and charging rules function network element to send a first resource allocation request message to the packet data network gateway, and the first resource allocation request message is used to request the packet data network gateway to establish a voice bearer between the calling terminal and the called terminal.

[0059] Specifically, the P-CSCF sends the session request message sent by the calling terminal to the S-CSCF, which forwards it to the called terminal. After the S-CSCF receives the 183Answer (reply message) returned by the called terminal, it forwards it to the P-CSCF. After receiving the reply message, the P-CSCF sends the first AAR message (Authorization Application Request) to the PCRF (Policy and Charging Rules Function) network element. After receiving the AAR message, the PCRF generates corresponding QoS (Quality of Service) rules and charging rules based on the subscription information, network policy and business requirements of the calling terminal, and sends these rules to the P-GW (PDN Gateway) through the first RAR (Resource Allocation Request) message.

[0060] It should be noted that the reply message returned by the called terminal contains the SDP (Session Description Protocol) information of the called terminal, and the AAR message sent by the P-CSCF network element to the PCRF contains media description information (including classifier, bandwidth requirements and media type, etc.), user identification, IMS application layer charging identification, etc.

[0061] If it is necessary to change or update the voice bearer between the calling terminal and the called terminal, the voice bearer can be changed in the following manner. The specific steps are as follows: sending a second authorization application request message to the policy and charging rules function network element, the second authorization application request message is used to instruct the policy and charging rules function network element to generate service quality rules, and send the service quality rules to the packet data network gateway through a second resource allocation request message, the second resource allocation request message is used to request the service quality rules to update the voice bearer between the calling terminal and the called terminal.

[0062] Specifically, the P-CSCF sends a second AAR message to the PCRF to modify the dedicated bearer information. The PCRF makes a policy decision based on the information carried in the second AAR message and the locally configured service information, generates QoS rules, and sends them to the P-GW via a second RAR message.

[0063] When the calling terminal ends the call, a farewell message sent by the calling terminal is received, and the farewell message is sent to the policy and charging rules function network element, where the farewell message is used to instruct the policy and charging rules function network element to send a third resource allocation request message to the packet data network gateway, where the third resource allocation request message is used to instruct the packet data network gateway to release the voice bearer.

[0064] Specifically, when the calling terminal ends the call, it initiates the voice bearer release process as follows: The UE sends a farewell message. This description uses the example of the calling terminal proactively releasing the bearer; the process for the called terminal proactively releasing the bearer is the same. The P-CSCF sends the farewell message to the S-CSCF. After receiving the application session termination message from the S-CSCF, the P-CSCF sends a STR (Session Termination Request) message to the PCRF to release the bearer session. After receiving the STR message, the PCRF sends a third RAR message to the P-GW, instructing the P-GW to delete the voice bearer.

[0065] In some embodiments of the present application, after the called terminal receives a session request message sent by the calling terminal, it sends a third response message to the PCRF on the called terminal side, and receives the third response message to the session request message sent by the called terminal; obtains the second proxy access network information field from the third response message of the session request message, and obtains the cell identifier accessed by the called terminal from the second proxy access network information field; when the cell identifier accessed by the called terminal belongs to the controlled area, determines that the called terminal is within the controlled area; and terminates the call when the called terminal is within the controlled area.

[0066] In actual application scenarios, the calling terminal and the called terminal need to be verified in sequence. Only when the calling terminal and the called terminal are not in the controlled area can the voice bearer be established.

[0067] Figure 3 Another call control method is shown. Figure 3 Shown, including:

[0068] Step 1: If the UE is in the EMM-UNREGISTERED state, it is necessary to first initiate a service request to reestablish the air interface. If the air interface has already been established, this step can be skipped.

[0069] Step 2: The UE sends an INVITE (Offer) to the called party through the default bearer.

[0070] Step 2': The P-CSCF determines whether the P-Access-Network-Info (first proxy access network information field) is in a controlled area according to a preset policy: if yes, a 503 service unavailable message response is sent; if no, the call is continued.

[0071] Step 2": Send a 503 service unavailable message response (second response message) to the UE.

[0072] Step 3: The P-CSCF forwards the INVITE (Offer) message (session request message) to the S-CSCF.

[0073] Step 4: After receiving the 183 (Answer) message returned by the called party, the S-CSCF forwards it to the P-CSCF.

[0074] Step 5: After receiving 183 (Answer), the P-CSCF sends an AAR message to the PCRF to start establishing a dedicated bearer. The AAR includes media description information (including classifier, bandwidth requirements, media type, etc.), user identity, and IMS application layer charging identity.

[0075] Step 6: Create a dedicated bearer for voice traffic.

[0076] Step 7: Based on the second RAA message returned by the P-GW, the PCRF responds to the authorization request result message via AAA (Authentication, Authorization and Accounting) to the P-CSCF, and reports eps-charging-info (charging information).

[0077] Step 8: The P-CSCF receives the AAA and saves the eps-charging-info.

[0078] Step 9: The P-GW receives the second RAR message and matches the dedicated bearer according to the QoS rules. If no match is found, a new dedicated bearer needs to be activated. The P-GW allocates the bearer QoS information and sends a CreateDedicated Beared Request to the UE to establish a new dedicated bearer.

[0079] Step 10: The P-GW receives the Create Bearer Response message, confirming that the dedicated bearer has been established.

[0080] Step 11: The P-GW sends a CCR_u message (Create Control Request-update, bearer control update request) to the PCRF to notify that the resource reservation is successful.

[0081] Step 12: The PCRF returns a CCA_u response (Create Control Answer-update, bearer control update confirmation reply) to the P-GW.

[0082] Step 13: When the PCRF receives the resource reservation success event report from the P-GW, it sends a RAR message to the P-CSCF to notify the bearer establishment status.

[0083] Step 14: The P-CSCF returns an RAA message to the PCRF.

[0084] Step 15: The P-CSCF forwards the INVITE 183 (Answer) message to the UE.

[0085] Step 16: The UE receives the INVITE 183 (Answer) and sends an UPDATE (Offer') (update confirmation message) to confirm the media negotiation result.

[0086] The dedicated voice bearer suggestion is complete, and the user can make a voice call.

[0087] Step 17: Dedicated bearer resource modification process.

[0088] During a voice call, each network element will adjust dedicated bearer resources based on session bandwidth and other factors.

[0089] The P-CSCF sends an AAR message to modify the dedicated bearer information.

[0090] Step 18: The PCRF makes a policy decision based on the information carried in the AAR message and the locally configured service information, generates QoS rules, and sends them to the P-GW via an RAR message.

[0091] Step 19: The P-GW returns the RAA to the PCRF.

[0092] Step 20: The PCRF sends an AAA message to the P-CSCF.

[0093] Step 21: The P-GW receives the RAR message and matches the dedicated bearer according to the QoS rules. If the match is successful, an Update Bearer Request is constructed according to the new QoS rules.

[0094] Step 22: After the dedicated bearer resource modification is completed, the P-GW receives the Update Bearer Response message.

[0095] Step 23: The P-GW sends a CCR_u message to the PCRF to notify that the resource update is successful.

[0096] Step 24: PCRF returns a CCA_u response to the P-GW.

[0097] Step 25: When the PCRF receives the resource update success event report from the P-GW, it sends a RAR message to the P-CSCF to notify the bearer update status.

[0098] Step 26: The P-CSCF returns an RAA message to the PCRF.

[0099] Step 27: The voice call ends and the dedicated bearer is released.

[0100] The UE sends a BYE message. Here, the calling user actively releases the bearer as an example. The process of the called user actively releasing the bearer is the same.

[0101] Step 28: The P-CSCF forwards the BYE message to the S-CSCF.

[0102] Step 29: The P-CSCF receives the application session termination message and sends a STR message to the PCRF to release the bearer session.

[0103] Step 30: The PCRF sends a RAR message (carrying a REMOVE QoS Rules indication) to notify the P-GW to delete the dedicated bearer.

[0104] Step 31: The P-GW returns the RAA to the PCRF.

[0105] Step 32: The PCRF returns the STA response to the P-CSCF.

[0106] Step 33: The P-GW deletes the related rules according to the instruction, releases the bearer session, and sends a Delete BearerRequest message to instruct the deletion of the dedicated bearer.

[0107] Step 34: The P-GW receives the Delete Bearer Response message, indicating that the dedicated bearer has been deleted.

[0108] Step 35: The P-GW sends a CCR_t (Create Control Requst-Termination) message to the PCRF, indicating that the dedicated bearer has been successfully deleted.

[0109] Step 36: The PCRF returns a CCA_t (Create Control Answer-Termination) message to the P-GW for confirmation.

[0110] Step 37: The S-CSCF sends a BYE 200OK (farewell message) to the P-CSCF.

[0111] Step 38: P-CSCF forwards BYE 200OK.

[0112] It can be understood that the above method is a method for performing call control on the calling terminal side.

[0113] Figure 4 Another call control method is shown. Figure 4 Shown, including:

[0114] Step 1: The S-CSCF sends an INVITE message to the P-CSCF.

[0115] Step 2: After receiving the INVITE message, the P-CSCF sends an AAR message to the PCRF.

[0116] Step 3: PCRF returns an AAA response message to P-CSCF.

[0117] Step 4: The P-CSCF sends the downlink data packet to the P-GW.

[0118] Step 5: The P-GW receives the downlink data packet (INVITE) from the P-CSCF and forwards it to the S-GW.

[0119] Step 6: The S-GW receives the downlink data packet from the P-GW, but the data plane is not connected, buffers the data packet, and sends a Downlink Data Notification message to the MME.

[0120] Step 7: After receiving the downlink data notification message from the S-GW, the MME returns a DownlinkData Notification Ack (downlink data notification confirmation) message to the S-GW.

[0121] Step 8: If the MME finds that the UE is registered locally but in the Idle state, it sends a paging message to all eNodeBs serving the TAIs (Tracking Area Identity Lists) registered by the UE.

[0122] Step 9: After receiving the paging message sent by the MME, the eNodeB starts paging the UE.

[0123] Step 10: The UE initiates a Service Request Procedure to reestablish air interface resources.

[0124] Step 11: The air interface is successfully established, and the S-GW forwards the buffered downlink data to the UE.

[0125] Step 12: The UE receives the INVITE (Offer) and returns an INVITE 183 to the P-CSCF, while returning its own access information via P-Access-Network-Info.

[0126] Step 12': The P-CSCF determines whether the P-Access-Network-Info in the response message 183 is in the controlled area: if yes, discard the message; if no, continue the call.

[0127] Step 13: The called party completes the dedicated bearer activation process.

[0128] Step 14: The P-CSCF returns 183 (Answer) to the S-CSCF.

[0129] Step 15: The S-CSCF sends an Update message to the P-CSCF.

[0130] Step 16: The P-CSCF sends an AAR message to the PCRF.

[0131] Step 17: The PCRF returns an AAA response message to the P-CSCF.

[0132] Step 18: The P-CSCF returns a P-Charging-Vector (charging vector) in INVITE 183, carrying the eps-charging-info reported by the P-GW.

[0133] Step 19: Upon receiving the UPDATE (Offer'), the UE sends an UPDATE 200 OK (Answer') confirmation if the QoS resources have been successfully reserved.

[0134] Step 20: The PCRF notifies the EPC network of the media information sent by the P-CSCF to update the dedicated bearer.

[0135] Step 21: The P-CSCF returns an Update 200 response message to the S-CSCF.

[0136] Step 22: The P-CSCF receives a subsequent message (such as 180 / PRACK / PRACK200) and directly transmits it if it does not involve bearer processing.

[0137] Step 23: The UE sends an INVITE 200 message to the eNodeB.

[0138] Step 24: The P-CSCF sends an INVITE 200 message to the S-CSCF.

[0139] Step 25: The S-CSCF returns an ACK response message.

[0140] Step 26: The P-CSCF returns an ACK response message to the UE.

[0141] Step 27: The S-CSCF initiates a release and sends a BYE message to the eNodeB.

[0142] Step 28: The eNodeB sends a BYE message to the UE.

[0143] Step 29: The P-CSCF receives the application session termination message and sends a STR message to the PCRF to release the bearer session.

[0144] Step 30: The PCRF instructs the EPC network to delete the dedicated bearer resources.

[0145] Step 31: The bearer session is successfully released, and the PCRF returns a STA response to the P-CSCF.

[0146] Step 32: The UE sends a BYE 200OK message to the P-CSCF.

[0147] Step 33: The P-CSCF sends a BYE 200OK message to the S-CSCF.

[0148] It can be understood that the above method is a call control method performed by the called terminal side.

[0149] Figure 5 Another call control method is shown, including:

[0150] Step S502: Receive a fourth response message to the session request message sent by the proxy call session control function network element, where the fourth response message is used to indicate whether the calling terminal is allowed to call the called terminal. The fourth response message is determined based on whether the calling terminal is in a controlled area. If the calling terminal is in a controlled area, the fourth response message is determined to indicate that the calling terminal is denied from calling the called terminal.

[0151] Step S504: When the fourth response message indicates that the calling terminal is allowed to call the called terminal, a bearer is established with the called terminal.

[0152] The above-mentioned call control method determines whether the calling terminal is in the controlled area based on the fourth response message in the session request message, thereby achieving the purpose of call control on the user terminal in the controlled area, thereby achieving the technical effect of enriching the call control types, and further solving the technical problem in the related technology that the call control type is relatively single because call control can only be performed on users between different networks.

[0153] Figure 6 A call control device is shown, which includes:

[0154] Receiving module 60, used to receive a session request message sent by the calling terminal;

[0155] a determination module 62, configured to obtain a first proxy access network information field from the session request message, and determine whether the calling terminal is in a controlled area according to the first proxy access network information field;

[0156] The establishing module 64 is configured to establish a voice bearer between the calling terminal and the called terminal when the calling terminal is not in the controlled area.

[0157] The above-mentioned call control device receives a session request message sent by a calling terminal; obtains a first proxy access network information field from the session request message, and determines whether the calling terminal is in a controlled area based on the first proxy access network information field; establishes a voice bearer between the calling terminal and the called terminal when the calling terminal is not in the controlled area, and determines whether the calling terminal is in a controlled area based on the first proxy access network information field in the session request message, thereby achieving the purpose of call control for user terminals in the controlled area, thereby achieving the technical effect of enriching call control types, and further solving the technical problem in the related art that the call control types are relatively single because call control can only be performed on users between different networks.

[0158] The determination module 62 includes: a determination submodule, configured to determine whether the calling terminal is in a controlled area based on the first proxy access network information field, including: obtaining an identifier of a cell accessed by the calling terminal from the first proxy access network information field; and determining that the calling terminal is within the controlled area when the identifier of the cell accessed by the calling terminal belongs to the controlled area.

[0159] The determination submodule includes: a response unit, which is used to send a first response message to the calling terminal when the calling terminal is not in the controlled area, wherein the first response message is used to indicate that the calling terminal is allowed to call the called terminal; and when the calling terminal is in the controlled area, send a second response message to the calling terminal, wherein the second response message is used to indicate that the calling terminal is denied to call the called terminal.

[0160] The establishment module 64 includes: an establishment submodule, which is used to establish a voice bearer between the calling terminal and the called terminal, including: after receiving a reply message sent by the called terminal forwarded by the service call session control function network element, sending a first authorization application request message to the policy and charging rules function network element, wherein the first authorization application request message is used to instruct the policy and charging rules function network element to send a first resource allocation request message to the packet data network gateway, and the first resource allocation request message is used to request the packet data network gateway to establish a voice bearer between the calling terminal and the called terminal.

[0161] The establishment submodule includes: an update unit, used to send a second authorization application request message to the policy and charging rules function network element, the second authorization application request message is used to instruct the policy and charging rules function network element to generate service quality rules, and send the service quality rules to the packet data network gateway through a second resource allocation request message, the second resource allocation request message is used to request the service quality rules to update the voice bearer between the calling terminal and the called terminal.

[0162] The above-mentioned call control device also includes: a release submodule, which is used to receive a farewell message sent by the calling terminal and send the farewell message to the policy and charging rules function network element, and the farewell message is used to instruct the policy and charging rules function network element to send a third resource allocation request message to the packet data network gateway, and the third resource allocation request message is used to instruct the packet data network gateway to release the voice bearer.

[0163] The above-mentioned call control device also includes: a called sub-module, which is used to receive a third response message to the session request message sent by the called terminal; obtain a second proxy access network information field from the third response message of the session request message, and obtain the cell identifier accessed by the called terminal from the second proxy access network information field; when the cell identifier accessed by the called terminal belongs to the controlled area, determine that the called terminal is within the controlled area; and terminate the call when the called terminal is within the controlled area.

[0164] It should be noted that Figure 6 The call control device shown is used to perform Figure 2 The call control method shown, therefore the above-mentioned relevant explanations except for the call control method also apply to the call control device, and will not be repeated here.

[0165] An embodiment of the present application also provides a communication device, including: a memory and a processor, wherein the memory is used to store program instructions; the processor is connected to the memory and is used to execute the above-mentioned call management method.

[0166] An embodiment of the present application also provides a computer program product, including computer instructions, which, when executed by a processor, implement the steps of the call control method in the present application.

[0167] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0168] In the above embodiments of the present application, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0169] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0170] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0171] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0172] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a communication device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0173] The above is only a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A call control method, characterized in that: include: Receiving a session request message sent by a calling terminal; Acquire a first proxy access network information field from the session request message, and determine whether the calling terminal is in a controlled area according to the first proxy access network information field; In a case where the calling terminal is not in the controlled area, a voice bearer is established between the calling terminal and the called terminal.

2. The method according to claim 1, characterized in that Determining whether the calling terminal is in a controlled area according to the first proxy access network information field includes: Acquire an identifier of a cell accessed by the calling terminal from the first proxy access network information field; In a case where the cell identifier accessed by the calling terminal belongs to the controlled area, it is determined that the calling terminal is within the controlled area.

3. The method according to claim 2, characterized in that The method further comprises: When the calling terminal is not in the controlled area, sending a first response message to the calling terminal, wherein the first response message is used to indicate that the calling terminal is allowed to call the called terminal; In a case where the calling terminal is within the controlled area, a second response message is sent to the calling terminal, wherein the second response message is used to indicate that the calling terminal is rejected from calling the called terminal.

4. The method according to claim 1, wherein Establishing a voice bearer between the calling terminal and the called terminal includes: After receiving the reply message sent by the called terminal forwarded by the service call session control function network element, a first authorization application request message is sent to the policy and charging rules function network element, wherein the first authorization application request message is used to instruct the policy and charging rules function network element to send a first resource allocation request message to the packet data network gateway, and the first resource allocation request message is used to request the packet data network gateway to establish a voice bearer between the calling terminal and the called terminal.

5. The method according to claim 4, characterized in that The method further comprises: A second authorization application request message is sent to the policy and charging rules function network element, where the second authorization application request message is used to instruct the policy and charging rules function network element to generate quality of service rules, and send the quality of service rules to the packet data network gateway through a second resource allocation request message, where the second resource allocation request message is used to request that the quality of service rules update the voice bearer between the calling terminal and the called terminal.

6. The method according to claim 1, characterized in that After the call ends, the method further includes: Receive a farewell message sent by the calling terminal, and send the farewell message to the policy and charging rules function network element, where the farewell message is used to instruct the policy and charging rules function network element to send a third resource allocation request message to the packet data network gateway, where the third resource allocation request message is used to instruct the packet data network gateway to release the voice bearer.

7. The method according to claim 1, characterized in that The method further comprises: receiving a third response message to the session request message sent by the called terminal; Acquire a second proxy access network information field from a third response message of the session request message, and acquire an identifier of a cell accessed by the called terminal from the second proxy access network information field; In a case where the cell identifier accessed by the called terminal belongs to the controlled area, determining that the called terminal is within the controlled area; The call is terminated when the called terminal is within the controlled area.

8. A call control method, characterized in that: include: receiving a fourth response message to the session request message sent by the proxy call session control function network element, wherein the fourth response message is used to indicate whether the calling terminal is allowed to call the called terminal, and the fourth response message is determined based on whether the calling terminal is in a controlled area. If the calling terminal is in the controlled area, determining that the fourth response message indicates that the calling terminal is denied from calling the called terminal; In a case where the fourth response message indicates that the calling terminal is allowed to call the called terminal, a bearer is established with the called terminal.

9. A call control device, characterized in that: include: A receiving module, configured to receive a session request message sent by a calling terminal; a determination module, configured to obtain a first proxy access network information field from the session request message, and determine whether the calling terminal is in a controlled area according to the first proxy access network information field; The establishing module is used to establish a voice bearer between the calling terminal and the called terminal when the calling terminal is not in the controlled area.

10. A communication device, characterized in that: include: A memory and a processor, wherein the memory is used to store program instructions; The processor is connected to the memory and is used to execute the call management method described in any one of claims 1 to 7.

11. A computer program product comprising computer instructions, characterized in that When the computer instructions are executed by a processor, the call control method according to any one of claims 1 to 7 is implemented.

Images