Sip message transmission method and apparatus, and communication device

By collaborating between the terminal and the network side and utilizing a combination of SIP message templates and the first message, the problems of SIP message transmission efficiency and success rate under limited bandwidth resources are solved. This achieves signaling compression and simplified interaction processes, thereby improving the efficiency of the communication system.

WO2026232747A1PCT designated stage Publication Date: 2026-11-12CHINA SATELLITE NETWORK EXPLORATION CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/125532
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2025-09-29
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In communication systems with limited bandwidth resources, existing technologies struggle to effectively improve the transmission efficiency and success rate of SIP messages.

Method used

By collaborating between the terminal and the network side, SIP message templates are sent in advance, and first messages are sent when needed to combine them into the final SIP message, reducing the number of fields transmitted and the signaling size.

Benefits of technology

It improves the transmission efficiency and success rate of SIP messages, reduces signaling redundancy, and meets the requirements of high-capacity and low-latency communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025125532_12112026_PF_FP_ABST
    Figure CN2025125532_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the present application are a SIP message transmission method and apparatus, and a communication device. The method comprises: receiving at least one SIP message template from a terminal, wherein the SIP message template comprises at least some fields in a SIP message, and a first preset value corresponding to each of the at least some fields; receiving a first message from the terminal, wherein the first message comprises a first field in the SIP message and a second preset value corresponding to the first field; and on the basis of the at least one SIP message template and the first message, determining the SIP message. The present application can improve the transmission efficiency of SIP messages.
Need to check novelty before this filing date? Find Prior Art

Description

SIP message transmission methods, apparatus and communication equipment

[0001] This application claims priority to Chinese Patent Application No. 202510603168.X, filed on May 8, 2025, entitled "SIP Message Transmission Method, Apparatus and Communication Equipment", the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] SIP is a text-based application layer protocol used to establish, modify, and terminate multimedia sessions. In an IMS session, multiple SIP message exchanges are required between the terminal and IMS to establish and terminate the IMS session.

[0004] With limited bandwidth resources, improving transmission efficiency has become an urgent problem to be solved. Summary of the Invention

[0005] This application provides a SIP message transmission method, apparatus, and communication device, which can improve the transmission efficiency and success rate of SIP messages.

[0006] Firstly, a Session Initiation Protocol (SIP) message transmission method is proposed for application on the network side, the method comprising:

[0007] Receive at least one SIP message template from a terminal, the SIP message template including at least some fields in a SIP message and a first preset value corresponding to each of the at least some fields;

[0008] Receive a first message from the terminal, the first message including a first field in a SIP message and a second preset value corresponding to the first field;

[0009] The SIP message is determined based on the at least one SIP message template and the first message.

[0010] In some embodiments, the SIP message type includes at least one of the following: INVITE message; PRACK message; UPDATE message; ACK message; BYE message; 183 Session Progress message; 180 Ringing message; and SDP message.

[0011] In some embodiments, the SIP message corresponds to at least one SIP message template.

[0012] In some embodiments, the first field includes fields that are different from those in the SIP message template.

[0013] In some embodiments, the first field includes the same field as the field in the SIP message template, and the same field has a second preset value that is different from the first preset value.

[0014] In some embodiments, the first field is a field used to indicate a first terminal identifier of the peer terminal.

[0015] In some embodiments, the first message further includes a first template identifier, wherein one SIP message template corresponds to one template identifier;

[0016] The step of determining the SIP message based on the at least one SIP message template and the first message includes:

[0017] Based on the first template identifier, a corresponding first message template is determined in the at least one SIP message template;

[0018] The first message and the first message template are combined to form the SIP message.

[0019] In some embodiments, each SIP message template in the at least one SIP message template corresponds to at least one of the following: at least one network type; at least one network condition; at least one media type; at least one codec type.

[0020] In some embodiments, each SIP message template in the at least one SIP message template corresponds to at least one network type, and the first message further includes information for indicating the first network type to which the terminal is connected;

[0021] The step of determining the SIP message based on the at least one SIP message template and the first message includes:

[0022] Based on the information indicating the first network type connected to the terminal, a corresponding second SIP message template is determined from the at least one SIP message template;

[0023] The first message and the second SIP message template are combined to form the SIP message.

[0024] In some embodiments, the at least one SIP message template is included in a SIP registration message.

[0025] In some embodiments, prior to receiving at least one SIP message template from the terminal, the method further includes:

[0026] Receive a SIP registration message from the terminal, the SIP registration message including information indicating that the terminal supports SIP message templates;

[0027] A SIP registration acceptance message is sent to the terminal, the SIP registration acceptance message including information indicating that the network side supports SIP message templates.

[0028] In some embodiments, the fields in the SIP message template and at least one of the first messages are fields that have undergone mapping simplification.

[0029] In some embodiments, the network side includes the Internet Protocol Multimedia Subsystem (IMS).

[0030] Secondly, a SIP message transmission method is proposed for use in a terminal, the method comprising:

[0031] Send at least one SIP message template to the network side, the SIP message template including at least some fields in the SIP message and a first preset value corresponding to each of the at least some fields;

[0032] Send a first message to the network side. The first message includes a first field in the SIP message and a second preset value corresponding to the first field.

[0033] In some embodiments, the SIP message type includes at least one of the following: INVITE message; PRACK message; UPDATE message; ACK message; BYE message; 183 Session Progress message; 180 Ringing message; SDP message.

[0034] In some embodiments, the SIP message corresponds to at least one SIP message template.

[0035] In some embodiments, the first field includes fields that are different from those in the SIP message template.

[0036] In some embodiments, the first field includes a field identical to a field in the SIP message template, and the identical field has a second preset value different from a first preset value. In some embodiments, the first field is a field used to indicate a first terminal identifier of the peer terminal.

[0037] In some embodiments, the first field and the value of the first field are determined by the terminal based on at least one of network type, network quality, or service requirements.

[0038] In some embodiments, the first message further includes a first template identifier, and one SIP message template corresponds to one template identifier.

[0039] In some embodiments, the first template is identified by the terminal based on at least one of network type or network condition, and one SIP message template corresponds to at least one of at least one network type or at least one of at least one network condition.

[0040] In some embodiments, each SIP message template in the at least one SIP message template corresponds to at least one of the following: at least one network type; at least one network condition; at least one media type; at least one codec type.

[0041] In some embodiments, each SIP message template in the at least one SIP message template corresponds to at least one network type, and the first message further includes information for indicating the first network type to which the terminal is connected.

[0042] In some embodiments, before sending at least one SIP message template to the network side, the method further includes:

[0043] Send a SIP registration message to the network side, the SIP registration message including information indicating that the terminal supports SIP message templates;

[0044] Receive a SIP registration acceptance message from the network side, the SIP registration acceptance message including information indicating that the network side supports SIP message templates.

[0045] In some embodiments, the network side includes IMS.

[0046] In some embodiments, the network side includes a proxy call session control function (P-CSCF) network element.

[0047] In some embodiments, before sending at least one SIP message template to the network side, the method further includes:

[0048] When the terminal accesses the core network, a request message to create an IMS connection is sent to the core network;

[0049] Receive information from the core network indicating that the IMS supports SIP message templates.

[0050] In some embodiments, the at least one SIP message template is included in a SIP registration message.

[0051] In some embodiments, the fields in the SIP message template and at least one of the first messages are fields that have undergone mapping simplification.

[0052] Thirdly, a SIP message transmission device is proposed for use on the network side, the device comprising:

[0053] A receiving module is configured to receive at least one SIP message template from a terminal, the SIP message template including at least some fields in a SIP message and a first preset value corresponding to each of the at least some fields;

[0054] The receiving module is further configured to receive a first message from the terminal, the first message including a first field in a SIP message and a second preset value corresponding to the first field;

[0055] The processing module is configured to determine the SIP message based on the at least one SIP message template and the first message.

[0056] Fourthly, a SIP message transmission device is proposed for use in a terminal, the device comprising:

[0057] A sending module is used to send at least one SIP message template to the network side, wherein the SIP message template includes at least some fields in the SIP message and a first preset value corresponding to each of the at least some fields;

[0058] The sending module is further configured to send a first message to the network side, the first message including a first field in a SIP message and a second preset value corresponding to the first field.

[0059] Fifthly, a communication device is provided, comprising: a processor, and a memory communicatively connected to the processor;

[0060] The memory stores computer-executed instructions;

[0061] The processor executes computer execution instructions stored in the memory to implement the method as described in any one of the first aspects and its implementable embodiments.

[0062] In a sixth aspect, a communication device is provided, comprising: a processor, and a memory communicatively connected to the processor;

[0063] The memory stores computer-executed instructions;

[0064] The processor executes computer execution instructions stored in the memory to implement the method as described in any one of the second aspect and its implementable embodiments.

[0065] In a seventh aspect, a computer-readable storage medium is provided, wherein computer-executable instructions are stored therein, which, when executed by a processor, are used to implement the method as described in any one of the first aspect and its implementable embodiments, and the second aspect and its implementable embodiments.

[0066] Eighthly, a computer program product is proposed, comprising a computer program that, when executed by a processor, implements the method of any one of the first aspect and its implementable embodiments, the second aspect and its implementable embodiments.

[0067] The SIP message transmission method, apparatus, and communication device provided in this application allow the terminal to pre-send a SIP message template when sending SIP messages. Subsequently, when a SIP message needs to be sent, only the first message needs to be sent. The required SIP message can be obtained through the SIP message template and the first message. The first message includes the first field and the second preset value of the SIP message, thereby reducing the number of fields that need to be sent when sending SIP messages, thus reducing the size of the signaling that needs to be sent when sending SIP messages, and improving the transmission efficiency and success rate of SIP messages. Attached Figure Description

[0068] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0069] Figure 1 is a structural diagram of a communication system according to an embodiment of this application;

[0070] Figure 2 is a flowchart illustrating a SIP message transmission method according to an embodiment of this application;

[0071] Figure 3 is a flowchart illustrating a SIP message transmission method according to another embodiment of this application;

[0072] Figure 4 is a flowchart illustrating a SIP message transmission method according to another embodiment of this application;

[0073] Figure 5 is a flowchart illustrating a SIP message transmission method according to another embodiment of this application;

[0074] Figure 6 is a flowchart illustrating a SIP message transmission method according to another embodiment of this application;

[0075] Figure 7 is a schematic block diagram of a SIP message transmission apparatus according to an embodiment of this application;

[0076] Figure 8 is a schematic block diagram of a SIP message transmission apparatus according to another embodiment of this application;

[0077] Figure 9 is a schematic block diagram of a communication device according to an embodiment of this application.

