Communication method and device between terminal devices

Abstract

The invention discloses a communication method and device between terminal devices. The method comprises the following steps: under the condition that a call request of a calling terminal is received, determining the state of an interface between a CSCF (Call Session Control Function) entity and a PCRF (Policy and Charging Rules Function) entity; under the condition that the state of the interface is unavailable, executing a first communication strategy without adopting the interface to realize communication; and under the condition that the state of the interface is available, executing a second communication strategy adopting the interface to realize communication. According to the method and the device, the technical problem that the terminal equipment cannot communicate with each other due to an interface fault between a proxy call session control function (P-CSCF) entity and a charging rule function (PCRF) entity is solved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a communication method and apparatus between terminal devices. Background Art

[0002] In the Voice over Long-Term Evolution (VoLTE) network, the VoLTE basic voice service and video service technical requirements require that terminals support resource reservation through the precondition mechanism. When the interface between the Proxy Call Session Control Function (P-CSCF) entity and the Policy and Charging Rules Function (PCRF) entity fails, resource reservation cannot be performed through the precondition mechanism, resulting in the inability of terminal devices to communicate.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of the present application provide a method and apparatus for communication between terminal devices, so as to at least solve the technical problem that the terminal devices cannot communicate due to an interface failure between a proxy call session control function P-CSCF entity and a charging rule function PCRF entity.

[0005] According to one aspect of an embodiment of the present application, a communication method between terminal devices is provided, including: when a call request from a calling terminal is received, determining the state of an interface between a call session control function CSCF entity and a policy and charging rules function PCRF entity; when the state of the interface is unavailable, executing a first communication strategy that does not adopt the interface to achieve communication; when the state of the interface is available, executing a second communication strategy that adopts the interface to achieve communication.

[0006] Optionally, the CSCF entity includes: a proxy call session control function P-CSCF entity, a service call session control function S-CSCF entity, and the interfaces include: a first interface for connecting the P-CSCF entity and a PCRF entity, a second interface for connecting the P-CSCF entity and a routing agent DRA entity, and a third interface for connecting the DRA entity and the PCRF entity, wherein the DRA entity is used to forward information sent by the P-CSCF entity to the PCRF entity; determining the state of the interface between the call session control function CSCF entity and the policy and charging rules function PCRF entity includes: determining the state of the interface according to the state of the first interface, and determining the state of the interface according to the state of the second interface and the state of the third interface.

[0007] Optionally, determining the state of the interface according to the state of the first interface includes: detecting the state of the first interface at a preset frequency, and determining the state of the interface as unavailable when the state of the first interface is unavailable; determining the state of the interface as available when the state of the first interface is available; determining the state of the interface according to the state of the second interface and the state of the third interface includes: detecting the state of the second interface and the state of the third interface at a preset frequency, and determining the state of the interface as unavailable when the state of the second interface or the state of the third interface is unavailable; determining the state of the interface as available when the state of the second interface is available and the state of the third interface is available.

[0008] Optionally, executing a first communication strategy that does not adopt an interface to achieve communication includes: executing a deletion policy through a P-CSCF entity in a CSCF entity, wherein the deletion policy is used to indicate deletion of parameters related to a reserved resource mechanism in a session establishment request message, wherein the reserved resource mechanism is used to implement a function of reserving resources before a calling terminal and a called terminal start a session; sending a session establishment request message after deleting the parameters related to the reserved resource mechanism to an S-CSCF entity in the CSCF entity; and achieving communication through the S-CSCF entity based on current common network resources.

[0009] Optionally, the deletion policy is executed through the P-CSCF entity, including: determining parameters related to the reserved resource mechanism in the session initiation protocol, wherein the parameters include at least: a precondition identifier in the session establishment request message, and a service quality parameter used to describe the service quality; deleting the precondition identifier and the service quality parameter.

[0010] Optionally, executing the deletion policy through the P-CSCF entity also includes: determining a session header of a session initiation protocol, wherein the session header includes parameters related to a reserved resource mechanism; deleting the session header, a precondition identifier, and a quality of service parameter, and adding a new session header for the session initiation protocol, wherein the new session header includes: basic parameters for supporting the session.

[0011] Optionally, communication is achieved through the S-CSCF entity based on the current common network resources, including: determining the number carried by the session establishment request message after deleting the parameters related to the reserved resource mechanism; obtaining the contract information of each number, wherein the contract information at least records the trigger priority of each number; and establishing sessions related to the numbers in sequence according to the trigger priorities of the numbers to achieve communication.

