Communication method and apparatus and computer readable storage medium

Abstract

The present application provides a communication method and apparatus and a computer readable storage medium. The communication method comprises: sending / receiving compressed session initialization protocol (SIP) signaling, wherein the compressed SIP signaling does not carry one or more of the following information: a first field that is identical across all calls, a second field that is repeated in other pieces of signaling, and a non-essential field. Therefore, a solution of compressing SIP signaling, reducing the complexity of a terminal device and improving the compression efficiency is provided.

Description

Communication method and device, and computer-readable storage medium

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on March 28, 2024, with application number 202410373077.7 and invention name “Communication method and device, computer-readable storage medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a communication method and device, and a computer-readable storage medium. Background Art

[0003] In narrowband networks, signaling protocols based on the Internet Protocol (IP) face bandwidth limitations. Text-based multimedia communication application layer protocols like the Session Initialization Protocol (SIP) and Session Description Protocol (SDP) have long signaling lengths, consuming significant bandwidth and resulting in lengthy call setup times, severely impacting user experience. Therefore, reducing SIP signaling length is the only way to minimize signaling latency and complete call setup in a shorter time.

[0004] In the prior art, there are multiple methods for reducing the length of SIP signaling, with signaling compression being a common approach. To address the issue of SIP compression, the Internet Engineering Task Force (IETF) developed the Signaling Compression (SigComp) standard (the compression standard specified in RFC3320). The basic process of the SipComp compression method is as follows: when sending an uplink SIP message, the application layer's SIP message is first sent to the compression scheduling module, then processed by the corresponding compression module based on the group identifier, resulting in a SigComp message. The compression scheduling module then sends the message to the transport layer, and finally to the network end. When receiving a downlink SIP message, the transport layer sends the received SigComp message to the decompression scheduling module, which then calls the UDVM (Universal Decompression Virtual Machine) for decompression, and finally sends the SIP message to the application layer.

[0005] However, SigComp requires that terminal devices implement compression and decompression. The compression algorithm and dictionary definitions, among other things, require high processing and storage capabilities. Implementing these features increases terminal complexity and is difficult for terminals with limited storage resources. Furthermore, common compression algorithms (such as zip) offer limited compression when the original SIP message length is relatively small. Summary of the Invention

[0006] The present application provides a communication method and apparatus, providing a solution for compressing SIP signaling, reducing the complexity of terminal equipment, and improving compression efficiency.

[0007] In order to achieve the above objectives, this application provides the following technical solutions:

[0008] In a first aspect, a communication method is provided, comprising: sending / receiving compressed Session Initiation Protocol (SIP) signaling, wherein the compressed SIP signaling does not carry one or more of the following information: a first field that is the same in all calls, a second field that is repeated in other signaling, and a non-essential field.

[0009] Optionally, the first field includes one or more of the following header attribute fields: International Mobile Equipment Identity (IMEI), Internet Protocol Multimedia Subsystem Communication Service Identifier (ICSI), and Media Function Tag.

[0010] Optionally, the SIP signaling is uplink signaling, and the first field includes one or more of the following header fields: maximum forwarding number, allow, support, accept, accept-contact, preferred service, proxy required, requirement, minimum session duration, session timeout, and early media.

[0011] Optionally, the SIP signaling is downlink signaling, and the first field includes one or more of the following header fields: permission, characteristics and capabilities, charging function address, charging vector, date, and extension field.

[0012] Optionally, the second field includes one or more of the following: a preferred identifier, a path, and an Internet Protocol address.

[0013] Optionally, the SIP signaling is an initial invitation signaling.

[0014] Optionally, the non-essential fields include one or more of the following: session name and overall bandwidth of the current call.

[0015] Optionally, the maximum length of the third field in the SIP signaling is a first threshold, and the maximum length of the fourth field in the SIP signaling is a second threshold.

[0016] Optionally, the third field includes a call identifier, and the fourth field includes a label and / or a branch.

[0017] Optionally, the first header field in the SIP signaling adopts a standard protocol compression format, and the second header field in the SIP signaling adopts a preset protocol compression format.

[0018] Optionally, the SIP signaling does not include one or more of the following signaling: 183 signaling, PRACK signaling, and 200OK signaling.

