Call method and apparatus

During the call setup process, the IMS network element uses narrowband high-orbit satellite access technology to determine the capabilities of the terminal equipment, directly generating 180-ring messages, simplifying the signaling process, solving the call latency problem, and improving the user experience.

WO2026233131A1PCT designated stage Publication Date: 2026-11-12HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2026/092644
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-04-23
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In existing call setup mechanisms, the signaling interaction process between the calling and called sides results in significant call latency, impacting user experience.

Method used

During the call setup process, the IMS network element uses narrowband high-orbit satellite access technology to determine the capabilities of the terminal equipment and directly generates a 180-ring message, replacing the traditional 183-session progress message and other signaling interactions, thus simplifying the signaling process and reducing call latency.

Benefits of technology

It effectively reduces the number of signaling interactions during call setup, reduces call latency, and improves user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2026092644_12112026_PF_FP_ABST
    Figure CN2026092644_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to the field of communications. Provided are a call method and apparatus, which can reduce a call delay and improve the user experience. The method comprises: a first IMS network element sending a first message to a second device, wherein the first message is used by a first terminal device to call a second terminal device, and the first message comprises media request information; receiving a second message from the second device, wherein the second message is used for indicating that a session is in progress, and the second message further comprises first media response information; determining that the first terminal device supports the capability of executing a call on the basis of narrowband high-orbit satellite access technology, and / or that the first terminal device accesses a network on the basis of the narrowband high-orbit satellite access technology; generating a third message, wherein the third message is used for indicating that the second terminal device has rung; and sending the third message to the first device.
Need to check novelty before this filing date? Find Prior Art

Description

Calling methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202510602390.8, filed with the State Intellectual Property Office of China on May 9, 2025, entitled "Calling Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a calling method and apparatus. Background Technology

[0003] The 3rd Generation Partnership Project (3GPP) standard defines a call setup mechanism, through which a call can be established between the calling party and the called party, thereby enabling a conversation between them.

[0004] Specifically, the call setup mechanism mainly includes four processes: call initiation media negotiation, temporary message confirmation, resource reservation confirmation, and ringing connection. Each of these four processes requires signaling interaction between the calling and called parties, resulting in significant call delays.

[0005] Therefore, how to reduce call latency is an urgent problem to be solved. Summary of the Invention

[0006] The calling method and apparatus provided in this application can reduce call latency and improve user experience.

