A communication method, a terminal device, and a readable storage medium

Abstract

The application relates to the communication field, in particular to a communication method, a terminal device and a readable storage medium. The method comprises the following steps: when a calling device establishes a call through a wireless local area network, an invite message carrying a precondition label is sent to an IMS core network, and after receiving a 183 message carrying the precondition label sent by the IMS core network, a timer can be started immediately; if the calling device does not receive a session message sent by the IMS core network before the timer expires, the calling device can actively send a resource reservation negotiation message to the IMS core network to perform resource reservation negotiation. In this way, the calling device can perform voice and video calls under the wireless local area network, and the experience of establishing a call by a user is improved.

Description

Technical Field

[0001] This application relates to the field of communications, and in particular to a communication method, terminal device, and readable storage medium. Background Technology

[0002] In mobile communication systems, when a calling device needs to establish a call with another called device, the calling device can initiate a call request (invite) message to the IMS core network via a cellular network or wireless LAN, based on IP Multimedia Dubsystem (IMS) voice call technology, such as Voice over Wi-Fi (VoWi-Fi). Regardless of the network type, the calling device will include a precondition tag in the invite message, indicating that it has resource reservation capabilities. Resource reservation refers to the calling device reserving corresponding bearer resources for its own session with other called devices; the session will not be established until resource reservation is completed. It is understood that, based on the 3rd Generation Partnership Project (3GPP) regulations, terminal devices establishing calls via VoWi-Fi do not need to perform resource reservation.

[0003] For example, Figure 1 The diagram illustrates a scenario where a calling device initiates a call request. Mobile phone 10 (the calling device) uses VoWi-Fi communication to send an invite message with a precondition tag to the IMS core network. Upon receiving the invite message, the IMS core network can send a 183 message with the precondition tag to mobile phone 10, indicating that it has received the invite message and has resource reservation capabilities. Furthermore, because the received invite message carries the precondition tag, the call establishment process cannot proceed further until mobile phone 10 sends a resource reservation negotiation message.

[0004] However, since mobile phone 10 establishes the call based on VoWi-Fi, it does not require resource reservation. Therefore, mobile phone 10 will not send a resource reservation negotiation message to the IMS core network. The IMS core network will not receive the resource reservation negotiation message from mobile phone 10, nor will it send a ringing message (180 ringing) to mobile phone 10. The 180 ringing message indicates that another called device has received the call request from mobile phone 10 and is ringing. Based on this, mobile phone 10 fails to establish the call. Summary of the Invention

[0005] To address the aforementioned problems, this application provides a communication method, a terminal device, and a readable storage medium.

[0006] In a first aspect, this application provides a communication method applied to a terminal device. The method includes: in response to a first call initiation instruction, sending a call request to a core network, wherein the call request includes a resource reservation tag and is used to request the establishment of a first type of call connection with the core network, the first type of call connection including VoWi-Fi call; receiving a response message returned by the core network and starting a timer; corresponding to the timer duration exceeding a first duration threshold and no session message being received from the core network, sending a resource reservation negotiation message to the core network.

[0007] It is understood that the terminal device can refer to the calling device (such as mobile phone 10) mentioned in the embodiments of this application; the core network can refer to the IMS core network mentioned in the embodiments of this application; and the response message can be the 183 message mentioned in the embodiments of this application. VoWi-Fi is a voice call technology based on wireless local area network (WLAN) for transmitting voice calls. For example, WLAN can be a wireless fidelity network (Wi-Fi), that is, users can use terminal devices with VoWi-Fi capability to make voice and video calls in a Wi-Fi environment.

[0008] Understandably, based on 3GPP regulations, when a terminal device sends a session request message to the IMS core network, it needs to carry a resource reservation tag. After receiving the session message with the resource reservation tag, the IMS core network needs to wait for the terminal device to send a resource reservation negotiation message. Furthermore, terminal devices establishing calls via Wi-Fi do not need to perform resource reservation, while terminal devices establishing calls via cellular networks do.

[0009] In some embodiments of this application, a terminal device establishing a call based on a wireless local area network sends a first session message carrying a resource reservation tag to the IMS core network to request the establishment of a call. After receiving a response message from the IMS core network in response to the first session message, the terminal device can start timing. Furthermore, if the timing ends and no session message is received from the IMS core network, the terminal device can send a resource reservation negotiation message to the IMS core network.

[0010] The method provided in this application allows terminal devices communicating via a wireless local area network (WLAN), i.e., those establishing calls via VoWi-Fi, to start a timer upon receiving a 183 message carrying a precondition tag from the IMS core network. This enables the terminal device to proactively send a resource reservation negotiation message to the IMS core network to negotiate resource reservation if it does not receive a session message from the IMS core network after the timeout. Thus, after the IMS core network sends the 183 message carrying the precondition tag, it can wait for the terminal device to send a resource reservation negotiation message before continuing with subsequent processes. This allows the terminal device to communicate via WLAN, i.e., establish calls via VoWi-Fi, thereby improving the user experience for VoWi-Fi-based calls.

[0011] In one possible implementation of the first aspect above, in response to the first call initiation command, sending a call request to the core network includes: obtaining a first parameter of the terminal device, wherein the first parameter is a parameter identifying the network registration type of the terminal device; determining the network registration type of the terminal device based on the first parameter; corresponding to the terminal device communicating based on the first network registration type, determining whether the terminal device is the calling device, wherein the first network type is a wireless local area network, and the first network registration type corresponds to a call connection of the first type; and sending a first session message corresponding to the call request to the core network based on the terminal device being the calling device.

[0012] It is understood that the first parameter can refer to the "P-Access-Network-Info" or "RAT" of the terminal device mentioned in the embodiments of this application, which is used to identify the network registration type of the terminal device. If "P-Access-Network-Info = i-wlan" or "RAT = Wi-Fi", then the network registration type of the terminal device can be determined to be a wireless local area network. The first session message can refer to the invite message mentioned in the embodiments of this application, which is used to request the establishment of a call.

[0013] In one possible implementation of the first aspect above, determining the network registration type of the terminal device based on the first parameter includes: determining whether the terminal device is a calling device based on the second network registration type communication of the terminal device, wherein the second network type is a cellular network; and sending a first session message corresponding to the call request to the core network based on the terminal device being a calling device, wherein the first session message includes a resource reservation tag.