[0012] Optionally, a second communication strategy relying on the interface is executed to achieve communication, including: establishing a dedicated bearer through a P-CSCF entity in the CSCF entity, wherein the dedicated bearer is dedicated to providing network resources for communication between the calling terminal and the called terminal; and communicating between the calling terminal and the called terminal based on the dedicated bearer.

[0013] According to another aspect of an embodiment of the present application, a communication device between terminal devices is also provided, including: a determination module, which is used to determine the state of the interface between the call session control function CSCF entity and the policy and charging rules function PCRF entity when a call request from a calling terminal is received; a first execution module, which, when the state of the interface is unavailable, executes a first communication strategy that does not adopt the interface to achieve communication; and a second execution module, which, when the state of the interface is available, executes a second communication strategy that adopts the interface to achieve communication.

[0014] According to another aspect of an embodiment of the present application, a non-volatile storage medium is further provided, in which a computer program is stored, wherein the above-mentioned communication method between terminal devices is executed by running the computer program on the device where the non-volatile storage medium is located.

[0015] According to another aspect of an embodiment of the present application, there is also provided an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to execute the above-mentioned communication method between terminal devices through the computer program.

[0016] According to another aspect of an embodiment of the present application, a computer program product is also provided, including computer instructions, which implement the steps of the above-mentioned communication method between terminal devices when executed by a processor.

[0017] In an embodiment of the present application, when a call request from a calling terminal is received, the state of the interface between a call session control function CSCF entity and a policy and charging rules function PCRF entity is determined; when the state of the interface is unavailable, a first communication strategy that does not use the interface is executed to achieve communication; when the state of the interface is available, a second communication strategy that uses the interface is executed to achieve communication. A method for achieving communication between terminal devices without relying on a reserved resource mechanism is provided. When the state of the interface between a P-CSCF entity and PCRF is unavailable, a communication strategy that does not rely on a reserved resource mechanism is started to achieve communication between terminal devices. When the state of the interface between the P-CSCF entity and PCRF is available, a communication strategy that relies on a reserved resource mechanism is started to achieve communication between terminal devices. The purpose of switching the communication strategy according to the state of the interface between the P-CSCF entity and PCRF is achieved, thereby achieving the technical effect of ensuring that voice services between terminal devices are always available, thereby solving the technical problem of terminal devices being unable to communicate due to an interface failure between a proxy call session control function P-CSCF entity and a charging rules function PCRF entity. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] 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:

[0019] Figure 1 is a schematic diagram of a communication system 100 according to an embodiment of the present application;

[0020] Figure 2 is a flowchart of a method for communication between terminal devices according to an embodiment of the present application;

[0021] Figure 3 is a schematic diagram of implementing communication between terminal devices through a reserved resource mechanism according to an embodiment of the present application;

[0022] Figure 4 is a structural diagram of a communication device between terminal devices according to an embodiment of the present application;

[0023] Figure 5 This is a flowchart of a calling terminal executing a first communication strategy according to an embodiment of the present application. DETAILED DESCRIPTION

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

[0025] 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 sequence. 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 an order 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.

[0026] 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:

[0027] Preconditioning mechanism: Before a media session is established, the Session Initiation Protocol (SIP) allows the terminal to include a precondition in the session request message (INVITE) to indicate its desired resource status. For example, the user equipment (UE) can use the precondition header field in the INVITE message to request the network to reserve sufficient bandwidth and quality of service (QoS) resources to support high-quality voice or video communications.

[0028] In the related art, the terminal devices rely on the preconditon mechanism to achieve communication. When the interface between the P-CSCF entity and the PCRF is unavailable, the preconditon mechanism cannot be executed, resulting in the inability to communicate between the terminal devices. Therefore, there are problems such as communication interruption, affecting the user experience, etc. In order to solve this problem, the embodiments of the present application provide a related solution, which is described in detail below.

[0029] According to an embodiment of the present application, a method embodiment of a communication method between terminal devices is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a 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.

[0030] The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: voice communication based on long term evolution (VoLTE) system, voice communication based on new wireless technology (Voice over New Radio, VoNR), voice communication based on wireless fidelity network (Voice over WiFi, Vowifi), global system of mobile communication (Global System of Mobile communication, GSM) system, code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general packet radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, LTE frequency division duplex (Frequency Division Duplex, FDD) system, LTE time division duplex (Time Division Duplex, TDD), universal mobile telecommunication system (Universal Mobile Telecommunication System, UMTS), world-wide interoperability for microwave access (Worldwide Interoperability for Microwave Access, WiMAX) communication system or 5G system, etc.

[0031] For example, a schematic diagram of a communication system 100 used in an embodiment of the present application is as follows: Figure 1As shown. The communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or referred to as a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographical area, and may communicate with terminal devices located in the coverage area. Optionally, the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or a base station (NodeB, NB) in a WCDMA system, or an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