[0019] In a second aspect, the present application also discloses a communication method, which includes: sending / receiving compressed Session Initiation Protocol SIP signaling, wherein the compressed SIP signaling does not carry one or more of the following information: a first field that is the same in all calls, a second field that is repeated in other signaling, and a non-essential field.

[0020] Optionally, the SIP signaling is downlink signaling, and the first field includes one or more of the following header fields: permission, characteristics and capabilities, charging function address, charging vector, date, and extension field.

[0021] In a third aspect, the present application also discloses a communication device, which includes: a communication module for sending / receiving compressed Session Initiation Protocol SIP signaling, wherein the SIP signaling does not carry one or more of the following information: a first field that is the same in all calls, a second field that is repeated in other signaling, and a non-essential field.

[0022] In a fourth aspect, the present application also discloses a communication device, which includes: a communication module for sending / receiving compressed Session Initiation Protocol SIP signaling, wherein the SIP signaling does not carry one or more of the following information: a first field that is the same in all calls, a second field that is repeated in other signaling, and a non-essential field.

[0023] In a fifth aspect, a computer-readable storage medium is provided, on which a computer program is stored. The computer program is executed by a processor to execute any one of the methods provided in the first aspect or the second aspect.

[0024] In a sixth aspect, a communication device is provided, comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and the processor runs the computer program to execute any one of the methods provided in the first aspect.

[0025] In a seventh aspect, a communication device is provided, comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and the processor runs the computer program to execute any one of the methods provided in the second aspect.

[0026] In an eighth aspect, a computer program product is provided, on which a computer program is stored, and the computer program is executed by a processor to execute any one of the methods provided in the first aspect or the second aspect.

[0027] In a ninth aspect, a communication system is provided, comprising the above-mentioned terminal device and the above-mentioned network device.

[0028] In the tenth aspect, an embodiment of the present application further provides a chip (or a data transmission device) on which a computer program is stored, and when the computer program is executed by the chip, the steps of the above method are implemented.

[0029] In the eleventh aspect, an embodiment of the present application also provides a system chip for use in a terminal, wherein the chip system includes at least one processor and an interface circuit, wherein the interface circuit and the at least one processor are interconnected through lines, and the at least one processor is used to execute instructions to execute any one of the methods provided in the first aspect or the second aspect.

[0030] Compared with the existing technology, the technical solution of this application has the following beneficial effects:

[0031] In the technical solution of the present application, a terminal device sends / receives compressed Session Initiation Protocol (SIP) signaling, and the SIP signaling does not carry one or more of the following information: a first field that is the same in all calls, a second field that is repeated in other signaling, and a non-essential field. In the technical solution of the present application, the compressed SIP signaling does not carry at least one of the first field, the second field, and the non-essential field. Since the values ​​of the above fields can be obtained by the terminal device / network device through other means, the SIP signaling can be trimmed while ensuring the normal progress of the call. In addition, the above SIP signaling trimming method has no requirements on the performance of the terminal device and can reduce the complexity of the terminal device. The above SIP signaling trimming method can also be applied to SIP signaling of various lengths, thereby improving compression efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] FIG1 is an interactive flow chart of a communication method provided in an embodiment of the present application;

[0033] FIG2 is an interactive flow chart of another communication method provided in an embodiment of the present application

[0034] FIG3 is an interaction flow chart of another communication method provided in an embodiment of the present application;

[0035] FIG4 is a schematic diagram of a specific application scenario provided by an embodiment of the present application;

[0036] FIG5 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0037] FIG6 is a schematic diagram of the hardware structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] The communication systems to which the embodiments of the present application are applicable include, but are not limited to, Long Term Evolution (LTE) systems, fifth-generation (5G) systems, new radio (NR) systems, and future evolution systems or multiple communication convergence systems. Among them, the 5G system can be a non-standalone (NSA) 5G system or a standalone (SA) 5G system. The technical solution of the present application is also applicable to different network architectures, including but not limited to relay network architecture, dual-connection architecture, vehicle-to-everything architecture and other architectures.

[0039] This application mainly relates to the communication between terminal devices and network devices. Among them:

[0040] The network device in the embodiment of the present application may also be referred to as an access network device, for example, a base station (BS) (also referred to as a base station device), which is a device deployed in a radio access network (RAN) to provide wireless communication functions. For example, in the second generation (2nd-Generation, 2G) network, the device providing the base station function includes a base transceiver station (Base Transceiver Station, BTS), in the third generation (3rd-Generation, 3G) network, the device providing the base station function includes a node B (NodeB), in the fourth generation (4th-Generation, 4G) network, the device providing the base station function includes an evolved node B (evolved NodeB, eNB), in the wireless local area network (Wireless Local Area Networks, WLAN), the device providing the base station function is an access point (Access Point, AP), and the device providing the base station function in NR is the next generation Node Base station (gNB), and the further evolved node B (ng-eNB), wherein the gNB and the terminal device communicate using NR technology, and the ng-eNB and the terminal device communicate using Evolved Universal Terrestrial Radio Access (E-UTRA) technology, and both gNB and ng-eNB can be connected to the 5G core network. The network device in the embodiment of the present application also includes a device that provides a base station function in a future new communication system, etc.

[0041] The terminal equipment in the embodiments of the present application may refer to various forms of access terminals, user units, user stations, mobile stations, mobile stations (MS), remote stations, remote terminals, mobile devices, user terminals, wireless communication devices, user agents, or user devices. The terminal equipment may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G network, or a terminal device in a future evolved Public Land Mobile Network (PLMN), etc., and the embodiments of the present application are not limited thereto. The terminal equipment may also be referred to as User Equipment (UE), a terminal, etc.

[0042] Furthermore, the present application can be applied to chips, chip modules, terminals, base stations, etc. that need to support SIP calls in a narrowband environment, and the present application does not impose any restrictions on this.

[0043] As described in the background, SigComp requires terminal devices to implement compression and decompression. Compression algorithms and dictionary definitions, among other things, require high processing and storage capabilities. Implementing these functions increases terminal complexity and is difficult for terminals with limited storage resources. Furthermore, common compression algorithms (such as zip) offer low compression performance when the original SIP message length is relatively small.

[0044] In the technical solution of the present application, the compressed SIP signaling does not carry at least one of the first field, the second field, and the non-essential field. Since the values ​​of the above fields can be obtained by the terminal device / network device through other means, the SIP signaling can be trimmed while ensuring the normal progress of the call. In addition, the above SIP signaling trimming method has no requirements on the performance of the terminal device and can reduce the complexity of the terminal device. The above SIP signaling trimming method can also be applied to SIP signaling of various lengths, thereby improving compression efficiency.

[0045] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, the specific embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0046] Referring to FIG1 , the method provided in this application specifically includes the following steps:

[0047] Step 101: The terminal device sends / receives compressed Session Initiation Protocol (SIP) signaling.

[0048] It should be noted that the serial numbers of the steps in this embodiment do not limit the execution order of the steps.

[0049] It is understood that, in a specific implementation, the communication method can be implemented in the form of a software program, which runs in a processor integrated within a chip or chip module. The method can also be implemented in the form of software combined with hardware, which is not limited in this application.

[0050] In this embodiment, the compressed SIP signaling does not carry one or more of the following information: the first field that is the same in all calls, the second field that is repeated in other signaling, and non-essential fields.

[0051] Among them, the first field represents the same field in all calls, that is, a fixed field. Therefore, the first field may not be carried in the SIP signaling, but the terminal device and the network device may pre-agree on a preset value, thereby reducing the length of the SIP signaling while ensuring the successful establishment of the call.

[0052] The second field indicates the field that is repeated in SIP signaling and other signaling. This means that when the SIP signaling does not carry the second field, the terminal device or network device can obtain the value of the second field from other signaling, thereby reducing the length of the SIP signaling while ensuring that the call is successfully established.

[0053] Non-essential fields are fields that do not affect call establishment. Therefore, a call can be established normally even if the SIP signaling does not carry non-essential fields. Therefore, SIP signaling can be omitted to reduce the length of the SIP signaling.

[0054] In one implementation, the compressed SIP signaling does not carry the first field.

