A communication method and related apparatus

Abstract

The application provides a communication method and related device, in which a first internet protocol (IP) multimedia subsystem (IMS) network element serving a called terminal device can determine a wireless access type of the called terminal device by receiving first information sent by a first core network network element or a subscription network element or the called terminal device, and send second information to a second IMS network element or a calling terminal device, the second information being used to indicate a call setup duration between the calling terminal device and the called terminal device or the access type of the called terminal device, so that the calling terminal device can wait patiently and the probability of the calling terminal device hanging up due to the mistaken belief that the network has a problem or the called terminal device is offline is reduced.

Description

[0001] This application claims priority to Chinese Patent Application No. 202510142468.2, filed with the State Intellectual Property Office of China on February 8, 2025, entitled “A Communication Method and Related Device”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method and related apparatus. Background Technology

[0003] Terminal devices can make calls via the Internet Protocol (IP) Multimedia Subsystem (IMS). In satellite communication systems, terminal devices can make IMS calls via satellite.

[0004] Currently, satellite communication systems can be classified into three types based on their orbital altitude: geostationary earth orbit (GEO) satellite communication systems (or synchronous orbit satellite systems); medium earth orbit (MEO) satellite communication systems; and low earth orbit (LEO) satellite communication systems. For example, the round-trip time delay for GEO satellite communication is 238–270 milliseconds (ms), while the round-trip time delay for LEO satellite communication is 8 ms–20 ms.

[0005] However, when a calling terminal device makes an IMS call to a called terminal device via satellite, especially in high-orbit GEO satellite communication scenarios, the transmission delay is relatively long. This can cause the user of the calling terminal device, as a caller, to potentially assume there is a network problem or that the called terminal device is offline, and thus hang up the phone. Summary of the Invention

[0006] This application provides a communication method and related apparatus. A first Internet Protocol (IP) Multimedia Subsystem (IMS) network element serving a called terminal device can receive first information sent by a first core network element, a subscribed network element, or the called terminal device to determine the wireless access type of the called terminal device. This information is then sent to a second IMS network element or the calling terminal device to indicate the call setup time between the calling and called terminal devices or the access type of the called terminal device. This allows the calling terminal device to wait patiently, reducing the probability of the calling terminal device mistakenly believing there is a network problem or that the called terminal device is offline and hanging up.

[0007] This application provides a communication method, which is executed by a first IMS network element, or by some components of the first IMS network element (e.g., processor, chip, chip system, proxy-call session control function (P-CSCF), serving-call session control function (S-CSCF), interrogating-call session control function (ICSCF), etc.), or may be implemented by a logic module or software capable of implementing all or part of the functions of the first IMS network element. This method can be applied to satellite scenarios. In the first aspect and its possible implementations, the method is described using the example of execution by a first IMS network element (also referred to as the called IMS). In this method, the first IMS network element receives first information sent by a first core network element, a subscribed network element, or a called terminal device. The first IMS network element sends second information to a second IMS network element or a calling terminal device.

[0008] The first piece of information indicates one or more of the following: the radio access type of the called terminal device and the call setup duration; the call setup duration is the duration of call setup between the calling terminal device and the called terminal device, and the call setup duration is related to the radio access type. The second piece of information indicates one or more of the following: the call setup duration and the radio access type of the called terminal device. The second IMS network element is used to serve the calling terminal device.

[0009] Furthermore, network elements marked with "first" are used to serve the called terminal equipment, while network elements marked with "second" are used to serve the calling terminal equipment. For example, the first IMS network element serves the called terminal equipment, and the second IMS network element serves the calling terminal equipment. The network elements marked with "first" and "second" can be the same or different network elements. For example, if the first IMS network element and the second IMS network element are the same IMS network element, this IMS network element can be used to serve not only the calling and called terminal equipment. The first IMS network element serves the called terminal equipment, and the second IMS network element serves the calling terminal equipment. For example, "IMS network element used to serve terminal equipment" can be interpreted as: the network element selected by the terminal equipment when registering for IMS. Or it can be interpreted as the network element responsible for receiving session initiation or 183 messages from the terminal equipment, etc.

[0010] It should be noted that, of course, sometimes network elements with the prefix "second" can serve not only the calling terminal equipment but also the called terminal equipment. Similarly, sometimes network elements with the prefix "first" can serve not only the called terminal equipment but also the calling terminal equipment.

[0011] For example, the second IMS network element can also include a multimedia telephony application server (MMTel AS)-B. Alternatively, it can be understood that the second IMS network element can also serve the called terminal device. For instance, MMTel AS-B can send a ringtone to the calling terminal device. In other words, MMTel AS-B can serve not only the called terminal device but also the calling terminal device.

[0012] In addition, the radio access type defines the transmission technology used in the access network. For example, the radio access type may also be called a radio access technology (RAT) type, access technology, or other names. Optionally, this type distinguishes different forms of radio access.

[0013] For example, radio access types include one or more of the following: cellular, new radio (NR) (i.e., 5G cellular access technology), long term evolution (LTE) (i.e., 4G cellular access technology), narrowband Internet of Things (NB-IoT), NTN, NR satellite access (including NR LEO / NR MEO / NRGEO / NR otherSAT, i.e., low-Earth orbit, medium-Earth orbit, and geostationary orbit satellites), LTE satellite access (similar to NR, there are also low-Earth orbit, medium-Earth orbit, etc., such as LTE LEO), and future access technologies. Furthermore, radio access types can be used for 3rd generation partnership project (3GPP) access as well as non-3GPP access.

[0014] Optionally, the subscribed network element may include one or more of the following: converged Home Location Register (HLR) / converged Home Subscriber Server (HSS) / converged Unified Data Management (UDM) / HLR / HSS / UDM. Alternatively, the subscribed network element can be an IMS network element in the IMS network (which can be called a converged HLR / converged HSS / converged UDM), a core network element in the core network, or an independent network element separate from the IMS network and core network elements; no specific limitation is made here. The terminal equipment (calling terminal equipment and / or called terminal equipment) can be an LTE terminal, NR terminal, NB-IoT terminal, etc.; no specific limitation is made here.

[0015] In addition, call setup time can also be called session / connection setup time, time for session / connection establishment, call setup delay, transmission time, or call waiting time / wait time for call setup / call waiting duration.

[0016] For example, call setup time, connection establishment time, or transmission time can be interpreted in several ways. For instance, it can be interpreted as the time interval between the sending of the calling signal and the reception of the call-connect signal. Alternatively, it can be interpreted as the duration / time required to complete all or part of the IMS call setup process (if partial, this could be the duration of bearer establishment by the calling and / or called party, the duration of the calling party receiving the response message, etc.). Or it can be interpreted as the duration from when the calling party initiates the call setup process (e.g., sending an INVITE message) to when the calling party receives the ringing signal.

[0017] For example, call waiting time or transmission time can be interpreted in several ways. For instance, it can be interpreted as: the waiting time from when the calling user dials the number until the calling user hears the ring / tone. Or it can be interpreted as: the time from when the calling user initiates the call setup process until the calling user receives the called user's answer-the-hook instruction message. Or it can be interpreted as: the waiting time from when the calling user dials the number until the calling user hears the called user answer / hook the phone, etc. Here, the calling user can be a person using the calling terminal device, artificial intelligence, etc.

[0018] Based on the above scheme, the first IMS network element serving the called terminal device can determine the wireless access type of the called terminal device by receiving the first information sent by the first core network element, the subscribed network element, or the called terminal device. Then, it can send the second information to the second IMS network element or the calling terminal device. The second information is used to indicate the call setup time between the calling terminal device and the called terminal device or the access type of the called terminal device, so that the calling terminal device can wait patiently and reduce the probability that the calling terminal device will hang up due to mistakenly believing that there is a network problem or that the called terminal device is offline.

[0019] Optionally, in one possible implementation of the first aspect, when the calling terminal device accesses the network via a terrestrial network, or when the first IMS network element does not receive an instruction from the calling terminal device or the second IMS network element to prohibit ringback tones / ringing, the second information is sent to the second IMS network element or the calling terminal device.

[0020] Among them, "the calling terminal device accesses through the terrestrial network" can be "the calling terminal device accesses through geostationary earth orbit (GEO) (or synchronous orbit satellite) or satellite access"; "prohibit sending ringtones or caller ID ringtones" can be "prohibit" or "suppress", etc.

[0021] In this possible implementation, a second message is sent if the calling party is not using GEO access (e.g., terrestrial access) or if no instruction to "prohibit sending ringtones or caller ID" is received, thereby clarifying whether to trigger the sending of the second message.

[0022] Optionally, in one possible implementation of the first aspect, the first IMS network element receives a session initiation message; and in response to the session initiation message, sends second information to the second IMS network element or the calling terminal device.

[0023] In this possible implementation, the step of the first IMS network element sending the second information is associated with the session initiation message, so that the first IMS network element can determine whether to send the second information based on whether it receives the session initiation message.

[0024] Optionally, in one possible implementation of the first aspect, the first IMS network element receives a response message to the session initiation message; after receiving the response message, the first IMS network element sends second information to the second IMS network element or the calling terminal device.

[0025] In this possible implementation, the step of the first IMS network element sending the second information is associated with the response message of the session initiation message, so that the first IMS network element can determine whether to send the second information based on whether it receives the response message of the session initiation message.

[0026] Optionally, in one possible implementation of the first aspect, the first IMS network element may also send request information to the first core network element or the subscribed network element, the request information being used to query the wireless access type of the called terminal device.

[0027] In this possible implementation, the first IMS network element can proactively query the wireless access type of the called terminal device from the first core network element or the subscribed network element, thereby improving the processing efficiency of the first IMS network element.

[0028] Optionally, in one possible implementation of the first aspect, the second information is used to indicate to the user of the calling terminal device one or more of the following: call setup duration, and the radio access type of the called terminal device.

[0029] In this possible implementation, the second information can also be used to remind the user of the calling terminal device, thereby reducing the probability that the calling user will mistakenly believe that there is a network problem or that the called terminal device is offline and hang up.

[0030] Alternatively, in one possible implementation of the first aspect, the second information is included in the response message of the ringing message or session initiation message.

[0031] In this possible implementation, the second information can be carried in different messages, and different messages correspond to different timing sequences, so that the wireless access type of the called terminal device can be flexibly indicated to the calling terminal device.

[0032] Optionally, in one possible implementation of the first aspect, the first IMS network element may also send third information, which is used to instruct the called terminal device to set to early ringing mode.

[0033] In this possible implementation, the early ringing mode can reduce the probability of the calling terminal only hearing a beep before the called terminal rings, due to the called party's bearer establishment process not being completed. This can lead to the calling terminal mistakenly believing there is a network problem or that the called terminal is offline, causing the call to hang up.

[0034] Alternatively, in one possible implementation of the first aspect, the first IMS network element may also determine the call setup duration based on the radio access type of the called terminal device.

[0035] In this possible implementation, the first IMS network element can determine the corresponding call setup duration according to different radio access types to support the scheme of the second information indicating the call setup duration.

[0036] Optionally, in one possible implementation of the first aspect, the wireless access type includes: satellite or non-satellite, wherein the satellite specifically includes one or more of the following: geostationary earth orbit (GEO) (or synchronous orbit satellite), medium earth orbit (MEO), and low earth orbit (LEO).

[0037] The second aspect of this application provides a communication method executed by a second IMS network element, or by some components of the second IMS network element (e.g., processor, chip, chip system, P-CSCF, S-CSCF, I-CSCF, multimedia telephony application server (MMTel-AS), customized alerting tone application server (CAT-AS), etc.), or the method can also be implemented by a logic module or software capable of implementing all or part of the functions of the first IMS network element. This method can be applied to satellite scenarios. In the second aspect and its possible implementations, the method is described as being executed by the first IMS network element (also referred to as the called IMS). In this method, the second IMS network element receives second information, which indicates the call setup duration or the radio access type of the called terminal device, the call setup duration being related to the radio access type. The second IMS network element sends fourth information to the calling terminal device, the fourth information indicating the call setup duration or the radio access type.

[0038] Based on the above scheme, the second IMS network element serving the calling terminal device can determine the wireless access type or call setup duration of the called terminal device through the received second information, and then send the prompt to the calling terminal device, so that the calling terminal device can wait patiently, reducing the probability that the calling terminal device will hang up due to mistakenly believing that there is a network problem or that the called terminal device is offline.

[0039] Alternatively, in one possible implementation of the second aspect, the fourth information includes media data used to indicate to the user of the calling terminal device the call setup duration or the type of wireless access.

[0040] In this possible implementation, the second IMS network element can send media data to the calling terminal device to notify the user of the calling terminal, thereby increasing the diversity of ways to remind the user.

[0041] Alternatively, in one possible implementation of the second aspect, the second IMS network element determines the fourth information based on the radio access type of the called terminal device.

[0042] In this possible implementation, the second IMS network element can determine the corresponding fourth information according to different wireless access types, thereby increasing the probability that the user perceives the fourth information and reducing the probability that the calling user will mistakenly believe that there is a network problem or that the called terminal device is offline and hang up.

[0043] Optionally, in one possible implementation of the second aspect, the second IMS network element sends the fourth information to the calling terminal device after the calling bearer is established.

[0044] In this possible implementation, sending the fourth information after the calling bearer is established can increase the probability that the calling terminal device will successfully receive the fourth information.

[0045] Optionally, in one possible implementation of the second aspect, the wireless access type includes: satellite or non-satellite, with satellite specifically including one or more of the following: GEO, MEO, LEO.

[0046] A third aspect of this application provides a communication method executed by a calling terminal, or by a component (e.g., a processor, chip, or chip system) within the calling terminal, or by a logic module or software capable of implementing all or part of the calling terminal's functions. In this third aspect and its possible implementations, the method is described as being executed by the calling terminal device. In this method, the calling terminal device receives a ringtone, which indicates the call setup duration between the calling terminal device and the called terminal device or the wireless access type of the called terminal device, the call setup duration being related to the wireless access type. The calling terminal device then plays the ringtone.

[0047] In this application, the ringtone can also be replaced with instruction information, signaling messages, or media information, such as video, audio, text, images, vibration, etc., without any specific limitation here.

[0048] Based on the above scheme, the calling terminal device can receive and play a ringtone, which is used to indicate the wireless access type or call setup time of the called terminal device. This allows the user of the calling terminal device to wait patiently based on the ringtone, reducing the probability that the calling terminal device will hang up mistakenly thinking that there is a network problem or that the called terminal device is offline.

[0049] Optionally, in one possible implementation of the third aspect, the wireless access type includes: satellite or non-satellite, with satellite specifically including one or more of the following: GEO, MEO, LEO.

[0050] This application provides a fourth aspect of a communication method, which is executed by a calling terminal, or by a component (e.g., a processor, chip, or chip system) within the calling terminal, or by a logic module or software capable of implementing all or part of the calling terminal's functions. In this fourth aspect and its possible implementations, the method is described as being executed by a calling terminal device. In this method, the calling terminal device receives first indication information, which indicates the call setup duration between the calling terminal device and the called terminal device or the radio access type of the called terminal device, wherein the call setup duration is related to the radio access type. The calling terminal device plays a ringtone based on the first indication information.

[0051] Based on the above scheme, the calling terminal device can receive the first instruction information and play a ringtone based on the first instruction information, so that the user of the calling terminal device can wait patiently according to the ringtone, reducing the probability that the calling terminal device will hang up due to mistakenly thinking that there is a network problem or that the called terminal device is offline.

[0052] Alternatively, in one possible implementation of the fourth aspect, the first instruction message is a 183 message.

[0053] Alternatively, in one possible implementation of the fourth aspect, the ringtone is used to indicate to the user of the calling terminal device one or more of the following: call setup time, waiting time, and the wireless access type of the called terminal device.

[0054] In this possible implementation, the ringtone can be used to remind the user of the calling terminal device, thereby reducing the probability that the calling user will mistakenly believe that there is a network problem or that the called terminal device is offline and hang up.

[0055] Alternatively, in one possible implementation of the fourth aspect, the ringtone includes one or more of the following: voice, video, and text.

[0056] In this possible implementation, there are multiple ways to present the ringtone in order to adapt to different user needs and improve the user experience.

[0057] Optionally, in one possible implementation of the fourth aspect, the wireless access type includes: satellite or non-satellite, with satellite specifically including one or more of the following: GEO, MEO, LEO.

[0058] This application provides a communication method, which is executed by a first core network element or a subscribed network element, or by a portion of a component (e.g., a processor, chip, or chip system) within the first core network element or subscribed network element, or by a logic module or software capable of implementing all or part of the functions of the first core network element or subscribed network element. In this fifth aspect and its possible implementations, the method is described as being executed by a first core network element or subscribed network element. In this method, the first core network element or subscribed network element receives request information from a first IMS network element, the request information being used to request the radio access type of the called terminal device. The first core network element or subscribed network element sends fifth information to the first IMS network element, the fifth information being used to indicate that the radio access type of the called terminal device is geostationary earth orbit (GEO) access.

[0059] Based on the above scheme, the first core network element or the contracted network element can send the fifth information according to the request information of the first IMS network element. Thus, the first IMS network element can determine that the wireless access type of the called terminal device is GEO access based on the fifth information. This facilitates subsequent reminders to the calling terminal device to wait patiently, reducing the probability of the calling terminal device mistakenly believing there is a network problem or that the called terminal device is offline and hanging up.

[0060] Optionally, in one possible implementation of the fifth aspect, the request information is a Location-Info-Request (LIR) message, and the fifth information is a Location-Info-Answer (LIA) message.

[0061] In this possible implementation, the adaptability of the solution can be improved by using the existing LIA to indicate the wireless access type of the called terminal device.

[0062] Optionally, in one possible implementation of the fifth aspect, the first core network element or the contracted network element may also determine that the wireless access type of the called terminal device is GEO access.

[0063] In this possible implementation, the first core network element or the contracted network element provides the first IMS network element with the wireless access type of the called terminal device, thereby reducing the processing complexity of the first IMS network element.

[0064] Optionally, in one possible implementation of the fifth aspect, the first core network element or the subscribed network element determines the wireless access type of the called terminal device as GEO access based on the subscription information of the called terminal device.

[0065] In this possible implementation, the first core network element or the contracted network element can determine whether the called terminal device is a GEO access device based on the contracted information of the called terminal device, providing a more reasonable way to determine the wireless access type.

[0066] Optionally, in one possible implementation of the fifth aspect, the wireless access type includes: satellite or non-satellite, with satellite specifically including one or more of the following: GEO, MEO, LEO.

[0067] The sixth aspect of this application provides a communication method, which is executed by a called terminal, or by a component (e.g., a processor, chip, or chip system) in the called terminal, or by a logic module or software capable of implementing all or part of the functions of the called terminal. In the sixth aspect and its possible implementations, the method is described as being executed by a called terminal device. In this method, when the radio access type of the called terminal device is GEO access, the called terminal device sends first information, which indicates one or more of the following: the radio access type of the called terminal device is GEO access, and the call setup duration; the call setup duration is the call setup duration between the calling terminal device and the called terminal device, and the call setup duration is related to the radio access type.

[0068] Based on the above solution, for the IMS GEO scenario, the called terminal device directly notifies its own terminal device that it is a GEO access, and the called side IMS network element triggers the ringback tone playback, thereby reducing the impact on the core network and the calling side IMS network element.

[0069] Alternatively, in one possible implementation of the sixth aspect, the first information is also used to indicate the media types supported by the called terminal device and / or the calling terminal device.

[0070] Optionally, in one possible implementation of the sixth aspect, the wireless access type of the called terminal device is GEO access, including: the current wireless access type of the called terminal device is GEO access, the called terminal device supports GEO access, the location of the called terminal device is within the GEO coverage area or service area, and receiving indication information from the operating system or application layer or user of the called terminal device; the indication information is used to indicate GEO access or to indicate the transmission of first information.