[0032] The communication system 100 also includes at least one terminal device 120 located within the coverage of the network device 110. As used herein, "terminal device" includes but is not limited to connection via a wired line, such as via a Public Switched Telephone Networks (PSTN), a Digital Subscriber Line (DSL), a digital cable, a direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as, for a cellular network, a Wireless Local Area Network (WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and / or a device of another terminal device configured to receive / send communication signals; and / or an Internet of Things (IoT) device. A terminal device configured to communicate via a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal" or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that may combine cellular radiotelephones with data processing, fax, and data communications capabilities; PDAs that may include radiotelephones, pagers, Internet / Intranet access, Web browsers, notepads, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or palmtop receivers or other electronic devices that include radiotelephone transceivers. A terminal device may refer to an access terminal, user equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved PLMN, etc.

[0033] Optionally, device to device (D2D) communication may be performed between the terminal devices 120 .

[0034] Optionally, the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.

[0035] The embodiment of the present application provides a communication method between terminal devices that can be operated in the above operating environment. Figure 2 is a flowchart of the steps of the communication method between terminal devices provided in an embodiment of the present application, such as Figure 2 As shown, the method comprises the following steps:

[0036] Step S202: upon receiving a call request from a calling terminal, determining the state of the interface between a call session control function CSCF entity and a policy and charging rules function PCRF entity.

[0037] The method provided in the embodiment of the present application can be applied to any user terminal equipment (User Equipment, UE), and in a communication, can be applied to both the calling terminal and the called terminal. Figure 3 It is a schematic diagram of communication between terminal devices through the reserved resource mechanism, such as Figure 3 As shown, the information sent by the calling terminal is forwarded to the called terminal via the session control function (CSCF) entity. Figure 3 It can be seen that when terminal devices communicate with each other, the session control function (CSCF) entity is responsible for processing and controlling SIP-based multimedia sessions. The reserved resource mechanism needs to be implemented based on the interface between the CSCF entity and the PCRF entity. When the interface between the CSCF entity and the PCRF entity is unavailable, the reserved resource mechanism cannot be implemented. The method provided in the embodiment of the present application determines whether to adopt a communication strategy that relies on the reserved resource mechanism to achieve communication between terminal devices based on the status of the interface. Therefore, in step S202, after receiving a session request sent by the calling terminal, the status of the interface between the CSCF entity and the PCRF entity is first determined to further determine which communication strategy to adopt.

[0038] According to an optional embodiment of the present application, the CSCF entity includes: a proxy call session control function P-CSCF entity, a service call session control function S-CSCF entity, and the interface includes: a first interface for connecting the P-CSCF entity and a PCRF entity, a second interface for connecting the P-CSCF entity and a routing agent DRA entity, and a third interface for connecting the DRA entity and the PCRF entity, wherein the DRA entity is used to forward information sent by the P-CSCF entity to the PCRF entity; determining the state of the interface between the call session control function CSCF entity and the policy and charging rules function PCRF entity includes: determining the state of the interface according to the state of the first interface, and determining the state of the interface according to the state of the second interface and the state of the third interface.

[0039] In an embodiment of the present application, the CSCF entity is a network entity composed of a P-CSCF entity and a Serving Call Session Control Function (S-CSCF) entity, that is, the CSCF entity includes a P-CSCF entity and an S-CSCF entity. In this embodiment, the reserved resource mechanism is executed starting from the P-CSCF entity and the PCRF entity, and the interface that needs to be judged for status is the interface between the P-CSCF entity and the PCRF entity. There are two transmission modes when transmitting messages between the P-CSCF entity and the PCRF entity. One is that the P-CSCF entity and the PCRF entity directly transmit information, and the other is that a routing agent (Diameter Routing Agent, DRA) entity is used to forward messages between the P-CSCF entity and the PCRF entity to achieve information transmission; therefore, the interface between the P-CSCF entity and the PCRF entity (the interface whose status needs to be detected) includes: one end is connected to the P-CSCF entity, and the other end is connected to the interface of the PCRF entity (i.e., the first interface) for transmitting information; one end is connected to the DRA entity, and the other end is connected to the interface of the P-CSCF entity (i.e., the second interface); one end is connected to the DRA entity, and the other end is connected to the interface of the PCRF entity (i.e., the third interface). When detecting whether the status of the interface is available, different detection methods are used according to different networking modes. Specifically, when the DRA entity is not included in the networking, the P-CSCF entity and the PCRF entity transmit information through the directly connected interface (i.e., the first interface). At this time, the status of the first interface is the status of the interface between the P-CSCF entity and the PCRF entity to be determined. If the network includes a DRA entity, the P-CSCF entity and the PCRF entity forward information through the second interface and the third interface. At this time, the state of the interface between the P-CSCF entity and the PCRF entity is determined according to the state of the second interface and the state of the third interface.

[0040] Optionally, determining the state of the interface according to the state of the first interface includes: detecting the state of the first interface at a preset frequency, and determining the state of the interface as unavailable when the state of the first interface is unavailable; determining the state of the interface as available when the state of the first interface is available; determining the state of the interface according to the state of the second interface and the state of the third interface includes: detecting the state of the second interface and the state of the third interface at a preset frequency, and determining the state of the interface as unavailable when the state of the second interface or the state of the third interface is unavailable; determining the state of the interface as available when the state of the second interface is available and the state of the third interface is available.

[0041] As mentioned in the above embodiment, there are two transmission modes when transmitting messages between the P-CSCF entity and the PCRF entity. Since the reserved resource mechanism needs to rely on the information transmission between the P-CSCF entity and the PCRF entity, there are also two ways to implement the reserved resource mechanism. Among them, when the P-CSCF entity and the PCRF entity transmit information through the first interface, the reserved resource mechanism is implemented based on the first interface; when the P-CSCF entity and the PCRF entity forward the message through the DRA entity, that is, transmit information through the second interface and the third interface, the reserved resource mechanism is implemented based on the second interface and the third interface; when the P-CSCF entity and the PCRF entity transmit information through the first interface, the communication strategy is selected according to the status of the first interface. Specifically, if the status of the first interface is available, the communication strategy based on the reserved resource mechanism (that is, the second communication strategy) is adopted. If If the state of the first interface is unavailable, a communication strategy that does not enable the reserved resource mechanism (i.e., the first communication strategy) is adopted; when the P-CSCF entity and the PCRF entity forward transmission information through the DRA entity, a communication strategy is selected according to the state of the second interface and the state of the third interface. Specifically, if the state of the second interface is available, it means that the DRA entity can receive the message sent by the P-CSCF entity, and if the state of the third interface is available, it means that the PCRF entity can receive the message forwarded by the DRA entity. Therefore, when selecting a communication strategy according to the state of the second interface and the state of the third interface, if the states of the second interface and the third interface are both available, a communication strategy based on the reserved resource mechanism (i.e., the second communication strategy) is adopted; if the state of any one of the second interface and the third interface is unavailable, a communication strategy that does not enable the reserved resource mechanism (i.e., the first communication strategy) is adopted. It should be noted that no matter which method is used to determine the state of the interface between the P-CSCF entity and the PCRF entity, a detection frequency can be preset, and the state of the first interface can be detected according to the preset detection frequency, or the state of the second interface and the state of the third interface can be detected according to the preset detection frequency.

[0042] Step S204: When the state of the interface is unavailable, a first communication strategy that does not use the interface is executed to achieve communication.

[0043] If the status of the interface between the CSCF entity and the PCRF entity is completely blocked (i.e., unavailable), it is determined that the reserved resource mechanism cannot be implemented through the interface. At this time, in step S204, a communication strategy that does not use the reservation mechanism (i.e., the first communication strategy) is adopted to implement communication between the calling terminal and its corresponding called terminal, wherein when the first communication strategy is adopted, the interface between the CSCF entity and the PCRF entity is not used to enable the reserved resource mechanism; the reasons why the status of the interface between the CSCF entity and the PCRF entity is completely blocked include network failure, hardware failure, software error, configuration problem, etc. When the interface is completely blocked, data cannot be exchanged between the CSCF entity and the PCRF entity, and communication between terminal devices cannot be implemented based on the reserved resource mechanism.

[0044] According to an optional embodiment of the present application, a first communication strategy that does not adopt an interface is executed to achieve communication, including: executing a deletion strategy through a P-CSCF entity in a CSCF entity, wherein the deletion strategy is used to indicate deletion of parameters related to a reserved resource mechanism in a session establishment request message, wherein the reserved resource mechanism is used to implement a function of reserving resources before a calling terminal and a called terminal start a session; sending a session establishment request message after deleting the parameters related to the reserved resource mechanism to an S-CSCF entity in the CSCF entity; and achieving communication through the S-CSCF entity based on current common network resources.

[0045] In this embodiment, since the parameters related to the reserved resource mechanism are included in the session request message (INVITE) sent by the terminal device, when the strategy of not enabling the reserved resource mechanism (i.e., the first communication strategy) is adopted to realize the communication between the calling terminal and its corresponding called terminal, the deletion strategy is first executed by the P-CSCF entity, wherein the deletion strategy value is used to indicate the deletion of the parameters related to the reserved resource mechanism in the session request message. The P-CSCF entity sends the request message (INVITE) after deleting the above parameters related to the reserved resource mechanism to the S-CSCF entity; further, the communication between the calling terminal and the called terminal is realized by the S-CSCF entity according to the currently used network resources; wherein, in the embodiment of the present application, if the reserved resource mechanism is enabled, a specific QoS will be set for the communication between the calling terminal and the called terminal; when the reserved resource mechanism is not enabled, the network performs an equal treatment mechanism for all data packets; general network resources refer to network resources that are not dedicated to the communication between the calling terminal and the called terminal.

[0046] Optionally, the deletion policy is executed through the P-CSCF entity, including: determining parameters related to the reserved resource mechanism in the session initiation protocol, wherein the parameters include at least: a precondition identifier in the session establishment request message, and a service quality parameter used to describe the service quality; deleting the precondition identifier and the service quality parameter.

[0047] In this embodiment, the parameters related to the resource reservation mechanism must include the following parameters: a precondition extension identifier (i.e., a precondition identifier) ​​newly added to the SIP signaling to indicate support for the resource reservation function, and the following service quality parameters related to the service quality: a=curr:qos local none (currently (curr:) the local calling party (local) qos resources have not yet been reserved), a=curr:qos remote none (currently (curr:) the remote called party (remote) qos resources have not yet been reserved), a=des:qos mandatory local sendrecv (the local calling party (local) expects (des) that the qos resources are bidirectional (sendrecv) resource reservations, and if the resources cannot be successfully reserved, the session will not be established), a=des:qos optional remote sendrecv (the qos resources expected (des) by the remote called party (remote) are bidirectional resource reservations, but it is not yet certain whether the called user really needs to make a reservation (none)); when the P-CSCF entity executes the deletion policy, it can only delete the precondition extension identifier (i.e., the precondition identifier) ​​and service quality parameters contained in the Session Initiation Protocol (SIP).

[0048] According to another optional embodiment of the present application, executing the deletion policy through the P-CSCF entity also includes: determining a session header of the session initiation protocol, wherein the session header includes parameters related to the reserved resource mechanism; deleting the session header, precondition identifier and service quality parameters, and adding a new session header for the session initiation protocol, wherein the new session header includes: basic parameters for supporting the session.

[0049] In some embodiments, in addition to the above-mentioned quality of service parameters, the parameters related to the reserved resource mechanism may also include relevant parameters recorded in the session header of the Session Initiation Protocol (SIP), for example, 100rel recorded in the supported header field of the session header. The SIP standard document defines a reliable transmission mechanism for temporary responses, introduces a "100rel" negotiation mechanism, and 100rel is extended to provide a corresponding mechanism for the reliable transmission of 100-type response messages. In the case where the parameters related to the reserved resource mechanism include both the precondition identifier and the quality of service parameter in the previous embodiment and the 100rel in the supported header field, when the P-CSCF entity executes the deletion policy, the precondition identifier and the quality of service parameter and the session header are deleted at the same time. However, since the supported header field contains the parameters necessary for basic calls (i.e., the basic parameters used to support sessions), for example, timer, replaces, histinfo, and tdialog, timer is used to indicate whether the session refresh function is supported; the replaces message header is used to indicate that a new SIP session is used to replace the current SIP session. The histinfo message header is used to record the processing history of the redirected request message so as to correctly provide services for subsequent sessions. When the request message is redirected, its old routing information may be lost, so that the subsequent session cannot be processed in the originally defined way; the History-Info message header can be used to collect the processing history of the request message and provide services for subsequent sessions; tdialog is the target dialog. The Require header field of SIP carries the tdialog identifier, indicating that the SCC AS (session continuity controller application server) supports the Target-Dialog header field. Target-Dialog represents the original Dialog ID of the session to be switched, including: the identifier of the original session (Call-ID), the remote device user instance (remote-tag), and the local device user instance (local-tag); therefore, if the P-CSCF entity deletes the precondition identifier, service quality parameters and session header when executing the deletion policy, it is also necessary to generate a new session header containing the above timer, replaces, histinfo and tdialog to realize the communication between the calling terminal and the called terminal.

[0050] Based on the above embodiments, it can be known that in the embodiments of the present application, when deleting parameters related to the reservation mechanism, there are the following two situations: one is to delete the above-mentioned a=curr:qos local none, a=curr:qos remote none, a=curr:qos remote none, a=des:qos mandatory local sendrecv and 100rel; the other is to only delete a=curr:qos local none, a=curr:qos remote none, a=curr:qos remote none and a=des:qos mandatory local sendrecv. Whether to delete 100rel is determined according to a preset network management policy. If the preset network policy indicates to delete 100rel when the state of the interface between the P-CSCF entity and the PCRF entity is unavailable, 100rel is deleted.

[0051] In addition, the SIP session header may include a Require header field in addition to the Supported header field. The Require header field is used to specify the features that the recipient must use or support in the SIP request. The Require header field contains a precondition identifier (precondition). When deleting parameters related to the reservation mechanism, the following situations may also exist: 1) Deleting the precondition identifier (precondition extension identifier) ​​of the Supported header field, 100rel, and the service quality parameters in the SDP, and deleting the Require header field and the precondition identifier (precondition extension identifier) ​​of the Require header field at the same time. 2) Deleting the precondition identifier (precondition extension identifier) ​​of the Supported header field, the service quality parameters in the SDP, the Require header field, and the precondition identifier (precondition extension identifier) ​​of the Require header field.

