Information transmission method and device, equipment, storage medium and computer program product

Abstract

The application discloses an information transmission method, device, equipment, storage medium and computer program product. The method comprises the following steps: a terminal sends terminal support high-orbit satellite IP multimedia subsystem communication capability information to a first core network network element.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to an information transmission method, apparatus, device, storage medium, and computer program product. Background Technology

[0002] Currently, for scenarios where terminals directly connect to satellites, a networking requirement has been proposed whereby User Equipment (UE) directly connects to a Geostationary Orbit (GEO) satellite to access the terrestrial network and provide IP Multimedia Subsystem (IMS) calls. However, in establishing IMS calls between terminals and GEO satellites, there are problems such as large communication latency leading to timer timeouts and call releases, resulting in low connection rates, poor user experience, and wasted network resources. Summary of the Invention

[0003] In view of the above, embodiments of this application aim to provide an information transmission method, apparatus, device, storage medium, and computer program product.

[0004] The technical solution of this application embodiment is implemented as follows:

[0005] This application provides an information transmission method applied to a terminal, the method comprising:

[0006] Send information about the terminal's IP multimedia subsystem communication capabilities supporting high-orbit satellites to the first core network element.

[0007] Furthermore, according to at least one embodiment of this application, the method further includes:

[0008] The system receives first information sent by the first core network element, wherein the first information represents the simplified requirements of the Session Initiation Protocol (SIP) signaling message and the setting rules of the SIP protocol timer.

[0009] Furthermore, according to at least one embodiment of this application, the simplification requirements for the SIP signaling message include at least one of the following:

[0010] Simplification requirements of the SIP method;

[0011] Simplified requirements for SIP message header fields;

[0012] Simplified requirements for SIP Uniform Resource Identifiers (URIs);

[0013] Simplified message body requirements;

[0014] The simplification requirements of the SIP mechanism.

[0015] Furthermore, according to at least one embodiment of this application, the simplification requirements of the SIP method include:

[0016] Retain the INVITE, ACK, BYE, CANCEL, REGISTER, PRACK, and MESSAGE methods; remove the SUBSCRIBE, NOTIFY, PUBLISH, INFO, REFER, UPDATE, and OPTIONS methods.

[0017] The simplified requirements for the SIP message header fields include:

[0018] Retain the following necessary header fields: from, to, via, Call-ID, Max-Forwards, CONTACT, Content-Type, Content-Length; simplify header fields to use 1 or 2 letters for replacement.

[0019] The simplified requirements for the SIP URI include:

[0020] Retain the variable portion of the domain name part of the SIP URI and remove the fixed portion of the domain name part of the SIP URI;

[0021] The simplified requirements for the message body include:

[0022] Multiple message bodies are not supported. The message body type for SIP voice messages is application or sdp, and the message body type for SIP short messages is application or vnd.3gpp.sms. The SDP in the message body of SIP voice messages retains v, o, s, c and m, and the IMS protocol is required. The necessary a line describing low bitrate encoding and decoding is also retained.

[0023] The simplification requirements of the SIP mechanism include:

[0024] Support for the following mechanisms is not required: reliable transport of temporary responses, resource reservation, and SIP protocol encryption via Transport Layer Security (TLS).

[0025] Furthermore, according to at least one embodiment of this application,

[0026] The step of sending information about the terminal's IP multimedia subsystem communication capabilities for high-orbit satellites to the first core network element includes:

[0027] Information about the terminal's IP multimedia subsystem communication capabilities supporting high-orbit satellites is sent to the first core network element through the access network element and the second core network element.

[0028] Furthermore, according to at least one embodiment of this application, the second core network element includes a mobility management network element, a core network data network element, and a call session control function.

[0029] Furthermore, according to at least one embodiment of this application, the method further includes:

[0030] The duration of the SIP protocol timer is adjusted according to the setting rules.

[0031] Furthermore, according to at least one embodiment of this application, the method further includes:

[0032] Obtain the address of the first core network element and the duration of the registration timer sent by the third core network element.

[0033] Furthermore, according to at least one embodiment of this application, the method further includes:

[0034] The registration timer of the terminal is adjusted according to the duration of the registration timer.

[0035] At least one embodiment of this application provides an information transmission method applied to a first core network element, the method comprising:

[0036] Obtain information from the terminal regarding its IP Multimedia Subsystem communication capabilities with high-orbit satellites.

[0037] Furthermore, according to at least one embodiment of this application, the method further includes:

[0038] Obtain high-orbit satellite access information sent by the access network element, wherein the high-orbit satellite access information includes satellite access type, satellite identifier, and satellite ephemeris.

[0039] Furthermore, according to at least one embodiment of this application, obtaining the terminal's IP Multimedia Subsystem communication capability information for high-orbit satellites, as sent by the terminal, includes:

[0040] The terminal obtains information on its IP multimedia subsystem communication capabilities with high-orbit satellites, sent from the access network element and the second core network element to the first core network element.

[0041] Furthermore, according to at least one embodiment of this application, obtaining high-orbit satellite access information sent by the access network element includes: obtaining high-orbit satellite access information sent by the access network element to the first core network element through the second core network element.

[0042] Furthermore, according to at least one embodiment of this application, the method further includes:

[0043] Send first information to the terminal, wherein the first information represents the simplification requirements of SIP signaling messages and the setting rules of SIP protocol timers.

[0044] Furthermore, according to at least one embodiment of this application, the simplification requirements for the SIP signaling message include at least one of the following:

[0045] Simplification requirements of the SIP method;

[0046] Simplified requirements for SIP message header fields;

[0047] Simplified requirements for SIP URIs;

[0048] Simplified message body requirements;

[0049] The simplification requirements of the SIP mechanism.

[0050] Furthermore, according to at least one embodiment of this application, the simplification requirements of the SIP method include:

[0051] Retain the INVITE, ACK, BYE, CANCEL, REGISTER, PRACK, and MESSAGE methods; remove the SUBSCRIBE, NOTIFY, PUBLISH, INFO, REFER, UPDATE, and OPTIONS methods.

[0052] The simplified requirements for the SIP message header fields include:

[0053] Retain the following necessary header fields: from, to, via, Call-ID, Max-Forwards, CONTACT, Content-Type, Content-Length; simplify header fields to use 1 or 2 letters for replacement.

[0054] The simplified requirements for the SIP URI include:

[0055] Retain the variable portion of the domain name part of the SIP URI and remove the fixed portion of the domain name part of the SIP URI;

[0056] The simplified requirements for the message body include:

[0057] Multiple message bodies are not supported. The message body type for SIP voice messages is application or sdp, and the message body type for SIP short messages is application or vnd.3gpp.sms. The SDP in the message body of SIP voice messages retains v, o, s, c and m, and the IMS protocol is required. The necessary a line describing low bitrate encoding and decoding is also retained.

[0058] The simplification requirements of the SIP mechanism include:

[0059] Support for the following mechanisms is not required: reliable transport of temporary responses, resource reservation, and SIP protocol encrypted with TLS.

[0060] Furthermore, according to at least one embodiment of this application, the first core network element is the calling core network element, and the method further includes:

[0061] Perform the calling party dialing (MO, Mobile Originated) procedure, and / or perform the called party calling (MT, Mobile Terminated) procedure.

[0062] Furthermore, according to at least one embodiment of this application, the execution of the MO process includes:

[0063] Obtain a simplified initial call request sent by the calling terminal;

[0064] Send a simplified call intermediate response to the calling terminal;

[0065] The duration of the SIP protocol timer is adjusted to convert the simplified initial call request into a complete call request, and the complete call request is sent to the called terminal; wherein the complete call request carries an indication that resource reservation is not supported;

[0066] Obtain the call intermediate response sent by the called terminal, which carries a Session Description Protocol (SDP) response (ANSWER);

[0067] A provisional response acknowledgement (PRACK) message is returned to the called terminal.

[0068] Obtain the call intermediate response sent by the called terminal in response to the PRACK message;

[0069] Return a PRACK message to the called terminal and send a simplified call intermediate response to the calling terminal that does not require reliable transmission of the interim response;

[0070] Receive the call intermediate response returned by the called terminal;

[0071] Send a simplified call intermediate response carrying an SDP ANSWER to the calling terminal;

[0072] Receive a simplified acknowledgment (ACK) message sent by the calling terminal;

[0073] The simplified ACK message is converted into a complete ACK message, and the complete ACK message is sent to the called terminal to complete the call establishment;

[0074] Obtain the simplified end-of-life (BYE) request sent by the calling terminal;

[0075] Return a call response to the calling terminal, convert the simplified BYE request into a complete BYE request, and send the complete BYE request to the called terminal;

[0076] Obtain the call response sent by the called terminal to end the call.

[0077] Furthermore, according to at least one embodiment of this application, the execution of the MT process includes:

[0078] Obtain the initial call request sent by the called terminal;

[0079] The duration of the SIP protocol timer is adjusted to send a simplified initial call request to the calling terminal, wherein the SDP carried in the simplified initial call request is a low-bit-rate SDP.

[0080] Obtain the simplified call intermediate response sent by the calling terminal;

[0081] Send an intermediate call response carrying a universal codec SDP ANSWER to the called terminal;

[0082] Obtain the PRACK message sent by the called terminal, and send a call response to the PRACK message to the called terminal;

[0083] Obtain the simplified call intermediate response sent by the calling terminal;

[0084] The simplified intermediate call response is converted into a complete intermediate call response that requires reliable transmission of the interim response, and the complete intermediate call response is sent to the called terminal.

[0085] Obtain the PRACK message sent by the called terminal, and send a call response to the PRACK message to the called terminal;

[0086] Obtain the simplified call answer response carrying SDP ANSWER sent by the calling terminal;

[0087] Save the SDP ANSWER, convert the simplified call answer response into a complete call answer response, and send the complete call answer response to the called terminal; the complete call answer response does not carry SDP.

[0088] Obtain the ACK message sent by the called terminal, convert the ACK message into a simplified ACK message, and send the simplified ACK message to the calling terminal to complete the call establishment;

[0089] Obtain the BYE request sent by the called terminal;

[0090] Send a call response to the called terminal, convert the BYE request into a simplified BYE request, and send the simplified BYE request to the calling terminal;

[0091] Obtain the call response returned by the calling terminal to end the call.

[0092] At least one embodiment of this application provides an information transmission method applied to a core network data element, the method comprising:

[0093] The terminal obtains information on its IP multimedia subsystem communication capabilities with high-orbit satellites, sent by the terminal through the access network element and the mobility management network element.

[0094] Furthermore, according to at least one embodiment of this application, the method further includes:

[0095] The high-orbit satellite access information sent by the access network element through the mobility management network element is obtained, wherein the high-orbit satellite access information includes satellite access type, satellite identifier, and satellite ephemeris.

[0096] Furthermore, according to at least one embodiment of this application, the method further includes:

[0097] Through the call session control function, information on the terminal's IP multimedia subsystem communication capability for high-orbit satellites and / or high-orbit satellite access information is sent to the first core network element.

[0098] Furthermore, according to at least one embodiment of this application, the method further includes:

[0099] Send user access satellite data to the application server; wherein, the user access satellite data includes information on the terminal's IP multimedia subsystem communication capability supporting high-orbit satellites and / or high-orbit satellite access information, the high-orbit satellite access information including satellite access type, satellite identifier, and satellite ephemeris.

[0100] At least one embodiment of this application provides an information transmission method applied to an application server, the method comprising:

[0101] Acquire user access satellite data; wherein, the user access satellite data includes information on the terminal's IP multimedia subsystem communication capabilities supporting high-orbit satellites and / or high-orbit satellite access information, the high-orbit satellite access information including satellite access type, satellite identifier, and satellite ephemeris.

[0102] Furthermore, according to at least one embodiment of this application, the method further includes:

[0103] Based on the user-accessed satellite data, business management or processing is performed;

[0104] The aforementioned business management or processing includes:

[0105] Encoding and decoding processing;

[0106] Inbound and outbound call processing for business.

[0107] Furthermore, according to at least one embodiment of this application, obtaining user access satellite data includes:

[0108] The user access satellite data is obtained from the core network data element where the terminal is located; or, the user access satellite data is obtained from the core network data element.

[0109] At least one embodiment of this application provides an information transmission device, comprising:

[0110] Sending module,

[0111] The sending module is used to send information about the terminal's IP multimedia subsystem communication capabilities supporting high-orbit satellites to the first core network element.

[0112] At least one embodiment of this application provides an information transmission device, comprising:

[0113] The first acquisition module is used to acquire information on the terminal's ability to support IP multimedia subsystem communication with high-orbit satellites, sent by the terminal.