[0071] Optionally, in one possible implementation of the sixth aspect, the first information is further used to instruct the calling terminal device to notify the user of the calling terminal device of the call setup duration or the radio access type of the called terminal device; or, the first information is further used to instruct the first IMS network element to notify the user of the calling terminal device of the call setup duration or the radio access type of the called terminal device.

[0072] Optionally, in one possible implementation of the sixth aspect, the first information is further used to instruct the second IMS network element to send media to the calling terminal device, the media being used to notify the user of the calling terminal device of the call setup duration or the radio access type of the called terminal device.

[0073] Alternatively, in one possible implementation of the sixth aspect, the called terminal device may also receive an INVITE message or an UPDATE message from the calling terminal device.

[0074] Alternatively, in one possible implementation of the sixth aspect, an INVITE message or an UPDATE message is used to trigger the sending of the first message.

[0075] A seventh aspect of this application provides a communication device, which is a first IMS network element, or a component of the first IMS network element (e.g., a processor, chip, chip system, P-CSCF, S-CSCF, I-CSCF, etc.), or the communication device is a logic module or software capable of implementing all or part of the functions of the first IMS network element. Taking the communication device as a first IMS network element as an example, the first IMS network element includes a transceiver unit. Alternatively, the first IMS network element includes a transceiver unit and a processing unit.

[0076] The transceiver unit is used to receive first information sent by a first core network element or a contracted network element or a called terminal device. The first information is used to indicate the wireless access type of the called terminal device.

[0077] The transceiver unit is also used to send second information to the second IMS network element or the calling terminal device. The second information is used to indicate the call setup time between the calling terminal device and the called terminal device or the radio access type of the called terminal device. The call setup time is related to the radio access type. The second IMS network element is used to serve the calling terminal device.

[0078] Optionally, in one possible implementation of the seventh aspect, the aforementioned transceiver unit is specifically used to send the second information to the second IMS network element or the calling terminal device when the calling terminal device accesses the network via a terrestrial network, or when the first IMS network element does not receive an instruction from the calling terminal device or the second IMS network element to prohibit ringback tones / ringing.

[0079] Optionally, in one possible implementation of the seventh aspect, the aforementioned transceiver unit is specifically used to receive a session initiation message; the transceiver unit is specifically used to send second information to the second IMS network element or the calling terminal device in response to the session initiation message.

[0080] Optionally, in one possible implementation of the seventh aspect, the aforementioned transceiver unit is specifically used to receive a response message to the session initiation message; the transceiver unit is specifically used to send second information to the second IMS network element or the calling terminal device after receiving the response message.

[0081] Optionally, in one possible implementation of the seventh aspect, the aforementioned transceiver unit is further configured to send request information to the first core network element or the subscribed network element, the request information being used to query the wireless access type of the called terminal device.

[0082] Optionally, in one possible implementation of the seventh aspect, the aforementioned second information is used to indicate to the user of the calling terminal device one or more of the following: call setup duration, and the radio access type of the called terminal device.

[0083] Alternatively, in one possible implementation of the seventh aspect, the aforementioned second information is included in the response message of the ringing message or session initiation message.

[0084] Optionally, in one possible implementation of the seventh aspect, the aforementioned transceiver unit is further configured to send third information, which instructs the called terminal device to set to early ringing mode.

[0085] Alternatively, in one possible implementation of the seventh aspect, the aforementioned processing unit is used to determine the call setup duration based on the radio access type of the called terminal device.

[0086] Optionally, in one possible implementation of the seventh aspect, the aforementioned wireless access type includes: satellite or non-satellite, with satellite specifically including one or more of the following: GEO, MEO, LEO.

[0087] The eighth aspect of this application provides a communication device, which is a second IMS network element, or a component of the second IMS network element (e.g., a processor, chip, chip system, P-CSCF, S-CSCF, I-CSCF, MMTel-AS, CAT-AS, etc.), or the communication device is a logic module or software capable of implementing all or part of the functions of a first IMS network element. Taking the communication device as a second IMS network element as an example, the second IMS network element includes a transceiver unit. Alternatively, the second IMS network element includes a transceiver unit and a processing unit.

[0088] The transceiver unit is used to receive second information, which indicates the call setup duration between the calling terminal equipment and the called terminal equipment or the radio access type of the called terminal equipment. The call setup duration is related to the radio access type.

[0089] The transceiver unit is also used to send a fourth message to the calling terminal equipment, which is used to indicate the call setup duration or the wireless access type.

[0090] Alternatively, in one possible implementation of the eighth aspect, the fourth information mentioned above includes media data used to indicate to the user of the calling terminal device the call setup duration or the type of wireless access.

[0091] Optionally, in one possible implementation of the eighth aspect, the aforementioned processing unit is used to determine the fourth information based on the wireless access type of the called terminal device.

[0092] Optionally, in one possible implementation of the eighth aspect, the aforementioned transceiver unit is specifically used to send the fourth information to the calling terminal device after the calling bearer is established.

[0093] Optionally, in one possible implementation of the eighth aspect, the aforementioned wireless access type includes: satellite or non-satellite, with satellite specifically including one or more of the following: GEO, MEO, LEO.

[0094] The ninth aspect of this application provides a communication device that is a calling terminal device, or a component (e.g., a processor, chip, or chip system) of a calling terminal device, or a logic module or software capable of implementing all or part of the functions of a calling terminal device. Taking the calling terminal device as an example, the calling terminal device includes a transceiver unit. Alternatively, the calling terminal device includes a transceiver unit and a processing unit.

[0095] The transceiver unit is used to receive ringtones, which are used to indicate the call setup time between the calling terminal equipment and the called terminal equipment or the wireless access type of the called terminal equipment. The call setup time is related to the wireless access type.

[0096] The processing unit is used to play the ringtone.

[0097] Optionally, in one possible implementation of the ninth aspect, the aforementioned wireless access type includes: satellite or non-satellite, with satellite specifically including one or more of the following: GEO, MEO, LEO.

[0098] The tenth aspect of this application provides a communication device that is a calling terminal device, or a component (e.g., a processor, chip, or chip system) of a calling terminal device, or a logic module or software capable of implementing all or part of the functions of a calling terminal device. Taking the calling terminal device as an example, the calling terminal device includes a transceiver unit. Alternatively, the calling terminal device includes a transceiver unit and a processing unit.

[0099] The transceiver unit is used to receive first indication information, which indicates the call setup duration between the calling terminal equipment and the called terminal equipment or the wireless access type of the called terminal equipment. The call setup duration is related to the wireless access type.

[0100] The processing unit is used to play a ringtone based on the first instruction information.

[0101] Alternatively, in one possible implementation of the tenth aspect, the first instruction information mentioned above is a 183 message.

[0102] Alternatively, in one possible implementation of the tenth aspect, the aforementioned ringtone is used to indicate to the user of the calling terminal device one or more of the following: call setup time, waiting time, and the wireless access type of the called terminal device.

[0103] Alternatively, in one possible implementation of the tenth aspect, the aforementioned ringtone includes one or more of the following: voice, video, and text.

[0104] Optionally, in one possible implementation of the tenth aspect, the aforementioned wireless access type includes: satellite or non-satellite, wherein satellite specifically includes one or more of the following: GEO, MEO, LEO.

[0105] The eleventh aspect of this application provides a communication device, which is a first core network element or a subscribed network element, or a component (e.g., a processor, chip, or chip system) of the first core network element or subscribed network element, or a logic module or software capable of implementing all or part of the functions of the first core network element or subscribed network element. Taking the communication device as a first core network element or subscribed network element as an example, the first core network element or subscribed network element includes a transceiver unit. Alternatively, the first core network element or subscribed network element includes a transceiver unit and a processing unit.

[0106] The transceiver unit is used to receive request information from the first IMS network element. The request information is used to request the wireless access type of the called terminal device.

[0107] The transceiver unit is also used to send fifth information to the first IMS network element. The fifth information is used to indicate that the wireless access type of the called terminal device is geostationary orbit (GEO) access.

[0108] Optionally, in one possible implementation of the eleventh aspect, the aforementioned request information is a location information request (LIR) message, and the fifth information is a location information response (LIA) message.

[0109] Optionally, in one possible implementation of the eleventh aspect, the aforementioned processing unit is used to determine that the wireless access type of the called terminal device is GEO access.

[0110] Optionally, in one possible implementation of the eleventh aspect, the aforementioned processing unit is specifically used to determine that the wireless access type of the terminal device is GEO access based on the subscription information of the called terminal device.

[0111] Optionally, in one possible implementation of the eleventh aspect, the aforementioned wireless access type includes: satellite or non-satellite, with satellite specifically including one or more of the following: GEO, MEO, LEO.

[0112] The twelfth aspect of this application provides a communication device, which is a called terminal device, or a component of the called terminal device (e.g., a processor, chip, or chip system), or the communication device is a logic module or software capable of implementing all or part of the functions of the called terminal device. Taking the called terminal device as an example, the called terminal device includes a transceiver unit. Alternatively, the called terminal device includes a transceiver unit and a processing unit.

[0113] The transceiver unit is configured to send first information when the radio access type of the called terminal device is GEO access. The first information is used to indicate one or more of the following: the radio access type of the called terminal device is GEO access, and the call setup duration; the call setup duration is the call setup duration between the calling terminal device and the called terminal device, and the call setup duration is related to the radio access type.

[0114] Alternatively, in one possible implementation of the twelfth aspect, the aforementioned first information is also used to indicate the media types supported by the called terminal device and / or the calling terminal device.

[0115] Optionally, in one possible implementation of the twelfth aspect, the wireless access type of the called terminal device is GEO access, including: the current wireless access type of the called terminal device is GEO access, the called terminal device supports GEO access, the location of the called terminal device is within the GEO coverage area or service area, and receiving indication information from the operating system or application layer or user of the called terminal device, the indication information being used to indicate GEO access or to indicate the transmission of first information.

[0116] Optionally, in one possible implementation of the twelfth aspect, the aforementioned first information is further used to instruct the calling terminal device to notify the user of the calling terminal device of the call setup duration or the radio access type of the called terminal device, or...

[0117] The first information is also used to instruct the first IMS network element to notify the user of the calling terminal device of the call setup duration or the wireless access type of the called terminal device.

[0118] Optionally, in one possible implementation of the twelfth aspect, the aforementioned first information is further used to instruct the second IMS network element to send media to the calling terminal device, the media being used to notify the user of the calling terminal device of the call setup duration or the radio access type of the called terminal device.

[0119] Optionally, in one possible implementation of the twelfth aspect, the aforementioned transceiver unit is further configured to receive an INVITE message or an UPDATE message from the calling terminal device.

[0120] Alternatively, in one possible implementation of the twelfth aspect, the aforementioned INVITE or UPDATE message is used to trigger the sending of the first message.

[0121] The thirteenth aspect of this application provides a communication device including at least one processor coupled to at least one memory; the at least one memory is used to store a program or instructions; the at least one processor is used to execute the program or instructions to enable the device to implement any possible implementation of any of the first to sixth aspects described above.

[0122] The fourteenth aspect of this application provides a communication device including at least one logic circuit and at least one input / output interface; the logic circuit is used to perform a method as described in any one of the possible implementations of the first to sixth aspects.

[0123] The fifteenth aspect of this application provides a communication system comprising one or more of the following: a communication device that performs any possible implementation of the first aspect, a communication device that performs any possible implementation of the second aspect, a communication device that performs any possible implementation of the third aspect, a communication device that performs any possible implementation of the fourth aspect, a communication device that performs any possible implementation of the fifth aspect, or a communication device that performs any possible implementation of the sixth aspect.

[0124] The sixteenth aspect of this application provides a communication system comprising one or more of the following: a first core network element. The first core network element is used to perform the method of any possible implementation of the fifth aspect described above.

[0125] Optionally, the aforementioned first core network element may include one or more of the following: policy control function (PCF), unified data repository (UDR) element, policy and charging rules function (PCRF) element, home subscriber server (HSS) or home location register (HLR), etc.

[0126] The seventeenth aspect of this application provides a computer-readable storage medium for storing one or more computer-executable instructions, which, when executed by a processor, perform the method as described in any possible implementation of any of the first to sixth aspects above.

[0127] The eighteenth aspect of this application provides a computer program product (or computer program) that, when executed by a processor, performs the method described in any possible implementation of any of the first to sixth aspects described above.

[0128] The nineteenth aspect of this application provides a chip or chip system including at least one processor for supporting a communication device in implementing the method described in any possible implementation of any of the first to sixth aspects.

[0129] In one possible design, the chip system may further include at least one memory for storing program instructions and data necessary for the communication device. The chip system may be composed of chips or may include chips and other discrete components. Optionally, the chip system may also include interface circuitry that provides program instructions and / or data to at least one processor.

[0130] The technical effects of any of the design methods in aspects seven through nineteen can be found in the technical effects of the different design methods in aspects one through six above, and will not be repeated here. Attached Figure Description

[0131] Figure 1 A schematic diagram of the communication system provided in this application;

[0132] Figure 2A Another schematic diagram of the communication system provided in this application;

[0133] Figure 2B Another schematic diagram of the communication system provided in this application;

[0134] Figure 3 A schematic diagram of the architecture of the IMS network provided in this application;

[0135] Figure 4A Another schematic diagram of the communication system provided in this application;

[0136] Figure 4B A schematic diagram of the IMS call setup process provided in this application;

[0137] Figure 5A A schematic diagram of the satellite communication process in the transparent transmission mode provided in this application;

[0138] Figure 5B A schematic diagram of the satellite communication process in the regeneration mode provided in this application;

[0139] Figure 6 A flowchart illustrating the communication method provided in this application;

[0140] Figure 7 Another flowchart illustrating the communication method provided in this application;

[0141] Figure 8 Another flowchart illustrating the communication method provided in this application;

[0142] Figure 9 Another flowchart illustrating the communication method provided in this application;

[0143] Figure 10 Another flowchart illustrating the communication method provided in this application;

[0144] Figures 11 to 14 Several other flowcharts illustrating the communication method provided in this application;

[0145] Figures 15 to 17 Several structural schematic diagrams of the communication device provided in this application. Detailed Implementation

[0146] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0147] First, some terms used in the embodiments of this application will be explained to facilitate understanding by those skilled in the art.

[0148] 1. In this application, "for indicating" can include both direct and indirect indication. When describing an indication information as indicating A, it can be understood that the indication information carries A, directly indicates A, or indirectly indicates A.

[0149] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementation, there are many ways to instruct the information to be instructed. For example, it can be implemented through direct instruction, such as through the information to be instructed itself or its index. It can also be implemented indirectly by instructing other information, where there is a relationship between the other information and the information to be instructed. Alternatively, only a part of the information to be instructed can be indicated, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent.

[0150] The information to be indicated can be sent as a whole or divided into multiple sub-information messages, and the sending period and / or timing of these sub-information messages can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device. This configuration information can include, for example, but not limited to, one or a combination of at least two of RRC signaling, medium access control (MAC) layer signaling, and physical layer signaling. MAC layer signaling includes, for example, MAC CE; physical layer signaling includes, for example, downlink control information (DCI).

[0151] 2. In the embodiments of this application, "sending" and "receiving" indicate the direction of signal transmission. In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be IMS network elements, core network elements, or terminals, or modules within an IMS network element, core network element, or terminal. Information sending and receiving can be information interaction between an IMS network element / core network element and a terminal, for example, information interaction between an IMS network element / core network element and a terminal; information sending and receiving can also be information interaction between two RAN nodes, such as information interaction between a CU and a DU; information sending and receiving can also be information interaction between different modules within a device, for example, information interaction between a terminal chip and other modules of the terminal, or information interaction between an IMS network element / core network element chip and other modules within that IMS network element / core network element. "Sending" can also be understood as the "output" of the chip interface, such as the baseband chip outputting information to the radio frequency chip, and "receiving" can also be understood as the "input" of the chip interface; for example, "sending" can also be understood as the baseband part inside the device outputting information to the radio frequency part, and "receiving" can also be understood as the radio frequency part inside the device receiving the information output by the baseband part.

[0152] 3. The terms "system" and "network" in the embodiments of this application can be used interchangeably. "At least one" and "one or more" can be used interchangeably, referring to one or more, while "more" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects have an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, "at least one of A, B, and C" includes A, B, C, AB, AC, BC, or ABC. Furthermore, unless otherwise specified, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the order, sequence, priority, or importance of multiple objects. Additionally, "information" in the embodiments of this application can also be replaced with messages or data, etc.

[0153] 4. Internet Protocol (IP) Multimedia Subsystem (IMS)

[0154] IMS can be understood as a standardized architecture framework that provides IP multimedia services.

[0155] Please see Figure 1 This application provides a system architecture. This system architecture includes: terminal equipment, radio access network (RAN) equipment, core network (CN), and digital network (DN).

[0156] The Core Network (CN) is responsible for maintaining the subscription data of the mobile network, managing the network elements of the mobile network, and providing terminal devices with functions such as session management, mobility management, policy management, and security authentication. When a terminal device attaches, it provides network access authentication; when a terminal device makes a service request, it allocates network resources to the terminal device; when a terminal device moves, it updates network resources for the terminal device; when a terminal device is idle, it provides a fast recovery mechanism; when a terminal device detaches, it releases network resources for the terminal device; and when a terminal device has service data, it provides data routing functions, such as forwarding uplink data to the data network; or receiving downlink data from the terminal device from the data network and forwarding it to the radio access network (RAN) to send it to the terminal device. Furthermore, the network elements included in the core network may vary depending on the applicable communication system, which will be discussed later. Figure 2A and Figure 2B The network elements included in the core network are described exemplarily.

[0157] A radio access network (RAN) can be understood as an access network that uses wireless communication technology to provide network access functions. RAN manages radio resources, provides access services to terminal devices, and facilitates the forwarding of control signals and user data between terminal devices and the core network.

[0158] A data network (DN) provides services to terminal devices. Typically, the client is located on the terminal device, and the server is located on the data network. A data network can be a private network, such as a local area network (LAN), an external network not controlled by the operator, such as the Internet, or a proprietary network jointly deployed by operators, such as a network providing IMS services. In short, a data network is used to provide data transmission. Examples include operator networks, the Internet, and third-party service networks.

[0159] In this embodiment of the application, the terminal device may be a wireless terminal device capable of receiving network device scheduling and instruction information. The wireless terminal device may be a device that provides voice and / or data connectivity to the user, or a handheld device with wireless connection function, or other processing device connected to a wireless modem.

[0160] Optionally, the terminal device can be a communication kit with wireless communication capabilities (the kit may include, for example, an antenna, a power supply module, cables, and a Wi-Fi module). The terminal device can also be a communication module with satellite communication capabilities, a satellite phone or a component thereof, or a very small aperture terminal (VSAT). The terminal device can be a mobile terminal device, such as a mobile phone (or "cellular" phone), a computer, or a data card. For example, it can be a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device that exchanges voice and / or data with a wireless access network. Examples include personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), tablets, and computers with wireless transceiver capabilities. Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station (MS), remote station, access point (AP), remote terminal, access terminal, user terminal, user agent, subscriber station (SS), customer premises equipment (CPE), terminal, user equipment (UE), mobile terminal (MT), drone, etc. Terminal equipment can also be wearable devices and next-generation communication systems, such as terminal equipment in future communication systems or terminal equipment in future evolved public land mobile networks (PLMNs). Of course, in this application, terminal equipment can also refer to chips, modems, system-on-a-chip (SoC), or communication platforms that may include radio frequency (RF) components, etc., that are primarily responsible for related communication functions.

[0161] Network devices can be devices within a wireless network. For example, a network device can be a radio access network (RAN) node (or device) that connects terminal devices to the wireless network, and can also be called a base station. Currently, some examples of RAN devices include: next-generation base stations, transmission reception points (TRPs), evolved Node Bs (eNBs), radio network controllers (RNCs), Node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved Node Bs, or home Node Bs (HNBs)), base band units (BBUs), or wireless fidelity (Wi-Fi) access points (APs), etc. Additionally, in a network architecture, network devices can include centralized unit (CU) nodes, distributed unit (DU) nodes, or RAN devices that include both CU and DU nodes.