[0052] According to some optional embodiments of the present application, communication is achieved through the S-CSCF entity based on the current common network resources, including: determining the number carried by the session establishment request message after deleting the parameters related to the reserved resource mechanism; obtaining the contract information of each number, wherein the contract information records at least the trigger priority of each number; and establishing sessions related to the numbers in sequence according to the trigger priorities of the numbers to achieve communication.

[0053] As mentioned in the above embodiment, the communication strategy (i.e., the first communication strategy) that does not enable the reserved resource mechanism ultimately implements the communication between the calling terminal and the called terminal based on the S-CSCF entity. Specifically, in this embodiment, the S-CSCF entity triggers the service according to the initial filter criteria (IFC) of the number contract; connects the called party; wherein, the contracted IFC of each number, i.e., the contract information of each number, records at least the priority of the service triggering, the conditions for the service triggering, and other information. Therefore, when the S-CSCF entity implements the communication between the calling terminal and the called terminal, it can first obtain the number recorded in the session invitation information (at this time, the parameters related to the reserved resource mechanism in the session invitation information have been deleted), and further, obtain the contract information (including the contracted IFC) of each number, set the triggering order for multiple numbers according to the triggering priority recorded in the contract information of each number, and connect the calling terminal or the called terminal corresponding to the number in turn according to the above triggering order, establish a session between the calling terminal and the called terminal, so as to realize the communication between the calling terminal and the called terminal. In this embodiment, the number can be a calling number or a called number. In the calling process, the S-CSCF entity on the calling side triggers the IFC of the calling number, and in the called process, the S-CSCF entity on the called side triggers the IFC of the called number. Since the number can be a calling number or a called number, the above-mentioned number-related sessions include: 1) a session between the calling terminal and the called terminal when the number is a calling number; 2) a session between the calling terminal and the called terminal when the number is a called number.

