Call establishment method, terminal, and network side device

Abstract

The present application relates to the technical field of communications, and discloses a call establishment method, a terminal, and a network side device. The call establishment method of embodiments of the present application comprises: during a process in which a first terminal establishes a call with a first communication device, a first network side device executing a first operation, the first operation comprising at least one of the following: the first network side device receiving a first I1 message and first information from the first terminal, the first I1 message being used by the first terminal to request the first communication device to establish the call; the first network side device sending a response message to the first I1 message and second information to the first terminal; the first network side device sending a second I1 message and third information to the first terminal, the second I1 message being used by the first communication device to request the first terminal to establish the call; and the first network side device receiving a response message to the second I1 message and fourth information that are sent by the first terminal.

Description

Methods for establishing a call, terminals, and network-side equipment

[0001] Cross-references to related applications

[0002] This application is based on and claims priority to Chinese Patent Application No. 202510359983.6, filed on March 25, 2025, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and more specifically, to a method for establishing a call, a terminal, and a network-side device. Background Technology

[0004] A satellite communication system consists of three parts: the satellite terminal, the ground terminal, and the user terminal. The satellite terminal acts as a relay station in the air, amplifying the electromagnetic waves transmitted from the ground station and sending them back. Currently, user equipment (UE) can directly access the network via satellite to make voice calls. UE accessing the network via satellite can be understood as the UE accessing an IP Multimedia Subsystem (IMS) network or a mobile communication network via satellite, or the UE initiating a call request via satellite. However, when the UE accesses the IMS network via satellite, there is a problem of excessively long call setup times, affecting the user experience. Summary of the Invention

[0005] This application provides a method for establishing a call, a terminal, and a network-side device, which can solve the problem of excessively long call establishment time when the terminal accesses the network.

[0006] Firstly, a method for establishing a call is provided, executed by a first network-side device, the method comprising:

[0007] During the process of establishing a call between the first terminal and the first communication device, the first network-side device performs a first operation, which includes at least one of the following:

[0008] The first network-side device receives a first I1 message and first information from the first terminal. The first I1 message is used by the first terminal to request the first communication device to establish a call, and the first information is used to indicate the call parameters to be used. The first network-side device sends a response message and second information to the first terminal, and the second information is used to indicate the call parameters to be used.

[0009] The first network-side device sends a second I1 message and a third information to the first terminal. The second I1 message is used by the first communication device to request the first terminal to establish a call, and the third information is used to indicate the call parameters to be used. The first network-side device receives a response message and a fourth information from the second I1 message sent by the first terminal. The fourth information is used to indicate the call parameters to be used.

[0010] Secondly, a method for establishing a call is provided, executed by a first terminal, the method comprising:

[0011] During the process of establishing a call between the first terminal and the first communication device, the first terminal performs a second operation, the second operation including at least one of the following:

[0012] The first terminal sends a first I1 message and first information to the first network-side device. The first I1 message is used by the first terminal to request the first communication device to establish a call, and the first information is used to indicate the call parameters to be used. The first terminal receives a response message and second information from the first network-side device for the first I1 message, and the second information is used to indicate the call parameters to be used.

[0013] The first terminal receives a second I1 message and a third information from the first network-side device. The second I1 message is used by the first communication device to request the first terminal to establish a call, and the third information is used to indicate the call parameters to be used. The first terminal sends a response message to the second I1 message and a fourth information to the first network-side device. The fourth information is used to indicate the call parameters to be used.

[0014] Thirdly, a method for establishing a call is provided, executed by a fourth network-side device, the method comprising:

[0015] During the registration, attachment, or session establishment process of the first terminal, a fifth message is received from the first terminal, the fifth message indicating at least one of the following:

[0016] Discover the first network-side device that supports I1 messages;

[0017] Discover the first network-side device that supports I1 message translation;

[0018] The first network-side device supporting GEO (Geostationary Earth Orbit) calls in a high-orbit satellite communication system was discovered.

[0019] The first terminal supports I1 messages.

[0020] Optionally, the method further includes:

[0021] During the registration, attachment, or session establishment process of the first terminal, the address information of the first network-side device is sent.

[0022] Optionally, sending the address information of the first network-side device during the registration, attachment, or session establishment process of the first terminal includes:

[0023] The address information of the first network-side device is sent by registering to receive messages; or...

[0024] The address information of the first network-side device is sent by attaching the received message; or...

[0025] The address information of the first network-side device is sent by accepting messages through a session.

[0026] Optionally, receiving the fifth information from the first terminal includes:

[0027] The fifth information is received from the first terminal via the protocol configuration option PCO.

[0028] Optionally, the step of sending the address information of the first network-side device includes:

[0029] The address information of the first network-side device is sent to the first terminal via the PCO.

[0030] Fourthly, a call establishment apparatus is provided, comprising: a receiving module or a sending module;

[0031] During the process of establishing a call between the first terminal and the first communication device, the receiving module or the sending module performs a first operation, the first operation including at least one of the following:

[0032] Receive a first I1 message and first information from the first terminal, wherein the first I1 message is used by the first terminal to request the first communication device to establish a call, and the first information is used to indicate the call parameters to be used; send a response message and second information to the first terminal, wherein the second information is used to indicate the call parameters to be used.

[0033] Send a second I1 message and a third message to the first terminal. The second I1 message is used by the first communication device to request the first terminal to establish a call, and the third message is used to indicate the call parameters to be used. Receive a response message and a fourth message from the first terminal regarding the second I1 message. The fourth message is used to indicate the call parameters to be used.

[0034] Fifthly, a call establishment apparatus is provided, including a sending module or a receiving module:

[0035] During the process of establishing a call between the device and the first communication device, the sending module or the receiving module performs a second operation, the second operation including at least one of the following:

[0036] Send a first I1 message and first information to a first network-side device, wherein the first I1 message is used by the device to request the first communication device to establish a call, and the first information is used to indicate the call parameters to be used; receive a response message and second information from the first I1 message from the first network-side device, wherein the second information is used to indicate the call parameters to be used;

[0037] The device receives a second I1 message and a third message from the first network-side device. The second I1 message is used by the first communication device to request the device to establish a call, and the third message is used to indicate the call parameters to be used. The device then sends a response message to the second I1 message and a fourth message to the first network-side device. The fourth message is used to indicate the call parameters to be used.

[0038] Sixthly, a call establishment apparatus is provided, comprising: a receiving module, used for:

[0039] During the registration, attachment, or session establishment process of the first terminal, a fifth message is received from the first terminal, the fifth message indicating at least one of the following:

[0040] Discover the first network-side device that supports I1 messages;

[0041] Discover the first network-side device that supports I1 message translation;

[0042] The first network-side device supporting GEO (Geostationary Earth Orbit) calls in a high-orbit satellite communication system was discovered.

[0043] The first terminal supports I1 messages.

[0044] Optionally, the device further includes a transmitting module for:

[0045] During the registration, attachment, or session establishment process of the first terminal, the address information of the first network-side device is sent.

[0046] Optionally, the sending module is specifically used for:

[0047] The address information of the first network-side device is sent by registering to receive messages; or...

[0048] The address information of the first network-side device is sent by attaching the received message; or...

[0049] The address information of the first network-side device is sent by accepting messages through a session.

[0050] Optionally, the receiving module is specifically used for:

[0051] The fifth information is received from the first terminal via the protocol configuration option PCO.

[0052] Optionally, the sending module is specifically used for:

[0053] The address information of the first network-side device is sent to the first terminal via the PCO.

[0054] In a seventh aspect, an apparatus for establishing a call is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect, or to implement the steps of the method described in the third aspect.

[0055] Eighthly, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect, or the steps of the method as described in the third aspect.

[0056] In a ninth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to perform a first operation during the establishment of a call between a first terminal and a first communication device, the first operation including at least one of the following:

[0057] Receive a first I1 message and first information from the first terminal, wherein the first I1 message is used by the first terminal to request the first communication device to establish a call, and the first information is used to indicate the call parameters to be used; send a response message and second information to the first terminal, wherein the second information is used to indicate the call parameters to be used.

[0058] Send a second I1 message and a third message to the first terminal. The second I1 message is used by the first communication device to request the first terminal to establish a call, and the third message is used to indicate the call parameters to be used. Receive a response message and a fourth message from the first terminal regarding the second I1 message. The fourth message is used to indicate the call parameters to be used.

[0059] In a tenth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is configured to receive fifth information from the first terminal during the registration, attachment, or session establishment process of the first terminal, the fifth information being configured to indicate at least one of the following:

[0060] Discover the first network-side device that supports I1 messages;

[0061] Discover the first network-side device that supports I1 message translation;

[0062] The first network-side device supporting GEO (Geostationary Earth Orbit) calls in a high-orbit satellite communication system was discovered.

[0063] The first terminal supports I1 messages.

[0064] Eleventhly, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0065] In a twelfth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to perform a second operation during the process of establishing a call between the device and a first communication device, the second operation including at least one of the following:

[0066] Send a first I1 message and first information to a first network-side device, wherein the first I1 message is used by the device to request the first communication device to establish a call, and the first information is used to indicate the call parameters to be used; receive a response message and second information from the first I1 message from the first network-side device, wherein the second information is used to indicate the call parameters to be used;

[0067] The device receives a second I1 message and a third message from the first network-side device. The second I1 message is used by the first communication device to request the device to establish a call, and the third message is used to indicate the call parameters to be used. The device then sends a response message to the second I1 message and a fourth message to the first network-side device. The fourth message is used to indicate the call parameters to be used.

[0068] In a thirteenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect.

[0069] In a fourteenth aspect, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal is configured to perform the steps of the method described in the first aspect, and the network-side device is configured to perform the steps of the method described in the second aspect or the method described in the third aspect.

[0070] In a fifteenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method as described in the first aspect, or the steps of the method as described in the second aspect, or the steps of the method as described in the third aspect.

[0071] In a sixteenth aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement, or the steps of the call establishment method as described in the first aspect, or the steps of the call establishment method as described in the second aspect, or the steps of the call establishment method as described in the third aspect.

[0072] In this embodiment, the first network-side device receives a first I1 message and first information from the first terminal, or sends a response message and second information to the first terminal, or sends a second I1 message and third information to the first terminal, or receives a response message and fourth information from the second I1 message from the first terminal. This enables the device to request the establishment of a call between the first terminal and the first communication device through I1 messages, and to transmit call parameters between the first terminal and the first communication device through relevant information. This allows the terminal to access the network using a smaller number of I1 messages, which helps to reduce the call establishment time and improve the user experience. Attached Figure Description

[0073] Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0074] Figure 2 is a schematic flowchart of the process by which a UE accesses the network via satellite;

[0075] Figure 3 is a schematic flowchart of a call establishment method according to an embodiment of this application;

[0076] Figure 4 is a schematic flowchart of another call establishment method according to an embodiment of this application;

[0077] Figure 5 is a schematic flowchart of another call establishment method according to an embodiment of this application;

[0078] Figure 6A is a schematic flowchart of another call establishment method according to an embodiment of this application;

[0079] Figure 6B is a schematic flowchart of another call establishment method according to an embodiment of this application;

[0080] Figure 7 is a schematic diagram of a registration, attachment, or session establishment process according to an embodiment of this application;

[0081] Figure 8 is a schematic flowchart of a call establishment method according to an embodiment of this application;

[0082] Figure 9 is a schematic flowchart of another call establishment method according to an embodiment of this application;

[0083] Figure 10 is a schematic diagram of a registration process according to an embodiment of this application;

[0084] Figure 11 is a schematic flowchart of a call establishment method according to an embodiment of this application;

[0085] Figure 12 is a schematic flowchart of another call establishment method according to an embodiment of this application;

[0086] Figure 13 is a schematic block diagram of a device for establishing a call according to an embodiment of this application;

[0087] Figure 14 is a schematic block diagram of another device for establishing a call according to an embodiment of this application;

[0088] Figure 15 is a schematic block diagram of another device for establishing a call according to an embodiment of this application;

[0089] Figure 16 is a schematic block diagram of a communication device according to an embodiment of this application;

[0090] Figure 17 is a schematic block diagram of a terminal according to an embodiment of this application;

[0091] Figure 18 is a schematic block diagram of a network-side device according to an embodiment of this application. Detailed Implementation

[0092] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0093] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0094] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.

[0095] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used not only in the systems and radio technologies mentioned above, but also in other systems and radio technologies.

[0096] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as user equipment (UE), and can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. Furthermore, in addition to the terminals described above, terminal 11 can also be a chip within a terminal, such as a modem chip, a system-on-chip (SoC), etc. It should be noted that the specific type of terminal 11 is not limited in the embodiments of this application.

[0097] Network-side equipment 12 may include access network equipment or core network equipment. Access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, wireless local area network (WLAN) access points (APs), or wireless Fidelity (WiFi) nodes, etc. The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), Non-Terrestrial Network (NTN) equipment (e.g., satellite or high altitude platform station), or any other suitable term in the field, provided that the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology.

[0098] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high-altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

[0099] For example, in a 4G network, the core network can be an Evolved Packet Core (EPC), while in a 5G network, the core network can be a 5G core (5GC).