[0114] At least one embodiment of this application provides an information transmission device, comprising:

[0115] The second acquisition module is used to acquire information on the terminal's ability to support IP Multimedia Subsystem communication with high-orbit satellites, sent by the terminal through the access network element and the mobility management network element.

[0116] At least one embodiment of this application provides an information transmission device, comprising:

[0117] The third acquisition module is used to acquire user access satellite data; wherein, the user access satellite data includes information on the terminal's IP multimedia subsystem communication capabilities supporting high-orbit satellites and / or high-orbit satellite access information, and the high-orbit satellite access information includes satellite access type, satellite identifier, and satellite ephemeris.

[0118] At least one embodiment of this application provides a terminal, including a processor and a memory for storing a computer program capable of running on the processor.

[0119] When the processor runs the computer program, it executes the steps of any of the methods described above on the terminal side.

[0120] At least one embodiment of this application provides a first core network element, including a processor and a memory for storing a computer program capable of running on the processor.

[0121] When the processor runs the computer program, it executes the steps of any one of the methods described above for the first core network element.

[0122] At least one embodiment of this application provides a core network data element, including a processor and a memory for storing computer programs capable of running on the processor.

[0123] When the processor runs the computer program, it executes the steps of any one of the methods described above for the core network data element side.

[0124] At least one embodiment of this application provides an application server, including a processor and a memory for storing computer programs capable of running on the processor.

[0125] When the processor runs the computer program, it executes the steps of any of the methods described above on the application server side.

[0126] At least one embodiment of this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the methods described above.

[0127] At least one embodiment of this application provides a computer program product, including a computer program that, when executed by a processor, implements the method described in any of the above-described embodiments.

[0128] The information transmission method, apparatus, device, storage medium, and computer program product provided in this application embodiment include a terminal sending information about its IP multimedia subsystem communication capability supporting high-orbit satellites to a first core network element.

[0129] Using the technical solution provided in this application embodiment, the terminal reports the IP Multimedia Subsystem communication capability information supporting high-orbit satellites to the first core network element. Subsequently, the first core network element can send the simplified requirements of SIP signaling messages and the setting rules of SIP protocol timers to the terminal. Both the first core network element and the terminal simplify the SIP signaling messages and adjust the duration of the SIP protocol timers. By optimizing the size of the SIP signaling messages and adjusting the timer settings, the communication delay does not exceed the set duration of the timer, thereby avoiding the problem of call release due to timer timeout caused by large communication delays. This improves the connection success rate, user experience, and network resource utilization during the IMS call establishment process. Attached Figure Description

[0130] Figure 1 This is a schematic diagram illustrating the networking requirements for IMS calls in related technologies;

[0131] Figure 2 This is a schematic diagram of the IMS call establishment process in related technologies;

[0132] Figure 3 This is a schematic diagram of the networking architecture based on the packet evolution core network in an embodiment of this application;

[0133] Figure 4 This is a schematic diagram of the network architecture based on the 5G core network in an embodiment of this application;

[0134] Figure 5 This is a schematic diagram of the implementation flow of the information transmission method in the embodiments of this application. Figure 1 ;

[0135] Figure 6 This is a schematic diagram illustrating the implementation process of a terminal sending capability information to a core network data element in an embodiment of this application. Figure 1 ;

[0136] Figure 7 This is a schematic diagram illustrating the implementation process of a terminal sending capability information to a core network data element in an embodiment of this application. Figure 2 ;

[0137] Figure 8 This is a schematic diagram illustrating the implementation process of the first core network element obtaining terminal capability information in an embodiment of this application;

[0138] Figure 9 This is a schematic diagram of the implementation flow of the information transmission method in the embodiments of this application. Figure 2 ;

[0139] Figure 10 This is a schematic diagram of the MO process in an embodiment of this application;

[0140] Figure 11This is a schematic diagram of the MT process in an embodiment of this application;

[0141] Figure 12 This is a schematic diagram of the implementation flow of the information transmission method in the embodiments of this application. Figure 3 ;

[0142] Figure 13 This is a schematic diagram of the implementation flow of the information transmission method in the embodiments of this application. Figure 4 ;

[0143] Figure 14 This is a schematic diagram of the composition of the information transmission device according to an embodiment of this application. Figure 1 ;

[0144] Figure 15 This is a schematic diagram of the composition of the information transmission device according to an embodiment of this application. Figure 2 ;

[0145] Figure 16 This is a schematic diagram of the composition of the information transmission device according to an embodiment of this application. Figure 3 ;

[0146] Figure 17 This is a schematic diagram of the composition of the information transmission device according to an embodiment of this application. Figure 4 ;

[0147] Figure 18 This is a schematic diagram of the component structure of the terminal in an embodiment of this application;

[0148] Figure 19 This is a schematic diagram of the composition structure of the first core network element in an embodiment of this application;

[0149] Figure 20 This is a schematic diagram of the composition structure of the core network data network elements in an embodiment of this application;

[0150] Figure 21 This is a schematic diagram of the composition structure of the application server in an embodiment of this application. Detailed Implementation

[0151] Before introducing the technical solutions of the embodiments of this application, the relevant technologies will be introduced first.

[0152] See Figure 1 , Figure 1 This is a diagram illustrating the networking requirements for IMS calls in related technologies, such as... Figure 1 As shown, for scenarios where terminals are directly connected to satellites, a networking requirement is proposed for User Equipment (UE) to directly connect to a Geostationary Orbit (GEO) satellite to access the terrestrial network and provide IMS calls.

[0153] See Figure 2 , Figure 2 This is a schematic diagram of the IMS call establishment process in related technologies, such as... Figure 2 As shown, it includes:

[0154] Step 1: After completing registration in the Evolved Packet Core (EPC) or 5G Core Network (5GC), the calling terminal (UE-1) establishes a Packet Data Network (PDN) connection or a Protocol Data Unit (PDU) session. Following the establishment of the PDN connection or PDU session, the System Architecture Evolution Gateway (SAE-GW), composed of the Serving Gateway and the Packet Data Network Gateway, or the Session Management Function (SMF), sends the address of the Proxy Call Session Control Function (P-CSCF / Session Border Controller) to the calling terminal (UE-1).

[0155] Step 2: The calling terminal (UE-1) sends a registration request to the IMS core network and interacts with the IMS core network to complete the registration and authentication.

[0156] Step 3: After successfully registering with the IMS network, the calling terminal (UE-1) sends an initial call invitation request to the P-CSCF / SBC.

[0157] Step 4: After receiving the Invite request, the P-CSCF / SBC returns a 100 response to suppress retransmission. Based on the SDP offer information in the request, it sends an AAR to the Policy and Charging Rules Function (PCRF) or the Policy Control Function (PCF) to make an initial resource request.

[0158] Step 5: The P-CSCF / SBC sends the call request to the Serving-CSCF (S-CSCF) based on the path obtained during registration. The S-CSCF triggers the call to the voice application server (AS) to complete the calling service processing. The voice AS then sends the call to the called terminal (UE-2) through the call session control function (CSCF) to complete the called call connection.

[0159] Step 6: After receiving the 183 response returned by the called party, the P-CSCF / SBC sends an AAR to modify resources based on the SDP answer information in the response.

[0160] Step 7: After the calling terminal (UE-1) rings, the called terminal (UE-2) answers and establishes a call.

[0161] Step 8: After establishing a call, the user can send a session Re-invite request to keep the call on hold, and then send an Invite request to establish a multi-party call. Alternatively, the user can accept calls from other users, triggering the call waiting service.

[0162] Step 9: The user sends a BYE message to end the established call.

[0163] Table 1 shows the timers, durations, and meanings of the Session Initiation Protocol (SIP) used in IMS calls. The IMS network system follows the existing IMS SIP standard definition.

[0164] Table 1

[0165]

[0166]

[0167] In related technologies, establishing an IMS call by directly connecting a terminal to a GEO satellite presents the following technical problems:

[0168] First, the low call connection rate negatively impacts user experience.

[0169] The existing solution does not take into account the low bandwidth rate (approximately 150 bytes / s per user) and large satellite-to-ground transmission latency (>500ms) of high-orbit satellite access. Currently, the normal initial call (invite) message is about 1500 bytes, and the sending time (about 10s) far exceeds the duration of the T1 timer (0.5s), resulting in multiple retransmissions. When a PRACK / ACK is returned after receiving a 183 / 200 response, it is necessary to wait for the retransmission message to be sent before sending it, which causes the timer to time out, resulting in call release, and consequently, low user connection rate and poor service experience.

[0170] Second, the large number of retransmitted messages leads to a waste of network resources.

[0171] The existing solution does not take into account the low bandwidth rate and large satellite-to-ground transmission delay of high-orbit satellite access, which will result in multiple retransmissions and generate a large number of retransmission messages, thus consuming a large amount of limited satellite network resources.

[0172] Third, it led to the failure of some business operations.

[0173] Terminals such as mobile phones use Internet of Things-NonTerrestrial Networks (IoT-NTN) protocols to access base stations via high-orbit satellites. This only supports two bearers. Existing solutions cannot accurately detect high-orbit satellite access methods, resulting in users having already occupied both signaling and media bearers after establishing a call. When waiting to connect to a new call, the bearer establishment fails, thus multi-party calling services cannot be provided.

[0174] Based on this, this application proposes an optimization scheme for IMS calls under UE direct connection to GEO satellite access. This scheme can improve the IMS communication service experience and reduce the waste of network resources by optimizing the coordination between the network and the terminal in IMS calls, based on the terminal's IP multimedia subsystem communication capability information and GEO satellite access information.

[0175] This application adds the acquisition of terminal capability information and high-orbit satellite access information, and simplifies message adaptation, timer adjustment, and service control, possessing the following technical advantages:

[0176] First, it improves the user experience. For high-orbit satellite access, it reduces communication latency by simplifying messages, adjusting timers, and simplifying message adaptation in the process. This ensures that the communication latency does not exceed the timer's set duration, thus avoiding the problem of timer timeout and call release due to large communication latency. This improves the call establishment success rate and enhances the granularity of Quality of Service (QoS) control, thereby improving the user experience.

[0177] Secondly, it avoids wasting network resources. By adjusting timers for high-orbit satellite access, a large number of retransmitted messages and responses are reduced, as well as the sending of a large number of non-session messages, thus avoiding the waste of limited network bandwidth resources.

[0178] Third, it reduces service failures. The network informs the terminal of its access capabilities and works with the terminal to reduce service failures such as call hold, third-party, multi-party, and unreachable forwarding.

[0179] In other words, it can combine terminal capability information and / or actual access information of high-orbit satellites to achieve IMS call optimization, thereby reducing the low call connection rate, network resource waste and service failure caused by the low bandwidth and high latency of high-orbit satellites, and thus improving the user's communication service experience.

[0180] See Figure 3 , Figure 3 This is a schematic diagram of the network architecture based on the Packet Evolution core network in an embodiment of this application, as shown below. Figure 3As shown, it includes: UE, GEO satellite, gateway station, radio network, EPC network, and IMS network; wherein, the radio network includes base stations; the EPC network includes a Mobility Management Entity (MME), a Home Subscriber Server (HSS), a System Architecture Evolution Gateway (SAE GW) consisting of a Serving Gateway and a Packet Data Network Gateway, and a PCRF; the IMS network includes a Voice Application Server (AS), a Query CSCF or Serving CSCF (I / S-CSCF), and a P-CSCF / SBC.

[0181] See Figure 4 , Figure 4 This is a schematic diagram of the network architecture based on the 5G core network in an embodiment of this application, as shown below. Figure 4 As shown, it includes: UE, GEO satellite, gateway station, radio network, 5GC network, and IMS network; wherein, the radio network includes base stations; the 5GC network includes Access and Mobility Management Function (AMF), Unified Data Management (UDM), PCRF, SMF, and User Plane Function (UPF); the IMS network includes Voice AS, I / S-CSCF, and P-CSCF / SBC.

[0182] It should be noted that, in response to the increased awareness of satellite access, the core network performs corresponding processing when it detects high-orbit satellite access. This includes acquiring high-orbit satellite access information, informing the UE whether it has the IMS communication capability to support high-orbit satellites based on access awareness registration, and performing message adaptation and conversion of MO and / or MT procedures based on access awareness, service management, simplifying messages, and adjusting timer management and processing, etc.

[0183] See Figure 5 , Figure 5 This is a schematic diagram illustrating the implementation flow of the information transmission method according to an embodiment of this application, applied to a terminal. The method includes step 501:

[0184] Step 501: Send information about the terminal's IP multimedia subsystem communication capability supporting high-orbit satellites to the first core network element.