[0054] Step S206: When the state of the interface is available, a second communication strategy using the interface is executed to achieve communication.

[0055] On the contrary, if the status of the interface between the CSCF entity and the PCRF entity is available, data can be exchanged between the CSCF entity and the PCRF entity through the interface, and the reserved resource mechanism can be enabled. Therefore, in step S206, if it is determined to use the interface between the CSCF entity and the PCRF entity, a communication strategy based on the reservation mechanism (i.e., the second communication strategy) is adopted to realize the communication between the calling terminal and its corresponding called terminal; wherein, when the second communication strategy is adopted, it is necessary to enable the reserved resource mechanism based on the interface.

[0056] Optionally, a second communication strategy relying on the interface is executed to achieve communication, including: establishing a dedicated bearer through a P-CSCF entity in the CSCF entity, wherein the dedicated bearer is dedicated to providing network resources for communication between the calling terminal and the called terminal; and communicating between the calling terminal and the called terminal based on the dedicated bearer.

[0057] As mentioned in step S206, when the status of the interface between the CSCF entity and the PCRF entity is available, the reserved resource mechanism is enabled, and a communication strategy based on the reserved resource mechanism (i.e., the second communication strategy) is adopted to realize the communication between the calling terminal and the called terminal. In this embodiment, when the second communication strategy is adopted, the reserved resource mechanism is enabled, and a dedicated bearer dedicated to providing network resources for communication between the calling terminal and the called terminal is established through the P-CSCF entity. After the dedicated bearer is established, the calling terminal and the called terminal only transmit information through the dedicated bearer when communicating, and communicate with each other based on the dedicated bearer.