[0055] In another embodiment, the compressed SIP signaling does not carry the second field.

[0056] In yet another embodiment, the compressed SIP signaling does not carry unnecessary fields.

[0057] In yet another embodiment, the compressed SIP signaling does not carry the first field and the second field.

[0058] In yet another embodiment, the compressed SIP signaling does not carry the first field and the non-essential field.

[0059] In yet another embodiment, the compressed SIP signaling does not carry the second field and the non-essential field.

[0060] In yet another embodiment, the compressed SIP signaling does not carry the first field, the second field, and the non-essential field.

[0061] Compared with the original SIP signaling, the compressed SIP signaling in the embodiment of the present application carries fewer fields and is shorter in length, thereby reducing the signaling delay and completing the call establishment in a shorter time.

[0062] Compared with existing SIP signaling compression schemes, the SIP signaling clipping method in the embodiment of the present application has no requirements on the performance of the terminal device and can reduce the complexity of the terminal device; the above-mentioned SIP signaling clipping method can also be applied to SIP signaling of various lengths, thereby improving compression efficiency.

[0063] In a specific embodiment, when the terminal device sends the compressed SIP signaling, the terminal device may compress the original SIP signaling. Specifically, the terminal device may delete at least one of the first field, the second field, and the unnecessary field in the original SIP signaling.

[0064] In another specific embodiment, when a terminal device receives compressed SIP signaling, it parses the received compressed SIP signaling. Specifically, the terminal device can add a first field not included in the compressed SIP signaling using a preset value pre-agreed with the network device. The terminal device can obtain a second field not included in the compressed SIP signaling from other signaling. Accordingly, the network device compresses the original SIP signaling, thereby reducing the length of SIP signaling over narrowband networks.

[0065] In a non-limiting embodiment, the first field that is the same in all calls may include one or more of the following header attribute fields: International Mobile Equipment Identity (IMEI), Internet Protocol Multimedia Subsystem Communication Service Identifier (ICSI), and Media Feature Tags.

[0066] In this embodiment, the SIP signaling includes a SIP header field and SDP. The first field is a partial header field attribute field in the SIP signaling, the value of which is fixed and can be pre-agreed by the terminal device and the network device.

[0067] The SIP signaling in this embodiment can be either uplink signaling or downlink signaling.

[0068] In the case where the SIP signaling is uplink signaling or downlink signaling, the first field not carried by the compressed SIP signaling is different, which will be described in detail below with reference to the embodiments.

[0069] In a non-limiting embodiment, the SIP signaling is uplink signaling, and the first field includes one or more of the following header fields: Maximum Number of Forwards (Max-Forwards), Allow (Allow), Supported (Supported), Accept (Accept), Accept-Contact (Accept-Contact), Preferred Service (P-Preferred-Service), Proxy-Require (Proxy-Require), Require (Require), Minimum Session Duration (Min-SE, also known as the minimum duration of a SIP session), Session Timeout (Session-Expires), and Early Media (P-Early-Media).

[0070] In another non-limiting embodiment, the SIP signaling is downlink signaling, and the first field includes one or more of the following header fields: Allow, Features and Capabilities (Feature-Caps, also known as features and capabilities), Charging Function Addresses (P-Charging-Function-Addresses), Charging Vector (P-Charging-Vector), Date, and Extension Field.

[0071] The extension field in the downlink SIP signaling indicates the extended header information customized by the network device, such as Ericsson invocation history (P-Ericsson.invocation-History) and ZTE cookies (X-ZTE-Cookie).

[0072] It should be noted that the English translations in this application may also be any other feasible names, and this application does not impose any restrictions on this.

[0073] In a non-limiting embodiment, the second field repeated in SIP signaling and other signaling may include one or more of the following: preferred identification (P-Preferred-Identity), path (Route), and Internet Protocol address (Internet Protocol Address).

[0074] Specifically, the SIP signaling sent by the terminal device to the network device, such as the initial INVITE signaling, may not carry the P-Preferred-Identity field. In this case, the network device can obtain the public identity (PUI) from the From header field of the SIP signaling as the P-Preferred-Identity.