[0007] Firstly, embodiments of this application provide a calling method, which can be executed by a first IMS network element. Unless otherwise specified, the "first IMS network element" in this application can be the first IMS network element itself, a component applicable to the first IMS network element (e.g., a communication module, processor, circuit, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the first IMS network element. The method includes: sending a first message to a second device, the first message being used by a first terminal device to call the second terminal device, the first message including media request information; receiving a second message from the second device, the second message indicating that a session is in progress, the second message also including first media response information; determining that the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on narrowband high-orbit satellite access technology; and generating a third message, the third message indicating that the second terminal device has been ringing; and sending the third message to the first device. Wherein, the first IMS network element is a network element in the IMS network accessed by the first terminal device, and correspondingly, the second device is a network element in the IMS network accessed by the second terminal device, and the first device is the first terminal device; or, the first IMS network element is a network element in the IMS network accessed by the second terminal device, and correspondingly, the second device is the second terminal device, and the first device is a network element in the IMS network accessed by the first terminal device.

[0008] Based on the first aspect, during the process of the calling terminal device (i.e., the first terminal device) calling the called terminal device (the second terminal device) (i.e., from the transmission of INVITE messages (such as the first message, which is used by the calling terminal device to call the called terminal device and includes media request information) between the calling and called parties), the IMS network element of the calling / called party (i.e., the first IMS network element) can receive 183 session processes from its upstream node (i.e., the second device; wherein, the first IMS network element is a network element in the IMS network accessed by the calling terminal device, and correspondingly, the second device is a network element in the IMS network accessed by the called terminal device; the first IMS network element is a network element in the IMS network accessed by the second terminal device, and correspondingly, the second device is the called terminal device). (Progress message) (as in the second message, which indicates that the session is in progress; the second message also includes first media response information; further, the calling / called side IMS network element can obtain whether the calling side terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether the calling side terminal device accesses the network based on narrowband high-orbit satellite access technology, and if the calling side terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or if the calling side terminal device accesses the network based on narrowband high-orbit satellite access technology, it generates a 180 ring message; and sends the 180 ring message to its next node (i.e., the first device; wherein, the first IMS network element is a network element in the IMS network accessed by the first terminal device, and correspondingly, the first device is the calling side terminal device; the first IMS network element is a network element in the IMS network accessed by the called side terminal device, and correspondingly, the first device is a network element in the IMS network accessed by the calling side terminal device.)

[0009] In other words, after receiving a 183 session progress message from its upstream node, the calling / called IMS network element can determine whether to generate a 180 ring and send it to the next node by judging whether the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether the calling terminal device accesses the network based on narrowband high-orbit satellite access technology. For example, it can convert the 183 session progress message into a 180 ring message and send it to its next node. Specifically, if the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or if the calling terminal device accesses the network based on narrowband high-orbit satellite access technology, then the calling / called IMS network element can directly convert the 183 session progress message into a 180 ring message and send it to its next node. At this point, the IMS network element on the calling / called side and the calling terminal device interact with each other using a 180ring message instead of a 183 session progress message. This eliminates the need for the IMS network element on the calling / called side and the calling terminal device to transmit 183 session progress messages, temporary message acknowledgment (PRACK) messages, and update (UPDATA) messages. In other words, the IMS network element on the calling / called side and the calling terminal device no longer need to sequentially transmit request (INVITE) messages, 183 session progress messages, PRACK messages, UPDATA messages, and 180ring messages to complete the call setup process. Instead, the 180ring message is transmitted directly after the INVITE message. Therefore, during the call setup process, the IMS network element on the calling / called side and the calling terminal device only need to complete signaling interactions such as INVITE and 180ring messages. This reduces the number of signaling messages exchanged during the call setup process, thereby reducing call latency and improving user experience.

[0010] In one possible design, determining that the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses a network based on narrowband high-orbit satellite access technology, includes: receiving a fourth message from the first device, the fourth message instructing the first terminal device to call a second terminal device, and instructing the first terminal device to support the ability to perform calls based on narrowband high-orbit satellite access technology, or that the first terminal device accesses a network based on narrowband high-orbit satellite access technology, at least one of the following: the fourth message includes media request information.

[0011] In one possible design, the supported header field in the fourth message is used to indicate that the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology; and / or, the private access network information (P-ANI) header field in the fourth message indicates that the first terminal device accesses the network based on narrowband high-orbit satellite access technology.

[0012] Based on the two possible designs mentioned above, the ability of the first terminal device to perform calls based on narrowband high-orbit satellite access technology, and / or the indication of the first terminal device accessing the network based on narrowband high-orbit satellite access technology, can be carried in a message that instructs the first terminal device to call the second terminal device, and includes media request information (i.e., a fourth message, such as an INVITE message). In other words, during the call process establishment, there is no need to configure new signaling; instead, this indication is carried in the existing signaling to save signaling overhead and facilitate implementation.

[0013] In one possible design, the first IMS network element is a network element in the IMS network accessed by the first terminal device. Determining that the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on the narrowband high-orbit satellite access technology, includes: receiving a fifth message from a first core network device, the fifth message indicating that the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, or that the first terminal device accesses the network based on narrowband high-orbit satellite access technology, at least one of the following: the first core network device is a communication device in the core network accessed by the first terminal device.

[0014] Based on this possible design, the first IMS network element can also learn from the calling side core network equipment that the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on the narrowband high-orbit satellite access technology. This provides a possible implementation method for the first IMS network element to determine the first terminal device's ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on the narrowband high-orbit satellite access technology.

[0015] In one possible design, the first message is also used to instruct the first terminal device to support the ability to perform calls based on narrowband high-orbit satellite access technology, or for the first terminal device to access a network based on narrowband high-orbit satellite access technology, at least one of the following:

[0016] Based on this possible design, an indication that the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, or that the first terminal device accesses the network based on narrowband high-orbit satellite access technology, can be carried in the first message and sent to the called side (such as the called side terminal device or the called side IMS network element), so that the called side can also know that the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, or that the first terminal device accesses the network based on narrowband high-orbit satellite access technology; thus providing a possible implementation method.

[0017] In one possible design, the method further includes: generating a sixth message, which confirms that the first IMS network element has received the first media response information; and sending the sixth message to the second device.

[0018] Based on this possible design, after receiving the second message, the first IMS network element can send a message (i.e., the sixth message, such as the PRACK message) to the called party (such as the called party terminal device or the called party IMS network element) to confirm that the first IMS network element has received the first media response information. Compared with the scheme where the calling party terminal device receives the first media response information and then sends a message, the first IMS network element can send a message in advance, thereby reducing call latency.

[0019] In one possible design, the method further includes: receiving a seventh message from a second device, the seventh message indicating that the second terminal device has rang; and generating a third message, including: generating the third message based on the seventh message.

[0020] Based on this possible design, after receiving a message from the called party indicating that the second terminal device has been ringing (i.e., the seventh message, such as a 180-ring message), the first IMS network element can generate and send a third message (such as a 180-ring message) to the calling party. That is, after exchanging INVITE messages, the first IMS network element and the calling party's terminal device do not need to exchange 183 session progress messages; they can directly exchange 180-ring messages, thereby reducing the number of signaling messages exchanged between the first IMS network element and the calling party's terminal device and reducing call latency. In one possible design, the third message also includes second media response information.

[0021] Based on this possible design, media response information can be carried in a third message (such as a 180-ring message), so that the first IMS network element and the calling terminal equipment no longer need to exchange 183 session progress messages, but can directly exchange 180-ring messages, thereby reducing the number of signaling messages exchanged between the first IMS network element and the calling terminal equipment, and thus reducing call latency.

[0022] In one possible design, the method further includes receiving an eighth message from the first device, the eighth message indicating that the first terminal device has received the second media response information and that the call resource reservation of the first terminal device has been successful.

[0023] Based on this possible design, the signaling message indicating that the first terminal device has received the second media response information and that the first terminal device has successfully reserved call resources can be transmitted in one signaling message (i.e., the eighth message) to reduce the number of signaling messages exchanged between the first IMS network element and the calling terminal device, thereby reducing call latency.

[0024] In one possible design, the method further includes sending a ninth message to a second device, the ninth message indicating that the call resources of the first terminal device have been successfully reserved.

[0025] In one possible design, sending a ninth message to the second device includes: receiving an eighth message from the first device, the eighth message indicating that the first terminal device has received the second media response information and that the call resource reservation of the first terminal device has been successful; and sending a ninth message based on the eighth message, the eighth message originating from the first device and indicating that the first device has received the second media response information and that the call resource reservation of the first terminal device has been successful, and the ninth message indicating that the call resource reservation of the first terminal device has been successful.

[0026] Based on this possible design, the first IMS network element can send a notification of successful call resource reservation for the first terminal device to the called party (i.e., the ninth message) only after learning that the call resource reservation for the first terminal device has been successful, thus ensuring the authenticity of the message. This improves the security of the ringing of the called party's terminal device.

[0027] In one possible design, the method further includes: sending a tenth message to a first device, the tenth message being used to instruct a second terminal device to respond to a call request from the first terminal device, the tenth message also including second media response information.

[0028] Based on this possible design, media response information can be carried in a message (such as an INVITE 200 OK message) that instructs the second terminal device to respond to the call request of the first terminal device. This eliminates the need for the first IMS network element and the calling terminal device to exchange 183 session progress messages, thereby reducing the number of signaling messages exchanged between the first IMS network element and the calling terminal device and reducing call latency.

[0029] Secondly, embodiments of this application provide a calling method, which can be executed by a first IMS network element. Unless otherwise specified, the "first IMS network element" in this application can be the first IMS network element itself, a component applicable to the first IMS network element (e.g., a communication module, processor, circuit, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the first IMS network element. The method includes: sending a first message to a second device, the first message being used by a first terminal device to call the second terminal device, the first message including media request information; receiving a second message from the second device, the second message indicating that the second terminal device has rang, the second message also including first media response information; determining that the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology; generating a third message, the third message indicating that a session is in progress, the third message also including second media response information; and sending the third message to the first device.

[0030] Wherein, the first IMS network element is a network element in the IMS network accessed by the first terminal device, and correspondingly, the second device is a network element in the IMS network accessed by the second terminal device, and the first device is the first terminal device; or, the first IMS network element is a network element in the IMS network accessed by the second terminal device, and correspondingly, the second device is the second terminal device, and the first device is a network element in the IMS network accessed by the first terminal device.

[0031] Based on the second aspect, during the process of the calling terminal device (i.e., the first terminal device) calling the called terminal device (the second terminal device) (i.e., from the transmission of INVITE messages (such as the first message, which is used by the calling terminal device to call the called terminal device and includes media request information) between the calling and called parties), the IMS network element of the calling / called party (i.e., the first IMS network element) can receive information from its upstream node (i.e., the second device); wherein, the first IMS network element is a network element in the IMS network accessed by the calling terminal device, and correspondingly, the second device is a network element in the IMS network accessed by the called terminal device; the first IMS network element is a network element in the IMS network accessed by the second terminal device. The IMS network element (correspondingly, the second device is the called-side terminal device) sends a 180-ring message (such as the second message, which indicates that the second terminal device has been ringing, and the second message also includes first media response information); furthermore, the calling / called-side IMS network element can obtain whether the calling-side terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether the calling-side terminal device accesses the network based on narrowband high-orbit satellite access technology, and if the calling-side terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or if the calling-side terminal device accesses the network based on non-narrowband high-orbit satellite access technology, it generates a 183-session progress message; and sends the 183-session progress message to its next node (i.e., the first device; wherein, the first IMS network element is a network element in the IMS network accessed by the first terminal device, and correspondingly, the first device is the calling-side terminal device; the first IMS network element is a network element in the IMS network accessed by the called-side terminal device, and correspondingly, the first device is a network element in the IMS network accessed by the calling-side terminal device).

[0032] In other words, after receiving the INVITE message from the calling terminal, the called terminal can directly send a 180ring message back to the IMS network element on the calling / called side. The 180ring message carries media response information (i.e., the first media response information). This means that the IMS network element on the calling / called side and the called terminal do not need to transmit messages such as 183 session progress, PRACK, and UPDATA, thereby reducing the number of signaling messages exchanged in the call setup process, reducing call latency, and improving user experience.

[0033] Furthermore, after receiving the 180ring message from its upstream node, the calling / called IMS network element can determine whether it can transmit the 180ring message to the next node by judging whether the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether the calling terminal device accesses the network based on narrowband high-orbit satellite access technology. If the calling terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or the calling terminal device accesses the network based on non-narrowband high-orbit satellite access technology, it indicates that the calling side does not support the simplified call setup process. Therefore, the existing call setup process needs to be used between the calling / called IMS network element and the calling terminal device. That is, the calling / called IMS network element can generate a 183 session progress message and feed it back to its next node. This provides different optional application scenarios for the implementation of the call setup process between the calling and called terminal devices (i.e., the calling side uses the existing call setup process, and the called side uses the simplified call setup process).

[0034] In one possible design, determining that the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology, includes: receiving a fourth message from the first device, the fourth message instructing the first terminal device to call a second terminal device, and instructing the first terminal device to support at least one of the following: the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology, wherein the fourth message includes media request information.

[0035] In one possible design, the supported header field in the fourth message does not include information indicating the first terminal device's ability to perform calls based on narrowband high-orbit satellite access technology; and / or, the private access network information (P-ANI) header field in the fourth message is used to indicate that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology.

[0036] In one possible design, the first IMS network element is a network element in the IMS network accessed by the first terminal device. Determining that the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology, includes: receiving a fifth message from a first core network device, the fifth message indicating that the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology, at least one of these conditions. The first core network device is a communication device in the core network accessed by the first terminal device.

[0037] In one possible design, the first message is also used to indicate that the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology, at least one of these.

[0038] In one possible design, the method further includes: receiving a sixth message from a first device, the sixth message indicating that the first terminal device has received the second media response information; receiving a seventh message from the first device, the seventh message indicating that the call resource reservation of the first terminal device has been successful; and sending an eighth message to the second device based on the sixth and seventh messages, the eighth message indicating confirmation that the first terminal device has received the second media response information and indicating that the call resource reservation of the first terminal device has been successful.

[0039] Based on this possible design, the first IMS network element can send a notification of successful call resource reservation for the first terminal device to the called party (i.e., the ninth message) only after learning that the call resource reservation for the first terminal device has been successful, thus ensuring the authenticity of the message. This improves the security of the ringing of the called party's terminal device.

[0040] In addition, the signaling message indicating that the first terminal device has received the second media response information and that the first terminal device has successfully reserved call resources can be transmitted in one signaling message (i.e., the eighth message) to reduce the number of signaling messages exchanged between the first IMS network element and the called terminal device, thereby reducing call latency.

[0041] In one possible design, the method further includes: receiving a seventh message from a first device, the seventh message indicating that the call resource reservation for the first terminal device has been successful; after receiving the seventh message from the first device and the second message from the second device, the method further includes: sending a ninth message to the first device, the ninth message indicating that the second terminal device has rang.

[0042] Based on this possible design, the first IMS network element can send a notification of successful call resource reservation for the first terminal device to the called party (i.e., the ninth message) only after learning that the call resource reservation for the first terminal device has been successful, thus ensuring the authenticity of the message. This improves the security of the ringing of the called party's terminal device.

[0043] The technical effects of any design in the second aspect can be referenced from the technical effects of the corresponding design in the first aspect, and will not be elaborated here.

[0044] Thirdly, embodiments of this application provide a calling method, which can be executed by a first IMS network element. Unless otherwise specified, the "first IMS network element" in this application can be the first IMS network element itself, a component applicable to the first IMS network element (e.g., a communication module, processor, circuit, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the first IMS network element. The method includes: sending a first message to a second device, the first message being used by a first terminal device to call the second terminal device, the first message including media request information; receiving a second message from the second device, the second message indicating that the second terminal device has been ringing; determining that the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on narrowband high-orbit satellite access technology; generating a third message, the third message indicating that the second terminal device has been ringing; and sending the third message to the first device. Wherein, the first IMS network element is a network element in the IMS network accessed by the first terminal device, and correspondingly, the second device is a network element in the IMS network accessed by the second terminal device, and the first device is the first terminal device; or, the first IMS network element is a network element in the IMS network accessed by the second terminal device, and correspondingly, the second device is the second terminal device, and the first device is a network element in the IMS network accessed by the first terminal device.

[0045] Based on the third aspect, during the process of the calling terminal device (i.e., the first terminal device) calling the called terminal device (the second terminal device) (i.e., from the transmission of INVITE messages (such as the first message, which is used by the calling terminal device to call the called terminal device and includes media request information) between the calling and called parties), the IMS network element of the calling / called party (i.e., the first IMS network element) can receive 180ring messages (such as the second message, which is used by the called party terminal device to call the called terminal device and includes media request information) from its upstream node (i.e., the second device; wherein, the first IMS network element is a network element in the IMS network accessed by the calling terminal device, and correspondingly, the second device is a network element in the IMS network accessed by the called terminal device; the first IMS network element is a network element in the IMS network accessed by the second terminal device, and correspondingly, the second device is the called terminal device) from the upstream node (i.e., the second device). Further, the calling / called party terminal device can receive 180ring messages (such as the second message, which is used by the called party terminal device to call the called terminal device) from the upstream node (i.e., the second device). The calling / called side IMS network element can obtain whether the calling side terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether the calling side terminal device accesses the network based on narrowband high-orbit satellite access technology. If the calling side terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or the calling side terminal device accesses the network based on narrowband high-orbit satellite access technology, it continues to the next node (i.e., the first device); where the first IMS network element is the network element in the IMS network accessed by the first terminal device, and correspondingly, the first device is the calling side terminal device; the first IMS network element is the network element in the IMS network accessed by the called side terminal device, and correspondingly, the first device sends a 180-ring message (such as the third message, the third message being used to indicate that the called side terminal device has rang) to the network element in the IMS network accessed by the calling side terminal device.

[0046] In other words, after receiving a 180ring message from its upstream node, the IMS network element on the calling / called side can determine whether to continue sending a 180ring message to the next node by judging whether the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether the calling terminal device accesses the network based on narrowband high-orbit satellite access technology. Specifically, if the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether the calling terminal device accesses the network based on narrowband high-orbit satellite access technology, then the IMS network element on both the calling and called sides can continue sending a 180ring message to the next node. At this point, the calling and called terminal devices interact using 180ring messages instead of 183 session progress messages. This eliminates the need for the calling and called terminal devices to transmit 183 session progress, PRACK, and UPDATA messages. In other words, the calling and called terminal devices no longer need to sequentially transmit INVITE, 183 session progress, PRACK, UPDATA, and 180ring messages to complete the call setup process. Instead, the 180ring message is transmitted directly after the INVITE message. Therefore, during the call setup process, the calling and called terminal devices only need to complete signaling interactions such as INVITE and 180ring messages. This reduces the number of signaling messages exchanged during the call setup process, thereby reducing call latency and improving user experience.

[0047] In one possible design, determining that the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology, includes: receiving a fourth message from the first device, the fourth message instructing the first terminal device to call a second terminal device, and instructing the first terminal device to support at least one of the following: the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology, wherein the fourth message includes media request information.

[0048] In one possible design, the supported header field in the fourth message does not include information indicating the first terminal device's ability to perform calls based on narrowband high-orbit satellite access technology; and / or, the private access network information (P-ANI) header field in the fourth message is used to indicate that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology.

[0049] In one possible design, the first IMS network element is a network element in the IMS network accessed by the first terminal device. Determining that the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology, includes: receiving a fifth message from a first core network device, the fifth message indicating that the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology, at least one of these conditions. The first core network device is a communication device in the core network accessed by the first terminal device.

[0050] In one possible design, the second message includes the first media response information.

[0051] Based on this possible design, the second message can carry media response information, thus eliminating the need to send a separate signaling instruction for media response information; thereby saving the number of signaling messages in the call setup process and reducing call latency.

[0052] In one possible design, the third message includes a second media response message, which is related to the first media response message.

[0053] In one possible design, the method further includes: receiving a sixth message from a first device, the sixth message being used to confirm that the first terminal device has received the second media response information and that the call resource reservation of the first terminal device has been successful; and sending a seventh message to the second device based on the sixth message, the seventh message being used to confirm that the first terminal device has received the second media response information and that the call resource reservation of the first terminal device has been successful.

[0054] The technical effects of any design in the third aspect can be referenced from the technical effects of the corresponding design in the first aspect, and will not be elaborated here.

[0055] Fourthly, embodiments of this application provide a calling method, which can be executed by a first terminal device. Unless otherwise specified, the "first terminal device" in this application can be the first terminal device itself, a component applicable to the first terminal device (e.g., a communication module, processor, circuit, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the first terminal device. The method includes: sending a fourth message, which is used by the first terminal device to call a second terminal device, and indicating whether the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or indicating whether the first terminal device accesses a network based on narrowband high-orbit satellite access technology; and receiving an eleventh message, which is used to indicate that the second terminal device has rang.

[0056] Based on the fourth aspect, the calling terminal equipment can carry at least one of the following in a message (i.e., the fourth message, such as the INVITE message) instructing the first terminal equipment to call the second terminal equipment and including media request information: whether it supports the ability to perform calls based on narrowband high-orbit satellite access technology and / or whether it accesses the network based on narrowband high-orbit satellite access technology. In other words, during the call process establishment, there is no need to configure new signaling; instead, this indication is carried in the existing signaling to save signaling overhead and facilitate implementation.

[0057] Furthermore, the calling terminal device can inform the first IMS network element of this indication, enabling the first IMS network element to respond accordingly. For example, if the first IMS network element determines that the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or the calling terminal device accesses the network based on narrowband high-orbit satellite access technology, it can convert the 183 session progress message received from the called party into a 180 ring message and send it to the calling terminal device. This reduces the number of signaling messages exchanged between the first IMS network element and the calling terminal device, thereby reducing call latency. In one possible design, at least one of the first terminal device or the second terminal device is based on a narrowband high-orbit satellite access network; and / or both the first terminal device and the second terminal device support the ability to perform calls based on narrowband high-orbit satellite access technology.

[0058] Based on this possible design, the scheme for the first IMS network element to perform signaling conversion can also be implemented in scenarios where at least one of the calling or called terminal devices is based on a narrowband high-orbit satellite access network; and / or, both the calling and called terminal devices support the ability to perform calls based on narrowband high-orbit satellite access technology, thereby enabling the scheme to be applied to different scenarios.

[0059] In one possible design, the eleventh message also includes a second media response message.

[0060] In one possible design, after receiving the eleventh message, the method further includes sending a sixth message, which confirms that the first terminal device has received the second media response information, the instruction, and that the first terminal device has successfully reserved call resources.

[0061] In one possible design, after receiving the eleventh message, the method further includes: receiving a tenth message, which instructs the second terminal device to respond to the call request of the first terminal device, and the tenth message also includes second media response information.

[0062] In one possible design, the supported header field in the fourth message is used to indicate whether the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology; and / or, the private access network information (P-ANI) header field in the fourth message indicates whether the first terminal device accesses the network based on narrowband high-orbit satellite access technology.

[0063] The technical effects of any design in the fourth aspect can be referenced from the technical effects of the corresponding design in the first aspect mentioned above, and will not be elaborated further here.

[0064] Fifthly, embodiments of this application provide a calling method, which can be executed by a second terminal device. Unless otherwise specified, the "first terminal device" in this application can be the first terminal device itself, a component applicable to the first terminal device (e.g., a communication module, processor, circuit, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the first terminal device. The method includes: receiving a first message, the first message being used by the first terminal device to request a call to the second terminal device, the first message including media request information; determining that at least one of the first terminal device or the second terminal device is based on a narrowband high-orbit satellite access network; generating a second message, the second message being used to instruct the second terminal device to ring; and sending the second message.

[0065] Based on the fifth aspect, after receiving the INVITE message (such as the first message), the called-side terminal device can determine the message it should send back by determining that at least one of the calling-side terminal device or the called-side terminal device is connected to a network. If it is determined that at least one of the calling-side terminal device or the called-side terminal device is connected to a narrowband high-orbit satellite network, it can send back a 180-ring message (i.e., the second message). That is, the calling and called sides no longer need to exchange 183-session progress messages, thereby reducing the number of signaling messages exchanged between the calling and called sides and reducing call latency.

[0066] In one possible design, both the first terminal device and the second terminal device support the ability to perform calls based on narrowband high-orbit satellite access technology.

[0067] In one possible design, the second message also includes the first media response information.

[0068] In one possible design, after sending the second message, the method further includes sending a twelfth message, which indicates the first media response information and the second terminal device responding to the call request of the first terminal device.

[0069] In one possible design, the method further includes receiving a thirteenth message, which is used to confirm that the first terminal device has received the media response information and to indicate that the call resource reservation of the first terminal device has been successful.

[0070] In one possible design, the first message is also used to indicate whether the first terminal device accesses the network based on narrowband high-orbit satellite access technology.

[0071] In one possible design, the supported header field in the first message is used to indicate whether the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology.

[0072] In one possible design, the first message is also used to indicate whether the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology.

[0073] In one possible design, the P-ANI header field in the first message indicates whether the first terminal device accesses the network based on narrowband high-orbit satellite access technology.

[0074] The technical effects of any design in the fifth aspect can be referenced from the technical effects of the corresponding design in the first aspect mentioned above, and will not be elaborated further here.

[0075] Sixthly, a communication device is provided for implementing various methods. This communication device can be a first IMS network element as described in the first, second, or third aspect, a first terminal device as described in the fourth aspect, or a second terminal device as described in the fifth aspect, such as a device, chip, or chip system. The communication device includes modules, units, or means corresponding to the implementation of the methods, which can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions.

[0076] In some possible designs, the communication device may include a processing module and a transceiver module. The processing module can be used to implement the processing functions in any of the above aspects and any possible implementations thereof. The transceiver module may include a receiving module and a transmitting module, respectively used to implement the receiving function and the transmitting function in any of the above aspects and any possible implementations thereof.

[0077] In some possible designs, the transceiver module can consist of transceiver circuitry, a transceiver unit, a transceiver interface, or a communication interface.

[0078] A seventh aspect provides a communication device, comprising: a processor and a memory; the memory is used to store computer instructions, which, when executed by the processor, cause the communication device to perform the method described in any aspect. The communication device may be a first IMS network element of the first, second, or third aspect, a first terminal device of the fourth aspect, or a second terminal device of the fifth aspect, such as a device, chip, or chip system. The communication device includes modules, units, or means corresponding to the implementation of the method, which may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the function.

[0079] Eighthly, a communication device is provided, comprising: a processor and a communication interface; the communication interface being used to communicate with a module outside the communication device; the processor being used to execute computer programs or instructions to cause the communication device to perform the method described in any of the aspects. The communication device may be a first IMS network element in the first, second, or third aspect, or a first terminal device in the fourth aspect, or a second terminal device in the fifth aspect, such as a device, chip, or chip system. The communication device includes modules, units, or means corresponding to the implementation method, which may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the function.

[0080] A ninth aspect provides a communication device, comprising: at least one processor; the processor being configured to execute a computer program or instructions to cause the communication device to perform the method described in any of the aspects. The communication device may be a first IMS network element of the first, second, or third aspect, or a first terminal device of the fourth aspect, or a second terminal device of the fifth aspect, such as a device, chip, or chip system. The communication device includes modules, units, or means corresponding to the implementation of the method, which may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions.

[0081] In some possible designs, the communication device includes a memory for storing at least one of necessary programs, instructions, or data. The memory may be coupled to the processor, or it may be independent of the processor.

[0082] In some possible designs, when the device is a chip system, it can be composed of chips or contain chips and other discrete components.

[0083] It is understandable that when the communication device provided in any of the sixth to ninth aspects is a chip, the sending action / function of the communication device can be understood as outputting information, and the receiving action / function of the communication device can be understood as inputting information.

[0084] The aforementioned first terminal device and / or second terminal device may be a terminal device, or a communication module in a terminal device, or a chip in a terminal device that is responsible for communication functions, such as a modem chip (also known as a baseband chip), or a system-on-chip (SoC) chip or system-in-a-package (SIP) chip that includes a modem module.

[0085] And / or, the aforementioned first IMS network element may be an IMS network element, or a communication module in an IMS network element, or a circuit or chip in an IMS network element responsible for communication functions, or a functional module in a network device capable of calling and executing programs.

[0086] In a tenth aspect, a computer-readable storage medium is provided that stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform the method described in any aspect.

[0087] In an eleventh aspect, a computer program product containing instructions is provided, which, when run on a communication device, enables the communication device to perform the method described in any one aspect.

[0088] In a twelfth aspect, a communication system is provided, comprising a first IMS network element (e.g., an IMS network element, a chip or chip system applied to the IMS network element) as described in the first, second, or third aspects; a first terminal device (e.g., a terminal device, a chip or chip system applied to the terminal device) as described in the fourth aspect; and a second terminal device (e.g., a terminal device, a chip or chip system applied to the terminal device) as described in the fifth aspect. The technical effects of any design method in aspects six through twelfth are similar to those of the different design methods described in aspects one through five above, and will not be repeated here. Attached Figure Description

[0089] Figures 1 and 2 are schematic diagrams of the network architecture provided in the embodiments of this application;

[0090] Figure 3 is a schematic diagram of a call flow provided in an embodiment of this application;

[0091] Figures 4 to 23 are schematic flowcharts of the calling method provided in the embodiments of this application;

[0092] Figure 24 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0093] Figure 25 is a schematic diagram of another communication device provided in an embodiment of this application;

[0094] Figure 26 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0095] To facilitate understanding of the technical solutions of the embodiments of this application, a brief introduction to the relevant technologies of this application is given below.

[0096] 1. Non-terrestrial networks (NTN):

[0097] Fifth-generation (5G) new radio (NR) technology is evolving from release 18 (Rle18 / R18) to R19. Simultaneously, NR technology has moved from the standardization phase to commercial deployment. The initial research on the NR standard protocol was for wireless communication technologies designed for terrestrial cellular network scenarios, capable of providing users with low latency, ultra-reliability, ultra-high speed, and massive connectivity wireless communication services. However, cellular networks cannot achieve seamless global coverage. For example, in areas without terrestrial base stations, such as ocean areas, polar regions, and rainforests, voice and data services cannot be provided to areas covered by cellular networks.

[0098] Compared to terrestrial communications, NTN communications offer significant advantages such as global coverage, long-distance transmission, flexible networking, convenient deployment, and freedom from geographical limitations. It has been widely applied in various fields including maritime communications, positioning and navigation, disaster relief, scientific experiments, video broadcasting, and Earth observation. NTN networks can be integrated with terrestrial networks, leveraging their respective strengths to create a seamless, globally integrated sea, land, air, space, and ground communications network, meeting the diverse and ubiquitous service needs of users.

[0099] Depending on the altitude of the flight platform above the ground, the NTN can include a low altitude platform (LAP) subnetwork, a high altitude platform (HAP) subnetwork, and a satellite communication subnetwork.

[0100] For example, in a LAP subnetwork, base stations or base station functions are deployed on low-altitude flight platforms (e.g., drones) at an altitude of 0.1km to 1km above the ground to provide coverage for terminals; in a HAP subnetwork, base stations or base station functions are deployed on high-altitude flight platforms (e.g., aircraft) at an altitude of 8km to 50km above the ground to provide coverage for terminals; and in a SATCOM subnetwork, base stations or base station functions are deployed on satellites at an altitude of more than 50km above the ground to provide coverage for terminals. Satellite communication has significant advantages such as global coverage, long-distance transmission, flexible networking, convenient deployment, and no geographical limitations, and has been widely used in various fields such as maritime communication, positioning and navigation, disaster relief, scientific experiments, video broadcasting, and Earth observation. Furthermore, satellites in satellite communication systems typically transmit information via inter-satellite links (ISL) or satellite-to-ground links.

[0101] Furthermore, based on the satellite's orbital altitude, satellite communication systems can be divided into geostationary earth orbit (GEO) satellite communication systems, medium earth orbit (MEO) satellite communication systems, and low-earth orbit (LEO) satellite communication systems.

[0102] GEO satellite communication systems, also known as geostationary orbit satellite systems or high Earth orbit satellite communication systems (abbreviated as GEO satellite communication systems), operate at an altitude of 35,786 km. Their orbital speed is the same as the Earth's rotation speed, meaning GEO satellites can remain stationary relative to the ground. GEO satellite communication systems can provide large cell coverage, typically with a cell diameter of 500 km. MEO satellites operate at altitudes between 2,000 and 35,786 km, achieving global coverage with a relatively small number of satellites. LEO satellites operate at altitudes between 300 and 2,000 km, lower than MEO satellites. They offer advantages such as low transmission latency, low transmission loss, and relatively low launch costs.

[0103] 2. Internet Protocol (IP) Multimedia Subsystem (IMS):

[0104] IMS is the collective term for the logical functional entities of the network core layer that control IP multimedia services. The IMS network is built on the operator's network using IP technology and can provide a wealth of telecom-grade multimedia services such as high-definition audio / video calls, video ringback tones, and teleconferencing.

[0105] The core functional entity of the IMS network is the Call Session Control Function (CSCF). It is primarily responsible for handling signaling control during multimedia call sessions and forming the Session Initialization Protocol (SIP) routing system. The CSCF includes the Proxy-Call Session Control Function (P-CSCF) and the Service-Call Session Control Function (S-CSCF) network elements. The P-CSCF is the first network element encountered by the user in the IMS system; all SIP signaling traffic from the user must be sent to the P-CSCF. Correspondingly, all terminating SIP signaling traffic from the network must be sent from the P-CSCF to the user equipment (UE). The S-CSCF is the core of the IMS system, providing session control services to the UE and maintaining session state according to the operator's needs to support services.

[0106] Therefore, as shown in Figure 1(a), for two UEs (i.e., UE#1 and UE#2) with a call requirement (such as a voice call or a video call), the transmission path of SIP signaling (such as signaling #1) from UE#1 to UE#2 is: UE#1 → Access Network Device #1 → Core Network Device #1 → P-CSCF Network Element #1 → S-CSCF Network Element #1 → S-CSCF Network Element #2 → P-CSCF Network Element #2 → Core Network Device #2 → Access Network Device #2 → UE#2. Correspondingly, the transmission path of SIP signaling (such as signaling #2) from UE#2 to UE#1 is: UE#2 → Access Network Device #2 → Core Network Device #2 → P-CSCF Network Element #2 → S-CSCF Network Element #2 → S-CSCF Network Element #1 → P-CSCF Network Element #1 → Core Network Device #1 → Access Network Device #1 → UE#1. Among them, UE#1, access network equipment #1, core network equipment #1, P-CSCF network element #1, and S-CSCF network element #1 are all calling side equipment; UE#2, access network equipment #2, core network equipment #2, P-CSCF network element #2, and S-CSCF network element #2 are all called side equipment.

[0107] Optionally, all network elements in the IMS network can be referred to as IMS network elements; for example, P-CSCF network elements, S-CSCF network elements, etc., can all be referred to as IMS network elements. Alternatively, network elements in the IMS network can be collectively referred to as IMS network elements; for example, P-CSCF network elements and S-CSCF network elements can be collectively referred to as IMS network elements. Thus, as shown in Figure 1(b), the transmission path of SIP signaling (such as signaling #1) from UE#1 to UE#2 is: UE#1 → Access Network Device #1 → Core Network Device #1 → IMS Network Element #1 → IMS Network Element #2 → Core Network Device #2 → Access Network Device #2 → UE#2. Correspondingly, the transmission path of SIP signaling (such as signaling #2) from UE#2 to UE#1 is: UE#2 → Access Network Device #2 → Core Network Device #2 → IMS Network Element #2 → IMS Network Element #1 → Core Network Device #1 → Access Network Device #1 → UE#1. Among them, UE#1, access network equipment #1, core network equipment #1, and IMS network element #1 are all calling side equipment; UE#2, access network equipment #2, core network equipment #2, and IMS network element #2 are all called side equipment.

[0108] Taking the P-CSCF and S-CSCF network elements as a single IMS network element as an example, the calling party establishment process defined in the 3GPP standard can include four processes: call initiation-media negotiation, temporary message confirmation, resource reservation confirmation, and ringing connection. Specifically, as shown in Figure 2, during the call initiation-media negotiation process, the calling UE (i.e., UE#1) can send an INVITE message to the called UE; the INVITE message is a call request initiated by the calling UE to the called UE; the INVITE message also carries media request information (i.e., a session description protocol (SDP) offer). For example, the INVITE message contains the number of the called UE (i.e., UE#2), the media types and encoding formats supported by the calling UE, etc. Correspondingly, after receiving the INVITE message, the called UE can send a 183 session progress message to the calling UE to indicate that the session is in progress. The 183 session progress message carries the called UE's media response (i.e., SDP answer) information. For example, the 183 session progress message includes the media types and encoding formats supported by the called UE.

[0109] In addition, during the call initiation-media negotiation process, after the calling side's IMS network element (i.e., IMS network element #1) receives the INVITE message, it can send a 100 Trying message to the calling side's UE to indicate that the calling side's IMS network element has received the INVITE message and is processing the INVITE message (such as sending it to the called side's IMS network element (i.e., IMS network element #2)).

[0110] Furthermore, after the calling side's IMS network element receives the 183 session progress message from the called side, it can send a message to the calling side's core network equipment (i.e., core network equipment #1) to trigger the core network equipment to establish the calling side UE's call bearer (or, the bearer used for the call). Thus, after the calling side UE's call bearer is established, the calling side's core network equipment can inform the calling side's IMS network element. In addition, the calling side's core network equipment can also inform the calling side UE that the calling side UE's call bearer has been established.

[0111] During the provisional message acknowledgment process, after receiving the 183 session progress message, the calling UE can send a provisional response acknowledgement (PRACK) message to the called UE to indicate that the calling UE has received the 183 session progress message. Correspondingly, after receiving the PRACK message, the called UE sends a PRACK 200 OK message to the calling UE to indicate that the called UE has received the PRACK message.

[0112] During the resource reservation confirmation process, after the calling UE learns that its call bearer establishment is complete (e.g., from the core network equipment on the calling side), it sends an update (UPDATA) message to the called UE to indicate that the call resource reservation for the calling UE is successful. Correspondingly, after receiving the UPDATA message and learning that its call bearer establishment is complete, the called UE can send an UPDATA 200 OK message to the calling UE to indicate that the call bearer establishment for the called UE is complete.

[0113] In this context, "call bearer establishment completed" signifies "call resource reservation successful"; that is to say, in this application, "call bearer establishment completed" and "call resource reservation successful" have the same meaning and can be used interchangeably.

[0114] During the ringing and connection process, after the called UE sends an UPDATA 200 OK message to the calling UE, the called UE rings and notifies the calling UE (i.e., sends a 180 ring message to the calling UE) to indicate that the called UE has rung. Further, the called UE answers and notifies the calling UE (i.e., sends an INVITE 200 OK message to the calling UE to indicate that the called UE has responded to the calling UE's call request, or in other words, to indicate that the called UE has answered). Upon receiving the INVITE 200 OK message, the calling UE can send an acknowledgment (ACK) message to the called UE. Thus, the calling UE can then communicate with the called UE.

[0115] In the call setup process shown in Figure 2 above, the time delay between the moment the calling UE sends the INVITE message and the moment it receives the 180ring message is called the call delay.

[0116] For example, the implementation of signaling interaction between the calling UE and the called UE in Figure 2 above can be found in the relevant description in Figure 1(b) above, and will not be repeated here.

[0117] With the widespread application of machine-type communication (MTC) and Internet of Things (IoT) communication in 5G NR, the number of IoT devices connected to the network is increasing, necessitating consideration of cost and power consumption requirements for IoT devices. Based on these cost and power consumption needs, narrowband IoT (NB-IoT) devices can be considered. NB-IoT devices can achieve power consumption down to the milliwatt (mW) level.

[0118] Especially in NTN scenarios, the use of narrow-band (NB) high-orbit satellites (or NB-IoT high-orbit satellites) to support voice services has become an industry trend. However, compared to terrestrial networks (TN), narrow-band high-orbit satellites have lower transmission rates, resulting in greater transmission latency. This leads to significant call delays during call setup (e.g., call delays greater than or equal to 80 seconds), degrading the user experience. Therefore, reducing call latency and improving user experience is a pressing issue that needs to be addressed.

[0119] Based on this, this application provides a calling method. During the process of a calling terminal device (i.e., the first terminal device) calling a called terminal device (the second terminal device) (i.e., from the transmission of INVITE messages (such as the first message, which is used by the calling terminal device to call the called terminal device and includes media request information) between the calling and called parties), the IMS network element (i.e., the first IMS network element) on the calling / called side can receive 183 sessions from its upstream node (i.e., the second device; wherein, the first IMS network element is a network element in the IMS network accessed by the calling terminal device (such as the calling P-CSCF), and correspondingly, the second device is a network element in the IMS network accessed by the called terminal device (such as the called P-CSCF); the first IMS network element is a network element in the IMS network accessed by the second terminal device (such as the called P-CSCF), and correspondingly, the second device is the called terminal device). The progress message (such as the second message, which indicates that the session is in progress, and also includes first media response information); furthermore, the IMS network element on the calling / called side can obtain whether the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether the calling terminal device accesses the network based on narrowband high-orbit satellite access technology, and if the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or if the calling terminal device accesses the network based on narrowband high-orbit satellite access technology, it generates a 180-ring message; and sends the 180-ring message to its next node (i.e., the first device; wherein, the first IMS network element is a network element in the IMS network accessed by the first terminal device (such as the calling side P-CSCF), and correspondingly, the first device is the calling side terminal device; the first IMS network element is a network element in the IMS network accessed by the called side terminal device (such as the called side P-CSCF), and correspondingly, the first device is a network element in the IMS network accessed by the calling side terminal device (such as the calling side P-CSCF).

[0120] In other words, after receiving a 183 session progress message from its upstream node, the IMS network element on the calling / called side can determine whether it can convert the 183 session progress message into a 180 ring message and send it to its next node by judging whether the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether the calling terminal device accesses the network based on narrowband high-orbit satellite access technology. Specifically, if the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether the calling terminal device accesses the network based on narrowband high-orbit satellite access technology, then the IMS network element on the calling / called side can directly convert the 183 session progress message into a 180 ring message and send it to its next node. At this point, the IMS network element on the calling / called side and the calling terminal device interact using a 180ring message instead of a 183 session progress message. Therefore, the IMS network element on the calling / called side and the calling terminal device no longer need to transmit 183 session progress, PRACK, and UPDATA messages. In other words, the IMS network element on the calling / called side and the calling terminal device do not need to sequentially transmit INVITE, 183 session progress, PRACK, UPDATA, and 180ring messages to complete the call setup process between the calling and called parties. Instead, the 180ring message is transmitted directly after the INVITE message. That is, in the call setup process, the IMS network element on the calling / called side and the calling terminal device only need to complete signaling interactions such as INVITE and 180ring messages. This reduces the number of signaling messages exchanged in the call setup process, thereby reducing call latency and improving user experience.

[0121] The technical solution provided in this application can be used in various communication systems, including high altitude platform station (HAPS) satellite communication systems, unmanned aerial vehicle (UAV) and other NTN systems, such as integrated communication and navigation (ICAN) systems, global navigation satellite systems (GNSS), and ultra-dense low-Earth orbit (LEO) satellite communication systems. Satellite communication systems can be integrated with traditional mobile communication systems. For example, the mobile communication system can be a 3GPP-related cellular system, such as the 4th generation (4G) long term evolution (LTE) system, the worldwide interoperability for microwave access (WiMAX) communication system, the evolved LTE system (LTE-Advanced, LTE-A) system, the 5G NR system, the vehicle to everything (V2X) system, the LTE and NR hybrid networking system, or the device-to-device (D2D) system, the machine-to-machine (M2M) communication system, the Internet of Things (IoT), and other future communication systems.

[0122] Alternatively, the communication system may be a non-3GPP communication system, such as an open radio access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a communication system that integrates multiple of the above communication systems. This application does not impose any restrictions.

[0123] The communication systems and scenarios applicable to this application mentioned above are merely illustrative examples. The communication systems and scenarios applicable to this application are not limited thereto. The communication systems and scenarios provided in this application do not impose any limitations on the solutions of this application. This is hereby stated uniformly and will not be repeated below.

[0124] This application provides an exemplary communication system. As shown in FIG3(a), the communication system may include at least one calling-side terminal device, at least one calling-side IMS network element, at least one called-side IMS network element, and at least one called-side terminal device.

[0125] During the signaling interaction between the calling terminal equipment and the called terminal equipment, the signaling can be sent from the calling terminal equipment to the calling IMS network element, then from the calling IMS network element to the called IMS network element, and finally from the called IMS network element to the called terminal equipment (i.e., the transmission path of the signaling is: calling terminal equipment → calling IMS network element → called IMS network element → called terminal equipment).

[0126] And / or, the signaling can be sent from the called-side terminal device to the called-side IMS network element, then from the called-side IMS network element to the calling-side IMS network element, and then from the calling-side IMS network element to the calling-side terminal device (i.e., the transmission path of the signaling is: called-side terminal device → called-side IMS network element → calling-side IMS network element → calling-side terminal device).

[0127] For example, in this application, the IMS network element can be composed of multiple network elements (such as P-CSCF network elements, S-CSCF network elements, etc.) in the IMS network element; or, it can be a P-CSCF network element in the IMS network element; this application does not limit this. Among them, the implementation of signaling interaction between the calling side IMS network element and the called side IMS network element under different implementations of the IMS network element can be referred to the relevant descriptions in (a) or (b) of Figure 1 above, and will not be repeated here.

[0128] Furthermore, during signaling interactions between the terminal device and IMS network elements (such as signaling interactions between the calling terminal device and the calling IMS network element, and / or, signaling interactions between the called terminal device and the called IMS network element), the terminal device can send signaling to its IMS network element through the IP-connectivity access network (IP-CAN). Here, IP-CAN is a collection of network entities and interfaces connecting the terminal device and the IMS network element. For example, IP-CAN can be an NB-IoT GEO network; that is, in this application, NB-IoT GEO can be used as IP-CAN.

[0129] Specifically, IP-CAN can include access network equipment and core network equipment. That is, the terminal device can sequentially send signaling to the IMS network element through the access network equipment and the core network equipment; the signaling transmission path is: terminal device → access network equipment → core network equipment → IMS network element. Correspondingly, the IMS network element can sequentially send signaling to the terminal device through the core network equipment and the access network equipment; the signaling transmission path is: IMS network element → core network equipment → access network equipment → terminal device. In this case, the communication system also includes the calling side access network equipment, the calling side core network equipment, the called side access network equipment, and the called side core network equipment. Among them, the core network equipment refers to the communication equipment (such as network elements and entities in the core network) within the core network to which the terminal device accesses.

[0130] When any communication device in the access network device and / or core network device receives signaling from its previous node (e.g., the previous node of the calling side access network device is the calling side terminal device, and the previous node of the calling side core network device is the calling side access network device), it may choose not to process the signaling and directly forward it to the next node; or it may modify or adjust the signaling and send the modified or adjusted signaling to the next node.

[0131] In addition, in NTN scenarios, the communication system also includes non-terrestrial platforms (such as low-altitude platforms (e.g., drones), high-altitude platforms (e.g., aircraft), or satellites; for ease of description, satellites will be used as an example below, and will not be elaborated further) and NTN gateways. Typically, NTN gateways are deployed on the ground. NTN gateways can communicate with satellites, and the link between the satellite and the NTN gateway can be called a feeder link.

[0132] Specifically, as shown in Figure 3(b), when the satellite acts as a wireless relay node, or in other words, when the satellite has relay forwarding capabilities, the NTN gateway has the functions of a base station or part of a base station. In this case, the NTN gateway can function as an access network device. Alternatively, the NTN gateway can be deployed separately from the access network device. Figure 3(b) illustrates this using the example of deploying the NTN gateway and access network device separately. In this case, the signaling sent by the terminal device can be transmitted sequentially through the satellite and the NTN gateway to the access network device (i.e., the signaling transmission path is: terminal device → satellite → NTN gateway → access network device); correspondingly, the signaling sent by the access network device can be transmitted sequentially through the NTN gateway and the satellite to the terminal device (i.e., the signaling transmission path is: access network device → NTN gateway → satellite → terminal device).

[0133] Furthermore, in the architecture shown in Figure 3(b), NG refers to the interface between the access network device and the core network device. Uu refers to the interface between the access network device and the terminal device. It is understood that as the communication system evolves, the interface names between the access network device and the core network device, and between the access network device and the terminal device, may also change, and this application does not specifically limit them.

[0134] It should be noted that in this application, during the transmission of a signaling message from the source address (i.e., the IP address of the first device to send the signaling message) to the destination address (i.e., the IP address of the last device to receive the signaling message), when the signaling message passes through an intermediate device, the intermediate device may forward the signaling message directly to the next node without making any modifications to it (i.e., pass-through forwarding); or, the intermediate device may modify or adjust the signaling message and transmit the modified or adjusted new signaling message to the next node.

[0135] For example, the terminal equipment shown in Figure 3(a) or (b) above can be a device or module that is connected to the above-mentioned communication system and has corresponding communication functions. Terminal equipment can also be called user equipment (UE), mobile station, mobile terminal, etc. Terminal equipment can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart cities, etc. Terminal equipment can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, transportation vehicles with wireless communication capabilities, communication modules, etc. The embodiments of this application do not limit the form of the terminal equipment. Terminal equipment typically contains communication modules, circuits, or chips that perform corresponding communication functions. The terminal device is also configured with program instructions for performing corresponding communication functions.

[0136] The access network device shown in Figure 3(b) above, sometimes also called a RAN entity or access node, is part of a communication system used to help terminal devices achieve wireless access. In one possible scenario, the access network device can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a WiFi system. The access network device can be a macro base station, a micro base station or an indoor station, a relay node or a donor node, or a radio controller in a CRAN scenario. Optionally, the access network device can also be a server, a wearable device, a vehicle, or an in-vehicle device. For example, the RAN node in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the access network device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The access network device may also include communication modules, circuits, or chips that perform corresponding communication functions. The access network device may also be configured with program instructions for performing corresponding communication functions, as well as corresponding program instructions. The access network device in this application may also be a logical node, logical module, or software capable of implementing all or part of the functions of an access network device.

[0137] In another possible scenario, multiple access network devices collaborate to assist terminal devices in achieving wireless access, with each access network device performing a portion of the base station's functions. For example, the access network devices can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. The CU and DU can be configured separately or included in the same network element, such as a baseband unit (BBU). The RU can be included in radio frequency equipment or radio frequency units, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0138] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0139] In some embodiments, the CU and DU can be divided according to the protocol layer of the wireless network: for example, the functions of the Packet Data Convergence Protocol (PDCP) layer and above (such as the Radio Resource Control (RRC) layer and the Service Data Adaptation Protocol (SDAP) layer) are set in the CU, and the functions of the protocol layers below the PDCP layer (such as the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, or the Physical (PHY) layer) are set in the DU; or, for example, the functions of the protocol layers above the PDCP layer are set in the CU, and the functions of the protocol layers below the PDCP layer are set in the DU, without restriction.

[0140] The above division of CU and DU processing functions according to protocol layers is merely an example; other methods can also be used. For instance, CUs or DUs can be divided into those with more protocol layer functions, or they can be divided into those with partial protocol layer processing functions. For example, some functions of the RLC layer and the protocol layer functions above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the protocol layer functions below the RLC layer can be placed in the DU. Furthermore, the functions of CUs or DUs can be divided according to service type or other system requirements, such as by latency. Functions that need to meet latency requirements can be placed in the DU, while functions that do not need to meet this latency requirement can be placed in the CU.

[0141] In some embodiments, the RU may be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0142] In some embodiments, when the RAN node is an access network device or a module of an access network device in an open ORAN system, in the ORAN system, CU can also be called open (O)-CU, DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0143] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU may also be called O-CU (open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU.

[0144] The following description, in conjunction with the communication system shown in Figure 3 and referring to Figure 4 below, further illustrates the calling method provided in this application, with the first IMS network element as the executing entity. Optionally, the method executed by the first IMS network element in this application can also be implemented by modules (e.g., circuits, chips, or chip systems) within the first IMS network element, or by logical nodes, logical modules, or software capable of implementing all or part of the functions of the first IMS network element. Alternatively, it can be implemented by at least one module in the communication or computing functions of the first IMS network element, or by circuits or chips (such as modem chips (also known as baseband chips), or system-on-chip (SoC) chips / system-in-a-package (SIP) chips containing modem cores, or graphics processing units (GPUs) / AI processors / application-specific integrated circuits (ASICs)) within the first IMS network element; this application does not impose any limitations.

[0145] Figure 4 is a flowchart illustrating a calling method provided in an embodiment of this application. As shown in Figure 4, the method may include the following steps:

[0146] S401, the first IMS network element sends a first message to the second device; correspondingly, the second device receives the first message from the first IMS network element. The first message is used for the calling terminal device (i.e., the first terminal device) to call the called terminal device (i.e., the second terminal device), and includes media request information.

[0147] For example, the first message can be an INVITE message.

[0148] Optionally, prior to step S401, as shown in Figure 5, the calling method may further include step S400:

[0149] S400, the first device sends a fourth message to the first IMS network element; correspondingly, the first IMS network element receives the fourth message from the first device. The fourth message is used by the calling terminal device to call the called terminal device and carries media request information.

[0150] For example, the fourth message could be an INVITE message.

[0151] Specifically, taking the example where both the first and fourth messages are INVITE messages, based on steps S400 to S401, it can be seen that the first device is the previous node of the INVITE message, and the second device is the next node of the INVITE message.

[0152] It is understandable that the transmission path of the INVITE message is: calling side terminal device → calling side IMS network element → called side IMS network element → called side terminal device. Therefore, if the first IMS network element is a network element in the IMS network accessed by the calling side terminal device (i.e., the calling side IMS network element, such as the calling side P-CSCF network element, or a combination of the calling side P-CSCF network element and the calling side S-CSCF network element), then the first device is the calling side terminal device, and the second device is the called side IMS network element (i.e., a network element in the IMS network accessed by the called side terminal device, such as the called side P-CSCF network element, or a combination of the called side P-CSCF network element and the called side S-CSCF network element); at this time, steps S400 to S401 can be as shown in Figure 6(a). If the first IMS network element is a network element in the IMS network accessed by the called-side terminal device (i.e., the called-side IMS network element), then the first device is the calling-side IMS network element and the second device is the called-side terminal device; at this time, steps S400 to S401 can be as shown in Figure 6(b).

[0153] Specifically, when the first device is the calling terminal device, the first IMS network element is the calling IMS network element, and the second device is the called IMS network element, the second device also needs to send a message to the called terminal device containing media request information, which is used by the calling terminal device (i.e., the first terminal device) to call the called terminal device (i.e., the second terminal device). For example, the second device can forward the first message to the called terminal device; or, the second device can send message #1 to the called terminal device, where message #1 is used by the calling terminal device to call the called terminal device and includes media request information; for example, message #1 is an INVITE message.

[0154] When the first device is the calling side IMS network element, and the second device is the called side terminal device, and the first IMS network element is the called side IMS network element, before sending the fourth message, the calling side terminal device also needs to send a message (such as message #2) to the first device to instruct the calling side terminal device to call the called side terminal device and to carry media request information. For example, the calling side terminal device sends message #2 to the first device, enabling the first device to execute step S400. For example, message #2 is an INVITE message.

[0155] Optionally, when the IMS network element (such as the calling side IMS network element or the called side IMS network element) is a P-CSCF network element, for the calling side IMS network element, the next node of the first message is actually the calling side S-CSCF network element. However, in the signaling interaction process described in the call method of this application, the function of the S-CSCF network element is mainly to forward the messages it receives (such as transparent forwarding or regeneration forwarding). Therefore, the description of this network element is omitted in this application, and it is used as an implementation of signaling interaction between the calling side P-CSCF network element and the called side P-CSCF network element.

[0156] Therefore, in this application, when the first IMS network element is the calling side P-CSCF network element, the second device can be considered as the called side P-CSCF network element. In this case, the first message between the first IMS network element and the second device needs to be sent to the calling side S-CSCF network element first, then to the called side S-CSCF network element, and then to the second device; that is, the transmission path of the first message is: first IMS network element (calling side P-CSCF network element) → calling side S-CSCF network element → called side S-CSCF network element → second device (called side P-CSCF network element). When the first IMS network element is the called side P-CSCF network element, the second device can be considered as the called side terminal device.

[0157] Furthermore, the implementation of the called-side IMS network element sending the first message to the called-side terminal device can be found in the description of the signaling interaction between the called-side IMS network element and the called-side terminal device in the foregoing embodiments, and will not be repeated here. For ease of description, the following embodiments use the example of an IMS network element composed of multiple network elements in the IMS network (such as P-CSCF network elements, S-CSCF network elements, etc.) to introduce the implementation of the call method described in this application; the implementation of the IMS network element as a P-CSCF network element is similar to the implementation of the IMS network element in the following embodiments, and can be found in the relevant descriptions in the following embodiments, and will not be repeated here.

[0158] S402, the second device sends a second message to the first IMS network element; correspondingly, the first IMS network element receives the second message from the second device. The second message indicates that a session is in progress, and also includes first media response information.

[0159] For example, the second message can be a 183 session progress message. It is understood that the transmission path of the 183 session progress message is typically: called-side terminal device → called-side IMS network element → calling-side IMS network element → calling-side terminal device. Therefore, if the first IMS network element is the called-side IMS network element, then the calling-side IMS network element receives the second message from the called-side terminal device, meaning the second device is the called-side terminal device; in this case, step S402 can be as shown in Figure 6(a). If the first IMS network element is the calling-side IMS network element, then the calling-side IMS network element receives the second message from the called-side IMS network element, meaning the second device is the called-side IMS network element. In this case, step S402 can be as shown in Figure 6(b).

[0160] In one implementation, after receiving an INVITE message (such as the first message or message #1), the called-side terminal device can directly generate and send a second message back to the first IMS network element. In another implementation, the called-side terminal device can determine its feedback message by determining at least one of the following: whether it supports the ability to perform calls based on narrowband high-orbit satellite access technology, or whether it accesses the network based on narrowband high-orbit satellite access technology. Specifically, if the called-side terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or accesses the network based on a non-narrowband high-orbit satellite access technology, it indicates that the called-side terminal device cannot process the signaling in the simplified procedure; therefore, a standard procedure (as shown in Figure 2) needs to be executed between the first IMS network element and the called-side terminal device. Therefore, after receiving the INVITE message, the called-side terminal device can send a 183 session progress message (such as generating and sending a second message back to the first IMS network element).

[0161] Specifically, whether the terminal device supports the ability to make calls based on narrowband high-orbit satellite access technology, and / or whether it accesses the network based on narrowband high-orbit satellite access technology, can be found in the relevant steps S403 below, which will not be described again here.

[0162] As an example, when the second device is the called-side terminal device, the first media response information is generated by the called-side terminal device. For example, the first media response information can be the media information of the called-side terminal device (such as the media types and encoding formats supported by the called-side terminal device); or, the first media response information can be the intersection between the media information of the called-side terminal device and the media information of the calling-side terminal device indicated by the media request information; or, the first media response information is determined based on the intersection between the media information of the called-side terminal device and the media information of the calling-side terminal device indicated by the media request information (such as the first media response information being a portion of the media information in the intersection, such as the media types and encoding formats supported by both the called-side terminal device and the calling-side terminal device).

[0163] As another example, when the second device is the called side IMS network element, the first media response information can be generated by the called side terminal device or the called side IMS network element.

[0164] When the first media response information is generated by the called-side terminal device, it means that after receiving the message carrying the first media response information (such as the 183 session progress message) from the called-side terminal device, the called-side IMS network element does not adjust or modify the first media response information, but directly sends the first media response information to the calling-side IMS network element; that is, the first media response information is sent through the second message.

[0165] When the first media response information is generated by the called-side IMS network element, it means that after receiving a message (such as a 183 session progress message) from the called-side terminal device carrying media response information #1 (generated by the called-side terminal device), the called-side IMS network element adjusts or modifies the media response information to obtain the first media response information and sends it to the calling-side IMS network element; that is, the first media response information is sent through the second message. For example, media response information #1 can be the media information of the called-side terminal device (such as the media types and encoding formats supported by the called-side terminal device); correspondingly, the first media response information can be the intersection between the media information of the called-side terminal device and the media information of the calling-side terminal device indicated by the media request information, or the first media response information can be determined based on the intersection between the media information of the called-side terminal device and the media information of the calling-side terminal device indicated by the media request information (such as the first media response information being a part of the media information in the intersection, such as the media types and encoding formats supported by both the called-side and calling-side terminal devices).

[0166] S403, The first IMS network element determines that the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the calling terminal device accesses the network based on narrowband high-orbit satellite access technology.

[0167] For example, if a terminal device does not support the ability to make calls using narrowband high-orbit satellite access technology, it accesses the network using a non-narrowband high-orbit satellite access technology. If a terminal device supports the ability to make calls using narrowband high-orbit satellite access technology, it can access the network using either a non-narrowband high-orbit satellite access technology or narrowband high-orbit satellite access technology. However, if a terminal device does not support the ability to make calls using narrowband high-orbit satellite access technology, it must access the network using a non-narrowband high-orbit satellite access technology when initiating a call; otherwise, the call cannot be established. Therefore, it can also be considered that if a terminal device accesses the network using narrowband high-orbit satellite access technology, it implicitly supports the ability to make calls using this technology. In other words, if the calling terminal device accesses the network using narrowband high-orbit satellite access technology, it means that the calling terminal device supports the ability to make calls using narrowband high-orbit satellite access technology and accesses the network using narrowband high-orbit satellite access technology.

[0168] Understandably, since the terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, it can access the network based on this technology. As described above, this will lead to increased call latency. Therefore, it is advisable to implement a simplified procedure (i.e., a simplified call procedure) in the call setup process when the terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology and / or can access the network based on this technology. This would reduce the number of signaling messages between the terminal device and the IMS network element, thereby reducing call latency.

[0169] However, for both the calling and called sides, one terminal device may not support the ability to perform calls based on narrowband high-orbit satellite access technology. Therefore, this terminal device cannot execute the simplified procedure. This results in one side executing the standard procedure (as shown in Figure 2) and the other side executing the standard procedure during the call setup process. In order to realize the call setup procedure in this scenario, at least one IMS network element needs to be able to convert the signaling in the standard procedure into the signaling in the simplified procedure, and / or convert the signaling in the simplified procedure into the signaling in the standard procedure.

[0170] For ease of description, the phrase "having the ability to convert signaling in a standard procedure into signaling in a simplified procedure, and / or converting signaling in a simplified procedure into signaling in a standard procedure" will be referred to as "having the ability to convert signaling" for short. This will be explained uniformly here and will not be elaborated further.

[0171] It is understood that in this application, the IMS network element has the ability to convert signaling, which can be understood as: the IMS network element can act as an end-to-end (back-to-back, B2B) user-agent (UA) to perform the conversion between signaling in the standard procedure and the signaling in the simplified procedure.

[0172] Taking the conversion of signaling in a standard procedure into a simplified procedure by an IMS network element as an example, the IMS network element can receive signaling in a standard procedure from its upstream node, convert it into signaling in a simplified procedure, and then send it to the next node. Therefore, for signaling in a standard procedure, the IMS network element can act as the node where the source address of the signaling in the standard procedure is located, executing the standard procedure. That is, the signaling in the standard procedure terminates at the IMS network element, or in other words, the IMS network element is the node where the destination address of the signaling in the standard procedure is located. Correspondingly, the IMS network element can also send back the corresponding standard procedure signaling to the node where the source address of the signaling in the standard procedure is located.

[0173] Similarly, for signaling in a simplified procedure, an IMS network element can act as a B2B UA to execute the simplified procedure between the node where the destination address of the signaling in the simplified procedure is located; that is, the node where the source address of the signaling in the simplified procedure is located is an IMS network element. Correspondingly, the node where the destination address of the signaling in the simplified procedure is located can also send back the corresponding simplified procedure signaling to the IMS network element.

[0174] For example, when accessing a network based on narrowband high-orbit satellite access technology, a simplified procedure is executed during call setup. Therefore, the terminal device needs to receive signaling from this simplified procedure, and it also needs to generate and output the signaling from the simplified procedure. In other words, the terminal device needs to process the signaling from the simplified procedure. Therefore, the terminal device's ability to perform calls based on narrowband high-orbit satellite access technology can also be understood as: the terminal device supports using narrowband high-orbit as IP-CAN to perform call services (such as voice and video services); further, it can also be understood as: the terminal device supports processing the signaling from the simplified procedure.

[0175] Therefore, the IMS network element can determine whether to enable its signaling conversion capability by determining whether the terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, or whether the terminal device accesses the network based on narrowband high-orbit satellite access technology, at least one of these conditions. Specifically, if the terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, or if the terminal device accesses the network based on narrowband high-orbit satellite access technology, at least one of these conditions is met, the IMS network element determines to enable its signaling conversion capability.

[0176] For example, an IMS network element can determine whether its corresponding local terminal device (e.g., the calling side IMS network element determines the calling side terminal device) supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether it accesses the network based on narrowband high-orbit satellite access technology; or, an IMS network element can determine whether its corresponding remote terminal device (e.g., the called side IMS network element determines the calling side terminal device) supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether it accesses the network based on narrowband high-orbit satellite access technology.

[0177] For example, when determining whether a simplified procedure should be executed between the IMS network element and the calling terminal device, it can be determined whether the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether it accesses the network based on narrowband high-orbit satellite access technology. If the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or accesses the network based on narrowband high-orbit satellite access technology, then it is determined that a simplified procedure should be executed between the IMS network element and the calling terminal device. Therefore, if a standard procedure is executed between the IMS network element and the called terminal device, then its ability to convert signaling needs to be enabled to convert the signaling in the standard procedure (such as the second message in step S402) into the signaling in the simplified procedure (such as the third message in step S404).

[0178] Optionally, in this application, the IMS network element may be assumed to have the capability to switch signaling. Therefore, the IMS network element can determine whether to enable its signaling switching capability by determining whether the terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, or whether the terminal device accesses the network based on narrowband high-orbit satellite access technology, at least one of these conditions. Alternatively, the IMS can determine whether it has the capability to switch signaling, and if it does, determine whether to enable its signaling switching capability by determining whether the terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, or whether the terminal device accesses the network based on narrowband high-orbit satellite access technology, at least one of these conditions.

[0179] For example, whether a terminal device supports the ability to make calls based on narrowband high-orbit satellite access technology can also be referred to as: whether a terminal device supports the ability to provide voice services (VoGEO) based on narrowband high-orbit satellites; the terminal device's access network technology based on narrowband high-orbit satellites includes, but is not limited to, the terminal device's access network based on GEO.

[0180] For ease of description, the following description will use "the terminal device's ability to perform calls based on narrowband high-orbit satellite access technology" as "the terminal device's ability to support VoGEO" and "the terminal device's access to the network based on narrowband high-orbit satellite access technology" as "the terminal device's access to the network based on GEO" as an example. This will be explained uniformly here and will not be repeated.

[0181] Specifically, non-narrowband high-orbit satellite access technologies include, but are not limited to, terrestrial network technologies; for example, LTE, NR, etc.

[0182] For example, the implementation of step S403 can be found in the relevant description in the following embodiments, and will not be repeated here.

[0183] It should be noted that this application does not limit the order of steps S401-S402 and step S403; for example, steps S401-S402 may be performed before step S403; or, steps S401-S402 may be performed after step S403; or, steps S401-S402 may be performed simultaneously with step S403.

[0184] S404, the first IMS network element generates a third message. This third message indicates that the called party's terminal device (the second terminal device) has been ringing.

[0185] For example, when the first IMS network element receives the second message and determines that the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the calling terminal device accesses the network based on narrowband high-orbit satellite access technology (or, in other words, determines that the first IMS network element enables the conversion signaling), it generates the third message.

[0186] For example, the third message can be a 180ring message.

[0187] S405, the first IMS network element sends a third message to the first device; correspondingly, the first device receives the third message from the first IMS network element.

[0188] Taking the third message as a 180ring message as an example, it can be understood that the transmission path of the 180ring message is usually: called side terminal device → called side IMS network element → calling side IMS network element → calling side terminal device. Therefore, if the first IMS network element is the called side IMS network element, then the called side IMS network element needs to send the message to the calling side IMS network element, that is, the first device is the calling side IMS network element; at this time, steps S404 to S405 can be as shown in Figure 6(a). If the first IMS network element is the calling side IMS network element, then the calling side IMS network element needs to send the message to the calling side terminal device, that is, the first device is the calling side terminal device; at this time, steps S404 to S405 can be as shown in Figure 6(b).

[0189] For example, when the first device is the calling side IMS network element, after receiving the third message, the first device also needs to send a message indicating that the called side terminal device has been ringing to the calling side terminal device; for example, after receiving the third message, the first device can directly forward the third message to the calling side terminal device; or, after receiving the third message, the first device can send message #3 to the calling side terminal device, message #3 is used to indicate that the called side terminal device has been ringing.

[0190] As can be seen from the foregoing embodiments, the first IMS network element is an intermediate node in the call setup process between the calling terminal device and the called terminal device. Typically, the intermediate node in the call setup process is used to forward the information received from the previous node to the next node until the information reaches the calling terminal device or the called terminal device. That is to say, typically, the node where the source address of the signaling exchanged in the call setup process is located is the calling terminal device or the called terminal device, and correspondingly, the node where the destination address is located is the called terminal device or the calling terminal device.

[0191] However, based on the above steps S401 to S405, in this application, after the first IMS network element receives the second message (such as the 183 session progress message) from its previous node (such as the second device), if it determines that the calling terminal device satisfies at least one of the following: the ability to perform calls based on narrowband high-orbit satellite access technology, or the ability to access the network based on narrowband high-orbit satellite access technology, then it does not need to send the second message or the message corresponding to the second message that indicates that the session is in progress and carries the first media response information to the next node (such as the first device); instead, it sends the third message to the next node. At this time, it can be considered that in this application, the second message (such as the 183 session progress message) terminates in the first IMS network element, or in other words, the first IMS network element is the termination node of the second message.

[0192] Based on the calling method shown in Figure 4, during the process of the calling terminal device (i.e., the first terminal device) calling the called terminal device (the second terminal device) (i.e., from the transmission of INVITE messages (such as the first message, which is used by the calling terminal device to call the called terminal device and includes media request information) between the calling and called parties), the IMS network element (i.e., the first IMS network element) on the calling / called side can receive 183 sessions from its upstream node (i.e., the second device; wherein, the first IMS network element is a network element in the IMS network accessed by the calling terminal device (such as the calling P-CSCF), and correspondingly, the second device is a network element in the IMS network accessed by the called terminal device (such as the called P-CSCF); the first IMS network element is a network element in the IMS network accessed by the second terminal device (such as the called P-CSCF), and correspondingly, the second device is the called terminal device). The progress message (such as the second message, which indicates that the session is in progress, and also includes first media response information); furthermore, the IMS network element on the calling / called side can obtain whether the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether the calling terminal device accesses the network based on narrowband high-orbit satellite access technology, and if the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or if the calling terminal device accesses the network based on narrowband high-orbit satellite access technology, it generates a 180-ring message; and sends the 180-ring message to its next node (i.e., the first device; wherein, the first IMS network element is a network element in the IMS network accessed by the first terminal device (such as the calling side P-CSCF), and correspondingly, the first device is the calling side terminal device; the first IMS network element is a network element in the IMS network accessed by the called side terminal device (such as the called side P-CSCF), and correspondingly, the first device is a network element in the IMS network accessed by the calling side terminal device (such as the calling side P-CSCF).

[0193] In other words, after receiving a 183 session progress message from its upstream node, the calling / called IMS network element can determine whether to generate a 180 ring and send it to the next node by judging whether the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether the calling terminal device accesses the network based on narrowband high-orbit satellite access technology. For example, it can convert the 183 session progress message into a 180 ring message and send it to its next node. Specifically, if the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or if the calling terminal device accesses the network based on narrowband high-orbit satellite access technology, then the calling / called IMS network element can directly convert the 183 session progress message into a 180 ring message and send it to its next node. At this point, the IMS network element on the calling / called side and the calling terminal device interact using a 180ring message instead of a 183 session progress message. Therefore, the IMS network element on the calling / called side and the calling terminal device no longer need to transmit 183 session progress, PRACK, and UPDATA messages. In other words, the IMS network element on the calling / called side and the calling terminal device do not need to sequentially transmit INVITE, 183 session progress, PRACK, UPDATA, and 180ring messages to complete the call setup process between the calling and called parties. Instead, the 180ring message is transmitted directly after the INVITE message. That is, in the call setup process, the IMS network element on the calling / called side and the calling terminal device only need to complete signaling interactions such as INVITE and 180ring messages. This reduces the number of signaling messages exchanged in the call setup process, thereby reducing call latency and improving user experience.

[0194] The above is an overall description of the call method provided in this application. The implementation of step S403 in the above embodiment will be described in detail below. For example, the first IMS network element can determine whether the calling terminal device supports VoGEO capability and / or whether the calling terminal device accesses the network based on GEO, based on the following two methods.

[0195] Method 1: The first IMS network element determines from the first device whether the calling terminal device supports VoGEO capability and / or whether the calling terminal device accesses the network based on GEO.

[0196] For example, in Mode 1, the first device can inform the first IMS network element via a fourth message whether the calling terminal device supports VoGEO capability and / or whether the calling terminal device accesses the network based on GEO; at this time, the fourth message also indicates at least one of whether the calling terminal device supports VoGEO capability or whether the calling terminal device accesses the network based on GEO. That is, in Mode 1, step S403 is the same as step S400.

[0197] As an example, when the first IMS network element is the calling side IMS network element, the first device is the calling side terminal device; the calling side terminal device can determine whether it supports VoGEO capability, and / or whether the calling side terminal device is based on GEO access network indication information, and inform the first IMS network element through the fourth message.

[0198] For example, information indicating whether the calling terminal device supports narrowband high-orbit satellite access technology for call execution can be located in the supported header field of the fourth message. That is, the supported header field in the fourth message is used to indicate whether the calling terminal device supports VoGEO capability. Specifically, when the supported header field indicates that the calling terminal device supports VoGEO capability, it means that the fourth message indicates that the calling terminal device supports VoGEO capability.

[0199] For example, the supprted header field can use a 1-bit field to indicate whether the calling terminal device supports VoGEO capability. If the 1-bit field is 1, it indicates that the calling terminal device supports VoGEO capability; conversely, if the 1-bit field is 0, it indicates that the calling terminal device does not support VoGEO capability.

[0200] Alternatively, if the 1-bit field exists in the supprted header field, it indicates that the calling terminal device supports VoGEO capability; if the 1-bit field does not exist in the supprted header field, it indicates that the calling terminal device does not support VoGEO capability.

[0201] For example, if the supported header field includes VoGEO (supported: VoGEO), it means that the calling terminal device supports VoGEO; if the supported header field does not include VoGEO, it means that the calling terminal device does not support VoGEO.

[0202] For example, the information used to indicate whether the calling terminal device accesses the network based on GEO can be located in the private access network information (P-ANI) header field of the fourth message; that is, the P-ANI header field in the fourth message is used to indicate whether the calling terminal device accesses the network based on GEO.

[0203] For example, the P-ANI header field is used to indicate the method by which the calling terminal device accesses the network; this method of network access includes, but is not limited to, GEO access, LTE access, NR access, etc. Specifically, when the P-ANI header field indicates that the calling terminal device accesses the network based on GEO, it means that the fourth message indicates that the calling terminal device accesses the network based on GEO.

[0204] As another example, when the first IMS network element is the called side IMS network element, the first device is the calling side IMS network element; at this time, the calling side IMS network element can learn from the calling side terminal device or the calling side core network device whether the calling side terminal device supports VoGEO capability, and / or whether the calling side terminal device accesses the network based on GEO.

[0205] Implementation Method 1: The calling side IMS network element can learn from the calling side terminal device whether the calling side terminal device supports VoGEO capability and / or whether the calling side terminal device accesses the network based on GEO.

[0206] For example, after determining whether it supports VoGEO capability and / or whether it accesses the network based on GEO, the calling terminal device may add information indicating whether it supports VoGEO capability and / or whether it accesses the network based on GEO to message #2; this allows the calling IMS network element to obtain message #2 from the calling terminal device, thereby knowing that message #2 is used to indicate whether the calling terminal device supports VoGEO capability and / or whether it accesses the network based on GEO; wherein, message #2 is used for the calling terminal device to call the called terminal device, and information indicating whether the calling terminal device supports VoGEO capability, or whether the calling terminal device accesses the network based on GEO, at least one of these, and message #2 includes media request information. Furthermore, the calling IMS network element can determine and send a fourth message (such as an INVITE message) to the called IMS network element based on message #2. Specifically, message #2 can be the same as the fourth message, meaning the calling IMS network element forwards message #2; or message #2 can be different from the fourth message, meaning the calling IMS network element can process (such as modify or adjust) message #2 to obtain the fourth message, and then send the fourth message to the called IMS network element. This enables the first IMS network element to determine whether the calling terminal device supports VoGEO capability and / or whether the calling terminal device accesses the network based on GEO.

[0207] Implementation Method 2: The calling side IMS network element can obtain information from the calling side core network (or, also known as the first core network equipment) about whether the calling side terminal equipment supports VoGEO capability and / or whether the calling side terminal equipment accesses the network based on GEO.

[0208] For example, the calling-side core network device can determine whether the calling-side terminal device accesses the network based on GEO. Furthermore, the calling-side core network device can determine whether the calling-side terminal device supports VoGEO capabilities; for example, the calling-side terminal device can report its VoGEO capability to the calling-side core network device, enabling the calling-side core network device to determine whether the calling-side terminal device supports VoGEO capabilities. This application does not limit the scope of the application to allowing the terminal device to report information indicating whether the calling-side terminal device supports VoGEO capabilities during network registration.

[0209] Furthermore, the calling-side core network device can send a message to the calling-side IMS network element indicating whether the calling-side terminal device supports VoGEO capability and / or whether the calling-side terminal device accesses the network based on GEO. This enables the calling-side IMS network element to determine whether the calling-side terminal device supports VoGEO capability and / or whether the calling-side terminal device accesses the network based on GEO. Typically, the calling-side core network device sends this message to the calling-side IMS network element based on a request message triggered by the request message from the calling-side IMS network element. This request message instructs the calling-side core network device to send the same message to the calling-side IMS network element.

[0210] Furthermore, after the calling side IMS network element learns whether the calling side terminal device supports VoGEO capability and / or whether the calling side terminal device accesses the network based on GEO, it can generate and send a fourth message to the called side IMS network element, enabling the called side IMS network element to determine whether the calling side terminal device supports VoGEO capability and / or whether the calling side terminal device accesses the network based on GEO. The fourth message is used for at least one of the following: the calling side terminal device calls the called side terminal device; and it indicates whether the calling side terminal device supports VoGEO capability or whether the calling side terminal device accesses the network based on GEO. The fourth message includes media request information. Specifically, the implementation of the fourth message can be found in the relevant description in the above embodiments, and will not be repeated here.

[0211] Optionally, in implementation method two, before step S401, the calling terminal device can also send message #2 to the calling IMS network element; where message #2 is used to instruct the calling terminal device to call the called terminal device, and message #2 also carries media request information. For example, message #2 can be an INVITE message. Further, the calling IMS network element can generate a fourth message based on message #2 and the fifth message. Taking the fourth message as an INVITE message as an example, after receiving the INVITE message (i.e., message #2) from the calling terminal device, the calling IMS network element can add information indicating whether the calling terminal device supports VoGEO capability and / or whether the calling terminal device accesses the network based on GEO, to obtain a new INVITE message (i.e., the fourth message), so that the new INVITE message indicates whether the calling terminal device supports VoGEO capability and / or whether the calling terminal device accesses the network based on GEO. This sends a new INVITE message, enabling the called party's IMS network element to determine whether the calling party's terminal device supports VoGEO capabilities and / or whether the calling party's terminal device accesses the network via GEO.

[0212] Method 2: When the first IMS network element is the calling side IMS network element, the first IMS network element can determine from the calling side core network equipment whether the calling side terminal equipment supports VoGEO capability and / or whether the calling side terminal equipment accesses the network based on GEO.

[0213] For example, the calling-side core network device can determine whether the calling-side terminal device accesses the network based on GEO. Furthermore, the calling-side core network device can determine whether the calling-side terminal device supports VoGEO capabilities; for example, the calling-side terminal device can report its VoGEO capability to the calling-side core network device, enabling the calling-side core network device to determine whether the calling-side terminal device supports VoGEO capabilities. This application does not limit the reporting of information indicating whether the calling-side terminal device supports VoGEO capabilities, such as including it in its INVITE message (e.g., the fourth message) or during network registration.

[0214] Furthermore, the calling-side core network device can send a message (i.e., the fifth message) to the calling-side IMS network element to indicate whether the calling-side terminal device supports VoGEO capability and / or whether the calling-side terminal device accesses the network based on GEO, thereby enabling the calling-side IMS network element to determine whether the calling-side terminal device supports VoGEO capability and / or whether the calling-side terminal device accesses the network based on GEO. Typically, the calling-side core network device sends this message to the calling-side IMS network element based on a request message from the calling-side IMS network element, indicating whether the calling-side terminal device supports VoGEO capability and / or whether the calling-side terminal device accesses the network based on GEO. This request message instructs the calling-side core network device to send this message to the calling-side IMS network element to indicate whether the calling-side terminal device supports VoGEO capability and / or whether the calling-side terminal device accesses the network based on GEO. Specifically, as shown in Figure 7, before step S403, the call method may further include:

[0215] S406. The calling side core network device sends the fifth message to the calling side IMS network element, and correspondingly, the calling side IMS network element receives the fifth message from the calling side core network device.

[0216] The fifth message indicates at least one of the following: whether the calling terminal device supports VoGEO capability, or whether the calling terminal device accesses the network based on GEO. In this case, step S403 can be replaced by: the first IMS network element determining, based on the fifth message, that the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the calling terminal device accesses the network based on narrowband high-orbit satellite access technology.

[0217] For example, if the calling terminal device supports VoGEO capability, the fifth message indicates that the calling terminal device supports VoGEO capability; if the calling terminal device accesses the network based on GEO, the fifth message indicates that the calling terminal device accesses the network based on GEO.

[0218] If the calling terminal device does not support VoGEO capability, the fifth message indicates that the calling terminal device does not support VoGEO capability; or, the calling core network device may not send the fifth message. In this case, it can also be considered that the calling core network device only sends the fifth message to the calling IMS network element if the calling terminal device supports VoGEO capability, that is, the fifth message indicates that the calling terminal device supports VoGEO capability.

[0219] Similarly, when the calling terminal device is based on a non-GEO access network, the fifth message is used to indicate that the calling terminal device is based on a non-GEO access network; for example, when the calling terminal device is based on an LTE access network, the fifth message is used to indicate that the calling terminal device is based on an LTE access network; when the calling terminal device is based on an NR access network, the fifth message is used to indicate that the calling terminal device is based on an NR access network.

[0220] Furthermore, the calling side core network device can send a fifth message to the calling side IMS network element based on the request message from the calling side IMS network element; that is, the fifth message is triggered by the request message from the calling side IMS; as shown in Figure 7, before step S406, the call method also includes step S407:

[0221] S407. The calling side IMS network element sends a request message to the calling side core network equipment; correspondingly, the calling side core network equipment receives the request message from the calling side IMS network element. The request message instructs the calling side core network equipment to send a fifth message.

[0222] Combining the two methods described above, optionally, after the first IMS network element learns whether the calling terminal device supports VoGEO capability or whether the calling terminal device accesses the network based on GEO (at least one of these), it can also inform the second device. For example, information indicating whether the calling terminal device supports VoGEO capability or whether the calling terminal device accesses the network based on GEO can be carried in a first message and communicated to the second device. In this case, steps S406-S407 and S403 are all executed before step S401. The first message further indicates whether the calling terminal device supports VoGEO capability or whether the calling terminal device accesses the network based on GEO (at least one of these). For example, the first information may also indicate whether the calling terminal device supports VoGEO capability or whether the calling terminal device accesses the network based on GEO (at least one of these).

[0223] Method 3: When the first IMS network element is the called party's IMS network element, if the first IMS network element determines in step S403 that it does not enable the ability of the switching signaling (i.e., the calling party's terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or, the calling party's terminal device accesses the network based on non-narrowband high-orbit satellite access technology), and the first IMS network element itself has the ability to switch signaling; at this time, the first IMS network element can further determine whether the called party's terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or, the called party's terminal device accesses the network based on narrowband high-orbit satellite access technology.

[0224] Wherein, if the called-side terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or, if the called-side terminal device accesses the network based on narrowband high-orbit satellite access technology, the first IMS network element can enable the ability to perform this conversion signaling; that is, the first IMS network element acts as a B2B UA to perform simplified signaling interaction with the called-side terminal device; and performs standard signaling interaction with the calling-side terminal device.

[0225] Furthermore, the first IMS network element can also inform the called terminal device that it has the ability to switch signaling; so that after receiving the INIVITE message, the called terminal device can send back signaling with a simplified process (such as sending back a 180ring message, i.e., executing step S1702 in Figure 17 below).

[0226] Specifically, since the first IMS network element interacts with the called-side terminal equipment as a B2B UA, the called-side terminal equipment considers the called-side IMS network element to be the calling-side equipment (such as the calling-side terminal equipment). Therefore, upon receiving this indication, it will assume that the calling side supports VoGEO capabilities. Furthermore, it can also be assumed that the calling side has the ability to process simplified procedure signaling, and thus, upon receiving the INIVITE message, it can feed back the simplified procedure signaling (such as a 180ring message). Optionally, the first media response information can also be carried in the 180ring message.

[0227] In other words, under Method 3, the called-side terminal device can send a 180ring message in any of the following situations: (1) The called-side terminal device accesses the network based on narrowband high-orbit satellite access technology; (2) The called-side terminal device accesses the network based on narrowband high-orbit satellite access technology, and the first IMS network element has the ability to convert signaling; (3) The called-side terminal device accesses the network based on non-narrowband high-orbit satellite access technology, the called-side IMS network element has the ability to convert signaling, and the calling-side terminal device accesses the network based on narrowband high-orbit satellite access technology; (4) The called-side terminal device accesses the network based on non-narrowband high-orbit satellite access technology, the called-side IMS network element has the ability to convert signaling, the calling-side terminal device accesses the network based on narrowband high-orbit satellite access technology, and the called-side terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology. This enables the first IMS network element to receive the second message in step S2002 below. Furthermore, the 180ring message is used to indicate the first media response information, enabling the first IMS network element to receive the second message in step S1702.

[0228] The above is an explanation of the implementation of step S403. The implementation of the "second message and third message" involved in the above embodiments will be described in detail below.

[0229] (I) Regarding the second message:

[0230] It can be understood that the messages used to indicate that a session is in progress and to carry media response information (such as a second message) are usually temporary messages. After the temporary message arrives at the node where its destination address is located or the terminating node, the node where the destination address is located or the terminating node needs to send an acknowledgment message for the temporary message to the node where the source address of the temporary message is located (i.e., to acknowledge the receipt of the temporary message to the node where the source address is located), to indicate that it has received the temporary message. Therefore, after step S402, as shown in Figure 8, the call method may also include steps S408 to S409:

[0231] S408. The first IMS network element generates a sixth message. This sixth message confirms that the first IMS network element has received the first media response information. For example, the sixth message can be a PRACK message.

[0232] S409, the first IMS network element sends the sixth message to the second device.

[0233] Furthermore, if the second device is the called-side IMS network element, the second device also needs to send the information indicated by the sixth message (i.e., the information used to confirm that the first IMS network element has received the first media response information) to the called-side terminal device.

[0234] For example, based on the aforementioned step S403, the first IMS network element can act as a B2B UA to interact with both the calling and called terminal devices. Therefore, after receiving the second message, the first IMS network element can execute steps S408 to S409 to interact with the called terminal device. In addition, after receiving the second message, the first IMS network element can also simultaneously execute steps S404 to S405 to interact with the calling terminal device.

[0235] In this process, the first IMS network element acts as a B2B UA and performs standard signaling interactions with the called terminal device. Specifically, after receiving confirmation from the first IMS network element that it has received the first media response information, the called terminal device can send a confirmation message (such as a PRACK 200 OK message, or a 200 OK PRACK message) to the first IMS network element. Further, the first IMS network element can send an UPDATA message to the called terminal device; correspondingly, the called terminal device sends a confirmation message (such as an UPDATA 200 OK message, or a 200 OK UPDATA message) to the first IMS network element. Additionally, the called terminal device sends a 180ring message to the first IMS network element.

[0236] Specifically, this application does not limit the order of steps S408-S409 with steps S404-S405. For example, steps S408-S409 may be performed before steps S404-S405; or steps S408-S409 may be performed after steps S404-S405; or steps S408-S409 may be performed simultaneously with steps S404-S405.

[0237] (II) Regarding the third message:

[0238] For example, the third message may include the following two possible implementations:

[0239] In one possible implementation, the third message includes second media response information. That is, the message used to indicate that the called terminal device has been ringing also carries second media response information.

[0240] For example, the second media response information may be the same as or different from the first media response information. For example, the implementation of the first media response information can be found in the relevant description of the above embodiments, and will not be repeated here.

[0241] For example, when the second media response information differs from the first media response information, the second media response information is generated by the first IMS device. For instance, the first media response information can be the media information of the called terminal device itself (such as the media types and encoding formats supported by the called terminal device); correspondingly, the second media response information can be the media information negotiated between the calling terminal device and the first IMS network element, that is, the media information applicable to narrowband high-orbit satellite access technology indicated by both the first IMS network element and the calling terminal device (such as media types and encoding formats, for example, the voice encoding format can be 1.2kbps, 0.8kbps, etc.).

[0242] Optionally, in this possible implementation, if the first device is the calling side IMS network element, after receiving the third message from the first IMS network element, the first device also needs to send the information carried in the third message to the calling side terminal device; for example, the calling side IMS network element can directly forward the third message to the calling side terminal device, or the calling side IMS network element can generate message #4 based on the third message and send message #4 to the calling side terminal device. Message #4 is used to indicate that the second terminal device has been ringing, and message #4 also carries second media response information.

[0243] As an example, the first IMS network element can generate and send the third message after receiving the second message without waiting for a 180ring message from the called party's terminal device. That is, the first IMS network element can directly execute steps S404 to S405 after steps S402 to S403.

[0244] Optionally, in this example, after receiving a message (such as a third message or message #4) indicating that the second terminal device has been ringing and carrying second media response information, the calling terminal device can send a PRACK message to the first IMS network element to confirm that it has received the second media response information. Specifically, when the first device is both the calling terminal device and the first IMS network element is also the calling IMS network element, the calling terminal device can directly send the PRACK message to the first IMS network element. When the first device is both the calling and called IMS network elements, the calling terminal device can send a PRACK message to the first device (i.e., the calling IMS network element). Further, after receiving the PRACK message, the calling IMS network element can forward the PRACK message to the first IMS network element (i.e., the called IMS network element), or it can generate a new PRACK message based on the PRACK message and send the new PRACK message to the first IMS network element. The new PRACK message indicates that the calling terminal device has received the second media response information. Specifically, the first IMS network element can process (such as modify or adjust) the PRACK message to obtain a new PRACK message.

[0245] Furthermore, the calling terminal device can also send an UPDATA message to the first IMS network element to indicate that the call resource reservation for the calling terminal device has been successful. Specifically, the implementation of the calling terminal device sending an UPDATA message to the first IMS network element is similar to the implementation of sending a PRACK message to the first IMS network element described above. For details, please refer to the relevant description of the calling terminal device sending a PRACK message to the first IMS network element, which will not be repeated here.

[0246] For example, the calling terminal device sends a PRACK message and an UPDATA message to the first IMS network element. Alternatively, the calling terminal device can use a signaling message (such as the eighth message) to indicate that it has received the second media response information and that the call resource reservation for the calling terminal device has been successful. When the first device is the calling IMS network element and the first IMS network element is the called IMS network element, the calling terminal device can send message #5 to the first device (i.e., the calling IMS network element). Message #5 is used to indicate that the calling terminal device has received the second media response information and that the call resource reservation for the calling terminal device has been successful. Further, after receiving message #5, the calling IMS network element can forward message #5 to the first IMS network element (i.e., the called IMS network element); at this time, message #5 is the eighth message. Alternatively, the eighth message can be generated based on message #5 and sent to the first IMS network element. Specifically, the first IMS network element can process message #5 (such as modifying or adjusting it) to obtain the eighth message.

[0247] Optionally, the UPDATA message sent by the first IMS network element to the called terminal device as described in the above embodiments can also be referred to as the ninth message. For example, in this case, this step can be performed after receiving the eighth message; that is, the first IMS network element can send the ninth message based on the eighth message (i.e., send the ninth message after receiving the eighth message); in other words, the first IMS network element can learn from the calling terminal device that the calling terminal device's call resource reservation has been successful, and then inform the second device of the successful call resource reservation indication from the calling terminal device. Furthermore, if the second device is the called IMS network element, the second device also needs to inform the called terminal device of the successful call resource reservation indication from the calling terminal device.

[0248] Furthermore, in this example, after the called-side terminal device sends a 180ring message to the first IMS network element, it can also send an INVITE 200 OK message (or, it can also be called a 200 OK INVITE message) to the calling-side terminal device; so that the calling-side terminal device can send an ACK message to the called-side terminal device; thereby realizing the call between the calling-side terminal device and the called-side terminal device.

[0249] The following example illustrates the calling method described in this application embodiment, where the first message is an INVITE message, the second message is a 183 session progress message, the third message is a 180 ring message, the fourth message is an INVITE message, the sixth message is a PRACK message, the eighth message is a PRACK message, the ninth message is an UPDATA message, the first and second media response information are both SDP answers, and the media request information is an SDP offer. For example, in this example, the calling method can be implemented based on the following two scenarios:

[0250] Scenario 1: The first IMS network element is the calling side IMS network element, the first device is the calling side terminal device, and the second device is the called side IMS device. Referring to Figure 9, a possible implementation of the calling method described in this application is shown. This calling method may include the following steps:

[0251] S901, the calling terminal device sends an INVITE message to the called terminal device; correspondingly, the called terminal device receives the INVITE message from the calling terminal device. The INVITE message is used by the calling terminal device to call the called terminal device, and the INVITE message includes an SDP offer.

[0252] Specifically, the INVITE message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0253] For example, after the calling IMS network element receives the INVITE message, it can also send a 100 Trying message back to the calling terminal device. That is, the calling IMS network element can execute step S902:

[0254] S902, the calling side IMS network element sends a 100 Trying message to the calling side terminal device; correspondingly, the calling side terminal device receives the 100 Trying message from the calling side IMS network element. The 100 Trying message is used to confirm that the calling side IMS network element has received the INVITE message sent by the calling side terminal device.

[0255] S903, the called-side terminal device sends a 183 session progress message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the 183 session progress message from the called-side terminal device. The 183 session progress message carries the SDP answer.

[0256] Specifically, the 183 session progress message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0257] S904, The calling side IMS network element determines the simplified process executed by the calling side.

[0258] For example, the calling side IMS network element determines whether the calling side should execute a simplified procedure based on at least one of the following: whether the calling side terminal device supports VoGEO capability, or whether the calling side terminal device accesses the network via GEO. When the calling side terminal device supports VoGEO capability and / or accesses the network via GEO, the calling side IMS network element determines that it has the capability to enable its conversion signaling and that the calling side terminal device has the capability to process signaling in the simplified procedure. Therefore, the calling side can execute the simplified procedure, which is the signaling interaction between the calling side terminal device and the calling side IMS network element for executing the simplified procedure. In other words, the calling side IMS network element acts as the B2BUA for simplified procedure signaling interaction with the calling side terminal device and for standard procedure signaling interaction with the called side terminal device. See the relevant descriptions in steps S905 to S915 below for details, which will not be repeated here.

[0259] Specifically, the implementation of step S904 can be found in the relevant description of step S403 above, and will not be repeated here.

[0260] S905, the calling side IMS network element generates a 180ring message. This 180ring message carries the SDP answer.

[0261] S906, The calling side IMS network element sends a 180-ring message to the calling side terminal equipment; correspondingly, the calling side terminal equipment receives the 180-ring message from the calling side IMS network element.

[0262] S907. The calling side terminal device sends a PRACK message to the calling side IMS network element; correspondingly, the calling side IMS network element receives the PRACK message from the host side terminal device.

[0263] The PRACK message is used to indicate that the calling terminal device has received the SDP answer. Furthermore, the PRACK message can also indicate that the calling terminal device has successfully reserved call resources.

[0264] S908. The calling IMS network element sends a PRACK 200 OK message to the calling terminal device; correspondingly, the calling terminal device receives the PRACK 200 OK message from the calling IMS network element. The PRACK 200 OK message indicates that the calling IMS network element has received the PRACK message.

[0265] Optionally, if the PRACK message in S907 does not indicate that the call resource reservation for the calling terminal device is successful, the calling terminal device still needs to send an UPDATA message to the calling IMS network element after it learns that the call resource reservation for the calling terminal device is successful, in order to inform the calling IMS network element that the call resource reservation for the calling terminal device is successful. Further, the calling IMS network element can send an UPDATA 200 OK message back to the calling terminal device to inform it that it has received the UPDATA message. For ease of description, Figure 9 uses the example of the calling terminal device receiving the SDP answer in the PRACK message in step S907 and the call resource reservation for the calling terminal device being successful. This will be explained uniformly here and will not be repeated.

[0266] In addition, after step S903, the calling method further includes the following steps:

[0267] S909, the calling IMS network element sends a PRACK message to the called terminal device; correspondingly, the called terminal device receives the PRACK message from the calling IMS network element. The PRACK message indicates that the calling IMS network element has received the SDP answer.

[0268] For example, the PRACK message sent by the calling side IMS network element reaches the called side terminal device through the called side IMS network element.

[0269] It should be noted that this application does not limit the order of steps S905-S906 and step S909; for example, steps S905-S906 can be performed before step S909, or steps S905-S906 can be performed after step S909, or steps S905-S906 can be performed simultaneously with step S909.

[0270] S910, the called-side terminal device sends a PRACK 200 OK message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the PRACK 200 OK message from the called-side terminal device. The PRACK 200 OK message indicates that the called-side terminal device has received the PRACK message.

[0271] For example, the PRACK 200 OK message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0272] Furthermore, after steps S908 and S910, the calling method further includes the following steps:

[0273] S911, the calling side IMS network element sends an UPDATA message to the called side terminal device; correspondingly, the called side terminal device receives the UPDATA message from the calling side IMS network element. The UPDATA message indicates that the calling side terminal device has successfully reserved call resources.

[0274] For example, after the calling side IMS network element learns from the calling side terminal device that the call resources reservation for the calling side terminal device has been successful (i.e., step S907), it sends an UPDATA message to the called side terminal device (i.e., step S911 is executed after step S907).

[0275] Specifically, the UPDATA message sent by the calling side IMS network element is delivered to the called side terminal device via the called side IMS network element.

[0276] S912, the called-side terminal device sends an UPDATA 200 OK message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the UPDATA 200 OK message from the called-side terminal device. The UPDATA 200 OK message indicates that the called-side terminal device has successfully reserved call resources.

[0277] For example, the UPDATA 200 OK message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0278] S913, The called-side terminal device sends a 180-ring message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the 180-ring message from the called-side terminal device.

[0279] For example, a 180-ring message sent by the called-side terminal device reaches the calling-side IMS network element via the called-side IMS network element.

[0280] S914. The called-side terminal device sends an INVITE 200 OK message to the calling-side terminal device; correspondingly, the calling-side terminal device receives the INVITE 200 OK message from the called-side terminal device.

[0281] For example, the INVITE 200 OK message sent by the called-side terminal device passes through the called-side IMS network element and the calling-side IMS network element in sequence to reach the calling-side terminal device.

[0282] S915, The calling terminal device sends an ACK message to the called terminal device; correspondingly, the called terminal device receives the ACK message from the calling terminal device.

[0283] Specifically, the ACK message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0284] Scenario 2: The first IMS network element is the called party's IMS network element, the first device is the calling party's IMS network element, and the second device is the called party's terminal device. Referring to Figure 10, another possible implementation of the calling method described in this application is shown. This calling method may include the following steps:

[0285] S1001, the calling terminal device sends an INVITE message to the called terminal device; correspondingly, the called terminal device receives the INVITE message from the calling terminal device. The INVITE message is used by the calling terminal device to call the called terminal device, and the INVITE message includes an SDP offer.

[0286] Specifically, the INVITE message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0287] For example, after the calling side IMS network element receives the INVITE message, it can also send a 100 Trying message back to the calling side terminal device. That is, the calling side IMS network element can execute step S1002:

[0288] S1002, the calling side IMS network element sends a 100 Trying message to the calling side terminal device; correspondingly, the calling side terminal device receives the 100 Trying message from the calling side IMS network element. The 100 Trying message is used to confirm that the calling side IMS network element has received the INVITE message sent by the calling side terminal device.

[0289] S1003, the called-side terminal device sends a 183 session progress message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the 183 session progress message from the called-side terminal device. The 183 session progress message carries the SDP answer.

[0290] Specifically, the 183 session progress message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0291] S1004. The called party's IMS network element determines the simplified process executed by the calling party.

[0292] For example, the called-side IMS network element determines whether the calling side should execute a simplified procedure based on at least one of the following: whether the calling-side terminal device supports VoGEO capability, or whether the calling-side terminal device accesses the network via GEO. When the calling-side terminal device supports VoGEO capability and / or accesses the network via GEO, the called-side IMS network element determines that it has the capability to enable its conversion signaling, and the calling-side terminal device has the capability to process signaling in the simplified procedure. Therefore, the calling side can execute the simplified procedure, i.e., the signaling interaction between the calling-side terminal device and the calling-side IMS network element for executing the simplified procedure. In other words, the calling-side IMS network element, as a B2B UA, performs simplified procedure signaling interaction with the calling-side terminal device, and standard procedure signaling interaction with the called-side terminal device. See the relevant descriptions of steps S1005 to S1015 below for details, which will not be repeated here.

[0293] For example, the called-side IMS network element can execute step S1004 by indicating in the INVITE message from the calling-side IMS network element whether the calling-side terminal device supports VoGEO capability or whether the calling-side terminal device accesses the network based on GEO, at least one of these indicators; thereby determining that the calling side can execute the simplified procedure if it is determined that the calling-side terminal device supports VoGEO capability or whether the calling-side terminal device accesses the network based on GEO, at least one of these indicators.

[0294] Specifically, the implementation of at least one of the following, such as whether the calling side knows whether the calling side terminal device supports VoGEO capability or indicates whether the calling side terminal device is based on GEO access network, can be found in the relevant descriptions in the foregoing embodiments and will not be repeated here.

[0295] S1005, The called party's IMS network element generates a 180ring message. This 180ring message carries the SDP answer.

[0296] S1006. The called side IMS network element sends a 180-ring message to the calling side terminal device; correspondingly, the calling side terminal device receives the 180-ring message from the called side IMS network element.

[0297] Specifically, the 180-ring message sent by the called side IMS network element reaches the calling side terminal device through the calling side IMS network element.

[0298] S1007. The calling terminal device sends a PRACK message to the called IMS network element; correspondingly, the called IMS network element receives the PRACK message from the host terminal device. The PRACK message indicates that the calling terminal device has received the SDP answer; furthermore, the PRACK message can also indicate that the calling terminal device has successfully reserved call resources.

[0299] Specifically, the PRACK message sent by the calling terminal device reaches the called IMS network element through the calling IMS network element.

[0300] S1008. The called party's IMS network element sends a PRACK 200 OK message to the calling party's terminal equipment; correspondingly, the calling party's terminal equipment receives the PRACK 200 OK message from the called party's IMS network element. The PRACK 200 OK message indicates that the called party's IMS network element has received the PRACK message.

[0301] Specifically, the PRACK 200 OK message sent by the called side IMS network element reaches the calling side terminal device through the calling side IMS network element.

[0302] Optionally, if the PRACK message in S1007 does not indicate that the call resource reservation for the calling terminal device is successful, the calling terminal device must also send an UPDATA message to the called IMS network element after it learns that the call resource reservation for the calling terminal device is successful, to inform the calling IMS network element that the call resource reservation for the calling terminal device is successful. Furthermore, the called IMS network element can send an UPDATA 200 OK message back to the calling terminal device to inform it that it has received the UPDATA message. For ease of description, Figure 10 uses the example of the calling terminal device receiving the SDP answer in the PRACK message in step S1007 and the call resource reservation for the calling terminal device being successful. This will be explained uniformly here and will not be repeated.

[0303] In addition, after step S1003, the calling method further includes the following steps:

[0304] S1009. The called party's IMS network element sends a PRACK message to the called party's terminal equipment; correspondingly, the called party's terminal equipment receives the PRACK message from the called party's IMS network element. The PRACK message indicates that the calling party has received the SDP answer.

[0305] It should be noted that this application does not limit the order of steps S1005-S1006 and step S1009; for example, steps S1005-S1006 can be performed before step S1009, or steps S1005-S1006 can be performed after step S1009, or steps S1005-S1006 can be performed simultaneously with step S1009.

[0306] In step S1009, since the called side IMS network element interacts with the called side terminal device as a B2B UA, the called side terminal device considers the called side IMS network element to be the calling side device (such as the calling side terminal device). Therefore, after receiving the PRACK message, the called side terminal device considers that the calling side has received the SDP answer.

[0307] S1010, the called-side terminal device sends a PRACK 200 OK message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the PRACK 200 OK message from the called-side terminal device. The PRACK 200 OK message indicates that the called-side terminal device has received the PRACK message.

[0308] Furthermore, after steps S1008 and S1010, the calling method further includes the following steps:

[0309] S1011, The called-side IMS network element sends an UPDATA message to the called-side terminal device; correspondingly, the called-side terminal device receives the UPDATA message from the called-side IMS network element. The UPDATA message indicates that the call resources reservation for the calling-side terminal device has been successful.

[0310] For example, after the called side IMS network element learns from the calling side terminal device that the call resource reservation of the calling side terminal device has been successful (i.e., step S907), it sends an UPDATA message to the called side terminal device (i.e., step S1011 is executed after step S1007).

[0311] S1012, the called-side terminal device sends an UPDATA 200 OK message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the UPDATA 200 OK message from the called-side terminal device. The UPDATA 200 OK message indicates that the called-side terminal device has successfully reserved call resources.

[0312] S1013. The called-side terminal device sends a 180-ring message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the 180-ring message from the called-side terminal device.

[0313] S1014. The called terminal device sends an INVITE 200 OK message to the calling terminal device; correspondingly, the calling terminal device receives the INVITE 200 OK message from the called terminal device.

[0314] For example, the INVITE 200 OK message sent by the called-side terminal device passes through the called-side IMS network element and the calling-side IMS network element in sequence to reach the calling-side terminal device.

[0315] S1015, The calling terminal device sends an ACK message to the called terminal device; correspondingly, the called terminal device receives the ACK message from the calling terminal device.

[0316] Specifically, the ACK message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0317] As another example, the first IMS network element can send a third message after receiving the second and seventh messages. The seventh message indicates that the called party's terminal device has been ringing. For example, the seventh message can be a 180-ring message; in this case, it can also be considered that the first IMS network element generates or sends the third message after receiving the 180-ring message from the called party's terminal device.

[0318] For example, in this example, step S404 can be replaced by: after step S403 and upon receiving the seventh message, the first IMS network element generates the third message. For instance, after step S403 and upon receiving the seventh message, the first IMS network element can add second media response information to the seventh message (i.e., the 180-ring message) to obtain the third message.

[0319] Optionally, in this example, after the calling terminal device receives a message (such as a third message or message #4) indicating that the second terminal device has been ringing and carrying second media response information, it can send a PRACK message to the first IMS network element to confirm that it has received the second media response information. Specifically, the implementation of the calling terminal device sending a PRACK message to the first IMS network element can be found in the relevant description in the foregoing embodiments, and will not be repeated here.

[0320] Furthermore, the calling terminal device can also send an UPDATA message to the first IMS network element to indicate that the call resource reservation for the calling terminal device has been successful. Specifically, the implementation of the calling terminal device sending an UPDATA message to the first IMS network element is similar to the implementation of sending a PRACK message to the first IMS network element described above. For details, please refer to the relevant description of the calling terminal device sending a PRACK message to the first IMS network element, which will not be repeated here.

[0321] For example, the calling terminal device sends a PRACK message and an UPDATA message to the first IMS network element, respectively. Alternatively, the calling terminal device can use a signaling message (such as the eighth message) to indicate that it has received the second media response information and that the call resource reservation for the calling terminal device has been successful. When the first device is the calling terminal device and the first IMS network element is the calling IMS network element, the calling terminal device can directly send the eighth message to the first IMS network element. The eighth message is used to indicate that the calling terminal device has received the second media response information and that the call resource reservation for the calling terminal device has been successful. Specifically, the implementation of the message (such as the eighth message) sent by the calling terminal device to the first IMS network element to indicate that it has received the second media response information and that the call resource reservation for the calling terminal device has been successful can be found in the aforementioned description of the eighth message, and will not be repeated here.

[0322] Optionally, the UPDATA message sent by the first IMS network element to the called terminal device as described in the above embodiments can also be referred to as the ninth message. For example, in this example, if the first IMS network element is the calling side IMS network element, the calling side IMS network element can send the UPDATA message after it has learned that the call resource reservation for the calling side terminal device has been successful; for example, the calling side IMS network element can learn from the calling side core network device that the call bearer for the calling side terminal device has been established, thereby knowing that the call resource reservation for the calling side terminal device has been successful.

[0323] Specifically, after receiving the 183 session progress message, the calling side IMS network element can send a message to the calling side core network device so that the calling side core network device can establish the call bearer of the calling side terminal device. After the establishment, the calling side core network device can report to the calling side IMS network element that the call bearer of the calling side terminal device has been established, so that the calling side IMS network element knows that the call resource reservation of the calling side terminal device has been successful.

[0324] If the first IMS network element is the called party's IMS network element, it can learn from the calling party's IMS network element that the call resource reservation for the calling terminal device has been successful. Alternatively, the called party's IMS network element may not actually know whether the call resource reservation for the calling terminal device has been successful, but instead sends a false UPDATA message to the called party's terminal device. Since the first IMS network element interacts with the called party's terminal device as a B2B UA, the called party's terminal device considers the called party's IMS network element to be the calling party's device (such as the calling party's terminal device). Therefore, after receiving the UPDATA message, the called party's terminal device considers the call resource reservation for the calling party's terminal device to be successful. Specifically, the implementation of the calling party's IMS network element knowing that the call resource reservation for the calling party's terminal device has been successful can be found in the relevant description in the foregoing embodiments, and will not be repeated here.

[0325] Furthermore, in this example, after the called-side terminal device sends a 180ring message to the first IMS network element, it can also send an INVITE 200 OK message (or, it can also be called a 200 OK INVITE message) to the calling-side terminal device; so that the calling-side terminal device can send an ACK message to the called-side terminal device; thereby realizing the call between the calling-side terminal device and the called-side terminal device.

[0326] The following example illustrates the calling method described in this application embodiment, where the first message is an INVITE message, the second message is a 183 session progress message, the third message is a 180 ring message, the fourth message is an INVITE message, the sixth message is a PRACK message, the eighth message is a PRACK message, the ninth message is an UPDATA message, the first and second media response information are both SDP answers, and the media request information is an SDP offer. For example, in this example, the calling method can be implemented based on the following two scenarios:

[0327] Scenario 1: The first IMS network element is the calling side IMS network element, the first device is the calling side terminal device, and the second device is the called side IMS device. Referring to Figure 11, another possible implementation of the calling method described in this application is shown. This calling method may include the following steps:

[0328] S1101, the calling terminal device sends an INVITE message to the called terminal device; correspondingly, the called terminal device receives the INVITE message from the calling terminal device. The INVITE message is used by the calling terminal device to call the called terminal device, and the INVITE message includes an SDP offer.

[0329] Specifically, the INVITE message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0330] For example, after the calling IMS network element receives the INVITE message, it can also send a 100 Trying message back to the calling terminal device. That is, the calling IMS network element can execute step S1102:

[0331] S1102, The calling side IMS network element sends a 100 Trying message to the calling side terminal device; correspondingly, the calling side terminal device receives the 100 Trying message from the calling side IMS network element. The 100 Trying message is used to confirm that the calling side IMS network element has received the INVITE message sent by the calling side terminal device.

[0332] S1103, the called-side terminal device sends a 183 session progress message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the 183 session progress message from the called-side terminal device. The 183 session progress message carries the SDP answer.

[0333] Specifically, the 183 session progress message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0334] S1104. The calling side IMS network element determines the simplified process executed by the calling side.

[0335] The implementation of step S1104 is similar to that of step S904. For details, please refer to the relevant description of step S904, which will not be repeated here.

[0336] S1105, The calling IMS network element sends a PRACK message to the called terminal device; correspondingly, the called terminal device receives the PRACK message from the calling IMS network element. The PRACK message indicates that the calling IMS network element has received the SDP answer.

[0337] For example, the PRACK message sent by the calling side IMS network element reaches the called side terminal device through the called side IMS network element.

[0338] S1106. The called-side terminal device sends a PRACK 200 OK message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the PRACK 200 OK message from the called-side terminal device. The PRACK 200 OK message indicates that the called-side terminal device has received the PRACK message.

[0339] For example, the PRACK 200 OK message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0340] S1107. The calling side IMS network element sends an UPDATA message to the called side terminal device; correspondingly, the called side terminal device receives the UPDATA message from the calling side IMS network element. The UPDATA message indicates that the call resources reservation for the calling side terminal device has been successful.

[0341] For example, the PRACK message sent by the calling side IMS network element reaches the called side terminal device through the called side IMS network element.

[0342] For example, the calling side IMS network element learns from the calling side core network equipment that the calling side terminal equipment has successfully reserved call resources, and then executes step S1107.

[0343] S1108. The called-side terminal device sends an UPDATA 200 OK message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the UPDATA 200 OK message from the called-side terminal device. The UPDATA 200 OK message indicates that the called-side terminal device has successfully reserved call resources.

[0344] For example, the UPDATA 200 OK message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0345] S1109. The called-side terminal device sends a 180-ring message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the 180-ring message from the called-side terminal device.

[0346] For example, a 180-ring message sent by the called-side terminal device reaches the calling-side IMS network element via the called-side IMS network element.

[0347] S1110, the calling side IMS network element generates a new 180ring message. This new 180ring message carries the SDP answer. For example, adding the SDP answer to a 180ring message results in a new 180ring message.

[0348] S1111, The calling side IMS network element sends a new 180ring message to the calling side terminal equipment; correspondingly, the calling side terminal equipment receives the new 180ring message from the calling side IMS network element.

[0349] S1112. The calling terminal device sends a PRACK message to the calling IMS network element; correspondingly, the calling IMS network element receives the PRACK message from the host terminal device. The PRACK message indicates that the calling terminal device has received the SDP answer. Furthermore, the PRACK message can also indicate that the calling terminal device has successfully reserved call resources.

[0350] S1113. The calling side IMS network element sends a PRACK 200 OK message to the calling side terminal equipment; correspondingly, the calling side terminal equipment receives the PRACK 200 OK message from the calling side IMS network element. The PRACK 200 OK message indicates that the calling side IMS network element has received the PRACK message.

[0351] Optionally, if the PRACK message in S1112 does not indicate that the call resource reservation for the calling terminal device is successful, the calling terminal device must also send an UPDATA message to the calling IMS network element after it learns that the call resource reservation for the calling terminal device is successful, to inform the calling IMS network element that the call resource reservation for the calling terminal device is successful. Furthermore, the calling IMS network element can send an UPDATA 200 OK message back to the calling terminal device to inform it that it has received the UPDATA message.

[0352] S1114. The called terminal device sends an INVITE 200 OK message to the calling terminal device; correspondingly, the calling terminal device receives the INVITE 200 OK message from the called terminal device.

[0353] For example, the INVITE 200 OK message sent by the called-side terminal device passes through the called-side IMS network element and the calling-side IMS network element in sequence to reach the calling-side terminal device.

[0354] S1115. The calling terminal device sends an ACK message to the called terminal device; correspondingly, the called terminal device receives the ACK message from the calling terminal device.

[0355] Specifically, the ACK message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0356] Scenario 2: The first IMS network element is the called side IMS network element, the first device is the calling side IMS network element, and the second device is the called side terminal device. Referring to Figure 12, another possible implementation of the calling method described in this application is shown. This calling method may include the following steps:

[0357] S1201, the calling terminal device sends an INVITE message to the called terminal device; correspondingly, the called terminal device receives the INVITE message from the calling terminal device. The INVITE message is used by the calling terminal device to call the called terminal device, and the INVITE message includes an SDP offer.

[0358] Specifically, the INVITE message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0359] For example, after the calling side IMS network element receives the INVITE message, it can also send a 100 Trying message back to the calling side terminal device. That is, the calling side IMS network element can execute step S1202:

[0360] S1202, The calling side IMS network element sends a 100 Trying message to the calling side terminal device; correspondingly, the calling side terminal device receives the 100 Trying message from the calling side IMS network element. The 100 Trying message is used to confirm that the calling side IMS network element has received the INVITE message sent by the calling side terminal device.

[0361] S1203, the called-side terminal device sends a 183 session progress message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the 183 session progress message from the called-side terminal device. The 183 session progress message carries the SDP answer.

[0362] Specifically, the 183 session progress message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0363] S1204. The called party's IMS network element determines the simplified process executed by the calling party.

[0364] The implementation of step S1204 is similar to that of step S1004. For details, please refer to the relevant description of step S904, which will not be repeated here.

[0365] S1205, the called-side IMS network element sends a PRACK message to the called-side terminal device; correspondingly, the called-side terminal device receives the PRACK message from the called-side IMS network element. The PRACK message indicates that the calling side has received the SDP answer.

[0366] In step S1205, since the called side IMS network element interacts with the called side terminal device as a B2B UA, the called side terminal device considers the called side IMS network element to be the calling side device (such as the calling side terminal device). Therefore, after receiving the PRACK message, the called side terminal device considers that the calling side has received the SDP answer.

[0367] S1206. The called-side terminal device sends a PRACK 200 OK message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the PRACK 200 OK message from the called-side terminal device. The PRACK 200 OK message indicates that the called-side terminal device has received the PRACK message.

[0368] S1207. The called party's IMS network element sends an UPDATA message to the called party's terminal device; correspondingly, the called party's terminal device receives the UPDATA message from the called party's IMS network element. The UPDATA message indicates that the call resources reserved by the calling party's terminal device have been successfully reserved.

[0369] Specifically, the called side IMS network element can learn from the calling side IMS network element that the call resources of the calling side terminal device have been successfully reserved; or, the called side IMS network element may not know whether the call resources of the calling side terminal device have been successfully reserved, but in order to complete the standard procedure between it and the called side terminal device, it can send the UPDATA message to the called side terminal device.

[0370] In step S1207, since the called side IMS network element interacts with the called side terminal device as a B2B UA, the called side terminal device considers the called side IMS network element to be the calling side device (such as the calling side terminal device). Therefore, after receiving the UPDATA message, the called side terminal device considers that the call resources of the calling side terminal device have been successfully reserved.

[0371] S1208, the called-side terminal device sends an UPDATA 200 OK message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the UPDATA 200 OK message from the called-side terminal device. The UPDATA 200 OK message indicates that the called-side terminal device has successfully reserved call resources.

[0372] S1209. The called-side terminal device sends a 180-ring message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the 180-ring message from the called-side terminal device.

[0373] S1210, The called party's IMS network element generates a new 180ring message. This new 180ring message carries the SDP answer. For example, adding the SDP answer to a 180ring message results in a new 180ring message.

[0374] S1211, The called side IMS network element sends a new 180ring message to the calling side terminal equipment; correspondingly, the calling side terminal equipment receives the new 180ring message from the called side IMS network element.

[0375] S1212, the calling terminal device sends a PRACK message to the called IMS network element; correspondingly, the called IMS network element receives the PRACK message from the host terminal device. The PRACK message indicates that the calling terminal device has received the SDP answer; furthermore, the PRACK message can also indicate that the calling terminal device has successfully reserved call resources.

[0376] Specifically, the PRACK message sent by the calling terminal device reaches the called IMS network element through the calling IMS network element.

[0377] S1213. The called party's IMS network element sends a PRACK 200 OK message to the calling party's terminal equipment; correspondingly, the calling party's terminal equipment receives the PRACK 200 OK message from the called party's IMS network element. The PRACK 200 OK message indicates that the called party's IMS network element has received the PRACK message.

[0378] Specifically, the PRACK 200 OK message sent by the called side IMS network element reaches the calling side terminal device through the calling side IMS network element.

[0379] Optionally, if the PRACK message in S1212 does not indicate that the call resource reservation for the calling terminal device is successful, the calling terminal device must also send an UPDATA message to the called IMS network element after it learns that the call resource reservation for the calling terminal device is successful, to inform the calling IMS network element that the call resource reservation for the calling terminal device is successful. Furthermore, the called IMS network element can send an UPDATA 200 OK message back to the calling terminal device to inform it that it has received the UPDATA message.

[0380] S1214. The called terminal device sends an INVITE 200 OK message to the calling terminal device; correspondingly, the calling terminal device receives the INVITE 200 OK message from the called terminal device.

[0381] For example, the INVITE 200 OK message sent by the called-side terminal device passes through the called-side IMS network element and the calling-side IMS network element in sequence to reach the calling-side terminal device.

[0382] S1215, The calling terminal device sends an ACK message to the called terminal device; correspondingly, the called terminal device receives the ACK message from the calling terminal device.

[0383] Specifically, the ACK message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0384] In another possible implementation, the third message does not contain the second media response information. That is, the message used to indicate that the called terminal device has been ringing does not carry the second media response information.