[0078] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0079] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0080] The Session Initiation Protocol (SIP) is a text-based application layer protocol used to establish, modify, and terminate multimedia sessions. During an IMS session, various SIP messages are exchanged, such as: the INVITE message, which initiates a call request and carries an SDP offer (media parameters proposed by the calling terminal) to begin media negotiation; the 183 Session Progress message, as a temporary response, carries an SDP answer (media parameters accepted or adjusted by the peer terminal) to confirm media parameters; the PRACK message, which ensures reliable transmission of the temporary response; the UPDATE message, which updates the QoS (Quality of Service) resource reservation status; the 180 Ringing message, which notifies the calling and peer terminals of the ringing status; the 200 OK message, which confirms the final session establishment; the ACK message, which completes the three-way handshake to confirm the final response; and the BYE message, which terminates the session. SDP messages, through the interaction of INVITE, 183 Session Progress, and UPDATE, complete the negotiation of media parameters such as encoding and decoding.

[0081] To improve the efficiency of SIP message transmission, SIP messages can be simplified to reduce the signaling size. The simplification process mainly includes: simplifying the mapping of SIP message header field names (e.g., shortening the field names in the SIP message to short characters) and simplifying the field values ​​of the SIP message (e.g., deleting unnecessary or reusable values ​​and retaining key information). This reduces SIP message signaling redundancy during continuous communication, achieving signaling compression and simplified interaction processes.

[0082] However, in some communication scenarios, due to limited bandwidth resources of the communication link, even after simplifying the SIP message before transmitting it, it is still difficult to meet the requirements of high-capacity and low-latency communication, resulting in SIP message transmission failure.

[0083] Based on this, embodiments of this application propose a SIP message transmission method, apparatus, and communication device to reduce the signaling size of SIP message transmission, improve the reliability of SIP message transmission, and improve the efficiency of SIP message transmission.

[0084] The technical solutions of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, future 5th Generation (5G) communication systems or new radio access technology (NR), vehicle-to-other devices (V2X), where V2X can include vehicle-to-network (V2N), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), etc., Long Term Evolution-Vehicle (LTE-V) communication, vehicle-to-everything (V2X) communication, machine-type communication (M2X). Communication technologies such as MTC (Mechanical, Communication and Communication Technology), Internet of Things (IoT), Long Term Evolution-Machine (LTE-M), and Machine to Machine (M2M) are mentioned.

[0085] As shown in Figure 1, the communication system may include an Internet Protocol Multimedia Subsystem (IMS), such as the network side 110 shown in Figure 1; the communication system may also include at least one terminal, such as terminal 120 shown in Figure 1. Terminal 120 may be mobile or fixed. IMS calls can be made between two terminals 120.

[0086] In this embodiment of the disclosure, the network side 110 can be any entity that supports the SIP protocol, such as devices supporting SIP signaling in enterprise networks, Internet Service Provider (ISP) networks, such as IMS, or SIP Proxy Servers in Voice over IP (VoIP) communication, or SIP PBXs in enterprise Internet Protocol (IP) telephony systems.

[0087] (Internet Protocol-based telephone exchange systems), etc., are not specifically limited here.

[0088] In this embodiment, terminal 120 is a user-side entity used to receive or transmit signals, such as a mobile phone. A terminal can also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), user-side equipment, etc. Terminals can be communication-enabled vehicles, smart cars, mobile phones, wearable devices, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.

[0089] In some embodiments, terminal 120 sends at least one SIP message template to network side 110. The SIP message template includes at least some fields in the SIP message and a first preset value corresponding to each field in the at least some fields. Terminal 120 sends a first message to network side 110. The first message includes a first field in the SIP message and a second preset value corresponding to the first field. Network side 110 determines a SIP message based on at least one SIP message template and the first message. In this way, network side 110 can obtain a SIP message by combining the first message and the SIP message template, thereby reducing the amount of data of the first message transmitted by the terminal to IMS and improving the transmission efficiency of the SIP message.

[0090] The embodiments disclosed herein do not limit the specific technologies or device forms used on the terminal / network side.

[0091] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0092] It is understood that the communication system described in the embodiments of this disclosure is for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and does not constitute a limitation on the technical solutions provided in the embodiments of this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this disclosure are also applicable to similar technical problems.

[0093] It is understood that in the embodiments of this application, "for indicating" can include both direct and indirect indication, as well as explicit and implicit indication. The information indicated by a certain piece of information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as, but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or its index. It can also indirectly indicate the information to be indicated by indicating other information, where there is a correlation between the other information and the information to be indicated. It can also indicate only a part of the information to be indicated, while the other parts are known or pre-agreed upon. For example, the indication of the information to be indicated can be achieved by pre-agreed upon (e.g., by a protocol specifying) the existence of a certain information element, thereby reducing the indication overhead to some extent.

[0094] It is understood that in the embodiments shown below, the terms "first," "second," and various numerical designations are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. For example, they may be used to distinguish different indication information, different time intervals, etc.

[0095] It is understood that "preset values" can be implemented by pre-saving corresponding codes, tables, or other means that can be used to indicate relevant information in a device (e.g., including terminal devices and IMS, P-CSCF). This application does not limit the specific implementation method. "Saving" can mean saving in one or more memories. The one or more memories can be separate settings or integrated into a codec or decoder, processor, or communication device. The one or more memories can also be partially separate settings and partially integrated into a decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0096] It is understood that the “protocol” involved in the embodiments of this application may refer to standard protocols in the field of communication, such as LTE protocol, NR protocol and related protocols applied to future communication systems, and this application does not limit it.

[0097] Understandably, "at least one" refers to one or more, while "more" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b, and c. Here, a, b, and c can be single or multiple.

[0098] It is understood that in the embodiments of this application, descriptions such as "when," "under the circumstances," "if," and "if" all refer to the fact that the device (e.g., a terminal device or a network device) will make corresponding processing under certain objective circumstances. They are not time limits, nor do they require the device (e.g., a terminal device or a network device) to make a judgment action when implementing it, nor do they imply any other limitations.

[0099] It is understood that, for the sake of clarity in illustrating the embodiments of this application, unless otherwise specified, all message names mentioned herein refer to message names in NR (New Message List). However, it is understood that these message names are merely illustrative examples for ease of understanding and should not constitute any limitation on this application. This application does not preclude the possibility of defining other message names in future protocols to replace the message names listed herein to achieve the same or similar functions. Furthermore, using message names in NR as examples to illustrate the embodiments of this application should not constitute any limitation on the scenarios to which the methods provided in this application are applicable.

[0100] It is understood that several embodiments are described in detail below with reference to multiple flowcharts. However, it should be understood that these flowcharts and their corresponding descriptions are illustrative only for ease of understanding and should not constitute any limitation on this application. Not every step in each flowchart is necessarily required to be performed; for example, some steps can be skipped. Furthermore, the execution order of each step is not fixed and is not limited to what is shown in the figures. The execution order of each step should be determined by its function and internal logic.

[0101] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0102] The methods provided in the embodiments of this application are described in detail below with reference to the accompanying drawings.

[0103] It should be understood that the following description is for ease of understanding and explanation only, using the interaction between a terminal device and a network device as an example to illustrate the methods provided in the embodiments of this application. However, this should not constitute any limitation on the subject executing the methods provided in this application. For example, the terminal device shown in the embodiments below can be replaced by components (such as chips or circuits) configured in the terminal device. The network device shown in the embodiments below can also be replaced by components (such as chips or circuits) configured in the network device.

[0104] The embodiments shown below do not specifically limit the structure of the execution subject of the method provided in the embodiments of this application. As long as it is possible to communicate according to the method provided in the embodiments of this application by running a program that records the code of the method provided in the embodiments of this application, for example, the execution subject of the method provided in the embodiments of this application can be a terminal device or a network device, or a functional module in a terminal device or network device that can call and execute a program.

[0105] Figure 2 is a flowchart illustrating a SIP message transmission method according to an embodiment of this application. As shown in Figure 2, the communication method may include steps S201 to S203. The steps in Figure 2 are described in detail below.

[0106] S201. The terminal sends at least one SIP message template to the network side.

[0107] In some embodiments, the terminal may be the terminal that initiates the IMS session, or it may be referred to as the calling terminal.

[0108] In some embodiments, the network side can be a physical device that supports SIP, such as at least one of SIP PBX, IMS, SIP Proxy Server, etc., without specific limitations.

[0109] In some embodiments, a SIP message template includes at least some fields in a SIP message and a first preset value corresponding to each of the at least some fields.

[0110] In some embodiments, a SIP message template may include some or all of the fields in a SIP message, and the SIP message template may also include a first preset value corresponding to each field.

[0111] In some embodiments, the types of SIP messages include at least one of the following: INVITE message, PRACK message, UPDATE message, ACK message, BYE message, 183 Session Progress message, 180 Ringing message, and Session Description Protocol (SDP) message.

[0112] In some embodiments, the SIP message can be a different type of SIP message, and different types of SIP messages can correspond to different SIP message templates. For example, the SIP message can be an INVITE message, or the SIP message can be a PRACK message, etc. No specific restrictions are made here.

[0113] In some embodiments, a type of SIP message may correspond to at least one SIP message template, such as a type of SIP message corresponding to one SIP message template of the same type or corresponding to two or more SIP message templates of the same type.

[0114] In one embodiment, the SIP message is an INVITE message, and the number of SIP message templates corresponding to the INVITE message can be four, such as SIP message template 1, SIP message template 2, SIP message template 3, and SIP message template 4 corresponding to the INVITE message.

[0115] In one embodiment, the SIP message template includes at least some fields in the corresponding SIP message and a first preset value corresponding to each field in the at least some fields. For example, if the SIP message is an INVITE message, then the corresponding SIP message template includes at least some fields in the INVITE message and a first preset value corresponding to each field in the at least some fields included therein.

[0116] In some embodiments, at least some fields in the corresponding SIP message included in the SIP message template can be fields whose values ​​are fixed, that is, the first preset value corresponding to each field in the SIP message template can be the fixed value of the corresponding field.

[0117] In other embodiments, at least some fields included in the SIP message template can be fields whose values ​​are fixed in the corresponding SIP message. That is, the first preset value corresponding to each field in the SIP message template can be a fixed value in the corresponding SIP message, or the first preset value corresponding to each field in the SIP message template can be the default value of the corresponding field in the corresponding SIP message.

[0118] For scenarios where the SIP message is an INVITE message, at least some fields in the INVITE message included in the corresponding SIP message template are fields whose values ​​are fixed in the INVITE message. The first preset value of each field in the SIP message template is either the fixed value of the corresponding field in the INVITE message, or the first preset value of each field in the SIP message template is the default value of the corresponding field in the INVITE message.