[0075] It is understandable that in an anonymous scenario, the initial invitation signaling needs to carry the P-Preferred-Identity field.

[0076] Specifically, the SIP signaling sent by the terminal device to the network device, such as the initial invitation signaling, may not carry the Route field. Accordingly, the SIP request sent by the terminal device to the network device in the conversation needs to add the Route converted from the Record-Route in the received downlink signaling.

[0077] Specifically, the IP address in the SDP in the SIP signaling may not be carried. This is because the IP address of the terminal device can be fixed to only one. If the terminal device and the network device have agreed in advance, the IP address can be deleted in the uplink SIP signaling.

[0078] In a non-limiting embodiment, the non-essential fields in the SIP signaling may include one or more of the following: session name and overall bandwidth of the current call.

[0079] Specifically, the s-line session name in the SDP in the SIP signaling can be simplified to "s=-".

[0080] Specifically, the overall bandwidth of the current call in line b of the SDP in the SIP signaling can be deleted, and s and b are values ​​specified in the communication standard protocol.

[0081] In a non-limiting embodiment, in order to further reduce the length of the SIP signaling, the length of certain fields in the SIP signaling may be restricted.

[0082] In this embodiment, the maximum length of the third field in the compressed SIP signaling is the first threshold, and the maximum length of the fourth field in the compressed SIP signaling is the second threshold.

[0083] Specifically, the third field includes a call identifier (Call-Identity, Call-ID), and the fourth field includes a tag and / or a branch.

[0084] Furthermore, the length of the Call-ID does not exceed 16 bytes, and the length of the tag and branch does not exceed 12 bytes.

[0085] Although the embodiment of the present application limits the length of the third field and the fourth field, the terminal device and / or the network device can still distinguish the corresponding information through the third field and the fourth field without exceeding the first threshold or the second threshold, thereby ensuring the normal establishment of the call.

[0086] In a non-limiting embodiment, the first header field in the SIP signaling adopts a standard protocol compression format, and the second header field in the SIP signaling adopts a preset protocol compression format.

[0087] In this embodiment, the first header field that can be compressed using a standard compression format, such as SigComp, is still compressed using the standard compression format.

[0088] For the second header field that cannot use the standard protocol compression format, you can customize the preset protocol compression format for compression. For example, the field access network information (P-Access-Network-Info) is compressed into PANI, and the field P-Preferred-Identity is compressed into PPI.

[0089] In a non-limiting embodiment, the compressed SIP signaling may not carry unnecessary signaling.

[0090] Specifically, the SIP signaling does not include one or more of the following signalings: 183 signaling, PRACK signaling, and 200OK signaling.

[0091] Please refer to FIG. 2 and FIG. 3 for details. FIG. 2 shows a process of a terminal device making a call, and FIG. 3 shows a process of a terminal device being called.

[0092] As shown in FIG2 , in step 201 , the terminal device sends an invitation signaling to the network device.

[0093] In step 202, the network device sends a 100 trying signaling to the terminal device.

[0094] In step 203, the terminal device sends 183 signaling to the network device. The 183 signaling (183 progressing) indicates that the terminal device is now establishing a connection.

[0095] In step 204, the network device sends a PRACK signaling to the terminal device. The PRACK signaling indicates an acknowledgment of the 183 signaling.

[0096] In step 205, the terminal device sends a 200 OK signaling to the network device. The 200 OK signaling is an acknowledgement of the PRACK signaling.

[0097] In step 206, the network device sends an update signaling to the terminal device.

[0098] In step 207, the terminal device sends a 200 OK signaling to the network device. Here, the 200 OK signaling is a confirmation of the update signaling.

[0099] In step 208, the network device sends a 180 Ring signaling to the terminal device.

[0100] In step 209, the terminal device sends a 200 OK signaling to the network device. Here, the 200 OK signaling is a confirmation of the 180 Ringing signaling.

[0101] In step 210, the network device sends an acknowledgement (ACK) signaling to the terminal device.

[0102] In the above process, the SIP signaling in steps 203 to 207 can be removed, and only necessary SIP signaling interactions are retained, so as to ensure the establishment of the call process while reducing the SIP signaling.