[0100] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0101] This application's embodiments may also relate to the IP Multimedia Subsystem (IMS). IMS is an IP-based network architecture used to provide rich multimedia communication services, such as voice, video, instant messaging, and multimedia conferencing. It was initially standardized by the 3rd Generation Partnership Project (3GPP) to provide next-generation communication services for mobile networks, but has since expanded to fixed networks and converged communication scenarios. The IMS network is a layered architecture, mainly including the access layer, transport layer, IMS core network, and application layer. The access layer allows UEs to connect to the IMS network through different access technologies. The transport layer is responsible for transmitting data between the access layer and the IMS core network, typically based on the IP protocol and supporting multiple transport protocols, such as the Session Initiation Protocol (SIP). The IMS core network is the core part of the IMS network architecture, responsible for handling signaling, user management, and service logic. The application layer provides various multimedia services and service logic. The IMS core network mainly includes the following network elements: Call Session Control Function (CSCF), HSS, Application Server (AS), Media Gateway Control Function (MGCF), IP Multimedia Media Gateway (IM-MGW), PDF, and Charging Collection Function (CCF). The CSCF can include Proxy Call Session Control Function (P-CSCF) and Serving Call Session Control Function (S-CSCF).

[0102] Optionally, in a 4G network, the IMS network is tightly integrated with the Evolved Packet Core (EPC) network and connects to the UE via a PDN gateway (PGW). Optionally, in a 5G network, the IMS network is integrated with the 5G core network (5GC) and connects to the UE via a UPF. Optionally, in a 6G network, the IMS network is integrated with the 6G core network (6GC) and connects to the UE via a UPF.

[0103] In some embodiments, IMS may provide the following services: voice calls, video calls, instant messaging, multimedia conferencing, emergency calls, etc., without limitation.

[0104] For ease of understanding, the satellite access process involved in the embodiments of this application will be described below.

[0105] A satellite communication system consists of three parts: the satellite terminal, the ground terminal, and the user terminal. The satellite terminal acts as a relay station in the air, amplifying the electromagnetic waves transmitted from the ground station and sending them back. Based on their operating orbit, satellite communication systems are generally classified into the following three categories:

[0106] Low Earth Orbit Satellite Communication System (LEO): 500-2000 km above the ground, with relatively low transmission latency and power consumption, but the coverage area of ​​each satellite is also relatively small.

[0107] Medium Earth Orbit Satellite Communication System (MEO): 2000-20000 km above the ground. The transmission delay is greater than that of low Earth orbit satellites, but the coverage area is also larger.

[0108] Geostationary Earth Orbit Satellite Communication System (GEO): 35,800 km above the Earth's surface, i.e., geostationary orbit. Theoretically, global coverage can be achieved using three GEO satellites.

[0109] Currently, UEs can directly access the network via satellite to make voice calls. It should be noted that UE accessing the network via satellite can be understood as the UE accessing the IMS network, 6G network, 5G network, or 4G network via satellite; or the UE initiating a call request via satellite.

[0110] Figure 2 shows a schematic flowchart of the process by which a UE accesses the network via satellite. As shown in Figure 2, the satellite access process includes steps S201 to S214.

[0111] S201. UE-1 initiates a call request (invite) message to UE-2. The invite message contains a Session Description Protocol (SDP) offer, which includes parameters for voice / video calls supported by the UE. These parameters may include supported voice codecs, video codecs, packetization time (ptime), and mode settings.

[0112] It is worth noting that this application describes voice calls as an example, but it can also be applied to video calls, augmented reality (AR) calls, avatar calls, etc.

[0113] S202.P-CSCF sends a temporary response message to UE-1 to notify UE-1 that it has received the invite message. For example, the temporary response message can be a 100 trying message.

[0114] S203.P-CSCF sends the aforementioned invite message to S-CSCF.

[0115] S204. UE-2 replies to UE-1 with a response message (e.g., message 183), which carries an SDP answer. The SDP answer contains at least one codec selected by UE-2 from the voice codecs provided by UE-1. For example, UE-2 can select 97 or 98.

[0116] S205. The P-CSCF sends the SDP answer to UE-1, such as a 183 message. In step S205, the P-CSCF can establish a bearer for UE-1 to transmit voice. For example, in a 5G communication system, this is a QoS flow with a Quality of Service (QoS) level of 1, and in a 4G communication system, it is an Evolved Packet System (EPS) bearer with a QoS level of 1.

[0117] S206. UE-1 sends a provisional response ACK (PRACK) to UE-2, which is used to notify UE-2 that it has received the 183 response message.

[0118] S207. UE-2 replies to UE-1 with a response message (e.g., 200 OK for PRACK) in response to PRACK.

[0119] S208-S209. UE-1 sends an Update message to UE-2. This Update message contains an SDP offer, which includes the codec selected by UE-1 for this call, such as 97 (AMR-WB, byte-aligned mode). Optionally, this Update message is also used to notify UE-2 that its voice bearer has been established.

[0120] S210-S211.UE-2 responds to Update messages with response messages (e.g., 200 OK for update), which carry the SDP answer.

[0121] S212. UE-2 starts ringing for the background user and sends a response message (such as a 180 ringing message) to UE-1.

[0122] S213. When a user in UE-2 answers a call, UE-2 replies with a response message (such as a 200 OK message), which is then routed to UE-1.

[0123] S214. UE-1 sends a confirmation message, such as ACK, to UE-2.

[0124] UE-1 and UE-2 started the call.

[0125] During the process of UE accessing the network via satellite, when making a voice call, the messages based on the SIP protocol are usually quite large. For example, the Invite message in steps S201 and S203 is 2000 bytes. In low-speed scenarios, such as GEO scenarios, assuming a data transmission rate of 1kbps, transmitting this Invite message would take 16 seconds, and the entire call setup time would exceed 1 minute, affecting the user experience.

[0126] The method for establishing a call provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0127] Figure 3 is a schematic flowchart of a call establishment method according to an embodiment of this application. As shown in Figure 3, the call establishment method is applied during the process of establishing a call between a first terminal and a first communication device. The first network-side device performs a first operation, which may include at least some of the following.

[0128] S301, the first network-side device receives a first I1 message and a first information from the first terminal. The first I1 message is used by the first terminal to request the first communication device to establish a call, and the first information is used to indicate the call parameters to be used.

[0129] Correspondingly, the first terminal sends a first I1 message and first information to the first network-side device.

[0130] S302, the first network-side device sends a response message to the first I1 message and second information to the first terminal, the second information being used to indicate the call parameters to be used.

[0131] Correspondingly, the first terminal receives a response message and second information from the first I1 message from the first network-side device.

[0132] S303, the first network-side device sends a second I1 message and a third information to the first terminal. The second I1 message is used by the first communication device to request the first terminal to establish a call, and the third information is used to indicate the call parameters to be used.

[0133] Correspondingly, the first terminal receives the second I1 message and the third information from the first network-side device.

[0134] S304, the first network-side device receives a response message to the second I1 message sent by the first terminal and fourth information, the fourth information being used to indicate the call parameters to be used.

[0135] Correspondingly, the first terminal sends a response message to the second I1 message and the fourth information to the first network-side device.

[0136] It should be understood that Figure 3 illustrates the steps or operations of a call establishment method, but these steps or operations are merely examples, and other operations or variations of the operations shown in Figure 3 may also be performed in this application.

[0137] In this embodiment, the first network-side device receives a first I1 message and first information from the first terminal, or sends a response message and second information to the first terminal, or sends a second I1 message and third information to the first terminal, or receives a response message and fourth information from the second I1 message from the first terminal. This enables the device to request the establishment of a call between the first terminal and the first communication device through I1 messages, and to transmit call parameters between the first terminal and the first communication device through relevant information. This allows the terminal to access the network using a smaller number of I1 messages, which helps to reduce the call setup time and improve the user experience.

[0138] In some embodiments, the first terminal may actively initiate a call establishment process with the first communication device. This process may be referred to as the calling process of the first terminal. In this embodiment, at least one of the above steps S301 and S302 may be executed.

[0139] In some embodiments, the first communication device can actively initiate a call establishment process with the first communication device, that is, the first terminal receives a call from the first communication device and initiates a call establishment process with the first communication device. This process can be referred to as the called party process of the first terminal. In this embodiment, at least one of the above steps S303 and S304 can be executed.

[0140] In some embodiments, the first terminal may actively initiate a call establishment process with the first communication device, or it may receive a call from the first communication device to initiate a call establishment process with the first communication device. This process, including the calling process of the first terminal, also includes the called process of the first terminal. In this embodiment, at least one of the above steps S301 to S304 can be executed.

[0141] In some embodiments, the first terminal and the first communication device can establish various calls, including but not limited to voice calls, video calls, augmented reality (AR) calls, avatar calls, etc., which are not limited in this application.

[0142] In some embodiments, the first communication device may include a user's terminal communication device or a network-side communication device. For example, when a user's first terminal establishes a call with the operator's customer service's first communication device, the first communication device is a network-side communication device rather than a terminal communication device.

[0143] In some embodiments, the first network-side device may include devices in the IMS network, including but not limited to CSCF, IMS AS, etc.

[0144] In some embodiments, call parameters include at least one of encoding / decoding parameters and packet time ptime.

[0145] For example, encoding / decoding parameters include voice codec parameters, video codec parameters, etc. Here, codec refers to the algorithm used for encoding and / or decoding. For example, voice codec parameters may include corresponding encoding / decoding protocols, such as G.711, AMR-WB, etc., and video codec parameters may include corresponding encoding / decoding protocols, such as H.264, H.265, etc.

[0146] Optionally, the encoding and decoding parameters may also include a mode set, where each mode defines the encoder’s operating mode under different conditions, such as bit rate and sampling rate.

[0147] Packet time (ptime) represents the duration of media contained in a Real-Time Transport Protocol (RTP) data packet, measured in milliseconds (ms). It determines the length of time that voice or video data is packaged before transmission.

[0148] In relevant protocols (such as the 3GPP TS24.294 protocol), I1 messages are a simplification of SIP messages, reducing their size. One approach is to encode I1 messages in binary format instead of traditional text. Using binary format removes redundant text information, such as header names and parameter names, transmitting only the necessary data, thus significantly reducing the I1 message size. Another approach is to transmit I1 messages based on the Hypertext Transfer Protocol (HTTP) / 2, leveraging HTTP / 2's multiplexing and header compression features to further optimize transmission efficiency. Yet another approach is to compress common SIP fields, such as From, To, and Call-ID, using predefined dictionaries, such as static and dynamic tables. These fields only need to be referenced from the dictionary during transmission, rather than transmitting the complete text. Finally, I1 messages can remove redundant information, such as spaces and newlines, further reducing their size. Therefore, in this embodiment of the application, during the communication process between the first terminal and the first network-side device, the original SIP message is replaced by an I1 message, and the first network-side device can perform conversion between the I1 protocol and the SIP protocol.

[0149] For example, in the calling process of the first terminal, the first network-side device performs a conversion from the I1 protocol to the SIP protocol. Specifically, after receiving the first I1 message and the first information from the first terminal, the first network-side device can send a SIP message to the first communication device.

[0150] For example, during the calling process of the first terminal, the first network-side device can also perform SIP protocol to I1 protocol conversion. Specifically, after receiving the SIP message from the first communication device, the first network-side device can send a response message for the first I1 message and second information to the first terminal.

[0151] For example, in the called party process of the first terminal, the first network-side device can perform a conversion from the SIP protocol to the I1 protocol. Specifically, after receiving the SIP message from the first communication device, the first network-side device can send a second I1 message and a third piece of information to the first terminal.

[0152] For example, during the called party process of the first terminal, the first network-side device can perform the conversion from the I1 protocol to the SIP protocol. Specifically, after receiving the response message of the first I1 message and the fourth information from the first terminal, the first network-side device can send a SIP message to the first communication device.

[0153] In some embodiments, an I1 message may include at least one information element (IE), including but not limited to at least one of the following: message type, call ID, message sequence number, timestamp, destination ID (To-ID), and source ID (From ID). Specifically, the message type indicates that the I1 message is an I1 invite message initiated by the terminal; the call ID uniquely identifies the I1 message; the message sequence number identifies the sequence number of the message transmission; the timestamp identifies the time the I1 message was generated; the destination ID identifies the destination address of the I1 message, such as a target phone number; and the source ID identifies the source address of the I1 message, such as the initiator's phone number.

[0154] Optionally, in some embodiments, the I1 message may also include relevant call parameters, such as requested call parameters or confirmed call parameters to be used, without limitation. Specifically, the call parameters can be referred to the relevant descriptions above.

[0155] Therefore, in this embodiment of the application, during the communication process between the first terminal and the first network-side device, a smaller I1 message is used to replace the original larger SIP message. The first network-side device then performs the conversion between the I1 protocol and the SIP protocol, thereby enabling the establishment of a call between the first terminal and the first communication device through an I1 message request. This achieves the use of a smaller I1 message to enable the terminal to access the network and reduces the call establishment time.

[0156] In some embodiments, the first network-side device receives a first I1 message and first information from the first terminal, including:

[0157] The first network-side device receives a first IP data packet from the first terminal. The first IP data packet includes the first I1 message, the first information, and the address information of the first network-side device.

[0158] Specifically, the first terminal can obtain the address information of the first network-side device before sending the first I1 message and the first information to the first network-side device. Optionally, this address information may include an IP address. Then, the first terminal can send a first IP data packet to the first network-side device based on the address information of the first network-side device. The first IP data packet includes the first I1 message, the first information, and the address information of the first network-side device. The address information of the first network-side device is the destination address of the first IP data packet.

[0159] In one implementation, the first IP packet may include a header and a payload, wherein the address information of the first network-side device is included in the header, and the first I1 message is included in the payload. Optionally, the first information may be included in the first I1 message or directly in the payload, without limitation.