[0185] It is understood that the terminal supports IP multimedia subsystem communication capabilities for high-orbit satellites, or it can be described as the terminal supporting voice communication capabilities for high-orbit satellites.

[0186] It is understandable that the first core network element can refer to the P-CSCF / SBC in the IMS network.

[0187] In practical applications, the terminal will report the IMS communication capability information of the high-orbit satellite to the first core network element. This is to avoid problems such as low connection rate, poor service experience, and waste of network resources when the terminal directly connects to the high-orbit satellite to access the ground network to provide IMS calls. The reason for the low connection rate, poor service experience, and waste of network resources is that the communication delay during the establishment of the IMS call is large, which causes the timer to time out and ultimately results in call release.

[0188] In this application, the terminal reports the IMS communication capability information of supporting high-orbit satellites to the first core network element. The first core network element can send the simplified requirements of SIP signaling messages and the setting rules of SIP protocol timers to the terminal. Both the first core network element and the terminal simplify the SIP signaling messages used in IMS calls and adjust the duration of SIP protocol timers (timers related to calls). By optimizing the size of SIP signaling messages and adjusting the timer settings, the communication delay does not exceed the set duration of the timer, thereby avoiding the problem of call release due to timer timeout caused by large communication delay. This improves the connection success rate, user experience, and network resource utilization during the IMS call establishment process.

[0189] In some embodiments, the method further includes:

[0190] The system receives first information sent by the first core network element, wherein the first information represents the simplification requirements of SIP signaling messages and the setting rules of SIP protocol timers.

[0191] It is understood that the SIP protocol timer may refer to a call-related timer.

[0192] In some embodiments, the simplification requirements for the SIP signaling message include at least one of the following:

[0193] Simplification requirements of the SIP method;

[0194] Simplified requirements for SIP message header fields;

[0195] Simplified requirements for SIP URIs;

[0196] Simplified message body requirements;

[0197] The simplification requirements of the SIP mechanism.

[0198] In some embodiments, the simplification requirements of the SIP method include:

[0199] Retain the INVITE, ACK, BYE, CANCEL, REGISTER, PRACK, and MESSAGE methods; remove the SUBSCRIBE, NOTIFY, PUBLISH, INFO, REFER, UPDATE, and OPTIONS methods.

[0200] The simplified requirements for the SIP message header fields include:

[0201] Retain the following necessary header fields: from, to, via, Call-ID, Max-Forwards, CONTACT, Content-Type, Content-Length; simplify header fields to use 1 or 2 letters for replacement.

[0202] The simplified requirements for the SIP URI include:

[0203] Retain the variable portion of the domain name part of the SIP URI and remove the fixed portion of the domain name part of the SIP URI;

[0204] The simplified requirements for the message body include:

[0205] Multiple message bodies are not supported. The message body type for SIP voice messages is application or sdp, and the message body type for SIP short messages is application or vnd.3gpp.sms. The SDP in the message body of SIP voice messages retains v, o, s, c and m, and the IMS protocol is required. The necessary a line describing low bitrate encoding and decoding is also retained.

[0206] The simplification requirements of the SIP mechanism include:

[0207] Support for the following mechanisms is not required: reliable transport of temporary responses, resource reservation, and SIP protocol encrypted with TLS.

[0208] In some embodiments, sending information about the terminal's IP multimedia subsystem communication capabilities supporting high-orbit satellites to the first core network element includes:

[0209] Information about the terminal's IP multimedia subsystem communication capabilities supporting high-orbit satellites is sent to the first core network element through the access network element and the second core network element.

[0210] In some embodiments, the second core network element includes a mobility management network element, a core network data network element, and a call session control function.

[0211] It is understood that the access network element may refer to a base station.

[0212] It is understood that the mobility management network element can refer to MME or AMF.

[0213] It is understood that the core network data element may refer to HSS or UDM.

[0214] It is understood that the call session control function may refer to I / S-CSCF.

[0215] It is understandable that the first core network element may refer to the SBC / P-CSCF.

[0216] As one implementation method, under the EPC architecture, the terminal can send information about its IP multimedia subsystem communication capability for high-orbit satellites to the HSS via the base station and MME. The HSS can then send this information to the SBC / P-CSCF via the I / S-CSCF.

[0217] As another implementation, under the 5GC architecture, the terminal can send information about its IP multimedia subsystem communication capabilities for high-orbit satellites to the UDM via the base station and AMF. The UDM can then send this information to the SBC / P-CSCF via the I / S-CSCF.

[0218] See Figure 6 , Figure 6 This is a schematic diagram illustrating the implementation process of a terminal sending capability information to a core network data element according to an embodiment of this application. It is applied to an EPC architecture, where the terminal is a UE and the core network data element is an HSS. Figure 6 As shown, steps 601 to 605 are included:

[0219] Step 601: The UE directly connects to the high-orbit satellite and sends an access (attach) request to the base station through the gateway station. The request carries information such as the UE's support for IMS communication with high-orbit satellites (GEO satellites).

[0220] Step 602: The base station supports high-orbit satellite access and forwards the attach request to the MME network element. The request carries information such as the UE's support for GEO satellite IMS communication, satellite access type, satellite identifier, and satellite ephemeris.

[0221] Here, the satellite access type mentioned can refer to high-orbit satellite access.

[0222] Here, the satellite identifier may refer to the identifier of a high-orbit satellite.

[0223] Step 603: After receiving the information, the MME interacts with the UE to complete the identity acquisition and authentication, and then sends an update location request to the HSS. This request carries information such as the UE's support for GEO satellite IMS communication, satellite access type, satellite identifier, and satellite ephemeris.

[0224] Step 604: After receiving the information, the HSS saves the UE's IMS communication indication for GEO satellites, satellite access type, satellite identifier, and satellite ephemeris information, and returns an update location response to the MME.

[0225] Step 605: After the MME successfully creates the default bearer, it sends an access acceptance (attach accept) instruction to the UE and interacts with the UE to complete the access (attach) process.

[0226] In this example, within the EPC architecture, the UE can support the acquisition of IMS communication instructions for GEO satellites and access information for high-orbit satellites.

[0227] See Figure 7 , Figure 7 This is a schematic diagram illustrating the implementation process of a terminal sending capability information to a core network data element according to an embodiment of this application. It is applied to a 5GC architecture, where the terminal is a UE and the core network data element is a UDM. Figure 7 As shown, steps 701 to 705 are included:

[0228] Step 701: The UE directly connects to the GEO satellite and sends a registration request to the base station through the gateway station. The request carries information such as the UE's support for GEO satellite IMS communication.

[0229] Step 702: The base station forwards the registration request to the AMF network element. The registration request carries information such as the UE's support for GEO satellite IMS communication indication, satellite access type, satellite identifier, and satellite ephemeris.

[0230] Step 703: After receiving the request, the AMF interacts with the UE to complete the identity acquisition and authentication, and then sends a Nudm_ECM_Registration request to the UDM. This request carries information such as the UE's support for GEO satellite IMS communication indication, satellite access type, satellite identifier, and satellite ephemeris.

[0231] Step 704: After receiving the data, the UDM saves the IMS communication indication, satellite access type, satellite identifier, and satellite ephemeris of the UE supporting GEO satellites, and returns the Nudm_ECM_Registration response to the AMF.

[0232] Step 705: The AMF sends a Register accept instruction to the UE and interacts with the UE to complete the registration process.

[0233] In this example, within the 5GC architecture, the UE can support IMS communication capability indication for GEO satellites and obtain high-orbit satellite access information.

[0234] In some embodiments, the method further includes:

[0235] The duration of the SIP protocol timer is adjusted according to the setting rules.

[0236] It is understood that the SIP protocol timers may include timers T1, T2, T4, Timer A, Timer B, Timer D, Timer E, Timer F, Timer G, Timer H, Timer I, Timer J, and Timer K.

[0237] Table 2 illustrates the rules for setting SIP protocol timers. As shown in Table 2, the rules for setting SIP protocol timers can include:

[0238] Timer T1: The value of T1 is equal to the delay of the entire SIP signaling process for establishing a call in the scenario where the terminal directly connects to the high-orbit satellite to access the terrestrial network to provide IMS calling (i.e., the round-trip time from sending a request to receiving a response from the other end, which is the time from dialing to the ringing of the called party). In actual applications, it can be adjusted according to the SIP message sending duration and transmission delay under high-orbit satellite.

[0239] Timer T2: The value of T2 is equal to the maximum retransmission interval of non-INVITE request messages and INVITE response messages in the scenario where the terminal directly connects to the high-orbit satellite to access the terrestrial network to provide IMS calls. In actual applications, it can be adjusted according to the SIP message sending duration and transmission delay under the high-orbit satellite.

[0240] Timer T4: The value of T4 is equal to the maximum time that a SIP message can exist in the network when the terminal is directly connected to a high-orbit satellite to access the terrestrial network for IMS calling. In actual applications, it can be adjusted according to the transmission delay and other factors such as the duration of SIP message transmission under high-orbit satellite.

[0241] Timer A: The value of this timer is equal to the retransmission interval of the INVITE message when using UDP transmission in the scenario where the terminal directly connects to the high-orbit satellite to access the ground network to provide IMS calls. In actual applications, it can be adjusted according to the sending duration and transmission delay of SIP messages under the high-orbit satellite.

[0242] Timer B: The value of this timer is equal to the INVITE transaction timeout duration in the scenario where the terminal directly connects to the high-orbit satellite to access the terrestrial network for IMS calling. In actual applications, it can be adjusted according to the SIP message sending duration, interaction process, and transmission latency under the high-orbit satellite.

[0243] Timer D: The value of this timer is equal to the duration of waiting for the response message to be retransmitted after receiving the response message in the scenario where the terminal directly connects to the high-orbit satellite to access the terrestrial network to provide IMS calls. In actual applications, it can be adjusted according to the SIP message sending duration, interaction process and transmission delay under high-orbit satellite.

[0244] Timer E: The value of this timer is equal to the retransmission interval of non-INVITE request messages when using UDP transmission in the scenario where the terminal directly connects to the high-orbit satellite to access the ground network to provide IMS calls. In actual applications, it can be adjusted according to the sending duration and transmission delay of SIP messages under the high-orbit satellite.

[0245] Timer F: The value of this timer is equal to the timeout duration of non-INVITE transactions in the scenario where the terminal directly connects to the high-orbit satellite to access the terrestrial network to provide IMS calls. In actual applications, it can be adjusted according to the SIP message sending duration, interaction process and transmission delay under the high-orbit satellite.

[0246] Timer G: The value of this timer is equal to the retransmission interval of the INVITE response message in the scenario where the terminal directly connects to the high-orbit satellite to access the terrestrial network to provide IMS calls. In actual applications, it can be adjusted according to the SIP message sending duration and transmission delay under the high-orbit satellite.

[0247] Timer H: The value of this timer is equal to the time it takes to wait for the ACK after sending the final response in the scenario where the terminal directly connects to the high-orbit satellite to access the terrestrial network to provide IMS calls. In actual applications, it can be adjusted according to the SIP message sending time, interaction process and transmission delay under high-orbit satellite.

[0248] Timer I: The value of this timer is equal to the duration of waiting for the ACK to be retransmitted after receiving the ACK in the scenario where the terminal is directly connected to the high-orbit satellite to access the ground network to provide IMS calls. In actual applications, it can be adjusted according to the SIP message sending duration and transmission delay under the high-orbit satellite.

[0249] Timer J: The value of this timer is equal to the duration for which the terminal continues to wait for the retransmission of a non-INVITE request after returning the final response to the non-INVITE request in the scenario of the terminal directly connecting to the high-orbit satellite to access the ground network to provide IMS calls. In actual applications, it can be adjusted according to the SIP message sending duration, interaction process and transmission delay under the high-orbit satellite.

[0250] Timer K: The value of this timer is equal to the duration for which the terminal continues to wait for the retransmission of the response message after receiving the response message in the scenario of the terminal directly connecting to the high-orbit satellite to access the terrestrial network to provide IMS calls. In actual applications, it can be adjusted according to the SIP message sending duration and transmission delay under the high-orbit satellite.

[0251] In this application, both the first core network element and the terminal reset the call-related timers in the scenario of the terminal directly connecting to the high-orbit satellite to access the terrestrial network to provide IMS calls, according to the setting rules. By setting appropriate timer values ​​and optimizing the size of SIP signaling messages, the communication delay does not exceed the set duration of the timers, which can avoid retransmission and ultimately lead to call release problems, thereby improving the connection success rate, user experience, and network resource utilization during the IMS call establishment process.

[0252] Table 2

[0253]

[0254]

[0255] In some embodiments, the method further includes:

[0256] Obtain the address of the first core network element and the duration of the registration timer sent by the third core network element.