[0385] For example, the implementation of the second media response information can be found in the relevant descriptions in the above embodiments, and will not be repeated here. Optionally, in this possible implementation, if the first device is a calling side IMS network element, after receiving the third message from the first IMS network element, the first device also needs to send the information carried by the third message to the calling side terminal device; for example, the calling side IMS network element can directly forward the third message to the calling side terminal device, or the calling side IMS network element can generate message #6 according to the third message and send message #6 to the calling side terminal device. Message #6 is used to indicate that the second terminal device has been ringing.

[0386] Optionally, in this possible implementation, the second media response information can be carried in the tenth message; wherein the tenth message is used to instruct the called terminal device to respond to the call request of the calling terminal device, and the tenth message also includes the second media response information. For example, the tenth message can be an INVITE 200 OK message.

[0387] Specifically, after the first IMS network element sends the third message, the called terminal device can also send message #7 to the first IMS network element to instruct the called terminal device to respond to the call request of the calling terminal device. Then, the first IMS network element can generate a tenth message based on message #7 and send the tenth message to the first device. If the first device is the calling IMS network element, it also needs to send a message instructing the called terminal device to respond to the call request of the calling terminal device, carrying second media response information, to the calling terminal device, so that the calling terminal device can obtain the second media response information. Then, the calling terminal device can send an ACK message to the called terminal device to establish a call between the calling and called terminal devices. For example, the called terminal device can send the tenth message after receiving a message from the first IMS network element confirming that the first IMS network element has received the first media response information (i.e., the sixth message, such as a PRACK message).