[0014] It is understood that if "P-Access-Network-Info = Cellular" or "RAT = NR" or "RAT = LTE", then the network registration type of the terminal device can be determined to be a cellular network, and the resource reservation tag can refer to the precondition tag mentioned in the embodiments of this application.

[0015] In other embodiments, if the terminal device is not the calling device, it can be determined that the terminal device is the called device, and the subsequent processes of the communication method provided in the embodiments of this application may not be executed.

[0016] In some embodiments of this application, regardless of whether the network registration type of the terminal device is the first network registration type or the second network registration type, the first session message sent by the terminal device can include a resource reservation tag.

[0017] In one possible implementation of the first aspect above, corresponding to the terminal device communicating based on the first network registration type, determining whether the terminal device is the calling device includes: obtaining first preset identification information of the terminal device, the first preset identification information being used to indicate the communication direction between the terminal device and the network; and determining the terminal device as the calling device based on the first preset identification information.

[0018] It is understood that the first preset identification information may refer to "UE TO NETWORK" mentioned in the embodiments of this application, which is used to identify the terminal device as the calling device. In some other embodiments, the first preset identification information may also be "NETWORK TO UE", which is used to identify the terminal device as the called device, and is not limited here.

[0019] In one possible implementation of the first aspect described above, the first parameter includes at least one of the parameter value "RAT" corresponding to the wireless access technology of the terminal device and the parameter value "P-Access-Network-Info" corresponding to the access network information.

[0020] In some embodiments, if "P-Access-Network-Info=i-wlan" or "RAT=Wi-Fi", then the network registration type of the terminal device can be determined to be a wireless LAN.

[0021] In other embodiments, if "P-Access-Network-Info = Cellular", "RAT = NR", or "RAT = LTE", then the network registration type of the terminal device can be determined to be a cellular network.

[0022] In one possible implementation of the first aspect above, in response to the first call initiation instruction, sending a call request to the core network further includes: corresponding to the terminal device communicating based on the first network registration type and the terminal device being the calling device, sending a first session message corresponding to the call request; receiving a response message sent by the core network corresponding to the first session message; wherein the first session message includes a resource reservation tag, and the resource reservation tag is used to indicate that the terminal device has resource reservation capability.

[0023] In one possible implementation of the first aspect above, receiving a response message sent by the core network corresponding to the first session message includes: determining whether the response message includes a resource reservation tag; corresponding to the response message including a resource reservation tag, starting a timer, and determining whether a session message sent by the core network is received within a first duration threshold, wherein the session message includes a ringback tone negotiation message.

[0024] It is understandable that the session messages sent by the core network may include color ringback tone negotiation messages. Color ringback tone negotiation messages can be of the following types: color ringback tone (CRBT) request messages, CRBT response messages, CRBT confirmation messages, CRBT update messages, CRBT control messages, etc., without being limited here.

[0025] In one possible implementation of the first aspect above, when the duration of the timed event exceeds a first duration threshold and no session message is received from the core network, a resource reservation negotiation message is sent to the core network, including: when the response message includes a resource reservation tag and it is determined that no session message is received from the core network within the first duration threshold, a resource reservation negotiation message is sent to the core network.

[0026] Based on this, for terminal devices communicating via Wi-Fi, i.e., terminal devices establishing calls via VoWi-Fi, a timer can be started upon receiving a 183 message carrying the precondition tag from the IMS core network. This allows the terminal device to proactively send a resource reservation negotiation message to the IMS core network to negotiate resource reservation if it does not receive a session message from the IMS core network after the timeout. Thus, after the IMS core network sends the 183 message with the precondition tag, it can wait for the terminal device to send a resource reservation negotiation message before continuing with subsequent processes. This allows the terminal device to communicate via Wi-Fi, i.e., to establish a call via VoWi-Fi, thereby improving the user experience for making calls via VoWi-Fi.

[0027] Secondly, embodiments of this application provide a terminal device, including a memory for storing instructions; and a processor for executing instructions to implement the communication method provided by the first aspect and various possible implementations of the first aspect.

[0028] Thirdly, embodiments of this application provide a readable storage medium storing instructions that, when executed on a terminal device, cause the terminal device to perform the communication methods provided in the first aspect and various possible implementations of the first aspect.

[0029] Fourthly, embodiments of this application also provide a computer program product, including a computer program / instruction that, when executed by a processor, implements the communication method provided by the first aspect and various possible implementations of the first aspect.

[0030] The beneficial effects of the second to fourth aspects mentioned above can be referred to the relevant descriptions in the first aspect and various possible implementations of the first aspect, which will not be repeated here. Attached Figure Description

[0031] Figure 1 A scenario diagram illustrating a calling device initiating a call request is shown based on methods provided in some embodiments;

[0032] Figure 2 According to the method provided in the embodiments of this application, a flowchart of a session interaction between a calling device and the IMS core network is shown;

[0033] Figure 3 According to the method provided in the embodiments of this application, a communication architecture diagram between a calling device and a network is shown;

[0034] Figure 4 A flowchart illustrating a communication method is shown based on the method provided in the embodiments of this application.

[0035] Figure 5 According to the method provided in the embodiments of this application, an interactive flowchart of communication between a calling device and the IMS core network is shown;

[0036] Figure 6 A detailed flowchart of a communication method is shown according to the method provided in the embodiments of this application;

[0037] Figure 7 A schematic diagram of the structure of a terminal device is shown according to the method provided in the embodiments of this application. Detailed Implementation

[0038] The illustrative embodiments of this application include, but are not limited to, a communication method, a terminal device, and a readable storage medium.

[0039] It is understood that the electronic devices in the embodiments of this application may also be referred to as terminals, user equipment (UE), mobile stations (MS), mobile terminals (MT), etc. Terminal devices may be mobile phones, smart TVs, wearable devices, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.

[0040] The technical solutions provided in this application can be applied to various communication systems, such as: 5th Generation (5G) mobile communication systems or new radio access technology (NR), Long Term Evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, Universal Mobile Telecommunications System (UMTS), etc. The technical solutions provided in this application can also be applied to future communication systems, such as 6th Generation (6G) mobile communication systems.