[0058] Through the above steps, a solution for selecting a communication strategy according to the state of the interface between the CSCF entity and the PCRF entity can be implemented. Specifically, when the state of the interface between the CSCF entity and the PCRF entity is available, a communication strategy based on a reserved resource mechanism (i.e., a second communication strategy) is adopted; when the state of the interface between the CSCF entity and the PCRF entity is unavailable, a communication strategy that does not enable a reserved resource mechanism (i.e., a first communication strategy) is adopted, thereby achieving a technical effect that when the interface between the CSCF entity and the PCRF entity is unavailable, terminal devices can still communicate with each other, thereby ensuring the implementation of basic voice services. In addition, during the communication process, the strategy can be switched without the user of the terminal device being aware of it, thereby ensuring that the communication between the terminal devices is not interrupted, thereby achieving a technical effect of improving the user experience.

[0059] Figure 4 is a structural diagram of a communication device between terminal devices provided according to an embodiment of the present application, such as Figure 4 As shown, the communication device between terminal devices includes: a determination module 40, which is used to determine the state of the interface between the call session control function CSCF entity and the policy and charging rules function PCRF entity when a call request from the calling terminal is received; a first execution module 42, which, when the state of the interface is unavailable, executes a first communication strategy that does not adopt the interface to achieve communication; and a second execution module 44, which, when the state of the interface is available, executes a second communication strategy that adopts the interface to achieve communication.