[0162] In some implementations, the network equipment may also include satellites, aircraft, drones, and ground station equipment connected to satellites, aircraft, and drones.

[0163] Optionally, the network device can send configuration information (e.g., carried in scheduling messages and / or indication messages) to the terminal device, and the terminal device further configures the network according to the configuration information, so that the network configurations of the network device and the terminal device are aligned; or, the network configurations of the network device and the terminal device can be aligned through preset network configurations on the network device and preset network configurations on the terminal device. Specifically, "alignment" means that when there are interactive messages between the network device and the terminal device, their understanding of the carrier frequency for sending and receiving interactive messages, the determination of the interactive message type, the meaning of the field information carried in the interactive message, or other configurations of the interactive message is consistent.

[0164] Furthermore, in other possible cases, the network device can be any other device that provides wireless communication functionality to the terminal device. The embodiments of this application do not limit the specific technology or device form employed by the network device.

[0165] In this application embodiment, the device for implementing the function of the network device can be the network device itself, or it can be a device capable of supporting the network device in implementing that function, such as a chip system, which can be installed in the network device. In the technical solutions provided in this application embodiment, the example of a network device being used to implement the function of the network device is used to describe the technical solutions provided in this application embodiment.

[0166] Alternatively, logically, Figure 1 The system architecture shown can be divided into two parts: the user plane and the control plane. The control plane is responsible for the management of the mobile network, while the user plane is responsible for the transmission of service data.

[0167] Understandable, Figure 1 The connections shown are just examples of some scenarios. In future communication systems, for instance, terminal devices may communicate directly with the core network. Similarly, wireless access network devices may communicate directly with the data network.