[0041] As mentioned earlier, when the calling device sends an invite message with a precondition tag to the IMS core network, the IMS core network, upon receiving the invite message with the precondition tag, needs to wait for the calling device to send a resource reservation negotiation message. However, since the calling device establishes the call based on VoWi-Fi, it does not need to reserve resources. Therefore, the calling device will not send a resource reservation negotiation message to the IMS core network. The IMS core network, not receiving the resource reservation negotiation message, will not send a ringing message (180 ringing, also known as a 180 message) to the calling device. The 180 message indicates that other called devices have received the call request from mobile phone 10 and are ringing. Based on this, mobile phone 10 fails to establish a call.

[0042] In addition, since the calling device does not receive the 180 message, it will not play a video ringback tone (VRBT), such as playing a video from the internet.

[0043] For example, Figure 2 A flowchart illustrating a session interaction between calling device 01 and IMS core network 02 is provided. The specific process of this session interaction may include:

[0044] 1. The calling device 01 sends an invite message to the IMS core network 02 via VoWi-Fi, carrying a resource reservation tag. This resource reservation tag is understood to be the precondition tag. In some embodiments, regardless of the voice call technology used, when the calling device 01 sends an invite message to the IMS core network 02 to request the establishment of a call, the invite message always carries a precondition tag, indicating that the calling device has the resource reservation capability of 01.

[0045] 2. The IMS core network 02 sends a 183 message to the calling device 01, carrying a resource reservation tag. In some embodiments, after receiving an invite message carrying a precondition tag, the IMS core network 02 sends a 183 message in response to the invite message to the calling device 01, and the 183 message carries a precondition tag, indicating that it has resource reservation capability.

[0046] 3. The calling device 01 does not send a resource reservation negotiation message to the IMS core network 02. In some embodiments, since the calling device 01 establishes a call based on VoWi-Fi, and according to 3GPP regulations, devices establishing calls via VoWi-Fi do not need to perform resource reservation. Therefore, the calling device 01 does not need to perform resource reservation, that is, it will not send a resource reservation negotiation message to the IMS core network 02.

[0047] 4. The IMS core network 02 does not send a response message "200ok" corresponding to the resource reservation negotiation to the calling device 01. In some embodiments, since the IMS core network 02 has not received the resource reservation negotiation message sent by the calling device, the IMS core network 02 will not send a response message "200ok" corresponding to the resource reservation negotiation to the calling device.

[0048] 5. The IMS core network 02 does not send a ringing message "180 ringing" to the calling device 01. In some embodiments, since the IMS core network 02 has not received a resource reservation negotiation message from the calling device 01, the IMS core network 02 will not send a ringing message "180 ringing" to the calling device 01.

[0049] 6. IMS core network 02 does not send a response message "200ok" corresponding to the invite message. In some embodiments, since IMS core network 02 has not received the resource reservation negotiation message sent by the calling device 01, nor has it sent the ringing message "180ringing", IMS core network 02 will not send a response message "200ok" corresponding to the invite message to the calling device 01.

[0050] Based on the above, the calling device 01 failed to establish a call.

[0051] It is understandable that if the calling device 01 establishes a call based on the cellular network, the calling device 01 needs to initiate a resource reservation negotiation message to the IMS core network 02.

[0052] It is understood that the invite message, resource reservation negotiation message, 180 message, and ringback tone negotiation message mentioned in the embodiments of this application all belong to the message corresponding to the session initiation protocol (SIP). SIP is a text-based application layer protocol that can be used to establish, modify, or terminate multimedia sessions.

[0053] It is understood that IMS-based voice call technologies can include VoWi-Fi, Voice over Long-Term Evolution (VoLTE), and Voice over NR (VoNR). VoWi-Fi is a voice call technology that transmits voice calls over a Wireless Local Area Network (WLAN), such as Wireless Fidelity (Wi-Fi). Users can use VoWi-Fi-enabled devices to make voice and video calls in a Wi-Fi environment. VoLTE and VoNR are both voice call technologies that transmit voice calls over cellular networks. Specifically, VoLTE is a voice call technology that transmits voice calls over a 4G network, allowing users to make voice and video calls over a 4G network. VoNR is a voice call technology that transmits voice calls over a 5G network, enabling users to make voice and video calls over a 5G network.

[0054] It is understood that the embodiments of this application involve wireless local area networks (WLANs), cellular networks, and IMS core networks. WLANs (such as Wi-Fi) and cellular networks are both wireless communication technologies. A WLAN is a local wireless communication network used for wireless network access between devices within a limited range. A cellular network, on the other hand, is a mobile communication network that supports mobility, allowing devices to communicate in different locations. Furthermore, the IMS core network provides a unified management and switching platform for multimedia communication services. Compared to Wi-Fi and cellular networks, the IMS core network focuses more on providing multimedia communication services. The IMS core network is a multimedia service based on the Internet Protocol (IP), supporting access to Wi-Fi and cellular networks (such as 2G, 3G, 4G, 5G, etc.), providing users with a variety of multimedia services, such as voice, video calls, text, and chat.

[0055] In communications, Wi-Fi is typically used for devices to connect to a network, while the IMS core network is responsible for managing and exchanging multimedia communication services. When a terminal device connects to the IMS network via Wi-Fi, it means that the terminal device has connected to the IMS core network through a Wi-Fi access point, thus enabling Wi-Fi-based multimedia communication services, i.e., VoWi-Fi.

[0056] To address the aforementioned issues, this application provides a communication method. The method includes: a calling device establishing a call via a wireless local area network (WLAN); when the calling device sends an invite message carrying a precondition tag and receives a 183 message carrying a precondition tag, a timer can be started immediately; if the calling device does not receive a session message from the network before the timer expires (the session message may include a ringback tone negotiation message, such as a 180 message), the calling device can proactively send a resource reservation negotiation message to the IMS core network. Subsequently, after the calling device and the IMS core network complete the resource reservation negotiation, subsequent processes can continue, enabling the calling device to establish a call with other called devices via the network.

[0057] It is understandable that when the calling device communicates via a wireless local area network, that is, when the calling device establishes a call via VoWi-Fi, VoWi-Fi is a voice call technology that transmits voice calls via a wireless local area network. Users can use calling devices with VoWi-Fi capability to conduct voice and video calls in a Wi-Fi environment.

[0058] With the above scheme, the calling device establishing a call via Wi-Fi can start a timer upon receiving a 183 message carrying the precondition tag. If no session message is received from the IMS core network after the timeout, the calling device can send a resource reservation negotiation message to the IMS core network to negotiate resource reservation. After the IMS core network sends the 183 message with the precondition tag, it can wait for the calling device to send a resource reservation negotiation message, and then continue with the subsequent procedures, enabling the calling device to successfully establish a call via Wi-Fi.