[0119] For example, in scenarios where the SIP message is an INVITE message, the SIP message template corresponding to the INVITE message can include at least some of the following fields: From (indicating the initiator of the SIP message), P-Preferred-Identity (indicating the identity of the initiator of the SIP message), Accept-Contact (indicating the service instance or device capability that the terminal wishes to access), P-Preferred-Service (indicating the service type associated with the INVITE message), P-Early-Media (indicating whether the terminal supports early media), P-Access-Network-Info (indicating the network type accessed by the terminal), Supported (indicating the SIP extension functions supported by the terminal), Allow (indicating the SIP methods supported by the terminal), Accept (indicating the data types that the terminal is willing to accept), Session-Ex... The parameters are: pires (representing the lifespan of an IMS session), Min-SE (representing the minimum lifespan value of an IMS session), Route (representing which intermediate nodes the INVITE message should pass through for transmission), Require (representing the functionality that the INVITE message receiver must support), Proxy-Require (representing the functionality that intermediate proxy points for INVITE message transmission must support), Security-Verify (representing the security mechanism used for authentication), User-Agent (representing the user agent of the SIP message initiator), Max-Forwards (representing the maximum number of SIP proxies the INVITE message can pass through), Content-Type (representing the type of the INVITE message body), and Content-Length (representing the number of bytes). It is understandable that the SIP message template corresponding to the INVITE message may also include the first preset value for each field.

[0120] For example, in scenarios where the SIP message is an SDP message, the SIP message template corresponding to the SDP message can include at least some of the following fields: v=0 (representing the SDP version number), s= (representing the session name), b=AS (representing the application-specific bandwidth), b=RR / b=RS (representing the bandwidth declaration), m=audio (representing the media description line), a=rtpmap (representing the encoding method corresponding to the load type), a=fmtp (representing the parameter of a specific encoding format), a=maxptime (representing the maximum packet duration), a=sendrecv (representing the current media direction), a=curr:qos (representing the current quality of service status), a=des:qos (representing the expected quality of service status), t=0 0 (representing the time field); it can be understood that the SIP message template corresponding to the SIP message can also include the first preset value of the corresponding field.

[0121] It is understood that the fields included in the SIP message template corresponding to the SDP message and some fields included in the SIP message template corresponding to the INVITE message are only exemplary. In other embodiments, other fields may also be included, and no specific restrictions are made here.

[0122] In some embodiments, the fields included in a SIP message template may not be arranged according to the format of each field in a SIP message. That is, a message that includes at least some fields in a SIP message and a first preset value corresponding to each field in at least some fields may be called a SIP message template.

[0123] In some embodiments, the type of SIP message template corresponds to the type of SIP message, such as an INVITE message corresponding to a SIP message template with an INVITE message, and an ACK message corresponding to a SIP message template with an ACK message.

[0124] Understandably, for a given type of SIP message, the corresponding SIP message template includes at least some fields in the SIP message and the first preset value corresponding to each field in the at least some fields.

[0125] In some embodiments, each SIP message template in at least one SIP message template corresponds to at least one of the following: at least one network type, at least one network condition, at least one media type, and at least one codec type.

[0126] In some embodiments, the network type may include high-orbit satellite networks, medium-orbit satellite networks, low-orbit satellite networks, and terrestrial networks. For different network types, there may be corresponding SIP message templates. For example, a SIP message under a high-orbit satellite network corresponds to one SIP message template, a SIP message under a medium-orbit satellite network corresponds to one SIP message template, a SIP message under a low-orbit satellite network corresponds to one SIP message template, and a SIP message under a terrestrial network corresponds to one SIP message template. It is understood that the SIP message templates corresponding to different network types may be the same or different. For example, different SIP message templates may correspond to different network types. Alternatively, at least two network types may have at least one SIP message template corresponding to a SIP message; that is, one SIP message template may correspond to at least one network type.

[0127] For example, in some embodiments, network conditions may include poor channel conditions, medium channel conditions, and excellent channel conditions. Then, there may be corresponding SIP message templates for different network conditions. For example, a SIP message under poor channel conditions corresponds to one SIP message template, a SIP message under medium channel conditions corresponds to one SIP message template, and a SIP message under excellent channel conditions corresponds to one SIP message template. It can be understood that the SIP message templates corresponding to different network conditions may be the same or different. For example, different SIP message templates for SIP messages corresponding to different network conditions may exist. Alternatively, there may be at least one SIP message template for SIP messages corresponding to at least two network conditions in different network types. That is, one SIP message template may correspond to at least one network condition.

[0128] In some embodiments, the SIP message templates for SIP messages corresponding to different media types can be the same or different. For example, different SIP message templates for SIP messages corresponding to different network conditions can exist in different media types. Alternatively, at least one SIP message template can exist for at least two network conditions corresponding to SIP messages, that is, one SIP message template can correspond to at least one network condition.

[0129] In some embodiments, the SIP message templates of SIP messages corresponding to different codec types can be the same or different. For example, different SIP message templates of SIP messages corresponding to different codec types can exist in different network types, and at least one SIP message template of SIP messages corresponding to at least two codec types can exist. That is, one SIP message template can correspond to at least one codec type.

[0130] Understandably, at least one of the following can correspond to a SIP message template: a network condition, a network type, a media type, or a codec type. For example, a high-orbit satellite network with poor channel conditions can correspond to a SIP message template.

[0131] Understandably, each SIP message template in at least one SIP message template corresponds to at least one of at least one network type, at least one network condition, at least one media type, and at least one codec type. Similarly, the SIP message templates corresponding to different SIP messages also correspond to at least one of at least one of at least one network type, at least one network condition, at least one media type, and at least one codec type. For example, INVITE message, PRACK message, UPDATE message, ACK message, BYE message, 183 Session Progress message, 180 Ringing message, and SDP message correspond to at least one of at least one network type, at least one network condition, at least one media type, and at least one codec type, respectively.

[0132] For example, if the SIP message is an INVITE message, the number of SIP message templates corresponding to the INVITE message can be one or more, and the SIP message templates corresponding to the INVITE message correspond to at least one of the following: at least one network type, at least one network condition, at least one media type, and at least one codec type; or if the SIP message is an SDP message, the number of SIP message templates corresponding to the SDP message can be one or more, and the SIP message templates corresponding to the SDP message correspond to at least one of the following: at least one network type, at least one network condition, at least one media type, and at least one codec type.

[0133] In some embodiments, for a single SIP message, there are multiple SIP message templates, and the fields included in the different SIP message templates are different, and / or the first preset values ​​of the fields included in the different SIP message templates are different.

[0134] In some embodiments, the at least one SIP message template is carried in a SIP registration message.

[0135] In some embodiments, the SIP registration message includes the at least one SIP message.

[0136] In some embodiments, the at least one SIP message template is included in the SIP registration message.

[0137] In some embodiments, the terminal sends a SIP registration message to the network side, the SIP registration message including at least one SIP message template.

[0138] In some embodiments, the network side includes an IMS, and the terminal sends a SIP registration message to the IMS, the SIP registration message including at least one SIP message template.

[0139] In some embodiments, the IMS includes a P-CSCF, which receives at least one SIP message template from the terminal, meaning the network side includes the P-CSCF in the IMS.

[0140] In some embodiments, the fields in the SIP message template can be fields that have undergone mapping simplification. That is, for the fields in the SIP message, at least some of the fields in the SIP message can be mapped and simplified to obtain the fields after mapping simplification. In this way, signaling compression of the SIP message template can be realized, signaling redundancy during SIP message template transmission can be reduced, and the efficiency of SIP message template transmission can be improved.

[0141] When the SIP message is an INVITE message, the "From" field in the INVITE message can be simplified by mapping, and the simplified field is "F". This can reduce the signaling volume in the SIP message template.

[0142] S202, The terminal sends the first message to the network side.

[0143] In some embodiments, the first message includes a first field in the corresponding SIP message and a second preset value corresponding to the first field.

[0144] In some embodiments, the first message may be a SIP message, in which case the first message includes a first field in the SIP message and a second preset value corresponding to the first field. The first message may also not be a SIP message, but it also includes the first field in the SIP message and the second preset value corresponding to the first field.

[0145] In some embodiments, when the first message is a SIP message, the type of the SIP message corresponding to the first message can be determined. In this way, a SIP message template with the same SIP message type as the first message can be determined. Subsequently, the SIP message can be determined through the first message and the SIP message template of the corresponding SIP message type.

[0146] In some other embodiments, the first message is not a SIP message, but it includes a first field and a second preset value corresponding to the first field. The first message may also include a SIP message template that indicates the type of the SIP message corresponding to the first field. Thus, the SIP message can be determined by the first message and the SIP message template of the corresponding SIP message type.

[0147] The type of SIP message corresponding to the first field in the first message can be determined by the second preset value of a certain field in the first field, or by other information other than the first field and the second preset value. No specific restrictions are imposed here.

[0148] In some embodiments, the terminal sends a SIP message to the network side, and it only sends a first message. The first message includes some fields of the SIP message, namely the first field, which is a partial field of the SIP message.

[0149] In some embodiments, the first field may be different from the fields in the SIP message template.

[0150] In some embodiments, the first field may be the same as a field in the SIP message template. In this case, the second preset value of the field in the first field that is the same as the field in the SIP message template is different from the first preset value of the same field in the SIP message template.

[0151] In some embodiments, the first field includes fields that are different from those in the SIP message template.

[0152] In some embodiments, the first field includes the same field as the field in the SIP message template, and the same field has a second preset value that is different from the first preset value.

[0153] In some embodiments, a SIP message corresponds to multiple SIP message templates, and the first field in the first message may include at least one of the following: a field that is different from a field in at least one of the multiple SIP message templates; or a field that is the same as a field in at least one of the multiple SIP message templates.

[0154] In other embodiments, the first field may be a field used to indicate a first terminal identifier of the peer terminal.

[0155] The peer terminal is another terminal that is having an IMS session with the terminal. If the terminal is the calling terminal in the IMS session, then the peer terminal is the called terminal; if the terminal is the called terminal in the IMS session, then the peer terminal is the calling terminal.

[0156] Understandably, the field used to indicate the first terminal identifier of the peer terminal can be a field in the SIP message template, and the field used to indicate the first terminal identifier of the peer terminal can also be different from the field in the SIP message template.

[0157] Therefore, by setting the first field, you can add fields that do not exist in the SIP message template corresponding to the SIP message and the second preset value of the corresponding field. You can also modify the first preset value of the field that exists in the SIP message template corresponding to the SIP message to the second preset value by setting the first field.

[0158] In some embodiments, the values ​​of the first field and the first field are determined by the terminal based on at least one of network type, network quality, or service requirements.

[0159] In some embodiments, if the terminal determines that a field in the SIP message template needs to be modified based on at least one of network type, network quality, or service requirements, then the field that needs to be modified is identified as one of the first fields, and the modified value is identified as the second preset value of that field.