[0257] It is understood that the third core network element may specifically refer to SMF / SAE-GW.

[0258] In some embodiments, the method further includes:

[0259] The registration timer of the terminal is adjusted according to the duration of the registration timer.

[0260] It is understandable that the duration of the registration timer can be set according to the actual situation. By setting an appropriate duration value, it can be ensured that the frequency of terminal registration is not too frequent.

[0261] See Figure 8 , Figure 8 This is a schematic diagram illustrating the implementation process of the first core network element obtaining terminal capability information in an embodiment of this application. The terminal is a UE, the first core network element is an SBC / P-CSCF, and the second core network element is an SMF / SAE-GW. Figure 8 As shown, steps 801 to 809 are included:

[0262] Step 801: The UE directly connects to the high-orbit satellite, completes registration through the EPC / 5GC network, establishes a Packet Data Network (PDN) connection or Protocol Data Unit (PDU) session, and obtains the address of the SBC / P-CSCF and the duration of the registration timer (Timer F) returned by the SMF / SAE-GW.

[0263] Here, the duration of the registration timer can be set according to the actual situation. By setting an appropriate duration value, it can be ensured that the frequency of terminal registration is not too frequent.

[0264] Step 802: After receiving the request, the UE sets the duration of the corresponding UE registration timer. The UE directly connects to the high-orbit satellite and sends the initial IMS registration request to the SBC / P-CSCF. After receiving the request, the SBC / P-CSCF forwards it to the I / S-CSCF.

[0265] Step 803: After receiving the data, the I / S-CSCF interacts with the UE to complete the authentication process and then sends a SAR message to the HSS / UDM to obtain the user's access satellite data.

[0266] Step 804: The HSS / UDM returns the SAA to the I / S-CSCF, carrying user satellite access data in the response. This user satellite access data includes information such as the UE's support for GEO satellites' IMS communication indication, satellite access type, satellite identifier, and satellite ephemeris.

[0267] Step 805: After receiving the SAA, the I / S-CSCF saves the user's satellite access data and sends a 200 response to the SBC / P-CSCF. The 200 response carries information such as the UE's support for GEO satellites' IMS communication indication, satellite access type, satellite identifier, and satellite ephemeris.

[0268] Step 806: After receiving the SBC / P-CSCF, use the satellite identifier to query the satellite data module for satellite communication-related data.

[0269] Here, the satellite communication-related data may include single-user uplink (UL) or downlink (DL) rates, transmission delay, etc. The transmission delay can be used to adjust the value of the SIP protocol timer.

[0270] Step 807: The SBC / P-CSCF sends a 200 response to the UE based on the UE's IMS communication indication that it supports GEO satellites and the acquired satellite communication-related data. The 200 response carries first information, which represents the simplification requirements of SIP signaling messages and the setting rules of SIP protocol timers.

[0271] Here, the first information can also be described as notification of simplified SIP protocol capability schemes / modes.

[0272] Here, the simplification requirements for the SIP signaling message include at least one of the following:

[0273] Simplification requirements of the SIP method;

[0274] Simplified requirements for SIP message header fields;

[0275] Simplified requirements for SIP URIs;

[0276] Simplified message body requirements;

[0277] The simplification requirements of the SIP mechanism.

[0278] Here, the simplification requirements of the SIP method include:

[0279] Retain the INVITE, ACK, BYE, CANCEL, REGISTER, PRACK, and MESSAGE methods; remove the SUBSCRIBE, NOTIFY, PUBLISH, INFO, REFER, UPDATE, and OPTIONS methods.

[0280] The simplified requirements for the SIP message header fields include:

[0281] Retain the following necessary header fields: from, to, via, Call-ID, Max-Forwards, CONTACT, Content-Type, Content-Length; simplify header fields to use 1 or 2 letters for replacement.

[0282] The simplified requirements for the SIP URI include:

[0283] Retain the variable portion of the domain name part of the SIP URI and remove the fixed portion of the domain name part of the SIP URI;

[0284] The simplified requirements for the message body include:

[0285] Multiple message bodies are not supported. The message body type for SIP voice messages is application or sdp, and the message body type for SIP short messages is application or vnd.3gpp.sms. The SDP in the message body of SIP voice messages retains v, o, s, c and m, and the IMS protocol is required. The necessary a line describing low bitrate encoding and decoding is also retained.

[0286] The simplification requirements of the SIP mechanism include:

[0287] Support for the following mechanisms is not required: reliable transport of temporary responses, resource reservation, and SIP protocol encrypted with Transport Layer Security (TLS).

[0288] That is, the first information may include the required simplified SIP method, the required simplified SIP message header field, the required simplified SIP URI and the required simplified message body, the required simplified SIP mechanism, and the required adjusted SIP protocol timer, etc.

[0289] Step 808: The SBC / P-CSCF adjusts the SIP protocol timer of the SBC / P-CSCF for the UE.

[0290] Here, the rules for setting the SIP protocol timer of the SBC / P-CSCF are the same as those for setting the SIP protocol timer of the instruction terminal.

[0291] Step 809: After receiving the response, the UE saves the first information carried in the 200 response and adjusts the duration of the SIP protocol timer according to the setting rules in the first information.

[0292] Here, the UE can set the duration of SIP protocol timers other than Timer C.

[0293] The embodiments of this application have the following technical advantages:

[0294] (1) The terminal reports the IMS communication capability information of supporting high-orbit satellites to the first core network element. In this way, the first core network element can send the simplified SIP signaling and the SIP protocol timer setting rules to the terminal. Both the first core network element and the terminal simplify the SIP signaling used in the IMS call and adjust the duration of the call-related timer in the SIP protocol according to the requirements of the first core network element. By optimizing the size of the SIP signaling message and adjusting the timer settings, the communication delay does not exceed the set duration of the timer, so as to avoid the problem of call release due to timer timeout caused by large communication delay. This improves the connection success rate, user experience and network resource utilization during the IMS call establishment process.

[0295] See Figure 9 , Figure 9 This is a schematic diagram illustrating the implementation flow of the information transmission method according to an embodiment of this application, applied to a first core network element. The method includes step 901:

[0296] Step 901: Obtain the terminal's IP Multimedia Subsystem communication capability information for high-orbit satellites sent by the terminal.

[0297] In some embodiments, the method further includes:

[0298] Obtain high-orbit satellite access information sent by the access network element, wherein the high-orbit satellite access information includes satellite access type, satellite identifier, and satellite ephemeris.

[0299] Here, the satellite access type mentioned can refer to high-orbit satellite access.

[0300] Here, the satellite identifier may refer to the identifier of a high-orbit satellite.

[0301] Here, the satellite ephemeris can refer to the ephemeris information of high-orbit satellites.

[0302] In some embodiments, obtaining the terminal's IP Multimedia Subsystem communication capability information for high-orbit satellites, sent by the terminal, includes:

[0303] The terminal obtains information on its IP multimedia subsystem communication capabilities with high-orbit satellites, sent from the access network element and the second core network element to the first core network element.

[0304] The second core network element includes a mobility management network element, a core network data network element, and a call session control function.

[0305] It is understood that the access network element may refer to a base station.

[0306] It is understood that the mobility management network element can refer to MME or AMF.

[0307] It is understood that the core network data element may refer to HSS or UDM.

[0308] It is understood that the call session control function may refer to I / S-CSCF.

[0309] It is understandable that the first core network element may refer to the SBC / P-CSCF.

[0310] As one implementation method, under the EPC architecture, the terminal can send information about its IP multimedia subsystem communication capability for high-orbit satellites to the HSS via the base station and MME. The HSS can then send this information to the SBC / P-CSCF via the I / S-CSCF.

[0311] As another implementation, under the 5GC architecture, the terminal can send information about its IP multimedia subsystem communication capabilities for high-orbit satellites to the UDM via the base station and AMF. The UDM can then send this information to the SBC / P-CSCF via the I / S-CSCF.

[0312] In some embodiments, obtaining the high-orbit satellite access information sent by the access network element includes:

[0313] Obtain high-orbit satellite access information sent by the access network element to the first core network element through the second core network element.

[0314] The second core network element includes a mobility management network element, a core network data network element, and a call session control function.

[0315] It is understood that the access network element may refer to a base station.

[0316] It is understood that the mobility management network element can refer to MME or AMF.

[0317] It is understood that the core network data element may refer to HSS or UDM.

[0318] It is understood that the call session control function may refer to I / S-CSCF.

[0319] It is understandable that the first core network element may refer to the SBC / P-CSCF.

[0320] As one implementation method, under the EPC architecture, the base station sends high-orbit satellite access information to the HSS through the MME, and the HSS sends high-orbit satellite access information to the SBC / P-CSCF through the I / S-CSCF.

[0321] As another implementation method, under the 5GC architecture, the base station sends high-orbit satellite access information to the UDM through the AMF, and the UDM sends high-orbit satellite access information to the SBC / P-CSCF through the I / S-CSCF.

[0322] It is understandable that after the first core network element receives the high-orbit satellite access information, it can query the satellite data module based on the satellite identifier in the access information to obtain satellite communication related data. This data may include single-user uplink or downlink rates, transmission delay, etc., wherein the transmission delay can be used to adjust the duration value of the SIP protocol timer.

[0323] In some embodiments, the method further includes:

[0324] Send first information to the terminal, wherein the first information represents the simplification requirements of SIP signaling messages and the setting rules of SIP protocol timers.

[0325] It is understandable that both the first core network element and the terminal simplify the SIP signaling messages used in IMS calls and adjust the duration of the SIP protocol timer (the timer related to the call). By optimizing the size of the SIP signaling messages and adjusting the timer settings, the communication delay does not exceed the set duration of the timer, thereby avoiding the problem of call release due to timer timeout caused by large communication delay. This improves the connection success rate, user experience, and network resource utilization during the IMS call establishment process.

[0326] It is understood that the SIP protocol timers may include timers T1, T2, T4, Timer A, Timer B, Timer D, Timer E, Timer F, Timer G, Timer H, Timer I, Timer J, and Timer K.

[0327] In this application, both the first core network element and the terminal reset the call-related timers in the scenario of the terminal directly connecting to the high-orbit satellite to access the terrestrial network to provide IMS calls, according to the setting rules. By setting appropriate timer values ​​and optimizing the size of SIP signaling messages, the communication delay does not exceed the set duration of the timers, which can avoid retransmission and ultimately lead to call release problems, thereby improving the connection success rate, user experience, and network resource utilization during the IMS call establishment process.

[0328] In some embodiments, the simplification requirements for the SIP signaling message include at least one of the following:

[0329] Simplification requirements of the SIP method;

[0330] Simplified requirements for SIP message header fields;

[0331] Simplified requirements for SIP URIs;

[0332] Simplified message body requirements;

[0333] The simplification requirements of the SIP mechanism.

[0334] In some embodiments, the simplification requirements of the SIP method include:

[0335] Retain the INVITE, ACK, BYE, CANCEL, REGISTER, PRACK, and MESSAGE methods; remove the SUBSCRIBE, NOTIFY, PUBLISH, INFO, REFER, UPDATE, and OPTIONS methods.

[0336] The simplified requirements for the SIP message header fields include:

[0337] Retain the following necessary header fields: from, to, via, Call-ID, Max-Forwards, CONTACT, Content-Type, Content-Length; simplify header fields to use 1 or 2 letters for replacement.

[0338] The simplified requirements for the SIP URI include:

[0339] Retain the variable portion of the domain name part of the SIP URI and remove the fixed portion of the domain name part of the SIP URI;

[0340] The simplified requirements for the message body include:

[0341] Multiple message bodies are not supported. The message body type for SIP voice messages is application or sdp, and the message body type for SIP short messages is application or vnd.3gpp.sms. The SDP in the message body of SIP voice messages retains v, o, s, c and m, and the IMS protocol is required. The necessary a line describing low bitrate encoding and decoding is also retained.

[0342] The simplification requirements of the SIP mechanism include:

[0343] Support for the following mechanisms is not required: reliable transport of temporary responses, resource reservation, and SIP protocol encrypted with TLS.

[0344] In some embodiments, the first core network element is the calling core network element, and the method further includes:

[0345] Execute the MO process, and / or execute the MT process.

[0346] In some embodiments, the execution of the MO process includes:

[0347] Obtain a simplified initial call request sent by the calling terminal;

[0348] Send a simplified call intermediate response to the calling terminal;

[0349] The duration of the SIP protocol timer is adjusted to convert the simplified initial call request into a complete call request, and the complete call request is sent to the called terminal; wherein the complete call request carries an indication that resource reservation is not supported;

[0350] Obtain the call intermediate response carrying SDP ANSWER sent by the called terminal;