[0059] Figure 3 According to an embodiment of this application, a schematic diagram of a communication system architecture between a calling device and a network is shown.

[0060] It is understood that the layered architecture currently used in the communication system 30 applied to the calling device can divide the software into several layers, with communication between the layers through software interfaces. These layers may include the application layer 301, the framework layer 302, the kernel layer 303, the modem 304, etc. The following description takes the layer containing the functional modules involved in the communication method provided in the embodiments of this application as an example.

[0061] like Figure 3 As shown, the application layer 301 may include a series of application packages (Android application packages, APKs) 3011. APK 3011 may include gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, SMS, and third-party applications (not shown in the figure), which are not limited here.

[0062] The framework layer 302 provides an application programming interface (API) and programming framework for the applications in the application layer 301. The framework layer 302 includes some predefined functions.

[0063] The framework layer 302 may include a telephony module 3021 and a network detection module 3022. The telephony module 3021 can establish media sessions for the calling device and implement voice services under a packet-switched network. That is, the telephony module 3021 can initiate calls to and receive calls from the operator's network. The operator's network can be a cellular network or a wireless LAN, and this is not limited here.

[0064] The network detection module 3022 can determine the network communication status of the calling device based on TCP / IP.

[0065] It is understood that the framework layer 302 may also include system services, window manager, view system, resource manager, notification manager, display engine service, surfaceflinger, graphics system, etc. (not shown in the figure), and is not limited here.

[0066] Kernel layer 303 can include sockets and Transmission Control Protocol / Internet Protocol (TCP / IP). A socket is a communication mechanism that abstracts away the communication details of various protocols, providing an abstraction of the TCP / IP protocol. A socket is the interface through which applications communicate using the TCP / IP protocol, allowing for unified and convenient use of TCP / IP functionality. TCP / IP is a communication transmission protocol and the most fundamental communication protocol in a network.

[0067] The modem 304 includes a SIP module 3048 and an air interface protocol stack. The SIP module 3048 can be used to establish, modify, and terminate multimedia sessions between the calling device and the IMS core network, such as voice, video, IP telephony, video conferencing, and instant messaging data communication applications. Furthermore, the air interface protocol stack in the modem 304 can be used to establish, configure, and release various radio bearer services. The air interface protocol stack can be divided into three layers: the first layer is the physical layer (PHY), the second layer is the data link layer, and the third layer is the network layer.

[0068] Specifically, the first-layer PHY 3041 can be used to provide wireless resources and physical layer processing for the data of the second and third layers.

[0069] Layer 2 can be used to establish and manage data link transmission between network nodes on top of the basic transmission services provided by the physical layer. Specifically, Layer 2 can include Medium Access Control (MAC) 3042, Radio Link Control (RLC) 3043, and Packet Data Convergence Protocol (PDCP) 3044.

[0070] The MAC 3042 can handle processes such as mapping, multiplexing and dereferencing between logical channels and transport channels, uplink and downlink scheduling, and random access.

[0071] PDCP 3044 can handle encryption / decryption and integrity protection, reordering, support out-of-order delivery, and duplicate dropping to improve the reliability of data packet transmission.

[0072] Layer 3 can be used to handle all signaling processing for the interaction between the calling device and the network. Specifically, Layer 3 can include NAS 3047 and RRC 3046.

[0073] The NAS 3047, as a non-access stratum, is used to handle communication between the calling device and the access and mobility management function (AMF) module (not shown in the diagram). The AMF is responsible for functions such as authentication, authorization, registration, mobility management, and connection management for the calling device.

[0074] RRC 3046, as the access layer, is used to control and configure all radio resources for lower-layer protocols, enabling communication between the calling device and the base station. The RRC layer can handle all messages between the calling device and the base station, including system messages, security management, cell reselection, measurement reporting, handover and mobility, NAS message transmission, radio resource management, etc.

[0075] It is understandable that after establishing a connection with the base station based on RRC, the calling device can access the evolved packet core (EPC) via the IP protocol. That is, the calling device's modem can obtain a unique network address (IP address) based on the IP protocol and access the EPC core network through the IP address. The EPC core network is mainly used for managing user subscription data, mobility management, and data exchange and forwarding, and supports multiple access methods, such as Long-Term Evolution (LTE), 5G networks, and Wi-Fi.

[0076] Furthermore, after the calling device accesses the EPC core network, it can further access the IMS core network via the SIP module 3048. The IMS core network is a multimedia service based on the Internet Protocol (IP), supporting access from Wi-Fi and cellular networks (such as 2G, 3G, 4G, and 5G), and can provide users with multimedia services such as voice, video, text, and chat.

[0077] Figure 4 According to an embodiment of this application, a flowchart of a communication method is shown. It can be understood that... Figure 4The execution entity in the flowchart shown is the SIP module 3048 of the terminal device. The execution entity of each step will not be described again when introducing the execution content of each step below.

[0078] like Figure 4 As shown, the specific process includes:

[0079] S401: In response to a call initiation command, send an invite message including a resource reservation tag over the wireless LAN.

[0080] In some embodiments of this application, the SIP module 3048 detects corresponding call initiation commands based on user making VoIP calls, initiating voice or video calls, etc. Furthermore, in response to the call initiation command, the SIP module 3048 of the terminal device can send an invite message including a resource reservation tag over a wireless local area network, that is, establish a call with the IMS core network based on VoWi-Fi.

[0081] It is understandable that when a terminal device establishes a call, it needs to register with IMS. IMS is an IP-based multimedia service that enables terminal customers to carry out multimedia services such as voice, video, text, and chat. IMS also supports access from wireless LANs (such as Wi-Fi) and cellular networks (such as 2G, 3G, 4G, 5G, etc.).

[0082] S402: Received 183 message carrying resource reservation tag, started timing.

[0083] In some embodiments of this application, when the IMS core network receives an invite message from a terminal device, it can send a 183 message to the terminal device, carrying a precondition tag. The 183 message is a response message used to reply to the invite message, and the precondition tag in the 183 message indicates that the IMS core network has resource reservation capabilities.