[0160] For example, if the network quality is congested or the network type changes, it may be necessary to adjust the first preset values ​​of some fields in the SIP message template, such as the values ​​of fields like b=AS, b=RR, b=RS, a=rtpmap, a=fmtp, and a=ptime in the SIP message template of the SDP message. In this case, the fields in the SIP message template that need to have their first preset values ​​adjusted are identified as at least some of the first fields, and the second preset values ​​of the fields that need to have their first preset values ​​adjusted are set.

[0161] For example, in some embodiments, if the terminal determines the value of a field that does not exist in the SIP message template based on at least one of network type, network quality, or service requirements, then the field that does not exist in the SIP message template is determined as a field in the first field, and the value of the field that does not exist in the SIP message template is determined as the second preset value of the corresponding field.

[0162] If the SIP message is an INVITE message, and the SIP message template corresponding to the INVITE message does not contain the fields Request-Line (representing the request line), To (representing the peer terminal), Contact (representing the location of the terminal), Call-ID (representing the unique identifier of the SIP session), CSeq9 (representing the sequence number and method name of the request), and Via (representing the path through which the request is made), then the fields Request-Line, To, Contact, Call-ID, CSeq, and Via will be determined as at least some of the fields in the first field, and the second preset value corresponding to the field will be set.

[0163] In some embodiments, the fields in the first message can be fields after mapping simplification. That is, for the fields in the first message, at least some fields in the first message can be mapped and simplified to obtain fields after mapping simplification. In this way, signaling compression of the first message can be realized, signaling redundancy during the transmission of the first message can be reduced, and the efficiency of the transmission of the first message can be improved.

[0164] In some embodiments, the first message is sent in response to the SIP message to be transmitted, that is, the first message may include at least one of the following: INVITE message, PRACK message, UPDATE message, ACK message, BYE message, 183 Session Progress message, 180 Ringing message, and SDP message.

[0165] In some embodiments, the network side can be an IMS, which includes a P-CSCF that receives the first message from the terminal.

[0166] In some embodiments, the network side can be a P-CSCF, which receives the first message from the terminal.

[0167] S203. The network side determines the SIP message based on at least one SIP message template and the first message.

[0168] In some embodiments, the network side can be IMS, which determines the SIP message based on at least one SIP message template and a first message.

[0169] In some embodiments, the IMS includes a P-CSCF, which determines a SIP message based on at least one SIP message template and a first message.

[0170] In some embodiments, the network side is a P-CSCF, which determines the SIP message based on at least one SIP message template and a first message.

[0171] In some embodiments, the first message includes a first field and a second preset value of the SIP message, and the SIP message template includes at least some fields of the SIP message and the first preset value. By combining the first message and the SIP message template, a SIP message can be obtained. In some embodiments, a SIP message template exists for each SIP message, and the SIP message template is combined with the first message to obtain the SIP message.

[0172] In some embodiments, if there are multiple SIP message templates corresponding to a SIP message, then a SIP message template can be determined from the multiple SIP message templates, and the determined SIP message template can be combined with the first message to obtain a SIP message.

[0173] In some embodiments, a SIP message template corresponds to a template identifier, that is, each SIP message template in at least one SIP message template corresponding to a SIP message has a template identifier.

[0174] It is understandable that for the same SIP message, different SIP message templates have different template identifiers, and for different SIP messages, the SIP message templates can be the same or different.

[0175] In some embodiments, the first message further includes a first template identifier. The network side determines the corresponding first message template in at least one SIP message template based on the first template identifier, and combines the first message and the first message template into a SIP message.

[0176] By using the first template identifier in the first message, the SIP message template whose template identifier is the first template identifier can be determined in at least one SIP message template corresponding to the SIP message, and the first message template can be obtained.

[0177] In some embodiments, the first message template contains at least some fields of a SIP message and at least some of the fields have first preset values. The first message includes a first field of a SIP message and second preset values ​​for each field in the first field. The first field includes at least one of the following: a field that is different from the field in the SIP message template and a field that is the same as the field in the SIP message template. Thus, by combining the fields in the first message template, the first preset values, the first field in the first message, and the second preset values, the corresponding SIP message can be determined.

[0178] In some embodiments, when combining the fields in the first message template, the first preset value, the first field in the first message, and the second preset value, for fields in the first field that are different from the fields in the first message template, the fields in the first field that are different from the fields in the first message template, as well as the second preset values ​​in each field, are aggregated with the fields in the first message template. For fields that are the same as the fields in the first message template, the first preset value of the same field in the first message template and the first field can be modified to the second preset value, thereby obtaining the SIP message.

[0179] It is understandable that when combining the fields in the first message template, the first preset value, the first field in the first message, and the second preset value to obtain a SIP message, the resulting SIP message conforms to the format of the corresponding SIP message.

[0180] In one embodiment, if the first field contains only fields that are different from the fields in the first message template, then the fields in the first field that are different from the fields in the first message template, as well as the second preset values ​​in each field, are aggregated with the fields in the first message template to obtain a SIP message.

[0181] In another embodiment, if the first field contains only fields that are identical to those in the first message template, then the first preset value of the identical fields in the first message template and the first field is modified to a second preset value, thereby obtaining a SIP message.

[0182] In another embodiment, if the first field contains only fields that are different from the fields in the first message template and also contains fields that are the same as the fields in the first message template, then the fields in the first field that are different from the fields in the first message template and the second preset values ​​in each field are aggregated with the fields in the first message template, and the first preset values ​​of the fields that are the same as the fields in the first field after aggregation are modified to the second preset values ​​to obtain a SIP message.

[0183] In some embodiments, the first template identifier may be determined by the terminal based on at least one of the following: network type, network conditions, codec type, and media type.

[0184] Understandably, since each SIP message template corresponds to at least one of at least one network type, at least one network condition, at least one codec type, and at least one media type, the terminal can determine the required SIP message template based on at least one of the network type, network condition, codec type, and media type it is in, and determine the template identifier of the required SIP message template as the first template identifier.

[0185] In some embodiments, each SIP message template in at least one SIP message template corresponds to at least one network type, and the first message also includes information for indicating the first network type to which the terminal is connected.

[0186] In some embodiments, the information used to indicate the first network type connected to the terminal may be the P-Access-Network-Info field and its corresponding second preset value.

[0187] In some embodiments, each SIP message template corresponds to at least one network type, and the first message also includes information indicating the first network type to which the terminal is connected. Thus, a corresponding second SIP message template can be determined from at least one SIP message template based on the information indicating the first network type to which the terminal is connected, and the first message and the second SIP message template can be combined into a SIP message.

[0188] In some embodiments, the second SIP message template contains at least some fields of the SIP message and at least some of the first preset values ​​of the fields. The first message includes the first field of the SIP message and the second preset values ​​of each field in the first field. The first field includes at least one of the fields that are different from the fields in the SIP message template and the fields that are the same as the fields in the SIP message template. Thus, by combining the fields in the second SIP message template, the first preset values, the first field in the first message, and the second preset values, the corresponding SIP message can be determined.

[0189] In some embodiments, when combining fields in the second SIP message template, the first preset value, the first field in the first message, and the second preset value, for fields in the first field that are different from fields in the second SIP message template, the fields in the first field that are different from fields in the second SIP message template, as well as the second preset values ​​in each field, are aggregated with the fields in the second SIP message template. For fields that are the same as fields in the second SIP message template, the first preset value of the same field in the second SIP message template and the first field can be modified to the second preset value, thereby obtaining the SIP message.

[0190] It is understandable that when combining the fields in the second SIP message template, the first preset value, the first field in the first message, and the second preset value to obtain a SIP message, the resulting SIP message conforms to the format of the corresponding SIP message.

[0191] In one embodiment, if the first field contains only fields that are different from the fields in the second SIP message template, then the fields in the first field that are different from the fields in the second SIP message template, as well as the second preset values ​​in each field, are aggregated with the fields in the second SIP message template to obtain a SIP message.

[0192] In another embodiment, if the first field contains only fields that are identical to those in the second SIP message template, then the first preset value of the identical fields in the second SIP message template and the first field is modified to a second preset value, thereby obtaining the SIP message.

[0193] In another embodiment, if the first field contains only fields that are different from the fields in the second SIP message template and also contains fields that are the same as the fields in the second SIP message template, then the fields in the first field that are different from the fields in the second SIP message template, as well as the second preset values ​​in each field, are aggregated with the fields in the second SIP message template. The first preset value of the field that is the same as the field in the first field after aggregation is modified to the second preset value to obtain the SIP message.

[0194] Understandably, in some embodiments, after a terminal sends a SIP message template, subsequent terminals that need to send SIP messages can simply send the first message. The network side can then determine the SIP message based on the SIP message template and the first message, thereby improving the efficiency of SIP message sending.

[0195] In some embodiments, the terminal pre-sends a SIP message template. When a SIP message needs to be sent subsequently, only the first message needs to be sent. The required SIP message can be obtained through the SIP message template and the first message. In this process, only the first message needs to be sent to realize the transmission of the SIP message. The first message may only include the first field and the second preset value in the SIP message, thereby reducing the number of fields that need to be sent when sending SIP messages, thereby reducing the size of the signaling that needs to be sent when sending SIP messages. This can adapt to scenarios with different communication link bandwidth resources, meet the requirements of high-capacity and low-latency communication of SIP messages, and improve the transmission efficiency and success rate of SIP messages.

[0196] Figure 3 is a flowchart illustrating a SIP message transmission method according to another embodiment of this application. As shown in Figure 3, the communication method may include steps S301 to S302. The steps in Figure 3 are described in detail below.

[0197] It is understood that the embodiment shown in Figure 3 can be implemented prior to the embodiment shown in Figure 2. Figure 3 shows that when the network side is IMS, the terminal can exchange information about IMS-supported SIP message templates with the core network.

[0198] S301. The terminal sends a request message to the core network to create an IMS connection.

[0199] In some embodiments, the terminal conducts an IMS session via IMS.

[0200] In some embodiments, the network side includes IMS, and the terminal conducts IMS sessions through IMS.

[0201] In some embodiments, the network side sends a request message to the core network to create an IMS connection, requesting to conduct an IMS session through IMS.

[0202] In some embodiments, when a terminal accesses the core network, a request message to create an IMS connection is sent to the core network.

[0203] In some embodiments, the core network can be a Public Land Mobile Network (PLMN) core network or a Non-Terrestrial Network (NTN) core network, without specific limitations.

[0204] S302. The core network sends information to the terminal to indicate that IMS supports SIP message templates.

[0205] In some embodiments, the network side is IMS, and the terminal can determine whether the IMS supports SIP message template information, and then send the SIP message template to the IMS.

[0206] In some embodiments, whether IMS has the capability to support SIP message templates can be determined by the information returned by the core network in response to the request message for creating an IMS connection.