[0160] Optionally, the first network-side device may also send a second IP data packet to the first terminal. The second IP data packet includes a response message to the first I1 message, the second information, and the address information of the first terminal. The way the response message to the first I1 message, the second information, and the address information of the first terminal are carried is similar to that of the first I1 message, the first information, and the address information of the first network-side device, as described above.

[0161] Optionally, the first network-side device may also send a third IP data packet to the first terminal. The third IP data packet includes the second I1 message, the third information, and the address information of the first terminal. The way the second I1 message, the third information, and the address information of the first terminal are carried is similar to that of the first I1 message, the first information, and the address information of the first network-side device, as described above.

[0162] Optionally, the first network-side device may also receive a fourth IP data packet from the first terminal. The fourth IP data packet includes a response message to the second I1 message, fourth information, and the address information of the first network-side device. The way the response message to the second I1 message, the fourth information, and the address information of the first network-side device are carried is similar to that of the first I1 message, the first information, and the address information of the first network-side device, as described above.

[0163] In some embodiments, at least one of the following is satisfied in the method:

[0164] The first I1 message includes the first information;

[0165] The response message to the first I1 message includes the second information;

[0166] The second I1 message includes the third information;

[0167] The response message to the second I1 message includes the fourth information.

[0168] For example, in the calling process of the first terminal, the first I1 message includes first information, and the response message of the first I1 message includes second information. For example, in the called process of the first terminal, the second I1 message includes third information, and the response message of the second I1 message includes fourth information.

[0169] In some implementations, the I1 message includes a scheme for indicating relevant information about call parameters, which can be called option 1.

[0170] For example, the first I1 message may carry first information, namely, the call parameters requested by the first terminal, or the call parameters requested by the first terminal in this call. Taking the call parameters including encoding and decoding parameters as an example, Table 1 shows an example of the first I1 message.

[0171] Table 1

[0172] Among them, Supported Codecs is used to identify the initiator, that is, the encoding and decoding parameters supported by the first terminal. In some implementations, Supported Codec can also be understood or replaced with codec information or other information, without limitation.

[0173] In one implementation, the first IP data packet may include a first I1 message, and the first I1 message carries first information, such as information indicating the call parameters to be used. For example, the first I1 message may be carried in the payload portion of the first IP data packet.

[0174] For example, the response message to the first I1 message may carry second information, namely, confirmed call parameters, or call parameters confirmed / selected by the first communication device or the second network-side device in this call. Taking the call parameters including codec parameters as an example, Table 2 shows an example of the response message to the first I1 message.

[0175] Table 2

[0176] The Confirmed Codec is used to identify the encoding / decoding parameters confirmed by the communication peer, such as a first communication device or a second network-side device. In some implementations, Confirmed Codec can also be understood as or replaced by Supported Codec or Codec information.

[0177] In one implementation, the second IP data packet may include a response message to the first I1 message, and the response message carries second information, such as information indicating the call parameters to be used. For example, the response message to the first I1 message may be carried in the payload portion of the second IP data packet.

[0178] For example, the second I1 message may carry third information, namely, the call parameters requested by the first communication device, or the call parameters requested by the first communication device in this call. For instance, the second I1 message may be the same as or similar to the first I1 message shown in Table 1, and the relevant descriptions in Table 1 can be referred to.

[0179] In one implementation, the third IP packet may include a second I1 message, and the second I1 message carries third information, such as information indicating the call parameters to be used. For example, the second I1 message may be carried in the payload portion of the third IP packet.

[0180] For example, the response message to the second I1 message may carry fourth information, namely, the determined call parameters, or the call parameters confirmed / selected by the first terminal or relevant network-side device in this call. For instance, the response message to the second I1 message may be the same as or similar to the response message to the first I1 message shown in Table 2, and the relevant descriptions in Table 2 can be referenced.

[0181] In one implementation, the fourth IP packet may include a response message to the second I1 message, and the response message carries fourth information, such as information indicating the call parameters to be used. For example, the response message to the second I1 message may be carried in the payload portion of the fourth IP packet.

[0182] Therefore, this application embodiment enhances the I1 protocol by carrying information for indicating call parameters in the I1 message, such as carrying first information in the first I1 message, carrying second information in the response message of the first I1 message, carrying third information in the second I1 message, or carrying fourth information in the response message of the second I1 message. This enables the I1 message to carry the relevant call parameters in the request message, resulting in smaller transmitted data and helping to shorten the call setup time.

[0183] In some embodiments, at least one of the following is satisfied in the method:

[0184] The first information includes a first Session Description Protocol (SDP) invitation, and the first SDP invitation includes call parameters requested by the first terminal.

[0185] The second information includes a first SDP response, which includes call parameters selected and used by the first communication device or the second network-side device.

[0186] The third information includes a second SDP invitation, which includes call parameters requested by the first communication device or the second network-side device.

[0187] The fourth information includes a second SDP response, which includes the call parameters selected by the first terminal.

[0188] For example, in the calling process of the first terminal, the first information includes a first SDP invitation, which includes the call parameters requested by the first terminal; the second information includes a first SDP response, which includes the call parameters confirmed / selected by the first communication device or the second network-side device.

[0189] For example, in the called party process of the first terminal, the third information includes a second SDP invitation, which includes the call parameters requested by the first communication device or the second network-side device; the fourth information includes a second SDP response, which includes the call parameters confirmed / selected by the first terminal.

[0190] In some implementations, the information used to indicate call parameters includes SDP information, which can be referred to as option 2.

[0191] For example, the first terminal sends a first I1 message and first information including a first SDP offer to the first network-side device. In other words, the first terminal can send the complete SDP offer and the first I1 message side-by-side in the same message to the first network-side device.

[0192] In one implementation, the first IP packet may include a first I1 message and a first SDP offer. For example, the first I1 message and the first SDP offer may be carried in the payload portion of the first IP packet.

[0193] For example, the first network-side device sends a response message to the first I1 message and second information including the first SDP answer to the first terminal. In other words, the first network-side device can send the response message to the first I1 message and the first SDP answer to the first terminal in the same message.

[0194] In one implementation, the second IP packet may include a response message to the first I1 message and a first SDP answer. For example, the response message to the first I1 message and the first SDP answer may be carried in the payload portion of the second IP packet.

[0195] For example, the first network-side device sends a second I1 message and third information including a second SDP offer to the first terminal. In other words, the first network-side device can send the second I1 message and the second SDP offer to the first terminal in the same message.

[0196] One implementation method is that the third IP packet may include a second I1 message and a second SDP offer. For example, the second I1 message and the second SDP offer may be carried in the payload portion of the third IP packet.

[0197] For example, the first terminal sends a response message to the second I1 message and second information including the second SDP answer to the first network-side device. In other words, the first terminal can send the response message to the second I1 message and the second SDP answer to the first network-side device.

[0198] In one implementation, the fourth IP packet may include a response message to the second I1 message and a second SDP answer. For example, the response message to the second I1 message and the second SDP answer may be carried in the payload portion of the first IP packet.

[0199] Therefore, by including I1 messages and SDP information side by side in the same message, the first network-side device only needs to add the SDP information contained in the message to the SIP message to realize the conversion from I1 message to SIP message, which helps to simplify the processing of the first network-side device. Furthermore, by sending I1 messages and related SDP information, the transmitted data can be smaller, which helps to shorten the call setup time.

[0200] In some embodiments, the first information may not include the first SDP invitation, but may include information for the first network-side device to generate the relevant SDP invitation, such as call parameters for indicating the request to use.

[0201] In one implementation, the first IP packet may include a first I1 message and first information, the first information indicating information about the requested call parameters. For example, the first I1 message and the first information may be carried in the payload portion of the first IP packet.

[0202] Alternatively, the second information may not include the first SDP response, but may include information generated by the first network-side device based on the relevant SDP response from the first communication device, such as call parameters used to indicate the determination of which to use.

[0203] In one implementation, the second IP data packet may include a response message to the first I1 message and second information, the second information indicating information about the call parameters used for confirmation. For example, the response message to the first I1 message and the second information may be carried in the payload portion of the second IP data packet.

[0204] Alternatively, the third information may not include the second SDP invitation, but may include information generated by the first network-side device based on the relevant SDP invitation from the first communication device, such as call parameters used to indicate the requested use.

[0205] In one implementation, the third IP packet may include a second I1 message and third information, the third information indicating information about the requested call parameters. For example, the second I1 message and the third information may be carried in the payload portion of the third IP packet.

[0206] Alternatively, the fourth information may not include the second SDP response, but may include information for the first network-side device to generate the relevant SDP response, such as information for indicating the call parameters to be used.

[0207] In one implementation, the fourth IP packet may include a response message to the second I1 message and fourth information, the fourth information indicating information confirming the use of call parameters. For example, the response message to the second I1 message and the fourth information may be carried in the payload portion of the fourth IP packet.

[0208] In some implementations, the I1 message is placed alongside relevant information that indicates call parameters in the same message, which may be referred to as option 3.

[0209] Therefore, by including the I1 message and the first information used to indicate the relevant call parameters in the same message, this embodiment of the application does not require enhancing the existing I1 protocol, makes little change to the existing standard, and can reduce the amount of data transmitted by sending the I1 message and the relevant call parameters, which is beneficial to shortening the call setup time.

[0210] Optionally, at least one of the following conditions must be met in the method:

[0211] The first information is used to indicate the call parameters supported by the first terminal;

[0212] The second information is used to indicate the call parameters supported by the first communication device or the call parameters supported by the second network-side device;

[0213] The third information is used to indicate the call parameters supported by the first communication device or the call parameters supported by the second network-side device.

[0214] The fourth piece of information is used to indicate the call parameters supported by the first terminal.

[0215] For example, in the calling process of the first terminal, the first information is used to indicate the call parameters supported or requested by the first terminal, and the second information is used to indicate the call parameters supported, confirmed or selected by the first communication device, or the call parameters supported, confirmed or selected by the second network-side device.

[0216] For example, in the called process of the first terminal, the third information is used to indicate the call parameters supported or requested by the first communication device or the call parameters supported or requested by the second network-side device, and the fourth information is used to indicate the call parameters supported, selected or confirmed by the first terminal.

[0217] Optionally, the second network-side device is controlled by the first network-side device and is a core network device used to transmit call data with the first terminal. For example, the second network-side device may include, but is not limited to, an Access Gateway (AGW) or a Media Gateway Control Function (MGCF). The AGW is controlled by the P-CSCF and is a core network device used to transmit voice call data with the first terminal, while the MGCF is controlled by the IMS AS and is also a core network device used to transmit voice call data with the first terminal.

[0218] Figure 4 is a schematic flowchart of another call establishment method according to an embodiment of this application. As shown in Figure 4, the call establishment method is applied to the process of establishing a call between a first terminal and a first communication device. The call establishment process is the calling process of the first terminal and may include at least some of the following contents S401 to S405.

[0219] S401, the first terminal sends a first I1 message and first information to the first network-side device.

[0220] Specifically, step S401 is the same as or similar to step S301 in Figure 3, and you can refer to the relevant description in Figure 3.

[0221] S402, the first network-side device sends a first message to the first communication device.

[0222] For example, the first network-side device can send a first message to the first communication device based on the first I1 message. The first message is used by the first network-side device to request the first communication device to establish the call.

[0223] In one implementation, the first network-side device can convert the I1 protocol to the SIP protocol based on the first I1 message, generate a first message, and then send the first message to the first communication device. For example, the first message can be a SIP invite message.

[0224] Optionally, the first network-side device may add an SDP offer to the first message.

[0225] One possible implementation is that the first network-side device generates an SDP offer based on the first information in the first I1 message, corresponding to the scheme of option 1. For example, the SDP offer can be generated based on the supported codecs in the first I1 message, which can reduce the amount of data transmitted between the first terminal and the first network-side device, thus shortening the call setup time.

[0226] Another possible approach is for the first network-side device to add the first SDP offer included in the first information to the first message, which corresponds to option 2 and simplifies the processing of the first network-side device.

[0227] Another possible approach is for the first network-side device to generate an SDP offer based on the first information, which corresponds to option 3. In this case, the first network-side device does not need to enhance the I1 message, and the standard modification is minor.

[0228] Optionally, in step S403, the first communication device sends a response message to the first network-side device for the first message. Correspondingly, the first network-side device receives the response message for the first message from the first communication device.

[0229] In some implementations, the response message of the first message may carry an SDP answer. This SDP answer may contain confirmation of the call parameters used. Optionally, the confirmation of the call parameters used may include call parameters selected by the first communication device or the second network-side device.

[0230] Optionally, S404, the first network-side device establishes a bearer.

[0231] Specifically, the first network-side device can establish a bearer for the first terminal to transmit call services.

[0232] For example, when the first network-side device is a P-CSCF, the first network-side device can establish a bearer for the first terminal to transmit call services.

[0233] Optionally, the first network-side device may also send a third message to the third network-side device, the third message being used to instruct the third network-side device to establish a bearer for the first terminal to transmit call services.

[0234] For example, when the first network-side device is an IMS AS, the first network-side device cannot establish a bearer for the first terminal to transmit call services. In this case, the first network-side device can send the aforementioned third message to the third network-side device (such as P-CSCF) to request the third network-side device to establish a bearer for the first terminal to transmit call services.

[0235] S405, the first network-side device sends a response message to the first I1 message and second information to the first terminal.