[0084] Therefore, when the terminal device receives a 183 message carrying a resource reservation tag from the IMS core network, it can start a timer. It then determines whether it has received a session message from the IMS core network within a first time threshold. For example, the first time threshold could be 5ms, etc., and is not limited here.

[0085] It is understandable that the session messages sent by the IMS core network can be ringback tone negotiation messages. Ringback tone negotiation messages refer to a series of negotiation messages between the terminal device and the IMS core network during the provision of color ringback tone (CRBT) service, to ensure that both parties can correctly negotiate and exchange relevant ringback tone negotiation information.

[0086] S403: When the timing duration exceeds the first duration threshold and no session message is received from the IMS core network, a resource reservation negotiation message is sent to the IMS core network.

[0087] Understandably, based on 3GPP regulations, terminal devices establishing calls via VoWi-Fi do not need to perform resource reservation negotiation. Therefore, terminal devices based on wireless LAN communication do not need to perform resource reservation negotiation; that is, the terminal device's SIP module 3048 will not send a resource reservation negotiation message to the IMS core network. However, after sending an invite message carrying a resource reservation tag to the IMS core network in S401, the IMS core network needs to wait for the terminal device to send its own resource reservation negotiation message before it can further recommend the call establishment process.

[0088] In some embodiments of this application, if it is determined that no message has been received from the IMS core network within a first time threshold after receiving the 183 message from the IMS core network, the SIP module 3048 can directly send a resource reservation negotiation message to the IMS core network.

[0089] Thus, the calling device establishing a call via Wi-Fi can start a timer upon receiving a 183 message carrying a precondition tag. If no session message is received from the IMS core network after the timeout, the calling device can proactively send a resource reservation negotiation message to the IMS core network to negotiate resource reservation. The IMS core network can then receive this resource reservation negotiation message and continue with the subsequent process, enabling the calling device to communicate via Wi-Fi, i.e., establish a call with other called devices.

[0090] For example, Figure 5 A flowchart illustrating the communication process between calling device 01 and IMS core network 02 is provided. It can be understood that calling device 01 can exchange session messages with IMS core network 02 through SIP module 3048.

[0091] like Figure 5 As shown, the specific process includes:

[0092] S501: The calling device 01 sends an invite message to the IMS core network 02 based on VoWi-Fi, carrying a resource reservation tag.

[0093] In some embodiments of this application, the calling device 01 sends an invite message to the IMS core network 02 via VoWi-Fi to request the establishment of a call, and the invite message carries a resource reservation tag. The resource reservation tag is the precondition tag, indicating that the calling device 01 has resource reservation capabilities.

[0094] VoWi-Fi is a voice calling technology that transmits voice calls based on a wireless local area network (WLAN). For example, WLAN can be a wireless fidelity network (Wi-Fi). Users can use terminal devices with VoWi-Fi capability to make voice and video calls in a Wi-Fi environment.

[0095] S502: IMS core network 02 sends a 183 message to calling device 01, carrying a resource reservation tag.

[0096] In some embodiments of this application, after receiving an invite message carrying a precondition tag, the IMS core network 02 sends a 183 message in response to the invite message to the calling device 01. The 183 message carries a precondition tag, indicating that the IMS core network 02 has the ability to reserve resources.

[0097] S503: The calling device 01 starts timing to determine that no session message has been received within the first time threshold.

[0098] In some embodiments of this application, when the SIP module 3048 of the calling device 01 receives a 183 message carrying a precondition tag sent by the IMS core network 02, it starts timing and determines that no session message has been received from the IMS core network 02 within a first time threshold.

[0099] It is understandable that the session messages sent by the IMS core network can be ringback tone negotiation messages. Ringback tone negotiation messages refer to a series of negotiation messages between the terminal device and the IMS core network during the provision of color ringback tone (CRBT) service, to ensure that both parties can correctly negotiate and exchange relevant ringback tone negotiation information.

[0100] S504: The calling device 01 sends a resource reservation negotiation message to the IMS core network 02.

[0101] Understandably, based on 3GPP regulations, devices establishing calls via VoWi-Fi do not need to reserve resources. Therefore, the calling device 01, based on wireless LAN communication, does not need to negotiate resource reservations; that is, the SIP module 3048 of the calling device 01 will not send a resource reservation negotiation message to the IMS core network 02. After the aforementioned S501 sends an invite message carrying a resource reservation tag to the IMS core network 02, the IMS core network 02 needs to wait for the resource reservation negotiation message sent by the calling device 01 before it can further recommend the call establishment process.

[0102] In some embodiments of this application, when it is determined that no session message has been received from IMS core network 02 within a first time threshold after receiving message 183 from IMS core network 02, the calling device 01 can directly send a resource reservation negotiation message to IMS core network 02 based on SIP module 3048.

[0103] S505: IMS core network 02 sends a response message “200ok” corresponding to the resource reservation message to calling device 01.

[0104] In some embodiments of this application, when the IMS core network 02 receives a resource reservation negotiation message sent by the calling device 01, it can send a response message "200ok" corresponding to the resource reservation negotiation message to the calling device 01.

[0105] S506: The calling device 01 and the IMS core network 02 negotiate the ringback tone.

[0106] In some embodiments of this application, after the calling device 01 and the IMS core network 02 complete the resource reservation negotiation, the calling device 01 and the IMS core network 02 can negotiate the ringback tone by sending ringback tone negotiation messages to each other.

[0107] It is understandable that the color ring back tone negotiation message refers to a series of negotiation messages between the terminal device and the IMS core network when providing color ring back tone (CRBT) service, in order to ensure that both parties can correctly negotiate and exchange relevant color ring back tone negotiation information.

[0108] For example, ringback tone negotiation messages can be of the following types: (1) CRBT request message: A request message sent by the terminal device to the IMS core network to request to obtain or change the ringback tone service. (2) CRBT response message: A message from the IMS core network responding to the request message sent by the terminal device, including acknowledging receipt of the request and returning ringback tone negotiation information. (3) CRBT confirmation message: A confirmation message sent by the terminal device after receiving the response message from the IMS core network to confirm receipt of the response from the IMS core network. (4) CRBT update message: An update message sent by the terminal device to the IMS core network to update the ringback tone information or notify the network of the ringback tone playback status. (5) CRBT control message: Used for the control and management of the ringback tone service between the terminal device and the IMS core network, such as pausing playback, stopping playback, setting loop playback, etc., which are not limited here.

