Communication methods, devices, terminals, chips, and storage media

By identifying and prioritizing the latest call request messages during network congestion, the problem of all calls failing to connect under network congestion is solved, thus improving the call success rate.

CN123124126APending Publication Date: 2026-11-17BEIJING X RING TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611399040.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-09
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In network congestion scenarios, the called terminal processes call request messages according to a first-in-first-out (FIFO) strategy. This results in the early call request messages being released due to network timeouts, while the later call request messages cannot be connected, leading to a situation where all calls cannot be connected.

Method used

By identifying network congestion within a time window, the latest arriving call request message is determined and prioritized to establish an RTP media channel, while earlier arriving call request messages are discarded or released.

Benefits of technology

It increases the probability of a successful call connection, avoids network devices releasing phone instances due to timeouts, and improves the worst-case scenario where all calls cannot be connected in congested situations, ensuring that at least one call can be connected.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123124126A_ABST
    Figure CN123124126A_ABST
Patent Text Reader

Abstract

This application proposes a call method, apparatus, terminal, chip, and storage medium, relating to the field of communications. The method includes: identifying network congestion based on the number of call request messages received within a time window; in response to identifying network congestion, determining the latest arriving call request message from the received call request messages within the time window; and performing call processing on the first call request message to establish an RTP media channel with the calling terminal. Since the last arriving call request message has the shortest transmission time in the network, the corresponding phone instance is most likely not yet available. When the network is congested, discarding earlier arriving call request messages with longer congestion times and only processing the last arriving call request message with the shortest congestion time allows the terminal to prioritize attempting to connect to the most likely surviving phone instance, thereby improving the call connection success rate.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a call method, apparatus, terminal, chip, and storage medium. Background Technology

[0002] When a user terminal receives an incoming call as the called party, the network device forwards the call request message to the called terminal. Upon receiving the message, the called terminal rings or answers the call. However, in real-world network environments, especially during network congestion, signal switching, or high core network load, the called terminal may receive multiple call request messages from different phones within a short period. In related technologies, the called terminal processes call request messages according to a First-In-First-Out (FIFO) principle. However, in congested scenarios, it's easy for all call request messages to fail to connect. Summary of the Invention

[0003] This application proposes a communication method, apparatus, terminal, chip, and storage medium to at least partially solve one of the technical problems in the related art.

[0004] One embodiment of this application proposes a call method, including: The network congestion status is identified based on the number of call request messages received within a time window. In response to the detection that the network is in a congested state, the latest arriving first call request message is determined from the call request messages received within the time window; Call processing is performed on the first call request message to establish a Real-Time Transport Protocol (RTP) media channel with the calling terminal.

[0005] Another embodiment of this application provides a communication device, including: The identification module is configured to identify the network congestion status based on the number of call request messages received within a time window. The determination module is configured to, in response to recognizing that the network is in a congested state, determine the latest arriving first call request message from the call request messages received within the time window; The execution module is configured to perform incoming call processing on the first call request message in order to establish an RTP media channel with the calling terminal.

[0006] Another aspect of this application provides a terminal including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, it implements the call method as described in the foregoing aspect.

[0007] In another aspect of this application, a chip is provided that includes an interface circuit and a processing circuit coupled to each other, the interface circuit being used to input or output signals, and the processing circuit being configured to perform the call method as described in the preceding aspect.

[0008] In another aspect, this application provides a non-transitory computer-readable storage medium storing computer program instructions that, when executed by a processor, implement the call method as described in the foregoing aspect.

[0009] Another aspect of this application provides a computer program product having a computer program stored thereon, which, when executed by a processor, implements the call method as described in the foregoing aspect.

[0010] The calling method, apparatus, terminal, chip, and storage medium proposed in this application identify network congestion by measuring the number of call request messages received within a time window. When network congestion is detected, the latest arriving call request message is determined from the received call request messages within the time window, and call processing is performed on the first call request message to establish a Real-time Transport Protocol (RTP) media channel with the calling terminal. Compared to related technologies that process call request messages according to FIFO in congestion scenarios, the network device may release the corresponding phone instance due to timeout because the first processed call request message has the longest congestion time, often resulting in all called calls being unable to be connected. Since the last call request message arrives in the network with the shortest transmission time, the network device is most likely not yet releasing the corresponding phone instance. In the event of network congestion, this application discards the earlier arriving call request messages, i.e., those with longer congestion times, and only processes the last arriving call request message, i.e., those with the shortest congestion time. This allows the terminal to prioritize trying to connect to the phone instance that is most likely still alive, thereby increasing the probability of a successful call connection. In turn, the worst-case scenario where all calls cannot be connected in a congested situation is improved to the point where at least one call may be connected.

[0011] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0012] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein: Figure 1 A flowchart illustrating a call method provided for an exemplary embodiment of this application; Figure 2A flowchart illustrating another call method provided for an exemplary embodiment of this application; Figure 3 A flowchart illustrating yet another call method provided for an exemplary embodiment of this application; Figure 4 A flowchart illustrating another call method provided for an exemplary embodiment of this application; Figure 5 A schematic diagram of a network architecture for a call method provided for an exemplary embodiment of this application; Figure 6 A schematic diagram of the structure of a communication device provided for an exemplary embodiment of this application; Figure 7 A schematic diagram of the structure of an electronic device provided for an exemplary embodiment of this application; Figure 8 This is a schematic diagram of the structure of a chip proposed as an exemplary embodiment of this application. Detailed Implementation

[0013] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0014] It should be noted that the acquisition, storage, use, and processing of data in this application comply with relevant laws and regulations and do not violate public order and good morals.