[0351] Return a PRACK message to the called terminal;

[0352] Obtain the call intermediate response sent by the called terminal in response to the PRACK message;

[0353] Return a PRACK message to the called terminal and send a simplified call intermediate response to the calling terminal that does not require reliable transmission of the interim response;

[0354] Receive the call intermediate response returned by the called terminal;

[0355] Send a simplified call intermediate response carrying an SDP ANSWER to the calling terminal;

[0356] Receive a simplified ACK message sent by the calling terminal;

[0357] The simplified ACK message is converted into a complete ACK message, and the complete ACK message is sent to the called terminal to complete the call establishment;

[0358] Obtain the simplified BYE request sent by the calling terminal;

[0359] Return a call response to the calling terminal, convert the simplified BYE request into a complete BYE request, and send the complete BYE request to the called terminal;

[0360] Obtain the call response sent by the called terminal to end the call.

[0361] It is understood that the intermediate call response may include a 100 response, a 180 response, etc.

[0362] It is understood that the call response may include a 200 response, etc.

[0363] Understandably, in the MO process, the initial call request can follow the following simplified requirements:

[0364] Simplification requirements for SIP methods, SIP URIs, SIP message header fields, message bodies, and SIP mechanisms.

[0365] Understandably, in the MO process, the call intermediate response can follow the following simplification requirements: simplification of SIP URI, simplification of SIP message header fields, simplification of message body, etc.

[0366] See Figure 10 , Figure 10 This is a schematic diagram of the MO process in an embodiment of this application, as shown below. Figure 10 As shown, the method includes steps 1001 to 1017:

[0367] Step 1001: The calling terminal (UE-1) initiates an Invite request through a direct connection to a high-orbit satellite based on the first information obtained during previous registration. The first information represents the simplification requirements of the SIP signaling message and the setting rules of the SIP protocol timer. The Invite request is sent to the SBC / P-CSCF through network elements such as satellite, gateway station, base station, SAE-GW-U / UPF, etc. The Invite request is a simplified message.

[0368] Here, the simplified request followed by the initial call request is as follows:

[0369] SIP method simplification: Among the methods allowed in Allow, retain INVITE, ACK, BYE, CANCEL, REGISTER, PRACK, MESSAGE, etc.; remove SUBSCRIBE, NOTIFY, PUBLISH, INFO, REFER, UPDATE, OPTIONS, etc.

[0370] SIP URI simplification: The variable part of the URI domain name is retained, while the fixed part is removed.

[0371] SIP message header field simplification: Retain necessary header fields such as from, to, via, Call-ID, Max-Forwards, CONTACT, Content-Type, and Content-Length, and simplify the header fields to 1-2 letter replacements, such as from can be simplified to f, and Call-ID can be simplified to CI, etc.

[0372] Simplified message body: Multiple message bodies are not supported. The SIP voice message body type is application / sdp, and the short message fixed type is application / vnd.3gpp.sms. The voice message body SDP retains the SDPs v, o, s, c, and m, as well as the required IMS protocol, and retains the necessary 'a' line describing low bitrate encoding and decoding.

[0373] Simplified SIP mechanism: Supported does not require support for reliable transmission of ad hoc responses, resource reservation (precondition), and SIP over TLS encryption.

[0374] Step 1002: After receiving the simplified invite request, the SBC / P-CSCF returns a simplified 100 response. The simplified request follows as follows:

[0375] SIP URI simplification: The variable part of the URI domain name is retained, while the fixed part is removed.

[0376] SIP message header field simplification: Retain necessary header fields such as from, to, via, Call-ID, Max-Forwards, Contact, and Content-Length, and simplify the header fields to 1-2 letter replacements, such as from can be simplified to f, and Call-ID can be simplified to CI, etc.

[0377] Step 1003: Based on the information obtained from the user's previous registration, such as the indication that the UE supports IMS communication with GEO satellites and the satellite communication-related data, the SBC / P-CSCF sets the duration of the SIP protocol timer, converts the invite request into a complete invite request, and sends it to the S-CSCF, carrying an indication that the reserved resources (precondition) are not supported.

[0378] Step 1004: After receiving the request, the S-CSCF sends an invite request to the application server (AS) to process the calling voice service. After the AS completes the calling voice service processing, it sends an invite request to the S-CSCF.

[0379] Step 1005: The S-CSCF forwards the invite request to the peer CSCF, and the peer CSCF sends the invite request to the called terminal (UE-2).

[0380] Step 1006: The called terminal (UE-2) returns a 183 response, which carries an SDP ANSWER and is sent to the calling CSCF and SBC / P-CSCF via the called SBC and CSCF.

[0381] Step 1007: After receiving the message, the calling SBC / P-CSCF saves the SDP negotiation result information locally based on the user satellite access data stored locally, returns a PRACK message to the called terminal (UE-2), and sends it to UE-2 through the calling CSCF, the peer CSCF and SBC.

[0382] Step 1008: After receiving the response, the called terminal (UE-2) sends a PRACK 200 response to the calling SBC / P-CSCF.

[0383] Step 1009: The called terminal (UE-2) returns a 180 response to the calling SBC / P-CSCF.

[0384] Step 1010: After receiving the 180 response, the calling SBC / P-CSCF returns a PRACK to the called terminal (UE-2) based on the locally stored user satellite access data. The called terminal (UE-2) then sends a simplified 180 response to the calling terminal (UE-1) that does not require reliable transmission of the provisional response, following the simplified request as follows:

[0385] SIP URI simplification: The variable part of the URI domain name is retained, while the fixed part is removed.

[0386] SIP message header field simplification: Retain necessary header fields such as from, to, via, Call-ID, Max-Forwards, CONTACT, Content-Type, and Content-Length, and simplify the header fields to 1-2 letter replacements, such as from can be simplified to f, and Call-ID can be simplified to CI, etc.

[0387] Step 1011: The called terminal (UE-2) returns a 200 response to the calling SBC / P-CSCF.

[0388] Step 1012: After receiving the 200 response, the calling SBC / P-CSCF sends a simplified 200 response carrying the SDP ANSWER to the calling terminal (UE-1) based on the locally stored user satellite access data. The simplified request follows as follows:

[0389] SIP URI simplification: The variable part of the URI domain name is retained, while the fixed part is removed.

[0390] SIP message header field simplification: Retain necessary header fields such as from, to, via, Call-ID, Max-Forwards, CONTACT, Content-Type, and Content-Length, and simplify the header fields to 1-2 letter replacements, such as from can be simplified to f, and Call-ID can be simplified to CI, etc.

[0391] Simplified message body: Multiple message bodies are not supported. The voice message body type is application / sdp, and the short message body type is application / vnd.3gpp.sms. The voice message body SDP retains the required SDP and IMS protocols such as v, o, s, c, and m, and retains the necessary 'a' line describing low bitrate encoding and decoding.

[0392] Step 1013: After receiving the simplified 200 response, the calling terminal (UE-1) saves the SDP negotiation result and sends an ACK message to the SBC / P-CSCF, where the ACK is a simplified message that follows the following simplified request:

[0393] SIP URI simplification: The variable part of the URI domain name is retained, while the fixed part is removed.

[0394] SIP message header field simplification: Retain necessary header fields such as from, to, via, Call-ID, Max-Forwards, CONTACT, Content-Type, and Content-Length, and simplify the header fields to 1-2 letter replacements, such as from can be simplified to f, and Call-ID can be simplified to CI, etc.

[0395] Step 1014: The SBC / P-CSCF converts the simplified ACK into a complete ACK based on the user satellite access data and other information stored locally, and sends it to the S-CSCF. The S-CSCF then forwards the ACK to the called terminal (UE-2) through the network to complete the call establishment.

[0396] Step 1015: The calling terminal (UE-1) sends a simplified BYE request to the SBC / P-CSCF.

[0397] Step 1016: After receiving the response, the SBC / P-CSCF returns a simplified 200 response, converts the simplified BYE into a full BYE, and sends it to the S-CSCF, which then forwards it to the called terminal (UE-2) via the network.

[0398] Step 1017: After receiving the response, the called terminal (UE-2) returns a 200 response, and the call ends.

[0399] In some embodiments, the execution of the MT process includes:

[0400] Obtain the initial call request sent by the called terminal;

[0401] The duration of the SIP protocol timer is adjusted to send a simplified initial call request to the calling terminal, wherein the SDP carried in the simplified initial call request is a low-bit-rate SDP.

[0402] Obtain the simplified call intermediate response sent by the calling terminal;

[0403] Send an intermediate call response carrying a universal codec SDP ANSWER to the called terminal;

[0404] Obtain the PRACK message sent by the called terminal, and send a call response to the PRACK message to the called terminal;

[0405] Obtain the simplified call intermediate response sent by the calling terminal;

[0406] The simplified intermediate call response is converted into a complete intermediate call response that requires reliable transmission of the interim response, and the complete intermediate call response is sent to the called terminal.

[0407] Obtain the PRACK message sent by the called terminal, and send a call response to the PRACK message to the called terminal;

[0408] Obtain the simplified call answer response carrying SDP ANSWER sent by the calling terminal;

[0409] Save the SDP ANSWER, convert the simplified call answer response into a complete call answer response, and send the complete call answer response to the called terminal; the complete call answer response does not carry SDP.

[0410] Obtain the ACK message sent by the called terminal, convert the ACK message into a simplified ACK message, and send the simplified ACK message to the calling terminal to complete the call establishment;

[0411] Obtain the BYE request sent by the called terminal;

[0412] Send a call response to the called terminal, convert the BYE request into a simplified BYE request, and send the simplified BYE request to the calling terminal;

[0413] Obtain the call response returned by the calling terminal to end the call.

[0414] It is understandable that the simplification of the initial call request and intermediate call response in the MT process is similar to that in the MO process, and will not be elaborated further here.

[0415] See Figure 11 , Figure 11 This is a schematic diagram of the MT process in an embodiment of this application, as shown below. Figure 11 As shown, the method includes steps 1101 to 1117:

[0416] Step 1101: Under terrestrial network coverage, the user, i.e. the called terminal (UE-2), initiates an initial call request to the calling terminal (UE-1). The invite request is sent to the I / S-CSCF network element where the calling terminal (UE-1) is located through the peer CSCF. The I / S-CSCF network element triggers the call to the voice application server (AS) where the user is located under satellite coverage.

[0417] Step 1102: After receiving the call request, the AS sends a request to obtain user data to the HSS / UDM where the calling terminal (UE-1) is located.

[0418] Step 1103: HSS / UDM returns a user data acquisition response to AS. The user data response carries user access satellite data such as indication that the UE supports IMS communication with GEO satellites, satellite access type, satellite identifier, and satellite ephemeris.

[0419] Here, the AS, based on the received user satellite access data, sets a corresponding unreachable forwarding timer duration for users who have subscribed to the unreachable forwarding service, taking into account the user's access satellite data. If the user is already in a call, new calls are rejected based on the accessed high-orbit satellite data.

[0420] Step 1104: AS sends an Invite request to S-CSCF, and S-CSCF forwards the call request to the calling SBC / P-CSCF.

[0421] Step 1105: After receiving the invite request, the calling SBC / P-CSCF sets the duration of the SIP protocol timer according to the locally stored user satellite access data, sends a simplified invite request to the calling terminal (UE-1), checks that the SDP in the request is an SDP carrying a general codec, modifies this SDP to a low code rate SDP codec, and follows the same simplified request as before.

[0422] Step 1106: After receiving the simplified invite request, the calling terminal (UE-1) returns a simplified 100 response to the calling SBC / P-CSCF, following the same simplified request as before.

[0423] Step 1107: The calling SBC / P-CSCF constructs and sends a non-simplified 183 response to the called terminal (UE-2), carrying a generic SDP ANSWER in the response.

[0424] Step 1108: After receiving the message, the called terminal (UE-2) sends a PRACK message to the calling SBC / P-CSCF where the calling terminal (UE-1) is located via the network. After receiving the message, the calling SBC / P-CSCF returns a 200 response with the PRACK message.

[0425] Step 1109: The calling terminal (UE-1) returns a simplified 180 response to the calling SBC / P-CSCF.

[0426] Step 1110: The calling SBC / P-CSCF converts the simplified 180 response into a complete 180 response requiring reliable transmission of the provisional response and sends it to the S-CSCF, which then forwards it over the network to the called terminal (UE-2).

[0427] Here, after the called terminal (UE-2) receives the message, it sends a PRACK to the calling SBC / P-CSCF where the calling terminal (UE-1) is located via the network. After receiving the message, the calling SBC / P-CSCF returns a PRACK 200 response.