[0207] In some embodiments, the core network sends information to the terminal indicating that IMS supports SIP message templates, and also sends the address information of the P-CSCF to the terminal. Subsequently, the terminal can conduct an IMS session through the address information of the P-CSCF.

[0208] In some embodiments, IMS has the capability to support SIP message templates, and the core network creates a response request message for the IMS connection and sends information to the terminal to indicate that IMS supports SIP message templates.

[0209] In some embodiments, the terminal receives information indicating that the IMS supports SIP message templates and may send at least one SIP message template to the IMS.

[0210] In some embodiments, after receiving information indicating that IMS supports SIP message templates, the terminal may send a SIP registration message to IMS, the SIP registration message including at least one SIP message template.

[0211] In some embodiments, the terminal receives information indicating that IMS supports SIP message templates and may send at least one SIP message template to the P-CSCF.

[0212] In some embodiments, when a terminal receives information indicating that IMS supports SIP message templates, it may send a SIP registration message to the P-CSCF, the SIP registration message including at least one SIP message template.

[0213] In one embodiment, in an LTE network, the request message for creating an IMS connection is a Packet Data Network (PDN) Connectivity Request message. The terminal sends a PDN Connectivity Request message to request the establishment of an IMS connection. This PDN Connectivity Request message contains information for requesting a P-CSCF address.

[0214] In its response to the PDN Connectivity Accept message, the core network returns the address of the P-CSCF and information indicating that IMS supports SIP message templates.

[0215] For example, in a 5G NR network, the request message for establishing an IMS connection is a Protocol Data Unit (PDU) Session Establishment Request message. The terminal requests to establish an IMS connection by sending a PDU Session Establishment Request message. This PDU Session Establishment Request message contains information for requesting a P-CSCF address.

[0216] In its response to the PDU Session Establishment Accept message, the core network returns the address of the P-CSCF and information indicating that IMS supports SIP message templates.

[0217] In some embodiments, if the core network does not send information to the terminal indicating that IMS supports SIP message templates, or if the core network sends information to the terminal indicating that IMS does not support SIP message templates, then the terminal will not send SIP message templates to IMS, or will not send SIP message templates through SIP registration messages.

[0218] Figure 4 is a flowchart illustrating a SIP message transmission method according to another embodiment of this application. As shown in Figure 4, the communication method may include steps S401 to S402. The steps in Figure 4 are described in detail below.

[0219] It is understood that the embodiments shown in Figure 4 may be implemented prior to the embodiments shown in Figure 2.

[0220] S401. The terminal sends a SIP registration message to the network side.

[0221] In some embodiments, the network side can be a physical device that supports SIP, such as at least one of SIP PBX, IMS, SIP Proxy Server, etc., without specific limitations.

[0222] In some embodiments, the SIP registration message includes information indicating that the terminal supports the SIP message template.

[0223] In some embodiments, the terminal informs the network side that it supports SIP message templates through information in the SIP registration message that indicates that the terminal supports SIP message templates.

[0224] In some embodiments, the network side can be IMS, which sends a SIP registration message to IMS before the terminal sends a SIP message template to IMS.

[0225] In some embodiments, the network side can be a P-CSCF, and the terminal sends a SIP registration message to the P-CSCF.

[0226] S402. The network-side terminal sends a SIP registration acceptance message, which includes information indicating that the network side supports SIP message templates.

[0227] In some embodiments, the information used to indicate that the network side supports SIP message templates may include information on the support of SIP message templates by different network-side entities. For example, if the network side includes at least one of IMS and P-CSCF, and P-CSCF is a network element in IMS, then the information used to indicate that the network side supports SIP message templates may include information used to indicate that IMS supports SIP message templates.

[0228] In some embodiments, the network side can be IMS, which sends a SIP registration acceptance message to the terminal.

[0229] In some embodiments, the network side can be IMS, and the IMS registration message includes information indicating that IMS supports SIP message templates.

[0230] In some embodiments, the network side can be a P-CSCF, which sends a SIP registration acceptance message to the terminal.

[0231] In some embodiments, the network side can be a P-CSCF, and the SIP registration accept message includes information indicating that IMS supports SIP message templates.

[0232] In some embodiments, the terminal receives information indicating that the network side supports SIP message templates, determines that the network side has the capability to support SIP message templates, and sends at least one SIP message template to the network side.

[0233] In some embodiments, the terminal receives information indicating that the IMS supports SIP message templates and sends at least one SIP message template to the IMS.

[0234] In some embodiments, the terminal receives information indicating that the P-CSCF supports SIP message templates and sends at least one SIP message template to the P-CSCF.

[0235] In some embodiments, the network side is either IMS or P-CSCF. If the SIP registration acceptance message does not include information indicating that IMS supports SIP message templates, and the core network does not send information indicating that IMS supports SIP message templates to the terminal, then the terminal does not send SIP message templates to IMS, or the terminal does not send at least one message template to P-CSCF.

[0236] In some embodiments, the network side is either IMS or P-CSCF. If the SIP registration acceptance message includes information indicating that IMS does not support SIP message templates, then the terminal does not send SIP message templates to IMS, or the terminal does not send at least one message template to P-CSCF.

[0237] In some embodiments, the network side is either IMS or P-CSCF. When a terminal receives at least one of the following: information from the core network indicating that IMS supports SIP message templates, or information from a SIP registration acceptance message indicating that IMS supports SIP message templates, it can send at least one SIP message template to IMS.

[0238] Understandably, in other embodiments, the network side may be other entities that support SIP. It may also determine whether other entities that support SIP support SIP message templates through signaling interaction. After determining that other entities that support SIP support SIP message templates, the terminal may send at least one SIP message template to the other entities that support SIP.

[0239] Figure 5 is a schematic flowchart illustrating a SIP message transmission method according to another embodiment of this application. It should be noted that the communication method in this embodiment is executed by the network side. This network side can be implemented by software and / or hardware. The network side is any entity device that supports SIP; it can be an IMS, or configured within an IMS, such as a Proxy-Call Session Control Function (P-CSCF) network element in the IMS, or other network elements capable of using the message transmission method provided in this disclosure.

[0240] As shown in Figure 5, the communication method may include steps S501 to S503. The steps in Figure 5 are described in detail below.

[0241] S501. Receive at least one SIP message template from the terminal, the SIP message template including at least some fields in the SIP message and a first preset value corresponding to each field in the at least some fields.

[0242] In some embodiments, the network side receives at least one SIP message template from the terminal.

[0243] In some embodiments, the network side includes an IMS, which receives at least one SIP message template from the terminal.

[0244] In some embodiments, the P-CSCF in the IMS receives at least one SIP message template from the terminal.

[0245] In some embodiments, the network side includes a P-CSCF, which receives at least one SIP message template from the terminal.

[0246] In some embodiments, the types of SIP messages include at least one of the following: INVITE message, PRACK message, UPDATE message, ACK message, BYE message, 183 Session Progress message, 180 Ringing message, and Session Description Protocol (SDP) message.

[0247] In some embodiments, a SIP message corresponds to at least one SIP message template.

[0248] Understandably, a type of SIP message corresponds to at least one SIP message template, meaning that a type of SIP message corresponds to at least one SIP message template.

[0249] In some embodiments, the correspondence between SIP messages and SIP message templates can be referred to the embodiments and related implementations disclosed in step S201 above, which will not be repeated here.

[0250] In some embodiments, the fields included in the SIP message template are at least some of the fields in the SIP message, and the SIP message template also includes a first preset value corresponding to each field, which is the default value corresponding to each field in the SIP message.

[0251] In some embodiments, the fields included in the SIP message template and the first preset values ​​corresponding to the fields can refer to the embodiments and related implementations disclosed in step S201 above, which will not be repeated here.

[0252] In some embodiments, each SIP message template in at least one SIP message template corresponds to at least one of the following: at least one network type, at least one network condition, at least one media type, and at least one codec type.

[0253] It is understandable that the correspondence between SIP message templates and network type, network condition, media type and codec type can be referred to the embodiments and related implementations disclosed in step S201 above, and will not be repeated here.

[0254] In some embodiments, at least one SIP message template is carried in a SIP registration message.

[0255] In some embodiments, the SIP registration message includes the at least one SIP message.

[0256] In some embodiments, the at least one SIP message template is included in the SIP registration message.

[0257] In some embodiments, at least one SIP message template can be sent separately to the network side after the terminal sends a SIP registration message to the network side.

[0258] In some embodiments, where the network side is IMS, at least one SIP message template can be sent separately to IMS after the terminal sends a SIP registration message to IMS.

[0259] In some embodiments, where the network side is IMS, at least one SIP message template can be sent separately to the P-CSCF in IMS after the terminal sends a SIP registration message to the P-CSCF in IMS.

[0260] In some embodiments, where the network side is a P-CSCF, at least one SIP message template can be sent separately to the P-CSCF in the IMS after the terminal sends a SIP registration message to the P-CSCF.

[0261] In some embodiments, the fields in a SIP message template can be fields that have undergone mapping simplification.

[0262] S502, Receive a first message from the terminal, the first message including a first field in the SIP message and a second preset value corresponding to the first field.

[0263] In some embodiments, the first field includes at least one of the following: a field that is different from a field in the SIP message template; or a field that is the same as a field in the SIP message template.

[0264] In some embodiments, if the first field contains a field that is identical to a field in the SIP message template, the second preset value of the field in the first field that is identical to the field in the SIP message template is different from the first preset value of the same field in the SIP message template.

[0265] In some embodiments, the first field includes only fields that are different from the fields in the SIP message template. These fields can compensate for fields in the SIP message template that are not present in the SIP message template. Thus, by combining the fields in the first message that are different from the fields in the SIP message template with the fields in the SIP message template, all fields in the SIP message can be obtained, as well as the first preset value or the second preset value corresponding to each field in each SIP message. This allows us to obtain the SIP message that the terminal wants to send to the network side.

[0266] In other embodiments, the first field includes only the fields that are the same as those in the SIP message template, but the second preset value corresponding to the fields that are the same as those in the SIP message template is different from the corresponding second preset value. Thus, by replacing the first preset value in the SIP message template with the second preset value of each field in the first message, the SIP message that the terminal wants to send to the network side can be obtained.

[0267] In other embodiments, the first field includes fields that are different from those in the SIP message template and fields that are the same as those in the SIP message template. Fields that are different from those in the SIP message template can compensate for fields of SIP messages that are not present in the SIP message template. Fields that are the same as those in the SIP message template have a second preset value. Replacing the first preset value in the SIP message template with the second preset value, the SIP message that the terminal wants to send to the network side can be obtained.

[0268] In some embodiments, the first field is a field used to indicate a first terminal identifier of the peer terminal.