[0015] It should also be noted that all data processed in this application is data that has been explicitly authorized by the user or relevant parties, and has been de-identified or anonymized before collection and use, and does not contain any personally identifiable information or user privacy content; all data is used only for energy-saving purposes, ensuring that data security and user privacy rights are fully protected while achieving technical effects.

[0016] Voice over Long Term Evolution (VoLTE) and Voice over New Radio (VoNR) are the main technologies for voice calls in current 4G / 5G networks. In the IP Multimedia Subsystem (IMS) architecture, the Session Initiation Protocol (SIP) serves as the core signaling protocol, used to establish, manage, and terminate multimedia sessions.

[0017] When a user receives an incoming call as the called party, the network device forwards the call request message to the called terminal. Upon receiving the call request message, the terminal performs operations such as ringing and answering. However, in real-world network environments, especially in scenarios involving network congestion, signal switching, or high core network load, the called terminal may receive multiple call request messages from different telephone numbers within a short period of time.

[0018] In existing technologies, the called terminal processes call request messages according to a FIFO (First-In, First-Out) strategy. This means the called terminal prioritizes the first arriving call request message and rejects subsequent messages. However, in congested scenarios, the first arriving call request message may have been transmitted over the network for a considerable time. The network device may have already released the corresponding phone instance due to timeout. Even if the terminal processes the message to attempt to establish a call, the network device cannot cooperate to complete the connection. Simultaneously, the terminal, busy processing the first message, rejects all subsequent calls, potentially causing the network device to discard still-active phone instances corresponding to later messages. This results in a situation where all calls fail to connect in a congested environment.

[0019] Therefore, in view of at least one of the problems existing in the above-mentioned related technologies, this application proposes a calling method, device, terminal, chip and storage medium.

[0020] The following description, with reference to the accompanying drawings, describes a call method, apparatus, terminal, chip, and storage medium according to embodiments of this application.

[0021] Figure 1 This is a flowchart illustrating a call method provided for an exemplary embodiment of this application.

[0022] It should be noted that the call method of this application embodiment can be applied to a call device. In some possible embodiments, the call device can be configured in a terminal or chip so that the terminal or chip can perform call functions. In addition, in some possible embodiments, the call device can also be software in the terminal, etc.

[0023] In any embodiment of this application, the chip can be integrated into a terminal. The chip includes a Central Processing Unit (CPU), an Image Signal Processing (ISP), an Application-Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Field-Programmable Gate Array (FPGA), a System-on-Chip (SOC), a Reduced Instruction Set Computer (RISC), etc., which will not be listed here.

[0024] In this context, a terminal is a user-side entity used to receive or transmit signals, such as a mobile phone. A terminal can also be called a terminal device (terminal), user equipment (UE), mobile station (MS), mobile terminal device (MT), etc. Terminals can be communication-enabled vehicles, smart cars, mobile phones, wearable devices, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in assisted driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, and so on. The embodiments in this application do not limit the specific technology or device form used in the terminal.

[0025] Among them, assisted driving refers to the technology that uses sensors, algorithms and artificial intelligence to perceive the environment, make decisions, plan and execute control commands of the vehicle in order to assist the driver to drive more safely and efficiently.

[0026] For ease of explanation, the following description will use the terminal as the entity executing this call method. It is understood that the terminal is the one being called.

[0027] like Figure 1 As shown, the call method may include, but is not limited to, the following steps: Step S101: Identify the network congestion status based on the number of call request messages received within the time window.

[0028] Different call request messages are initiated by different calling terminals. Under normal network conditions, network devices will not send multiple call request messages from different terminals to the same called terminal simultaneously. Instead, network devices will send or submit these call request messages from different calling terminals to the same called terminal at time intervals. However, in network congestion scenarios, the called terminal may receive two or more call request messages from different calling terminals within a very short period (e.g., within 1 second). This phenomenon often occurs because these call request messages are delayed during network transmission due to congestion. Once the congestion eases, these delayed call request messages and newly arrived call request messages will arrive at the called terminal in a short period.

[0029] For the reasons mentioned above, as a possible implementation, the network congestion status can be identified based on the number of call request messages received within a time window.

[0030] As one possible implementation, the time window can be a pre-configured window used to detect whether different phone call request messages have arrived.

[0031] As one possible implementation, the time window can be configured to a set duration, such as 1000 millimeters (which is 1 second).

[0032] As one possible implementation, the time window can be periodically timed using a timer to identify the state of the periodic network.

[0033] As one possible implementation, the call request message may include, but is not limited to, SIP invitation (INVITE) messages, call transfer messages, etc.

[0034] As one possible implementation, the terminal can receive call request messages sent by network devices within a time window, count the number of call request messages received within the time window, and further identify whether the network is in a congested state based on the number of call request messages received within the time window.

[0035] As one possible implementation, in response to the number of call request messages received within a time window being greater than a set number, such as 1, that is, when the number of call request messages received within a time window is two or more, the network can be identified as being in a congested state.

[0036] Understandably, if the number of call request messages received within a time window is less than or equal to a set number, for example, if the number of call request messages received within a time window is one or zero, it can be identified that the network is not in a congested state, that is, the network is in a normal state.

[0037] Step S102: In response to the detection that the network is in a congested state, the latest arriving first call request message is determined from the call request messages received within the time window.

[0038] As one possible implementation, the latest arriving first call request message is the last call request message to arrive among all call request messages received within the time window.

[0039] As one possible implementation, the last arriving first call request message is the one with the shortest network congestion among all call request messages received within the time window.

[0040] Step S103: Perform incoming call processing on the first call request message to establish an RTP media channel with the calling terminal.

[0041] As one possible implementation, after the called terminal determines the first call request message, it can interact with the network equipment and the calling terminal to process the incoming call, and then establish an RTP media channel with the calling terminal, so that the called terminal and the calling terminal can have a real-time call on the RTP media channel.