[0103] Similar to the embodiment shown in Figure 2, referring to Figure 3, in the process of the terminal device being called, the SIP signaling in steps 303 to 307 can be removed. Other specific signaling can refer to the above embodiment and will not be repeated here.

[0104] Taking the MO scenario as an example, the compressed SIP signaling is shown in Table 1.

[0105] Table 1

[0106] As can be seen from Table 1 above, the number of compressed SIP signaling messages is smaller and the number of bytes of the SIP signaling messages is smaller, thereby shortening the call establishment time in a narrowband network.

[0107] Furthermore, if the terminal device already supports the standard SIP protocol, only the above clipping rules need to be added to achieve better compression. In addition, the embodiment of the present application does not require the addition of a SIP compression / decompression module, the impact on code size can be ignored, and it will not increase system resource consumption.

[0108] In a specific embodiment of the present application, terminal device 401 can send compressed SIP signaling to network function 1 (402). Network function 1 converts the compressed SIP signaling into standard SIP signaling and then sends it to network function 2 (403).

[0109] Specifically, for the first field not included in the compressed SIP signaling, the network function 1 can add it by using a preset value agreed upon with the terminal device 401. For the second field not included in the compressed SIP signaling, the network function 1 can obtain it from other signaling.

[0110] In this embodiment, the adaptation between the compressed SIP signaling and the standard SIP signaling is achieved through network function 1, so that the terminal device can still perform SIP signaling interaction with the public network device and achieve compatibility with the public network standard SIP protocol.

[0111] Specifically, the network function 1 may be the following functional entities: Session Border Controller (SBC), Proxy-Call Session Control Function (P-CSCF), etc. The network function 2 may be other network elements on the core network side.

[0112] For more specific implementation methods of the embodiments of the present application, please refer to the aforementioned embodiments, which will not be repeated here.

[0113] Please refer to FIG5 , which shows a communication device 50. The communication device 50 may include:

[0114] The communication module 501 is configured to send / receive compressed Session Initiation Protocol (SIP) signaling, wherein the SIP signaling does not carry one or more of the following information: a first field that is the same in all calls, a second field that is repeated in other signaling, and a non-essential field.

[0115] Furthermore, the first field includes one or more of the following header attribute fields: International Mobile Equipment Identity (IMEI), Internet Protocol Multimedia Subsystem Communication Service Identifier (ICSI), and Media Capability Tag.

[0116] Furthermore, the SIP signaling is uplink signaling, and the first field includes one or more of the following header fields: maximum forwarding number, allow, support, accept, accept-contact, preferred service, proxy required, requirement, minimum session duration, session timeout, and early media.

[0117] Furthermore, the second field includes one or more of the following: a preferred identifier, a path, and an Internet Protocol address.

[0118] Furthermore, the non-essential fields include one or more of the following: session name and overall bandwidth of the current call.

[0119] In a specific implementation, the above-mentioned communication device 50 can correspond to a chip with communication function in the terminal equipment, such as a system-on-a-chip (SOC), a baseband chip, etc.; or correspond to a chip module with communication function in the terminal equipment; or correspond to a chip module with a data processing function chip, or correspond to the terminal equipment.

[0120] In another non-limiting embodiment, the communication module 501 is configured to send / receive compressed Session Initiation Protocol (SIP) signaling.

[0121] Furthermore, the SIP signaling is downlink signaling, and the first field includes one or more of the following header fields: permission, characteristics and capabilities, charging function address, charging vector, date, and extension field.

[0122] In a specific implementation, the above-mentioned communication device 50 can correspond to a chip with communication function in a network device, such as an SOC, a baseband chip, etc.; or correspond to a chip module with communication function in a network device; or correspond to a chip module with a data processing function chip, or correspond to a network device.

[0123] For other related descriptions about the communication device 50 , reference may be made to the related descriptions in the aforementioned embodiments, which will not be repeated here.