[0109] S507: The calling device 01 sends a ringing message "180ringing" to the IMS core network 02.

[0110] In some embodiments of this application, resource reservation negotiation and ringback tone negotiation are completed based on the calling device 01 and the IMS core network 02. Furthermore, the calling device 01 can send a ringing message "180 ringing" to the IMS core network 02.

[0111] S508: IMS core network 02 sends a response message “200ok” corresponding to the invite message to calling device 01.

[0112] In some embodiments of this application, after the IMS core network 02 sends a ringing message "180ringing" to the calling device 01, the IMS core network 02 can further send a response message "200ok" corresponding to the invite message to the calling device 01, thereby establishing the call.

[0113] Based on the above Figure 3 The communication architecture shown below, combined with Figure 6 The flowchart shown below illustrates the technical solution of this application in detail.

[0114] Figure 6 A schematic flowchart of a communication method is shown according to an embodiment of this application. It can be understood that... Figure 6 The entity executing the process shown can be one of the above. Figure 3 The SIP module 3048 of the terminal device mentioned in the text will not be described again when introducing the execution content of each step.

[0115] like Figure 6 As shown, the specific process includes:

[0116] S601: A call initiation command was detected, and the IMS registration information of the terminal device was checked.

[0117] In some embodiments of this application, the SIP module 3048 detects corresponding call initiation commands based on user making VoIP calls, initiating voice or video calls, etc. Based on this, the SIP module 3048 can further detect the IMS registration information of the terminal device, thereby obtaining the network registration type registered by the terminal device, etc.

[0118] It is understandable that when a terminal device needs to establish a call, it needs to register with IMS. IMS is an IP-based multimedia service that enables terminal customers to carry out multimedia services such as voice, video, text, and chat. IMS also supports access from wireless LANs (such as Wi-Fi) and cellular networks (such as 2G, 3G, 4G, 5G, etc.).

[0119] S602: Determine whether the network registration type of the terminal device is wireless LAN.

[0120] In some embodiments of this application, the IMS registration detection result of the terminal device is obtained through the SIP module 3048. Based on the IMS registration detection result, the parameter value "P-Access-Network-Info" corresponding to the access network information of the terminal device can be obtained. "P-Access-Network-Info" is a parameter that identifies the network registration type of the terminal device. If "P-Access-Network-Info = i-wlan", and "i-wlan" is a specific value used to explicitly identify WLAN (Wireless Local Area Network), then it can be determined that the terminal device accesses the mobile network through WLAN, that is, the network registration type of the terminal device is Wireless Local Area Network.

[0121] In other embodiments of this application, the IMS registration detection result of the terminal device is obtained through the SIP module 3048. Based on the IMS registration detection result, the radio access technology (RAT) of the terminal device can be obtained. The network registration type of the terminal device can be determined through the RAT of the terminal device. If "RAT = Wi-Fi", then the network registration type of the terminal device can be determined to be a wireless local area network.

[0122] It's understandable that RAT can also reflect the network standard registered by the terminal device, such as Wi-Fi, LTE, NR, etc., which are not limited here. Among them, Wi-Fi belongs to WLAN, that is, wireless local area network, while LTE, NR, etc. belong to cellular network.

[0123] S603: Determine whether the terminal device is the calling device.

[0124] In some embodiments of this application, after determining that the terminal device accesses the mobile network via a wireless local area network, the SIP module 3048 can further determine whether the current terminal device is the calling device. It can be understood that the calling device is the terminal device used to send an invite message to request the establishment of a call.

[0125] If the judgment result is yes, proceed to S604 and send an invite message carrying a resource reservation tag.

[0126] If the result is negative, the process ends.

[0127] For example, when the SIP module 3048 detects that the system configuration file of the terminal device includes "UE TO NETWORK", it can determine that the current terminal device is the calling device.

[0128] It is understood that in some other embodiments, when the SIP module 3048 detects that the system configuration file of the terminal device includes "NETWORK TO UE", it can determine that the current terminal device is the called device.

[0129] S604: Send an invite message carrying a resource reservation tag.

[0130] Understandably, based on 3GPP regulations, the calling device sends an invite message to the IMS core network, and the invite message needs to carry a precondition tag, indicating that the calling device has the ability to reserve resources.

[0131] In some embodiments of this application, when it is determined that the terminal device is the calling device, and a call is requested to be established based on the wireless local area network, the calling device's SIP module 3048 can further send an invite message carrying a precondition tag to the IMS core network to request the establishment of the call.

[0132] S605: Get message 183.

[0133] In some embodiments of this application, after receiving an invite message from a calling device, the IMS core network sends a 183 message to the calling device, carrying a precondition tag. The 183 message is a response message used to reply to the invite message, and the precondition tag in the 183 message indicates that the IMS core network has resource reservation capabilities. Based on this, the calling device can obtain the 183 message sent by the IMS core network.

[0134] S606: Determine whether the 183 message includes a resource reservation tag.

[0135] In some embodiments of this application, based on the 183 message obtained in S605, it is determined whether the 183 message includes a resource reservation tag.

[0136] If the judgment result is yes, proceed to S607 to determine whether a session message sent by the core network has been received within the first time duration threshold.

[0137] If the result is negative, the process ends.

[0138] S607: Determine whether a session message sent by the core network has been received within the first time duration threshold.

[0139] In some embodiments of this application, when the SIP module 3048 of the calling device receives the 183 message sent by the IMS core network, it starts timing and determines whether a session message sent by the IMS core network has been received within a first duration threshold.

[0140] If the judgment result is yes, the process ends.

[0141] If the judgment result is negative, proceed to S608 and send a resource reservation negotiation message.

[0142] It is understandable that the session messages sent by the IMS core network can be ringback tone negotiation messages. Ringback tone negotiation messages refer to a series of negotiation messages between the terminal device and the IMS core network during the provision of color ringback tone (CRBT) service, to ensure that both parties can correctly negotiate and exchange relevant ringback tone negotiation information. Furthermore, ringback tone negotiation messages can include one or more of the following negotiation messages:

[0143] (1) CRBT Request Message: A request message sent by the terminal device to the IMS core network to request to obtain or change the ringback tone service.

[0144] (2) CRBT response message: The message in which the IMS core network responds to the request message sent by the terminal device, including acknowledging receipt of the request and returning ringback tone negotiation information.