[0042] In this context, network equipment refers to an entity on the network side used for transmitting or receiving signals. Network equipment includes access network equipment and core network equipment. Access network equipment can be an evolved NodeB (eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G new radio (NR) system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiments of this application do not limit the specific technology or equipment form used in the access network equipment. The access network equipment provided in the embodiments of this application can be composed of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure allows the protocol layer of a network device, such as a base station, to be separated. Some protocol layer functions are centrally controlled by the CU, while the remaining part or all protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0043] As an example, imagine three calling terminals simultaneously in a network: terminal A, terminal B, and terminal C. Terminals A, B, and C each send a call to terminal D. Under normal network conditions, the network equipment will send the call request messages (INVITE messages) from these three calling terminals to terminal D sequentially at reasonable time intervals. However, when the network is congested, the following phenomenon may occur: The INVITE message (INVITE_A) from the calling terminal A is sent by the network device first, but due to the current network congestion, the INVITE_A message is congested in the network for the longest time. For example, the INVITE_A message may be congested in the network for 15 seconds. The calling terminal B's INVITE message (INVITE_B) is then sent by the network device, but due to the current network congestion, the INVITE_B message is congested in the network for a longer period of time. For example, the INVITE_B message may be congested in the network for 10 seconds. The INVITE message (INVITE_C) from the calling terminal C is eventually sent by the network device. However, due to the current network congestion, the INVITE_C message may be congested in the network for a very short time. For example, the INVITE_C message may be congested in the network for 5 seconds.

[0044] Once network congestion eases, INVITE_A, INVITE_B, and INVITE_C messages will arrive at the called terminal D within a very short time (e.g., within 1 second).

[0045] In this application, the called terminal can identify that the network is currently in a congested state based on receiving 3 INVITE messages within 1 second. In a congested scenario, since the INVITE_A and INVITE_B messages are congested on the network for a long time, the network device may release the phone instance corresponding to the INVITE_A and INVITE_B messages due to timeout. However, the INVITE_C message is congested on the network for a short time, and the phone instance corresponding to the INVITE_C message is still alive. That is, the network device does not release the phone instance corresponding to the INVITE_C message.

[0046] To improve the success rate of call connection, the called terminal D can determine from the INVITE_A, INVITE_B and INVITE_C messages that the INVITE_C message is the latest INVITE message. Since the telephone instance corresponding to the INVITE_C message is still alive, the incoming call processing can be performed on the INVITE_C message, thereby establishing an RTP media channel between the called terminal D and the calling terminal C.

[0047] The call method in this embodiment identifies network congestion by counting the number of call request messages received within a time window. When network congestion is detected, the latest arriving call request message is determined from the received call request messages within the time window. Call processing is then performed on this first call request message to establish a Real-time Transport Protocol (RTP) media channel with the calling terminal. Compared to related technologies that process call request messages in a FIFO manner during congestion, the network device often releases the corresponding phone instance due to timeout because the first processed call request message has the longest congestion time, resulting in all called calls failing to connect. Since the last call request message arrives in the network with the shortest transmission time, the network device is most likely not yet releasing the corresponding phone instance. In the event of network congestion, this application discards the earlier arriving call request messages, i.e., those with longer congestion times, and only processes the last arriving call request message, i.e., those with the shortest congestion time. This allows the terminal to prioritize trying to connect to the phone instance that is most likely still alive, thereby increasing the probability of a successful call connection. In turn, the worst-case scenario where all calls cannot be connected in a congested situation is improved to the point where at least one call may be connected.

[0048] As one possible implementation method, Figure 2 A flowchart illustrating another call method provided for an exemplary embodiment of this application.

[0049] It should be noted that the call method can be executed alone, or it can be executed together with any embodiment of this application or any possible implementation in the embodiment, or it can be executed together with any technical solution in the related technology. The embodiments of this application do not limit this.

[0050] like Figure 2 As shown, the call method may include, but is not limited to, the following steps: Step S201: Identify the network congestion status based on the number of call request messages received within the time window.

[0051] As one possible implementation, from the call request messages received within the time window, it is determined that the call request messages belong to different call identifiers (Call-IDs), and the number of call request messages belonging to different call identifiers is further counted. In response to the number being greater than a set value, it is determined that the network is in a congested state.

[0052] As one possible implementation, Call-ID is a globally unique call identifier. All call request messages (i.e., INVITE messages) for the same phone or call can share the same Call-ID, while different phones have different Call-IDs.

[0053] As one possible implementation, the terminal can parse the received call request message (i.e., the INVITE message) to obtain the Call-ID, and then distinguish the call request messages of different phones.

[0054] It should be noted that the aforementioned description of step S201 also applies to this embodiment, and will not be repeated here.

[0055] In this embodiment, by detecting whether multiple call request messages with different Call-IDs are received within a time window, network congestion can be identified. This enables the terminal to perceive network congestion based on the number of call request messages, facilitating flexible processing of these messages and improving call connection success rates. Furthermore, this network congestion perception mechanism is implemented entirely on the terminal, without relying on explicit congestion notifications from network devices or requiring any modifications to the network equipment. It is characterized by simple deployment and good compatibility.

[0056] Step S202: In response to the detection that the network is in a congested state, obtain the arrival timestamp of the call request message.

[0057] As one possible implementation, upon detecting network congestion, the arrival timestamp of the call request message can be obtained. Optionally, the terminal can also record the system time when the call request message arrives at itself, as the arrival timestamp of the call request message. Optionally, the arrival timestamp of the call request message can be a time with millisecond precision.

[0058] It should be noted that in the event of network congestion, call request messages will be sent to the called terminal in the order in which the calling terminal initiated the call request message. Thus, the arrival timestamp of the call request message can reflect the order in which multiple call request messages were initiated by their respective calling terminals.