[0060] It should be noted that Figure 4 The preferred implementation of the illustrated embodiment can be found in Figure 2 The relevant description of the illustrated embodiment will not be repeated here.

[0061] Figure 5 is a flow chart of the calling terminal executing the first communication strategy, such as Figure 5As shown in the figure, when the calling terminal establishes communication with the called terminal, the network architecture of the calling terminal side includes the terminal equipment (UE), the base station (eNodeB), the mobility management entity (MME), the serving gateway (S-GW), the packet data network gateway (P-GW), the PCRF and the CSCF including the P-CSCF and the S-CSCF. In the process of the call procedure, after the P-CSCF entity receives the session invitation information (i.e., INVITE (Offer)) containing the parameters related to the reserved resource mechanism sent by the UE as the calling terminal, the P-CSCF entity deletes the parameters related to the reserved resource mechanism (i.e., precondition related parameters) in the session invitation information, and sends the session invitation information (i.e., INVITE) with the precondition related parameters deleted to the S-CSCF entity. The S-CSCF entity returns a temporary response information (100 trying) to the UE to inform the UE that the information it sent has been received. The INVITE will continue to be transmitted to the called terminal. When the INVITE arrives at the called terminal, the called terminal will send a temporary response information (180 ringing) to the S-CSCF entity of the calling terminal to inform the calling terminal that the called terminal has received the INVITE. After a period of time, if the called terminal accepts the request, it will return a final response information (200 OK) to the calling terminal. After receiving the final response information (200 OK), the calling terminal establishes a session with the called terminal and can start communication. When the communication ends, the calling terminal sends a message to stop the session (BYE) to the called terminal. When the session is successfully stopped, the called terminal returns a message to the calling terminal indicating that the session has been successfully stopped (BYE 200).

[0062] An embodiment of the present application further provides a non-volatile storage medium, in which a computer program is stored, wherein the above-mentioned communication method between terminal devices is executed by running the computer program on a device where the non-volatile storage medium is located.

[0063] The above-mentioned non-volatile storage medium is used to store a program that performs the following functions: when a call request from a calling terminal is received, determining the state of the interface between the call session control function CSCF entity and the policy and charging rules function PCRF entity; when the state of the interface is unavailable, executing a first communication strategy that does not use the interface to achieve communication; when the state of the interface is available, executing a second communication strategy that uses the interface to achieve communication.

[0064] An embodiment of the present application also provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to execute the above-mentioned communication method between terminal devices through the computer program.

[0065] The processor in the above-mentioned electronic device is used to run a program that performs the following functions: when a call request from a calling terminal is received, determining the state of the interface between a call session control function CSCF entity and a policy and charging rules function PCRF entity; when the state of the interface is unavailable, executing a first communication strategy that does not use the interface to achieve communication; when the state of the interface is available, executing a second communication strategy that uses the interface to achieve communication.

[0066] The embodiment of the present application also provides a computer program product, including computer instructions, which implement the steps of the above-mentioned communication method between terminal devices when executed by a processor.

[0067] It should be noted that the various modules in the communication device between the above-mentioned terminal devices can be program modules (for example, a set of program instructions that implement a certain specific function) or hardware modules. For the latter, it can be expressed in the following forms, but is not limited to this: the expression form of each of the above-mentioned modules is a processor, or the functions of each of the above-mentioned modules are implemented by a processor.

[0068] 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.

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

[0070] 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 schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or entities 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.

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