[0236] For example, upon receiving a response message from the first communication device for the first message, the first network-side device may send a response message for the first I1 message and the second information to the first terminal.

[0237] For example, the first network-side device can generate a response message and second information for the first I1 message based on the SDP answer in the response message of the first message, and send the response message and second information of the first I1 message to the first terminal.

[0238] One possible implementation is that the first network-side device can carry second information, corresponding to option 1, in the response message of the first I1 message based on the SDP answer in the response message of the first message. This response message of the first I1 message can be carried in the payload portion of the second IP data packet.

[0239] Alternatively, the first network-side device can add the SDP answer from the response message of the first message to the payload portion of the second IP packet, which corresponds to option 2. In this case, the second message includes the SDP answer. The payload portion of the second IP packet also includes the response message of the first I1 message.

[0240] Alternatively, the first network-side device can generate second information based on the SDP answer in the response message of the first message, and add the second information to the payload of the second IP packet, which corresponds to option 3. In this case, the payload of the second IP packet also includes the response message of the first I1 message.

[0241] Specifically, the response message to the first I1 message and the second information can be found in the relevant description in Figure 3.

[0242] Therefore, in this embodiment, the first network-side device receives the first I1 message and the first information from the first terminal, sends the first message to the first communication device to request the establishment of a call, and sends the response message of the first I1 message and the second information to the first terminal upon receiving the response message of the first message from the first communication device. This enables the first terminal to initiate a request to establish a call between the first terminal and the first communication device, and enables the terminal to access the network using a smaller I1 message, which helps to reduce the call establishment time and improve the user experience.

[0243] Figure 5 is a schematic flowchart of another call establishment method according to an embodiment of this application. As shown in Figure 5, the call establishment method is applied to the process of establishing a call between a first terminal and a first communication device. The call establishment process is the called process of the first terminal and may include at least some of the following contents S501 to S505.

[0244] S501, the first communication device sends a second message to the first network-side device. Correspondingly, the first network-side device receives the second message from the first communication device. The second message is used by the first communication device to request the first terminal to establish a call.

[0245] For example, the second message could be a SIP invite message.

[0246] Optionally, the second message may include an SDP offer, which includes call parameters requested by the first communication device or the second network-side device.

[0247] Optionally, the destination address of the second message is the address information of the first terminal. This address information can be a SIP Uniform Resource Identifier (URI) or an IP address.

[0248] S502, the first network-side device sends a second I1 message and a third message to the first terminal.

[0249] For example, the first network-side device can send the second I1 message and the third information to the first terminal based on the second message.

[0250] For example, the first network-side device can convert the SIP protocol to the I1 protocol according to the second message, generate a second I1 message and a third message, and then send the second I1 message and the third message to the first terminal.

[0251] One possible implementation is that the first network-side device can carry third information, corresponding to option 1, in a second I1 message based on the SDP offer in the second message. This second I1 message can be carried in the payload portion of the third IP packet.

[0252] Alternatively, the first network-side device can add the SDP offer from the second message to the payload of the third IP packet, corresponding to option 2. In this case, the third message includes the SDP offer. The payload of the third IP packet also includes the second I1 message.

[0253] Alternatively, the first network-side device can generate third information based on the SDP answer in the second message and add this third information to the payload of the third IP packet, which corresponds to option 3. In this case, the payload of the third packet also includes the second I1 message.

[0254] Specifically, the second I1 message and the third information can be found in the relevant descriptions in Figure 3.

[0255] S503, the first terminal sends a response message to the second I1 message and fourth information to the first network-side device.

[0256] Specifically, the response message to the second I1 message and the fourth information can be found in the relevant description in Figure 3.

[0257] S504, the first network-side device establishes a bearer.

[0258] Specifically, the first network-side device can establish a bearer for the first terminal to transmit call services.

[0259] Optionally, the first network-side device may also send a third message to the third network-side device, the third message being used to instruct the third network-side device to establish a bearer for the first terminal to transmit call services.

[0260] Specifically, the process of establishing the bearer can be referred to in the relevant description of step S404 in Figure 4.

[0261] S505, the first network-side device sends a response message for the second message to the first communication device.

[0262] Specifically, the first network-side device can send a response message of the second message to the first communication device based on the response message of the second I1 message and the fourth information.

[0263] In one implementation, the first network-side device can convert the I1 protocol to the SIP protocol based on the response message of the second I1 message, generate a response message for the second message, and then send the response message of the second message to the first communication device.

[0264] Optionally, the first network-side device may add an SDP answer to the response message of the second message.

[0265] One possible implementation is that the first network-side device can generate an SDP answer based on the third information in the response message of the second I1 message, corresponding to option 1. For example, the first network-side device can generate an SDP answer based on the Confirmed Codecs in the first I1 message and add it to the response message of the second message.

[0266] Another possible approach is for the first network-side device to add the second SDP answer included in the third information to the response message of the second message, which corresponds to option 2, thus simplifying the processing of the first network-side device.

[0267] Another possible approach is for the first network-side device to generate an SDP answer based on the third information, which corresponds to option 3. In this case, the first network-side device does not need to enhance the I1 message, resulting in minor standard modifications.

[0268] Therefore, in this embodiment, the first network-side device receives a second message from the first communication device and sends a second I1 message and a third message to the first terminal to request the establishment of a call. Upon receiving the response message of the second I1 message and the fourth message from the first terminal, the device sends a response message of the second message to the first communication device. This enables the first terminal to be requested to establish a call between the first terminal and the first communication device, and enables the terminal to access the network using a smaller I1 message. This helps to reduce the call establishment time and improve the user experience.

[0269] In some embodiments, the first network-side device may also receive a registration request message related to the first terminal and address information of the third network-side device. The registration request message includes information about the first terminal, and a response message to the registration request message is sent. The response message to the registration request message includes the address information of the first network-side device.

[0270] Specifically, the first terminal can perform a network registration process, such as an IMS registration process. During this registration process, the registration request message related to the first terminal is sent to the first network-side device via a relevant network-side device, such as a P-CSCF or S-CSCF. For example, when sending the registration request message to the first network-side device, the S-CSCF may also carry the address information of a third network-side device (such as the P-CSCF serving the first terminal). The first network-side device receives the registration request message related to the first terminal and the address information of the third network-side device, and replies with a response message, which may carry the address information of the first network-side device. The first terminal records the address information of the first network-side device serving it.

[0271] For example, taking the first network-side device as an IMS AS, during the IMS registration process initiated by the first terminal, a registration request message can be sent to its corresponding network-side device #1 (such as the P-CSCF serving the first terminal). This registration request includes information about the first terminal, such as its SIP URI and IP address. The P-CSCF serving the first terminal routes this registration request message to network-side device #2 (such as the S-CSCF) based on the first terminal's domain name information. The S-CSCF records the first terminal's information (such as the mapping between SIP URIs and IP addresses) and, based on the first terminal's subscription information, sends a registration request message to the first network-side device (i.e., the IMS AS) serving the first terminal, carrying the first terminal's information such as its SIP URI and IP address.

[0272] Correspondingly, the first network-side device can send a response message to the registration request message, which includes the address information of the first network-side device, such as its IP address. This response message is forwarded to the first terminal via network-side device #2 and network-side device #2.

[0273] In some implementations, the first network-side device may send the aforementioned third message to the third network-side device based on the address information of the third network-side device.

[0274] In some implementation methods, the first terminal can send the aforementioned related I1 messages and related information, such as the first IP data packet and the fourth IP data packet, to the first network-side device based on the address information of the first network-side device.

[0275] Figure 6A is a schematic flowchart of another call establishment method according to an embodiment of the present application. As shown in Figure 6A, the call establishment method is applied during the process of establishing a call between a first terminal and a first communication device. The first terminal performs a second operation, which includes at least one of the following.

[0276] S601, the first terminal sends a first I1 message and a first information to the first network-side device. The first I1 message is used by the first terminal to request the first communication device to establish a call, and the first information is used to indicate the call parameters to be used.

[0277] S602, the first terminal receives a response message and second information from the first network-side device for the first I1 message, the second information being used to indicate the call parameters to be used.

[0278] S603, the first terminal receives a second I1 message and a third information from the first network-side device. The second I1 message is used by the first communication device to request the first terminal to establish a call, and the third information is used to indicate the call parameters to be used.

[0279] S604, the first terminal sends a response message to the second I1 message and fourth information to the first network-side device, the fourth information being used to indicate the call parameters to be used.

[0280] It should be understood that Figure 6 illustrates the steps or operations of a call establishment method, but these steps or operations are merely examples, and other operations or variations of the operations in Figure 6 may also be performed in this application.

[0281] In this embodiment, the first terminal sends a first I1 message and first information to the first network-side device, or receives a response message and second information from the first I1 message from the first network-side device, or receives a second I1 message and third information from the first network-side device, or sends a response message and fourth information to the first network-side device. This enables the establishment of a call between the first terminal and the first communication device through I1 messages, and the transmission of call parameters between the first terminal and the first communication device through relevant information. This allows the terminal to access the network using a smaller number of I1 messages, which helps to reduce the call establishment time and improve the user experience.

[0282] In some embodiments, at least one of the following is satisfied in the method:

[0283] The first I1 message includes the first information;

[0284] The response message to the first I1 message includes the second information;

[0285] The second I1 message includes the third information;

[0286] The response message to the second I1 message includes the fourth information.

[0287] In some embodiments, at least one of the following is satisfied in the method:

[0288] The first information includes a first Session Description Protocol (SDP) invitation, and the first SDP invitation includes call parameters requested by the first terminal.

[0289] The second information includes a first SDP response, which includes call parameters selected and used by the first communication device or the second network-side device.

[0290] The third information includes a second SDP invitation, which includes call parameters requested by the first communication device or the second network-side device.

[0291] The fourth information includes a second SDP response, which includes the call parameters selected by the first terminal.

[0292] In some embodiments, at least one of the following is satisfied in the method:

[0293] The first information is used to indicate the call parameters supported by the first terminal;

[0294] The second information is used to indicate the call parameters supported by the first communication device or the call parameters supported by the second network-side device;

[0295] The third information is used to indicate the call parameters supported by the first communication device or the call parameters supported by the second network-side device.

[0296] The fourth piece of information is used to indicate the call parameters supported by the first terminal.

[0297] In some embodiments, the first terminal sends a first I1 message and first information to the first network-side device, including:

[0298] The first terminal sends a first IP data packet to the first network-side device. The first IP data packet includes the first I1 message, the first information, and the address information of the first network-side device.

[0299] Specifically, the operations of the first terminal in establishing a call between the first terminal and the first communication device correspond to the operations of the first network-side device in establishing a call between the first terminal and the first communication device, as can be seen in the relevant descriptions in Figures 3 to 5.

[0300] In some embodiments, the first terminal may also send an IMS registration request message related to the first terminal; and

[0301] A response message to the IMS registration request message is received, wherein the response message to the IMS registration request message includes the address information of the first network-side device.

[0302] Specifically, the first terminal can perform a network registration process, such as IMS registration. During this registration process, the registration request message related to the first terminal is sent to the first network-side device via a relevant network-side device, such as a P-CSCF or S-CSCF. For example, when sending the registration request message to the first network-side device, the S-CSCF may also carry the address information of a third network-side device (such as the P-CSCF serving the first terminal). The first network-side device receives the registration request message related to the first terminal and the address information of the third network-side device, and replies with a response message, which may carry the address information of the first network-side device. The first terminal records the address information of the first network-side device serving it.

[0303] In some embodiments, the first terminal may also send a fifth message during the registration, attachment, or session establishment process, the fifth message indicating at least one of the following:

[0304] Discover the first network-side device that supports I1 messages;

[0305] Discover the first network-side device that supports I1 message translation;

[0306] The first network-side device supporting GEO (Geostationary Earth Orbit) calls in a high-orbit satellite communication system was discovered.

[0307] The first terminal supports I1 messages.

[0308] Specifically, the first terminal may initiate a registration request, attach request, or session establishment request to the network-side device (such as a mobility management element) during the registration, attach process, or session establishment process (such as the establishment of a Packet Data Network (PDN) connection). The request includes the fifth information mentioned above.

[0309] For example, the first network-side device that supports I1 messages can refer to a first network-side device that supports the I1 protocol.

[0310] For example, the first network-side device that supports I1 message conversion can refer to the first network-side device that supports I1 protocol conversion. Here, I1 protocol conversion can be understood or replaced as: supporting the conversion of I1 protocol to SIP protocol, or supporting the mutual conversion between I1 protocol and SIP protocol.

[0311] For example, the first network-side device supporting GEO calls can refer to a first network-side device that supports network access via satellite. It is understood that when the first network-side device supports GEO calls, it can also support I1 messages.

[0312] For example, the first terminal supporting I1 messages can mean that the first terminal supports the I1 protocol.

[0313] Here, "supporting I1 messages" or "I1 protocol" can refer to supporting the reception or sending of I1 messages, or supporting the parsing of I1 messages, without any limitation.

[0314] For example, a first network-side device that supports I1 messages or I1 message translation may include a P-CSCF.

[0315] Therefore, in this embodiment of the application, the first terminal can send a fifth message during the registration, attachment, or session establishment process to instruct the network-side device to discover a first network-side device that supports I1 messages or I1 message conversion, or to instruct the network-side device to a first network-side device that supports GEO calls, or to instruct the network-side device to instruct the first terminal to support I1 messages, thereby enabling the use of I1 messages between the first terminal and the first network-side device.