[0388] Optionally, the UPDATA message sent by the first IMS network element to the called terminal device as described in the above embodiments can also be referred to as the ninth message. For example, in this example, if the first IMS network element is the calling side IMS network element, the calling side IMS network element can send the UPDATA message after it has learned that the call resource reservation for the calling side terminal device has been successful; for example, the calling side IMS network element can learn from the calling side core network device that the call bearer for the calling side terminal device has been established, thereby knowing that the call resource reservation for the calling side terminal device has been successful.

[0389] Specifically, after receiving the 183 session progress message, the calling IMS network element can send a message to the calling core network device to enable the calling core network device to establish the call bearer for the calling terminal device. After establishment, the calling core network device can report to the calling IMS network element that the call bearer for the calling terminal device has been established, so that the calling IMS network element knows that the call resource reservation for the calling terminal device has been successful. Alternatively, after receiving the INVITE message from the calling terminal device, the calling IMS network element, based on the calling terminal device's narrowband high-orbit satellite access (because this access method only supports low bit rate voice encoding format, it is not necessary to wait for the called party's response message, i.e., there is no need to negotiate with the called party's terminal device; the calling IMS network element and the calling terminal device negotiate the low bit rate voice encoding format, which triggers the establishment of the voice call bearer), sends a message to the calling core network device to enable the calling core network device to establish the call bearer for the calling terminal device in advance.