[0269] When the first field is a field used to indicate the first terminal identifier of the peer terminal, the field used to indicate the first terminal identifier of the peer terminal may be the same as or different from a field in the SIP message template.

[0270] That is, the SIP message template may or may not contain the field used to indicate the first terminal identifier of the peer terminal.

[0271] It is understandable that the descriptions of the first field and the second preset value in the first message, the relationship between the first field and the fields in the SIP message template, and the relationship between the second preset value and the first preset value of the corresponding field in the SIP message template can be referred to the embodiments and related implementation methods disclosed in step S202 above, and will not be repeated here.

[0272] In some embodiments, the fields in the first message may be fields that have undergone mapping simplification.

[0273] S503. Determine the SIP message based on at least one SIP message template and the first message.

[0274] In some embodiments, the first message further includes a first template identifier, and one SIP message template corresponds to one template identifier. The network side determines the corresponding first message template in at least one SIP message template based on the first template identifier. The network side combines the first message and the first message template into a SIP message.

[0275] In some embodiments, the implementation method of determining the corresponding first message template in at least one SIP message template based on the first template identifier by the network side can refer to the embodiments and related implementation methods disclosed in step S203 above, which will not be repeated here.

[0276] In some embodiments, the implementation method of combining the first message and the first message template into a SIP message on the network side can refer to the embodiments and related implementation methods disclosed in step S203 above, which will not be repeated here.

[0277] In some embodiments, each SIP message template in at least one SIP message template corresponds to at least one network type, and the first message further includes information for indicating the first network type to which the terminal is connected; the network side determines the corresponding second SIP message template in at least one SIP message template based on the information for indicating the first network type to which the terminal is connected; the network side combines the first message and the second SIP message template into a SIP message.

[0278] In some embodiments, the implementation of determining the corresponding second SIP message template in at least one SIP message template based on information indicating the first network type of the terminal connection by the network side can be referred to the embodiments and related implementations disclosed in step S203 above, and will not be repeated here.

[0279] In some embodiments, the implementation method of combining the first message and the second SIP message template into a SIP message on the network side can refer to the embodiments and related implementation methods disclosed in step S203 above, which will not be repeated here.

[0280] In some embodiments, before sending at least one SIP message template to the network side, the terminal may first determine whether the network side supports SIP message templates.

[0281] In some embodiments, the network side is either IMS or P-CSCF. Before sending at least one SIP message template to IMS / P-CSCF, the terminal can first determine whether IMS supports SIP message templates.

[0282] In some embodiments, the network side receives a SIP registration message from the terminal, the SIP registration message including information indicating that the terminal supports SIP message templates; the network side sends a SIP registration acceptance message to the terminal, the SIP registration acceptance message including information indicating that the network side supports SIP message templates, and then the network side receives at least one SIP message template from the terminal.

[0283] In some embodiments, the network side is either IMS or P-CSCF. The IMS / P-CSCF receives a SIP registration message from the terminal, the SIP registration message including information indicating that the terminal supports SIP message templates. The IMS / P-CSCF sends a SIP registration acceptance message to the terminal, the SIP registration acceptance message including information indicating that the IMS supports SIP message templates. Then, the IMS / P-CSCF receives at least one SIP message template from the terminal.

[0284] It is understandable that the way the network side interacts with the terminal to indicate that the network side supports SIP message templates can be referred to the embodiments and related implementations disclosed in step S203 above, and will not be repeated here.

[0285] Understandably, the network side can use either IMS or P-CSCF. The network side does not interact with the terminal to indicate whether the network side supports SIP message templates. The terminal can interact with the core network to determine whether IMS supports SIP message templates.

[0286] It is understood that the way the IMS / P-CSCF interacts with the core network to indicate that the IMS supports SIP message templates can be referred to the embodiments and related implementations disclosed in steps S203 and S503 above, and will not be repeated here.

[0287] In this embodiment, the network side first receives the SIP message template sent by the terminal. When the terminal sends a SIP message later, it does not need to send the complete SIP message. For example, it can send fields that do not exist in the SIP message template and the second preset value of the corresponding fields, or send fields that exist in the SIP message template but whose corresponding first preset value needs to be modified and the second preset value of the corresponding fields. This reduces the signaling size of SIP message transmission, can adapt to different channel conditions, and ensures the reliability of SIP message transmission.

[0288] Figure 6 is a schematic flowchart illustrating a SIP message transmission method according to another embodiment of this application. It should be noted that the communication method in this embodiment is executed by a communication device. This communication device can be implemented by software and / or hardware. The communication device can be a terminal, or configured within a terminal.

[0289] As shown in Figure 6, the communication method may include steps S601 to S602. The steps in Figure 6 are described in detail below.

[0290] S601. Send at least one SIP message template to the network side. The SIP message template includes at least some fields in the SIP message and a first preset value corresponding to each field in the at least some fields.

[0291] In some embodiments, the network side can be a physical device that supports SIP, such as at least one of SIP PBX, IMS, SIP Proxy Server, etc., without specific limitations.

[0292] In some embodiments, the network side includes IMS, and the terminal sends at least one SIP message template to the IMS.

[0293] In some embodiments, the terminal sends at least one SIP message template to the P-CSCF in the IMS.

[0294] In some embodiments, the network side includes a P-CSCF, and the terminal sends at least one SIP message template to the P-CSCF.

[0295] In some embodiments, the types of SIP messages include at least one of the following: INVITE message, PRACK message, UPDATE message, ACK message, BYE message, 183 Session Progress message, 180 Ringing message, and Session Description Protocol (SDP) message.

[0296] In some embodiments, a SIP message corresponds to at least one SIP message template.

[0297] In some embodiments, the correspondence between SIP messages and SIP message templates can be referred to the embodiments and related implementations disclosed in steps S201 and S501 above, which will not be repeated here.

[0298] In some embodiments, the fields included in the SIP message template are at least some of the fields in the SIP message, and the SIP message template also includes a first preset value corresponding to each field, which is the default value corresponding to each field in the SIP message.

[0299] In some embodiments, the first preset value corresponding to the fields included in the SIP message template can be referred to the embodiments and related implementations disclosed in steps S201 and S501 above, and will not be repeated here.

[0300] In some embodiments, each SIP message template in at least one SIP message template corresponds to at least one of the following: at least one network type, at least one network condition, at least one media type, and at least one codec type.

[0301] It is understandable that the correspondence between SIP message templates and network type, network conditions, media type and codec type can be referred to the embodiments and related implementations disclosed in steps S201 and S501 above, and will not be repeated here.

[0302] In some embodiments, at least one SIP message template is carried in a SIP registration message.

[0303] In some embodiments, the SIP registration message includes the at least one SIP message.

[0304] In some embodiments, the at least one SIP message template is included in the SIP registration message. In some embodiments, when sending a SIP registration message, the terminal carries at least one SIP message template in the SIP registration message and sends it to the network side.

[0305] In some embodiments, the network side is IMS, and when the terminal sends a SIP registration message, it carries at least one SIP message template in the SIP registration message and sends it to the IMS.

[0306] In some embodiments, after the terminal sends a SIP registration message to the network side, it sends at least one SIP message template to the network side separately.

[0307] In some embodiments, the network side is IMS. After the terminal sends a SIP registration message to the IMS, it sends at least one SIP message template to the IMS separately.

[0308] In some embodiments, after the terminal sends a SIP registration message to the P-CSCF, it sends at least one SIP message template to the P-CSCF separately.

[0309] In some embodiments, the network side is a P-CSCF. After the terminal sends a SIP registration message to the P-CSCF, it sends at least one SIP message template to the P-CSCF separately.

[0310] In some embodiments, the fields in a SIP message template can be fields that have undergone mapping simplification.

[0311] S602. Send a first message to the network side. The first message includes the first field in the SIP message and the second preset value corresponding to the first field.

[0312] In some embodiments, the first field may include one or more fields.

[0313] In some embodiments, the first field includes fields that are different from those in the SIP message template.

[0314] In some embodiments, the first field includes a field that is identical to a field in the SIP message template, and the identical field has a second preset value that is different from the first preset value. In some embodiments, the first field includes at least one of the following: a field that is different from a field in the SIP message template; a field that is identical to a field in the SIP message template.

[0315] In some embodiments, if the first field contains a field that is identical to a field in the SIP message template, the second preset value of the field in the first field that is identical to the field in the SIP message template is different from the first preset value of the same field in the SIP message template.

[0316] In some embodiments, the first field includes only fields that are different from the fields in the SIP message template. These fields can compensate for fields in the SIP message template that are not present in the SIP message template. Thus, by combining the fields in the first message that are different from the fields in the SIP message template with the fields in the SIP message template, all fields in the SIP message can be obtained, as well as the first preset value or the second preset value corresponding to each field in each SIP message. This allows us to obtain the SIP message that the terminal wants to send to the network side.

[0317] In other embodiments, the first field includes only the fields that are the same as those in the SIP message template, but the second preset value corresponding to the fields that are the same as those in the SIP message template is different from the corresponding second preset value. Thus, by replacing the first preset value in the SIP message template with the second preset value of each field in the first message, the SIP message that the terminal wants to send to the network side can be obtained.

[0318] In other embodiments, the first field includes fields that are different from those in the SIP message template and fields that are the same as those in the SIP message template. Fields that are different from those in the SIP message template can compensate for fields of SIP messages that are not present in the SIP message template. Fields that are the same as those in the SIP message template have a second preset value. Replacing the first preset value in the SIP message template with the second preset value, the SIP message that the terminal wants to send to the network side can be obtained.

[0319] In some embodiments, the first field is a field used to indicate a first terminal identifier of the peer terminal.

[0320] When the first field is a field used to indicate the first terminal identifier of the peer terminal, the field used to indicate the first terminal identifier of the peer terminal may be the same as or different from a field in the SIP message template.

[0321] That is, the SIP message template may or may not contain the field used to indicate the first terminal identifier of the peer terminal.

[0322] It is understandable that the descriptions of the first field and the second preset value in the first message, the relationship between the first field and the fields in the SIP message template, and the relationship between the second preset value and the first preset value of the corresponding field in the SIP message template can be referred to the embodiments and related implementations disclosed in steps S202 and S502 above, and will not be repeated here.

[0323] In some embodiments, the values ​​of the first field and the first field are determined by the terminal based on at least one of network type, network quality, or service requirements.

[0324] It is understandable that the determination of the first field and its value based on at least one of network type, network quality, or service requirements by the terminal can refer to the embodiments and related implementations disclosed in step S202 above, which will not be repeated here.

[0325] In some embodiments, the fields in the first message may be fields that have undergone mapping simplification.

[0326] In some embodiments, the first template is identified by the terminal based on at least one of network type or network condition, and a SIP message template corresponds to at least one of at least one network type or at least one of at least one network condition.