[0316] In some embodiments, the first terminal may send the fifth information via the Protocol Configuration Option (PCO).

[0317] For example, a registration request, attachment request, or session establishment request may include a PCO carrying the fifth information.

[0318] In some embodiments, the first terminal receives the address information of the first network-side device during the registration, attachment, or session establishment process.

[0319] For example, after a network-side device (such as a mobility management element) receives the fifth information sent by the first terminal, it can select a network-side device (such as a PGW or SGW) and send the fifth information to the selected network-side device. Taking a PGW as an example, the PGW can select a first network-side device that supports I1 messages, or a first network-side device that supports I1 message conversion, or a first network-side device that supports GEO calls, based on the fifth information, and send the address information of the first network-side device. Correspondingly, the first terminal receives the address information of the first network-side device.

[0320] In one possible implementation, the address information of the first network-side device can be forwarded to the first terminal via a mobility management network element.

[0321] In some embodiments, during registration, attachment, or session establishment, the first terminal receives address information from the first network-side device, including:

[0322] Receive the address information of the first network-side device by registering and accepting messages; or...

[0323] Receive the address information of the first network-side device via the attach message; or...

[0324] The address information of the first network-side device is received by accepting messages through a session.

[0325] For example, during the registration process of the first terminal, the registration acceptance message may include the address information of the first network-side device, so that the first terminal receives the address information of the first network-side device through the registration acceptance message.

[0326] For example, during the attachment process of the first terminal, the attachment acceptance message may include the address information of the first network-side device, so that the first terminal receives the address information of the first network-side device through the attachment acceptance message.

[0327] For example, during the session establishment process, the session establishment acceptance message may include the address information of the first network-side device, so that the first terminal can receive the address information of the first network-side device through the session establishment acceptance message.

[0328] Optionally, the first network-side device may include an IMS AS or a P-CSCF, and this application does not limit it.

[0329] In some embodiments, the first terminal receives the address information of the first network-side device via the PCO.

[0330] For example, a registration acceptance request, an attachment acceptance request, or a session establishment acceptance request may include a PCO, which includes the address information of a first network-side device.

[0331] Therefore, in this embodiment of the application, the first terminal can successfully register, attach, or establish a session, thereby obtaining the address information of the first network-side device that supports the I1 protocol or supports I1 protocol conversion, in order to prepare for sending data packets in the future.

[0332] Figure 6B is a schematic flowchart of another call establishment method according to an embodiment of the present application. As shown in Figure 6B, the call establishment method is applied to the process of establishing a call between a first terminal and a first communication device, including the following:

[0333] S605, during the registration, attachment, or session establishment process of the first terminal, a fifth message is received from the first terminal, the fifth message indicating at least one of the following:

[0334] Discover the first network-side device that supports I1 messages;

[0335] Discover the first network-side device that supports I1 message translation;

[0336] The first network-side device supporting GEO (Geostationary Earth Orbit) calls in a high-orbit satellite communication system was discovered.

[0337] The first terminal supports I1 messages.

[0338] For example, this method can be executed by a network-side device, which may include, but is not limited to, MME, SGW / PGW, etc.

[0339] Therefore, in this embodiment of the application, the first terminal can receive a fifth message from the first terminal during the registration, attachment, or session establishment process, and can instruct the network-side device to discover a first network-side device that supports I1 messages or I1 message conversion, or instruct the network-side device to indicate a first network-side device that supports GEO calls, or instruct the network-side device to indicate that the first terminal supports I1 messages, thereby enabling the use of I1 messages between the first terminal and the first network-side device.

[0340] Optionally, the method may further include:

[0341] During the registration, attachment, or session establishment process of the first terminal, the address information of the first network-side device is sent.

[0342] For example, the first network-side device may include, but is not limited to, P-CSCF or IMS AS, etc.

[0343] Optionally, sending the address information of the first network-side device during the registration, attachment, or session establishment process of the first terminal includes:

[0344] The address information of the first network-side device is sent by registering to receive messages; or...

[0345] The address information of the first network-side device is sent by attaching the received message; or...

[0346] The address information of the first network-side device is sent by accepting messages through a session.

[0347] Optionally, receiving the fifth information from the first terminal includes:

[0348] The fifth information is received from the first terminal via the protocol configuration option PCO.

[0349] Optionally, the step of sending the address information of the first network-side device includes:

[0350] The address information of the first network-side device is sent to the first terminal via the PCO.

[0351] Specifically, this method can be applied to the registration, attachment, or session establishment process of the first terminal, as described above.

[0352] Therefore, in this embodiment of the application, the first terminal can successfully register, attach, or establish a session, thereby obtaining the address information of the first network-side device that supports the I1 protocol or supports I1 protocol conversion, in order to prepare for sending data packets in the future.

[0353] The call establishment process between the first terminal and the first communication device is described in detail below with reference to Figures 7 to 12. It should be understood that Figures 7 to 12 are described using a 4G network as an example, and this call establishment process is also applicable to 5G, 6G, 7G, or future communication networks. Specifically, the first terminal is UE-1 and the first communication device is UE-2, as an example.

[0354] Figures 7 to 9 illustrate the use of P-CSCF as an example of the first network-side device.

[0355] Figure 7 is a schematic diagram of a registration, attachment, or session establishment process according to an embodiment of this application. As shown in Figure 7, the registration, attachment, or session establishment method is applied during the process of establishing a call between a first terminal and a first communication device. The registration, attachment, or session establishment process includes at least one of the following steps S701 to S705.

[0356] S701, UE-1 sends a registration request / attachment request / PDN establishment request to the MME.

[0357] For example, UE-1 can initiate a session establishment request during the registration / attachment process, such as a PDN establishment request, or UE-1 can initiate a session establishment request independently.

[0358] One possible implementation is that the PCO can be carried in the registration process, attachment process, or PDN connection request, and the PCO can carry information #1 (an example of the fifth information above), information #1 is used to indicate or include at least one of the following:

[0359] A P-CSCF supporting I1 messages was discovered;

[0360] A P-CSCF supporting I1 message translation was discovered;

[0361] P-CSCF supporting GEO (Geostationary Orbit) satellite communication systems was discovered;

[0362] The UE supports I1 messages.

[0363] S702, MME sends a session creation request to SGW / PGW.

[0364] In one possible approach, the MME can select the SGW / PGW and send a session creation request to the SGW / PGW, carrying the PCO sent by UE-1.

[0365] For S703, SGW / PGW, a P-CSCF that supports I1 protocol conversion is selected.

[0366] Specifically, the SGW / PGW can select a P-CSCF that supports I1 protocol conversion based on information #1.

[0367] In this context, "supporting I1 protocol conversion" can also be understood or replaced as: supporting the conversion of I1 protocol to SIP protocol, or supporting the conversion between I1 protocol and SIP protocol.

[0368] S704, SGW / PGW sends a session creation response to MME.

[0369] Specifically, the SGW / PGW sends a session creation response message to the MME. One possible implementation is to include the P-CSCF address (e.g., IP address) in the response message via the PCO. Optionally, the IMS AS address (e.g., IP address) may also be included in the response message. Here, the P-CSCF or IMS AS is an example of the first network-side device mentioned above.

[0370] S705, the MME sends a registration accept / attach accept / PDN establishment accept message to UE1.

[0371] One possible implementation is that the MME sends a Registration Acceptance / Attach Acceptance / PDN Establishment Acceptance message to the UE, which may carry the PCO.

[0372] Therefore, through the above steps S701 to S705, UE-1 can successfully register, attach, or establish a session, thereby obtaining the address information of the P-CSCF that supports the I1 protocol or supports I1 protocol conversion, or obtaining the address information of the IMS AS that serves the UE, in order to prepare for the UE to send IP packets in the future.

[0373] Figure 8 is a schematic flowchart of a call establishment method according to an embodiment of the present application. As shown in Figure 8, the call establishment method is applied to the process of establishing a call between a first terminal and a first communication device. The call establishment process is the calling process of UE-1 and may include at least some of the following contents S801 to S810.

[0374] S801, PDN connection established, obtain P-CSCF address.

[0375] Specifically, the process of establishing a PDN connection and obtaining the P-CSCF address can be referred to in Figure 7.

[0376] In step S802, UE-1 sends an IP message to the P-CSCF, which includes an I1 invite. Optionally, the IP message may also include an SDP offer.

[0377] Specifically, UE-1 generates an I1 invite message and an IP message (i.e., an IP data packet). The destination address of the IP message is the address of the P-CSCF, and the payload of the IP message carries the I1 invite message. The I1 invite message is an example of the first I1 message in Figure 3, and the IP message is an example of the first IP data packet mentioned above.

[0378] Option 1 includes a call parameter indication in the I1 invite message. For details, please refer to Table 1 above for the description of the I1 Invite message. The call parameter indication is an example of the first message mentioned above.

[0379] Option 2 includes an SDP offer in the payload portion of the IP message.

[0380] For example, the SDP offer includes call parameters supported by UE-1, such as supported codec parameters, ptime, mode-set, etc. In this case, the SDP offer is an example of the first piece of information mentioned above.

[0381] It should be noted that the relevant schemes do not support carrying SDP information in I1 messages. Option 1 carries the key content of the SDP in the I1Invite message. Option 2 is another approach, which includes the complete SDP along with the I1 Invite message in the IP message payload.

[0382] Option 3 includes message #2 in the IP message payload, which instructs the P-CSCF to generate an SDP offer. Message #2 is an example of the first message mentioned above.

[0383] It's important to note that the difference between Option 3 and Option 2 is that Option 3 includes crucial information for generating the SDP offer in the IP message payload, allowing the P-CSCF to generate the SDP offer based on this information. Compared to Option 1, Option 3 does not require enhancements to the I1 protocol and involves fewer modifications to the standard.

[0384] S803 and P-CSCF perform protocol conversion.

[0385] Specifically, the P-CSCF generates a SIP Invite message based on the I1Invite message, and adds an SDP offer to the SIP Invite message. This SIP Invite message is an example of the first message in Figure 4.

[0386] Option 1: The P-CSCF generates an SDP offer based on the call parameters indicated in the I1Invite message. Therefore, by carrying all the information in a single I1Invite message, the process of the UE generating IP messages is simplified, the amount of data transmitted between the UE and the P-CSCF is reduced, and the call setup time is shortened.

[0387] Option 2: The P-CSCF adds the SDP offer contained in the IP message to the SIP Invite message. This simplifies the P-CSCF processing.

[0388] Option 3: The P-CSCF generates an SDP offer based on information #2 contained in the IP message. This eliminates the need to enhance the I1Invite message, resulting in minimal standard changes. Simultaneously, the amount of data transmitted by the UE is reduced, shortening the call setup time.

[0389] S804, P-CSCF sends an Invite message to UE-2, which includes an SDP offer.

[0390] Specifically, the P-CSCF sends the generated SIP Invite message to the peer UE-2.

[0391] S805, UE-2 sends a response message, such as message 183, to P-CSCF, which includes the SDP answer.

[0392] S806, P-CSCF establishes a dedicated EPS bearer for transmitting voice services.

[0393] Specifically, the P-CSCF establishes a dedicated EPS bearer for UE-1 for transmitting voice services based on the SDP negotiation results (such as the SDP answer).

[0394] S807 and P-CSCF perform protocol conversion.

[0395] Specifically, the P-CSCF can generate an I1 progress message based on message 183 in step S805. The I1 progress message is an example of the response message to the first I1 message in Figure 3.

[0396] Option 1: The P-CSCF, based on the SDP answer, includes an indication of the call parameters used for confirmation in the I1progress message. Specifically, the I1progress message can be found in Table 2 above. This indication of the call parameters used for confirmation is an example of the second message mentioned above.

[0397] Option 2: The P-CSCF adds the SDP answer from the 183 message to the IP message. The SDP answer in the IP message is an example of the second information mentioned above. In this way, the P-CSCF only needs to add the SDP answer from the 183 message to the IP message, simplifying the P-CSCF process.

[0398] Option 2, the P-CSCF generates information #3 based on the SDP answer. Information #3 is used to indicate the call parameters to be used. This information #3 is an example of the second information mentioned above.

[0399] S808, the P-CSCF sends an IP message to UE-1, which includes the I1 progress. Optionally, the IP message may also include the SDP answer.

[0400] Specifically, the P-CSCF sends an IP message containing an I1progress message to UE-1. The I1progress message is carried in the payload portion of this IP message. Optionally, the payload portion of this IP message may also contain the SDP answer in Option 2 or information #3 in Option 3. This IP message is an example of the second IP packet in Figure 3.

[0401] S809, UE-2 sends 200 OK to P-CSCF.

[0402] Specifically, UE-2 receives the incoming call from UE-1 and sends a SIP 200 OK message.

[0403] S810, P-CSCF sends an IP message to UE-1, which includes an I1 connection message.

[0404] Specifically, the P-CSCF generates an I1connecting message based on the SIP 200OK message and sends the I1connecting message to UE-1 by carrying it in the payload of the IP message.

[0405] Therefore, in this embodiment of the application, UE-1 can initiate a call request using I1 messages, and P-CSCF can perform the conversion from I1 protocol to SIP protocol to realize the negotiation of call parameters between UE1 and UE2. This enables the terminal to access the network using smaller I1 messages, which is beneficial for shorter call setup time and improved user experience.

[0406] Figure 9 is a schematic flowchart of another call establishment method according to an embodiment of this application. As shown in Figure 9, the call establishment method is applied to the process of establishing a call between a first terminal and a first communication device. The call establishment process is the called process of UE-1 and may include at least some of the following contents S901 to S911.