[0390] If the first IMS network element is the called party's IMS network element, it can learn from the calling party's IMS network element that the call resources for the calling terminal device have been successfully reserved. Alternatively, the called party's IMS network element may not actually know whether the call resources for the calling terminal device have been successfully reserved, but instead sends a false UPDATA message to the called party's terminal device. Since the first IMS network element interacts with the called party's terminal device as a B2B UA, the called party's terminal device considers the called party's IMS network element to be the calling party's device (such as the calling party's terminal device). Therefore, after receiving the UPDATA message, the called party's terminal device considers the call resources for the calling party's terminal device to have been successfully reserved.

[0391] Specifically, the implementation of the calling side IMS network element knowing that the calling side terminal device has successfully reserved call resources can be found in the relevant description in the aforementioned embodiments, and will not be repeated here.

[0392] Furthermore, after the called terminal device sends a 180 ring message to the first IMS network element, it can also send an INVITE 200 OK message (or, it can also be called a 200 OK INVITE message) to the calling terminal device; so that the calling terminal device can send an ACK message to the called terminal device; thereby realizing the call between the calling terminal device and the called terminal device.

[0393] As an example, the first IMS network element can generate and send the third message after receiving the second message without waiting for a 180ring message from the called party's terminal device. That is, the first IMS network element can directly execute steps S404 to S405 after steps S402 to S403.

[0394] The following example illustrates the calling method described in this application embodiment, where the first message is an INVITE message, the second message is a 183 session progress message, the third message is a 180 ring message, the fourth message is an INVITE message, the sixth message is a PRACK message, the tenth message is an INVITE 200 OK message, the first and second media response information are both SDP answer, and the media request information is an SDP offer. For example, in this example, the calling method can be implemented based on the following two scenarios:

[0395] Scenario 1: The first IMS network element is the calling side IMS network element, the first device is the calling side terminal device, and the second device is the called side IMS device. Referring to Figure 13, another possible implementation of the calling method described in this application is shown. This calling method may include the following steps:

[0396] S1301, the calling terminal device sends an INVITE message to the called terminal device; correspondingly, the called terminal device receives the INVITE message from the calling terminal device. The INVITE message is used by the calling terminal device to call the called terminal device, and the INVITE message includes an SDP offer.

[0397] Specifically, the INVITE message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0398] For example, after the calling IMS network element receives the INVITE message, it can also send a 100 Trying message back to the calling terminal device. That is, the calling IMS network element can execute step S1302:

[0399] S1302, The calling side IMS network element sends a 100 Trying message to the calling side terminal device; correspondingly, the calling side terminal device receives the 100 Trying message from the calling side IMS network element. The 100 Trying message is used to confirm that the calling side IMS network element has received the INVITE message sent by the calling side terminal device.

[0400] S1303, the called-side terminal device sends a 183 session progress message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the 183 session progress message from the called-side terminal device. The 183 session progress message carries the SDP answer.

[0401] Specifically, the 183 session progress message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0402] S1304. The calling side IMS network element determines the simplified process executed by the calling side.

[0403] The implementation of step S1304 can be found in the description of step S904 above, and will not be repeated here.

[0404] S1305, The calling side IMS network element generates a 180-ring message.

[0405] S1306, The calling side IMS network element sends a 180-ring message to the calling side terminal device; correspondingly, the calling side terminal device receives the 180-ring message from the calling side IMS network element.

[0406] Optionally, after step S1303, the calling method further includes the following steps:

[0407] S1307. The calling IMS network element sends a PRACK message to the called terminal device; correspondingly, the called terminal device receives the PRACK message from the calling IMS network element. The PRACK message indicates that the calling IMS network element has received the SDP answer.

[0408] For example, the PRACK message sent by the calling side IMS network element reaches the called side terminal device through the called side IMS network element.

[0409] It should be noted that this application does not limit the order of steps S1307 and S1304 to S1306; for example, step S1307 may be performed before steps S1304 to S1306, or step S1307 may be performed after steps S1304 to S1306, or step S1307 may be performed simultaneously with steps S1304 to S1306.

[0410] S1308, the called-side terminal device sends a PRACK 200 OK message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the PRACK 200 OK message from the called-side terminal device. The PRACK 200 OK message indicates that the called-side terminal device has received the PRACK message.

[0411] For example, the PRACK 200 OK message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0412] S1309. The calling side IMS network element sends an UPDATA message to the called side terminal device; correspondingly, the called side terminal device receives the UPDATA message from the calling side IMS network element. The UPDATA message indicates that the call resources reservation for the calling side terminal device has been successful.

[0413] For example, the calling side IMS network element can learn from the calling side core network equipment that the call bearer of the calling side terminal equipment has been established, thereby knowing that the call resource reservation of the calling side terminal equipment has been successful.

[0414] Specifically, after receiving the 183 session progress message, the calling IMS network element can send a message to the calling core network device to enable the calling core network device to establish the call bearer for the calling terminal device. After establishment, the calling core network device can report to the calling IMS network element that the call bearer for the calling terminal device has been established, so that the calling IMS network element knows that the call resource reservation for the calling terminal device has been successful. Alternatively, after receiving the INVITE message from the calling terminal device, the calling IMS network element, based on the calling terminal device's narrowband high-orbit satellite access (because this access method only supports low bit rate voice encoding format, it is not necessary to wait for the called party's response message, i.e., there is no need to negotiate with the called party's terminal device; the calling IMS network element and the calling terminal device negotiate the low bit rate voice encoding format, which triggers the establishment of the voice call bearer), sends a message to the calling core network device to enable the calling core network device to establish the call bearer for the calling terminal device in advance.

[0415] S1310, the called-side terminal device sends an UPDATA 200 OK message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the UPDATA 200 OK message from the called-side terminal device. The UPDATA 200 OK message indicates that the called-side terminal device has successfully reserved call resources.

[0416] For example, the UPDATA 200 OK message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0417] S1311, The called-side terminal device sends a 180-ring message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the 180-ring message from the called-side terminal device.

[0418] For example, a 180-ring message sent by the called-side terminal device reaches the calling-side IMS network element via the called-side IMS network element.

[0419] S1312, The called-side terminal device sends an INVITE 200 OK message to the calling-side IMS network element; correspondingly, the calling-side terminal device receives the INVITE 200 OK message from the called-side terminal device.

[0420] For example, the INVITE 200 OK message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0421] S1313, The calling side IMS network element generates a new INVITE 200 OK message, which carries the SDP answer.

[0422] For example, the calling side IMS network element adds an SDP answer to the INVITE 200 OK message received in step S1312 to obtain a new INVITE 200 OK message.

[0423] S1314. The calling side IMS network element sends a new INVITE 200 OK message to the calling side terminal device; correspondingly, the calling side terminal device receives the new INVITE 200 OK message from the calling side IMS network element.

[0424] S1315, The calling terminal device sends an ACK message to the called terminal device; correspondingly, the called terminal device receives the ACK message from the calling terminal device.

[0425] Specifically, the ACK message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0426] Scenario 2: The first IMS network element is the called side IMS network element, the first device is the calling side IMS network element, and the second device is the called side terminal device. Referring to Figure 14, another possible implementation of the calling method described in this application is shown. This calling method may include the following steps:

[0427] S1401, the calling terminal device sends an INVITE message to the called terminal device; correspondingly, the called terminal device receives the INVITE message from the calling terminal device. The INVITE message is used by the calling terminal device to call the called terminal device, and the INVITE message includes an SDP offer.

[0428] Specifically, the INVITE message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0429] For example, after the calling IMS network element receives the INVITE message, it can also send a 100 Trying message back to the calling terminal device. That is, the calling IMS network element can execute step S1402:

[0430] S1402, The calling side IMS network element sends a 100 Trying message to the calling side terminal device; correspondingly, the calling side terminal device receives the 100 Trying message from the calling side IMS network element. The 100 Trying message is used to confirm that the calling side IMS network element has received the INVITE message sent by the calling side terminal device.

[0431] S1403, the called-side terminal device sends a 183 session progress message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the 183 session progress message from the called-side terminal device. The 183 session progress message carries the SDP answer.

[0432] Specifically, the 183 session progress message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0433] S1404. The called party's IMS network element determines the simplified process executed by the calling party.

[0434] The implementation of step S1404 is similar to that of step S1004. For details, please refer to the relevant description of step S1004 above, which will not be repeated here.

[0435] S1405, The called side IMS network element generates a 180-ring message.

[0436] S1406, The called side IMS network element sends a 180-ring message to the calling side terminal equipment; correspondingly, the calling side terminal equipment receives the 180-ring message from the called side IMS network element.

[0437] Specifically, the 180-ring message sent by the called side IMS network element reaches the calling side terminal device through the calling side IMS network element.

[0438] S1407. The called party's IMS network element sends a PRACK message to the called party's terminal equipment; correspondingly, the called party's terminal equipment receives the PRACK message from the called party's IMS network element. The PRACK message indicates that the calling party has received the SDP answer.

[0439] It should be noted that this application does not limit the order of steps S1407 and S1404 to S1406; for example, step S1407 may be performed before steps S1404 to S1406, or step S1407 may be performed after steps S1404 to S1406, or step S1407 may be performed simultaneously with steps S1404 to S1406.

[0440] In step S1407, since the called side IMS network element interacts with the called side terminal device as a B2B UA, the called side terminal device considers the called side IMS network element to be the calling side device (such as the calling side terminal device). Therefore, after receiving the PRACK message, the called side terminal device considers that the calling side has received the SDP answer.

[0441] S1408. The called-side terminal device sends a PRACK 200 OK message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the PRACK 200 OK message from the called-side terminal device. The PRACK 200 OK message indicates that the called-side terminal device has received the PRACK message. S1409. The called-side IMS network element sends an UPDATA message to the called-side terminal device; correspondingly, the called-side terminal device receives the UPDATA message from the called-side IMS network element. The UPDATA message indicates that the calling-side terminal device has successfully reserved call resources.

[0442] For example, the called-side IMS network element can learn from the calling-side IMS network element that the call resources of the calling-side terminal device have been successfully reserved. Alternatively, the called-side IMS network element may not actually know whether the call resources of the calling-side terminal device have been successfully reserved, but instead send a fake UPDATA message to the called-side terminal device. Since the first IMS network element interacts with the called-side terminal device as a B2B UA, the called-side terminal device considers the called-side IMS network element to be the calling-side device (such as the calling-side terminal device). Therefore, after receiving the UPDATA message, the called-side terminal device considers that the call resources of the calling-side terminal device have been successfully reserved.

[0443] Specifically, the implementation of the calling side IMS network element knowing that the calling side terminal device has successfully reserved call resources can be found in the relevant description in the aforementioned embodiments, and will not be repeated here.

[0444] S1410, the called-side terminal device sends an UPDATA 200 OK message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the UPDATA 200 OK message from the called-side terminal device. The UPDATA 200 OK message indicates that the called-side terminal device has successfully reserved call resources.

[0445] S1411, The called-side terminal device sends a 180-ring message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the 180-ring message from the called-side terminal device.

[0446] S1412, The called-side terminal device sends an INVITE 200 OK message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the INVITE 200 OK message from the called-side terminal device.

[0447] S1413. The called party's IMS network element generates a new INVITE 200 OK message, which carries the SDP answer.

[0448] For example, the called-side IMS network element adds an SDP answer to the INVITE 200 OK message to obtain a new INVITE 200 OK message.

[0449] S1414, The called side IMS network element sends a new INVITE 200 OK message to the calling side terminal equipment; correspondingly, the calling side terminal equipment receives the new INVITE 200 OK message from the called side IMS network element.

[0450] For example, the INVITE 200 OK message sent by the called-side terminal device passes through the called-side IMS network element and the calling-side IMS network element in sequence to reach the calling-side terminal device.

[0451] S1415, The calling terminal device sends an ACK message to the called terminal device; correspondingly, the called terminal device receives the ACK message from the calling terminal device.

[0452] Specifically, the ACK message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0453] As another example, the first IMS network element can send a third message after receiving the second and seventh messages. The seventh message indicates that the called party's terminal device has been ringing. For example, the seventh message can be a 180-ring message; in this case, it can also be considered that the first IMS network element generates or sends the third message after receiving the 180-ring message from the called party's terminal device.

[0454] For example, in this example, step S404 can be replaced by: after step S403 and upon receiving the seventh message, the first IMS network element generates the third message. For example, if the seventh message is the same as the third message, the IMS directly uses the seventh message as the third message. Alternatively, if the seventh message is different from the third message, the first IMS network element can process the seventh message (e.g., modify or adjust it) to obtain the third message.

[0455] Optionally, the UPDATA message sent by the first IMS network element to the called terminal device as described in the above embodiments can also be referred to as the ninth message. For example, in this example, if the first IMS network element is the calling side IMS network element, the calling side IMS network element can send the UPDATA message after it has learned that the call resource reservation for the calling side terminal device has been successful; for example, the calling side IMS network element can learn from the calling side core network device that the call bearer for the calling side terminal device has been established, thereby knowing that the call resource reservation for the calling side terminal device has been successful.

[0456] Specifically, after receiving the 183 session progress message, the calling side IMS network element can send a message to the calling side core network device so that the calling side core network device can establish the call bearer of the calling side terminal device. After the establishment, the calling side core network device can report to the calling side IMS network element that the call bearer of the calling side terminal device has been established, so that the calling side IMS network element knows that the call resource reservation of the calling side terminal device has been successful.

[0457] If the first IMS network element is the called side IMS network element, the first IMS network element can learn from the calling side IMS network element that the call resources of the calling side terminal device have been successfully reserved; or, the called side IMS network element does not actually know whether the call resources of the calling side terminal device have been successfully reserved, but sends a fake UPDATA message to the called side terminal device; since the first IMS network element interacts with the called side terminal device as a B2B UA, the called side terminal device regards the called side IMS network element as the calling side device (such as the calling side terminal device), and thus after receiving the UPDATA message, the called side terminal device regards the call resources of the calling side terminal device as successfully reserved.

[0458] Specifically, the implementation of the calling side IMS network element knowing that the calling side terminal device has successfully reserved call resources can be found in the relevant description in the aforementioned embodiments, and will not be repeated here.

[0459] Furthermore, in this example, after the called-side terminal device sends a 180ring message to the first IMS network element, it can also send an INVITE 200 OK message (or, it can also be called a 200 OK INVITE message) to the calling-side terminal device; so that the calling-side terminal device can send an ACK message to the called-side terminal device; thereby realizing the call between the calling-side terminal device and the called-side terminal device.

[0460] The following example illustrates the calling method described in this application embodiment, where the first message is an INVITE message, the second message is a 183 session progress message, the third message is a 180 ring message, the fourth message is an INVITE message, the sixth message is a PRACK message, the tenth message is an INVITE 200 OK message, the first and second media response information are both SDP answer, and the media request information is an SDP offer. For example, in this example, the calling method can be implemented based on the following two scenarios:

[0461] Scenario 1: The first IMS network element is the calling side IMS network element, the first device is the calling side terminal device, and the second device is the called side IMS device. Referring to Figure 15, another possible implementation of the calling method described in this application is shown. This calling method may include the following steps:

[0462] S1501, the calling terminal device sends an INVITE message to the called terminal device; correspondingly, the called terminal device receives the INVITE message from the calling terminal device. The INVITE message is used by the calling terminal device to call the called terminal device, and the INVITE message includes an SDP offer.

[0463] Specifically, the INVITE message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0464] For example, after the calling side IMS network element receives the INVITE message, it can also send a 100 Trying message back to the calling side terminal device. That is, the calling side IMS network element can execute step S1502:

[0465] S1502, The calling side IMS network element sends a 100 Trying message to the calling side terminal device; correspondingly, the calling side terminal device receives the 100 Trying message from the calling side IMS network element. The 100 Trying message is used to confirm that the calling side IMS network element has received the INVITE message sent by the calling side terminal device.

[0466] S1503, the called-side terminal device sends a 183 session progress message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the 183 session progress message from the called-side terminal device. The 183 session progress message carries the SDP answer.

[0467] Specifically, the 183 session progress message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0468] S1504. The calling side IMS network element determines the simplified process executed by the calling side.

[0469] The implementation of step S1504 is similar to that of step S904. For details, please refer to the relevant description of step S904, which will not be repeated here.

[0470] S1505, the calling IMS network element sends a PRACK message to the called terminal device; correspondingly, the called terminal device receives the PRACK message from the calling IMS network element. The PRACK message indicates that the calling IMS network element has received the SDP answer.

[0471] For example, the PRACK message sent by the calling side IMS network element reaches the called side terminal device through the called side IMS network element.

[0472] S1506, the called-side terminal device sends a PRACK 200 OK message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the PRACK 200 OK message from the called-side terminal device. The PRACK 200 OK message indicates that the called-side terminal device has received the PRACK message.

[0473] For example, the PRACK 200 OK message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0474] S1507. The calling IMS network element sends an UPDATA message to the called terminal device; correspondingly, the called terminal device receives the UPDATA message from the calling IMS network element. The UPDATA message indicates that the call resources reserved by the calling terminal device have been successfully reserved.

[0475] For example, the PRACK message sent by the calling side IMS network element reaches the called side terminal device through the called side IMS network element.

[0476] For example, the calling side IMS network element can learn from the calling side core network equipment that the call bearer of the calling side terminal equipment has been established, thereby knowing that the call resource reservation of the calling side terminal equipment has been successful.

[0477] Specifically, after receiving the 183 session progress message, the calling IMS network element can send a message to the calling core network device to enable the calling core network device to establish the call bearer for the calling terminal device. After establishment, the calling core network device can report to the calling IMS network element that the call bearer for the calling terminal device has been established, so that the calling IMS network element knows that the call resource reservation for the calling terminal device has been successful. Alternatively, after receiving the INVITE message from the calling terminal device, the calling IMS network element, based on the calling terminal device's narrowband high-orbit satellite access (because this access method only supports low bit rate voice encoding format, it is not necessary to wait for the called party's response message, i.e., there is no need to negotiate with the called party's terminal device; the calling IMS network element and the calling terminal device negotiate the low bit rate voice encoding format, which triggers the establishment of the voice call bearer), sends a message to the calling core network device to enable the calling core network device to establish the call bearer for the calling terminal device in advance.

[0478] S1508, the called-side terminal device sends an UPDATA 200 OK message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the UPDATA 200 OK message from the called-side terminal device. The UPDATA 200 OK message indicates that the called-side terminal device has successfully reserved call resources.

[0479] For example, the UPDATA 200 OK message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0480] S1509, The called-side terminal device sends a 180-ring message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the 180-ring message from the called-side terminal device.

[0481] For example, a 180-ring message sent by the called-side terminal device reaches the calling-side IMS network element via the called-side IMS network element.

[0482] S1510, The calling side IMS network element sends a 180-ring message to the calling side terminal device; correspondingly, the calling side terminal device receives the 180-ring message from the calling side IMS network element.

[0483] For example, step S1510 is performed after step S1509.

[0484] S1511, The called-side terminal device sends an INVITE 200 OK message to the calling-side IMS network element; correspondingly, the calling-side terminal device receives the INVITE 200 OK message from the called-side terminal device.

[0485] For example, the INVITE 200 OK message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0486] S1512. The calling side IMS network element generates a new INVITE 200 OK message, which carries the SDP answer.

[0487] For example, the calling IMS network element adds an SDP answer to the INVITE 200 OK message it receives, thus obtaining a new INVITE 200 OK message.

[0488] S1513, The calling side IMS network element sends a new INVITE 200 OK message to the calling side terminal device; correspondingly, the calling side terminal device receives the new INVITE 200 OK message from the calling side IMS network element.

[0489] S1514. The calling terminal device sends an ACK message to the called terminal device; correspondingly, the called terminal device receives the ACK message from the calling terminal device.

[0490] Specifically, the ACK message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0491] Scenario 2: The first IMS network element is the called side IMS network element, the first device is the calling side IMS network element, and the second device is the called side terminal device. Referring to Figure 16, another possible implementation of the calling method described in this application is shown. This calling method may include the following steps:

[0492] S1601, the calling terminal device sends an INVITE message to the called terminal device; correspondingly, the called terminal device receives the INVITE message from the calling terminal device. The INVITE message is used by the calling terminal device to call the called terminal device, and the INVITE message includes an SDP offer.

[0493] Specifically, the INVITE message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0494] For example, after the calling side IMS network element receives the INVITE message, it can also send a 100 Trying message back to the calling side terminal device. That is, the calling side IMS network element can execute step S1602:

[0495] S1602, The calling side IMS network element sends a 100 Trying message to the calling side terminal device; correspondingly, the calling side terminal device receives the 100 Trying message from the calling side IMS network element. The 100 Trying message is used to confirm that the calling side IMS network element has received the INVITE message sent by the calling side terminal device.

[0496] S1603, the called-side terminal device sends a 183 session progress message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the 183 session progress message from the called-side terminal device. The 183 session progress message carries the SDP answer.

[0497] S1604. The called party's IMS network element determines the simplified process executed by the calling party.

[0498] The implementation of step S1604 is similar to that of step S1004. For details, please refer to the relevant description of step S904, which will not be repeated here.

[0499] S1605, The called party's IMS network element sends a PRACK message to the called party's terminal equipment; correspondingly, the called party's terminal equipment receives the PRACK message from the called party's IMS network element. The PRACK message indicates that the calling party has received the SDP answer.

[0500] In step S1605, since the called side IMS network element interacts with the called side terminal device as a B2B UA, the called side terminal device considers the called side IMS network element to be the calling side device (such as the calling side terminal device). Therefore, after receiving the PRACK message, the called side terminal device considers that the calling side has received the SDP answer.

[0501] S1606, The called-side terminal device sends a PRACK 200 OK message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the PRACK 200 OK message from the called-side terminal device. The PRACK 200 OK message indicates that the called-side terminal device has received the PRACK message.

[0502] S1607. The called party's IMS network element sends an UPDATA message to the called party's terminal device; correspondingly, the called party's terminal device receives the UPDATA message from the called party's IMS network element. The UPDATA message indicates that the calling party's terminal device has successfully reserved call resources.

[0503] For example, the called-side IMS network element may learn from the calling-side IMS network element that the call resources for the calling-side terminal device have been successfully reserved; alternatively, the called-side IMS network element may not actually know whether the call resources for the calling-side terminal device have been successfully reserved, but instead sends a false UPDATA message to the called-side terminal device. Since the first IMS network element interacts with the called-side terminal device as a B2B UA, the called-side terminal device considers the called-side IMS network element to be the calling-side device (such as the calling-side terminal device), and thus, after receiving the UPDATA message, the called-side terminal device considers the call resources for the calling-side terminal device to have been successfully reserved. Specifically, the implementation of the calling-side IMS network element knowing that the call resources for the calling-side terminal device have been successfully reserved can be found in the relevant description in the foregoing embodiments, and will not be repeated here.

[0504] S1608, the called-side terminal device sends an UPDATA 200 OK message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the UPDATA 200 OK message from the called-side terminal device. The UPDATA 200 OK message indicates that the called-side terminal device has successfully reserved call resources.

[0505] S1609, The called-side terminal device sends a 180-ring message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the 180-ring message from the called-side terminal device.

[0506] S1610, The called side IMS network element sends a 180-ring message to the calling side terminal device; correspondingly, the calling side terminal device receives the 180-ring message from the called side IMS network element.

[0507] Specifically, the 180-ring message sent by the called side IMS network element reaches the calling side terminal device through the calling side IMS network element.

[0508] S1611, The called-side terminal device sends an INVITE 200 OK message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the INVITE 200 OK message from the called-side terminal device.

[0509] S1612. The called party's IMS network element generates a new INVITE 200 OK message, which carries the SDP answer.