[0428] Step 1111: The calling terminal (UE-1) returns a simplified 200 response to the calling SBC / P-CSCF, carrying an SDP ANSWER in the response.

[0429] Step 1112: After receiving the SDP ANSWER information, the calling SBC / P-CSCF saves the corresponding SDP ANSWER information, converts it into a complete 200 response and sends it to the S-CSCF. The S-CSCF then forwards the response to the called terminal (UE-2) through the network. The response does not carry SDP information.

[0430] Step 1113: After receiving the message, the called terminal (UE-2) returns an ACK message to the calling SBC / P-CSCF via the network.

[0431] Step 1114: The calling SBC / P-CSCF converts the ACK message into a simplified ACK message and sends it to the called terminal (UE-1) to complete the call establishment.

[0432] Step 1115: The called terminal (UE-2) sends a BYE request to the calling SBC / P-CSCF via the network.

[0433] Step 1116: After receiving the request, the calling SBC / P-CSCF returns a 200 response, converting the complete BYE request into a simplified BYE request and sending it to the calling terminal (UE-1).

[0434] Step 1117: Upon receiving the message, the calling terminal (UE-1) returns a simplified 200 response, thus ending the call.

[0435] The embodiments of this application have the following technical advantages:

[0436] (1) The terminal reports the IMS communication capability information of supporting high-orbit satellites to the first core network element. In this way, the first core network element can send the simplified SIP signaling and the SIP protocol timer setting rules to the terminal. Both the first core network element and the terminal simplify the SIP signaling used in the IMS call and adjust the duration of the call-related timer in the SIP protocol according to the requirements of the first core network element. By optimizing the size of the SIP signaling message and adjusting the timer settings, the communication delay does not exceed the set duration of the timer, so as to avoid the problem of call release due to timer timeout caused by large communication delay. This improves the connection success rate, user experience and network resource utilization during the IMS call establishment process.

[0437] (2) In the MO and MT processes, SIP signaling messages such as initial call request and call intermediate response can be simplified to simplify the process, which means simplifying message adaptation and ensuring that the communication delay does not exceed the timer's set duration. This avoids the problem of call release caused by timer timeout due to large communication delay, thereby improving the connection success rate, user experience and network resource utilization during the IMS call establishment process.

[0438] See Figure 12 , Figure 12 This is a schematic diagram illustrating the implementation flow of the information transmission method according to an embodiment of this application, applied to a core network data element. The method includes step 1201:

[0439] Step 1201: Obtain information on the terminal's ability to support IP Multimedia Subsystem communication with high-orbit satellites, sent by the terminal through the access network element and the mobility management network element.

[0440] In some embodiments, the method further includes:

[0441] The high-orbit satellite access information sent by the access network element through the mobility management network element is obtained, wherein the high-orbit satellite access information includes satellite access type, satellite identifier, and satellite ephemeris.

[0442] In some embodiments, the method further includes:

[0443] Through the call session control function, information on the terminal's IP multimedia subsystem communication capability for high-orbit satellites and / or high-orbit satellite access information is sent to the first core network element.

[0444] It is understood that the access network element may refer to a base station.

[0445] It is understood that the mobility management network element can refer to MME or AMF.

[0446] It is understood that the core network data element may refer to HSS or UDM.

[0447] It is understood that the call session control function may refer to I / S-CSCF.

[0448] It is understandable that the first core network element may refer to the SBC / P-CSCF.

[0449] As one implementation method, under the EPC architecture, the terminal can send information about its IP multimedia subsystem communication capability for high-orbit satellites to the HSS via the base station and MME. The HSS can then send this information to the SBC / P-CSCF via the I / S-CSCF.

[0450] As another implementation, under the 5GC architecture, the terminal can send information about its IP multimedia subsystem communication capabilities for high-orbit satellites to the UDM via the base station and AMF. The UDM can then send this information to the SBC / P-CSCF via the I / S-CSCF.

[0451] As one implementation method, under the EPC architecture, the base station sends high-orbit satellite access information to the HSS through the MME, and the HSS sends high-orbit satellite access information to the SBC / P-CSCF through the I / S-CSCF.

[0452] As another implementation method, under the 5GC architecture, the base station sends high-orbit satellite access information to the UDM through the AMF, and the UDM sends high-orbit satellite access information to the SBC / P-CSCF through the I / S-CSCF.

[0453] It is understandable that after the first core network element receives the high-orbit satellite access information, it can query the satellite data module based on the satellite identifier in the access information to obtain satellite communication-related data. This data may include single-user uplink or downlink rates, transmission delay, etc. The transmission delay can be used to adjust the duration value of the SIP protocol timer.

[0454] In some embodiments, the method further includes:

[0455] Send user access satellite data to the application server; wherein, the user access satellite data includes information on the terminal's IP multimedia subsystem communication capability supporting high-orbit satellites and / or high-orbit satellite access information, the high-orbit satellite access information including satellite access type, satellite identifier, and satellite ephemeris.

[0456] The embodiments of this application have the following technical advantages:

[0457] (1) The terminal's IMS communication capability information supporting high-orbit satellites is reported to the first core network element through the core network data element. In this way, the first core network element can send the simplified SIP signaling and SIP protocol timer setting rules to the terminal. Both the first core network element and the terminal simplify the SIP signaling used in the IMS call and adjust the duration of the call-related timers in the SIP protocol according to the requirements of the first core network element. By optimizing the SIP signaling message size and adjusting the timer settings, the communication delay does not exceed the set duration of the timer, thus avoiding the problem of timer timeout due to large communication delays and resulting call release. This improves the connection success rate, user experience, and network resource utilization during the IMS call establishment process.

[0458] (2) Through the core network data element, the user access satellite data is sent to the application server. In this way, the application server performs business management or processing, such as encoding and decoding processing, and inbound and outbound call processing. By adjusting the timer duration, the number of call service failures is reduced, so that the communication delay does not exceed the timer's set duration. This avoids the problem of call release due to timer timeout caused by large communication delay, thereby improving the connection success rate, user experience, and network resource utilization during the IMS call establishment process.

[0459] See Figure 13 , Figure 13 This is a schematic diagram illustrating the implementation flow of the information transmission method according to an embodiment of this application, applied to an application server. The method includes 1301:

[0460] Step 1301: Obtain user access satellite data; wherein, the user access satellite data includes information on the terminal's IP multimedia subsystem communication capabilities supporting high-orbit satellites and / or high-orbit satellite access information, and the high-orbit satellite access information includes satellite access type, satellite identifier, and satellite ephemeris.

[0461] In some embodiments, the method further includes:

[0462] Based on the user-accessed satellite data, business management or processing is performed;

[0463] The aforementioned business management or processing includes:

[0464] Encoding and decoding processing;

[0465] Inbound and outbound call processing for business.

[0466] For example, based on the received user access satellite data, the application server sets a corresponding unreachable forwarding timer duration for users who have subscribed to the unreachable forwarding service. If the user is already on a call, new calls are rejected based on the accessed high-orbit satellite data, thus handling inbound and outbound calls for the service. This reduces service failures. The network can also inform the terminal of the user access satellite data, working together with the terminal to reduce service failures such as call hold, three-way, multi-way, and unreachable forwarding.

[0467] In some embodiments, the acquisition of user access satellite data includes

[0468] The user access satellite data is obtained from the core network data element where the terminal is located; or, the user access satellite data is obtained from the core network data element.

[0469] It is understood that the core network data element may specifically refer to HSS or UDM.

[0470] The embodiments of this application have the following technical advantages:

[0471] (1) The application server obtains the user's access satellite data, so it can perform business management or processing such as encoding and decoding processing, business inbound and outbound call processing. By adjusting the timer duration, the number of call service failures can be reduced, so that the communication delay does not exceed the timer's set duration, thereby avoiding the problem of call release due to timer timeout caused by large communication delay. This improves the connection success rate, user experience, and network resource utilization during the IMS call establishment process.

[0472] To implement the information transmission method of this application embodiment, this application embodiment also provides an information transmission device, which is installed in a terminal. Figure 14 This is a schematic diagram of the composition structure of the information transmission device according to an embodiment of this application, as shown below. Figure 14 As shown, the device includes:

[0473] The sending module 141 is used to send information about the terminal's IP multimedia subsystem communication capability supporting high-orbit satellites to the first core network element.

[0474] In some embodiments, the device is further configured to:

[0475] The system receives first information sent by the first core network element, wherein the first information represents the simplified requirements of the initial session protocol SIP signaling message and the setting rules of the SIP protocol timer.

[0476] In some embodiments, the simplification requirements for the SIP signaling message include at least one of the following:

[0477] Simplification requirements of the SIP method;

[0478] Simplified requirements for SIP message header fields;

[0479] Simplified requirements for SIP URIs;

[0480] Simplified message body requirements;

[0481] The simplification requirements of the SIP mechanism.

[0482] In some embodiments, the simplification requirements of the SIP method include:

[0483] Retain the INVITE, ACK, BYE, CANCEL, REGISTER, PRACK, and MESSAGE methods; remove the SUBSCRIBE, NOTIFY, PUBLISH, INFO, REFER, UPDATE, and OPTIONS methods.

[0484] The simplified requirements for the SIP message header fields include:

[0485] Retain the following necessary header fields: from, to, via, Call-ID, Max-Forwards, CONTACT, Content-Type, Content-Length; simplify header fields to use 1 or 2 letters for replacement.

[0486] The simplified requirements for the SIP URI include:

[0487] Retain the variable portion of the domain name part of the SIP URI and remove the fixed portion of the domain name part of the SIP URI;

[0488] The simplified requirements for the message body include:

[0489] Multiple message bodies are not supported. The message body type for SIP voice messages is application or sdp, and the message body type for SIP short messages is application or vnd.3gpp.sms. The SDP in the message body of SIP voice messages retains v, o, s, c and m, and the IMS protocol is required. The necessary a line describing low bitrate encoding and decoding is also retained.

[0490] The simplification requirements of the SIP mechanism include:

[0491] Support for the following mechanisms is not required: reliable transport of temporary responses, resource reservation, and SIP protocol encrypted with TLS.

[0492] In some embodiments, the sending module 151 is specifically used for:

[0493] Information about the terminal's IP multimedia subsystem communication capabilities supporting high-orbit satellites is sent to the first core network element through the access network element and the second core network element.

[0494] In some embodiments, the second core network element includes a mobility management network element, a core network data network element, and a call session control function.

[0495] In some embodiments, the apparatus is further configured to: adjust the duration of the SIP protocol timer according to the setting rules.

[0496] In some embodiments, the apparatus is further configured to: obtain the address of the first core network element sent by the third core network element and the duration of the registered timer.

[0497] In some embodiments, the device is further configured to: adjust the registration timer of the terminal according to the duration of the registration timer.

[0498] In practical applications, the sending module 141 can be implemented by the communication interface in the information transmission device.

[0499] It should be noted that the information transmission device provided in the above embodiments is only illustrated by the division of the above program modules. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the information transmission device and the information transmission method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0500] To implement the information transmission method of this application embodiment, this application embodiment also provides an information transmission device, which is set in the first core network element. Figure 15 This is a schematic diagram of the composition structure of the information transmission device according to an embodiment of this application, as shown below. Figure 15 As shown, the device includes:

[0501] The first acquisition module 151 is used to acquire information on the terminal's ability to support IP multimedia subsystem communication with high-orbit satellites, sent by the terminal.

[0502] In some embodiments, the first acquisition module 151 is further configured to:

[0503] Obtain high-orbit satellite access information sent by the access network element, wherein the high-orbit satellite access information includes satellite access type, satellite identifier, and satellite ephemeris.

[0504] In some embodiments, the first acquisition module 151 is specifically used for:

[0505] The terminal obtains information on its IP multimedia subsystem communication capabilities with high-orbit satellites, sent from the access network element and the second core network element to the first core network element.

[0506] In some embodiments, the first acquisition module 151 is specifically used for:

[0507] Obtain high-orbit satellite access information sent by the access network element to the first core network element through the second core network element.

[0508] In some embodiments, the device is further configured to:

[0509] Send first information to the terminal, wherein the first information represents the simplification requirements of SIP signaling messages and the setting rules of SIP protocol timers.

[0510] In some embodiments, the simplification requirements for the SIP signaling message include at least one of the following:

[0511] Simplification requirements of the SIP method;

[0512] Simplified requirements for SIP message header fields;

[0513] Simplified requirements for SIP URIs;

[0514] Simplified message body requirements;

[0515] The simplification requirements of the SIP mechanism.

[0516] In some embodiments, the simplification requirements of the SIP method include:

[0517] Retain the INVITE, ACK, BYE, CANCEL, REGISTER, PRACK, and MESSAGE methods; remove the SUBSCRIBE, NOTIFY, PUBLISH, INFO, REFER, UPDATE, and OPTIONS methods.