[0407] S901, PDN connection establishment complete.

[0408] Specifically, the process of establishing a PDN connection and obtaining the P-CSCF is described in Figure 7.

[0409] S902, UE-2 sends an Invite message to S-CSCF, which includes the UE-1 URI and SDP offer.

[0410] Specifically, UE-2 can initiate a call request to UE-1 via a SIP Invite message, the destination address of which is the UE's SIP URI. This SIP Invite message can be routed via the S-CSCF-2 serving UE-2 to the S-CSCF-1 serving UE-1.

[0411] S903, the S-CSCF sends an Invite message to the P-CSCF, which includes the UE-1 IP address and SDP offer.

[0412] Specifically, the S-CSCF-1 serving UE-1 replaces the SIP URI of the Invite message with the IP address of UE-1 and sends the Invite message to the P-CSCF-1 serving UE-1. This Invite message is an example of the second message in Figure 5 above.

[0413] S904 and P-CSCF perform protocol conversion.

[0414] Specifically, the P-CSCF serving UE-1 generates an I1 Invite message and an IP message (i.e., an IP packet) based on the SIP Invite message. The destination address of this IP message is the address of UE-1 (such as its IP address), and the payload of the IP message carries the I1 Invite message. The I1 Invite message is an example of the second I1 message in Figure 3, and the IP message is an example of the third IP packet mentioned above.

[0415] Option 1 includes a call parameter indication in the I1 message. For details, refer to Table 1 above for the I1 Invite message description. This call parameter indication is an example of the third message mentioned above.

[0416] Option 2 includes an SDP offer in the payload portion of the IP message.

[0417] For example, the P-CSCF can add the SDP offer carried in the Invite message in step S903 to the IP message. This SDP offer can be carried in the payload portion of the IP message. This SDP offer is an example of the third information mentioned above.

[0418] It should be noted that the relevant schemes do not support carrying SDP information in I1 messages. Option 1 carries the key content of the SDP in the I1Invite message. Option 2 is another approach, which includes the complete SDP along with the I1 invite message in the payload of the IP message.

[0419] Option 3, the IP message payload also includes message #4, which indicates the call parameters used in this call.

[0420] It should be noted that the difference between Option 3 and Option 2 is that Option 3 includes the key information of the SDP offer in the payload of the IP message, so that UE-1 can obtain the requested call parameters based on this information. Compared to Option 1, Option 3 does not require enhancement to the I1 protocol and involves less modification to the standard.

[0421] For example, the P-CSCF can obtain the call parameter indication for this call based on the SDP offer carried in the Invite message in step S903.

[0422] S905, the P-CSCF sends an IP message to UE-1, which includes an I1 Invite. Optionally, the IP message may also include an SDP offer.

[0423] S906, UE-1 sends an IP message to the P-CSCF, which includes the I1 process. Optionally, the IP message may also include an SDP answer.

[0424] Specifically, UE-1 generates an I1 progress response message to the IP Invite message, and also generates an IP message. The I1 progress message is an example of a response message to the second I1 message, and the IP message is an example of a fourth data packet.

[0425] Option 1 includes a call parameter indication in the I1 progress message to confirm the current call. For details, please refer to Table 2 above. The call parameter indication used for this confirmation is an example of the fourth message mentioned above.

[0426] Option 2 includes an SDP answer in the IP message payload. This SDP answer in the IP message is an example of the fourth piece of information mentioned above.

[0427] Option 3 includes message #5 in the IP message payload. Message #5 indicates the call parameters to be used. This message #5 is an example of the fourth message mentioned above.

[0428] S907, P-CSCF establishes a dedicated EPS bearer for transmitting voice services.

[0429] Specifically, the P-CSCF establishes a dedicated EPS bearer for UE-1 for transmitting voice services based on the SDP negotiation results (such as the SDP answer).

[0430] S908 and P-CSCF perform protocol conversion.

[0431] Specifically, the P-CSCF can generate a SIP 183 message containing an SDP answer based on the IP message in step S906, such as the I1 progress message, optionally an SDP answer, or information #5. This SIP 183 message is an example of a response message to the second message in Figure 5.

[0432] S909, P-CSCF sends Message 183 to UE-2, which includes the SDP answer.

[0433] S910, UE-1 sends an IP message to P-CSCF, which includes I1 connecting.

[0434] Specifically, when the user of UE-1 accepts the call request, UE-1 generates an I1 connecting message and sends the I1 connecting message in the payload of the IP message to the P-CSCF.

[0435] S911, P-CSCF sends a 200 OK message to UE-2.

[0436] Specifically, the P-CSCF converts the IP message into a SIP 200OK message and sends it to UE-2.

[0437] Therefore, in this embodiment of the application, UE-1 can use I1 messages to accept call requests, and P-CSCF can perform the conversion from I1 protocol to SIP protocol to realize the negotiation of call parameters between UE1 and UE2. This enables the terminal to access the network using a smaller number of I1 messages, which is beneficial for shorter call setup time and improved user experience.

[0438] Figures 10 to 12 illustrate the example of an IMS AS as the first network-side device.

[0439] Figure 10 is a schematic diagram of a registration process according to an embodiment of the present application. As shown in Figure 10, the registration process is applied during the process of establishing a call between a first terminal and a second terminal. The registration process includes at least one of the following steps S1001 to S1006.

[0440] S1001, UE-1 sends a registration request to P-CSCF.

[0441] For example, UE-1 can initiate an IMS registration process. For instance, UE-1 can initiate this registration request via a SIP registration message. Optionally, the registration request message may include information such as UE-1's SIP URI and IP address.

[0442] S1002, P-CSCF sends a registration request to S-CSCF.

[0443] Specifically, the P-CSCF providing services to UE-1 routes the registration request to the S-CSCF based on UE-1's domain name information.

[0444] S1003, S-CSCF sends a registration request to IMS AS.

[0445] Specifically, the S-CSCF records the mapping between UE-1's SIP URI and IP address. Based on UE-1's subscription information, it sends a registration request message to the IMS AS that provides services to UE-1, which carries information such as UE-1's SIP URI and IP address.

[0446] Optionally, the S-CSCF also sends the address information of the P-CSCF to the IMS AS. In one implementation, the P-CSCF address information can be carried in the registration request message.

[0447] S1004, IMS AS sends a 200 OK message to S-CSCF.

[0448] Specifically, the 200 OK message can be a registration acceptance message.

[0449] S1005, S-CSCF sends a 200 OK message to P-CSCF.

[0450] Specifically, the 200 OK message can carry the address information of the IMS AS (such as its IP address).

[0451] S1006, P-CSCF sends a 200 OK message to UE-1.

[0452] After receiving the 200 OK message, UE-1 records the address information of the IMS AS that provides services to UE-1.

[0453] Therefore, after going through the above steps S1001 to S1006, UE-1 can successfully register with IMS and obtain the address information of IMS AS, thus preparing for the UE to send IP packets in the future.

[0454] Figure 11 is a schematic flowchart of a call establishment method according to an embodiment of the present application. As shown in Figure 11, the call establishment method is applied to the process of establishing a call between a first terminal and a first communication device. The call establishment process is the calling process of UE-1 and may include at least some of the following contents S1101 to S1111.

[0455] S1101, UE-1 registers and obtains the address of IMS AS.

[0456] Specifically, the process of UE-1 registering and obtaining the address of the IMS AS can be referred to in Figure 7 or Figure 10.

[0457] S1102, UE-1 sends an IP message to the IMS AS, which includes an I1 Invite. Optionally, the IP message may also include an SDP offer.

[0458] Specifically, step S1102 is similar to step S802 in Figure 8, and can be found in the relevant description in Figure 8. The difference from Figure 8 is that the destination address of this IP message is the IP address of the IMS AS.

[0459] S1103, IMS AS performs protocol conversion.

[0460] Specifically, step S1103 is similar to step S803 in Figure 8, and can be found in the relevant description in Figure 8. The difference from Figure 8 is that this step is performed by the IMS AS.

[0461] S1104, IMS AS sends an Invite message to UE-2, which includes an SDP offer.

[0462] Specifically, the IMS AS sends the generated SIP Invite message to the peer UE-1.

[0463] S1105, UE-2 sends a response message, such as message 183, to the IMS AS, which includes the SDP answer.

[0464] S1106, IMS AS sends a message to P-CSCF, which includes the SDP negotiation result.

[0465] For example, the message may include an SDP answer. Optionally, the message may also include UE-1 information, such as a SIP URI or IP address. This message is an example of the third message mentioned above.

[0466] In some implementations, the message can be a SIP MESSAGE, SIP INFO, SIP UPDATE, or SIPre-Invite message, etc., without limitation.

[0467] S1107, P-CSCF establishes a dedicated EPS bearer for transmitting voice services.

[0468] S1108, IMS AS performs protocol conversion.

[0469] S1109, the IMS AS sends an IP message to UE 1, which includes the I1 progress. Optionally, the IP message may also include the SDP answer.

[0470] S1110, UE-2 sends 200 OK to IMS AS.

[0471] S1111, IMS AS sends an IP message to UE-1, which includes I1 connecting.

[0472] Specifically, steps S1108-S1111 are similar to steps S807-S810 in Figure 8, and can be referred to the relevant description above. The difference from Figure 8 is that in steps S1108-S1111, the IMS AS replaces the P-CSCF in performing the corresponding actions.

[0473] Therefore, in this embodiment of the application, UE-1 can initiate a call request using I1 messages, and IMS AS can perform the conversion from I1 protocol to SIP protocol to realize the negotiation of call parameters between UE1 and UE2, so as to realize the terminal access to the network using smaller I1 messages, which is beneficial to reduce the call establishment time and improve the user experience.

[0474] Figure 12 is a schematic flowchart of another call establishment method according to an embodiment of this application. As shown in Figure 12, the call establishment method is applied to the process of establishing a call between a first terminal and a first communication device. The call establishment process is the called process of UE-1 and may include at least some of the following contents S1201 to S1212.

[0475] S1201, UE-1 performs IMS registration and obtains the address of IMS AS.

[0476] S1202, UE-2 sends an Invite message to S-CSCF, which includes the UE-1 URI and SDP offer.

[0477] S1203, S-CSCF sends an Invite message to IMS AS, which includes the UE-1 IP address and SDP offer.

[0478] S1204, IMS AS performs protocol conversion.

[0479] S1205, the IMS AS sends an IP message to UE-1, which includes an I1 Invite. Optionally, the IP message may also include an SDP offer.

[0480] S1206, UE-1 sends an IP message to the IMS AS, which includes the I1 process. Optionally, the IP message may also include an SDP answer.

[0481] Specifically, steps S1202 to S1206 are similar to steps S902 to S906 in Figure 9, and can be referred to the relevant description in Figure 9. The difference from Figure 9 is that in steps S1202 to S1206, the IMS AS replaces the P-CSCF in performing the relevant actions.

[0482] S1207, IMS AS sends a message to P-CSCF, which includes the SDP result.

[0483] S1208, P-CSCF establishes a dedicated EPS bearer for transmitting voice services.

[0484] Specifically, steps S1207-S1208 are similar to steps S1106 to S1107 in Figure 11, and can be referred to the relevant description in Figure 11.

[0485] S1209, IMAS AS performs protocol conversion.

[0486] S1210, IMS AS sends Message 183 to UE-2, which includes the SDP answer.

[0487] S1211, UE-1 sends an IP message to the IMS AS, which includes I1 connecting.

[0488] S1212, IMS AS sends a 200 OK message to UE-2.

[0489] Specifically, steps S1209 to S1212 are similar to steps S908 to S911 in Figure 9, and can be referred to the relevant description in Figure 9. The difference from Figure 9 is that in steps S1209 to S1212, the IMS AS replaces the P-CSCF in performing the relevant actions.

[0490] Therefore, in this embodiment of the application, UE-1 can use I1 messages to accept call requests, and IMS AS can perform the conversion from I1 protocol to SIP protocol to realize the negotiation of call parameters between UE1 and UE2, so as to realize the terminal access to the network using smaller I1 messages, which is beneficial to reduce the call establishment time and improve the user experience.

[0491] The call establishment method provided in this application can be executed by a call establishment device. This application uses an example of a call establishment device executing a communication establishment method to illustrate the call establishment device provided in this application.

[0492] This application provides a call establishment apparatus. As an example, the call establishment apparatus may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0493] The device for establishing a call includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include a general-purpose processor, a special-purpose processor, such as a Central Processing Unit (CPU), a microprocessor, a Digital Signal Processor (DSP), an Artificial Intelligence (AI) processor, a Graphics Processing Unit (GPU), an Application Specific Integrated Circuit (ASIC), a Network Processor (NP), a Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, buses, radio frequency units, etc.

[0494] Specifically, referring to Figure 13, when the device for establishing a call is a first network-side device or a component of the first network-side device, the device for establishing a call 1300 includes a receiving module 1301 or a sending module 1302.

[0495] During the process of establishing a call between the first terminal and the first communication device, the receiving module 1301 or the sending module 1302 performs a first operation, which includes at least one of the following:

[0496] Receive a first I1 message and first information from the first terminal, wherein the first I1 message is used by the first terminal to request the first communication device to establish a call, and the first information is used to indicate the call parameters to be used; send a response message and second information to the first terminal, wherein the second information is used to indicate the call parameters to be used.