[0145] (3) CRBT confirmation message: A confirmation message sent by the terminal device after receiving the response message from the IMS core network to confirm receipt of the response from the IMS core network.

[0146] (4) CRBT update message: An update message sent by the terminal device to the IMS core network to update the ringback tone information or notify the network ringback tone playback status, etc.

[0147] (5) CRBT Control Messages: Used for controlling and managing ringback tone services between terminal devices and the IMS core network, such as pausing playback, stopping playback, and setting loop playback. No further limitations are specified here.

[0148] S608: Send a resource reservation negotiation message.

[0149] Understandably, based on 3GPP regulations, devices establishing calls via VoWi-Fi do not need to reserve resources. Therefore, the calling device using WLAN communication does not need to negotiate resource reservations; that is, the calling device's SIP module 3048 will not send a resource reservation negotiation message to the IMS core network. After the aforementioned S604 sends an invite message carrying a resource reservation tag to the IMS core network, the IMS core network needs to wait for the calling device to send its own resource reservation negotiation message before it can further recommend the call establishment process.

[0150] In some embodiments of this application, if it is determined that no session message has been received from the IMS core network within a first time threshold after receiving the 183 message sent by the IMS core network, the SIP module 3048 can directly send a resource reservation negotiation message to the IMS core network.

[0151] Thus, the calling device establishing a call via Wi-Fi can start a timer upon receiving a 183 message carrying a precondition tag. If no session message is received from the IMS core network after the timeout, the calling device can proactively send a resource reservation negotiation message to the IMS core network to negotiate resource reservation. The IMS core network can then receive this resource reservation negotiation message and continue with the subsequent process, enabling the calling device to communicate via Wi-Fi, i.e., establish a call with other called devices.

[0152] S609: Determine whether the terminal device is the calling device.

[0153] In some embodiments of this application, after determining that the terminal device is not accessing the mobile network via a wireless local area network, the SIP module 3048 can further determine whether the current terminal device is the calling device. It can be understood that the calling device is the terminal device used to send an invite message to request the establishment of a call.

[0154] If the judgment result is yes, proceed to S610 and send an invite message carrying a resource reservation tag.

[0155] If the result is negative, the process ends.

[0156] For example, when the SIP module 3048 detects that the system configuration file of the terminal device includes "UE TO NETWORK", it can determine that the current terminal device is the calling device.

[0157] It is understood that in some other embodiments, when the SIP module 3048 detects that the system configuration file of the terminal device includes "NETWORK TO UE", it can determine that the current terminal device is the called device.

[0158] S610: Send an invite message carrying a resource reservation tag.

[0159] Understandably, based on 3GPP regulations, when a calling device sends an invite message to the IMS core network, the invite message needs to carry a precondition tag.

[0160] In some embodiments of this application, when it is determined that the terminal device is not accessing the mobile network through a wireless local area network and the terminal device is the calling device, the SIP module 3048 of the calling device can send an invite message carrying a precondition tag to the IMS core network to request the establishment of a call.

[0161] Through the above scheme, the calling device establishing a call based on a wireless LAN can start a timer after receiving a 183 message carrying a precondition tag. If no session message is received from the IMS core network after the timeout, the calling device can proactively send a resource reservation negotiation message to the IMS core network to negotiate resource reservation. The IMS core network can then obtain this resource reservation negotiation message and continue the subsequent process, enabling the calling device to communicate over the wireless LAN, i.e., to establish a call with other called devices via VoWi-Fi, thus improving the user experience for VoWi-Fi-based calls.

[0162] further, Figure 7 A schematic diagram of a terminal device 100 is shown according to some embodiments of this application. The communication methods mentioned in the embodiments of this application can be implemented based on the terminal device 100.

[0163] like Figure 7 As shown, the terminal device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a subscriber identification module (SIM) card interface 195, a communication device 196, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a proximity sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and a color temperature sensor 180N, etc.

[0164] Processor 110 may include one or more processing units, such as: application processor (AP), microcontroller unit (MCU), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0165] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0166] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 may store data that the processor 110 has just used or that is being reused. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0167] In some embodiments, the processor 110 may be used to execute the communication methods provided in the various embodiments of this application.

[0168] USB port 130 is a USB standard compliant interface, specifically a Mini USB port, Micro USB port, or USB Type-C port. USB port 130 can be used to connect a charger to charge terminal device 100, and can also be used for data transfer between terminal device 100 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as AR devices.

[0169] The charging management module 140 receives charging input from the charger. While charging the battery 142, the charging management module 140 can also supply power to the terminal device 100 through the power management module 141.

[0170] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, internal memory 121, display 194, camera 193, and wireless communication module 160, etc.

[0171] The wireless communication function of the terminal device 100 can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0172] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals, that is, wireless carrier information.

[0173] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the terminal device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1.

[0174] The wireless communication module 160 can provide solutions for wireless communication applications on the terminal device 100, including wireless local area networks (WLANs) (such as Wi-Fi), Bluetooth (BT), near field communication (NFC), global navigation satellite system (GNSS), frequency modulation (FM), infrared (IR), and ultra-wideband (UWB). The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 can receive electromagnetic waves via antenna 2, filter and amplify the received electromagnetic waves, and transmit them to a modem processor for demodulation. The wireless communication module 160 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 2.

[0175] Terminal device 100 implements interface display functions through a GPU, display screen 194, and application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0176] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a mini-LED, a micro-LED, a micro-OLED, a quantum dot light-emitting diode (QLED), etc.

[0177] Camera 193 is used to capture still images or videos.

[0178] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to perform data storage functions.

[0179] Internal memory 121 can be used to store executable program code, including instructions, such as those in the aforementioned memory 103. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function, etc. The data storage area may store data created during the use of terminal device 100, such as control identifiers of security controls, screenshot redraw policy identifiers corresponding to security controls, and patterns, images, and text corresponding to screenshot redraw policies. In addition, internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. The processor 110 executes various functional applications of terminal device 100 by running instructions stored in internal memory 121 and / or instructions stored in memory located in processor 110.

[0180] Terminal device 100 can implement audio functions through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0181] Touch sensor 180K, also known as a "touch device," can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touchscreen." Touch sensor 180K detects touch operations applied to or near it. It transmits the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194.

[0182] Motor 191 can generate vibration alerts.

[0183] Indicator 192 can be an indicator light, used to indicate charging status, power changes, or to indicate messages, missed calls, notifications, etc.