[0327] In some embodiments, the first message further includes a first template identifier, and one SIP message template corresponds to one template identifier. The network side determines the corresponding first message template in at least one SIP message template based on the first template identifier. The network side combines the first message and the first message template into a SIP message.

[0328] In some embodiments, the implementation method of determining the corresponding first message template in at least one SIP message template based on the first template identifier by the network side can refer to the embodiments and related implementation methods disclosed in step S203 above, which will not be repeated here.

[0329] In some embodiments, the implementation of combining the first message and the first message template into a SIP message on the network side can refer to the embodiments and related implementations disclosed in steps S203 and S503 above, and will not be repeated here.

[0330] In some embodiments, each SIP message template in at least one SIP message template corresponds to at least one network type, and the first message further includes information for indicating the first network type to which the terminal is connected; the network side determines the corresponding second SIP message template in at least one SIP message template based on the information for indicating the first network type to which the terminal is connected; the network side combines the first message and the second SIP message template into a SIP message.

[0331] In some embodiments, the implementation of the network side determining the corresponding second SIP message template in at least one SIP message template based on information indicating the first network type of the terminal connection can be referred to the embodiments and related implementations disclosed in steps S203 and S503 above, and will not be repeated here.

[0332] In some embodiments, the implementation method of combining the first message and the second SIP message template into a SIP message on the network side can refer to the embodiments and related implementation methods disclosed in steps S203 and S503 above, which will not be repeated here.

[0333] In this embodiment, before sending a SIP message to the network side, the terminal can first send a SIP message template to the network side. The SIP message template may include at least some fields of the SIP message and the first preset value corresponding to each field. When the terminal sends a SIP message to the network side later, it may only send the first message, which includes the first field of the SIP message. At this time, the first message may not include the fields already sent in the SIP message template, or it may not include the fields already sent in the SIP message template whose first preset values ​​remain unchanged, thereby reducing the number of fields sent in the first message and reducing the signaling size required when sending the SIP message. The network side can then obtain the SIP message based on the first message and the SIP message template, thereby improving the efficiency of SIP message sending.

[0334] In some embodiments, before sending at least one SIP message template to the network side, the terminal may first determine whether the network side supports SIP message templates.

[0335] In some embodiments, the network side is at least one of IMS and P-CSCF. Before sending at least one SIP message template to IMS / P-CSCF, the terminal may first determine whether IMS supports SIP message templates.

[0336] In some embodiments, the network side receives a SIP registration message from the terminal, the SIP registration message including information indicating that the terminal supports SIP message templates; the network side sends a SIP registration acceptance message to the terminal, the SIP registration acceptance message including information indicating that the network side supports SIP message templates, and then the network side receives at least one SIP message template from the terminal.

[0337] In some embodiments, the network side is at least one of IMS and P-CSCF. The IMS / P-CSCF receives a SIP registration message from the terminal, the SIP registration message including information indicating that the terminal supports SIP message templates; sends a SIP registration acceptance message to the terminal, the SIP registration acceptance message including information indicating that the IMS supports SIP message templates; and then the IMS / P-CSCF receives at least one SIP message template from the terminal.

[0338] It is understandable that the way the network side interacts with the terminal to indicate that the network side supports SIP message templates can be referred to the embodiments and related implementations disclosed in steps S203 and S503 above, and will not be repeated here.

[0339] Understandably, the network side consists of at least one of IMS and P-CSCF. The network side does not interact with the terminal, but the terminal can interact with the core network to determine whether IMS supports SIP message templates.

[0340] In some embodiments, when a terminal accesses the core network, the terminal sends a request message to the core network to create an IMS connection; the terminal receives information from the core network indicating that the IMS supports SIP message templates, and then the terminal sends at least one SIP message template to the IMS / P-CSCF.

[0341] In some embodiments, the terminal can interact with the core network and, after determining that IMS supports SIP message templates, can send at least one SIP message template to IMS / P-CSCF in a SIP registration message.

[0342] It is understood that the way the IMS / P-CSCF interacts with the core network to indicate that the IMS supports SIP message templates can be referred to the embodiments and related implementations disclosed in steps S203 and S503 above, and will not be repeated here.

[0343] Figure 7 is a schematic block diagram of a SIP message transmission device according to an embodiment of this application. As shown in Figure 7, the SIP message transmission device 700 may include a receiving module 701 and a processing module 702.

[0344] In one embodiment, the SIP message transmission device 700 can be used to implement the network-side operations in the above embodiments, such as implementing the operations corresponding to at least one of IMS and P-CSCF in the above embodiments. The SIP message transmission device 700 is a network-side device. For example, the SIP message transmission device 700 is an IMS, or a component configured in the IMS, such as a chip or circuit; or, for another example, the SIP message transmission device 700 is a P-CSCF, or a component configured in the P-CSCF, such as a chip or circuit.

[0345] The SIP message transmission device 700 can implement the corresponding network-side operations, such as the corresponding operations of IMS or P-CSCF, in the embodiments of the SIP message transmission methods shown in Figures 2 to 6. The SIP message transmission device 700 may include modules for executing the methods executed on the network side in the embodiments of the SIP message transmission methods shown in Figures 2 to 6, such as modules for executing methods executed by IMS or P-CSCF. Furthermore, each module in the SIP message transmission device 700 and the other operations and / or functions described above are respectively for implementing the corresponding processes in the embodiments of the SIP message transmission methods shown in Figures 2 to 6.

[0346] In some embodiments, the receiving module 701 is configured to receive at least one SIP message template from a terminal, the SIP message template including at least some fields in the SIP message and a first preset value corresponding to each field in the at least some fields.

[0347] In some embodiments, the receiving module 701 is further configured to receive a first message from the terminal, the first message including a first field in a SIP message and a second preset value corresponding to the first field.

[0348] In some embodiments, the processing module 702 is configured to determine a SIP message based on at least one SIP message template and a first message.

[0349] In some embodiments, the types of SIP messages include at least one of the following: INVITE message, PRACK message, UPDATE message, ACK message, BYE message, 183 Session Progress message, 180 Ringing message, and SDP message.

[0350] In some embodiments, a SIP message corresponds to at least one SIP message template.

[0351] In some embodiments, the first field includes fields that are different from those in the SIP message template.

[0352] In some embodiments, the first field includes a field that is identical to a field in the SIP message template, and the identical field has a second preset value that is different from the first preset value. In some embodiments, the first field includes at least one of the following: a field that is different from a field in the SIP message template, and a field that is identical to a field in the SIP message template.

[0353] Where, if there is a field in the first field that is the same as a field in the SIP message template, the second preset value of the field in the first field that is the same as the field in the SIP message template is different from the first preset value of the same field in the SIP message template.

[0354] In some embodiments, the first field is a field used to indicate a first terminal identifier of the peer terminal.

[0355] In some embodiments, the first message may also include a first template identifier, and one SIP message template corresponds to one template identifier.

[0356] In some embodiments, the processing module 702 is further configured to determine the corresponding first message template in at least one SIP message template based on the first template identifier.

[0357] The processing module 702 is also used to combine the first message and the first message template into a SIP message.

[0358] In some embodiments, each SIP message template in at least one SIP message template corresponds to at least one of the following: at least one network type, at least one network condition, at least one media type, and at least one codec type.

[0359] In some embodiments, each SIP message template in at least one SIP message template corresponds to at least one network type, and the first message also includes information for indicating the first network type to which the terminal is connected.

[0360] In some embodiments, the processing module 702 is further configured to determine a corresponding second SIP message template in at least one SIP message template based on information indicating a first network type for terminal connection.

[0361] The processing module 702 is also used to combine the first message and the second SIP message template into a SIP message.

[0362] In some embodiments, at least one SIP message template is included in the SIP registration message.

[0363] In some embodiments, the receiving module is further configured to receive a SIP registration message from the terminal, the SIP registration message including information indicating that the terminal supports SIP message templates.

[0364] In some embodiments, the SIP message transmission device 700 further includes a sending module, which is configured to send a SIP registration acceptance message to a terminal. The SIP registration acceptance message includes information indicating that the network side supports the SIP message template.

[0365] In some embodiments, the fields in at least one of the SIP message templates and the first message are fields that have undergone mapping simplification.

[0366] In some embodiments, the network side includes the Internet Protocol Multimedia Subsystem (IMS).

[0367] Figure 8 is a schematic block diagram of a SIP message transmission apparatus according to another embodiment of this application. As shown in Figure 8, the SIP message transmission apparatus 800 may include a sending module 801.

[0368] In one embodiment, the SIP message transmission device 800 can be used to implement the operations corresponding to the terminal in the above embodiments. For example, the SIP message transmission device 800 is a terminal, or a component configured in the terminal, such as a chip or circuit.

[0369] The SIP message transmission device 800 can implement the corresponding operations of the terminal in the embodiments of the SIP message transmission method shown in Figures 2 to 6. The SIP message transmission device 800 may include modules for executing the methods performed by the terminal in the embodiments of the SIP message transmission method shown in Figures 2 to 6. Furthermore, each module in the SIP message transmission device 800 and the other operations and / or functions described above are respectively for implementing the corresponding processes in the embodiments of the SIP message transmission method shown in Figures 2 to 6.

[0370] In some embodiments, the sending module 801 is configured to send at least one SIP message template to the network side. The SIP message template includes at least some fields in the corresponding SIP message and a first preset value corresponding to each field in the at least some fields.

[0371] In some embodiments, the sending module 801 is further configured to send a first message to the network side, the first message including a first field in the corresponding SIP message and a second preset value corresponding to the first field.

[0372] In some embodiments, the types of SIP messages include at least one of the following: INVITE message, PRACK message, UPDATE message, ACK message, BYE message, 183 Session Progress message, 180 Ringing message, and SDP message.

[0373] In some embodiments, a SIP message corresponds to at least one SIP message template.

[0374] In some embodiments, the first field includes fields that are different from those in the SIP message template.

[0375] In some embodiments, the first field includes a field that is identical to a field in the SIP message template, and the identical field has a second preset value that is different from the first preset value. In some embodiments, the first field includes at least one of the following: a field that is different from a field in the SIP message template, and a field that is identical to a field in the SIP message template.

[0376] Where, if there is a field in the first field that is the same as a field in the SIP message template, the second preset value of the field in the first field that is the same as the field in the SIP message template is different from the first preset value of the same field in the SIP message template.

[0377] In some embodiments, the first field is a field used to indicate a first terminal identifier of the peer terminal.

[0378] In some embodiments, the values ​​of the first field and the first field are determined by the terminal based on at least one of network type, network quality, or service requirements.

[0379] In some embodiments, the first message may also include a first template identifier, and one SIP message template corresponds to one template identifier.