[0497] Send a second I1 message and a third message to the first terminal. The second I1 message is used by the first communication device to request the first terminal to establish a call, and the third message is used to indicate the call parameters to be used. Receive a response message and a fourth message from the first terminal regarding the second I1 message. The fourth message is used to indicate the call parameters to be used.

[0498] Optionally, in some embodiments, at least one of the following is satisfied:

[0499] The first I1 message includes the first information;

[0500] The response message to the first I1 message includes the second information;

[0501] The second I1 message includes the third information;

[0502] The response message to the second I1 message includes the fourth information.

[0503] Optionally, in some embodiments, at least one of the following is satisfied:

[0504] The first information includes a first Session Description Protocol (SDP) invitation, and the first SDP invitation includes call parameters requested by the first terminal.

[0505] The second information includes a first SDP response, which includes call parameters selected and used by the first communication device or the second network-side device.

[0506] The third information includes a second SDP invitation, which includes call parameters requested by the first communication device or the second network-side device.

[0507] The fourth information includes a second SDP response, which includes the call parameters selected by the first terminal.

[0508] Optionally, in some embodiments, at least one of the following is satisfied:

[0509] The first information is used to indicate the call parameters supported by the first terminal;

[0510] The second information is used to indicate the call parameters supported by the first communication device or the call parameters supported by the second network-side device;

[0511] The third information is used to indicate the call parameters supported by the first communication device or the call parameters supported by the second network-side device.

[0512] The fourth piece of information is used to indicate the call parameters supported by the first terminal.

[0513] Optionally, in some embodiments, the sending module 1302 is further configured to:

[0514] According to the first I1 message, a first message is sent to the first communication device, and the first message is used by the device to request the first communication device to establish the call.

[0515] Optionally, in some embodiments, the sending module 1302 is specifically used for:

[0516] Upon receiving a response message from the first communication device in response to the first message, the response message to the first I1 message and the second information are sent to the first terminal.

[0517] Optionally, in some embodiments, the receiving module 1301 is further configured to:

[0518] Receive a second message from the first communication device, the second message being used by the first communication device to request the first terminal to establish a call;

[0519] Specifically, the sending module is used for:

[0520] According to the second message, the second I1 message and the third information are sent to the first terminal.

[0521] Optionally, in some embodiments, the receiving module 1301 is further configured to:

[0522] Based on the response message of the second I1 message and the fourth information, a response message of the second message is sent to the first communication device.

[0523] Optionally, in some embodiments, a building module is also included, for:

[0524] Establish a bearer for transmitting call services on the first terminal.

[0525] Optionally, in some embodiments, the sending module 1302 is further configured to:

[0526] A third message is sent to a third network-side device, the third message being used to instruct the third network-side device to establish a bearer for the first terminal to transmit call services.

[0527] Optionally, in some embodiments, the receiving module 1301 is specifically used for:

[0528] The device receives a first IP data packet from the first terminal, the first IP data packet including the first I1 message, the first information, and the address information of the device.

[0529] Optionally, in some embodiments, the receiving module 1301 is further configured to:

[0530] Receive a registration request message related to the first terminal and the address information of the third network-side device, wherein the registration request message includes information about the first terminal;

[0531] The sending module is further configured to send a response message to the registration request message, the response message of which includes the address information of the device.

[0532] Optionally, in some embodiments, the call parameters include at least one of encoding / decoding parameters and packet time ptime.

[0533] In this embodiment, the first network-side device receives a first I1 message and first information from the first terminal, or sends a response message and second information to the first terminal, or sends a second I1 message and third information to the first terminal, or receives a response message and fourth information from the second I1 message from the first terminal. This enables the device to request the establishment of a call between the first terminal and the first communication device through I1 messages, and to transmit call parameters between the first terminal and the first communication device through relevant information. This allows the terminal to access the network using a smaller number of I1 messages, which helps to reduce the call setup time and improve the user experience.

[0534] Referring to Figure 14, when the device for establishing a call is a first terminal or a component in the first terminal, the device 1400 for establishing a call includes a receiving module 1401 or a sending module 1402.

[0535] During the process of establishing a call between the device and the first communication device, the sending module 1402 or the receiving module 1401 performs a second operation, which includes at least one of the following:

[0536] Send a first I1 message and first information to a first network-side device, wherein the first I1 message is used by the device to request the first communication device to establish a call, and the first information is used to indicate the call parameters to be used; receive a response message and second information from the first I1 message from the first network-side device, wherein the second information is used to indicate the call parameters to be used;

[0537] The device receives a second I1 message and a third message from the first network-side device. The second I1 message is used by the first communication device to request the device to establish a call, and the third message is used to indicate the call parameters to be used. The device then sends a response message to the second I1 message and a fourth message to the first network-side device. The fourth message is used to indicate the call parameters to be used.

[0538] Optionally, in some embodiments, at least one of the following is satisfied:

[0539] The first I1 message includes the first information;

[0540] The response message to the first I1 message includes the second information;

[0541] The second I1 message includes the third information;

[0542] The response message to the second I1 message includes the fourth information.

[0543] Optionally, in some embodiments, at least one of the following is satisfied:

[0544] The first information includes a first Session Description Protocol (SDP) invitation, which includes call parameters requested by the device.

[0545] The second information includes a first SDP response, which includes call parameters selected and used by the first communication device or the second network-side device.

[0546] The third information includes a second SDP invitation, which includes call parameters requested by the first communication device or the second network-side device.

[0547] The fourth information includes a second SDP response, which includes the call parameters selected by the device.

[0548] Optionally, in some embodiments, at least one of the following is satisfied:

[0549] The first information is used to indicate the call parameters supported by the device;

[0550] The second information is used to indicate the call parameters supported by the first communication device or the call parameters supported by the second network-side device;

[0551] The third information is used to indicate the call parameters supported by the first communication device or the call parameters supported by the second network-side device.

[0552] The fourth piece of information is used to indicate the call parameters supported by the device.

[0553] Optionally, in some embodiments, the sending module 1402 is specifically used for:

[0554] Send a first IP data packet to the first network-side device. The first IP data packet includes the first I1 message, the first information, and the address information of the first network-side device.

[0555] Optionally, in some embodiments, the sending module 1402 is further configured to:

[0556] Send the IMS registration request message related to the device;

[0557] The receiving module is further configured to receive a response message to the IMS registration request message, the response message of which includes the address information of the first network-side device.

[0558] Optionally, in some embodiments, the sending module 1402 is further configured to:

[0559] During registration, attachment, or session establishment, the device sends a fifth message, which indicates at least one of the following:

[0560] Discover the first network-side device that supports I1 messages;

[0561] Discover the first network-side device that supports I1 message translation;

[0562] The first network-side device supporting GEO (Geostationary Earth Orbit) calls in a high-orbit satellite communication system was discovered.

[0563] The device supports I1 messages.

[0564] Optionally, in some embodiments, the receiving module 1401 is further configured to:

[0565] During the registration, attachment, or session establishment process, the device receives the address information of the first network-side device.

[0566] Optionally, in some embodiments, the receiving module 1401 is specifically used for:

[0567] Receive the address information of the first network-side device by registering and accepting messages; or...

[0568] Receive the address information of the first network-side device by attaching and receiving messages; or...

[0569] The address information of the first network-side device is received by accepting messages through a session.

[0570] Optionally, in some embodiments, the sending module 1402 is specifically used for:

[0571] The fifth message is sent via the protocol configuration option PCO.

[0572] Optionally, in some embodiments, the receiving module 1401 is specifically used for:

[0573] The address information of the first network-side device is received through the PCO.

[0574] In this embodiment, the first terminal sends a first I1 message and first information to the first network-side device, or receives a response message and second information from the first I1 message from the first network-side device, or receives a second I1 message and third information from the first network-side device, or sends a response message and fourth information to the first network-side device. This enables the establishment of a call between the first terminal and the first communication device through I1 messages, and the transmission of call parameters between the first terminal and the first communication device through relevant information. This allows the terminal to access the network using a smaller number of I1 messages, which helps to reduce the call establishment time and improve the user experience.

[0575] Furthermore, in this embodiment of the application, the first terminal can send a fifth message during the registration, attachment, or session establishment process to instruct the network-side device to discover a first network-side device that supports I1 messages or I1 message conversion, or to instruct the network-side device to a first network-side device that supports GEO calls, or to instruct the network-side device to instruct the first terminal to support I1 messages, thereby enabling the use of I1 messages between the first terminal and the first network-side device.

[0576] Referring to Figure 15, when the call establishment device is a fourth network-side device or a component of the fourth network-side device, the call establishment device 1500 includes a receiving module 1501.

[0577] The receiving module 1501 is configured to: receive fifth information from the first terminal during the registration, attachment, or session establishment process of the first terminal, the fifth information being used to indicate at least one of the following:

[0578] Discover the first network-side device that supports I1 messages;

[0579] Discover the first network-side device that supports I1 message translation;

[0580] The first network-side device supporting GEO (Geostationary Earth Orbit) calls in a high-orbit satellite communication system was discovered.

[0581] The first terminal supports I1 messages.

[0582] Optionally, the device further includes a transmitting module 1502, used for:

[0583] During the registration, attachment, or session establishment process of the first terminal, the address information of the first network-side device is sent.

[0584] Optionally, the sending module 1502 is specifically used for:

[0585] The address information of the first network-side device is sent by registering to receive messages; or...

[0586] The address information of the first network-side device is sent by attaching the received message; or...

[0587] The address information of the first network-side device is sent by accepting messages through a session.

[0588] Optionally, the receiving module 1501 is specifically used for:

[0589] The fifth information is received from the first terminal via the protocol configuration option PCO.

[0590] Optionally, the sending module 1502 is specifically used for:

[0591] The address information of the first network-side device is sent to the first terminal via the PCO.

[0592] Therefore, in this embodiment of the application, the first terminal can receive a fifth message from the first terminal during the registration, attachment, or session establishment process, and can instruct the network-side device to discover a first network-side device that supports I1 messages or I1 message conversion, or instruct the network-side device to indicate a first network-side device that supports GEO calls, or instruct the network-side device to indicate that the first terminal supports I1 messages, thereby enabling the use of I1 messages between the first terminal and the first network-side device.

[0593] The call establishment apparatus provided in this application embodiment can implement the various processes implemented in the method embodiments of Figures 3 to 12 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0594] As shown in Figure 16, this application embodiment also provides a communication device 1600, including a processor 1601 and a memory 1602. The memory 1602 stores a program or instructions that can run on the processor 1601. For example, when the communication device 1600 is a terminal, the program or instructions executed by the processor 1601 implement the various steps of the first terminal in the above-described call establishment method embodiment, and achieve the same technical effect. When the communication device 1600 is a network-side device, the program or instructions executed by the processor 1601 implement the various steps of the first network-side device in the above-described call establishment method embodiment, and achieve the same technical effect. To avoid repetition, this will not be described again here.

[0595] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the first terminal in the method embodiments shown in Figures 3 to 12. This terminal embodiment corresponds to the above-described terminal-side method embodiments, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. The terminal can be the device shown in Figure 14. Specifically, Figure 17 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0596] The terminal 1700 includes, but is not limited to, at least some of the following components: radio frequency unit 1701, network module 1702, audio output unit 1703, input unit 1704, sensor 1705, display unit 1706, user input unit 1707, interface unit 1708, memory 1709, and processor 1710.

[0597] Those skilled in the art will understand that terminal 1700 may also include a power supply (such as a battery) for powering various components. The power supply may be logically connected to processor 1710 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 17 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0598] It should be understood that, in this embodiment, the input unit 1704 may include a graphics processor 17041 and a microphone 17042. The graphics processor 17041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1706 may include a display panel 17061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1707 includes at least one of a touch panel 17071 and other input devices 17072. The touch panel 17071 is also called a touch screen. The touch panel 17071 may include a touch detection device and a touch controller. Other input devices 17072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0599] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1701 can transmit it to the processor 1710 for processing; in addition, the radio frequency unit 1701 can send uplink data to the network-side device. Typically, the radio frequency unit 1701 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0600] The memory 1709 can be used to store software programs or instructions, as well as various data. The memory 1709 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1709 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 1709 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0601] Processor 1710 may include one or more processing units; optionally, processor 1710 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1710.

[0602] During the process of establishing a call between the first terminal and the first communication device, the radio frequency unit 1701 performs a second operation, which includes at least one of the following:

[0603] The first terminal sends a first I1 message and first information to the first network-side device. The first I1 message is used by the first terminal to request the first communication device to establish a call, and the first information is used to indicate the call parameters to be used. The first terminal receives a response message and second information from the first network-side device for the first I1 message, and the second information is used to indicate the call parameters to be used.

[0604] The first terminal receives a second I1 message and a third information from the first network-side device. The second I1 message is used by the first communication device to request the first terminal to establish a call, and the third information is used to indicate the call parameters to be used. The first terminal sends a response message to the second I1 message and a fourth information to the first network-side device. The fourth information is used to indicate the call parameters to be used.

[0605] In this embodiment, the first terminal sends a first I1 message and first information to the first network-side device, or receives a response message and second information from the first I1 message from the first network-side device, or receives a second I1 message and third information from the first network-side device, or sends a response message and fourth information to the first network-side device. This enables the establishment of a call between the first terminal and the first communication device through I1 messages, and the transmission of call parameters between the first terminal and the first communication device through relevant information. This allows the terminal to access the network using a smaller number of I1 messages, which helps to reduce the call establishment time and improve the user experience.