[0168] In one possible implementation method Figure 1 The system architecture shown can be specifically as follows: Figure 2A The diagram shows the 4G system architecture. The network elements / equipment in this 4G system architecture include: terminal equipment ( Figure 2A Taking the UE as an example, the key network elements include: Mobility Management Entity (MME), Serving GPRS Support Node (SGSN), Home Subscriber Server (HSS), Serving Gateway (SGW or S-GW), Public Data Network Gateway (PDN Gateway, PGW or P-GW), Policy and Charging Rules Function (PCRF) entity, and Evolved Universal Terrestrial Radio Access Network (E-TURAN). The following is an introduction to key 4G network elements:

[0169] E-UTRAN includes multiple evolved nodeBs (eNodeBs). The eNodeBs are interconnected with each other through the X2 interface, and the eNodeBs are interconnected with the evolved packet core (EPC) through the S1 interface. The eNodeBs are interconnected with terminal equipment through LTE-Uu.

[0170] The main functions of the MME are to support NAS messages and their security, management of the track area (TA) list, selection of P-GW and S-GW, selection of MME during handover across MMEs, selection of SGSN during handover to 2G / 3G access systems, authentication of terminal devices, roaming control and bearer management, and mobility management between core network nodes of different access networks under the 3rd Generation Partnership Project (3GPP).

[0171] An S-GW is a gateway terminating at the E-UTRAN interface. Its main functions include: serving as a local anchor point during inter-base station handovers and assisting in base station reordering; serving as a mobility anchor point during handovers between different 3GPP access systems; performing lawful eavesdropping; routing and forwarding data packets; performing packet marking at the uplink and downlink transport layers; and being used for inter-carrier billing, etc.

[0172] A P-GW is a gateway that terminates at the SGi interface for a PDN. If an end device accesses multiple PDNs, it will correspond to one or more P-GWs. The main functions of a P-GW include packet filtering based on the end device, lawful eavesdropping, Internet Protocol (IP) address allocation for interconnection between end devices, packet delivery level marking in the uplink, uplink and downlink service level accounting and service level threshold control, and service-based uplink and downlink rate control.

[0173] HSS is a database used to store subscription information of terminal devices. The home network can contain one or more HSSs. HSS is responsible for storing information related to terminal devices, such as terminal device identifier, number and routing information, security information, location information, profile information, etc.

[0174] The SGSN can be used for signaling interaction when moving between 2G / 3G and E-UTRAN 3GPP access networks, including the selection of P-GW and S-GW, and the selection of MME for terminal equipment switching to E-UTRAN 3GPP access networks.

[0175] PCRF entities terminate at the Rx and Gx interfaces. In non-roaming scenarios, within the home public land mobile network (HPLMN), there is only one PCRF associated with one IP-connectivity access network (IP-CAN) session of the terminal device. In roaming scenarios where the service flow is localized, there may be two PCRFs associated with one terminal device's IP-CAN session.

[0176] In another possible way of implementation Figure 1 The system architecture shown can be specifically as follows: Figure 2B The diagram illustrates the 5G system architecture. The network elements / devices in this 5G system architecture include: terminal equipment ( Figure 2B Taking UE as an example, the network elements include DN, RAN, network slice selection function (NSSF), network exposure function (NEF), network repository function (NRF), policy control function (PCF), unified data management (UDM), application function (AF), authentication server function (AUSF), access and mobility management function (AMF), session management function (SMF), service communication proxy (SCP), and user plane function (UPF).

[0177] Optionally, Figure 2BThe system architecture shown may also include other network elements not shown in the following figures, such as network slice-specific authentication and authorization function (NSSAAF) network elements, network slice admission control function (NSACF) network elements, unified data storage (UDR) network elements, etc., which are not limited here.

[0178] The following is an introduction to several key network elements included in 5G CN:

[0179] 1. AMF network element: responsible for user mobility management, including mobility status management, assigning temporary user identities, authenticating and authorizing users.

[0180] 2. UDM network element: Responsible for managing contract data. When the contract data is modified, it is responsible for notifying the corresponding network element.

[0181] 3. NSSF network element: responsible for selecting network slices.

[0182] 4. SMF network element: Responsible for user plane (UP) network element selection, UP network element reselection, Internet Protocol (IP) address allocation, session establishment, modification and release, and Quality of Service (QoS) control.

[0183] 5. AUSF network element: mainly responsible for network security, used to generate keys, realize two-way authentication for UE, and realize 3GPP and non-3GPP access authentication.

[0184] 6. NEF Network Elements: Open up the capabilities of various network elements, transform internal and external information, and use them for edge computing scenarios.

[0185] 7. PCF network element: mainly used for managing policy rules and user subscription information, etc.

[0186] 8. UDR Network Element: Stores and retrieves subscription data, policy data, and public architecture data, providing relevant data to UDM, PCF, and NEF. The UDR should have different data access authentication mechanisms for different types of data, such as subscription data and policy data, to ensure data access security. The UDR should be able to return a failure response with an appropriate reason value for illegal service operations or data access requests.

[0187] 9. NRF Network Element: Responsible for the registration and discovery functions of network elements, and maintaining information about the network element, such as the instance identifier, type, PLMN, slice-related identifiers, IP address or fully qualified domain name (FQDN), the capabilities of the network element, and supported services.

[0188] 10. AF Network Element: Primarily used to send data routing information affecting applications to the network, and to perform policy control through interaction with the policy framework via network open function network elements.

[0189] 11. UPF Network Element: Interconnects Protocol Data Unit (PDU) sessions with the data network, performs packet routing and forwarding, and detects packets.

[0190] To facilitate understanding, the similarities between 4G and 5G architectures are described below. For example, the 4G MME functions similarly to the 5G AMF+SMF. That is, the MME can be understood as AMF+SMF. Similarly, the 4G SGW is similar to the 5G UPF and also has some SMF functions. Likewise, the 4G PGW is similar to the 5G UPF and also has some SMF functions. The 4G PCRF is similar to the 5G PCF. The 4G SCEF is similar to the 5G PCF. The 4G HSS is similar to the 5G UDM. Furthermore, the 4G HSS is similar to the Home Location Register (HLR) in the Global System for Mobile Communications (GSMC).

[0191] For example, the 5G architecture can be found in 3GPP TS23.501, and the 4G architecture can be found in 3GPP TS23.401.

[0192] It is understood that the network architecture applicable to the embodiments of this application is not limited to... Figure 2A or Figure 2B Any network architecture or future mobile network architecture capable of implementing the functions of the aforementioned network elements is applicable to the embodiments of this application. Furthermore, the network elements included in the core network can be independent devices or integrated into the same device to implement different functions; this application does not limit the specific form of the aforementioned network elements.

[0193] This application can be applied to long term evolution (LTE) systems, new radio / new radio (NR) systems, or new radio vehicle to everything (NR V2X) systems; it can also be applied to systems with hybrid LTE and 5G networks; or device-to-device (D2D) communication systems, machine-to-machine (M2M) communication systems, Internet of Things (IoT) systems, or drone communication systems; or communication systems that support multiple wireless technologies, such as those supporting LTE and NR technologies; or non-terrestrial network (NTN) systems, such as satellite communication systems and high-altitude communication platforms. Alternatively, this communication system can also be applied to narrowband Internet of Things (NB-IoT), enhanced data rate for GSM evolution (EDGE), wideband code division multiple access (WCDMA), code division multiple access 2000 (CDMA2000), time division-synchronization code division multiple access (TD-SCDMA), and future-oriented communication technologies.

[0194] It should be noted that the above naming is defined solely for the purpose of distinguishing different functions and should not constitute any limitation on this application. This application does not preclude the possibility of using other naming conventions in 5G networks and other future networks. For example, in future communication networks, some or all of the above-mentioned network elements may use the terminology from 5G, or they may use other names, etc. Figures 1 to 2B The interface names between the various network elements are merely examples; in actual implementations, the interface names may differ, and this application does not impose any specific limitations on them. Furthermore, the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0195] It is understandable that the above Figure 2A and Figure 2B only Figure 1 Two examples of system architecture, in practical applications, Figure 1 The system architecture shown can also take other forms, which are not limited here.

[0196] For example, the above Figures 1 to 2B The DN in this context can be an IMS network. IMS is one of the core technologies of network communication, capable of meeting the needs of terminals for newer and more diversified multimedia services. It is an important way to solve the convergence of mobile and fixed networks and introduce differentiated services such as voice, data, and video triple convergence. The following section will combine... Figure 3 A brief introduction to the IMS network.

[0197] Figure 3 A schematic diagram of the IMS network architecture, as shown below. Figure 3 As shown, the IMS network may include: a telephony application server (TAS), a proxy-call session control function (P-CSCF / PCSCF) entity, a serving-call session control function (S-CSCF / SCSCF) entity, an IMS access gateway (IMS-AGW), a transition gateway (TrGW), an interconnection border control function (IBCF) entity, a breakout gateway control function (BGCF) entity, a media gateway control function (MGCF) entity, etc.

[0198] For example, the IMS architecture can be found in 3GPP TS23.228.

[0199] TAS provides voice and multimedia calling services for users of fixed and mobile converged networks, supports related basic and supplementary services, integrates fixed and mobile converged services on the same platform, and provides a unified service experience for fixed and mobile network users.

[0200] The S-CSCF entity is the central node of the IMS network, responsible for user registration, authentication, sessions, routing, and service triggering. The S-CSCF entity is the service switching center of the IMS network, primarily responsible for receiving and processing UE registration requests, user management, session control, service switching, service control, session initiation protocol (SIP) message processing, billing, etc., and can trigger SIP requests to the corresponding application server (AS) according to the application's triggering principles.

[0201] The P-CSCF entity is the entry point for SIP users to access the IMS network, primarily responsible for forwarding SIP signaling between the SIP user and the home network. The P-CSCF entity is the first point of contact for users accessing the IMS network during service applications. It is responsible for proxying SIP signaling and performing call routing control; providing QoS resource reservation; supporting SIP signaling compression to improve bandwidth utilization efficiency of the air interface; providing NAT control to support NAT traversal for enterprise networks; and maintaining a security association with the UE to protect the privacy and integrity of signaling between the UE and the UE.

[0202] IMS-AGW is the IMS access gateway, primarily responsible for media plane interoperability between the user and network interfaces.

[0203] TrGW is the IMS interconnection gateway, responsible for media plane interconnection between network interfaces.

[0204] The IBCF entity is primarily used to enable interoperability between the IMS network and other IMS network control planes. For example, if the calling party is on China Mobile's IMS network and the called party is on China Telecom's IMS network, the BGCF entity is responsible for selecting an MGCF entity for the call to connect to the CS network when the calling party is an IMS user and the called party is a circuit-switched (CS) network user.

[0205] The MGCF entity is primarily used to enable interoperability between the IMS network and the control plane of other non-IP networks (such as the public switched telephone network, PSTN).

[0206] It should be noted that, in other embodiments, the IMS network may further include the following: Figure 3Other network elements not shown in the diagram may include one or more of the following: interrogating-call session control function (I-CSCF / ICSCF), multimedia telephony application server (MMTel-AS), and customized alerting tone application server (CAT-AS), etc., without being specifically limited here.

[0207] The I-CSCF can be understood as the unified entry point of the user's home network, responsible for the allocation of S-CSCFs and the query of the called party's S-CSCF. It also performs IMS inter-domain topology hiding. The MMTel-AS provides basic and supplementary multimedia telephony services; it also provides Terminating Access Domain Selection (T-ADS) functionality, enabling the network side to select the called party's domain. CAT-AS can be the same as MMTel-AS, or have similar functionality.

[0208] It is understandable that other networks besides IMS (such as CS or IMS) can also be referred to as B party when acting as the caller or the called party in real-time audio and video communication.

[0209] above Figure 3 This section only describes the IMS network; the following section uses UE-A and UE-B as examples to further describe the entire communication system. Please refer to [link / reference]. Figure 4A Another communication system provided in this application includes: UE-A, core network element serving UE-A, IMS network, UE-B, and core network element serving UE-B.

[0210] The core network element serving UE-A can be PCRF-A / PCF-A, and the core network element serving UE-B can be PCRF-B / PCF-B. The IMS network includes IMS network elements serving UE-A and IMS network elements serving UE-B. The IMS network elements serving UE-A include one or more of the following: PCSCF-A / SCSCF-A, Interrogating-call session control function (ICSCF)-A, and HLR / HSS. The IMS network elements serving UE-B include one or more of the following: PCSCF-B / SCSCF-B, ICSCF-B, and HLR / HSS. Each network element can be referred to in the preceding description and will not be repeated here.

[0211] It should be noted that, Figure 4A Taking the HLR / HSS located in the IMS network as an example (which can also be called converged HLR / converged HSS), in other embodiments, the HLR / HSS can also be a core network element.

[0212] Optionally, UE-A can also be referred to as the calling terminal equipment, and UE-B can be referred to as the called terminal equipment. Correspondingly, the core network elements serving UE-A can also be referred to as the calling core network elements, and the core network elements serving UE-B can also be referred to as the called core network elements. Similarly, the IMS network elements serving UE-A can also be referred to as the calling IMS network elements, and the IMS network elements serving UE-B can also be referred to as the called IMS network elements. Alternatively, it can be understood that network elements with "-A" in their name serve the calling UE-A, while those with "-B" serve the called UE-B.

[0213] Optionally, the HLR / HSS can be located within the IMS network or the core network. The HLR / HSS is a shared network element that stores the subscription data of both the calling terminal equipment and the called terminal equipment.

[0214] For example, the call setup procedure between UE-A and UE-B can be as follows: Figure 4B As shown below, Figure 4B The steps involved are described below:

[0215] Step 0:

[0216] On Figure 4B Before the process begins, both UE-A and UE-B need to register with the core network and the IMS network (these are two separate processes). After these two registrations are completed, UE-A and UE-B each establish a default bearer to the IMS network. The default bearer is used to send signaling, does not guarantee service experience, and cannot be used to send media data such as ringtones or user voice messages.

[0217] Step 1:

[0218] The calling UE-A initiates a call (makes a phone call) to the called UE-B and sends an INVITE message.

[0219] The INVITE message is a Session Description Protocol (SDP) message that is transmitted in the default bearer established between the calling and called parties.

[0220] Steps 2-3:

[0221] After the INVITE message arrives at PCSCF-A, PCSCF-A sends an AAR message to PCRF-A, providing some user-related information.

[0222] Step 4:

[0223] SCSCF-A sends an INVITE message to ICSCF-B. (SCSCF-A can look up the address of ICSCF-B from HSS.)

[0224] Steps 5-6:

[0225] After receiving the INVITE message, ICSCF-B queries HSS for the address of PCSCF-B / SCSCF-B and forwards the INVITE message to PCSCF-B / SCSCF-B.

[0226] Step 7:

[0227] PCSCF-B sends an AAR message to PCRF-B, instructing PCRF-B to establish a dedicated bearer for UE-B (for subsequent transmission of media data such as ringtones and user voice).

[0228] Step 8:

[0229] After receiving the response from PCRF-B, PCSCF-B sends an INVITE message to UE-B.

[0230] Step 9-12b:

[0231] After receiving the INVITE message, UE-B responds with a 183 message.

[0232] The 183 message arrives at PCSCF-B first. Upon receiving the 183 message, PCSCF-B triggers the establishment of the called party's dedicated bearer. At the same time, PCSCF-B continues to forward the 183 message to PCSCF-A.

[0233] After receiving the 183 message, PCSCF-A triggers the establishment of the calling dedicated bearer and forwards the 183 message to UE-A.

[0234] (That is, the establishment of the dedicated bearer for the called party and the calling party can be carried out simultaneously).

[0235] Step 11 is optional. The 180 message is a ringing message, which triggers the calling network element to send a ringing tone to the calling UE. (After the 180 message arrives at SSCCF-A or ICSCF-A, it will trigger the network element playing the ringing tone to send the ringing tone to UE-A through a dedicated bearer, for example, sending the ringing tone to UE-A after the calling dedicated bearer is established; see the next chapter for details. The 180 message will also arrive at UE-A as a response.) There are two ringing modes: early ringing and late ringing, corresponding to sending the 180 ringing message in steps 11 and 15, respectively.

[0236] Step 13:

[0237] The PRACK message, as the caller's response to the 183 message, indicates to the called party that the caller's dedicated bearer has been established.

[0238] Step 14:

[0239] A 200 message, as the called party's response to a PRACK message, indicates to the calling party that the called party's dedicated bearer has been established.

[0240] Step 15:

[0241] When the UE-B rings late, it sends a 180 message after the 200 message to indicate the ringing.

[0242] Steps 16-17:

[0243] After the called party answers the phone, UE-B sends a 200 message to UE-A. This 200 message is a response to the INVITE message (different from the previous 200 message), indicating that the called party has answered the phone and the subsequent call connection process will be executed.

[0244] Optionally, based on the above IMS call setup procedure, after the called party sends a 180 message, the calling network element will trigger a ringing sound and send media data as a ringtone to the calling UE. In addition to supporting basic ringtones (beep sounds), the 3GPP standard also defines the procedure for playing custom ringtones, see 3GPP TS24.182 for details. Regarding the triggering of custom ringtones, in... Figure 4B In step 14, in message 200, UE-B indicates that it needs to be used as a ringback tone medium. After message 180 in step 15 arrives at SSCCF-A, SSCCF-A will forward message 180 to the network element playing the ringtone (MMTel AS or CAT-AS), instructing it to send the corresponding ringtone medium to UE-A.

[0245] Furthermore, the technical solutions of this application embodiment can also be applied to communication systems that integrate terrestrial and satellite communications, which can also be called non-terrestrial network (NTN) communication systems. In other words, Figures 1 to 2B The RAN in this context can include terrestrial base stations. Terrestrial communication systems can be, for example, long-term evolution (LTE) systems, universal mobile telecommunication systems (UMTS), 5G communication systems, new radio (NR) systems, or future communication systems that are the next step in the development of 5G communication systems; no specific limitations are imposed here.

[0246] Among these advantages, satellite communication offers wider coverage compared to traditional mobile communication systems. Communication costs are independent of transmission distance, and it can overcome natural geographical barriers such as oceans, deserts, and mountains. To overcome the shortcomings of traditional communication networks, satellite communication can serve as an effective supplement. It is generally believed that non-terrestrial network communication has different channel characteristics compared to terrestrial network communication, such as large transmission delays and Doppler frequency offset.

[0247] Optionally, satellite communication systems can be categorized into three types based on their orbital altitude: geostationary earth orbit (GEO) satellite communication systems (or synchronous orbit satellite systems), medium earth orbit (MEO) satellite communication systems, and low earth orbit (LEO) satellite communication systems. For example, the round-trip time latency for GEO satellite communication is 238–270 milliseconds (ms). The round-trip time latency for LEO satellite communication is 8 ms–20 ms. Furthermore, NTN systems may also include highly elliptical orbit (HEO) satellites, high altitude platform station (HAPS) communication systems, and other aerial network equipment; specific details are not limited here.

[0248] GEO satellites, also known as high-orbit satellites, orbit at an altitude of 35,786 kilometers. Their main advantages are relative stationary position and large coverage area. However, GEO satellites also have significant drawbacks: the large distance from Earth necessitates larger antennas; their transmission latency is relatively high, with a round-trip time of around 0.5 seconds, failing to meet the demands of real-time services; and their orbital resources are relatively scarce, resulting in high launch costs and an inability to provide coverage to polar regions. MEO satellites, orbiting at altitudes between 2,000 and 35,786 kilometers, can achieve global coverage with a relatively small number of satellites, but their transmission latency is higher than that of LEO satellites, and they are primarily used for positioning and navigation. Furthermore, satellites orbiting at altitudes between 300 and 2,000 kilometers are called low-orbit (LEO) satellites. LEO satellites are lower in altitude than MEO and GEO satellites, resulting in lower data propagation latency, lower power loss, and relatively lower launch costs. Therefore, LEO satellite communication networks have made significant progress and attracted considerable attention in recent years.

[0249] In addition, satellite equipment can be divided into transparent mode and regenerative mode according to its working mode.

[0250] For example, Figure 5A This is an example of a transparent payload mode (or transparent mode) combining an NTN communication system with an IMS network. The system architecture in this example includes: terminal equipment, satellite, gateway station (also called a ground station, earth station, etc.), base station, core network, and IMS network.

[0251] Specifically, satellites and gateway stations can act as relays for communication between terminal devices and base stations, transparently transmitting signals between the satellite and the terminal device. For example, a gateway station can access the core network through a base station, and then access the IMS network. In transparent transmission mode, the satellite only performs transparent forwarding. Figure 5A The description of the system architecture for each network element / device can be referenced above, and will not be repeated here.

[0252] For example, Figure 5B This is an example of a regenerative mode combining an NTN communication system with an IMS network. The system architecture in this example includes: terminal equipment, a satellite ("base station onboard") gateway, a core network, and an IMS network. Specifically, in regenerative mode, the satellite needs to possess all or some of the functions of a base station. Figure 5BThe network elements / devices described above can be referred to, and will not be repeated here. For example, in the regeneration mode, not only can the base station be deployed on a satellite, but some or all of the network elements in the core network and IMS network can also be deployed on the same or different satellites as the base station.

[0253] It should be understood that Figures 1 to 5B The number of each device / network element mentioned is just an example. In actual applications, the specific number of devices / network elements included in each of the above systems is not limited here.

[0254] As mentioned above, terminal devices can make calls via IMS. In satellite communication systems, terminal devices can make IMS calls via satellite. Currently, based on their orbital altitude, satellite communication systems can be classified into three types: GEO satellite communication systems (or geostationary orbit satellite systems), MEO satellite communication systems, and LEO satellite communication systems. For example, the round-trip time delay for GEO satellite communication is 238–270 milliseconds (ms), while the round-trip time delay for LEO satellite communication is 8 ms–20 ms.

[0255] However, when a calling terminal device makes an IMS call to a called terminal device via satellite, especially in GEO satellite communication scenarios, the latency is relatively long. This can cause the calling terminal device, acting as a user making a call, to potentially assume there is a network problem or that the called party is offline, and thus hang up the phone.

[0256] For example, if the called party is in GEO coverage and the caller is using terrestrial access, the latency caused by GEO may result in a call setup delay of approximately 20-30 seconds. This means that after the caller dials the number, there may be no sound for 20-30 seconds (corresponding to late ringing) or only a beeping sound without anyone answering (corresponding to early ringing). For example, during early ringing... Figure 4B In a typical call, the 180 ringback message is sent first to the calling party, who hears a beep. However, because the called party's bearer has not yet been established, the calling party only hears the beep, while the called party's ringtone remains silent (the called party's bearer establishment process is incomplete). The calling party might assume the called party is not answering, but in reality, the called party's bearer establishment process is incomplete. Similarly, during late-night ringing, the beeping sound that occurs during normal calls while waiting for the called party to answer will not be heard; this sound is triggered by the 180 ringback message.

[0257] To address the aforementioned technical problems, embodiments of this application provide a communication method and related apparatus. A first IMS network element serving the called terminal device can receive first information sent by a first core network element, a subscribed network element, or the called terminal device to determine the wireless access type of the called terminal device. This information is then sent to a second IMS network element or the calling terminal device to indicate the call setup time between the calling and called terminal devices or the access type of the called terminal device. This allows the calling terminal device to wait patiently, reducing the probability of the calling terminal device mistakenly believing there is a network problem or that the called terminal device is offline and thus hanging up.

[0258] The IMS network element in this embodiment may include Figures 2A to 4A At least one IMS network element, and core network elements may include Figures 2A to 4A At least one core network element in the network.

[0259] For example, the first IMS network element may include one or more of the following: PCSCF-B, SSCCF-B, ICSCF-B, MMTelAS, or CAT-AS, etc. Correspondingly, the second IMS network element may include one or more of the following: PCSCF-A, SSCCF-A, ICSCF-A, MMTelAS, or CAT-AS, etc. As another example, the first core network element may include one or more of the following: 4G PCRF-B, 5G PCF-B, UDR, HLR / HSS / UDM, policy network element, policy management network element, or storage network element, etc. Subscribed network elements may include one or more of the following: converged HLR / converged HSS / converged UDM / HLR / HSS / UDM. Alternatively, a subscribed network element can be an IMS network element in the IMS network (which can be called a converged HLR / converged HSS / converged UDM), a core network element in the core network, or an independent network element separate from the IMS network and core network elements; the specifics are not limited here. The terminal equipment (the calling terminal equipment and / or the called terminal equipment) can be an LTE terminal, NR terminal, NB-IoT terminal, etc., and there is no specific limitation here.

[0260] Additionally, the second IMS network element may also include MMTel AS-B. Alternatively, it can be understood that the second IMS network element can also serve the called terminal equipment. For example, MMTel AS-B can send a ringtone to the calling terminal equipment. In other words, MMTel AS-B can serve not only the called terminal equipment but also the calling terminal equipment.

[0261] Please see Figure 6This application provides a flowchart illustrating a communication method, which may include steps 601 to 604. Steps 601 to 604 can be executed by a communication device, or by some components of the communication device (e.g., a processor, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the communication device. The following description uses execution by a communication device as an example. The processing performed by a single execution entity in steps 601 to 604 can also be divided into multiple execution entities, which can be logically and / or physically separated. For example, when the communication device is an access network device, the processing performed by the communication device can be divided into execution by at least one of the functions such as CU, DU, and RU. As another example, when the communication device is a 4G core network device, the processing performed by the communication device can be divided into execution by at least one of the network elements such as MME or PCRF. As yet another example, when the communication device is a 5G core network device, the processing performed by the communication device can be divided into execution by at least one of the network elements such as SMF or PCF. For example, when the communication device is an IMS network element, the processing performed by the communication device can be divided and executed by at least one network element in the IMS network. This method can be applied to the aforementioned... Figures 1 to 5B In any of the system architectures shown, the specifics are not limited here.

[0262] Due to the long intervals between the steps, steps 601 to 604 are briefly described here first, and then described in detail later. Step 601: The first core network element or subscribed network element sends the first information to the first IMS network element. Step 6021: The first IMS network element sends the second information to the second IMS network element. Step 603: The second IMS network element sends the fourth information to the calling terminal device. Step 6022: The first IMS network element sends the second information to the calling terminal device. Step 604: The calling terminal device plays a ringtone based on the second or fourth information. The following is a detailed description of each step:

[0263] Step 601: The first core network element, the contracted network element, or the called terminal device sends the first information to the first IMS network element.

[0264] In this embodiment, the first IMS network element and the first core network element or the subscribed network element are used to serve the called terminal equipment, and the second IMS network element and the second core network element are used to serve the calling terminal equipment. Alternatively, it can be understood that network elements marked "first" are used to serve the called terminal equipment, and network elements marked "second" are used to serve the calling terminal equipment. Of course, sometimes network elements marked "second" can serve both the calling and called terminal equipment. Similarly, sometimes network elements marked "first" can serve both the called and called terminal equipment. For example, the MMTel AS described previously.

[0265] In this context, the network element marked with "first" and the network element marked with "second" can be the same network element or different network elements. For example, if the first IMS network element and the second IMS network element are the same IMS network element, this IMS network element can be used not only to serve the calling and receiving terminal devices, but also to serve the called terminal device.

[0266] For example, the IMS network element used to serve terminal equipment can be interpreted as: the network element selected by the terminal equipment when registering for IMS. Or it can be interpreted as the network element responsible for receiving session initiation or 183 messages from the terminal equipment.

[0267] The first core network element or subscribed network element sends the first information to the first IMS network element. Correspondingly, the first IMS network element receives the first information sent by the first core network element, subscribed network element, or called terminal device. This first information indicates one or more of the following: the radio access type of the called terminal device, and the call setup duration; the call setup duration is the call setup duration between the calling terminal device and the called terminal device, and the call setup duration is related to the radio access type.

[0268] Optionally, the first information may also have other functions, such as instructing the calling terminal to play media indicating the call setup time or the access type of the called terminal.

[0269] For example, it can be used to indicate the call waiting time of the calling terminal device, to instruct the user of the calling terminal device to wait patiently, or to indicate the generation of a special ringtone (to indicate the call waiting time of the user of the calling terminal device, or to remind the user of the calling terminal device to wait patiently), etc. This allows the first IMS network element to clearly understand the purpose of subsequently sending the second information after receiving the first information.

[0270] For example, the first information is also used to indicate the media types supported by the called terminal equipment and / or the calling terminal equipment. This media type may include one or more of the following: SDP-B, SDP-A, encoding methods, etc. Here, SDP-A is the media type supported by the calling terminal equipment, and SDP-B is the media type supported by the called terminal equipment.

[0271] For example, the first information can also be used to instruct certain network elements or devices to trigger a notification. For instance, the first information can also be used to instruct the calling terminal device to notify its user of the call setup duration or the radio access type of the called terminal device. For instance, the first information can also be used to instruct the first IMS network element to notify the calling terminal device's user of the call setup duration or the radio access type of the called terminal device.

[0272] For example, the first information is also used to instruct the second IMS network element to send media to the calling terminal device. The media is used to notify the user of the calling terminal device of the call setup duration or the radio access type of the called terminal device. Alternatively, it can be understood that the called terminal device sends the first information to the called IMS network element, thereby causing the called IMS network element to instruct the calling IMS network element to send media to the calling terminal device.

[0273] The ringtone in this embodiment can also be replaced with indication information, signaling messages, or media information, such as video, audio, text, images, vibration, etc., and no specific limitation is made here.

[0274] It should be noted that in the embodiments of this application, "sending" or "receiving" only refers to the transmission of information. This can be direct interaction between the two network elements or indirect interaction between the two network elements through other network elements. For example, the first core network element can directly send the first information to the first IMS network element, or it can forward the first information to the first IMS network element through other network elements.

[0275] The wireless access type definition in this application embodiment is used for the transmission technology of the access network. For example, the wireless access type may also be called radio access technology (RAT) type, access technology or other names.

[0276] For example, wireless access types include one or more of the following: cellular, New Radio (i.e., 5G cellular access technology), LTE (i.e., 4G cellular access technology), Narrowband Internet of Things (NB-IoT), NTN, NR satellite access (including NR LEO / NR MEO / NR GEO / NR otherSAT, i.e., low-Earth orbit, medium-Earth orbit, and geostationary orbit satellites), LTE satellite access (similar to NR, there are also low-Earth orbit, medium-Earth orbit, etc., such as LTE GEO), and future access technologies. Furthermore, wireless access types can be used for both 3GPP access and non-3GPP access.

[0277] For example, the first information may directly indicate GEO access (e.g., LTE GEO or NR GEO), or indicate that the terminal device has subscribed to / authorized GEO access, or indicate that the terminal device has subscribed to / authorized to use GEO IMS services. In this case, the first information may also be referred to as the fifth information. Alternatively, it can be understood that the fifth information is a special case of the first information.

[0278] Optionally, the aforementioned steps are included before step 601. Figure 4B Steps 1 to 7 in the process refer to the process of the first IMS network element receiving INVITE.

[0279] In addition, this step 601 has multiple triggering methods:

[0280] In one possible implementation, step 601 may be triggered by a request message sent by the first IMS network element. Alternatively, it can be understood that the first information is used to respond to the request message. The first core network element or the subscribed network element receives the request message sent by the first IMS network element, which is used to query the radio access type of the called terminal device.

[0281] For example, taking the first IMS network element as ICSCF-B and the subscribed network element as a converged HLR / HSS, in this example, the aforementioned steps are included before step 601. Figure 4BSteps 1 to 5 are shown. The request information is a Location-Info-Request (LIR) message, used to request the name of the S-CSCF currently providing services to the user. Correspondingly, the first information is a Location-Info-Answer (LIA) message, used to respond to the Location-Info-Request command and provide the server address or capability set information of the S-CSCF. Specifically, taking GEO access as an example (i.e., taking the application in the IMSGEO scenario as an example), the called terminal device subscribes to and registers its time period for using GEO access or GEO IMS service at the HLR / HSS, or subscribes to GEO IMS service. If the HLR / HSS receives the LIR message sent by ICSCF-B, it indicates in the LIA message sent to ICSCF-B that the called terminal device is using GEO access, or indicates that the called terminal device has subscribed to / authorized GEO access, or indicates that the called terminal device has subscribed to / authorized to use GEO IMS service. Therefore, ICSCF-B can send a second message to PCSCF-A (e.g., ICSCF-B directly sends a 183 message or a 180 ringing message to PCSCF-A, or ICSCF-B instructs PCSCF-B or SSCCF-B to send a 183 message or a 180 ringing message to PCSCF-A). Optionally, the first IMS network element can also be PCSCF-B or SSCCF-B. In this case, the first message (indicating that the called terminal device is a GEO access device, or indicating that the called terminal device has subscribed to / authorized GEO access, or indicating that the called terminal device has subscribed to / authorized to use GEO IMS service) is forwarded to PCSCF-B or SSCCF-B through ICSCF-B. Therefore, PCSCF-B or SSCCF-B can send the second message to PCSCF-A (e.g., via a 183 message or a 180 ringing message).

[0282] For example, taking PCSCF-B as the first IMS network element and PCRF-B as the first core network element, the request information is an Authorization Request (AAR) message, and the first information is an AAR response message. The AAR message is used to instruct the establishment of a dedicated bearer for the called terminal device.

[0283] Optionally, after receiving the INVITE message, the first IMS network element sends a request message to the first core network element, for example, by carrying the request message in an AAR message.

[0284] In another possible implementation, after the first core network element receives the AAR message from the first IMS network element (in this approach, the AAR message may not be used to query the radio access type of the called terminal device, but rather to indicate the establishment of a dedicated bearer for the called terminal device), the first core network element proactively adds an indication (indicating the radio access type of the called terminal device) to the AAR response message sent to the first IMS network element. For example, explicit indication information can be added to the AAR response message to indicate the radio access type of the called terminal device.

[0285] Optionally, if the first core network element determines that the wireless access type of the called terminal device is satellite access or GEO access, the AAR response message sent to the first IMS network element indicates that the wireless access type of the called terminal device is satellite access or GEO access.

[0286] In another possible implementation, when the called terminal device's wireless access type is GEO access, the called terminal device sends first information to the first IMS network element.

[0287] The called terminal device's wireless access type is GEO access, including one or more of the following: the called terminal device's current wireless access type is GEO access; the called terminal device supports GEO access; the called terminal device's location is within the GEO coverage area or service area; or it has received indication information from the called terminal device's operating system, application layer, or user. The indication information is used to indicate GEO access or to indicate the transmission of first information.

[0288] Alternatively, it can be understood that, under one or more of the above conditions, the called terminal device determines its wireless access type as GEO access.

[0289] In another possible implementation, upon receiving an INVITE or UPDATE message from the calling terminal device, the called terminal device sends first information to the first IMS network element. This will be described later with reference to other accompanying figures and will not be elaborated upon here. For example, upon receiving an INVITE message from the calling terminal device, the called terminal device can send first information to the first IMS network element via a 183 message. Alternatively, the called terminal device can also send first information to the first IMS network element during the IMS registration process, etc., but specific details are not limited here.

[0290] It is understood that the above-mentioned methods of triggering the first information are just examples. In other embodiments, there are other methods, which are not limited here.

[0291] It should be noted that there are multiple ways for the first core network element or the contracted network element to determine the radio access type of the called terminal device. The following example uses GEO access. For instance, during the tracking area update (TAU) process, the called terminal device reports its radio access technology (RAT type) to the PCRF / PCF (which can be forwarded via the MME / AMF). When the called terminal device moves from non-GEO access to GEO access, it will definitely initiate a TAU process. Therefore, based on this mechanism, if the called terminal device is using GEO access, the first core network element will definitely be able to detect this when the terminal moves to GEO access. Another example is that the called terminal device reports its radio access technology (RAT type) to the PCRF / PCF when registering with the core network (which can be forwarded via the MME / AMF). Yet another example is that the first core network element configures the GEO coverage area and obtains the location of the called terminal device. When the called terminal device's location is within the coverage area, it determines that the called terminal device is using GEO access. For example, the first core network element determines that the radio access type of the called terminal device is GEO access based on the subscription information of the called terminal device (e.g., the PCRF / PCF obtains the subscription information of the called terminal device from the HSS / UDM). For another example, the subscription network element determines that the radio access type of the called terminal device is GEO access based on the subscription information of the called terminal device.

[0292] In this embodiment of the application, after receiving the first information, the first IMS network element can send the second information to the second IMS network element (i.e., step 6021) or send the second information to the calling terminal device (i.e., step 6022). For example, the second information can be a ringing message (such as a 180 ringing message), a session initiation response message (such as a 183 message or a 200 message), a temporary feedback message, or a temporary response message, etc. Steps 6021 and 6022 are described below.

[0293] In addition, the first IMS network element can also send SDP information to the second IMS network element. This SDP information indicates the media type of the calling terminal equipment and / or the called terminal equipment. This SDP information may include: SDP-A of the calling terminal equipment and / or SDP-B of the called terminal equipment. SDP-A can be understood as the media types supported by the calling terminal equipment, and SDP-B can be understood as the media types supported by the called terminal equipment. Of course, the SDP information can also indicate the media type negotiated between the calling and called terminal equipment, etc., but this is not limited here.

[0294] Step 6021: The first IMS network element sends the second information to the second IMS network element. This step is optional.

[0295] Optionally, after receiving the first information, the first IMS network element sends the second information to the second IMS network element. Correspondingly, the second IMS network element receives the second information sent by the first IMS network element.

[0296] The second information in this embodiment is used to indicate one or more of the following: the call setup time between the calling terminal device and the called terminal device, or the wireless access type of the called terminal device, etc. The call setup time is related to the wireless access type of the called terminal device. This second information can be indication information or signaling messages, or it can be media information, such as video, audio, text, images, vibration, etc., and is not specifically limited here.

[0297] Call setup time can also be called session / connection setup time, time for session / connection establishment, call setup delay, transmission time, or call waiting time / wait time for call setup / call waiting duration.

[0298] For example, call setup time, connection establishment time, or transmission time can be interpreted in several ways. For instance, it can be interpreted as the time interval between the sending of the calling signal and the reception of the call-connect signal. Alternatively, it can be interpreted as the duration / time required to complete all or part of the IMS call setup process (if partial, this could be the duration of bearer establishment by the calling and / or called party, the duration of the calling party receiving the response message, etc.). Or it can be interpreted as the duration from when the calling party initiates the call setup process (e.g., sending an INVITE message) to when the calling party receives the ringing signal.

[0299] For example, call waiting time or transmission time can be interpreted in several ways. For instance, it can be interpreted as: the waiting time from when the calling user dials the number until the calling user hears the ring / tone. Or it can be interpreted as: the time from when the calling user initiates the call setup process until the calling user receives the called user's answer-the-hook instruction message. Or it can be interpreted as: the waiting time from when the calling user dials the number until the calling user hears the called user answer / hook the phone, etc. Here, the calling user can be a person using the calling terminal device, artificial intelligence, etc.

[0300] Optionally, the relationship between call setup duration and the radio access type of the called terminal device can be interpreted in several ways. For example, the call setup duration may be determined based on the radio access type. Alternatively, the call setup duration may be a pre-configured value corresponding to a specific radio access type. Another example is when the first IMS receives an indication of the radio access type of the called terminal device and sends information indicating the call setup duration to the second IMS network element or the calling terminal device, in which case the call setup duration is considered to be related to the radio access type.

[0301] In this embodiment of the application, the unit for call setup duration can be one or more of the following: hours, quarter-hours, minutes, seconds, milliseconds, etc., and there is no specific limitation here. For example, the call setup duration is 10 seconds, 20 seconds, or 1 minute.

[0302] Optionally, after receiving the first information sent by the first core network element, the subscribed network element, or the called terminal device, the first IMS network element determines the second information based on the first information. Alternatively, this can be understood as: the first IMS network element determines the second information based on the radio access type of the called terminal device. Or, this can be understood as: the first IMS network element determines the call setup duration or radio access type based on the radio access type of the called terminal device.

[0303] For example, the first IMS network element is configured / pre-configured with an association or mapping table. This association or mapping table represents the relationship between radio access type and call setup duration; different radio access types may correspond to different call setup durations. For example, the mapping table is shown in Table 1 or Table 2.

[0304] Table 1

[0305] Wireless access type of the called terminal device Call setup time Satellite Access Duration 1 Non-satellite access Duration 2

[0306] Wherein, if the called terminal device's wireless access type is satellite access, the corresponding call setup duration is duration 1. If the called terminal device's wireless access type is non-satellite access, the corresponding call setup duration is duration 2. Optionally, duration 1 is greater than duration 2. Of course, there can be only one, for example, satellite access corresponds to duration 1.

[0307] Table 2

[0308] Wireless access type of the called terminal device Call setup time GEO Access Duration 3 MEO Access Duration 4 LEO Access Duration 5

[0309] Wherein, when the called terminal device's radio access type is GEO access, the corresponding call setup duration is duration 3. When the called terminal device's radio access type is MEO access, the corresponding call setup duration is duration 4. When the called terminal device's radio access type is LEO access, the corresponding call setup duration is duration 5. Optionally, duration 3 is greater than duration 4, and duration 4 is greater than duration 5.

[0310] Furthermore, the second information used to indicate call setup time can be interpreted in several ways. For example, it can indicate a time period, which can vary depending on the wireless access type of the called terminal device. For instance, the call setup time for GEO access type is longer than for other access types. Similarly, the call setup time for MEO access type is longer than that for LEO access type. It can also be used to prompt the user to wait patiently. Furthermore, it can instruct the second IMS network element to send the fourth information to the calling terminal device. Finally, it can instruct the second IMS network element to remind the user of the calling terminal device.

[0311] In this application embodiment, "patiently waiting" can be understood as indicating a period of time, or it may not indicate a period of time, but rather be an instruction to the calling terminal device or a reminder to the user of the calling terminal device. This reminder is used to reduce the probability that the calling terminal device or the user of the calling terminal device will hang up the IMS call too early, or it may be used to increase the waiting time for the calling terminal device or the user of the calling terminal device to receive a call.

[0312] Optionally, the second information is used to instruct the user of the calling terminal device on one or more of the following: call setup time, waiting time, and the wireless access type of the called terminal device.

[0313] It should be noted that the content of the first information and the second information may be the same or different, but their functions are the same. For example, if the content and function of the first information and the second information are the same, it means that the first IMS network element does not perform intermediate processing, and the first information is equivalent to being transparently transmitted through the first IMS network element (for example, step 6021 is the first information being transparently transmitted to the second IMS network element, and step 6022 is the first information being transparently transmitted to the calling terminal device). Another example is that the content of the first information and the second information are different, but their functions are the same, indicating that the first IMS network element performs intermediate processing (for example, the first IMS network element determines the call setup duration indicated by the second information based on the first information; or the first IMS network element determines the second information based on the first information to instruct the calling terminal user to wait patiently; or the first IMS network element determines the second information based on the first information to instruct the generating of a special ringtone, which is used to remind the calling terminal user to wait patiently, etc.).

[0314] In addition, the first IMS network element can send the second information (e.g., steps 6021 and 6022) in several ways:

[0315] In one possible implementation, the second information is sent to the second IMS network element or the calling terminal device when the calling terminal device accesses via a terrestrial network, or when the first IMS network element does not receive an instruction from the calling terminal device or the second IMS network element to prohibit ringback tones / displays. That is, the second information is sent when the calling party is not accessing via GEO (e.g., terrestrial access), or when no instruction to "prohibit ringback tones or displays" has been received.

[0316] Among them, "the calling terminal equipment accesses through the terrestrial network" can be "the calling terminal equipment accesses through GEO or satellite"; "prohibit the sending of ringtones or caller ID ringtones" can be "prohibit" or "suppress", etc.

[0317] In another possible implementation, the first IMS network element receives the session initiation message and, in response to the session initiation message, sends the second information to the second IMS network element or the calling terminal device.

[0318] For example, if the session initiation message is an INVITE message and the second message is a 183 message or a 180 ringing message, the first IMS network element uses the aforementioned... Figure 4B After receiving the INVITE message in steps 1 to 7, and determining the wireless access type of the called terminal device as satellite access or GEO access based on the first information, the first IMS network element sends a 183 message or a 180 ringing message to the second IMS network element. For example, if the second IMS network element includes CAT-AS / MMTel-AS, the first IMS network element sends a 180 ringing message to CAT-AS / MMTel-AS, which is used by CAT-AS to generate a special ringtone. As another example, if the second IMS network element includes PCSCF-A, the first IMS network element sends a 183 message to PCSCF-A.

[0319] In another possible implementation, the first IMS network element receives the response message of the session initiation message, and after receiving the response message of the session initiation message, sends the second information.

[0320] For example, assuming the session initiation message is an INVITE message, and the response message is a 183 message or a ringing message, the first IMS network element sends an INVITE message to the called terminal device and receives a 183 message or a ringing message from the called terminal device. Then, the first IMS network element sends a second message. This second message can also be a 180 ringing message or a new message. This is used by MGCF / CAT-AS / MMTel to generate special ringtones.

[0321] Optionally, if the first IMS network element determines through the first information that the wireless access type of the called terminal device is satellite access or GEO access, the first IMS network element can also send third information to the called terminal device. This third information is used to instruct the called terminal device to set to early ringing mode. Of course, setting the called terminal device to early ringing mode can be triggered by the third information, or it can be pre-configured or pre-configured. For example, terminal devices with GEO access or supporting GEO IMS service are pre-configured to early ringing mode.

[0322] Step 603: The second IMS network element sends the fourth information to the calling terminal device. This step is optional.

[0323] Optionally, after receiving the second information sent by the first IMS network element, the second IMS network element sends a fourth information to the calling terminal device. Correspondingly, the calling terminal device receives the fourth information sent by the second IMS network element. This fourth information is used to indicate the call setup duration or the radio access type of the called terminal device. This fourth information can be in video, audio, text, image, vibration, etc., and is not specifically limited here.

[0324] For example, the fourth information may include media data used to indicate to the user of the calling terminal device the call setup time or to wait patiently, or the radio access type of the called terminal device. This fourth information may also be a ringtone or a first indication message used to indicate to the user of the calling terminal device the call setup time or to wait patiently, or the radio access type of the called terminal device.

[0325] Optionally, after receiving the second information sent by the first IMS network element, the second IMS network element first determines the fourth information based on the second information, and then sends the fourth information to the calling terminal device. For example, the second IMS network element determines the fourth information based on the radio access type of the called terminal device. Another example is that the second IMS network element determines the fourth information based on the call setup time.

[0326] Optionally, after the calling bearer is established, a fourth message is sent to the calling terminal device.

[0327] It should be noted that the content of the second and fourth pieces of information may be the same or different, and their functions may also be the same or different. For example, if the content and function of the second and fourth pieces of information are the same, it means that the second IMS network element does not perform intermediate processing, and the second information is equivalent to being transparently transmitted to the calling terminal device through the second IMS network element. For example, the second and fourth pieces of information may have different contents but the same function, indicating that the second IMS network element performs intermediate processing (e.g., the second IMS network element determines the call setup duration corresponding to the fourth piece of information based on the call setup duration in the second piece of information). Alternatively, the second and fourth pieces of information may have different contents and functions. For example, the second IMS network element may determine the call setup duration corresponding to the fourth piece of information based on the radio access type of the called terminal device in the second piece of information. Or, the second IMS network element may determine that the fourth piece of information is used to instruct the calling terminal user to wait patiently. Or, the second IMS network element may determine the special ringtone corresponding to the fourth piece of information based on the second piece of information, and then send the special ringtone or the corresponding indication or identifier to the calling terminal device (assuming the calling terminal device stores a special ringtone, the calling terminal device can play the corresponding ringtone according to the indication or identifier)

[0328] Optionally, when determining the call setup duration corresponding to the fourth information based on the second information, the second IMS network element may or may not consider the radio access type of the calling terminal device. That is, the call setup duration corresponding to the second information and the call setup duration corresponding to the fourth information may be the same or different. For example, when both the called terminal device and the calling terminal device have GEO access, the call setup duration corresponding to the fourth information may be greater than the call setup duration corresponding to the second information. For instance, the call setup duration corresponding to the fourth information may be twice the call setup duration corresponding to the second information.

[0329] For example, the second IMS network element is configured / pre-configured with an association or mapping table. This association or mapping table represents the relationship between radio access type and call setup duration; different radio access types may correspond to different call setup durations. Alternatively, the association or mapping table represents the relationship between radio access type and ringtone; different radio access types may correspond to different ringtones. Or, the association or mapping table represents the relationship between call setup duration and ringtone; different call setup durations may correspond to different ringtones. For example, a mapping table between radio access type and call setup duration is shown in Table 1 or Table 2 above. Another example is a mapping table between radio access type and ringtone, as shown in Table 3. Yet another example is a mapping table between call setup duration and ringtone, as shown in Table 4.

[0330] Table 3

[0331] Wireless access type of the called terminal device Call setup time Satellite Access Ringtone 1 Non-satellite access Ringtone 2

[0332] In this context, when the called terminal device's wireless access type is satellite access, the corresponding call setup time is ringtone 1. When the called terminal device's wireless access type is non-satellite access, the corresponding call setup time is ringtone 2. For example, ringtone 1 is an audio signal: the called terminal device is using satellite access, please wait patiently. Ringtone 2 is an audio signal: the called terminal device is using non-satellite access, the call is not being answered. Another example is ringtone 1 consisting of N vibrations, prompting the calling terminal device user to wait patiently. Ringtone 2 consists of M vibrations. N and M are different positive integers; N can be greater than or less than M. Of course, there can also be only one option; for example, satellite access corresponds to ringtone 1.

[0333] Table 4

[0334] Call setup time Call setup time Duration 3 Ringtone 3 Duration 4 Ringtone 4 Duration 5 Ringtone 5

[0335] Specifically, when the call setup time for the called terminal device is 3 minutes, the corresponding call setup time is 3 ringtones. When the call setup time for the called terminal device is 4 minutes, the corresponding call setup time is 4 ringtones. When the call setup time for the called terminal device is 5 minutes, the corresponding call setup time is 5 ringtones.

[0336] Optionally, the network element receiving the second information in step 6021 and the network element sending the fourth information in step 603 can be the same network element or different network elements. For example, taking different network elements as an example, the second IMS network element includes PCSCF-A+CAT-AS / MMTel-AS. After receiving the second information, PCSCF-A forwards it to CAT-AS / MMTel-AS (it can be a direct forwarding or the information can be processed, but the function of the information remains unchanged). After receiving the second information, CAT-AS / MMTel-AS determines or obtains the fourth information and sends the fourth information to the calling terminal equipment.

[0337] Step 6022: The first IMS network element sends the second information to the calling terminal device. This step is optional.

[0338] Optionally, after receiving the first information, the first IMS network element sends the second information to the calling terminal device. Correspondingly, the calling terminal device receives the second information sent by the first IMS network element. The second information can be referred to the description in step 6021 above, and will not be repeated here.

[0339] Optionally, the second information in step 6021 and the second information in step 6022 can be used to instruct the calling terminal device. Alternatively, the second information in step 6021 can be understood as indirectly instructing the calling terminal device, while the second information in step 6022 is used directly instructing the calling terminal device. For example, the second information in step 6021 can instruct the second IMS network element to instruct the calling terminal device to provide the fourth information. Or, the second information can instruct the second IMS network element to remind the user of the calling terminal device.

[0340] Step 604: The calling terminal device plays a ringtone based on the second or fourth information.

[0341] After receiving the second or fourth information, the calling terminal device plays a ringtone based on that information. This ringtone indicates one or more of the following to the user of the calling terminal device: call setup time, patience required, and the wireless access type of the called terminal device. This increases the waiting time for the user of the calling terminal device and reduces the probability of the user mistakenly believing there is a network problem or that the called terminal device is offline, thus hanging up the call.

[0342] Optionally, the ringtone can be audio, video, text, image, or a ringing sound, etc., and there are no specific restrictions here.

[0343] The second or fourth information can be a ringtone, or the second or fourth information can be a first indication information. The ringtone or the first indication information is used to indicate to the user of the calling terminal device the call setup time or to wait patiently, or the wireless access type of the called terminal device.

[0344] In one possible implementation, the calling terminal device receives and plays a ringtone sent by a first IMS network element or a second IMS network element. This ringtone is used to indicate the call setup duration between the calling and called terminal devices or the radio access type of the called terminal device; the call setup duration is related to the radio access type.

[0345] Alternatively, this can be understood as follows: in the above method, the terminal device can receive and play ringtones sent by other network elements.

[0346] In another possible implementation, the calling terminal device receives first indication information sent by a first IMS network element or a second IMS network element. This first indication information indicates the call setup duration between the calling terminal device and the called terminal device, or the radio access type of the called terminal device. The call setup duration is related to the radio access type. The calling terminal device plays a ringtone based on the first indication information. This ringtone is related to the radio access type of the called terminal device.

[0347] Alternatively, in the above method, the terminal device can receive instruction information sent by other network elements, determine the locally stored ringtone or obtain the corresponding ringtone (e.g., download) based on the instruction information, and play the ringtone.

[0348] Optionally, playing a ringtone can be replaced by instructing the user of the calling terminal device on one or more of the following: call setup time, wait patiently, and the wireless access type of the called terminal device.

[0349] The method provided in this embodiment has multiple variations. For example, the method provided in this embodiment includes steps 601, 6021, 603, and 604. Alternatively, the method provided in this embodiment may include steps 601, 6022, and 604, etc., and the specific method is not limited here.

[0350] In this embodiment, the first IMS network element serving the called terminal device can determine the wireless access type of the called terminal device by receiving the first information sent by the first core network element, the subscribed network element, or the called terminal device. Then, it can send the second information to the second IMS network element or the calling terminal device. The second information is used to indicate the call setup time between the calling terminal device and the called terminal device or the access type of the called terminal device, so that the calling terminal device can wait patiently and reduce the probability that the calling terminal device will hang up because it mistakenly thinks that there is a network problem or that the called terminal device is offline.

[0351] because Figure 6 The illustrated embodiments involve various network element scenarios; the following section uses 4G as an example. Figure 6 The different network element scenarios in the illustrated embodiments are described separately.

[0352] Example 1: The called terminal device is UE-B, the first IMS network element is PCSCF-B / SCSCF-B, and the first core network element is PCRF-B. The calling terminal device is UE-A, the second IMS network element is PCSCF-A / SCSCF-A, and the second core network element is PCRF-A. The radio access type (or access technology) of the called terminal device is GEO access, taking the application in the IMSGEO scenario as an example.

[0353] Please see Figure 7 This application provides another flowchart illustrating a communication method, which may include steps 1 to 24. Steps 1 to 24 may be executed by a communication device, or by some components of the communication device (e.g., a processor, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the communication device. The following description uses the example of execution by a communication device.

[0354] Steps 1 to 7 can be referred to the above. Figure 4B Steps 1 to 7 in the process will not be detailed here.

[0355] In step 8a, when PCSCF-B / SCSCF-B receives the INVITE message, it queries PCCF-B for the access technology of UE-B.

[0356] Step 9a: PCSCF-B / SCSCF-B sends an AAR to PCRF-B (instructing PCRF-B to establish a dedicated bearer for UE-B and to query the access technology of UE-B).

[0357] Step 8b: PCSCF-B / SCSCF-B sends an AAR to PCRF-B (instructing PCRF-B to establish a dedicated bearer for UE-B).

[0358] In step 9b, if PCRF-B receives an AAR message indicating the establishment of a called bearer, it will provide UE-B's access technology to PCSCF-B / SCSCF-B.

[0359] Step 10: PCRF-B sends an AAR response to PCSCF-B / SCSCF-B (indicating that UE-B is using GEO access).

[0360] Step 11a: If PCSCF-B / SCSCF-B determines that UE-B is a GEO access, then it indicates that UE-B is in early ringing mode.

[0361] Step 11b: If PCSCF-B / SCSCF-B determines that UE-B is a GEO access, it will directly generate a ringing message and send it to PCSCF-A / SCSCF-A.

[0362] Step 12: PCSCF-B / SCSCF-B sends a 183 message (SDP) to PCSCF-A / SCSCF-A.

[0363] Step 13, establish the calling side bearer.

[0364] Step 14: PCSCF-B / SCSCF-B sends a 180 ringing message (SDP, indicating that UE-B is a GEO access) to CAT-AS / MMTel-AS.

[0365] Step 15: CAT-AS / MMTel-AS generates a ringtone instructing the user to wait patiently, based on the instruction (i.e., the instruction of the 180 ringing message).

[0366] Step 16: CAT-AS / MMTel-AS sends an address complete message (ACM) to UE-A (a ringtone indicates that the user should wait patiently).

[0367] Step 17: PCSCF-B / SCSCF-B sends an INVITE message to UE-B (optionally, if step 11a is performed, the early ringing mode is indicated).

[0368] Step 18: UE-B sends 183 message (SDP) / 180 ringing message to PCSCF-B / SCSCF-B.

[0369] Step 19: If PCSCF-B / SCSCF-B determines that UE-B is a GEO access, then the ringing message will indicate that UE-B is a GEO access.

[0370] Step 20: PCSCF-B / SCSCF-B sends a 183 message (SDP) to PCSCF-A / SCSCF-A.

[0371] Step 21, establish the calling side bearer.

[0372] Step 22: PCSCF-B / SCSCF-B sends a 180 ringing message (SDP, indicating that UE-B is a GEO access) to CAT-AS / MMTel-AS.

[0373] Step 23: CAT-AS / MMTel-AS generates a ringtone based on the 180 ringing message, instructing the user to wait patiently or to specify the call setup time or the type of wireless access the called party.

[0374] Step 24: CAT-AS / MMTel-AS sends an ACM message to UE-A (a ringtone indicates that the user should wait patiently).

[0375] The method provided in this embodiment has multiple variations. For example, the method provided in this embodiment includes steps 1-7, 8a, 9a, 10, 11a, and 17-24. Another example is that the method provided in this embodiment includes steps 1-7, 8a, 9a, 10, and 17-24. Yet another example is that the method provided in this embodiment includes steps 1-7, 8b, 9b, 10, 11a, and 17-24. Yet another example is that the method provided in this embodiment includes steps 1-7, 8b, 9b, 10, and 17-24. Yet another example is that the method provided in this embodiment includes steps 1-7, 8a, 9a, 10, 11a, 11b, and 12-16. Yet another example is that the method provided in this embodiment includes steps 1-7, 8a, 9a, 10, 11b, and 12-16. Yet another example is that the method provided in this embodiment includes steps 1-7, 8b, 9b, 10, 11a, 11b, and 12-16. For example, the method provided in this embodiment includes steps 1-7, 8b, 9b, 10, 11b, 12-16, etc., and the specific steps are not limited here. All of the above cases may include or exclude 11b. Alternatively, they may include or exclude 19. Where 11a is absent, the INVITE message in step 17 may not indicate an early ringing mode.

[0376] In this embodiment, if PCSCF-B determines that UE-B is under GEO access, it instructs the IMS network element to generate a special ringtone so that the caller can perceive that the called party is under GEO coverage or prompt the caller to wait patiently, thereby reducing the chance of the caller mistakenly thinking that a fault has occurred and hanging up the phone.

[0377] Example 2: The called terminal device is UE-B, the first IMS network element is PCSCF-B / SCSCF-B, the first core network element is PCRF-B, and the calling terminal device is UE-A. The radio access type (or access technology) of the called terminal device is GEO access, taking the application in an IMS GEO scenario as an example.

[0378] Please see Figure 8 This application provides another flowchart illustrating the communication method, which may include steps 0 to 18. Steps 0 to 18 may be executed by a communication device, or by some components of the communication device (e.g., a processor, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the communication device. The following description uses the example of execution by a communication device.

[0379] Step 0: If UE-A supports GEO-IMS service, then store or retrieve a ringtone indicating whether the user is waiting patiently, the call setup time, or the called wireless access type.

[0380] Steps 1 to 11b can be referred to the above. Figure 7Steps 1 to 11b are detailed here and will not be repeated.

[0381] Step 12: PCSCF-B / SCSCF-B sends a 183 message (SDP, indicating that UE-B is GEO access / wait patiently) to UE-A.

[0382] Step 13: UE-A plays a locally stored ringtone as instructed in message 183, prompting the user to wait patiently.

[0383] Steps 14 to 16 can be referred to the above. Figure 7 Steps 17 to 19 are detailed here and will not be repeated.

[0384] Step 17: PCSCF-B / SCSCF-B sends a 183 message (SDP, indicating that UE-B is GEO access / wait patiently) to UE-A.

[0385] In step 18, UE-A plays a locally stored ringtone as instructed in message 183, prompting the user to wait patiently.

[0386] The method provided in this embodiment has multiple possible scenarios. For example, the method provided in this embodiment includes steps 0-7, 8a, 9a, 10, 11a, and 14-18. Another example is that the method provided in this embodiment includes steps 0-7, 8a, 9a, 10, and 14-18. Yet another example is that the method provided in this embodiment includes steps 0-7, 8a, 9a, 10, 11a, 11b, 12, and 13. Yet another example is that the method provided in this embodiment includes steps 0-7, 8a, 9a, 10, 11b, 12, and 13, etc., and the specific implementation is not limited here. All of the above scenarios may include or exclude step 11b. Alternatively, they may all include or exclude step 16. Where step 11a is absent, the INVITE message in step 14 may not indicate an early ringing mode.

[0387] In this embodiment, if PCSCF-B determines that UE-B is under GEO access, it will instruct UE-A to generate a special ringtone through the IMS network element, so that the caller can perceive that the called party is under GEO coverage or prompt the caller to wait patiently, thereby reducing the effect of the caller hanging up the phone because they mistakenly think that a fault has occurred.

[0388] Example 3: The called terminal device is UE-B, the first IMS network element includes PCSCF-B / SCSCF-B and / or ICSCF-B, and the first core network element includes HLR / HSS and / or PCRF-B. The calling terminal device is UE-A, the second IMS network element is PCSCF-A / SCSCF-A, and the second core network element includes HLR / HSS and / or PCRF-A. The example uses GEO access as the radio access type (or access technology) of the called terminal device, specifically in an IMS GEO scenario.

[0389] Please see Figure 9 This application provides another flowchart illustrating the communication method, which may include steps 0 to 30. Steps 0 to 30 may be executed by a communication device, or by some components of the communication device (e.g., a processor, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the communication device. The following description uses execution by a communication device as an example.

[0390] Step 0: UE-B subscribes to GEO IMS (or GEO Access) service at the HLR / HSS. For example, UE-B registers the time period for using GEO Access or GEO IMS service.

[0391] Steps 1 to 5 can be referred to the above. Figure 7 Steps 1 to 5 in the process will not be detailed here.

[0392] Step 6: ICSCF-B sends an LIR message to HLR / HSS (requesting the address of the SSCCF-B corresponding to UE-B. Optionally, the LIR can also be used to query whether UE-B has subscribed to GEO IMS).

[0393] Step 7: HLR / HSS determines the UE-B's contract with GEO IMS based on the UE-B's contract information.

[0394] Step 8: HLR / HSS sends an LIA message to ICSCF-B (instructing UE-B to subscribe to GEO IMS).

[0395] Step 9: If ICSCF-B determines that UE-B is a GEO access, it will directly generate / instruct PCSCF-B to ring a message and send it to PCSCF-A / SCSCF-A.

[0396] Step 10: ICSCF-B sends a 183 message (SDP) to PCSCF-A / SCSCF-A.

[0397] Step 11, establish the calling side bearer.

[0398] Step 12: ICSCF-B sends a 180 ringing message (SDP, indicating that UE-B is a GEO access) to CAT-AS / MMTel-AS.

[0399] Step 13: CAT-AS / MMTel-AS generates a ringtone instructing the user to wait patiently based on the 180 ringing message.

[0400] Step 14: CAT-AS / MMTel-AS sends an ACM (ringing sound to instruct the user to wait patiently) to UE-A.

[0401] Step 15: ICSCF-B sends an INVITE message to PCSCF-B / SCSCF-B (instructing UE-B to enable GEO access / instructing the generation of a ringing message).

[0402] Step 16: PCSCF-B / SCSCF-B generates a ringing message / indicates early ringing / adds an indication that UE-B is a GEO access in the ringing message according to the instructions of ICSCF-B.

[0403] Step 17: PCSCF-B / SCSCF-B sends a 183 message (SDP) to PCSCF-A / SCSCF-A.

[0404] Step 18: Establish caller-side bearer.

[0405] Step 19: PCSCF-B / SCSCF-B sends a 180 ringing message (SDP, indicating that UE-B is a GEO access) to CAT-AS / MMTel-AS.

[0406] Step 20: CAT-AS / MMTel-AS generates a ringtone instructing the user to wait patiently based on the 180 ringing message.

[0407] Step 21: CAT-AS / MMTel-AS sends an ACM (ringing sound to instruct the user to wait patiently) to UE-A.

[0408] Step 22, PCSCF-B / SCSCF-B transmits AAR to PCRF-B (instructing PCRF-B to establish a dedicated bearer for UE-B).

[0409] Step 23: PCSCF-B / SCSCF-B sends an INVITE message to UE-B.

[0410] Step 24: UE-B sends 183 message (SDP) / 180 ringing message to PCSCF-B / SCSCF-B.

[0411] Step 25: If PCSCF-B / SCSCF-B determines that UE-B is a GEO access, then the ringing message will indicate that UE-B is a GEO access.

[0412] Step 26: PCSCF-B / SCSCF-B sends a 183 message (SDP) to PCSCF-A / SCSCF-A.

[0413] Step 27: Establish caller-side bearer.

[0414] Step 28: PCSCF-B / SCSCF-B sends a 180 ringing message (SDP, indicating that UE-B is a GEO access) to CAT-AS / MMTel-AS.

[0415] Step 29: CAT-AS / MMTel-AS generates a ringtone instructing the user to wait patiently based on the 180 ringing message.

[0416] Step 30: CAT-AS / MMTel-AS sends an ACM message to UE-A (a ringtone indicates that the user should wait patiently).

[0417] The method provided in this embodiment has multiple possible scenarios. For example, the method provided in this embodiment includes steps 0-14. Another example is that the method provided in this embodiment includes steps 0-9 and 15-21. Yet another example is that the method provided in this embodiment includes steps 0-9, 15, 16, 22-30, etc., and the specific details are not limited here. All of the above scenarios may include or exclude step 9. Alternatively, they may include or exclude step 25.

[0418] In this embodiment, if the HLR / HSS determines that UE-B is under GEO access, it notifies ICSCF-B / SCSCF-B / PCSCF-B to instruct CAT-AS / MMTel-AS / IMS-AS to generate a special ringtone so that the caller can perceive that the called party is under GEO coverage or to prompt the caller to wait patiently, thereby reducing the chance of the caller mistakenly thinking that a malfunction has occurred and hanging up the phone.

[0419] Example 4: The called terminal device is UE-B, the first IMS network element includes PCSCF-B / SCSCF-B and / or ICSCF-B, and the first core network element includes HLR / HSS and / or PCRF-B. The calling terminal device is UE-A, the second IMS network element is PCSCF-A / SCSCF-A, and the second core network element includes HLR / HSS and / or PCRF-A. The example uses GEO access as the radio access type (or access technology) of the called terminal device, specifically in an IMS GEO scenario.

[0420] Please see Figure 10This application provides another flowchart illustrating the communication method, which may include steps 0 to 21. Steps 0 to 21 may be executed by a communication device, or by some components of the communication device (e.g., a processor, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the communication device. The following description uses the example of execution by a communication device.

[0421] Step 0: UE-B subscribes to GEO IMS (or GEO access) at HLR / HSS. For example, UE-B registers the time period for using GEO access.

[0422] Steps 1 to 9 can be referred to the above. Figure 9 Steps 1 to 9 in the process will not be detailed here.

[0423] Step 10: ICSCF-B sends a 183 message (SDP) to UE-A via PCSCF-A / SCSCF-A.

[0424] Step 11: UE-A plays a locally stored ringtone as instructed in message 183, prompting the user to wait patiently.

[0425] Step 12: ICSCF-B sends an INVITE message to PCSCF-B / SCSCF-B (instructing UE-B to enable GEO access / instructing the generation of a ringing message).

[0426] Step 13: PCSCF-B / SCSCF-B generates a ringing message / indicates early ringing / adds an indication that UE-B is a GEO access in the ringing message according to the instructions of ICSCF-B.

[0427] Step 14: PCSCF-B / SCSCF-B sends a 183 message (SDP) to UE-A via PCSCF-A / SCSCF-A.

[0428] Step 15: UE-A plays a locally stored ringtone as instructed in message 183, prompting the user to wait patiently.

[0429] Step 16: PCSCF-B / SCSCF-B transmits AAR to PCRF-B (instructing PCRF-B to establish a dedicated bearer for UE-B).

[0430] Step 17: PCSCF-B / SCSCF-B sends an INVITE message to UE-B.

[0431] Step 18: UE-B sends 183 message (SDP) / 180 ringing message to PCSCF-B / SCSCF-B.

[0432] Step 19: If PCSCF-B / SCSCF-B determines that UE-B is a GEO access, then the ringing message will indicate that UE-B is a GEO access.

[0433] Step 20: PCSCF-B / SCSCF-B sends a 183 message (SDP) to UE-A via PCSCF-A / SCSCF-A.

[0434] Step 21: UE-A plays a locally stored ringtone as instructed in message 183, prompting the user to wait patiently.

[0435] The method provided in this embodiment has multiple possible scenarios. For example, the method provided in this embodiment includes steps 0-11. Another example is that the method provided in this embodiment includes steps 0-9 and 12-15. Yet another example is that the method provided in this embodiment includes steps 0-9, 12, 13, 16-21, etc., and the specific details are not limited here. All of the above scenarios may include or exclude step 9. Alternatively, they may include or exclude step 25.

[0436] In this embodiment, if the HLR / HSS determines that UE-B is under GEO access, it will instruct UE-A to generate a special ringtone through the IMS network element, so that the caller can perceive that the called party is under GEO coverage or prompt the caller to wait patiently, thereby reducing the effect of the caller hanging up the phone because he thinks there is a fault.

[0437] Example 5: The called terminal device is UE-B, the first IMS network element is CSCF-B (e.g., including one or more of the following: PCSCF-B, SSCCF-B, ICSCF-B), and the first core network element includes PCRF-B. The calling terminal device is UE-A, the second IMS network element is CSCF-A (e.g., including one or more of the following: PCSCF-A, SSCCF-A, ICSCF-A), and the second core network element includes PCRF-A. The radio access type (or access technology) of the called terminal device is GEO access, taking the application in an IMS GEO scenario as an example.

[0438] Please see Figure 11 This application provides another flowchart illustrating the communication method, which may include steps 1 to 26. Steps 1 to 26 may be executed by a communication device, or by some components of the communication device (e.g., a processor, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the communication device. The following description uses the example of execution by a communication device.

[0439] Step 1: UE-A sends an INVITE message to UE-B via CSCF-A and CSCF-B. This step 1 can also be understood as the process of UE-A calling UE-B.

[0440] Step 2: UE-B sends a 183 message to CSCF-B.

[0441] Alternatively, the 183 message can be Access Network Information (PANI) or SDP-B, etc.

[0442] For example, if message 183 is SDP-B, message 183 can be interpreted as including: the UE-B's access method is GEO and the media type (SDP-B) supported by the UE-B.

[0443] Step 3: CSCF-B sends an AAR to PCRF-B.

[0444] Step 4: PCRF-B sends an AAR response to CSCF-B.

[0445] Step 5a: PCRF-B reserves resources for UE-B startup.

[0446] Step 5b: CSCF-B sends a 183 message to UE-A via CSCF-A.

[0447] Step 6: CSCF-A sends AAR to PCRF-A.

[0448] Step 7: PCRF-A sends an AAR response to CSCF-A.

[0449] Step 8: PCRF-A reserves resources for UE-A. Steps 3 to 8 can be understood as the process of establishing the calling and called bearers in the IMS on the calling and called sides.

[0450] Step 9: UE-A sends a PRACK message to UE-B through CSCF-A and CSCF-B.

[0451] Step 10: UE-B sends 200 OK (PRACK) to UE-A via CSCF-B and CSCF-A. Alternatively, 200 OK can be understood as a response message to PRACK.

[0452] Step 11: UE-A sends an UPDATE message to CSCF-B via CSCF-A. For example, after the calling bearer is established, UE-A sends an UPDATE message. (Because the called party uses GEO access, the bearer establishment is slower than the calling bearer).

[0453] Step 12, CSCF-B sends 180 to MMTel-AS-B.

[0454] When the called IMS network element CSCF-B receives the UPDATE message, if UE-B indicated in step 2 that UE-B is using GEO access, then CSCF-B sends indication information to MMTel-AS-B, instructing MMTel-AS-B to indicate UE-B's access type to UE-A and / or to indicate the call waiting / establishment time to UE-A. The indication information may include: UE-B's access type or call waiting / establishment time, and optionally, SDP-B.

[0455] For example, if the indication information does not indicate SDP-B, it is assumed that MMTel-AS-B uses media types (such as encoding types) that are supported or negotiated by both UE-A and UE-B by default.

[0456] Step 13: MMTel-AS-B negotiates the media type with the ringback tone platform (CAT platform).

[0457] For example, MMTel-AS-B sends the received SDP_B to the ringback tone platform, indicating the use of the corresponding media type.

[0458] Step 14: MMTel-AS-B sends a ringtone to UE-A. That is, MMTel-AS-B obtains the ringtone media from the ringback tone platform and sends the ringtone to UE-A. The content of the ringtone indicates the UE-B's access type and / or call waiting / establishment time.

[0459] Step 15, UE-A plays a ringtone. For example, UE-A plays the ringtone to the calling user (the person making the call).

[0460] Step 16: CSCF-B sends an UPDATE to UE-B via PCRF-B.

[0461] Step 17, UE-B resource reservation completed. In this application, bearer establishment can also be referred to as resource reservation. That is, the completion of UE-B resource reservation can be described as the completion of UE-B bearer establishment.

[0462] Step 18, UE-B notifies the user. For example, it notifies the called user that bearer establishment is complete.

[0463] Step 19: UE-B sends a 200 OK (UPDATE) to UE-A via CSCF-B and CSCF-A.

[0464] Step 20: UE-B sends a 180 ringing message to UE-A via CSCF-B and CSCF-A. This step is optional.

[0465] Step 21: UE-A stops the ringing and starts playing the ringtone. This step is optional. Alternatively, it can be understood that after receiving the ringtone message, UE-A can stop the ringing playback from step 15 and start playing the ringtone.

[0466] Step 22, UE-B user response. Or, it can be understood as, after the called user picks up the phone (answers the call), UE-B sends a 200 OK (INVITE) message. Upon receiving this message, UE-A stops the ringing or ringing (if steps 20 and 21 are not executed, the ringing from step 15 will still be playing at this time, so the ringing will stop; if steps 20 and 21 are executed, the ringing will stop).

[0467] Step 23: UE-B sends 200 OK (INVITE) to UE-A via CSCF-B and CSCF-A.

[0468] Step 24a: UE-A stops the ringing / ringing and plays voice media.

[0469] Step 24b: UE-B plays audio media.

[0470] Step 25: UE-A sends an ACK to UE-B via CSCF-A and CSCF-B. This ACK is a 200 OK (INVITE) response message.

[0471] Step 26: UE-A and UE-B conduct session media transmission. Alternatively, this can be understood as UE-A replying with a 200 OK (INVITE) ACK response message, after which the calling and called users begin their call.

[0472] In this context, the 183 message in steps 2 and 5b can also be replaced with a 180 message. For example, if step 2 is a 180 message, step 12 can be brought forward. Or, step 12 can be understood as being triggered by the 180 message in step 2. As another example, if step 2 is a 183 message, step 12 is triggered by the UPDATE statement in step 11.

[0473] In this embodiment, the scenario is IMS GEO. The called party's IMS network element triggers a ringback tone playback by directly notifying UE-B that it is a GEO access, thus reducing the impact on the core network and the calling party's IMS network element. For example, when the called party's IMS network element CSCF-B receives an UPDATE message, if UE-B indicates that it is a GEO access in step 2, then CSCF-B instructs MMTel-AS-B to play a ringback tone to UE-A, indicating that UE-B is a GEO access.

[0474] Example 6: The called terminal device is UE-B, the first IMS network element is CSCF-B (e.g., including one or more of the following: PCSCF-B, SSCCF-B, ICSCF-B), and the first core network element includes PCRF-B. The calling terminal device is UE-A, the second IMS network element is CSCF-A (e.g., including one or more of the following: PCSCF-A, SSCCF-A, ICSCF-A), and the second core network element includes PCRF-A. The example uses GEO access as the radio access type (or access technology) of the called terminal device, i.e., an application in an IMS GEO scenario.

[0475] Please see Figure 12 This application provides another flowchart illustrating the communication method, which may include steps 1 to 27. Steps 1 to 27 may be executed by a communication device, or by some components of the communication device (e.g., a processor, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the communication device. The following description uses the example of execution by a communication device.

[0476] Step 1: UE-A sends an INVITE message to UE-B via CSCF-A and CSCF-B. This step 1 can also be understood as the process of UE-A calling UE-B.

[0477] Step 2: If the preset conditions are met, UE-B triggers the transmission of the second indication information.

[0478] The preset conditions include one or more of the following: UE-A is an NB-IoT GEO access, UE-A supports NB-IoT GEO access, UE-B is located within GEO coverage, UE-B is located within the GEO service range, etc., and the specifics are not limited here.

[0479] The second indication information is used to indicate the duration of GEO access and / or call setup for the UE-B. Further optionally, the second indication information may also indicate the media type (SDP-B) supported by the UE-B.

[0480] Step 3: UE-B sends a second indication message to CSCF-B.

[0481] Step 4: CSCF-B sends a 180 message to MMTel-AS-B. Alternatively, this can be understood as CSCF-B instructing MMTel-AS-B, based on the second instruction information, to play a ringtone to UE-A.

[0482] Step 5: MMTel-AS-B negotiates the media type with the ringback tone platform (CAT platform).

[0483] Step 6: MMTel-AS-B sends a ringtone to UE-A. That is, MMTel-AS-B obtains the ringtone media from the ringback tone platform and sends the ringtone to UE-A. The content of the ringtone indicates the UE-B's access type and / or call waiting / establishment time.

[0484] Step 7, UE-A plays the ringtone. For example, UE-A plays the ringtone to the calling user (the person making the call).

[0485] Step 8: UE-B sends 183 message (PANI, SDP-B) to CSCF-B.

[0486] Step 9: CSCF-B sends an AAR to PCRF-B.

[0487] Step 10: PCRF-B sends an AAR response to CSCF-B.

[0488] Step 11a: PCRF-B reserves resources for UE-B startup.

[0489] Step 11b: CSCF-B sends a 183 message to UE-A via CSCF-A.

[0490] Step 12, CSCF-A sends AAR to PCRF-A.

[0491] Step 13: PCRF-A sends an AAR response to CSCF-A.

[0492] Step 14: PCRF-A reserves resources for UE-A startup.

[0493] Step 15: UE-A sends a PRACK message to UE-B through CSCF-A and CSCF-B.

[0494] Step 16: UE-B sends 200 OK (PRACK) to UE-A via CSCF-B and CSCF-A.

[0495] Step 17: UE-A sends an UPDATE to UE-B via CSCF-A and CSCF-B.

[0496] Step 18: UE-B resource reservation completed.

[0497] Step 19, UE-B reminds the user.

[0498] Step 20: UE-B sends a 200 OK (UPDATE) to UE-A via CSCF-B and CSCF-A.

[0499] Step 21: UE-B sends a 180 ringing message to UE-A via CSCF-B and CSCF-A. This step is optional.

[0500] Step 22: UE-A stops the ringing and plays a ringtone. This step is optional.

[0501] Step 23, UE-B user response.

[0502] Step 24: UE-B sends 200 OK (INVITE) to UE-A via CSCF-B and CSCF-A.

[0503] Step 25a: UE-A stops the ringing / ringing and plays voice media.

[0504] Step 25b: UE-B plays audio media.

[0505] Step 26: UE-A sends an ACK to UE-B through CSCF-A and CSCF-B.

[0506] Step 27: UE-A and UE-B conduct session media transmission.

[0507] In this embodiment, steps 8 to 17 can be referred to the foregoing. Figure 11 The descriptions of steps 2 to 11 and step 16 in the illustrated embodiment will not be repeated here. Steps 18 to 27 in this embodiment can be referred to the foregoing. Figure 11 The descriptions of steps 2 to 17 and step 26 in the illustrated embodiment will not be repeated here.

[0508] In this embodiment, the scenario is IMS GEO. UE-B directly triggers a notification to UE-A that it is a GEO access, and the called party's IMS network element triggers a ringback tone playback, thus reducing the impact on the core network and the calling and called party's IMS network elements, and ensuring that the calling UE is notified as quickly as possible. For example, when the called UE-B receives the INVITE message, if it is an NB-IoT GEO access / supports NB-IoT GEO access / UE-B's location is under GEO coverage / UE-B's location is within the GEO service range, it instructs the IMS network element to send a ringtone to UE-A. Another example is that the indication information includes UE-B's GEO access / call setup time, and optionally also indicates its supported media type (SDP-B).

[0509] Example 7: The called terminal device is UE-B, the first IMS network element is CSCF-B (e.g., including one or more of the following: PCSCF-B, SSCCF-B, ICSCF-B), and the first core network element includes PCRF-B. The calling terminal device is UE-A, the second IMS network element is CSCF-A (e.g., including one or more of the following: PCSCF-A, SSCCF-A, ICSCF-A), and the second core network element includes PCRF-A. The radio access type (or access technology) of the called terminal device is GEO access, taking the application in an IMS GEO scenario as an example.

[0510] Please see Figure 13 This application provides another flowchart illustrating the communication method, which may include steps 1 to 27. Steps 1 to 27 may be executed by a communication device, or by some components of the communication device (e.g., a processor, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the communication device. The following description uses the example of execution by a communication device.

[0511] Step 1: UE-A sends an INVITE message to UE-B via CSCF-A and CSCF-B. This step 1 can also be understood as the process of UE-A calling UE-B.

[0512] Step 2: UE-B sends a 183 message (PANI, SDP-B) to CSCF-B.

[0513] Step 3: CSCF-B sends an AAR to PCRF-B.

[0514] Step 4: PCRF-B sends an AAR response to CSCF-B.

[0515] Step 5a: PCRF-B reserves resources for UE-B startup.

[0516] Step 5b: CSCF-B sends a 183 message to UE-A via CSCF-A.

[0517] Step 6: CSCF-A sends AAR to PCRF-A.

[0518] Step 7: PCRF-A sends an AAR response to CSCF-A.

[0519] Step 8: PCRF-A reserves resources for UE-A startup.

[0520] Step 9: UE-A sends a PRACK message to UE-B through CSCF-A and CSCF-B.

[0521] Step 10: UE-B sends 200 OK (PRACK) to UE-A via CSCF-B and CSCF-A.

[0522] Step 11: UE-A sends an UPDATE to UE-B via CSCF-A and CSCF-B.

[0523] Step 12: If the preset conditions are met, UE-B triggers the transmission of the second indication information.

[0524] The preset conditions include one or more of the following: UE-A is an NB-IoT GEO access, UE-A supports NB-IoT GEO access, UE-B is located within GEO coverage, UE-B is located within the GEO service range, etc., and the specifics are not limited here.

[0525] The second indication information is used to indicate the duration of GEO access and / or call setup for the UE-B. Further optionally, the second indication information may also indicate the media type (SDP-B) supported by the UE-B.

[0526] Optionally, the second indication information can also be a pre-alert message or a 180 message. For example, if the second indication information is a 180 message, it can also be sent after the INVITE message.

[0527] Step 13: UE-B sends a second indication message to CSCF-B.

[0528] Step 14: CSCF-B sends a 180 message to MMTel-AS-B. Alternatively, this can be understood as CSCF-B instructing MMTel-AS-B, based on the second instruction information, to play a ringtone to UE-A.

[0529] Step 15: MMTel-AS-B negotiates the media type with the ringback tone platform (CAT platform).

[0530] Step 16: MMTel-AS-B sends a ringtone to UE-A. That is, MMTel-AS-B obtains the ringtone media from the ringback tone platform and sends the ringtone to UE-A. The content of the ringtone indicates the UE-B's access type and / or call waiting / establishment time.

[0531] Step 17, UE-A plays a ringtone. For example, UE-A plays the ringtone to the calling user (the person making the call).

[0532] Step 18: UE-B resource reservation completed.

[0533] Step 19, UE-B reminds the user.

[0534] Step 20: UE-B sends a 200 OK (UPDATE) to UE-A via CSCF-B and CSCF-A.

[0535] Step 21: UE-B sends a 180 ringing message to UE-A via CSCF-B and CSCF-A. This step is optional.

[0536] Step 22: UE-A stops the ringing and plays a ringtone. This step is optional.

[0537] Step 23, UE-B user response.

[0538] Step 24: UE-B sends 200 OK (INVITE) to UE-A via CSCF-B and CSCF-A.

[0539] Step 25a: UE-A stops the ringing / ringing and plays voice media.

[0540] Step 25b: UE-B plays audio media.

[0541] Step 26: UE-A sends an ACK to UE-B through CSCF-A and CSCF-B.

[0542] Step 27: UE-A and UE-B conduct session media transmission.

[0543] In this embodiment, steps 2 to 11 can be referred to the foregoing. Figure 12 The descriptions of steps 8 to 17 in the illustrated embodiment will not be repeated here. Steps 12 to 17 in this embodiment can be referred to the foregoing. Figure 12 The descriptions of steps 2 to 7 in the illustrated embodiment will not be repeated here. Steps 18 to 27 in this embodiment can be referred to the foregoing. Figure 12 The descriptions of steps 12 to 27 in the illustrated embodiment will not be repeated here.

[0544] In this embodiment, the scenario is IMS GEO. UE-B directly triggers a notification to UE-A that it is a GEO access UE. The called party's IMS network element triggers a ringback tone playback, reducing the impact on the core network and the IMS network elements on both the calling and called parties, while ensuring timely notification to the calling UE. For example, when the called UE-B receives an UPDATE message, if it is an NB-IoT GEO access UE / supports NB-IoT GEO access UE / its location is within GEO coverage UE / its location is within GEO service range, it instructs the IMS network element to send a ringtone to UE-A. As another example, the indication information includes whether UE-B is a GEO access UE / call setup time, and optionally also indicates the supported media type (SDP-B).

[0545] Example 8: The called terminal device is UE-B, the first IMS network element is CSCF-B (e.g., including one or more of the following: PCSCF-B, SSCCF-B, ICSCF-B), and the first core network element includes PCRF-B. The calling terminal device is UE-A, the second IMS network element is CSCF-A (e.g., including one or more of the following: PCSCF-A, SSCCF-A, ICSCF-A), and the second core network element includes PCRF-A. The radio access type (or access technology) of the called terminal device is GEO access, taking the application in an IMS GEO scenario as an example.

[0546] Please see Figure 14 This application provides another flowchart illustrating the communication method, which may include steps 1 to 25. Steps 1 to 25 may be executed by a communication device, or by some components of the communication device (e.g., a processor, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the communication device. The following description uses the example of execution by a communication device.

[0547] Step 1: UE-A sends an INVITE message to UE-B via CSCF-A and CSCF-B. This step 1 can also be understood as the process of UE-A calling UE-B.

[0548] Step 2: If the preset conditions are met, UE-B triggers the transmission of the second indication information.

[0549] The preset conditions include one or more of the following: UE-A is an NB-IoT GEO access, UE-A supports NB-IoT GEO access, UE-B is located within GEO coverage, UE-B is located within the GEO service range, etc., and the specifics are not limited here.

[0550] The second indication information is used to indicate the duration of GEO access and / or call setup for the UE-B. Further optionally, the second indication information may also indicate the media type (SDP-B) supported by the UE-B.

[0551] Step 3: UE-B sends a second indication message to CSCF-B.

[0552] Step 4: CSCF-B sends third indication information to UE-A via CSCF-A. The function of the third indication information can be the same as the second indication information. For example, the third indication information is the same as the second indication information. Or, for another example, the third indication information is obtained by adjusting the second indication information.

[0553] Step 5: UE-A plays the corresponding prompt tone according to the third instruction information.

[0554] Step 5 and the above Figure 12 Step 7 in the illustrated embodiment is similar, with the UE-A playing a prompt tone to instruct the user to wait patiently.

[0555] Step 6: UE-B sends a 183 message (PANI, SDP-B) to CSCF-B.

[0556] Step 7: CSCF-B sends an AAR to PCRF-B.

[0557] Step 8: PCRF-B sends an AAR response to CSCF-B.

[0558] Step 9a: PCRF-B reserves resources for UE-B startup.

[0559] Step 9b: CSCF-B sends a 183 message to UE-A via CSCF-A.

[0560] Step 10: CSCF-A sends AAR to PCRF-A.

[0561] Step 11: PCRF-A sends an AAR response to CSCF-A.

[0562] Step 12: PCRF-A reserves resources for UE-A startup.

[0563] Step 13: UE-A sends a PRACK message to UE-B through CSCF-A and CSCF-B.

[0564] Step 14: UE-B sends 200 OK (PRACK) to UE-A via CSCF-B and CSCF-A.

[0565] Step 15: UE-A sends an UPDATE to UE-B via CSCF-A and CSCF-B.

[0566] Step 16: UE-B resource reservation completed.

[0567] Step 17, UE-B reminds the user.

[0568] Step 18: UE-B sends a 200 OK (UPDATE) to UE-A via CSCF-B and CSCF-A.

[0569] Step 19: UE-B sends a 180 ringing message to UE-A via CSCF-B and CSCF-A. This step is optional.

[0570] Step 20: UE-A stops the ringing and plays a ringtone. This step is optional.

[0571] Step 21, UE-B user response.

[0572] Step 22: UE-B sends 200 OK (INVITE) to UE-A via CSCF-B and CSCF-A.

[0573] Step 23a: UE-A stops the ringing / ringing and plays voice media.

[0574] Step 23b: UE-B plays audio media.

[0575] Step 24: UE-A sends an ACK to UE-B through CSCF-A and CSCF-B.

[0576] Step 25: UE-A and UE-B conduct session media transmission.

[0577] In this embodiment, steps 6 to 25 can be referred to the foregoing. Figure 12 The descriptions of steps 8 to 27 in the illustrated embodiment will not be repeated here.

[0578] Or to understand it as, Figure 14 Triggering timing and message as described above Figure 12 The embodiment shown is similar, except that in this embodiment, step 14 is to directly continue forwarding to UE-A (optionally, after receiving step 3, CSCF-B can determine the expected call setup time based on the GEO access indicated by UE-B, and then carry the call setup time and / or the indication of GEO access in step 4).

[0579] In this embodiment, the scenario is IMS GEO. UE-B directly triggers a notification to UE-A that it is a GEO access, and the called party's IMS network element triggers a ringback tone playback, thus reducing the impact on the core network and the IMS network elements on both the calling and called parties, and ensuring that the calling UE is notified as quickly as possible. For example, when the called UE-B receives the INVITE message, if it is an NB-IoT GEO access / supports NB-IoT GEO access / UE-B's location is under GEO coverage / UE-B's location is within the GEO service range, then it sends a ringtone to UE-A. Another example is that the indication information includes whether UE-B is a GEO access / call setup time, and optionally also indicates the supported media type (SDP-B).

[0580] The communication method in the embodiments of this application has been described above. The communication device in the embodiments of this application is described below. Please refer to [link / reference]. Figure 15This application provides an embodiment of the communication device 1500. This communication device 1500 can implement the functions of the terminal device or network device in the above method embodiments, and therefore also achieves the beneficial effects of the above method embodiments. In this application embodiment, the communication device 1500 can be a communication device, or it can be an integrated circuit or component inside the communication device, such as a chip. The communication device 1500 includes a transceiver unit 1501. Alternatively, the communication device 1500 includes a transceiver unit 1501 and a processing unit 1502, wherein the transceiver unit 1501 is used to perform any network element transmission and reception related operations in the above method embodiments, and the processing unit 1502 is used to perform other operations of any network element in the above method embodiments besides transmission and reception operations.

[0581] In one possible implementation, the communication device 1500 is as described above. Figures 1 to 14 The first IMS network element in the illustrated embodiment has the following functions for each unit:

[0582] The transceiver unit 1501 is used to receive first information sent by the first core network element or the subscribed network element or the called terminal device. The first information is used to indicate one or more of the following: the radio access type of the called terminal device and the call setup duration; the call setup duration is the call setup duration between the calling terminal device and the called terminal device, and the call setup duration is related to the radio access type.

[0583] The transceiver unit 1501 is also used to send second information to the second IMS network element or the calling terminal device. The second information is used to indicate one or more of the following: call setup duration, radio access type of the called terminal device; the second IMS network element is used to serve the calling terminal device.

[0584] Optionally, the transceiver unit 1501 is specifically used to send the second information to the second IMS network element or the calling terminal device when the calling terminal device accesses the network via a terrestrial network, or when the first IMS network element does not receive an instruction from the calling terminal device or the second IMS network element to prohibit ringback tones / ringing.

[0585] Optionally, the transceiver unit 1501 is specifically used to receive a session initiation message; the transceiver unit 1501 is specifically used to send second information to the second IMS network element or the calling terminal device in response to the session initiation message.

[0586] Optionally, the transceiver unit 1501 is specifically used to receive a response message to the session initiation message; after receiving the response message, the transceiver unit 1501 is specifically used to send second information to the second IMS network element or the calling terminal device.

[0587] Optionally, the transceiver unit 1501 is also used to send request information to the first core network element, the request information being used to query the wireless access type of the called terminal device.

[0588] Optionally, the second information is used to indicate one or more of the following to the user of the calling terminal device: call setup duration, and the radio access type of the called terminal device.

[0589] Optionally, the second information is included in the response message to the ringing message or session initiation message.

[0590] Optionally, the transceiver unit 1501 is also used to send third information, which is used to instruct the called terminal device to set to early ringing mode.

[0591] Optionally, the processing unit 1502 is used to determine the call setup duration based on the wireless access type of the called terminal device.

[0592] Optionally, the wireless access type includes satellite or non-satellite, with satellite specifically including one or more of the following: GEO, MEO, LEO.

[0593] In this embodiment, the operations performed by each unit in the communication device are the same as those described above. Figures 1 to 14 The description of the first IMS network element in the illustrated embodiment is similar and will not be repeated here.

[0594] In this embodiment, the transceiver unit 1501 can receive the first information sent by the first core network element to determine the wireless access type of the called terminal device, and then send the second information to the second IMS network element or the calling terminal device. The second information is used to indicate the call setup time between the calling terminal device and the called terminal device or the access type of the called terminal device, so that the calling terminal device can wait patiently and reduce the probability that the calling terminal device will hang up because it mistakenly thinks that there is a network problem or that the called terminal device is offline.

[0595] In another possible implementation, the communication device 1500 is as described above. Figures 1 to 14 The second IMS network element in the illustrated embodiment has the following functions for each unit:

[0596] Transceiver unit 1501 is used to receive second information, which indicates the call setup duration between the calling terminal equipment and the called terminal equipment or the radio access type of the called terminal equipment. The call setup duration is related to the radio access type.

[0597] The transceiver unit 1501 is also used to send fourth information to the calling terminal equipment, which is used to indicate the call setup duration or the wireless access type.

[0598] Optionally, the fourth information includes media data used to indicate to the user of the calling terminal device the call setup duration or the type of wireless access.

[0599] Optionally, the processing unit 1502 is used to determine the fourth information based on the wireless access type of the called terminal device.

[0600] Optionally, the transceiver unit 1501 is specifically used to send the fourth information to the calling terminal device after the calling bearer is established.

[0601] Optionally, the wireless access type includes satellite or non-satellite, with satellite specifically including one or more of the following: GEO, MEO, LEO.

[0602] In this embodiment, the operations performed by each unit in the communication device are the same as those described above. Figures 1 to 14 The description of the second IMS network element in the illustrated embodiment is similar and will not be repeated here.

[0603] In this embodiment, the transceiver unit 1501 can determine the wireless access type or call setup time of the called terminal device through the received second information, and then send the prompt to the calling terminal device, so that the calling terminal device can wait patiently, reducing the probability that the calling terminal device will hang up because it mistakenly thinks that there is a network problem or that the called terminal device is offline.

[0604] In another possible implementation, the communication device 1500 is as described above. Figures 1 to 14 The calling terminal device in the illustrated embodiment has the following functions for each unit:

[0605] The transceiver unit 1501 is used to receive ringtones, which are used to indicate the call setup time between the calling terminal equipment and the called terminal equipment or the wireless access type of the called terminal equipment. The call setup time is related to the wireless access type.

[0606] Processing unit 1502 is used to play ringtones.

[0607] Optionally, the wireless access type includes satellite or non-satellite, with satellite specifically including one or more of the following: GEO, MEO, LEO.

[0608] In this embodiment, the operations performed by each unit in the communication device are the same as those described above. Figures 1 to 14 The description of the calling terminal device in the illustrated embodiment is similar and will not be repeated here.

[0609] In this embodiment, the processing unit 1502 can play the ringtone received by the transceiver unit 1501. The ringtone is used to indicate the wireless access type or call setup time of the called terminal device, so that the user of the calling terminal device can wait patiently according to the ringtone, reducing the probability that the calling terminal device will hang up because it mistakenly thinks that there is a network problem or that the called terminal device is offline.

[0610] In another possible implementation, the communication device 1500 is as described above. Figures 1 to 14 The calling terminal device in the illustrated embodiment has the following functions for each unit:

[0611] The transceiver unit 1501 is used to receive first indication information, which is used to indicate the call setup time between the calling terminal equipment and the called terminal equipment or the wireless access type of the called terminal equipment. The call setup time is related to the wireless access type.

[0612] Processing unit 1502 is used to play a ringtone based on the first instruction information.

[0613] Optionally, the first instruction message is a 183 message.

[0614] Optionally, the ringtone is used to indicate one or more of the following to the user of the calling terminal device: call setup time, waiting time, and the wireless access type of the called terminal device.

[0615] Optionally, ringtones may include one or more of the following: voice, video, and text.

[0616] Optionally, the wireless access type includes satellite or non-satellite, with satellite specifically including one or more of the following: GEO, MEO, LEO.

[0617] In this embodiment, the operations performed by each unit in the communication device are the same as those described above. Figures 1 to 14 The description of the calling terminal device in the illustrated embodiment is similar and will not be repeated here.

[0618] In this embodiment, the processing unit 1502 can play a ringtone through the first instruction information received by the transceiver unit 1501, so that the user of the calling terminal device can wait patiently according to the ringtone, reducing the probability that the calling terminal device will hang up mistakenly thinking that there is a network problem or that the called terminal device is offline.

[0619] In another possible implementation, the communication device 1500 is as described above. Figures 1 to 14 The first core network element in the illustrated embodiment has the following functions:

[0620] The transceiver unit 1501 is used to receive request information from the first IMS network element. The request information is used to request the wireless access type of the called terminal device.

[0621] The transceiver unit 1501 is also used to send fifth information to the first IMS network element. The fifth information is used to indicate that the wireless access type of the called terminal device is geostationary orbit (GEO) access.

[0622] Optionally, the request information is a location information request (LIR) message, and the fifth information is a location information response (LIA) message.

[0623] Optionally, the processing unit 1502 is used to determine that the wireless access type of the called terminal device is GEO access.

[0624] Optionally, the processing unit 1502 is specifically used to determine that the wireless access type of the terminal device is GEO access based on the subscription information of the called terminal device.

[0625] Optionally, the wireless access type includes satellite or non-satellite, with satellite specifically including one or more of the following: GEO, MEO, LEO.

[0626] In this embodiment, the operations performed by each unit in the communication device are the same as those described above. Figures 1 to 14 The description of the first core network element in the illustrated embodiment is similar and will not be repeated here.

[0627] In this embodiment, the transceiver unit 1501 can send fifth information based on the request information from the first IMS network element, so that the first IMS network element can determine that the wireless access type of the called terminal device is GEO access based on the fifth information. This is to facilitate subsequent reminders to the calling terminal device to wait patiently, reducing the probability that the calling terminal device will mistakenly believe that there is a network problem or that the called terminal device is offline and hang up.

[0628] In another possible implementation, the communication device 1500 is as described above. Figures 1 to 14 The called terminal device in the illustrated embodiment has the following functions for each unit:

[0629] The transceiver unit 1501 is used to send first information when the wireless access type of the called terminal device is GEO access. The first information is used to indicate one or more of the following: the wireless access type of the called terminal device is GEO access, and the call setup duration; the call setup duration is the call setup duration between the calling terminal device and the called terminal device, and the call setup duration is related to the wireless access type.

[0630] Optionally, the first information is also used to indicate the media types supported by the called terminal device and / or the calling terminal device.

[0631] Optionally, the wireless access type of the called terminal device is GEO access, including: the current wireless access type of the called terminal device is GEO access, the called terminal device supports GEO access, the location of the called terminal device is within the GEO coverage area or service area, and receiving indication information from the operating system or application layer or user of the called terminal device, the indication information being used to indicate GEO access or to indicate the transmission of first information.

[0632] Optionally, the first information is further used to instruct the calling terminal device to notify the user of the calling terminal device of the call setup duration or the radio access type of the called terminal device; or, the first information is further used to instruct the first IMS network element to notify the user of the calling terminal device of the call setup duration or the radio access type of the called terminal device.

[0633] Optionally, the first information is also used to instruct the second IMS network element to send media to the calling terminal device, the media being used to notify the user of the calling terminal device of the call setup duration or the radio access type of the called terminal device.

[0634] Optionally, the transceiver unit 1501 is also used to receive INVITE or UPDATE messages from the calling terminal device.

[0635] Optionally, an INVITE or UPDATE message is used to trigger the sending of the first message.

[0636] In this embodiment, the operations performed by each unit in the communication device are the same as those described above. Figures 1 to 14 The description of the called terminal device in the illustrated embodiment is similar and will not be repeated here.

[0637] In this embodiment, for the IMS GEO scenario, the transceiver unit 1501 directly notifies the called terminal device that it is accessing via GEO, and the called side IMS network element triggers the ringback tone playback, thereby reducing the impact on the core network and the calling side IMS network element.

[0638] Please see Figure 16 This is another schematic structural diagram of the communication device 1600 provided in this application. The communication device 1600 includes a logic circuit 1601 and an input / output interface 1602. The communication device 1600 can be a chip or an integrated circuit.

[0639] Optionally, Figure 16 The input / output interface 1602 in the middle can be equivalent to Figure 15 The transceiver unit 1501 shown may include an input interface and an output interface 1602. Alternatively, the communication interface may also be a transceiver circuit, which may include an input interface circuit and an output interface circuit. Figure 16 The logic circuit 1601 in the text can be equivalent to... Figure 15The processing unit 1502 shown.

[0640] The logic circuit 1601 and the input / output interface 1602 can also perform other steps performed by the network device or terminal device in any embodiment and achieve corresponding beneficial effects, which will not be elaborated here.

[0641] For example, when the communication device 1600 is the first IMS network element, the input / output interface 1602 can be used for one or more of the following: receiving first information, sending second information, receiving a session initiation message, receiving a response message to the session initiation message, sending request information, sending third information, etc. The logic circuit 1601 can be used to determine the call setup duration based on the wireless access type of the called terminal device, etc.

[0642] For example, when the communication device 1600 is a second IMS network element, the input / output interface 1602 can be used for one or more of the following: receiving second information, sending a fourth message, etc. The logic circuit 1601 can be used to determine the fourth information based on the wireless access type of the called terminal device, etc.

[0643] For example, when the communication device 1600 is a calling terminal device, the input / output interface 1602 can be used for one or more of the following: receiving second information, receiving fourth information, etc. The logic circuit 1601 can be used to play a ringtone based on the second or fourth information, etc.

[0644] For example, when the communication device 1600 is a first core network element, the input / output interface 1602 can be used for one or more of the following: receiving request information, sending a fifth message, etc. The logic circuit 1601 can be used to determine whether the wireless access type of the called terminal device is GEO access, etc.

[0645] Optionally, the logic circuit 1601 can be a processing device, the functions of which can be partially or entirely implemented in software.

[0646] Optionally, the processing apparatus may include a memory and a processor, wherein the memory is used to store a computer program, and the processor reads and executes the computer program stored in the memory to perform the corresponding processing and / or steps in any of the method embodiments.

[0647] Optionally, the processing device may consist of only a processor. A memory for storing computer programs is located outside the processing device, and the processor is connected to the memory via circuitry / wires to read and execute the computer programs stored in the memory. The memory and processor may be integrated together or physically independent of each other.

[0648] Optionally, the processing device may be one or more chips, or one or more integrated circuits. For example, the processing device may be one or more field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), system on-chips (SoCs), central processors (CPUs), network processors (NPs), digital signal processors (DSPs), microcontroller units (MCUs), programmable logic devices (PLDs), or other integrated chips, or any group of the above chips or processors.

[0649] Please see Figure 17 The communication device 1700 mentioned in the above embodiments provided in this application can specifically be a communication device that serves as a network device or a terminal device in the above embodiments, or it can be a chip or functional module in a network device or a terminal device.

[0650] The present invention provides a possible logical structure diagram of the communication device 1700, which may include, but is not limited to, at least one processor 1701 and a communication port 1702.

[0651] Optionally, Figure 17 Communication port 1702 in the middle can be equivalent to Figure 15 The transceiver unit 1501 shown may include an input interface and an output interface for its communication port 1702. Alternatively, the communication port 1702 may also be a transceiver circuit, which may include an input interface circuit and an output interface circuit.

[0652] Further optionally, the device may also include at least one of a memory 1703 and a bus. In embodiments of this application, the at least one processor 1701 is used to control the operation of the communication device 1700. The memory 1703 is used to store device program code and / or data. Optionally, the processor 1701 may be equivalent to... Figure 15 The processing unit 1502 shown.

[0653] For example, when the communication device 1700 is the first IMS network element, the communication port 1702 can be used for one or more of the following: receiving first information, sending second information, receiving a session initiation message, receiving a response message to the session initiation message, sending request information, sending third information, etc. At least one processor 1701 can be used to determine the call setup duration based on the radio access type of the called terminal device, etc.

[0654] For example, when the communication device 1700 is a second IMS network element, the communication port 1702 can be used for one or more of the following: receiving second information, sending a fourth message, etc. At least one processor 1701 can be used to determine the fourth information based on the radio access type of the called terminal device, etc.

[0655] For example, when the communication device 1700 is a calling terminal device, the communication port 1702 can be used for one or more of the following: receiving second information, receiving fourth information, etc. At least one processor 1701 can be used to play a ringtone based on the second or fourth information, etc.

[0656] For example, when the communication device 1700 is a first core network element, the communication port 1702 can be used for one or more of the following: receiving request information, sending a fifth message, etc. At least one processor 1701 can be used to determine whether the wireless access type of the called terminal device is GEO access, etc.

[0657] Furthermore, the processor 1701 can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, etc. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0658] It is understandable that this application relates to Figure 17 The number of each component shown is not limited. For example, the number of processors 1701, communication ports 1702, and memory 1703 can each be one or more, and the specific number is not limited here.

[0659] It should be noted that, Figure 17 The communication device 1700 shown can be used to implement the steps of any network element in the aforementioned method embodiments and achieve the corresponding technical effects. Figure 17 The specific implementation of the communication device shown can be referred to the description in the foregoing method embodiments, and will not be repeated here.

[0660] When the aforementioned communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above method embodiments. The terminal chip receives information from other modules (such as radio frequency modules or antennas) in the terminal, information sent to the terminal by IMS network elements or core network elements; or, the terminal chip sends information to other modules (such as radio frequency modules or antennas) in the terminal, information sent by the terminal to IMS network elements or core network elements. For example, in the case of a terminal, sending information can be understood as the process of the terminal's chip outputting information.

[0661] When the aforementioned communication device is a module applied to an IMS network element or core network element, the IMS network element or core network element module implements the functions of the IMS network element or core network element in the above method embodiments. The IMS network element or core network element module receives information from other modules (such as radio frequency modules or antennas) within the IMS network element or core network element, which is information sent by the terminal to the IMS network element or core network element; or, the IMS network element or core network element module sends information to other modules (such as radio frequency modules or antennas) within the IMS network element or core network element, which is information sent by the IMS network element or core network element to the terminal. For example, in the case of an IMS network element or core network element, the sending of information by the IMS network element or core network element can be understood as the process of the IMS network element or core network element's chip outputting information.

[0662] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in an IMS network element, core network element, or terminal. The processor and storage medium can also exist as discrete components in an IMS network element, core network element, or terminal.

[0663] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer programs or instructions. When a computer program or instruction is loaded and executed on a computer, all or part of the processes or functions of the embodiments of this application are performed. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, a computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0664] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

Claims

1. A communication method characterized by comprising: The method is applied to a first Internet Protocol Multimedia Subsystem (IMS) network element, the first IMS network element being used to serve called terminal equipment, the method comprising: The system receives first information sent by a first core network element, a subscribed network element, or the called terminal device. The first information is used to indicate one or more of the following: the radio access type of the called terminal device and the call setup duration; the call setup duration is the call setup duration between the calling terminal device and the called terminal device, and the call setup duration is related to the radio access type. Send second information to the second IMS network element or the calling terminal device, the second information being used to indicate one or more of the following: the call setup duration, the radio access type of the called terminal device; the second IMS network element is used to serve the calling terminal device.

2. The method of claim 1, wherein, Sending the second information to the second IMS network element or the calling terminal device includes: When the calling terminal device accesses the network via a terrestrial network, or when the first IMS network element does not receive an instruction from the calling terminal device or the second IMS network element to prohibit ringback tones / ringing, the second information is sent to the second IMS network element or the calling terminal device.

3. The method of claim 1, wherein, Sending the second information to the second IMS network element or the calling terminal device includes: Receive session initiation message; In response to the session initiation message, the second information is sent to the second IMS network element or the calling terminal device.

4. The method of claim 1, wherein, Sending the second information to the second IMS network element or the calling terminal device includes: Receive a response message to the session initiation message; After receiving the response message, the second information is sent to the second IMS network element or the calling terminal device.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Send a request message to the first core network element or the contracted network element. The request message is used to query the wireless access type of the called terminal device.

6. The method according to any one of claims 1 to 5, characterized in that, The second information is used to indicate one or more of the following to the user of the calling terminal device: the call setup duration and the wireless access type of the called terminal device.

7. The method according to any one of claims 1 to 6, characterized in that, The second information is included in the response message of the ringing message or session initiation message.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: Send a third message, which is used to instruct the called terminal device to set to early ringing mode.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: The call setup duration is determined based on the wireless access type of the called terminal device.

10. The method according to any one of claims 1 to 9, characterized in that, The wireless access type includes one or more of the following: geostationary orbit (GEO), medium Earth orbit (MEO), and low Earth orbit (LEO).

11. A communication method, comprising: The method is applied to a second Internet Protocol Multimedia Subsystem (IMS) network element, which serves calling terminal equipment. The method includes: The system receives second information, which indicates the call setup duration between the calling terminal device and the called terminal device or the radio access type of the called terminal device, wherein the call setup duration is related to the radio access type. Send a fourth message to the calling terminal device, the fourth message being used to indicate the call setup duration or the wireless access type.

12. The method of claim 11, wherein, The fourth piece of information includes media data, which is used to indicate the call setup duration or the wireless access type to the user of the calling terminal device.

13. The method of claim 12, wherein, The method further includes: The fourth information is determined based on the wireless access type of the called terminal device.

14. The method according to any one of claims 11 to 13, characterized in that, Sending the fourth information to the calling terminal device includes: After the calling bearer is established, the fourth information is sent to the calling terminal device.

15. The method according to any one of claims 11 to 14, characterized in that, The wireless access type includes one or more of the following: GEO, MEO, LEO.

16. A method of communication, comprising: The method is applied to a calling terminal device or a chip in the calling terminal device, and the method includes: Receive a ringtone, the ringtone being used to indicate the call setup time between the calling terminal device and the called terminal device or the wireless access type of the called terminal device, the call setup time being related to the wireless access type; Play the aforementioned ringtone.

17. The method of claim 16, wherein, The wireless access type includes one or more of the following: GEO, MEO, LEO.

18. A method of communication, comprising: The method is applied to a calling terminal device or a chip in the calling terminal device, and the method includes: Receive first indication information, the first indication information being used to indicate the call setup duration between the calling terminal device and the called terminal device or the wireless access type of the called terminal device, the call setup duration being related to the wireless access type; Play a ringtone based on the first instruction information.

19. The method of claim 18, wherein, The first indication message is message 183.

20. The method of claim 18 or 19, wherein, The ringtone is used to indicate to the user of the calling terminal device one or more of the following: the call setup time, waiting time, and the wireless access type of the called terminal device.

21. The method of any one of claims 18-20, wherein, The ringtone may include one or more of the following: voice, video, and text.

22. The method of any one of claims 18-21, wherein, The wireless access type includes one or more of the following: GEO, MEO, LEO.

23. A method of communication, comprising: The method is applied to a first core network element or a contracted network element, and the method includes: Receive request information from a first IMS network element, the request information being used to request the wireless access type of the called terminal device; Send a fifth message to the first IMS network element, the fifth message being used to indicate that the wireless access type of the called terminal device is geostationary orbit (GEO) access.

24. The method of claim 23, wherein, The request information is a Location Information Request (LIR) message, and the fifth information is a Location Information Response (LIA) message.

25. The method of claim 23 or 24, wherein, The method further includes: The wireless access type of the called terminal device is determined to be GEO access.

26. The method of claim 25, wherein, Determining that the wireless access type of the called terminal device is GEO access includes: Based on the subscription information of the called terminal device, the wireless access type of the terminal device is determined to be GEO access.

27. The method of any one of claims 23-26, wherein, The wireless access type includes one or more of the following: GEO, MEO, LEO.

28. A method of communication, comprising: The method is applied to a called terminal device or a chip in the called terminal device, and the method includes: When the wireless access type of the called terminal device is GEO access, a first message is sent, the first message indicating one or more of the following: the wireless access type of the called terminal device is GEO access, and the call setup duration; the call setup duration is the call setup duration between the calling terminal device and the called terminal device, and the call setup duration is related to the wireless access type.

29. The method of claim 28, wherein, The first information is also used to indicate the media types supported by the called terminal device and / or the calling terminal device.

30. The method of claim 28, wherein, The wireless access type of the called terminal device is GEO access, including: The called terminal device currently uses GEO access as its wireless access type. The called terminal device supports the GEO access. The location of the called terminal device is within the GEO coverage area or service area. The system receives an instruction from the operating system, application layer, or user of the called terminal device. The instruction is used to instruct the GEO to access or to instruct the transmission of the first information.

31. The method of any one of claims 28-30, wherein, The first information is also used to instruct the calling terminal device to notify the user of the calling terminal device of the call setup duration or the wireless access type of the called terminal device, or, The first information is also used to instruct the first IMS network element to notify the user of the calling terminal device of the call setup duration or the wireless access type of the called terminal device.

32. The method of any one of claims 28-31, wherein, The first information is also used to instruct the second IMS network element to send media to the calling terminal device, the media being used to notify the user of the calling terminal device of the call setup duration or the wireless access type of the called terminal device.

33. The method of any one of claims 28-32, wherein, The method further includes: Receive an INVITE message or UPDATE message from the calling terminal device.

34. The method of claim 33, wherein, The INVITE message or the UPDATE message is used to trigger the sending of the first information.

35. A communications device, characterized by Includes a module for performing the method as described in any one of claims 1 to 34.

36. A communications device, characterized by It includes at least one processor for executing a computer program or instructions in memory to implement the method as described in any one of claims 1 to 34.

37. A chip or chip system, characterized by The chip or chip system is used to perform the method as described in any one of claims 1 to 34.

38. A communication system, characterized in that, It includes one or more of the following: a communication device for performing the method of any one of claims 1 to 10, a communication device for performing the method of any one of claims 11 to 15, a communication device for performing the method of claim 16 or 17, a communication device for performing the method of any one of claims 18 to 22, a communication device for performing the method of any one of claims 23 to 27, and a communication device for performing the method of any one of claims 28 to 34.

39. A readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1 to 34.

40. A computer program product, characterized in that, Includes a computer program or instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1 to 34.

Images