[0072] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0073] 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, or the part that contributes to the relevant technology or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc. Various media that can store program codes.

[0074] The above is only a preferred implementation 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 communication method between terminal devices, characterized in that: include: In case of receiving a call request from a calling terminal, determining a state of an interface between a call session control function CSCF entity and a policy and charging rules function PCRF entity; When the state of the interface is unavailable, executing a first communication strategy that does not use the interface to achieve communication; When the state of the interface is available, a second communication strategy using the interface is executed to achieve communication.

2. The method according to claim 1, characterized in that The CSCF entity includes: a proxy call session control function P-CSCF entity and a service call session control function S-CSCF entity, and the interface includes: a first interface for connecting the P-CSCF entity with the PCRF entity, a second interface for connecting the P-CSCF entity with a routing agent DRA entity, and a third interface for connecting the DRA entity with the PCRF entity, wherein the DRA entity is used to forward information sent by the P-CSCF entity to the PCRF entity; Determining the state of the interface between a call session control function CSCF entity and a policy and charging rules function PCRF entity includes: determining the state of the interface according to the state of the first interface, and determining the state of the interface according to the state of the second interface and the state of the third interface.

3. The method according to claim 2, characterized in that Determining the state of the interface according to the state of the first interface includes: detecting the state of the first interface at a preset frequency, and determining that the state of the interface is unavailable when the state of the first interface is unavailable; and determining that the state of the interface is available when the state of the first interface is available; Determining the state of the interface according to the state of the second interface and the state of the third interface includes: The status of the second interface and the status of the third interface are detected according to the preset frequency. When the status of the second interface or the status of the third interface is unavailable, the status of the interface is determined to be unavailable; when the status of the second interface is available and the status of the third interface is available, the status of the interface is determined to be available.

4. The method according to claim 1, characterized in that Executing a first communication strategy that does not use the interface to achieve communication includes: Executing a deletion policy through a P-CSCF entity in the CSCF entity, wherein the deletion policy is used to indicate deleting parameters related to a reserved resource mechanism in a session establishment request message, wherein the reserved resource mechanism is used to implement a function of reserving resources before the calling terminal and the called terminal start a session; Sending a session establishment request message with parameters related to the reserved resource mechanism deleted to an S-CSCF entity in the CSCF entity; The communication is realized through the S-CSCF entity based on the current common network resources.

5. The method according to claim 4, characterized in that Executing the deletion policy through the P-CSCF entity includes: Determine the parameters related to the reserved resource mechanism in the session initiation protocol, wherein the parameters at least include: a precondition identifier in the session establishment request message and a service quality parameter for describing the service quality; delete the precondition identifier and the service quality parameter.

6. The method according to claim 5, characterized in that Executing the deletion policy by the P-CSCF entity also includes: Determine a session header of the session initiation protocol, wherein the session header includes the parameters related to the reserved resource mechanism; The session header, the precondition identifier and the service quality parameter are deleted, and a new session header is added to the session initiation protocol, wherein the new session header includes: basic parameters for supporting the session.

7. The method according to claim 4, characterized in that Implementing communication through the S-CSCF entity based on current common network resources includes: Determining the number carried by the session establishment request message after deleting the parameters related to the reserved resource mechanism; Acquire the contract information of each of the numbers, wherein the contract information records at least the trigger priority of each of the numbers; Sessions related to the numbers are established in sequence according to the triggering priorities of the numbers to achieve communication.

8. The method according to claim 1, characterized in that Executing a second communication strategy that relies on the interface to achieve communication includes: Establishing a dedicated bearer through a P-CSCF entity in the CSCF entity, wherein the dedicated bearer is dedicated to providing network resources for communication between the calling terminal and the called terminal; The calling terminal and the called terminal communicate with each other based on the dedicated bearer.

9. A communication device between terminal devices, characterized in that: include: A determination module, configured to determine the state of an interface between a call session control function CSCF entity and a policy and charging rules function PCRF entity when a call request from a calling terminal is received; A first execution module, when the state of the interface is unavailable, executes a first communication strategy that does not use the interface to achieve communication; The second execution module executes the second communication strategy of the interface to realize communication when the state of the interface is available.

10. A non-volatile storage medium, characterized in that: The non-volatile storage medium stores a computer program, wherein the device where the non-volatile storage medium is located executes the communication method between terminal devices described in any one of claims 1 to 8 by running the computer program.

11. An electronic device comprising a memory and a processor, characterized in that: The memory stores a computer program, and the processor is configured to execute the communication method between terminal devices according to any one of claims 1 to 8 through the computer program.

12. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed by the processor, the steps of the communication method between terminal devices described in any one of claims 1 to 8 are implemented.

Images