[0606] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be described again here.

[0607] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the first network-side device in the method embodiments shown in Figures 3 to 12. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effects.

[0608] Specifically, this application also provides a network-side device. As shown in FIG18, the network-side device 1800 includes a processor 1801, a network interface 1802, and a memory 1803. The network-side device may be the device shown in FIG13. The network interface 1802 is, for example, a Common Public Radio Interface (CPRI).

[0609] The network interface 1802 is used to perform a first operation during the process of establishing a call between the first terminal and the first communication device, the first operation including at least one of the following:

[0610] The first network-side device receives a first I1 message and first information from the first terminal. The first I1 message is used by the first terminal to request the first communication device to establish a call, and the first information is used to indicate the call parameters to be used. The first network-side device sends a response message and second information to the first terminal, and the second information is used to indicate the call parameters to be used.

[0611] The first network-side device sends a second I1 message and a third information to the first terminal. The second I1 message is used by the first communication device to request the first terminal to establish a call, and the third information is used to indicate the call parameters to be used. The first network-side device receives a response message and a fourth information from the second I1 message sent by the first terminal. The fourth information is used to indicate the call parameters to be used.

[0612] In addition, the network-side device 1800 of this application embodiment also includes: a program or instructions stored in the memory 1803 and executable on the processor 1801. The processor 1801 calls the program or instructions in the memory 1803 to execute the methods executed by the modules shown in FIG3 to FIG12 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0613] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described call establishment method embodiment and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0614] The processor mentioned above is either the processor in the terminal described in the above embodiments or the processor in the network-side device. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0615] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described call establishment method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0616] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0617] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described call establishment method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0618] This application also provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to perform the steps executed by the first terminal in the call establishment method described above, and the network-side device can be used to perform the steps executed by the first network-side device in the call establishment method described above.

[0619] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0620] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.), and the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0621] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A method for establishing a call, comprising: During the process of establishing a call between the first terminal and the first communication device, the first network-side device performs a first operation, which includes at least one of the following: The first network-side device receives a first I1 message and a first information from the first terminal. The first I1 message is used by the first terminal to request the first communication device to establish a call, and the first information is used to indicate the call parameters to be used. The first network-side device sends a response message to the first I1 message and second information to the first terminal, wherein the second information is used to indicate the call parameters to be used. The first network-side device sends a second I1 message and a third information to the first terminal. The second I1 message is used by the first communication device to request the first terminal to establish a call, and the third information is used to indicate the call parameters to be used. The first network-side device receives a response message to the second I1 message sent by the first terminal and fourth information, wherein the fourth information is used to indicate the call parameters to be used.

2. The method of claim 1, wherein, The method satisfies at least one of the following: The first I1 message includes the first information; The response message to the first I1 message includes the second information; The second I1 message includes the third information; The response message to the second I1 message includes the fourth information.

3. The method of claim 1, wherein, The method satisfies at least one of the following: The first information includes a first Session Description Protocol (SDP) invitation, and the first SDP invitation includes call parameters requested by the first terminal. The second information includes a first SDP response, which includes call parameters selected and used by the first communication device or the second network-side device. The third information includes a second SDP invitation, which includes call parameters requested by the first communication device or the second network-side device. The fourth information includes a second SDP response, which includes the call parameters selected by the first terminal.

4. The method of claim 1, wherein, The method satisfies at least one of the following: The first information is used to indicate the call parameters supported by the first terminal; The second information is used to indicate the call parameters supported by the first communication device or the call parameters supported by the second network-side device; The third information is used to indicate the call parameters supported by the first communication device or the call parameters supported by the second network-side device. The fourth piece of information is used to indicate the call parameters supported by the first terminal.

5. The method according to any one of claims 1 to 4, wherein, Also includes: According to the first I1 message, a first message is sent to the first communication device. The first message is used by the first network-side device to request the first communication device to establish the call.

6. The method of claim 5, wherein, The first network-side device sends a response message to the first I1 message and second information to the first terminal, including: Upon receiving a response message from the first communication device in response to the first message, the first network-side device sends a response message to the first I1 message and the second information to the first terminal.

7. The method according to any one of claims 1-4, further comprising: Receive a second message from the first communication device, the second message being used by the first communication device to request the first terminal to establish a call; The first network-side device sends a second I1 message and third information to the first terminal, including: The first network-side device sends the second I1 message and the third information to the first terminal based on the second message.

8. The method of claim 7, wherein, Also includes: Based on the response message of the second I1 message and the fourth information, a response message of the second message is sent to the first communication device.

9. The method of any one of claims 1-8, wherein, Also includes: Establish a bearer for transmitting call services on the first terminal.

10. The method of claim 9, wherein, Also includes: A third message is sent to a third network-side device, the third message being used to instruct the third network-side device to establish a bearer for the first terminal to transmit call services.

11. The method of any one of claims 1-10, wherein, The first network-side device receives a first I1 message and first information from the first terminal, including: The first network-side device receives a first IP data packet from the first terminal. The first IP data packet includes the first I1 message, the first information, and the address information of the first network-side device.

12. The method of any one of claims 1-11, wherein, Also includes: Receive a registration request message related to the first terminal and the address information of the third network-side device, wherein the registration request message includes information about the first terminal; Send a response message to the registration request message, the response message including the address information of the first network-side device.

13. The method of any one of claims 1-12, wherein, The call parameters include at least one of the following: encoding / decoding parameters and packet time ptime.

14. A method for establishing a call, comprising: During the process of establishing a call between the first terminal and the first communication device, the first terminal performs a second operation, the second operation including at least one of the following: The first terminal sends a first I1 message and first information to the first network-side device. The first I1 message is used by the first terminal to request the first communication device to establish a call, and the first information is used to indicate the call parameters to be used. The first terminal receives a response message and second information from the first network-side device for the first I1 message, the second information being used to indicate the call parameters to be used; The first terminal receives a second I1 message and a third information from the first network-side device. The second I1 message is used by the first communication device to request the first terminal to establish a call, and the third information is used to indicate the call parameters to be used. The first terminal sends a response message to the second I1 message and a fourth information to the first network-side device. The fourth information is used to indicate the call parameters to be used.

15. The method of claim 14, wherein, The method satisfies at least one of the following: The first I1 message includes the first information; The response message to the first I1 message includes the second information; The second I1 message includes the third information; The response message to the second I1 message includes the fourth information.

16. The method of claim 14, wherein, The method satisfies at least one of the following: The first information includes a first Session Description Protocol (SDP) invitation, and the first SDP invitation includes call parameters requested by the first terminal. The second information includes a first SDP response, which includes call parameters selected and used by the first communication device or the second network-side device. The third information includes a second SDP invitation, which includes call parameters requested by the first communication device or the second network-side device. The fourth information includes a second SDP response, which includes the call parameters selected by the first terminal.

17. The method of claim 14, wherein, The method satisfies at least one of the following: The first information is used to indicate the call parameters supported by the first terminal; The second information is used to indicate the call parameters supported by the first communication device or the call parameters supported by the second network-side device; The third information is used to indicate the call parameters supported by the first communication device or the call parameters supported by the second network-side device. The fourth piece of information is used to indicate the call parameters supported by the first terminal.

18. The method of any one of claims 14-17, wherein, The first terminal sends a first I1 message and first information to the first network-side device, including: The first terminal sends a first IP data packet to the first network-side device. The first IP data packet includes the first I1 message, the first information, and the address information of the first network-side device.

19. The method of any one of claims 14-18, wherein, Also includes: Send a registration request message for the IP Multimedia Subsystem (IMS) associated with the first terminal; A response message to the IMS registration request message is received, wherein the response message to the IMS registration request message includes the address information of the first network-side device.

20. The method of any one of claims 14-19, wherein, Also includes: During the registration, attachment, or session establishment process, the first terminal sends a fifth message, which indicates at least one of the following: Discover the first network-side device that supports I1 messages; Discover the first network-side device that supports I1 message translation; The first network-side device supporting GEO (Geostationary Earth Orbit) calls in a high-orbit satellite communication system was discovered. The first terminal supports I1 messages.

21. The method of any one of claims 14-20, wherein, Also includes: During the registration, attachment, or session establishment process, the first terminal receives the address information of the first network-side device.

22. The method of claim 21, wherein, During the registration, attachment, or session establishment process, the first terminal receives address information from the first network-side device, including: Receive the address information of the first network-side device by registering and accepting messages; or... Receive the address information of the first network-side device by attaching and receiving messages; or... The address information of the first network-side device is received by accepting messages through a session.

23. The method of claim 20, wherein, Sending the fifth information includes: The first terminal sends the fifth information through the Protocol Configuration Option (PCO).

24. The method of claim 21 or 22, wherein, The receipt of the address information from the first network-side device includes: The first terminal receives the address information of the first network-side device through the PCO.

25. An apparatus for call setup, comprising: Receive module or transmit module; During the process of establishing a call between the first terminal and the first communication device, the receiving module or the sending module performs a first operation, the first operation including at least one of the following: Receive a first I1 message and a first information from the first terminal. The first I1 message is used by the first terminal to request the first communication device to establish a call, and the first information is used to indicate the call parameters to be used. Send a response message to the first I1 message and second information to the first terminal, wherein the second information is used to indicate the call parameters to be used; Send a second I1 message and a third information to the first terminal. The second I1 message is used by the first communication device to request the first terminal to establish a call. The third information is used to indicate the call parameters to be used. The system receives a response message to the second I1 message sent by the first terminal and a fourth message, wherein the fourth message is used to indicate the call parameters to be used.

26. The apparatus of claim 25, wherein, The sending module is also used for: According to the first I1 message, a first message is sent to the first communication device, and the first message is used by the device to request the first communication device to establish the call.

27. The apparatus of claim 26, wherein, The sending module is specifically used for: Upon receiving a response message from the first communication device in response to the first message, the response message to the first I1 message and the second information are sent to the first terminal.

28. The apparatus of claim 25, further wherein the receiving module is configured to: Receive a second message from the first communication device, the second message being used by the first communication device to request the first terminal to establish a call; wherein The sending module is specifically used for: According to the second message, the second I1 message and the third information are sent to the first terminal.

29. The apparatus of claim 28, wherein, The receiving module is also used for: Based on the response message of the second I1 message and the fourth information, a response message of the second message is sent to the first communication device.

30. The apparatus of claim 25, wherein, The sending module is also used for: A third message is sent to a third network-side device, the third message being used to instruct the third network-side device to establish a bearer for the first terminal to transmit call services.

31. The apparatus of any of claims 25-30, wherein, The receiving module is specifically used for: The device receives a first IP data packet from the first terminal, the first IP data packet including the first I1 message, the first information, and the address information of the device.

32. The apparatus of any one of claims 25-31, wherein, The receiving module is also used for: Receive a registration request message related to the first terminal and the address information of the third network-side device, wherein the registration request message includes information about the first terminal; The sending module is further configured to send a response message to the registration request message, the response message of which includes the address information of the device.

33. A call establishment apparatus, comprising a transmitting module or a receiving module: During the process of establishing a call between the device and the first communication device, the sending module or the receiving module performs a second operation, the second operation including at least one of the following: Send a first I1 message and first information to a first network-side device, wherein the first I1 message is used by the device to request the first communication device to establish a call, and the first information is used to indicate the call parameters to be used; receive a response message and second information from the first I1 message from the first network-side device, wherein the second information is used to indicate the call parameters to be used; The device receives a second I1 message and a third information from the first network-side device. The second I1 message is used by the first communication device to request the device to establish a call, and the third information is used to indicate the call parameters to be used. Send a response message to the second I1 message and fourth information to the first network-side device, the fourth information being used to indicate the call parameters to be used.

34. The apparatus of claim 33, wherein, The sending module is specifically used for: Send a first IP data packet to the first network-side device. The first IP data packet includes the first I1 message, the first information, and the address information of the first network-side device.

35. The apparatus of claim 33 or 34, wherein, The sending module is also used for: Send the IMS registration request message related to the device; The receiving module is further configured to receive a response message to the IMS registration request message, the response message of which includes the address information of the first network-side device.

36. The apparatus of any one of claims 33-35, wherein, The sending module is also used for: During registration, attachment, or session establishment, the device sends a fifth message, which indicates at least one of the following: Discover the first network-side device that supports I1 messages; Discover the first network-side device that supports I1 message translation; The first network-side device supporting GEO (Geostationary Earth Orbit) calls in a high-orbit satellite communication system was discovered. The device supports I1 messages.

37. The device of any one of claims 33-36, wherein, The receiving module is also used for: During the registration, attachment, or session establishment process, the device receives the address information of the first network-side device.

38. The apparatus of claim 37, wherein, The receiving module is specifically used for: Receive the address information of the first network-side device by registering and accepting messages; or... Receive the address information of the first network-side device by attaching and receiving messages; or... The address information of the first network-side device is received by accepting messages through a session.

39. The device of claim 36, wherein, The sending module is specifically used for: The fifth message is sent via the protocol configuration option PCO.

40. The apparatus according to claim 37 or 38, wherein, The receiving module is specifically used for: The address information of the first network-side device is received through the PCO.

41. A network-side device, comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the call establishment method as claimed in any one of claims 1 to 13.

42. A terminal comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the call establishment method as claimed in any one of claims 14 to 24.

43. A readable storage medium storing a program or instructions that, when executed by a processor, implement the call establishment method as claimed in any one of claims 1-13, or implement the steps of the call establishment method as claimed in any one of claims 14-24.

Images