[0510] For example, the called-side IMS network element adds an SDP answer to the INVITE 200 OK message to obtain a new INVITE 200 OK message.

[0511] S1613, The called side IMS network element sends a new INVITE 200 OK message to the calling side terminal equipment; correspondingly, the calling side terminal equipment receives the new INVITE 200 OK message from the called side IMS network element.

[0512] For example, a new INVITE 200 OK message sent by the called party's IMS network element reaches the calling party's terminal device via the calling party's IMS network element.

[0513] S1614. The calling terminal device sends an ACK message to the called terminal device; correspondingly, the called terminal device receives the ACK message from the calling terminal device.

[0514] Specifically, the ACK message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0515] It should be noted that in any of the calling methods shown in Figures 4 to 16 above, the 180ring message received by the calling terminal device can also be called the eleventh message; if the first device is the calling terminal device, the eleventh message is the third message mentioned above; if the first device is the calling IMS network element, the eleventh message is message #3 mentioned above.

[0516] Similarly, in any of the calling methods shown in Figures 4 to 16 above, the INVITE 200 OK message sent by the called-side terminal device can also be called the twelfth message. The message it receives, confirming that the calling-side terminal device has received the media response information and indicating that the first terminal device has successfully reserved call resources, can also be called the thirteenth message; if the first device is the calling-side terminal device, the thirteenth message is the aforementioned tenth message; if the first device is the calling-side IMS network element, the thirteenth message is the aforementioned message sent by the first device to the calling-side terminal device, indicating that the called-side terminal device should respond to the calling-side terminal device's call request and carrying the second media response information. Referring to Figure 17, which is a flowchart illustrating another calling method provided in this application embodiment, as shown in Figure 17, the method may include the following steps:

[0517] S1701, the first IMS network element sends a first message to the second device; correspondingly, the second device receives the first message from the first IMS network element. The first message is used for the calling terminal device (i.e., the first terminal device) to call the called terminal device (i.e., the second terminal device), and includes media request information.

[0518] Optionally, when the first IMS network element is the calling side IMS network element, the corresponding second device is the called side IMS network element; or, when the first IMS network element is the called side IMS network element, the corresponding second device is the called side terminal device. Wherein, when the second device is the called side IMS network element, the called side IMS network element also needs to send the first message or the information carried in the first message to the called side terminal device.

[0519] For example, the first message can be an INVITE message.

[0520] For example, step S1701 is the same as step S401. For details, please refer to the relevant description of step S401 above, which will not be repeated here.

[0521] S1702, the second device sends a second message to the first IMS network element; correspondingly, the first IMS network element receives the second message from the second device. The second message indicates that the called terminal device has been ringing, and also includes first media response information.

[0522] For example, the implementation of the first media response information can be found in the relevant description in the above embodiments, and will not be repeated here.

[0523] For example, the second message can be a 180ring message.

[0524] Optionally, after receiving the INVITE message (such as the first message), the called terminal device can determine its feedback message by judging whether the called terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, or whether the called terminal device accesses the network based on narrowband high-orbit satellite access technology, at least one of these factors.

[0525] For example, when the called-side terminal device accesses the network based on narrowband high-orbit satellite access technology, it indicates that the called-side terminal device is capable of handling signaling in the simplified procedure; therefore, the first IMS network element and the called-side terminal device can execute the simplified procedure (i.e., perform signaling interaction in the simplified procedure). That is, after receiving the INVITE message, it can generate and feedback the signaling in the simplified procedure (i.e., the 180ring message), enabling the first IMS network element to receive the second message.

[0526] For example, whether the terminal device supports the ability to make calls based on narrowband high-orbit satellite access technology, and whether the terminal device accesses the network based on narrowband high-orbit satellite access technology, can be found in the relevant description in step S1703 below, and will not be repeated here.

[0527] S1703, The first IMS network element determines that the calling terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or the calling terminal device accesses the network based on non-narrowband high-orbit satellite access technology.

[0528] For example, if a terminal device does not support the ability to make calls using narrowband high-orbit satellite access technology, it accesses the network using a non-narrowband high-orbit satellite access technology. If a terminal device supports the ability to make calls using narrowband high-orbit satellite access technology, it can access the network using either a non-narrowband high-orbit satellite access technology or narrowband high-orbit satellite access technology. However, if a terminal device does not support the ability to make calls using narrowband high-orbit satellite access technology, it must access the network using a non-narrowband high-orbit satellite access technology when initiating a call; otherwise, the call cannot be established. Therefore, it can also be considered that if a terminal device accesses the network using narrowband high-orbit satellite access technology, it implicitly supports the ability to make calls using this technology. In other words, if the calling terminal device accesses the network using narrowband high-orbit satellite access technology, it means that the calling terminal device supports the ability to make calls using narrowband high-orbit satellite access technology and accesses the network using narrowband high-orbit satellite access technology.

[0529] Understandably, since the terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, it can access the network based on this technology. As described above, this will lead to increased call latency. Therefore, it is advisable to implement a simplified procedure (i.e., a simplified call procedure) in the call setup process when the terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology and / or can access the network based on this technology. This would reduce the number of signaling messages between the terminal device and the IMS network element, thereby reducing call latency.

[0530] However, for both the calling and called sides, one terminal device may not support the ability to perform calls based on narrowband high-orbit satellite access technology. Therefore, this terminal device cannot execute the simplified procedure. This results in one side executing the standard procedure (as shown in Figure 2) and the other side executing the standard procedure during the call setup process. In order to realize the call setup procedure in this scenario, at least one IMS network element needs to be able to convert the signaling in the standard procedure into the signaling in the simplified procedure, and / or convert the signaling in the simplified procedure into the signaling in the standard procedure.

[0531] For ease of description, the phrase "having the ability to convert signaling in a standard procedure into signaling in a simplified procedure, and / or converting signaling in a simplified procedure into signaling in a standard procedure" will be referred to as "having the ability to convert signaling" for short. This will be explained uniformly here and will not be elaborated further.

[0532] It is understood that in this application, the IMS network element has the ability to convert signaling, which can be understood as: the IMS network element can convert between signaling in the standard procedure and the simplified procedure of the B2BUA.

[0533] Taking the conversion of signaling in a simplified procedure into signaling in a standard procedure by an IMS network element as an example, the IMS network element can receive signaling in a simplified procedure from its upstream node, convert it into signaling in a standard procedure, and then send it to the next node. Therefore, for signaling in a simplified procedure, the IMS network element can act as the node where the source address of the signaling in the simplified procedure is located, executing the simplified procedure. That is, the signaling in the simplified procedure terminates at the IMS network element, or in other words, the IMS network element is the node where the destination address of the signaling in the simplified procedure is located. Correspondingly, the IMS network element can also feed back the corresponding simplified procedure signaling to the node where the source address of the signaling in the simplified procedure is located.

[0534] Similarly, for signaling in standard procedures, an IMS network element can act as a B2B UA to execute the standard procedure between itself and the node where the destination address of the signaling in the standard procedure is located; that is, the node where the source address of the signaling in the standard procedure is located is the IMS network element. Correspondingly, the node where the destination address of the signaling in the standard procedure is located can also send back the corresponding standard procedure signaling to the IMS network element.

[0535] For example, when accessing a network based on narrowband high-orbit satellite access technology, a simplified procedure is executed during call setup. Therefore, the terminal device needs to receive signaling from this simplified procedure, and it also needs to generate and output the signaling from the simplified procedure. In other words, the terminal device needs to process the signaling from the simplified procedure. Therefore, the terminal device's ability to perform calls based on narrowband high-orbit satellite access technology can also be understood as: the terminal device supports using narrowband high-orbit as IP-CAN to perform call services (such as voice and video services); further, it can also be understood as: the terminal device supports processing the signaling from the simplified procedure.

[0536] Therefore, the IMS network element can determine whether to enable its signaling conversion capability by determining whether the terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, or whether the terminal device accesses the network based on narrowband high-orbit satellite access technology, at least one of these conditions. Specifically, if the terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, or if the terminal device accesses the network based on non-narrowband high-orbit satellite access technology, at least one of these conditions, the IMS network element determines to enable its signaling conversion capability.

[0537] For example, an IMS network element can determine whether its corresponding local terminal device (e.g., the calling side IMS network element determines the calling side terminal device) supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether it accesses the network based on narrowband high-orbit satellite access technology; or, an IMS network element can determine whether its corresponding remote terminal device (e.g., the called side IMS network element determines the calling side terminal device) supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether it accesses the network based on narrowband high-orbit satellite access technology.

[0538] For example, when determining whether a standard procedure is executed between the IMS network element and the calling terminal device, it can be determined whether the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether it accesses the network based on narrowband high-orbit satellite access technology. In the case where the calling terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or accesses the network based on non-narrowband high-orbit satellite access technology, it is determined that a standard procedure is executed between the IMS network element and the calling terminal device. Therefore, if a simplified procedure is executed between the IMS network element and the called terminal device, it is necessary to enable its signaling conversion capability to convert the signaling in the simplified procedure (such as the second message in step S402) into the signaling in the standard procedure (such as the third message in step S404).

[0539] Optionally, in this application, the IMS network element may be assumed to have the capability to switch signaling. Therefore, the IMS network element can determine whether to enable its signaling switching capability by determining whether the terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, or whether the terminal device accesses the network based on narrowband high-orbit satellite access technology, at least one of these conditions. Alternatively, the IMS can determine whether it has the capability to switch signaling, and if it does, determine whether to enable its signaling switching capability by determining whether the terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, or whether the terminal device accesses the network based on narrowband high-orbit satellite access technology, at least one of these conditions.

[0540] For example, whether a terminal device supports the ability to make calls based on narrowband high-orbit satellite access technology can also be referred to as: whether the terminal device supports VoGEO capability; the terminal device's narrowband high-orbit satellite access network technology includes, but is not limited to, the terminal device's GEO access network.

[0541] For ease of description, the following description will use "the terminal device's ability to perform calls based on narrowband high-orbit satellite access technology" as "the terminal device's ability to support VoGEO" and "the terminal device's access to the network based on narrowband high-orbit satellite access technology" as "the terminal device's access to the network based on GEO" as an example. This will be explained uniformly here and will not be repeated.

[0542] Specifically, non-narrowband high-orbit satellite access technologies include, but are not limited to, terrestrial network technologies; for example, LTE, NR, etc.

[0543] It should be noted that this application does not limit the order of steps S1701-S1702 and step S1703; for example, steps S1701-S1702 may be performed before step S1703; or, steps S1701-S1702 may be performed after step S1703; or, steps S1701-S1702 may be performed simultaneously with step S1703.

[0544] S1704, the first IMS network element generates a third message. This third message indicates that a session is in progress and also includes second media response information.

[0545] For example, the second media response information may be the same as or different from the first media response information. The implementation of the second media response information can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0546] For example, when the first IMS network element receives the second message and determines that the calling terminal device does not support VoGEO capability, and / or that the calling terminal device is based on a non-GEO access network, it indicates that the calling terminal device cannot process the signaling in the simplified procedure. Therefore, the first IMS network element and the calling terminal device need to execute the standard procedure. Since the first IMS network element executes the simplified procedure with the called terminal device, the second message received by the first IMS network element is the signaling in the simplified procedure. Therefore, when the first IMS network element interacts with the calling terminal device, it needs to convert the received signaling from the simplified procedure into signaling in the standard procedure (such as the third message) in order to achieve signaling interaction with the calling terminal device.

[0547] S1705, the first IMS network element sends a third message to the first device; correspondingly, the first device receives the third message from the first IMS network element.

[0548] Optionally, if the first IMS network element is the calling side IMS network element and the first device is the calling side terminal device, then the calling side terminal device learns the media response information (such as the second media response information) upon receiving the third message. If the first IMS network element is the called side IMS network element and the first device is the calling side IMS network element, then the called side IMS network element needs to send the third message to the calling side IMS network element, and then the calling side IMS network element sends the third message, or a message obtained after processing (such as modifying or adjusting) the third message, which indicates that the session is in progress and carries the second media response information, to the calling side terminal device, so that the calling side terminal device learns the media response information (such as the second media response information).

[0549] Based on the calling method shown in Figure 17, during the process of the calling terminal device (i.e., the first terminal device) calling the called terminal device (the second terminal device) (i.e., from the transmission of INVITE messages (such as the first message, which is used by the calling terminal device to call the called terminal device and includes media request information) between the calling and called parties), the IMS network element (i.e., the first IMS network element) on the calling / called side can receive data from its upstream node (i.e., the second device); where the first IMS network element is a network element in the IMS network accessed by the calling terminal device (such as the calling P-CSCF), and correspondingly, the second device is a network element in the IMS network accessed by the called terminal device, such as the called P-CSCF; the first IMS network element is a network element in the IMS network accessed by the second terminal device. The network element in the incoming IMS network (such as the called-side P-CSCF), and correspondingly, the second device (the called-side terminal device) receives a 180-ring message (such as a second message, which indicates that the second terminal device has been ringing, and also includes first media response information); furthermore, the IMS network element on the calling / called side can obtain whether the calling-side terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether the calling-side terminal device accesses the network based on narrowband high-orbit satellite access technology, and if the calling-side terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or if the calling-side terminal device accesses the network based on non-narrowband high-orbit satellite access technology, and generates a 183-session message. The first IMS network element is a network element in the IMS network accessed by the first terminal device (such as the calling side P-CSCF), and the first device is the calling side terminal device. The second IMS network element is a network element in the IMS network accessed by the called side terminal device (such as the called side P-CSCF), and the first device is the calling side terminal device.

[0550] In other words, after receiving the INVITE message from the calling terminal, the called terminal can directly send a 180ring message back to the IMS network element on the calling / called side. The 180ring message carries media response information (i.e., the first media response information). This means that the IMS network element on the calling / called side and the called terminal do not need to transmit messages such as 183 session progress, PRACK, and UPDATA, thereby reducing the number of signaling messages exchanged in the call setup process, reducing call latency, and improving user experience.

[0551] Furthermore, after receiving the 180ring message from its upstream node, the calling / called IMS network element can determine whether it can transmit the 180ring message to the next node by judging whether the calling terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or whether the calling terminal device accesses the network based on narrowband high-orbit satellite access technology. If the calling terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or the calling terminal device accesses the network based on non-narrowband high-orbit satellite access technology, it indicates that the calling side does not support the simplified call setup process. Therefore, the existing call setup process needs to be used between the calling / called IMS network element and the calling terminal device. That is, the calling / called IMS network element can generate a 183 session progress message and feed it back to its next node. This provides different optional application scenarios for the implementation of the call setup process between the calling and called terminal devices (i.e., the calling side uses the existing call setup process, and the called side uses the simplified call setup process).

[0552] The above is an overall description of the call method provided in this application. The implementation of step S1703 in the above embodiment will be described in detail below. For example, the first IMS network element can determine whether the calling terminal device supports VoGEO capability and / or whether the calling terminal device accesses the network based on GEO in the following two ways:

[0553] Method 1: The first IMS network element determines from the first device whether the calling terminal device supports VoGEO capability and / or whether the calling terminal device accesses the network based on GEO.

[0554] For example, in Mode 1, the first device can inform the first IMS network element via a fourth message whether the calling terminal device supports VoGEO capability and / or whether the calling terminal device accesses the network based on GEO. In this case, the fourth message also indicates at least one of whether the calling terminal device supports VoGEO capability or whether the calling terminal device accesses the network based on GEO. The implementation of the fourth message can be found in the relevant description in step S400 above, and will not be repeated here.

[0555] As an example, when the first IMS network element is the calling side IMS network element, the first device is the calling side terminal device; the calling side terminal device can determine whether it supports VoGEO capability, and / or whether the calling side terminal device is based on GEO access network indication information, and inform the first IMS network element through the fourth message.

[0556] For example, information indicating whether the calling terminal device supports narrowband high-orbit satellite access technology for call execution can be located in the supported header field of the fourth message. That is, the supported header field in the fourth message is used to indicate whether the calling terminal device supports VoGEO capability. Specifically, if the supported header field indicates that the calling terminal device does not support VoGEO capability, then the fourth message indicates that the calling terminal device does not support VoGEO capability.

[0557] For example, the supprted header field can use a 1-bit field to indicate whether the calling terminal device supports VoGEO capability. If the 1-bit field is 1, it indicates that the calling terminal device supports VoGEO capability; conversely, if the 1-bit field is 0, it indicates that the calling terminal device does not support VoGEO capability.

[0558] Alternatively, if the 1-bit field exists in the supprted header field, it indicates that the calling terminal device supports VoGEO capability; if the 1-bit field does not exist in the supprted header field, it indicates that the calling terminal device does not support VoGEO capability. In this case, it can also be considered that the supprted header field in the fourth message does not include information indicating that the calling terminal device supports VoGEO capability.

[0559] For example, if the supported header field includes VoGEO (supported: VoGEO), it means that the calling terminal device supports VoGEO; if the supported header field does not include VoGEO, it means that the calling terminal device does not support VoGEO.

[0560] For example, the information used to indicate whether the calling terminal device accesses the network based on GEO can be located in the P-ANI header field of the fourth message; that is, the P-ANI header field in the fourth message is used to indicate whether the calling terminal device accesses the network based on GEO.

[0561] For example, the P-ANI header field is used to indicate the method by which the calling terminal device accesses the network; this method includes, but is not limited to, GEO access, LTE access, and NR access. When the P-ANI header field indicates that the calling terminal device accesses the network based on LTE or NR, it means that the fourth message indicates that the calling terminal device accesses the network based on a non-GEO network.

[0562] As another example, when the first IMS network element is the called side IMS network element, the first device is the calling side IMS network element; at this time, the calling side IMS network element can learn from the calling side terminal device or the calling side core network device whether the calling side terminal device supports VoGEO capability, and / or whether the calling side terminal device accesses the network based on GEO.

[0563] For example, the calling side IMS network element learns whether the calling side terminal device supports VoGEO capability and / or whether the calling side terminal device is based on GEO access network implementation; furthermore, the called side IMS network element learns from the calling side IMS network element whether the calling side terminal device supports VoGEO capability and / or whether the calling side terminal device is based on GEO access network implementation, all of which can be referred to in the relevant descriptions in "Implementation Method 1 and Implementation Method 2" above, and will not be repeated here.

[0564] Method 2: When the first IMS network element is the calling side IMS network element, the first IMS network element can determine from the calling side core network equipment whether the calling side terminal equipment supports VoGEO capability and / or whether the calling side terminal equipment accesses the network based on GEO.

[0565] For example, the calling-side core network device can determine whether the calling-side terminal device accesses the network based on GEO. Furthermore, the calling-side core network device can determine whether the calling-side terminal device supports VoGEO capabilities; for example, the calling-side terminal device can report its VoGEO capability to the calling-side core network device, enabling the calling-side core network device to determine whether the calling-side terminal device supports VoGEO capabilities. This application does not limit the reporting of information indicating whether the calling-side terminal device supports VoGEO capabilities, such as including it in its INVITE message (e.g., the fourth message) or during network registration.

[0566] Furthermore, the calling side core network device can send a message (i.e., the fifth message) to the calling side IMS network element to indicate whether the calling side terminal device supports VoGEO capability and / or whether the calling side terminal device accesses the network based on GEO. This allows the calling side IMS network element to determine whether the calling side terminal device supports VoGEO capability and / or whether the calling side terminal device accesses the network based on GEO. Typically, the calling side core network device sends this message to the calling side IMS network element based on a request message from the calling side IMS network element. This request message instructs the calling side core network device to send the same message to the calling side IMS network element.

[0567] For example, if the calling terminal device supports VoGEO capability, the fifth message is used to indicate that the calling terminal device supports VoGEO capability; if the calling terminal device accesses the network based on GEO, the fifth message is used to indicate that the calling terminal device accesses the network based on GEO.

[0568] If the calling terminal device does not support VoGEO capability, the fifth message is used to indicate that the calling terminal device does not support VoGEO capability; or, the calling core network device may not send the fifth message. In this case, it can also be considered that the calling core network device only sends the fifth message to the calling IMS network element if the calling terminal device supports VoGEO capability, that is, the fifth message is used to indicate that the calling terminal device supports VoGEO capability.

[0569] Similarly, if the calling terminal device is accessing the network via a non-GEO network, the fifth message is used to indicate that the calling terminal device is accessing the network via a non-GEO network; or, the calling core network device may not send the fifth message. In this case, it can also be considered that the calling core network device only sends the fifth message to the calling IMS network element when the calling terminal device is accessing the network via a GEO network, that is, the fifth message is used to indicate that the calling terminal device is accessing the network via a GEO network.

[0570] Optionally, after the first IMS network element learns whether the calling terminal device supports VoGEO capability or whether the calling terminal device accesses the network based on GEO, it can also inform the second device. For example, information indicating whether the calling terminal device supports VoGEO capability or whether the calling terminal device accesses the network based on GEO can be included in a first message and communicated to the second device. In this case, step S1703 is executed before step S1701. The first message further indicates whether the calling terminal device does not support VoGEO capability or whether the calling terminal device accesses the network based on a non-GEO network.

[0571] Method 3: When the first IMS network element is the called party's IMS network element, if the first IMS network element determines, according to step S1703, that it does not enable the capability of the switching signaling (i.e., the calling party's terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or, the calling party's terminal device accesses the network based on narrowband high-orbit satellite access technology), and the first IMS network element itself has the capability of switching signaling; at this time, the first IMS network element can further determine whether the called party's terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or, the called party's terminal device accesses the network based on narrowband high-orbit satellite access technology.

[0572] Wherein, if the called-side terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or, if the called-side terminal device accesses the network based on narrowband high-orbit satellite access technology, the first IMS network element can enable the ability to perform this conversion signaling; that is, the first IMS network element acts as a B2B UA to perform simplified signaling interaction with the called-side terminal device; and performs standard signaling interaction with the calling-side terminal device.

[0573] Furthermore, the first IMS network element can also inform the called terminal device that it has the ability to switch signaling; so that after receiving the INIVITE message, the called terminal device can send back signaling with a simplified process (such as sending back a 180ring message, i.e., executing step S1702 in Figure 17 below).

[0574] Specifically, since the first IMS network element interacts with the called-side terminal equipment as a B2B UA, the called-side terminal equipment considers the called-side IMS network element to be the calling-side equipment (such as the calling-side terminal equipment). Therefore, upon receiving this indication, it will assume that the calling side supports VoGEO capabilities. Furthermore, it can also be assumed that the calling side has the ability to process simplified procedure signaling, and thus, upon receiving the INIVITE message, it can feed back the simplified procedure signaling (such as a 180ring message). Optionally, the first media response information can also be carried in the 180ring message.

[0575] In other words, under Method 3, the called-side terminal device can send a 180ring message in any of the following situations: (1) The called-side terminal device accesses the network based on narrowband high-orbit satellite access technology; (2) The called-side terminal device accesses the network based on narrowband high-orbit satellite access technology, and the first IMS network element has the ability to convert signaling; (3) The called-side terminal device accesses the network based on non-narrowband high-orbit satellite access technology, the called-side IMS network element has the ability to convert signaling, and the calling-side terminal device accesses the network based on narrowband high-orbit satellite access technology; (4) The called-side terminal device accesses the network based on non-narrowband high-orbit satellite access technology, the called-side IMS network element has the ability to convert signaling, the calling-side terminal device accesses the network based on narrowband high-orbit satellite access technology, and the called-side terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology. This enables the first IMS network element to receive the second message in step S2002 below. Furthermore, the 180ring message is used to indicate the first media response information, enabling the first IMS network element to receive the second message in step S1702.

[0576] Combining the above three methods, it can be understood that the 183 session progress message is usually a temporary message. After the temporary message reaches the node where its destination address is located or the terminating node, the node where the destination address is located or the terminating node needs to send an acknowledgment message for the temporary message to the node where the source address of the temporary message is located (i.e., to acknowledge the source address node), to indicate that it has received the temporary message (or received the information carried by the temporary message). Therefore, after step S1705, the calling terminal device can send a PRACK message to the first IMS network element to indicate that it has received the second media response information; furthermore, the first IMS network element can send a PRACK 200 OK message (or, it can also be called: 200 OK PRACK message) to the calling terminal device to indicate that the first IMS network element has received the PRACK message.

[0577] Specifically, when the first IMS network element is the calling side IMS network element and the first device is the calling side terminal device, the calling side terminal device can send a sixth message (such as a PRACK message) to the calling side IMS network element; the sixth message is used to confirm that the calling side terminal device has received the second media response information. Then, the calling side IMS network element sends a PRACK 200 OK message back to the calling side terminal device. When the first IMS network element is the called side IMS network element and the first device is the calling side IMS network element, the calling side terminal device can send message #4 to the calling side IMS network element to confirm that the calling side terminal device has received the second media response information; then, the calling side IMS network element can forward message #4 to the called side IMS network element, where message #4 can also be called the sixth message; or, the calling side IMS network element can process message #4 (such as adjusting or modifying it) to obtain the sixth message and send it to the called side IMS network element. Subsequently, the called-side IMS network element sends a PRACK 200 OK message to the calling-side terminal device. In other words, the first IMS network element can receive a sixth message from the first device to confirm that the calling-side terminal device has received the second media response information.