[0518] The simplified requirements for the SIP message header fields include:

[0519] Retain the following necessary header fields: from, to, via, Call-ID, Max-Forwards, CONTACT, Content-Type, Content-Length; simplify header fields to use 1 or 2 letters for replacement.

[0520] The simplified requirements for the SIP URI include:

[0521] Retain the variable portion of the domain name part of the SIP URI and remove the fixed portion of the domain name part of the SIP URI;

[0522] The simplified requirements for the message body include:

[0523] Multiple message bodies are not supported. The message body type for SIP voice messages is application or sdp, and the message body type for SIP short messages is application or vnd.3gpp.sms. The SDP in the message body of SIP voice messages retains v, o, s, c and m, and the IMS protocol is required. The necessary a line describing low bitrate encoding and decoding is also retained.

[0524] The simplification requirements of the SIP mechanism include:

[0525] Support for the following mechanisms is not required: reliable transport of temporary responses, resource reservation, and SIP protocol encrypted with TLS.

[0526] In some embodiments, the first core network element is a primary core network element, and the apparatus is further configured to:

[0527] Execute the MO process, and / or execute the MT process.

[0528] In some embodiments, the execution of the MO process includes:

[0529] Obtain a simplified initial call request sent by the calling terminal;

[0530] Send a simplified call intermediate response to the calling terminal;

[0531] The duration of the SIP protocol timer is adjusted to convert the simplified initial call request into a complete call request, and the complete call request is sent to the called terminal; wherein the complete call request carries an indication that resource reservation is not supported;

[0532] Obtain the call intermediate response carrying the SDP response ANSWER sent by the called terminal;

[0533] Return a PRACK message to the called terminal;

[0534] Obtain the call intermediate response sent by the called terminal in response to the PRACK message;

[0535] Return a PRACK message to the called terminal and send a simplified call intermediate response to the calling terminal that does not require reliable transmission of the interim response;

[0536] Receive the call intermediate response returned by the called terminal;

[0537] Send a simplified call intermediate response carrying an SDP ANSWER to the calling terminal;

[0538] Receive a simplified ACK message sent by the calling terminal;

[0539] The simplified ACK message is converted into a complete ACK message, and the complete ACK message is sent to the called terminal to complete the call establishment;

[0540] Obtain the simplified BYE request sent by the calling terminal;

[0541] Return a call response to the calling terminal, convert the simplified BYE request into a complete BYE request, and send the complete BYE request to the called terminal;

[0542] Obtain the call response sent by the called terminal to end the call.

[0543] In some embodiments, the device is further configured to:

[0544] Obtain the initial call request sent by the called terminal;

[0545] The duration of the SIP protocol timer is adjusted to send a simplified initial call request to the calling terminal, wherein the SDP carried in the simplified initial call request is a low-bit-rate SDP.

[0546] Obtain the simplified call intermediate response sent by the calling terminal;

[0547] Send an intermediate call response carrying a universal codec SDP ANSWER to the called terminal;

[0548] Obtain the PRACK message sent by the called terminal, and send a call response to the PRACK message to the called terminal;

[0549] Obtain the simplified call intermediate response sent by the calling terminal;

[0550] The simplified intermediate call response is converted into a complete intermediate call response that requires reliable transmission of the interim response, and the complete intermediate call response is sent to the called terminal.

[0551] Obtain the PRACK message sent by the called terminal, and send a call response to the PRACK message to the called terminal;

[0552] Obtain the simplified call answer response carrying SDP ANSWER sent by the calling terminal;

[0553] Save the SDP ANSWER, convert the simplified call answer response into a complete call answer response, and send the complete call answer response to the called terminal; the complete call answer response does not carry SDP.

[0554] Obtain the ACK message sent by the called terminal, convert the ACK message into a simplified ACK message, and send the simplified ACK message to the calling terminal to complete the call establishment;

[0555] Obtain the BYE request sent by the called terminal;

[0556] Send a call response to the called terminal, convert the BYE request into a simplified BYE request, and send the simplified BYE request to the calling terminal;

[0557] Obtain the call response returned by the calling terminal to end the call.

[0558] In practical applications, the first acquisition module 151 can be implemented by the communication interface in the information transmission device.

[0559] It should be noted that the information transmission device provided in the above embodiments is only illustrated by the division of the above program modules. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the information transmission device and the information transmission method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0560] To implement the information transmission method of this application embodiment, this application embodiment also provides a virtual machine device, which is set in the core network data network element. Figure 16 This is a schematic diagram of the composition structure of the information transmission device according to an embodiment of this application, as shown below. Figure 16 As shown, the device includes:

[0561] The second acquisition module 161 is used to acquire information on the terminal's ability to support IP multimedia subsystem communication with high-orbit satellites, which is sent by the terminal through the access network element and the mobility management network element.

[0562] In some embodiments, the second acquisition module 161 is further configured to:

[0563] The high-orbit satellite access information sent by the access network element through the mobility management network element is obtained, wherein the high-orbit satellite access information includes satellite access type, satellite identifier, and satellite ephemeris.

[0564] In some embodiments, the device is further configured to:

[0565] Through the call session control function, information on the terminal's IP multimedia subsystem communication capability for high-orbit satellites and / or high-orbit satellite access information is sent to the first core network element.

[0566] In some embodiments, the device is further configured to:

[0567] Send user access satellite data to the application server; wherein, the user access satellite data includes information on the terminal's IP multimedia subsystem communication capability supporting high-orbit satellites and / or high-orbit satellite access information, the high-orbit satellite access information including satellite access type, satellite identifier, and satellite ephemeris.

[0568] In practical applications, the second acquisition module 161 can be implemented by the communication interface in the information transmission device; the processing unit can be implemented by the processor in the information transmission device.

[0569] It should be noted that the information transmission device provided in the above embodiments is only illustrated by the division of the above program modules. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the information transmission device and the information transmission method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0570] To implement the information transmission method of this application embodiment, this application embodiment also provides an information transmission device, which is set on the application server. Figure 17 This is a schematic diagram of the composition structure of the information transmission device according to an embodiment of this application, as shown below. Figure 17 As shown, the device includes:

[0571] The third acquisition module 171 is used to acquire user access satellite data; wherein, the user access satellite data includes information on the terminal's IP multimedia subsystem communication capability for supporting high-orbit satellites and / or high-orbit satellite access information, and the high-orbit satellite access information includes satellite access type, satellite identifier, and satellite ephemeris.

[0572] In some embodiments, the device is further configured to:

[0573] Based on the user-accessed satellite data, business management or processing is performed;

[0574] The aforementioned business management or processing includes:

[0575] Encoding and decoding processing;

[0576] Inbound and outbound call processing for business.

[0577] In some embodiments, the third acquisition module 171 is further configured to:

[0578] The user access satellite data is obtained from the core network data element where the terminal is located; or, the user access satellite data is obtained from the core network data element.

[0579] In practical applications, the third acquisition module 171 can be implemented by the communication interface in the information transmission device; the processing unit can be implemented by the processor in the information transmission device.

[0580] It should be noted that the information transmission device provided in the above embodiments is only illustrated by the division of the above program modules. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the information transmission device and the information transmission method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0581] This application also provides a terminal, such as... Figure 18 As shown, it includes:

[0582] The first communication interface 181 is capable of exchanging information with other devices;

[0583] The first processor 182, connected to the first communication interface 181, is used to execute the methods provided by one or more of the aforementioned terminal-side technical solutions when running a computer program. The computer program is stored in the first memory 183.

[0584] It should be noted that the specific processing procedures of the first processor 182 and the first communication interface 181 are detailed in the method embodiment and will not be repeated here.

[0585] Of course, in practical applications, the various components in terminal 180 are coupled together through bus system 184. It can be understood that bus system 184 is used to implement communication between these components. In addition to a data bus, bus system 184 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 18 The general labeled all buses as Bus System 184.

[0586] The first memory 183 in this embodiment is used to store various types of data to support the operation of the terminal 200. Examples of such data include any computer program used to operate on the terminal 180.

[0587] The methods disclosed in the above embodiments of this application can be applied to the first processor 182, or implemented by the first processor 182. The first processor 182 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware or by instructions in the form of software in the first processor 182. The first processor 182 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 182 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly reflected as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the first memory 183. The first processor 182 reads the information in the first memory 183 and completes the steps of the aforementioned method in combination with its hardware.

[0588] This application embodiment also provides a first core network element, such as Figure 19 As shown, it includes:

[0589] The second communication interface 191 is capable of exchanging information with other devices;

[0590] The second processor 192, connected to the second communication interface 191, is used to execute the methods provided by one or more technical solutions on the first core network element side when running a computer program. The computer program is stored in the second memory 193.

[0591] It should be noted that the specific processing procedures of the second processor 192 and the second communication interface 191 are detailed in the method embodiment and will not be repeated here.

[0592] Of course, in practical applications, the various components in the first core network element 190 are coupled together through the bus system 194. It can be understood that the bus system 194 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 194 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, in... Figure 19 The general labeled all buses as Bus System 194.

[0593] The second memory 193 in this embodiment is used to store various types of data to support the operation of the first core network element 190. Examples of such data include any computer program used to operate on the first core network element 190.

[0594] The methods disclosed in the embodiments of this application can be applied to, or implemented by, the second processor 192. The second processor 192 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the integrated logic circuitry of the hardware or by instructions in the software form of the second processor 192. The second processor 192 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The second processor 192 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, specifically a second memory 193. The second processor 192 reads information from the second memory 193 and, in conjunction with its hardware, completes the steps of the aforementioned method.

[0595] This application also provides a core network data element, such as... Figure 20 As shown, it includes:

[0596] The third communication interface 201 is capable of exchanging information with other devices;

[0597] The third processor 202, connected to the third communication interface 201, is used to execute the methods provided by one or more technical solutions on the core network data element side when running a computer program. The computer program is stored in the third memory 203.

[0598] It should be noted that the specific processing procedures of the third processor 202 and the third communication interface 201 are detailed in the method embodiment and will not be repeated here.

[0599] Of course, in practical applications, the various components in the core network data element 200 are coupled together through the bus system 204. It can be understood that the bus system 204 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 204 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, in... Figure 20 The general designated all buses as Bus System 204.

[0600] The third memory 203 in this embodiment is used to store various types of data to support the operation of the core network data element 230. Examples of such data include any computer program used to operate on the core network data element 200.

[0601] The methods disclosed in the embodiments of this application can be applied to, or implemented by, the third processor 202. The third processor 202 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the integrated logic circuitry of the hardware or by instructions in the software form of the third processor 202. The third processor 202 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The third processor 202 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, specifically a third memory 203. The third processor 202 reads information from the third memory 203 and, in conjunction with its hardware, completes the steps of the aforementioned method.

[0602] This application also provides an application server, such as... Figure 21 As shown, it includes:

[0603] The fourth communication interface 213 is capable of exchanging information with other devices;

[0604] The fourth processor 212, connected to the fourth communication interface 213, is used to execute the methods provided by one or more technical solutions on the AS side when running a computer program. The computer program is stored in the fifth memory 213.

[0605] It should be noted that the specific processing procedures of the fourth processor 212 and the fourth communication interface 213 are detailed in the method embodiment and will not be repeated here.

[0606] Of course, in practical applications, the various components in application server 210 are coupled together through bus system 214. It can be understood that bus system 214 is used to implement communication between these components. In addition to a data bus, bus system 214 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 21 The general designated all buses as Bus System 214.

[0607] The fourth memory 213 in this embodiment is used to store various types of data to support the operation of AS210. Examples of such data include any computer program used to operate on AS210.

[0608] The methods disclosed in the embodiments of this application can be applied to, or implemented by, the fourth processor 212. The fourth processor 212 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the integrated logic circuitry of the hardware or by instructions in the software form of the fourth processor 212. The fourth processor 212 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The fourth processor 212 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, specifically a fourth memory 213. The fourth processor 212 reads information from the fourth memory 213 and, in conjunction with its hardware, completes the steps of the aforementioned method.

[0609] In an exemplary embodiment, the terminal 180, the first core network element 190, the core network data element 200, and the application server 210 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned method.

[0610] It is understood that the memories (first memory 183, second memory 193, etc.) in the embodiments of this application can be volatile memories or non-volatile memories, or both. Non-volatile memories can be read-only memories (ROM), programmable read-only memories (PROM), erasable programmable read-only memories (EPROM), electrically erasable programmable read-only memories (EEPROM), magnetic random access memories (FRAM), flash memories, magnetic surface memories, optical discs, or compact disc read-only memories (CD-ROM); magnetic surface memories can be disk storage or magnetic tape storage. Volatile memories can be random access memories (RAM), which are used as external caches. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0611] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a memory storing a computer program, which can be executed by the first processor 182 of the terminal 180 to complete the steps described in the aforementioned terminal-side method. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