[0059] Step S203: Select the call request message with the latest arrival timestamp as the first call request message.

[0060] As one possible implementation, the call request message with the latest arrival timestamp is selected from the call request messages received within the time window as the first call request message. In other words, the call request message with the largest timestamp is selected from the call request messages received within the time window as the first call request message to be processed.

[0061] As one possible implementation, the order in which call request messages arrive at the terminal can be recorded, and the call request messages can be numbered based on the recorded order, with the numbers arranged from earliest to latest in ascending order. These numbers can reflect the order in which multiple call request messages were initiated by their respective calling terminals. Furthermore, by comparing the numbers, the call request message with the latest arrival timestamp is selected from the call request messages received within the time window and designated as the first call request message.

[0062] Understandably, the latest arriving call request message, also known as the first call request message, is the most recent. Since network devices have a timeout release mechanism for each phone instance, the shorter the congestion time of the first call request message, the higher the probability that its corresponding phone instance has not yet been released by the network device. Therefore, prioritizing the processing of the latest first call request message ensures that the terminal is most likely to attempt to connect to a live phone instance, thereby improving the connection success rate.

[0063] In this embodiment of the application, by introducing an arrival timestamp mechanism, the called terminal can accurately identify the arrival order of multiple call request messages when they receive them simultaneously or nearly simultaneously, based on the order of their arrival timestamps. This allows the terminal to determine the latest arriving call request message, which is the most likely valid call request message. The terminal then processes the latest likely valid call request message, thereby prioritizing the connection of the most likely still active phone instance. This increases the probability of a successful call connection and improves the worst-case scenario where all calls fail to connect in a congested environment to one where at least one call may be connected.

[0064] Step S204: Perform incoming call processing on the first call request message to establish an RTP media channel with the calling terminal.

[0065] As one possible implementation, the called terminal can send a response message to the network device for the first call request message; for example, the response message could be a 100 Trying provisional response. Further, the called terminal can negotiate a Session Description Protocol (SDP) with the network device. Upon completion of the SDP negotiation, the called terminal is triggered to ring to notify the user of an incoming call. Further, upon the call being answered, the called terminal can send a success response message to the network device to establish an RTP media channel with the calling terminal.

[0066] As one possible implementation, after the user answers the call, the called terminal can send a 200 OK response (i.e., a success response message) to the network device, and then establish an RTP media channel with the calling terminal through the network device to complete the call setup.

[0067] As one possible approach, users can answer calls manually or through a voice assistant.

[0068] The call method in this embodiment identifies network congestion by counting the number of call request messages received within a time window. When network congestion is detected, the latest arriving call request message is determined from the received call request messages within the time window. Call processing is then performed on this first call request message to establish a Real-time Transport Protocol (RTP) media channel with the calling terminal. Compared to related technologies that process call request messages in a FIFO manner during congestion, the network device often releases the corresponding phone instance due to timeout because the first processed call request message has the longest congestion time, resulting in all called calls failing to connect. Since the last call request message arrives in the network with the shortest transmission time, the network device is most likely not yet releasing the corresponding phone instance. In the event of network congestion, this application discards the earlier arriving call request messages, i.e., those with longer congestion times, and only processes the last arriving call request message, i.e., those with the shortest congestion time. This allows the terminal to prioritize trying to connect to the phone instance that is most likely still alive, thereby increasing the probability of a successful call connection. In turn, the worst-case scenario where all calls cannot be connected in a congested situation is improved to the point where at least one call may be connected.

[0069] As one possible implementation method, Figure 3 A flowchart illustrating yet another call method provided for an exemplary embodiment of this application.

[0070] It should be noted that the call method can be executed alone, or it can be executed together with any embodiment of this application or any possible implementation in the embodiment, or it can be executed together with any technical solution in the related technology. The embodiments of this application do not limit this.

[0071] like Figure 3 As shown, the call method may include, but is not limited to, the following steps: Step S301: Identify the network congestion status based on the number of call request messages received within the time window.

[0072] Step S302: In response to the identification that the network is in a congested state, the latest arriving first call request message is determined from the call request messages received within the time window.

[0073] As one possible implementation, in response to the identification that the network is in a congested state, the network congestion flag is configured as the first indication.

[0074] As one possible implementation, in response to the completion of the first call request message processing, the network congestion flag is reset to a second indication to enter a waiting state.

[0075] In this embodiment, when the network congestion flag is set to the first indication, the called terminal can be triggered to adopt a strategy of discarding the second call request message and processing only the first call request message to connect the call. When the network congestion flag is set to the second indication, the called terminal can be triggered to adopt a FIFO strategy to connect the call. In other words, the processing strategy for call request messages can be dynamically switched based on the identification result of the network congestion status, giving the terminal an adaptive capability.

[0076] It should be noted that the foregoing description of steps S301 to S302 also applies to this embodiment, and will not be repeated here.

[0077] Step S303: Mark the second call request message (other than the first call request message) among the call request messages received within the time window as discardable, and release the relevant transaction resources of the second call request message.

[0078] After the first call request message is identified, other call request messages received within the time window, i.e., the second call request message, are considered old call request messages to the called terminal. The network device will discard the phone instances corresponding to these call request messages due to timeouts; in other words, the phone instances corresponding to these call request messages are invalid. Upon receiving the call request message, the called terminal will create a SIP transaction for the call request message and allocate relevant resources. Optionally, when a SIP transaction is created, the SIP protocol stack will allocate a memory resource in the heap, which can be used to store the transaction control block, the INVITE message string, state machine variables, timer handles, etc. Optionally, when a SIP transaction is created, the SIP protocol stack will also allocate network resources for the SIP transaction, such as, but not limited to, ports and data buffers. Optionally, when a SIP transaction is created, the SIP protocol stack will also allocate routing resources for the SIP transaction.