[0380] In some embodiments, the first template is identified by the terminal based on at least one of network type or network condition, and a SIP message template corresponds to at least one of at least one network type or at least one of at least one network condition.

[0381] In some embodiments, each SIP message template in at least one SIP message template corresponds to at least one of the following: at least one network type, at least one network condition, at least one media type, and at least one codec type.

[0382] In some embodiments, each SIP message template in at least one SIP message template corresponds to at least one network type, and the first message also includes information for indicating the first network type to which the terminal is connected.

[0383] In some embodiments, the sending module 801 is further configured to send a SIP registration message to the IMS, the SIP registration message including information indicating that the terminal supports SIP message templates.

[0384] The receiving module is also used to receive SIP registration acceptance messages from IMS, which include information indicating that the network side supports SIP message templates.

[0385] In some embodiments, the network side includes IMS.

[0386] In some embodiments, the network side includes a proxy call session control function (P-CSCF) network element.

[0387] In some embodiments, the sending module 801 is further configured to send a request message to the core network to create an IMS connection when the terminal accesses the core network.

[0388] In some embodiments, the SIP message transmission apparatus 800 further includes a receiving module for receiving information from the core network indicating that IMS supports SIP message templates.

[0389] In some embodiments, at least one SIP message template is included in the SIP registration message.

[0390] In some embodiments, the network side includes the IMS P-CSCF and a sending module, which is also used to send at least one SIP message template to the IMS Proxy Call Session Control Function network element P-CSCF.

[0391] In some embodiments, the network side includes a proxy call session control function (P-CSCF) network element and a sending module, which is also used to send a first message to the IMS's P-CSCF.

[0392] In some embodiments, the fields in at least one of the SIP message templates and the first message are fields that have undergone mapping simplification.

[0393] Figure 9 is a schematic block diagram of a communication device according to an embodiment of this application. As shown in Figure 9, the communication device 900 can be a network side, such as IMS, P-CSCF, etc., without specific limitations here, and can also be a terminal. The communication device 900 can be used to implement the methods described in the above method embodiments, and for details, please refer to the description in the above method embodiments.

[0394] The communication device 900 includes a processor 91 and a memory 92 that is communicatively connected to the processor 91.

[0395] Memory 92 is used to store computer-executed instructions.

[0396] The processor 91 is used to execute the computer execution instructions stored in the memory, so that the communication device 900 performs the above method.

[0397] In some embodiments, the communication device 900 may further include a transceiver 93, which may include a transmitter and / or a receiver. The transmitter may also be referred to as a transmitter, transmitter, transmitting port, or transmitting interface, and the receiver may also be referred to as a receiver, receiving port, or receiving interface, etc. Exemplarily, the memory 92, the processor 91, and the transceiver 93 are interconnected via a bus 94.

[0398] The processor 90 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0399] In some embodiments, all or part of the memory 92 may also be located outside the communication device 900.

[0400] In some embodiments, the communication device 900 is a terminal, and the terminal includes: a processor and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the SIP message transmission method executed by the terminal as described above.

[0401] In some embodiments, the communication device 900 is a network side, which includes: a processor and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the SIP message transmission method executed by the network side as described above.

[0402] In some embodiments, if the communication device 900 is an IMS, then the IMS includes: a processor, and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the SIP message transmission method performed by the IMS as described above.

[0403] In some embodiments, the communication device 900 is a P-CSCF, which includes: a processor and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the SIP message transmission method performed by the P-CSCF as described above.

[0404] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the SIP message transmission method shown in any of the above embodiments.

[0405] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the SIP message transmission method shown in any of the above embodiments.

[0406] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0407] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for transmitting a Session Initiation Protocol (SIP) message, applied to a network side, and characterized in that, The method comprises: receiving at least one SIP message template from a terminal, the SIP message template comprising at least part of fields in a SIP message and first preset values corresponding to each of the at least part of fields; receiving a first message from the terminal, the first message comprising a first field in the SIP message and a second preset value corresponding to the first field; determining the SIP message based on the at least one SIP message template and the first message.

2. The method of claim 1, wherein, The type of the SIP message comprises at least one of: a call request INVITE message; a proxy acknowledgement PRACK message; an update UPDATE message; a response ACK message; a session termination BYE message; a temporary response 183 Session Progress message; a ringing 180 Ringing message; a session description protocol SDP message.

3. The method according to claim 1 or 2, characterized in that, The SIP message corresponds to at least one SIP message template.

4. The method according to any one of claims 1 to 3, characterized in that, The first field comprises a field different from a field in the SIP message template.

5. The method according to any one of claims 1 to 4, characterized in that, The first field comprises a same field as a field in the SIP message template, and the same field has a second preset value different from the first preset value.

6. The method according to any one of claims 1 to 5, characterized in that, The first field is a field for indicating a first terminal identifier of a peer terminal.

7. The method according to any one of claims 1 to 6, characterized in that, The first message further comprises a first template identifier, and one SIP message template corresponds to one template identifier. The determining the SIP message based on the at least one SIP message template and the first message comprises: determining a corresponding first message template in the at least one SIP message template based on the first template identifier; and combining the first message and the first message template into the SIP message.

8. The method according to any one of claims 1 to 7, characterized in that, Each of the at least one SIP message template corresponds to at least one of: at least one network type; at least one network condition; at least one media type; and at least one codec type.

9. The method according to any one of claims 1 to 7, characterized in that, Each of the at least one SIP message template corresponds to at least one network type, and the first message further comprises information for indicating a first network type to which the terminal is connected. The determining the SIP message based on the at least one SIP message template and the first message comprises: determining a corresponding second SIP message template in the at least one SIP message template based on the information for indicating the first network type to which the terminal is connected; and combining the first message and the second SIP message template into the SIP message.

10. The method according to any one of claims 1 to 9, characterized in that, The at least one SIP message template is contained in a SIP registration message.

11. The method according to any one of claims 1 to 9, characterized in that, Before the receiving at least one SIP message template from a terminal, the method further comprises: receiving a SIP registration message from the terminal, the SIP registration message comprising information for indicating that the terminal supports SIP message templates; sending a SIP registration acceptance message to the terminal, the SIP registration acceptance message comprising information for indicating that the network side supports SIP message templates.

12. The method according to any one of claims 1 to 11, characterized in that, The field in at least one of the SIP message template and the first message is a field after simplification processing.

13. The method according to any one of claims 1 to 12, characterized in that, The network side comprises an Internet Protocol Multimedia Subsystem (IMS).

14. A SIP message transmission method applied to a terminal, characterized in that, The method comprises: sending at least one SIP message template to a network side, the SIP message template comprising at least part of fields in a SIP message and first preset values corresponding to the fields; sending a first message to the network side, the first message comprising a first field in the SIP message and a second preset value corresponding to the first field.

15. The method of claim 14, wherein, The type of the SIP message comprises at least one of: an INVITE message; a PRACK message; an UPDATE message; an ACK message; a BYE message; a 183 Session Progress message; a 180 Ringing message; an SDP message.

16. The method according to claim 14 or 15, characterized in that The SIP message corresponds to at least one SIP message template.

17. The method according to any one of claims 14-16, characterized by, The first field comprises a field different from the field in the SIP message template.

18. The method according to any one of claims 14-17, characterized by, The first field comprises a same field as the field in the SIP message template, and the same field has a second preset value different from the first preset value.

19. The method according to any one of claims 14-18, characterized by, The first field is a field for indicating a first terminal identifier of a peer terminal.

20. The method according to any one of claims 14-19, characterized by, The first field and the value of the first field are determined by the terminal according to at least one of a network type, a network quality or a service requirement.

21. The method according to any one of claims 14-20, characterized by, The first message further comprises a first template identifier, and one SIP message template corresponds to one template identifier.

22. The method of claim 21, wherein, The first template identifier is determined by the terminal according to at least one of a network type or a network condition, and one SIP message template corresponds to at least one of at least one network type or at least one network condition.

23. The method according to any one of claims 14-20, characterized by, Each of the at least one SIP message template corresponds to at least one of: at least one network type; at least one network condition; at least one media type; at least one codec type.

24. The method according to any one of claims 14-22, characterized by, Each of the at least one SIP message template corresponds to at least one network type, and the first message further comprises information for indicating a first network type to which the terminal is connected.

25. The method according to any one of claims 14-24, characterized by, Before the step of sending at least one SIP message template to the network side, the method further comprises: sending a SIP registration message to the network side, the SIP registration message comprising information for indicating that the terminal supports SIP message templates; receiving a SIP registration acceptance message from the network side, the SIP registration acceptance message comprising information for indicating that the network side supports SIP message templates.

26. The method of any one of claims 14-24, wherein, The network side comprises an IMS.

27. The method of any one of claims 14-24, wherein, The network side comprises a Proxy Call Session Control Function (P-CSCF).

28. The method of claim 26 or 27, wherein, Before the step of sending at least one SIP message template to the network side, the method further comprises: in a case where the terminal accesses to a core network, sending a request message for creating an IMS connection to the core network; receiving information from the core network for indicating that the IMS supports SIP message templates.

29. The method of any one of claims 14-24 or 26-28, wherein, The at least one SIP message template is contained in a SIP registration message.

30. The method of any one of claims 14-29, wherein, The field in at least one of the SIP message template, the first message is a field after simplifying mapping processing.

31. A SIP message transmission apparatus applied to a network side, characterized in that, The apparatus comprises: a receiving module configured to receive at least one SIP message template from a terminal, the SIP message template comprising at least part of fields in a SIP message and a first preset value corresponding to each field in the at least part of fields; the receiving module is further configured to receive a first message from the terminal, the first message comprising a first field in a SIP message and a second preset value corresponding to the first field; a processing module configured to determine the SIP message based on the at least one SIP message template and the first message.

32. A SIP message transmission apparatus applied to a terminal, characterized by comprising: The apparatus comprises: a sending module configured to send at least one SIP message template to a network side, the SIP message template comprising at least part of fields in a SIP message and a first preset value corresponding to each field in the at least part of fields; the sending module is further configured to send a first message to the network side, the first message comprising a first field in a SIP message and a second preset value corresponding to the first field.

33. A communications device, comprising: comprise: a processor, and a memory connected with the processor in communication; the memory stores computer execution instructions; the processor executes the computer execution instructions stored in the memory to implement the method according to any one of claims 1-13.

34. A communications device, comprising: comprise: a processor, and a memory connected with the processor in communication; the memory stores computer execution instructions; the processor executes the computer execution instructions stored in the memory to implement the method according to any one of claims 14-30.

35. A computer readable storage medium, characterized in that, The computer readable storage medium stores computer execution instructions, and the computer execution instructions are executed by the processor to implement the method according to any one of claims 1-30.

36. A computer program product, characterised in that, comprise a computer program, and the computer program is executed by the processor to implement the method according to any one of claims 1-30.