[0578] In addition, after the calling terminal device has completed the reservation of call resources, the calling terminal device can also send an UPDATA message to the first IMS network element to indicate that the call resource reservation of the calling terminal device has been completed; then, the first IMS network element can send an UPDATA 200 OK message (or, it can also be called: 200 OK UPDATA message) to the calling terminal device to indicate that the first IMS network element has received the UPDATA message.

[0579] Specifically, when the first IMS network element is the calling side IMS network element and the first device is the calling side terminal device, the calling side terminal device can send a seventh message (such as an UPDATA message) to the calling side IMS network element; wherein, the sixth message is used to indicate that the call resource reservation of the calling side terminal device is complete. Then, the calling side IMS network element sends an UPDATA 200 OK message back to the calling side terminal device. When the first IMS network element is the called side IMS network element and the first device is the calling side IMS network element, the calling side terminal device can send message #5 to the calling side IMS network element to indicate that the call resource reservation of the calling side terminal device is complete; then, the calling side IMS network element can forward message #5 to the called side IMS network element, in which case message #5 can also be called the seventh message; or, the calling side IMS network element can process message #5 (such as adjusting or modifying) to obtain the seventh message, and send the seventh message to the called side IMS network element. Subsequently, the called-side IMS network element sends an UPDATA 200 OK message to the calling-side terminal device. In other words, the first IMS network element can receive a seventh message from the first device indicating that the call resource reservation for the calling-side terminal device is complete.

[0580] Furthermore, after receiving the UPDATA message from the calling terminal device, the first IMS network element can generate a ninth message; this ninth message is used to indicate that the second terminal device has been ringing. For example, the first IMS network element can delete the first media response information from the received second message to obtain the ninth message. The first IMS network element can then send this ninth message to the calling terminal device. For example, the ninth message can be a 180ring message, in which case the 180ring message does not carry media response information (such as the first or second media response information).

[0581] Optionally, after sending a 180ring message to the calling terminal device, the interaction between the first IMS network element and the called terminal device can include the following two possible implementation methods:

[0582] In one possible implementation, the first IMS network element can generate an eighth message based on the sixth and seventh messages it has received; wherein the eighth message is used to confirm that the calling terminal device has received the second media response information and to indicate that the call resource reservation of the calling terminal device is complete. Then, the eighth message is sent to the called terminal device.

[0583] For example, when the first IMS network element is the calling side IMS network element and the second device is the called side IMS network element, the calling side IMS network element sends an eighth message to the called side IMS network element. Then, the called side IMS network element can forward this eighth message to the called side terminal device, or it can process the eighth message (such as modifying or adjusting it) to obtain message #7, and then forward message #7 to the called side terminal device. Message #7 is used to confirm that the calling side terminal device has received the second media response information and to indicate that the call resource reservation of the calling side terminal device is complete. When the first IMS network element is the called side IMS network element and the second device is the called side terminal device, the called side IMS network element sends an eighth message to the called side terminal device. This allows the called side terminal device to know that the calling side terminal device has received the second media response information and that the call resource reservation of the calling side terminal device is complete. Furthermore, after receiving the eighth message or message #7, the called terminal device can also send an INVITE 200 OK message (or, it can also be called a 200 OK INVITE message) to the calling terminal device, so that the calling terminal device can send an ACK message to the called terminal device, thereby enabling the call between the calling and called terminal devices.

[0584] The following example illustrates the calling method described in this application embodiment, where the first message is an INVITE message, the second message is a 180-ring message, the third message is a 183-session progress message, the sixth message is a PRACK message, the seventh message is an UPDATA message, the eighth message is a PRACK message, the ninth message is a 180-ring message, the first and second media response information are both SDP answers, and the media request information is an SDP offer. For example, in this example, the calling method can be implemented based on the following two scenarios:

[0585] Scenario 1: The first IMS network element is the calling side IMS network element, the first device is the calling side terminal device, and the second device is the called side IMS device. Referring to Figure 18, another possible implementation of the calling method described in this application is shown. This calling method may include the following steps:

[0586] S1801, the calling terminal device sends an INVITE message to the called terminal device; correspondingly, the called terminal device receives the INVITE message from the calling terminal device. The INVITE message is used by the calling terminal device to call the called terminal device, and the INVITE message includes an SDP offer.

[0587] Specifically, the INVITE message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0588] For example, after the calling IMS network element receives the INVITE message, it can also send a 100 Trying message back to the calling terminal device. That is, the calling IMS network element can execute step S1802:

[0589] S1802, the calling side IMS network element sends a 100 Trying message to the calling side terminal device; correspondingly, the calling side terminal device receives the 100 Trying message from the calling side IMS network element. The 100 Trying message is used to confirm that the calling side IMS network element has received the INVITE message sent by the calling side terminal device.

[0590] S1803, The called-side terminal device sends a 180-ring message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the 180-ring message from the called-side terminal device.

[0591] Specifically, the 180ring message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0592] Optionally, the SDP answer can be carried in the 180ring message.

[0593] For example, after receiving the INVITE message, the called terminal device can determine the message it is responding to, and then execute step S1803 in the case described in step 1702 above.

[0594] S1804. The calling side IMS network element determines the standard procedure executed by the calling side.

[0595] Among them, the calling side IMS network element is based on whether the calling side terminal equipment supports VoGEO capability, or whether the calling side terminal equipment is based on GEO.

[0596] At least one of the access networks determines whether the calling side executes a standard procedure. When the calling side terminal device does not support VoGEO-based access and / or the calling side terminal device accesses the network based on a non-GEO network, the calling side IMS network element determines that the calling side executes a standard procedure, that is, the signaling interaction between the calling side terminal device and the calling side IMS network element to execute the standard procedure. In other words, the calling side IMS network element acts as a B2B UA for simplified procedure signaling interaction with the called side terminal device, and also has standard procedure signaling interaction with the calling side terminal device.

[0597] For details, please refer to the relevant descriptions of steps S1805 to S1816 below, which will not be repeated here.

[0598] Specifically, the implementation of step S1804 can be found in the relevant description of step S1703 above, and will not be repeated here.

[0599] S1805, the calling side IMS network element generates a 183 session progress message. The 183 session progress message carries the SDP answer.

[0600] For example, if the 180ring message carries an SDP answer, the calling IMS network element can determine the SDP answer carried in the 183 session progress message based on the SDP answer carried in the 180ring message.

[0601] If the 180 ring message does not carry the SDP answer, the calling IMS network element can generate the SDP answer and add it to the 183 session progress message. In this case, the encoding formats used between the calling IMS network element and the calling terminal device, and between the calling IMS network element and the called terminal device, may be different; for example, the bitrate format used between the calling IMS network element and the calling terminal device may be a standard bitrate, while the encoding format used between the calling IMS network element and the called terminal device may be a low bitrate.

[0602] S1806, The calling side IMS network element sends a 183 session progress message to the calling side terminal device; correspondingly, the calling side terminal device receives the 183 session progress message from the calling side IMS network element.

[0603] S1807. The calling terminal device sends a PRACK message to the calling IMS network element; correspondingly, the calling IMS network element receives the PRACK message from the calling terminal device network element. The PRACK message indicates that the calling terminal device has received the SDP answer.

[0604] S1808, the calling side IMS network element sends a PRACK 200 OK message to the calling side terminal equipment; correspondingly, the calling side terminal equipment receives the PRACK 200 OK message from the calling side IMS network element. The PRACK 200 OK message indicates that the calling side IMS network element has received the PRACK message.

[0605] S1809, The calling terminal device sends an UPDATA message to the calling IMS network element; correspondingly, the calling IMS network element receives the UPDATA message from the calling terminal device network element. The UPDATA message indicates that the calling terminal device has successfully reserved call resources.

[0606] S1810, the calling side IMS network element sends an UPDATA 200 OK message to the calling side terminal equipment; correspondingly, the calling side terminal equipment receives the UPDATA 200 OK message from the calling side IMS network element. The UPDATA 200 OK message indicates that the call resources reservation for both the calling and called side terminal equipment has been successful.

[0607] S1811, The calling side IMS network element generates a new 180ring message; the new 180ring message does not carry the SDP answer.

[0608] For example, if the 180ring message received in step S1802 carries an SDP answer, the calling side IMS network element can delete the SDP answer from the 180ring message received in step S1802 to obtain a new 180ring message.

[0609] S1812, The calling side IMS network element sends a new 180ring message to the calling side terminal equipment; correspondingly, the calling side terminal equipment receives the new 180ring message from the calling side IMS network element.

[0610] S1813, The calling IMS network element sends a PRACK message to the called terminal device; correspondingly, the called terminal device receives the PRACK message from the calling IMS network element. The PRACK message indicates that the calling terminal device has received the SDP answer. Furthermore, the PRACK message also indicates that the calling terminal device has successfully reserved call resources.

[0611] For example, the PRACK message sent by the calling side IMS network element reaches the called side terminal device through the called side IMS network element.

[0612] For example, taking the PRACK message in S1813 as indicating that the calling terminal device has received the SDP answer and also indicating that the call resource reservation of the calling terminal device is successful, the calling IMS network element can generate the PRACK message in step S1813 and execute step S1813 after receiving the PRACK message and UPDATA message from the calling terminal device. Furthermore, the called terminal device can ring the phone after receiving the PRACK message.

[0613] Optionally, if the PRACK message in S1813 does not indicate that the call resource reservation for the calling terminal device is successful, the calling IMS network element must also send an UPDATA message to the called terminal device after it learns that the call resource reservation for the calling terminal device is successful, to inform the called terminal device that the call resource reservation for the calling terminal device is successful. Thus, the called terminal device can ring after receiving the PRACK message or the UPDATA message. Furthermore, the called terminal device can send an UPDATA 200 OK message back to the calling IMS network element to inform it that it has received the UPDATA message. For ease of description, Figure 18 uses the example of the calling terminal device receiving the SDP answer in the PRACK message in step S1803 and the call resource reservation for the calling terminal device being successful. This will be explained uniformly here and will not be repeated.

[0614] S1814. The called-side terminal device sends a PRACK 200 OK message to the calling-side IMS network element; correspondingly, the calling-side IMS network element receives the PRACK 200 OK message from the called-side terminal device. The PRACK 200 OK message indicates that the called-side terminal device has received the PRACK from step S1813.

[0615] Specifically, when the PRACK message in step S1813 also indicates that the call resource reservation for the calling terminal device is successful, the PRACK 200OK message can also indicate that the call resource reservation for the called terminal device is successful.

[0616] For example, the PRACK 200 OK message sent by the called-side terminal device reaches the calling-side IMS network element through the called-side IMS network element.

[0617] S1815, The called-side terminal device sends an INVITE 200 OK message to the calling-side terminal device; correspondingly, the calling-side terminal device receives the INVITE 200 OK message from the called-side terminal device.

[0618] For example, the INVITE 200 OK message sent by the called-side terminal device passes through the called-side IMS network element and the calling-side IMS network element in sequence to reach the calling-side terminal device.

[0619] S1816. The calling terminal device sends an ACK message to the called terminal device; correspondingly, the called terminal device receives the ACK message from the calling terminal device.

[0620] Specifically, the ACK message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0621] Scenario 2: The first IMS network element is the called party's IMS network element, the first device is the calling party's IMS network element, and the second device is the called party's terminal device. Referring to Figure 19, another possible implementation of the calling method described in this application is shown. This calling method may include the following steps:

[0622] S1901, the calling terminal device sends an INVITE message to the called terminal device; correspondingly, the called terminal device receives the INVITE message from the calling terminal device. The INVITE message is used by the calling terminal device to call the called terminal device, and the INVITE message includes an SDP offer.

[0623] Specifically, the INVITE message sent by the calling terminal device passes through the calling IMS network element and the called IMS network element in sequence before reaching the calling terminal device.

[0624] For example, after the calling IMS network element receives the INVITE message, it can also send a 100 Trying message back to the calling terminal device. That is, the calling IMS network element can execute step S1902:

[0625] S1902, the calling side IMS network element sends a 100 Trying message to the calling side terminal device; correspondingly, the calling side terminal device receives the 100 Trying message from the calling side IMS network element. The 100 Trying message is used to confirm that the calling side IMS network element has received the INVITE message sent by the calling side terminal device.

[0626] S1903, The called-side terminal device sends a 180-ring message to the called-side IMS network element; correspondingly, the called-side IMS network element receives the 180-ring message from the called-side terminal device.

[0627] Optionally, the 180ring message carries the SDP answer.

[0628] For example, after receiving the INVITE message, the called terminal device can determine the message it is responding to, and then perform step S1903 in the case described in step 1702 above.

[0629] S1904, The called party's IMS network element determines the standard procedu...

Claims

1. A calling method, characterized in that, The method is applied to a first network protocol multimedia subsystem (IMS) network element, and the method includes: Send a first message to the second device, the first message being used by the first terminal device to call the second terminal device, the first message including media request information; Receive a second message from the second device, the second message indicating that a session is in progress, the second message also including first media response information; It is determined that the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on the narrowband high-orbit satellite access technology; A third message is generated, which indicates that the second terminal device has been ringing; Send the third message to the first device; Wherein, the first IMS network element is a network element in the IMS network accessed by the first terminal device, and correspondingly, the second device is a network element in the IMS network accessed by the second terminal device, and the first device is the first terminal device; or... The first IMS network element is a network element in the IMS network accessed by the second terminal device. Correspondingly, the second device is the second terminal device, and the first device is a network element in the IMS network accessed by the first terminal device.

2. The method according to claim 1, characterized in that, The determination that the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on the narrowband high-orbit satellite access technology, includes: The first terminal device receives a fourth message, which instructs the first terminal device to call the second terminal device, and instructs the first terminal device to support the ability to perform a call based on narrowband high-orbit satellite access technology, or the first terminal device to access a network based on the narrowband high-orbit satellite access technology, wherein the fourth message includes the media request information.

3. The method according to claim 2, characterized in that, The supported header field in the fourth message is used to indicate that the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology; and / or, The private access network information (P-ANI) header field in the fourth message indicates that the first terminal device accesses the network based on the narrowband high-orbit satellite access technology.

4. The method according to claim 1, characterized in that, The first IMS network element is a network element in the IMS network accessed by the first terminal device. The step of determining that the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on the narrowband high-orbit satellite access technology, includes: The first terminal device receives a fifth message from a first core network device, the fifth message indicating that the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, or that the first terminal device accesses the network based on the narrowband high-orbit satellite access technology, at least one of the following: the first core network device is a communication device in the core network to which the first terminal device accesses.

5. The method according to any one of claims 1-4, characterized in that, The first message is also used to indicate at least one of the following: the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, or the first terminal device accesses the network based on narrowband high-orbit satellite access technology.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: A sixth message is generated, which is used to confirm that the first IMS network element has received the first media response information; The sixth message is sent to the second device.

7. The method according to any one of claims 1-5, characterized in that, The method further includes: Receive a seventh message from the second device, the seventh message being used to indicate that the second terminal device has been ringing; The generation of the third message includes: The third message is generated based on the seventh message.

8. The method according to any one of claims 1-7, characterized in that, The third message also includes second media response information.

9. The method according to claim 8, characterized in that, The method further includes: The first terminal device receives an eighth message, which indicates that the first terminal device has received the second media response information and that the call resource reservation of the first terminal device has been successful.

10. The method according to any one of claims 1-9, characterized in that, The method further includes: A ninth message is sent to the second device, the ninth message being used to indicate that the call resources of the first terminal device have been successfully reserved.

11. The method according to claim 10, characterized in that, Sending the ninth message to the second device includes: The device receives an eighth message from the first device, the eighth message indicating that the first terminal device has received the second media response information and that the call resource reservation of the first terminal device has been successful. According to the eighth message, the ninth message is sent. The eighth message comes from the first device and is used to indicate that the first device has received the second media response information and that the call resource reservation of the first terminal device has been successful. The ninth message is used to indicate that the call resource reservation of the first terminal device has been successful.

12. The method according to any one of claims 1-7, characterized in that, The method further includes: A tenth message is sent to the first device, the tenth message being used to instruct the second terminal device to respond to the call request of the first terminal device, the tenth message also including second media response information.

13. A calling method, characterized in that, The method is applied to a first network protocol multimedia subsystem (IMS) network element, and the method includes: Send a first message to the second device, the first message being used by the first terminal device to call the second terminal device, the first message including media request information; Receive a second message from the second device, the second message being used to indicate that the second terminal device has been ringing, the second message also including first media response information; It is determined that the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology; The third message is generated, which is used to indicate that the session is in progress, and the third message also includes second media response information; Send the third message to the first device; Wherein, the first IMS network element is a network element in the IMS network accessed by the first terminal device, and correspondingly, the second device is a network element in the IMS network accessed by the second terminal device, and the first device is the first terminal device; or... The first IMS network element is a network element in the IMS network accessed by the second terminal device. Correspondingly, the second device is the second terminal device, and the first device is a network element in the IMS network accessed by the first terminal device.

14. The method according to claim 13, characterized in that, The determination that the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology, includes: The device receives a fourth message from the first device, the fourth message indicating that the first terminal device calls the second terminal device, and indicating that the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology, at least one of the following: the fourth message includes the media request information.

15. The method according to claim 14, characterized in that, The supported header field in the fourth message does not include information indicating the first terminal device's ability to perform calls based on narrowband high-orbit satellite access technology. And / or, The P-ANI header field in the fourth message is used to indicate that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology.

16. The method according to claim 13, characterized in that, The first IMS network element is a network element in the IMS network accessed by the first terminal device. The determination that the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology, includes: The first terminal device receives a fifth message from a first core network device. The fifth message indicates that the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology. The first core network device is a communication device in the core network to which the first terminal device accesses.

17. The method according to any one of claims 13-16, characterized in that, The first message is also used to indicate at least one of the following: the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, or the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology.

18. The method according to any one of claims 13-17, characterized in that, The method further includes: Receive a sixth message from the first device, the sixth message being used to indicate that the first terminal device has received the second media response information; Receive a seventh message from the first device, the seventh message being used to indicate that the call resources of the first terminal device have been successfully reserved; Based on the sixth and seventh messages, an eighth message is sent to the second device. The eighth message is used to indicate that the first terminal device has received the second media response information and to indicate that the call resource reservation of the first terminal device has been successful.

19. The method according to any one of claims 13-18, characterized in that, The method further includes: Receive a seventh message from the first device, the seventh message being used to indicate that the call resources of the first terminal device have been successfully reserved; After receiving the seventh message from the first device and the second message from the second device, the method further includes: A ninth message is sent to the first device, the ninth message being used to indicate that the second terminal device has been ringing.

20. A calling method, characterized in that, The method is applied to a first network protocol multimedia subsystem (IMS) network element, and the method includes: Send a first message to the second device, the first message being used by the first terminal device to call the second terminal device, the first message including media request information; Receive a second message from the second device, the second message being used to indicate that the second terminal device has been ringing; It is determined that the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on the narrowband high-orbit satellite access technology; The third message is generated to indicate that the second terminal device has been ringing; Send the third message to the first device; Wherein, the first IMS network element is a network element in the IMS network accessed by the first terminal device, and correspondingly, the second device is a network element in the IMS network accessed by the second terminal device, and the first device is the first terminal device; or... The first IMS network element is a network element in the IMS network accessed by the second terminal device. Correspondingly, the second device is the second terminal device, and the first device is a network element in the IMS network accessed by the first terminal device.

21. The method according to claim 20, characterized in that, The determination that the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology, includes: The device receives a fourth message from the first device, the fourth message indicating that the first terminal device calls the second terminal device, and indicating that the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology, at least one of the following: the fourth message includes the media request information.

22. The method according to claim 21, characterized in that, The supported header field in the fourth message does not include information indicating the first terminal device's ability to perform calls based on narrowband high-orbit satellite access technology. And / or, The P-ANI header field in the fourth message is used to indicate that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology.

23. The method according to claim 20, characterized in that, The first IMS network element is a network element in the IMS network accessed by the first terminal device. The determination that the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, and / or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology, includes: The first terminal device receives a fifth message from a first core network device. The fifth message indicates that the first terminal device does not support the ability to perform calls based on narrowband high-orbit satellite access technology, or that the first terminal device accesses the network based on non-narrowband high-orbit satellite access technology. The first core network device is a communication device in the core network to which the first terminal device accesses.

24. The method according to any one of claims 20-23, characterized in that, The second message includes the first media response information.

25. The method according to claim 24, characterized in that, The third message includes a second media response message, which is related to the first media response message.

26. The method according to claim 25, characterized in that, The method further includes: A sixth message is received from the first device, the sixth message being used to confirm that the first terminal device has received the second media response information and that the call resources of the first terminal device have been successfully reserved; According to the sixth message, a seventh message is sent to the second device. The seventh message is used to confirm that the first terminal device has received the second media response information and that the call resources of the first terminal device have been successfully reserved.

27. A calling method, characterized in that, The method includes: Send a fourth message, the fourth message being used for the first terminal device to call the second terminal device, and to indicate whether the first terminal device supports the ability to perform a call based on narrowband high-orbit satellite access technology, and / or to indicate whether the first terminal device accesses the network based on the narrowband high-orbit satellite access technology; Receive the eleventh message, which is used to indicate that the second terminal device has been ringing.

28. The method according to claim 27, characterized in that, At least one of the first terminal device or the second terminal device is based on a narrowband high-orbit satellite access network; and / or, Both the first terminal device and the second terminal device support the ability to make calls based on the narrowband high-orbit satellite access technology.

29. The method according to claim 27 or 28, characterized in that, The eleventh message also includes a second media response.

30. The method according to claim 29, characterized in that, After receiving the eleventh message, the method further includes: A sixth message is sent, which is used to confirm that the first terminal device has received the second media response information, the instruction, and that the call resources of the first terminal device have been successfully reserved.

31. The method according to claim 27 or 28, characterized in that, After receiving the eleventh message, the method further includes: The tenth message is received, which is used to instruct the second terminal device to respond to the call request of the first terminal device. The tenth message also includes second media response information.

32. The method according to any one of claims 27-31, characterized in that, The supported header field in the fourth message is used to indicate whether the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology. And / or, The P-ANI header field in the fourth message indicates whether the first terminal device accesses the network based on the narrowband high-orbit satellite access technology.

33. A calling method, characterized in that, The method includes: Receive a first message, the first message being used by a first terminal device to request a call to a second terminal device, the first message including media request information; Determine that at least one of the first terminal device or the second terminal device is based on a narrowband high-orbit satellite access network; A second message is generated, which instructs the second terminal device to ring. Send the second message.

34. The method according to claim 33, characterized in that, Both the first terminal device and the second terminal device support the ability to make calls based on narrowband high-orbit satellite access technology.

35. The method according to claim 33 or 34, characterized in that, The second message also includes information on the first media response.

36. The method according to claim 33 or 34, characterized in that, After sending the second message, the method further includes: Send a twelfth message, which is used to indicate the first media response information and the second terminal device's response to the first terminal device's call request.

37. The method according to any one of claims 33-36, characterized in that, The method further includes: The thirteenth message is received, which is used to confirm that the first terminal device has received the media response information and to indicate that the call resources of the first terminal device have been successfully reserved.

38. The method according to any one of claims 33-37, characterized in that, The first message is also used to indicate whether the first terminal device accesses the network based on the narrowband high-orbit satellite access technology.

39. The method according to claim 38, characterized in that, The supported header field in the first message is used to indicate whether the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology.

40. The method according to any one of claims 33-39, characterized in that, The first message is also used to indicate whether the first terminal device supports the ability to perform calls based on narrowband high-orbit satellite access technology.

41. The method according to claim 40, characterized in that, The P-ANI header field in the first message indicates whether the first terminal device accesses the network based on the narrowband high-orbit satellite access technology.

42. A communication device, characterized in that, The communication device includes a processor; the processor is configured to run a computer program or instructions to cause the communication device to perform the method as claimed in any one of claims 1-12; or to cause the communication device to perform the method as claimed in any one of claims 13-19; or to cause the communication device to perform the method as claimed in any one of claims 20-26; or to cause the communication device to perform the method as claimed in any one of claims 27-32; or to cause the communication device to perform the method as claimed in any one of claims 33-41.

43. A computer-readable storage medium, characterized in that, A computer-readable storage medium stores computer instructions or programs that, when executed on a computer, cause the method of any one of claims 1-12 to be performed; or cause the method of any one of claims 13-19 to be performed; or cause the method of any one of claims 20-26 to be performed; or cause the method of any one of claims 27-32 to be performed; or cause the method of any one of claims 33-41 to be performed.

44. A computer program product, characterized in that, The computer program product includes a computer program or instructions; when some or all of the computer instructions are executed on a computer, they cause the method of any one of claims 1-12 to be performed; or cause the method of any one of claims 13-19 to be performed; or cause the method of any one of claims 20-26 to be performed; or cause the method of any one of claims 27-32 to be performed; or cause the method of any one of claims 33-41 to be performed.

45. A chip, characterized in that, include: Memory is used to store computer program instructions; A processor is configured to execute the computer program instructions, causing a communication device including the chip to perform the method as described in any one of claims 1-12; or, causing the communication device including the chip to perform the method as described in any one of claims 13-19; or, causing the communication device including the chip to perform the method as described in any one of claims 20-26; or, causing the communication device including the chip to perform the method as described in any one of claims 27-32; or, causing the communication device including the chip to perform the method as described in any one of claims 33-41.