[0079] As one possible implementation, the second call request message can be marked as discarded. When the second call request message is marked as discarded, the called terminal will not process the call. In order to avoid waste and invalid occupation of resources, the relevant transaction resources of the second call request message can be released.

[0080] In this embodiment of the application, by promptly releasing the resources associated with the transaction requested by the second call request message after the second call request message is marked as discarded, the heap memory occupancy rate, port and data buffer load of the called terminal can be reduced, the invalid occupation of resources by invalid call request messages can be avoided, and the resource utilization rate can be improved.

[0081] It should be noted that, since the second call request message takes a long time to transmit during congestion, the network device may have already released the corresponding telephone instance. Therefore, for the SIP transaction corresponding to the discarded second call request message, the called terminal does not reply with any SIP response, which can avoid occupying signaling and transmission resources.

[0082] Step S304: Perform incoming call processing on the first call request message to establish an RTP media channel with the calling terminal.

[0083] It should be noted that the aforementioned description of step S304 also applies to this embodiment, and will not be repeated here.

[0084] It should be noted that this application does not limit the execution order of steps S303 to S304. Step S303 can be executed first, followed by step S304, or step S304 can be executed first, followed by step S303, or steps S303 and S304 can be executed simultaneously.

[0085] Step S305: In response to the identification that the network is not in a congested state, call request messages received within the time window are processed according to the first-in-first-out (FIFO) strategy.

[0086] As one possible implementation, if the network is not congested, it can be determined that the call request messages received within the time window are single messages. These messages are then processed according to a FIFO (First-In, First-Out) strategy, meaning the first call request to arrive is processed first. At this point, the call request messages arriving at the called terminal are sequentially delivered to the call control module, triggering the normal call processing flow.

[0087] In this embodiment, when no congestion is detected, i.e., when the terminal does not receive multiple INVITE messages with different Call-IDs within a short period of time, the FIFO strategy is used to process call request messages, without affecting call request message processing under normal network conditions. Furthermore, based on the network congestion identification result, the call request message processing strategy can be dynamically switched. That is, it can dynamically switch between the FIFO strategy and a strategy of discarding the second call request message and processing only the first call request message, giving the terminal adaptive capabilities.

[0088] As one possible implementation method, Figure 4 A flowchart illustrating yet another call method provided for an exemplary embodiment of this application.

[0089] It should be noted that the call method can be executed alone, or it can be executed together with any embodiment of this application or any possible implementation in the embodiment, or it can be executed together with any technical solution in the related technology. The embodiments of this application do not limit this.

[0090] like Figure 4 As shown, the call method may include, but is not limited to, the following steps: Step S401: Initialize the message processing module in the called terminal.

[0091] As one possible implementation, the message processing module within the called terminal may include, but is not limited to, a SIP protocol stack, or other processing modules.

[0092] Step S402: Wait to receive call request messages to obtain call request messages received within the time window.

[0093] As one possible implementation, the initialization of the call request message processing module can include, but is not limited to, the following initializations: Optionally, a message buffer can be initialized to temporarily cache pending call request messages received within a time window. The message buffer can also be used to record the Call-ID and arrival timestamp of each call request message.

[0094] Optionally, a congestion identification time window is initialized, for example, a default value of 1000 milliseconds (1 second), which is used to determine whether call request messages from different calling terminals have arrived within this time window.

[0095] Optionally, the congestion detection flag can be initialized, for example, with an initial value of false or 0. The initial value is used to indicate that the network is currently in a normal state.

[0096] Optionally, the arrival timestamp of the most recent call request message can be initialized to 0.

[0097] Step S403: Extract the call identifier and arrival timestamp of the call request message, and send them to the call request messages received within the cache time window in the message buffer.

[0098] As one possible implementation, the call request messages received within the time window are parsed to obtain the Call-ID of the call request message. Furthermore, the time when the call request message arrives at the called terminal is recorded as the arrival timestamp of the call request message.

[0099] As one possible implementation, after obtaining the Call-ID and arrival timestamp of the call request message, the call request messages received within the time window can be cached in the message buffer, along with the Call-ID and arrival timestamp of the call request message.

[0100] It should be noted that the aforementioned description of step S402 also applies to this embodiment, and will not be repeated here.

[0101] Step S404: Identify whether the network is in a congested state.

[0102] One possible implementation is to obtain the number of cached call request messages in the message buffer and, based on the number of cached call request messages in the message buffer, identify whether the network is in a congested state.

[0103] One possible implementation is to cache each received call request message in the message buffer within the time window. After the time window ends, the number of cached call request messages in the message buffer can be counted. It's understood that the counted number of cached call request messages represents the number of call request messages belonging to different Call-IDs. It's also understood that in congested scenarios, the message buffer can contain multiple call request messages belonging to different Call-IDs.

[0104] As one possible implementation, in response to a number of call request messages greater than or equal to two, the network is identified as being in a congested state, and step S405 is executed.

[0105] As one possible implementation, in response to a single call request message, if the network is not in a congested state, step S406 is executed.

[0106] As one possible implementation, in response to the identification of network congestion, the network congestion flag is configured as the first indication. When the network congestion flag is configured as the first indication, the called terminal can be triggered to adopt a strategy of discarding the second call request message and only processing the first call request message, thereby enabling the call to be connected.

[0107] As one possible implementation, in response to the detection that the network is not in a congested state, the network congestion flag is configured as a second indicator. When the network congestion flag is set to the second indicator, the called terminal can be triggered to adopt a FIFO strategy to connect the call.

[0108] It should be noted that the foregoing description of step S404 also applies to this embodiment, and will not be repeated here.