[0612] For example, this application also provides a computer program product, including a computer program that can be executed by a first processor 202 of a terminal 180 to complete the steps of any of the aforementioned terminal-side methods; the computer program can be executed by a second processor 192 of a first core network element 190 to complete the steps of any of the aforementioned first core network element-side methods; the computer program can be executed by a third processor 202 of a core network data element 200 to complete the steps of any of the aforementioned core network data element-side methods; and the computer program can be executed by a fourth processor 212 of an application server 210 to complete the steps of any of the aforementioned application server-side methods.

[0613] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0614] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0615] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application.

Claims

1. A method of information transmission, characterized in that, Applied to a terminal, the method includes: Send information about the terminal's IP multimedia subsystem communication capabilities supporting high-orbit satellites to the first core network element.

2. The method according to claim 1, characterized in that, The method further includes: The system receives first information sent by the first core network element, wherein the first information represents the simplified requirements of the Session Initiation Protocol (SIP) signaling message and the setting rules of the SIP protocol timer.

3. The method according to claim 2, characterized in that, The simplification requirements for the SIP signaling messages include at least one of the following: Simplification requirements of the SIP method; Simplified requirements for SIP message header fields; Simplified requirements for SIP Uniform Resource Identifier (URI); Simplified message body requirements; The simplification requirements of the SIP mechanism.

4. The method according to claim 3, characterized in that, The simplification requirements of the SIP method include: Retain the INVITE, ACK, BYE, CANCEL, REGISTER, PRACK, and MESSAGE methods; remove the SUBSCRIBE, NOTIFY, PUBLISH, INFO, REFER, UPDATE, and OPTIONS methods. The simplified requirements for the SIP message header fields include: Retain the following necessary header fields: from, to, via, Call-ID, Max-Forwards, CONTACT, Content-Type, Content-Length; simplify header fields to use 1 or 2 letters for replacement. The simplified requirements for the SIP URI include: Retain the variable portion of the domain name part of the SIP URI and remove the fixed portion of the domain name part of the SIP URI; The simplified requirements for the message body include: Multiple message bodies are not supported. The message body type for SIP voice messages is application or sdp, and the message body type for SIP short messages is application or vnd.3gpp.sms. The SDP in the message body of SIP voice messages retains v, o, s, c and m, and the IMS protocol is required. The necessary a line describing low bitrate encoding and decoding is also retained. The simplification requirements of the SIP mechanism include: Support for the following mechanisms is not required: reliable transport of temporary responses, resource reservation, and SIP protocol encrypted with Transport Layer Security (TLS).

5. The method according to claim 1, characterized in that, The step of sending information about the terminal's IP multimedia subsystem communication capabilities for high-orbit satellites to the first core network element includes: Information about the terminal's IP multimedia subsystem communication capabilities supporting high-orbit satellites is sent to the first core network element through the access network element and the second core network element.

6. The method according to claim 5, characterized in that, The second core network element includes a mobility management network element, a core network data network element, and a call session control function.

7. The method according to claim 2, characterized in that, The method further includes: The duration of the SIP protocol timer is adjusted according to the setting rules.

8. The method according to claim 1, characterized in that, The method further includes: Obtain the address of the first core network element and the duration of the registration timer sent by the third core network element.

9. The method according to claim 8, characterized in that, The method further includes: The registration timer of the terminal is adjusted according to the duration of the registration timer.

10. An information transmission method, characterized in that, Applied to the first core network element, the method includes: Obtain information from the terminal regarding its IP Multimedia Subsystem communication capabilities with high-orbit satellites.

11. The method according to claim 10, characterized in that, The method further includes: Obtain high-orbit satellite access information sent by the access network element, wherein the high-orbit satellite access information includes satellite access type, satellite identifier, and satellite ephemeris.

12. The method according to claim 10, characterized in that, The acquisition of information regarding the terminal's support for IP Multimedia Subsystem communication capabilities with high-orbit satellites, sent by the terminal, includes: The terminal obtains information on its IP multimedia subsystem communication capabilities with high-orbit satellites, sent from the access network element and the second core network element to the first core network element.

13. The method according to claim 11, characterized in that, The acquisition of high-orbit satellite access information sent by the access network element includes: Obtain high-orbit satellite access information sent by the access network element to the first core network element through the second core network element.

14. The method according to claim 10, characterized in that, The method further includes: Send first information to the terminal, wherein the first information represents the simplification requirements of SIP signaling messages and the setting rules of SIP protocol timers.

15. The method according to claim 14, characterized in that, The simplification requirements for the SIP signaling messages include at least one of the following: Simplification requirements of the SIP method; Simplified requirements for SIP message header fields; Simplified requirements for SIP URIs; Simplified message body requirements; The simplification requirements of the SIP mechanism.

16. The method according to claim 15, characterized in that, The simplification requirements of the SIP method include: Retain the INVITE, ACK, BYE, CANCEL, REGISTER, PRACK, and MESSAGE methods; remove the SUBSCRIBE, NOTIFY, PUBLISH, INFO, REFER, UPDATE, and OPTIONS methods. The simplified requirements for the SIP message header fields include: Retain the following necessary header fields: from, to, via, Call-ID, Max-Forwards, CONTACT, Content-Type, Content-Length; simplify header fields to use 1 or 2 letters for replacement. The simplified requirements for the SIP URI include: Retain the variable portion of the domain name part of the SIP URI and remove the fixed portion of the domain name part of the SIP URI; The simplified requirements for the message body include: Multiple message bodies are not supported. The message body type for SIP voice messages is application or sdp, and the message body type for SIP short messages is application or vnd.3gpp.sms. The SDP in the message body of SIP voice messages retains v, o, s, c and m, and the IMS protocol is required. The necessary a line describing low bitrate encoding and decoding is also retained. The simplification requirements of the SIP mechanism include: Support for the following mechanisms is not required: reliable transport of temporary responses, resource reservation, and SIP protocol encrypted with TLS.

17. The method according to claim 10, characterized in that, The first core network element is the calling core network element, and the method further includes: Perform the calling party dialing (MO) procedure, and / or perform the called party calling (MT) procedure.

18. The method according to claim 17, characterized in that, The execution of the MO process includes: Obtain a simplified initial call request sent by the calling terminal; Send a simplified call intermediate response to the calling terminal; The duration of the SIP protocol timer is adjusted to convert the simplified initial call request into a complete call request, and the complete call request is sent to the called terminal; wherein the complete call request carries an indication that resource reservation is not supported; Obtain the call intermediate response sent by the called terminal, which carries the Session Description Protocol (SDP) response ANSWER. A temporary response PRACK message is returned to the called terminal; Obtain the call intermediate response sent by the called terminal in response to the PRACK message; Return a PRACK message to the called terminal and send a simplified call intermediate response to the calling terminal that does not require reliable transmission of the interim response; Receive the call intermediate response returned by the called terminal; Send a simplified call intermediate response carrying an SDP ANSWER to the calling terminal; Receive a simplified ACK message sent by the calling terminal; The simplified ACK message is converted into a complete ACK message, and the complete ACK message is sent to the called terminal to complete the call establishment; Obtain the simplified end-of-call (BYE) request sent by the calling terminal; Return a call response to the calling terminal, convert the simplified BYE request into a complete BYE request, and send the complete BYE request to the called terminal; Obtain the call response sent by the called terminal to end the call.

19. The method according to claim 17, characterized in that, The execution of the MT process includes: Obtain the initial call request sent by the called terminal; The duration of the SIP protocol timer is adjusted to send a simplified initial call request to the calling terminal, wherein the SDP carried in the simplified initial call request is a low-bit-rate SDP. Obtain the simplified call intermediate response sent by the calling terminal; Send an intermediate call response carrying a universal codec SDP ANSWER to the called terminal; Obtain the PRACK message sent by the called terminal, and send a call response to the PRACK message to the called terminal; Obtain the simplified call intermediate response sent by the calling terminal; The simplified intermediate call response is converted into a complete intermediate call response that requires reliable transmission of the interim response, and the complete intermediate call response is sent to the called terminal. Obtain the PRACK message sent by the called terminal, and send a call response to the PRACK message to the called terminal; Obtain the simplified call answer response carrying SDP ANSWER sent by the calling terminal; Save the SDP ANSWER, convert the simplified call answer response into a complete call answer response, and send the complete call answer response to the called terminal; the complete call answer response does not carry SDP. Obtain the ACK message sent by the called terminal, convert the ACK message into a simplified ACK message, and send the simplified ACK message to the calling terminal to complete the call establishment; Obtain the BYE request sent by the called terminal; Send a call response to the called terminal, convert the BYE request into a simplified BYE request, and send the simplified BYE request to the calling terminal; Obtain the call response returned by the calling terminal to end the call.

20. An information transmission method, characterized in that, Applied to core network data elements, the method includes: The terminal obtains information on its IP multimedia subsystem communication capabilities with high-orbit satellites, sent by the terminal through the access network element and the mobility management network element.

21. The method according to claim 20, characterized in that, The method further includes: The high-orbit satellite access information sent by the access network element through the mobility management network element is obtained, wherein the high-orbit satellite access information includes satellite access type, satellite identifier, and satellite ephemeris.

22. The method according to claim 21, characterized in that, The method further includes: Through the call session control function, information on the terminal's IP multimedia subsystem communication capability for high-orbit satellites and / or high-orbit satellite access information is sent to the first core network element.

23. The method according to claim 21, characterized in that, The method further includes: Send user access satellite data to the application server; wherein, the user access satellite data includes information on the terminal's IP multimedia subsystem communication capability supporting high-orbit satellites and / or high-orbit satellite access information, the high-orbit satellite access information including satellite access type, satellite identifier, and satellite ephemeris.

24. An information transmission method, characterized in that, Applied to an application server, the method includes: Acquire user access satellite data; wherein, the user access satellite data includes information on the terminal's IP multimedia subsystem communication capabilities supporting high-orbit satellites and / or high-orbit satellite access information, the high-orbit satellite access information including satellite access type, satellite identifier, and satellite ephemeris.

25. The method according to claim 24, characterized in that, The method further includes: Based on the user-accessed satellite data, business management or processing is performed; The aforementioned business management or processing includes: Encoding and decoding processing; Inbound and outbound call processing for business.

26. The method according to claim 24, characterized in that, The acquisition of user access satellite data includes: The user access satellite data is obtained from the core network data element where the terminal is located; or, the user access satellite data is obtained from the core network data element.

27. An information transmission device, characterized in that, include: The sending module is used to send information about the terminal's IP multimedia subsystem communication capabilities supporting high-orbit satellites to the first core network element.

28. An information transmission device, characterized in that, include: The first acquisition module is used to acquire information on the terminal's ability to support IP multimedia subsystem communication with high-orbit satellites, sent by the terminal.

29. An information transmission device, characterized in that, include: The second acquisition module is used to acquire information on the terminal's ability to support IP Multimedia Subsystem communication with high-orbit satellites, sent by the terminal through the access network element and the mobility management network element.

30. An information transmission device, characterized in that, include: The third acquisition module is used to acquire user access satellite data; wherein, the user access satellite data includes information on the terminal's IP multimedia subsystem communication capabilities supporting high-orbit satellites and / or high-orbit satellite access information, and the high-orbit satellite access information includes satellite access type, satellite identifier, and satellite ephemeris.

31. A terminal, characterized in that, This includes a processor and memory for storing computer programs that can run on the processor. When the processor is used to run the computer program, it performs the steps of the method according to any one of claims 1 to 9.

32. A first core network element, characterized in that, This includes a processor and memory for storing computer programs that can run on the processor. When the processor is used to run the computer program, it performs the steps of the method according to any one of claims 10 to 19.

33. A core network data element, characterized in that, This includes a processor and memory for storing computer programs that can run on the processor. When the processor is used to run the computer program, it performs the steps of the method according to any one of claims 20 to 23.

34. An application server, characterized in that, This includes a processor and memory for storing computer programs that can run on the processor. When the processor is used to run the computer program, it performs the steps of the method according to any one of claims 24 to 26.

35. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 9, or implements the steps of the method according to any one of claims 10 to 19, or implements the steps of the method according to any one of claims 20 to 23, or implements the steps of the method according to any one of claims 24 to 26.

36. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method according to any one of claims 1 to 9, or implements the method according to any one of claims 10 to 19, or implements the method according to any one of claims 20 to 23, or implements the method according to any one of claims 24 to 26.

Images