[0124] Regarding the various modules / units contained in the various devices and products described in the above embodiments, they can be software modules / units, hardware modules / units, or partly software modules / units and partly hardware modules / units. For example, for various devices and products applied to or integrated into a chip, the various modules / units contained therein can all be implemented in the form of hardware such as circuits, or at least part of the modules / units can be implemented in the form of software programs, which run on the processor integrated inside the chip, and the remaining (if any) modules / units can be implemented in the form of hardware such as circuits; for various devices and products applied to or integrated into a chip module, the various modules / units contained therein can all be implemented in the form of hardware such as circuits, and different modules / units can be located in the same component of the chip module (such as a chip, circuit module, etc.) or in different components, or at least part of the modules / units can be implemented in the form of software programs. It is implemented in the form of a software program, which runs on the processor integrated inside the chip module, and the remaining (if any) modules / units can be implemented in the form of hardware such as circuits; for various devices and products applied to or integrated in the terminal equipment, the various modules / units contained therein can be implemented in the form of hardware such as circuits, and different modules / units can be located in the same component (for example, chip, circuit module, etc.) or different components in the terminal equipment, or, at least some modules / units can be implemented in the form of a software program, which runs on the processor integrated inside the terminal equipment, and the remaining (if any) modules / units can be implemented in the form of hardware such as circuits.

[0125] The present application also discloses a storage medium, which is a computer-readable storage medium having a computer program stored thereon. When the computer program is executed, the steps of the method shown in Figures 1 to 3 can be executed. The storage medium may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc. The storage medium may also include a non-volatile memory or a non-transitory memory, etc.

[0126] 6 , an embodiment of the present application further provides a hardware structure diagram of a communication device, which includes a processor 601 , a memory 602 , and a transceiver 603 .

[0127] Processor 601 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application. Processor 601 may also include multiple CPUs, and processor 601 may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor here may refer to one or more devices, circuits, or processing cores for processing data (such as computer program instructions).

[0128] The memory 602 may be a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer, and the embodiments of the present application do not impose any restrictions on this. The memory 602 can be independent (in this case, the memory 602 can be located outside the device or inside the device), or it can be integrated with the processor 601. Among them, the memory 602 can contain computer program code. The processor 601 is used to execute the computer program code stored in the memory 602, thereby implementing the method provided in the embodiments of the present application.

[0129] The processor 601, memory 602, and transceiver 603 are connected via a bus. The transceiver 603 is used to communicate with other devices or a communication network. Optionally, the transceiver 603 may include a transmitter and a receiver. The device used to implement the receiving function in the transceiver 603 can be considered a receiver, which is used to perform the receiving steps in the embodiments of the present application. The device used to implement the transmitting function in the transceiver 603 can be considered a transmitter, which is used to perform the transmitting steps in the embodiments of the present application.

[0130] When the structural diagram shown in FIG6 is used to illustrate the structure of the terminal device involved in the above embodiments, the processor 601 is used to control and manage the actions of the terminal device. For example, the processor 601 is used to support the terminal device in executing the actions performed by the terminal device in other processes described in the embodiments of this application. The processor 601 can communicate with other network entities, such as the above-mentioned network devices, via the transceiver 603. The memory 602 is used to store program code and data of the terminal device.

[0131] When the structural diagram shown in Figure 6 is used to illustrate the structure of the network device involved in the above embodiments, the processor 601 is used to control and manage the actions of the network device. For example, the processor 601 is used to support the network device in executing the actions performed by the network device in other processes described in the embodiments of this application. The processor 601 can communicate with other network entities via the transceiver 603, for example, with the terminal device described above. The memory 602 is used to store program code and data of the network device.

[0132] The embodiment of the present application defines the unidirectional communication link from the access network to the terminal device as a downlink, the data transmitted on the downlink is downlink data, and the transmission direction of the downlink data is called the downlink direction; and the unidirectional communication link from the terminal device to the access network is an uplink, the data transmitted on the uplink is uplink data, and the transmission direction of the uplink data is called the uplink direction.

[0133] It should be understood that the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document indicates that the related objects are in an "or" relationship.

[0134] The term "plurality" used in the embodiments of the present application refers to two or more.

[0135] The first, second, etc. descriptions appearing in the embodiments of this application are only for illustration and distinction of the description objects. There is no order, nor does it indicate any special limitation on the number of devices in the embodiments of this application, and cannot constitute any limitation on the embodiments of this application.