[0109] Step S405: Determine the latest arriving first call request message from the message buffer.

[0110] As one possible implementation, the message buffer caches the arrival timestamps of call request messages, and the arrival timestamps of call request messages can be compared to determine the latest arriving first call request message.

[0111] Step S406: Perform incoming call processing on the first call request message to establish an RTP media channel with the calling terminal.

[0112] It should be noted that the aforementioned description of step S406 also applies to this embodiment, and will not be repeated here.

[0113] Step S407: For the call request messages received in the message buffer, perform incoming call processing according to the FIFO strategy.

[0114] In one possible implementation, call request messages in the message buffer are sequentially submitted to the call control module, triggering the normal incoming call processing flow. The call control module checks whether the terminal is currently processing other call request messages. If the terminal is idle, it triggers ringing, media negotiation, and other processes sequentially according to the order in which the call request messages arrived. If the terminal is processing a previous call request message, it rejects (e.g., by sending 486 Busy Here) subsequent call request messages. If the user does not answer a previous call request message, subsequent call request messages are queued or rejected.

[0115] It should be noted that the aforementioned description of step S407 also applies to this embodiment, and will not be repeated here.

[0116] Step S408: Clear the message buffer area and / or reset the network congestion flag to return to the waiting state.

[0117] As one possible implementation, in response to the completion of the first call request message processing, the message buffer is cleared to avoid invalid messages occupying the buffer and to prevent the message from being repeatedly identified as being in a network congested state, which would cause the call request message to be processed inaccurately.

[0118] As one possible implementation, timing begins when the call request message is cached in the message buffer. That is, when the first call request message received within the time window arrives in the message buffer, timing is started. In response to the failure to complete network congestion identification and / or the determination of the first call request message within the set time, the call request messages cached in the message buffer are processed according to the FIFO policy to establish an RTP media channel with the calling terminal.

[0119] As one possible implementation, in response to the completion of the first call request message processing, the network congestion flag is reset to the second indication to enter a waiting state. Upon the arrival of a new call request message, the called terminal can be triggered to process the new call request message using a FIFO strategy.

[0120] In this embodiment of the application, a timeout protection mechanism or a downgraded FIFO strategy can be used to prevent the failure of incoming call processing due to an abnormality in the congestion identification itself. Furthermore, by downgrading to a FIFO strategy, the complete loss of call request messages can be avoided.

[0121] Optionally, starting from the first arrival of the call request message in the buffer, if congestion detection and / or INVITE message filtering (i.e., determining the first call request) are not completed within the timeout threshold T_timeout (default value is 10000 milliseconds, i.e., 10 seconds), the system automatically downgrades to a FIFO strategy. Optionally, in the event of network congestion identification failure, such as an anomaly like message buffer overflow, the system can also downgrade to a FIFO strategy.

[0122] In this embodiment of the application, by configuring a message buffer, call request messages received in a short time can be cached in a timely manner, avoiding the discarding of call request messages under conflict, which would lead to the inability to accurately identify whether the network is in a congested state, or to accurately determine the latest first call request message, thereby failing to improve the call connection rate.

[0123] The call method provided in this embodiment can be applied to, for example, Figure 5 The network structure shown includes a calling terminal, which can be labeled UE_A. There can be multiple calling terminals, for example, three, labeled UE_A1, UE_A2, and UE_A3. Furthermore, each calling terminal can send an INVITE message to the IMS core network to request the establishment of a call channel with the called terminal. Further, the IMS core network forwards the INVITE message sent by the calling terminal to the called terminal, which can be labeled UE_B.

[0124] As one possible implementation, the IMS core network may include a ProxyCall Session Control Function (P-CSCF) network element and a Serving Call Session Control Function (S-CSCF) network element, through which the calling terminal and the called terminal can communicate.

[0125] As one possible implementation, the SIP protocol stack of the called terminal can implement the call method provided in this application, and can identify network congestion status and filter the latest arriving INVITE message, that is, determine the latest arriving first call request message.

[0126] As one possible implementation, the call method in this application embodiment can be applied to scenarios where VoLTE or VoNR terminals receive incoming calls. When network congestion occurs, multiple SIP INVITE messages belonging to different calling terminals arrive at the called terminal in a short period of time, triggering the congestion detection and INVITE filtering processing mechanism of this solution.

[0127] To implement the above embodiments, this application also proposes a communication device.

[0128] Figure 6 This is a schematic diagram of the structure of a communication device provided for an exemplary embodiment of this application.

[0129] like Figure 6 As shown, the communication device 600 may include: an identification module 610, a determination module 620, and an execution module 630.

[0130] The identification module 610 is configured to identify the network congestion status based on the number of call request messages received within a time window.

[0131] The determination module 620 is configured to, in response to recognizing that the network is in a congested state, determine the latest arriving first call request message from the call request messages received within the time window; The execution module 630 is configured to perform incoming call processing on the first call request message in order to establish an RTP media channel with the calling terminal.

[0132] In one implementation of this application embodiment, the determining module 620 is further configured to: Obtain the arrival timestamp of the call request message; The call request message with the latest arrival timestamp is selected as the first call request message.

[0133] In one implementation of this application embodiment, the identification module 630 is further configured as follows: From the call request messages received within the time window, identify call request messages belonging to different call identifiers; Count the number of call request messages belonging to different call identifiers; In response to the number exceeding a set value, the network is determined to be in a congested state.

[0134] In one implementation of this application embodiment, the communication device 600 may further include: The parsing module is configured to parse the call request messages received within the time window before identifying the network congestion status based on the number of call request messages received within the time window, and obtain the call identifier of the call request message. The recording module is configured to record the time when the call request message arrives at the called terminal as the arrival timestamp of the call request message.