[0184] The SIM card interface 195 is used to connect the SIM card.

[0185] It is understood that the structure of the terminal device 100 shown in the embodiments of this application does not constitute a specific limitation on the terminal device 100. In other embodiments of this application, the terminal device 100 may include more or fewer components than shown, or combine some components, or split some components, or have different component arrangements. The components shown may be implemented in hardware, software, or a combination of software and hardware.

[0186] This application also provides a program product that, when executed on a terminal device, enables the terminal device to implement the communication methods provided in the foregoing embodiments.

[0187] This application also provides a readable storage medium storing one or more programs, which, when executed by a terminal device, enable the terminal device to implement the communication methods provided in the foregoing embodiments.

[0188] The embodiments disclosed in this application can be implemented in hardware, software, firmware, or a combination of these implementation methods. Embodiments of this application can be implemented as computer programs or program code executable on a programmable system, the programmable system including at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0189] Program code can be applied to input instructions to execute the functions described in this application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, the processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), or a microprocessor. The program code can be implemented using a high-level programming language or an object-oriented programming language to communicate with the processing system.

[0190] When necessary, the program code can also be implemented using assembly language or machine language. In fact, the mechanism described in this application is not limited to any particular programming language. In either case, the language can be a compiled language or an interpreted language.

[0191] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may be implemented as instructions carried or stored thereon on one or more temporary or non-temporary machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, the instructions may be distributed via a network or through other computer-readable media. Therefore, machine-readable media may include any mechanism for storing or transmitting information in a machine-readable (e.g., computer-readable) form, including but not limited to floppy disks, optical disks, CD-ROMs, magneto-optical disks, read-only memory (ROM), random access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic cards or optical cards, flash memory, or tangible machine-readable storage for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) using the Internet in the form of electrical, optical, acoustic, or other forms of propagated signals. Therefore, machine-readable media includes any type of machine-readable medium suitable for storing or transmitting electronic instructions or information in a machine-readable (e.g., computer-readable) form.

[0192] In the accompanying drawings, certain structural or methodological features are shown in a specific arrangement and / or order. However, it should be understood that such a specific arrangement and / or order may not be necessary. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the illustrative drawings. Furthermore, the inclusion of structural or methodological features in a particular figure does not imply that such features are required in all embodiments, and in some embodiments, these features may be omitted or may be combined with other features.

[0193] It should be noted that all units / modules mentioned in the device embodiments of this application are logical units / modules. Physically, a logical unit / module can be a physical unit / module, a part of a physical unit / module, or a combination of multiple physical units / modules. The physical implementation of these logical units / modules themselves is not the most important factor; the combination of functions implemented by these logical units / modules is the key to solving the technical problem proposed in this application. Furthermore, to highlight the innovative aspects of this application, the above-described device embodiments of this application have not introduced units / modules that are not closely related to solving the technical problem proposed in this application. This does not mean that the above-described device embodiments do not contain other units / modules.

[0194] It should be noted that in the examples and description of this patent, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element. While this application has been illustrated and described with reference to certain preferred embodiments, those skilled in the art will understand that various changes in form and detail may be made therein without departing from the scope of this application.

Claims

1. A communication method, characterized in that, Applied to a terminal device, the method includes: In response to the first call initiation command, a first session message corresponding to the call request is sent to the core network, wherein the first session message is an invite message, including a resource reservation tag, and the first session message is used to request to establish a first type of call connection with the core network, the first type of call connection including VoWi-Fi call; Upon receiving the response message returned by the core network, a timer is started, wherein the response message is a 183 message carrying a resource reservation tag; If the duration of the timed event exceeds a first duration threshold and no session message is received from the core network, a resource reservation negotiation message is sent to the core network.

2. The method according to claim 1, characterized in that, The first session message sent to the core network in response to the first call initiation command includes: Obtain a first parameter of the terminal device, wherein the first parameter is a parameter that identifies the network registration type of the terminal device; The network registration type of the terminal device is determined based on the first parameter; Corresponding to the terminal device communicating based on the first network registration type, it is determined whether the terminal device is the calling device, wherein the first network registration type is a wireless local area network, and the first network registration type corresponds to a first type of call connection; Based on the terminal device being the calling device, the first session message corresponding to the call request is sent to the core network.

3. The method according to claim 2, characterized in that, The step of determining whether the terminal device is a calling device based on the first network registration type communication corresponding to the terminal device includes: Obtain first preset identification information of the terminal device, wherein the first preset identification information is used to indicate the communication direction between the terminal device and the network; The terminal device is determined to be the calling device based on the first preset identification information.

4. The method according to claim 2, characterized in that, The first parameter includes at least one of the parameter value "RAT" corresponding to the wireless access technology of the terminal device and the parameter value "P-Access-Network-Info" corresponding to the access network information.

5. The method according to claim 2, characterized in that, The step of sending a call request to the core network in response to the first call initiation command further includes: When the terminal device communicates based on the first network registration type and the terminal device is the calling device, a first session message corresponding to the call request is sent. Receive a response message sent by the core network corresponding to the first session message; The first session message includes a resource reservation tag, which is used to indicate that the terminal device has resource reservation capability.

6. The method according to claim 5, characterized in that, The receipt of the response message corresponding to the first session message sent by the core network includes: Determine whether the response message includes a resource reservation tag; The response message includes a resource reservation tag, starts timing, and determines whether a session message sent by the core network is received within a first duration threshold, wherein the session message includes a ringback tone negotiation message.

7. The method according to claim 1, characterized in that, If the duration corresponding to the timing exceeds a first duration threshold and no session message is received from the core network, a resource reservation negotiation message is sent to the core network, including: If the response message includes a resource reservation tag and it is determined that no session message sent by the core network has been received within the first time threshold, a resource reservation negotiation message is sent to the core network.

8. A terminal device, characterized in that, include: The processor and memory, the memory including physical memory and secondary memory, are used to store instructions executed by one or more processors of the terminal device; And a processor, configured to execute the instructions to cause the terminal device to implement the communication method of any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed by an electronic device, causes the electronic device to implement the communication method according to any one of claims 1 to 7.

10. A computer program product, characterized in that, Includes a computer program / instruction that, when the computer program product is run on an electronic device, causes the electronic device to perform the communication method according to any one of claims 1 to 7.

Images