[0136] The "connection" appearing in the embodiments of the present application refers to various connection methods such as direct connection or indirect connection to achieve communication between devices, and the embodiments of the present application do not impose any limitations on this.

[0137] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired or wireless means.

[0138] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0139] In the several embodiments provided in this application, it should be understood that the disclosed methods, devices, and systems can be implemented in other ways. For example, the device embodiments described above are merely schematic; for example, the division of the units is merely a logical function division, and there may be other division methods in actual implementation; for example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection of devices or units, which may be electrical, mechanical, or other forms.

[0140] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0141] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may be physically included separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0142] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium and includes a number of instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to perform some steps of the method described in each embodiment of the present application.

[0143] Although the present application is disclosed as above, the present application is not limited thereto. Any person skilled in the art may make various changes and modifications without departing from the spirit and scope of the present application. Therefore, the scope of protection of the present application shall be based on the scope defined by the claims.

Claims

1. A communication method, characterized in that: include: Send / receive compressed Session Initiation Protocol (SIP) signaling, wherein the compressed SIP signaling does not carry one or more of the following information: a first field that is the same in all calls, a second field that is repeated in other signaling, and a non-essential field.

2. The communication method according to claim 1, wherein: The first field includes one or more of the following header attribute fields: International Mobile Equipment Identity (IMEI), Internet Protocol Multimedia Subsystem Communication Service Identifier (ICSI), and Media Capability Tag.

3. The communication method according to claim 1, wherein: The SIP signaling is an uplink signaling, and the first field includes one or more of the following header fields: maximum forwarding number, allow, support, accept, accept-contact, preferred service, proxy required, requirement, minimum session duration, session timeout, and early media.

4. The communication method according to claim 1, wherein: The SIP signaling is downlink signaling, and the first field includes one or more of the following header fields: permission, characteristics and capabilities, charging function address, charging vector, date, and extension field.

5. The communication method according to claim 1, wherein: The second field includes one or more of the following: a preferred identifier, a path, and an Internet Protocol address. The communication method according to claim 5 , wherein: The SIP signaling is an initial invitation signaling.

7. The communication method according to claim 1, wherein: The non-essential fields include one or more of the following: session name and overall bandwidth of the current call.

8. The communication method according to claim 1, wherein: The maximum length of the third field in the SIP signaling is a first threshold, and the maximum length of the fourth field in the SIP signaling is a second threshold.

9. The communication method according to claim 8, wherein: The third field includes a call identifier, and the fourth field includes a label and / or a branch.

10. The communication method according to claim 1, wherein: The first header field in the SIP signaling adopts a standard protocol compression format, and the second header field in the SIP signaling adopts a preset protocol compression format.

11. The communication method according to any one of claims 1 to 10, characterized in that: The SIP signaling does not include one or more of the following signalings: 183 signaling, PRACK signaling, and 200OK signaling.

12. A communication method, characterized in that: include: Send / receive compressed Session Initiation Protocol (SIP) signaling, wherein the compressed SIP signaling does not carry one or more of the following information: a first field that is the same in all calls, a second field that is repeated in other signaling, and a non-essential field.

13. The communication method according to claim 12, wherein: The SIP signaling is downlink signaling, and the first field includes one or more of the following header fields: permission, characteristics and capabilities, charging function address, charging vector, date, and extension field.

14. A communication device, characterized in that: include: The communication module is used to send / receive compressed Session Initiation Protocol (SIP) signaling, wherein the SIP signaling does not carry one or more of the following information: a first field that is the same in all calls, a second field that is repeated in other signaling, and a non-essential field.

15. A communication device, characterized in that: include: The communication module is used to send / receive compressed Session Initiation Protocol (SIP) signaling, wherein the SIP signaling does not carry one or more of the following information: a first field that is the same in all calls, a second field that is repeated in other signaling, and a non-essential field.

16. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the communication method according to any one of claims 1 to 13 are executed.

17. A communication device comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, characterized in that: When the processor runs the computer program, the processor performs the steps of the communication method according to any one of claims 1 to 11.

18. A communication device comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, characterized in that: When the processor runs the computer program, the processor performs the steps of the communication method according to any one of claims 12 to 13.

Images