[0135] In one implementation of this application embodiment, the communication device 600 may further include: The discarding module is configured to, after determining the latest arriving first call request message, mark the second call request message (other than the first call request message) received within the time window as discardable. The release module is configured to release the transaction resources associated with the second call request message.

[0136] In one implementation of this application embodiment, the execution module 630 is further configured to: In response to the identification that the network is not in a congested state, the incoming call processing is performed on the call request messages received within the time window according to the FIFO strategy.

[0137] In one implementation of this application embodiment, the execution module 630 is further configured to: Send a response message to the network device for the first call request message; Negotiate Session Description Protocol (SDP) with the network device; In response to the end of SDP negotiation, the called terminal is triggered to ring. In response to the call being answered, a success response message is sent to the network device to establish an RTP media channel with the calling terminal.

[0138] In one implementation of this application, the communication device 600 may further include: The caching module is configured to cache the call request message in a message buffer based on the call identifier and arrival timestamp of the call request message; The determination module 620 is also configured to determine the latest arriving first call request message from the message buffer in response to recognizing that the network is in a congested state.

[0139] In one implementation of this application, the communication device 600 may further include: The configuration module is configured to perform at least one of the following operations: In response to the detection that the network is in a congested state, configure the network congestion flag as the first indication; In response to the completion of the first call request message processing, the network congestion flag is reset to the second indication to enter a waiting state; The clear module is configured to clear the message buffer in response to the completion of the first call request message processing.

[0140] In one implementation of this application, the communication device 600 may further include: The timing module is configured to start timing from caching the call request message in the message buffer; The execution module 630 is also configured to, in response to the determination that network congestion identification has not been completed within a set time and / or the first call request message has been determined, perform call processing on the call request messages already cached in the message buffer according to the FIFO strategy.

[0141] Network congestion is identified by counting the number of call request messages received within a time window. When congestion is detected, the latest arriving call request message is selected from those received within the time window. This message is then processed to establish a Real-time Transport Protocol (RTP) media channel with the calling terminal. Compared to related technologies that process call request messages in a FIFO (First-In, First-Out) manner during congestion, the earlier processed message often experiences the longest congestion time, leading to network devices releasing the corresponding phone instance due to timeouts, frequently resulting in all called calls failing to connect. Since the last call request message arrives in the network with the shortest transmission time, the network device is most likely not yet releasing the corresponding phone instance. In the event of network congestion, this application discards the earlier arriving call request messages, i.e., those with longer congestion times, and only processes the last arriving call request message, i.e., those with the shortest congestion time. This allows the terminal to prioritize trying to connect to the phone instance that is most likely still alive, thereby increasing the probability of a successful call connection. In turn, the worst-case scenario where all calls cannot be connected in a congested situation is improved to the point where at least one call may be connected.

[0142] To implement the above embodiments, this application also proposes a terminal, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the aforementioned... Figures 1 to 4 The call method described in any embodiment.

[0143] Figure 7 This is a schematic diagram of the structure of an electronic device provided for an exemplary embodiment of this application. The electronic device 800 includes a terminal.

[0144] Reference Figure 7 The electronic device 700 may include one or more of the following components: processing component 702, memory 704, power component 706, multimedia component 707, audio component 710, input / output (I / O) interface 712, sensor component 714, and communication component 716.

[0145] Processing component 702 typically controls the overall operation of electronic device 700, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 702 may include one or more processors 720 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 702 may include one or more modules to facilitate interaction between processing component 702 and other components. For example, processing component 702 may include a multimedia module to facilitate interaction between multimedia component 707 and processing component 702.

[0146] The memory 704 is configured to store various types of data to support the operation of the electronic device 700. The memory 704 can be implemented by any type of volatile or non-volatile storage device or a combination thereof.

[0147] Power component 706 provides power to various components of electronic device 700. Power component 706 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 700.

[0148] Multimedia component 707 includes a screen that provides an output interface between the electronic device 700 and the user. In some embodiments, multimedia component 707 includes a front-facing camera and / or a rear-facing camera. Each front-facing and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0149] Audio component 710 is configured to output and / or input audio signals. For example, audio component 710 includes a microphone (MIC) configured to receive external audio signals when electronic device 700 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 704 or transmitted via communication component 716. In some embodiments, audio component 710 also includes a speaker for outputting audio signals.

[0150] I / O interface 712 provides an interface between processing component 702 and peripheral interface modules, such as keyboards, click wheels, buttons, etc.

[0151] Sensor assembly 714 includes one or more sensors for providing state assessments of various aspects of electronic device 700. For example, sensor assembly 714 can detect the on / off state of electronic device 700, the relative positioning of components, changes in the position of electronic device 700 or one of its components, the presence or absence of user contact with electronic device 700, the orientation or acceleration / deceleration of electronic device 700, temperature changes of electronic device 700, the presence of nearby objects, etc.

[0152] Communication component 716 is configured to facilitate wired or wireless communication between electronic device 700 and other devices. Electronic device 700 can access wireless networks based on communication standards, such as WiFi, 4G, or 5G, or combinations thereof. In one exemplary embodiment, communication component 716 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 716 also includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module may be based on Radio Frequency Identification (RFID), Infrared Data Association (IrDA), Ultra-Wideband (UWB), Bluetooth, and other technologies.

[0153] In an exemplary embodiment, the electronic device 700 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0154] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 704 including instructions, which can be executed by a processor 720 of an electronic device 700 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, and optical data storage device, etc.

[0155] To implement the above embodiments, this application also proposes a chip, wherein the chip includes an interface circuit and a processing circuit coupled to each other. The interface circuit is used to input or output signals, and the processing circuit is configured to perform the call method provided in any of the foregoing embodiments.

[0156] Figure 8 This is a schematic diagram of a chip structure proposed as an exemplary embodiment of this application. See also... Figure 8 The diagram shown is a schematic representation of the structure of chip 800, but is not limited to this.

[0157] Chip 800 includes processing circuitry 801, which is configured to perform any of the above call methods.

[0158] In some embodiments, the chip 800 further includes one or more interface circuits 802. Optionally, the interface circuit 802 is connected to the memory 803, and the interface circuit 802 can be used to receive signals from the memory 803 or other devices, and the interface circuit 802 can be used to send signals to the memory 803 or other devices. For example, the interface circuit 802 can read instructions stored in the memory 803 and send the instructions to the processing circuit 801.

[0159] In some embodiments, the interface circuit 802 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processing circuit 801 performs other steps.

[0160] In some embodiments, the terms interface circuit, interface, transceiver pin, transceiver, etc., can be used interchangeably.

[0161] In some embodiments, chip 800 further includes one or more memories 803 for storing instructions. Optionally, all or part of the memories 803 may be located outside of chip 800.

[0162] To implement the above embodiments, this application also proposes a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the call method as described in any of the foregoing method embodiments.

[0163] To implement the above embodiments, this application also proposes a computer program product having a computer program stored thereon, which, when executed by a processor, implements the call method as described in any of the foregoing method embodiments.

[0164] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0165] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0166] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0167] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-including system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and compact disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0168] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0169] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0170] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0171] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.

Claims

1. A call method characterized by, The method includes: The network congestion status is identified based on the number of call request messages received within a time window. In response to the detection that the network is in a congested state, the latest arriving first call request message is determined from the call request messages received within the time window; Call processing is performed on the first call request message to establish a Real-Time Transport Protocol (RTP) media channel with the calling terminal.

2. The method of claim 1, wherein, The determination of the latest arriving first call request message from the call request messages received within the time window includes: Obtain the arrival timestamp of the call request message; The call request message with the latest arrival timestamp is selected as the first call request message.

3. The method of claim 1, wherein, The method of identifying network congestion based on the number of call request messages received within a time window includes: From the call request messages received within the time window, identify call request messages belonging to different call identifiers; Count the number of call request messages belonging to different call identifiers; In response to the number exceeding a set value, the network is determined to be in a congested state.

4. The method according to claim 1, characterized in that, Before identifying network congestion based on the number of call request messages received within a time window, the process also includes: The call request messages received within the time window are parsed to obtain the call identifier of the call request message; The time when the call request message arrives at the called terminal is recorded as the arrival timestamp of the call request message.

5. The method according to claim 1, characterized in that, After determining the latest arriving first call request message, the method further includes at least one of the following operations: Of the call request messages received within the time window, the second call request message other than the first call request message is marked as discarded; Release the transaction resources associated with the second call request message.

6. The method according to claim 1, characterized in that, The method further includes: In response to the identification that the network is not in a congested state, the incoming call processing is performed on the call request messages received within the time window according to the first-in-first-out (FIFO) strategy.

7. The method according to claim 1, characterized in that, The step of performing incoming call processing on the first call request message to establish a Real-Time Transport Protocol (RTP) media channel with the calling terminal includes: Send a response message to the network device for the first call request message; Negotiate Session Description Protocol (SDP) with the network device; In response to the end of SDP negotiation, the called terminal is triggered to ring. In response to the call being answered, a success response message is sent to the network device to establish an RTP media channel with the calling terminal.

8. The method according to any one of claims 1-7, characterized in that, The method of determining the latest arriving first call request message from the call request messages received within the time window further includes: Based on the call identifier and arrival timestamp of the call request message, cache the call request message in the message buffer. The latest arriving first call request message is determined from the message buffer.

9. The method according to claim 8, characterized in that, The method further includes at least one of the following operations: In response to the detection that the network is in a congested state, configure the network congestion flag as the first indication; In response to the completion of the first call request message processing, the network congestion flag is reset to the second indication to enter a waiting state; Upon completion of the first call request message processing, the message buffer is cleared.

10. The method according to claim 8, characterized in that, The method further includes: The timing begins from caching the call request message in the message buffer; In response to the failure to complete network congestion identification and / or the determination of the first call request message within a set time period, the call request messages already cached in the message buffer are processed according to the FIFO strategy.

11. A communication device, characterized in that, include: The identification module is configured to identify the network congestion status based on the number of call request messages received within a time window. The determination module is configured to, in response to recognizing that the network is in a congested state, determine the latest arriving first call request message from the call request messages received within the time window; The execution module is configured to perform incoming call processing on the first call request message in order to establish an RTP media channel with the calling terminal.

12. The apparatus according to claim 11, characterized in that, The determining module is further configured to: Obtain the arrival timestamp of the call request message; The call request message with the latest arrival timestamp is selected as the first call request message.

13. The apparatus according to claim 11, characterized in that, The identification module is further configured to: From the call request messages received within the time window, identify call request messages belonging to different call identifiers; Count the number of call request messages belonging to different call identifiers; In response to the number exceeding a set value, the network is determined to be in a congested state.

14. The apparatus according to any one of claims 11-13, characterized in that, The determining module is further configured to: Based on the call identifier and arrival timestamp of the call request message, cache the call request message in the message buffer. The latest arriving first call request message is determined from the message buffer.

15. A terminal, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, it implements the steps of the method as described in any one of claims 1 to 10.

16. A non-transitory computer-readable storage medium having computer program instructions stored thereon, characterized in that, When executed by a processor, the program instructions implement the steps of the method according to any one of claims 1 to 10.

17. A chip, characterized in that, The chip includes an interface circuit and a processing circuit that are coupled to each other. The interface circuit is used to input or output signals, and the processing circuit is used to implement the method of any one of claims 1 to 10.

18. A computer program product, characterized in that, Includes a computer program, which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 10.