Wireless communication method, terminal device, and network device

Abstract

A wireless communication method, a terminal device, and a network device. The method comprises: a terminal device sends first indication information and / or encoding information to a network device, wherein the first indication information is used for indicating whether the terminal device performs a voice call by means of a first radio access type, and the encoding information is used for indicating an encoding mode supported by or requested to be used by the terminal device. On the basis of first indication information, a network device can determine whether a terminal device performs a voice call by means of a first radio access type, thereby executing a corresponding voice call setup procedure.

Description

Wireless communication method, terminal device and network device

[0001] The present application claims priority to the Chinese patent application No. PCT / CN2024 / 112438, filed on August 15, 2024, and titled “Wireless communication method, terminal device and network device”, the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, and more particularly, to a wireless communication method, a terminal device and a network device. BACKGROUND

[0003] With the development of communication technology, voice calls can be made using more diverse wireless access types. For example, with the popularization of non-terrestrial networks (NTN) communication, the demand for making calls using NTN (e.g., satellites) has increased significantly. SUMMARY

[0004] The present application provides a wireless communication method, a terminal device and a network device. The various aspects of the present application are described below.

[0005] In a first aspect, a wireless communication method is provided, which includes: a terminal device sending first indication information and / or encoding information to a network device; wherein the first indication information is used to indicate whether the terminal device makes a voice call through a first wireless access type; and the encoding information is used to indicate an encoding mode supported or requested by the terminal device.

[0006] In a second aspect, a wireless communication method is provided, which includes: a network device receiving first indication information and / or encoding information sent by a terminal device; wherein the first indication information is used to indicate whether the terminal device makes a voice call through a first wireless access type; and the encoding information is used to indicate an encoding mode supported or requested by the terminal device.

[0007] In a third aspect, a wireless communication method is provided, which includes: a terminal device skipping a first step in a voice call setup procedure; wherein the first step includes one or more of the following: a step related to called domain selection; a step related to secondary confirmation in a media negotiation process; a resource reservation confirmation step; and a step of establishing a voice dedicated bearer or a quality of service (QoS) data flow.

[0008] In a fourth aspect, a method for wireless communication is provided. The method includes: skipping, by a network device, a first step in a voice call setup procedure; wherein the first step comprises one or more of: a step related to called domain selection; a step related to secondary confirmation in a media negotiation procedure; a resource reservation confirmation step; a step of setting up a voice dedicated bearer or a QoS data flow.

[0009] In a fifth aspect, a terminal device is provided. The terminal device includes: a first sending unit configured to send first indication information and / or encoding information to a network device; wherein the first indication information is used to indicate whether the terminal device makes a voice call through a first radio access type; and the encoding information is used to indicate an encoding mode supported or requested by the terminal device.

[0010] In a sixth aspect, a network device is provided. The network device includes: a first receiving unit configured to receive first indication information and / or encoding information sent by a terminal device; wherein the first indication information is used to indicate whether the terminal device makes a voice call through a first radio access type; and the encoding information is used to indicate an encoding mode supported or requested by the terminal device.

[0011] In a seventh aspect, a terminal device is provided. The terminal device includes: a first skipping unit configured to skip a first step in a voice call setup procedure; wherein the first step comprises one or more of: a step related to called domain selection; a step related to secondary confirmation in a media negotiation procedure; a resource reservation confirmation step; a step of setting up a voice dedicated bearer or a QoS data flow.

[0012] In an eighth aspect, a network device is provided. The network device includes: a second skipping unit configured to skip a first step in a voice call setup procedure; wherein the first step comprises one or more of: a step related to called domain selection; a step related to secondary confirmation in a media negotiation procedure; a resource reservation confirmation step; a step of setting up a voice dedicated bearer or a QoS data flow.

[0013] In a ninth aspect, a terminal device is provided. The terminal device includes a processor and a memory. The memory is configured to store one or more computer programs. The processor is configured to invoke the computer programs in the memory to cause the terminal device to perform some or all of the steps in the method of the first aspect and the third aspect.

[0014] In a tenth aspect, a network device is provided. The network device includes a processor, a memory, and a transceiver. The memory is configured to store one or more computer programs. The processor is configured to invoke the computer programs in the memory to cause the network device to perform some or all of the steps in the method of the second aspect and the fourth aspect.

[0015] In a eleventh aspect, an embodiment of the present application provides a communication system, which comprises the terminal device and / or the network device described above. In another possible design, the system can further comprise other devices interacting with the terminal device or the network device in the solutions provided by the embodiments of the present application.

[0016] In a twelfth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. The computer program causes the terminal device and / or the network device to perform some or all of the steps of the methods in the various aspects described above.

[0017] In a thirteenth aspect, an embodiment of the present application provides a computer program product. The computer program product includes a non-transitory computer-readable storage medium storing a computer program. The computer program is operable to cause the terminal device and / or the network device to perform some or all of the steps of the methods in the various aspects described above. In some implementations, the computer program product can be a software installation package.

[0018] In a fourteenth aspect, an embodiment of the present application provides a chip. The chip includes a memory and a processor. The processor can invoke and run a computer program from the memory, to implement some or all of the steps described in the methods in the various aspects described above.

[0019] Through the first indication information, the network device can know whether the terminal device makes voice call through the first radio access type, so as to perform the corresponding voice call establishment (referred to as call establishment) process. Taking the first radio access type as the NTN-based radio access type as an example, due to the bandwidth limitation of NTN, and the large distance between the NTN network device (such as satellite) and the terminal device, etc., when making a voice call establishment, a long time is often needed to wait. If the terminal device informs the network device through the first indication information that the terminal device makes voice call through NTN, the network device and the terminal device can perform the voice call establishment process for NTN. Among them, the voice call establishment process for NTN can shorten the time of NTN call establishment, thereby improving the user experience. BRIEF DESCRIPTION OF DRAWINGS

[0020] FIG. 1 is a schematic diagram of a wireless communication system to which embodiments of the present application are applied.

[0021] FIG. 2 is an example diagram of a registration process.

[0022] FIG. 3 is an example diagram of a call establishment process.

[0023] FIG. 4 is a schematic flowchart of a wireless communication method provided by an embodiment of the present application.

[0024] FIG. 5 is a schematic flowchart of another method of wireless communication provided by embodiments of the present application.

[0025] FIG. 6 is a schematic structural diagram of a terminal device provided by embodiments of the present application.

[0026] FIG. 7 is a schematic structural diagram of a network device provided by embodiments of the present application.

[0027] FIG. 8 is a schematic structural diagram of another terminal device provided by embodiments of the present application.

[0028] FIG. 9 is a schematic structural diagram of another network device provided by embodiments of the present application.

[0029] FIG. 10 is a schematic structural diagram of an apparatus for communication provided by embodiments of the present application. DETAILED DESCRIPTION

[0030] The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0031] Communication system

[0032] FIG. 1 is a wireless communication system 100 to which embodiments of the present application are applied. The wireless communication system 100 can include communication devices. The communication devices can include a network device 110 and a terminal device 120. The network device 110 can be a device that communicates with the terminal device 120.

[0033] FIG. 1 exemplarily shows one network device and two terminals. Optionally, the wireless communication system 100 can include multiple network devices and each network device can include other numbers of terminal devices within its coverage, which is not limited in the embodiments of the present application.

[0034] Optionally, the wireless communication system 100 can further include a network controller, a mobile management entity, and other network entities, which are not limited in the embodiments of the present application.

[0035] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, for example, a 5th generation (5G) system or new radio (NR), a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD), and the like. The technical solutions provided by the present application can also be applied to future communication systems, such as a 6th generation mobile communication system, a satellite communication system, and the like.

[0036] The terminal device in the embodiments of the present application can also be referred to as a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile station (MS), a mobile terminal (MT), a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user apparatus. The terminal device in the embodiments of the present application can refer to a device providing voice and / or data connectivity for a user, and can be used to connect people, things and machines, such as handheld devices with wireless connection functions, vehicle-mounted devices, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer (Pad), a notebook computer, a palm computer, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity, which provides sidelink signals between UEs in vehicle-to-everything (V2X) or device to device (D2D), etc. For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and the smart home device communicate with each other without relaying the communication signals through the base station.

[0037] The network device in the embodiments of the present application can be a device for communicating with a terminal device. The network device can also include an access network device. The access network device can provide communication coverage for a specific geographic area and can communicate with terminal devices 120 located within the coverage area. The access network device can also be referred to as a radio access network device or a base station, etc. The access network device in the embodiments of the present application can refer to a radio access network (RAN) node (or device) that accesses a terminal device to a wireless network. The access network device can broadly cover or be replaced by various names as follows, such as: Node B (NodeB), evolved Node B (eNB), next generation Node B (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), master eNB (MeNB), secondary eNB (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. The base station can also refer to a communication module, modem, or chip used in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs the function of a base station in D2D, V2X, machine-to-machine (M2M) communication, a network side device in a 6G network, a device that performs the function of a base station in a future communication system, etc. The base station can support networks of the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form adopted by the access network device.

[0038] The base station can be fixed or mobile. For example, a helicopter or a drone can be configured to act as a mobile base station, and one or more cells can move according to the location of the mobile base station. In other examples, a helicopter or a drone can be configured to serve as a device that communicates with another base station.

[0039] The communication devices involved in the wireless communication system can include not only access network devices and terminal devices, but also core network elements. The core network elements can be implemented by devices, that is, the core network elements are core network devices. It can be understood that the core network devices can also be a kind of network devices.

[0040] The core network elements in the embodiments of the present application can include network elements that process and forward signaling and data of users. For example, the core network devices can include core network access and mobility management function (core access and mobility management function, AMF), session management function (session management function, SMF), and user plane gateway, location management function (location management function, LMF), and other core network devices. Among them, the user plane gateway can be a server with functions of mobility management, routing, forwarding, etc. for user plane data, and is generally located on the network side, such as a serving gateway (serving gateway, SGW) or a packet data network gateway (packet data network gateway, PGW) or a user plane function entity (user plane function, UPF). Of course, other network elements can also be included in the core network, which are not listed here.

[0041] In some deployments, the network device in the embodiments of the present application can refer to a CU or a DU, or the network device includes a CU and a DU. The gNB can also include an AAU.

[0042] The network device and the terminal device can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; can also be deployed on the water surface; can also be deployed on airplanes, balloons and satellites in the air. The scenarios in which the network device and the terminal device are located are not limited in the embodiments of the present application.

[0043] It should be understood that all or part of the functions of the communication device in the present application can also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform (such as a cloud platform).

[0044] IP multimedia subsystem (IP multimedia subsystem, IMS) registration process

[0045] The registration process is an important step for the terminal device to establish a communication relationship with the network. The IMS registration process can allow the terminal device to use the services provided by the IMS.

[0046] The IMS registration procedure will be described below in connection with Fig. 2.

[0047] As shown in Fig. 2, the IMS registration procedure can comprise steps S101-S126.

[0048] At step S101, a caller UE sends an initial registration request. The initial registration request can be a REGISTER message. The REGISTER message can carry a public user identity (PUI), a private user identity (PVI), a home realm name, an instance ID, a globally routable UA URI (GRUU) support indication.

[0049] At steps S102-S103, a proxy-call session control function (P-CSCF) looks up a domain name system (DNS) according to a home domain, thereby obtaining an address of an interrogating call session control function (I-CSCF). Steps S102-S103 are implemented based on a DNS Query message and a DNS Query Resp message, respectively.

[0050] At step S104, the P-CSCF sends a registration message to the I-CSCF. The registration message carries a P-CSCF address / name, the PUI, the PVI, a P-CSCF identity, and a UE IP address.

[0051] Steps S105 and S106 are a serving-call session control function (S-CSCF) allocation procedure.

[0052] At step S105, the I-CSCF sends a Diameter message: user authorization request (UAR) to a home subscriber server (HSS), which carries the PUI, the PVI, and the P-CSCF identity. Based on the Diameter message, the HSS checks whether the UE is allowed to register to the P-CSCF.

[0053] Step S106, HSS returns a Diameter message: user authorization answer (UAA). The Diameter message includes S-CSCF information (e.g. name or capability set).

[0054] Step S107, I-CSCF gets S-CSCF from HSS, i.e. S-CSCF assignment procedure.

[0055] Steps S108 and S109 are procedures of downloading authentication vector set.

[0056] Step S108, S-CSCF sends a Diameter message: multimedia auth request (MAR) to HSS. The Diameter message includes PUI, PVI, S-CSCF name.

[0057] Step S109, HSS returns a Diameter message: multimedia auth answer (MAA). The Diameter message includes authentication data (authentication method (Digest), authentication vector (username password))

[0058] Steps S110-S119 are authentication procedures. In steps S110-S112, authentication parameters are returned to UE. Steps S113 and S116 are authentication responses. Steps S117 and S118 are S-CSCF assignment procedures.

[0059] Steps S120-S121, download user subscription information. The subscription information can also be referred to as subscription profile. The subscription profile can include initial filter criteria (iFC) information, etc.

[0060] After registration is successful, S-CSCF checks iFC and informs application server (AS) serving the user that the user has registered and is reachable, steps S125-S126.

[0061] IMS call setup procedure

[0062] In a communication system, voice communication between terminal devices can be implemented through an IMS call setup procedure, i.e. voice over IMS (VoIMS).

[0063] The key steps in the IMS call setup procedure are described below in connection with Fig. 3.

[0064] The IMS call establishment procedure mainly includes the following key steps: media negotiation process, dedicated QoS flow / bearer establishment process, terminating-access domain selection (T-ADS) process, resource reservation process, and ring process. The following will be described respectively.

[0065] The media negotiation process can include steps S201-S212 and S301-S312 in FIG. 3. The media negotiation process mainly negotiates the media type and encoding scheme supported by the calling UE with the called UE through the session description protocol (SDP) bearer (through two SDP request-answers)

[0066] The dedicated QoS flow / bearer establishment process can include steps S207 and S306 in FIG. 3. The dedicated QoS flow / bearer establishment process is an S-CSCF triggered UE dedicated bearer / data flow establishment process, which is triggered after the first SDP request answer to trigger the core network session modification procedure.

[0067] The T-ADS process can include step S302 in FIG. 3. The T-ADS process can determine in which domain (for example, 2 / 3G core network (CN) or evolved packet system (EPS) or 5G system (5GS)) the called UE is currently camping. The S-CSCF triggers the AS to query the HSS about the domain (for example, evolved packet core (EPC) or circuit switched (CS)) in which the called UE is currently camping, and then the S-CSCF sends a message to the specified domain according to the domain of the called UE.

[0068] The resource reservation process can include steps S210 and S313 shown in FIG. 3. In order to ensure that the negotiated media plane can be successfully established, resources need to be reserved on the calling and called sides. Resource reservation usually occurs after the media negotiation process is completed (after two SDP request-answers)

[0069] The ring process can include steps S323-S325 and S222-S224. The ring process can occur after the resource reservation is successful.

[0070] Non-terrestrial networks (NTN)

[0071] An NTN can provide communication services to users in a non-terrestrial manner. That is, a terminal device can communicate with a non-terrestrial network device such as a satellite (SAT), an unmanned aerial system platform (UAS platform), and the like. The type of satellite can include a low earth orbit (LEO), a medium earth orbit (MEO), or a geostationary earth orbit (GEO), and the like.

[0072] For terrestrial network communication, scenarios such as oceans, mountains, deserts, and the like cannot be covered by land communication. Or, considering the cost of building and operating communication equipment, land communication usually does not cover sparsely populated areas. Compared with terrestrial network communication, NTN has many advantages. First, for an NTN communication network, there is no geographical restriction. In theory, a satellite can orbit the earth, so every corner of the earth can be covered by satellite communication. Moreover, the area covered by a non-terrestrial network device is much larger than the area covered by a terrestrial communication device. That is, an NTN cell can cover a larger range.

[0073] FIG. 4 is a schematic flowchart of a wireless communication method according to an embodiment of the present application. The method shown in FIG. 4 can be performed by a terminal device and a network device. The network device can include one or more of a control plane network element, a user plane network element. For example, the network device can include a P-CSCF.

[0074] The method shown in FIG. 4 can include step S410.

[0075] In step S410, the terminal device sends first indication information and / or encoding information to the network device.

[0076] The first indication information can be used to indicate a radio access type. The radio access type can be for voice. For example, the first indication information can be used to indicate whether the terminal device makes a voice call, voice operation, or voice service, and the like through a first radio access type. In other words, the first indication information can be used to indicate the radio access type through which the terminal device makes a voice call, voice operation, or voice service. The radio access type can include the first radio access type.

[0077] It should be noted that in the present application, the terms "voice call", "voice operation", "voice service", and the like can be used interchangeably.

[0078] In some embodiments, the first radio access type can be, for example, an NTN-based radio access type. In other words, the first indication information can be used to indicate whether the terminal device makes a voice call through an NTN.

[0079] Through the first indication information, the network device can learn whether the terminal device makes voice call through the first radio access type, so as to perform a corresponding voice call establishment process. Taking the first radio access type as the NTN-based radio access type as an example, due to the bandwidth limitation of NTN, the distance between the NTN network device (for example, a satellite) and the terminal device is large, and a long time is often needed when performing voice call establishment. If the terminal device informs the network device through the first indication information that the terminal device makes voice call through NTN, the network device and the terminal device can perform a call establishment process for NTN. The call establishment process for NTN (for example, the call establishment process provided in FIG. 5 in the following of the present application) can shorten the time of NTN call establishment, thereby improving user experience.

[0080] In some embodiments, the encoding information can be used to indicate an encoding mode supported by the terminal device for use. In other words, the encoding information can be used to indicate the capability of the terminal device related to the encoding mode.

[0081] In some embodiments, the encoding information can be used to indicate an encoding mode requested by the terminal device for use. In other words, the terminal device can request the network device to communicate with the terminal device through the encoding mode indicated by the encoding information.

[0082] In some embodiments, the encoding mode can include one or more of the following parameters: encoding type, code rate, frame format, transmission protocol, service type. The encoding type can be used to indicate the codec type. The encoding mode can include one or more values of the parameters.

[0083] For example, the encoding information can indicate that the encoding type requested or supported by the terminal device includes one or more of the following: Codec-2, AMR codec, EVS codec.

[0084] For another example, the encoding information can indicate that the code rate requested or supported by the terminal device is 0.7 kbps and / or 0.45 kbps.

[0085] For another example, the encoding information can indicate that the frame format requested or supported by the terminal device is the real-time transport protocol (RTP) packet format.

[0086] For another example, the encoding information can indicate that the transmission protocol requested or supported by the terminal device is the RTP / AVP over UDP based on UCP.

[0087] For another example, the encoding information can indicate that the service type requested or supported by the terminal device is audio.

[0088] In some embodiments, the encoding information can include one or more parameters and corresponding values of the parameters. That is, the encoding information can directly indicate the parameters and values in the encoding mode.

[0089] In some embodiments, the encoding information can include one or more parameters and corresponding values of the parameters. That is, the encoding information can directly indicate the parameters and values in the encoding mode.

[0090] In some embodiments, the encoding information can include a first index (or referred to as a first identifier). The first index can correspond to one or more parameters and corresponding values of the parameters. For example, the value of the first index included in the encoding information is 0, which can represent: encoding type: Codec-2; code rate: 0.7 kbps or 0.45 kbps; frame format: RTP packet format; transmission protocol: RTP / AVP over UDP; service type: Audio. For another example, the value of the first index included in the encoding information is 1, which can represent: encoding type: AMR codec; code rate: 0.7 kbps or 0.45 kbps; frame format: RTP packet format; transmission protocol: RTP / AVP over UDP; service type: Audio.

[0091] In some embodiments, the first indication information can be carried in the first message. In other words, the first indication information can be indicated by the first message. The first message can be a message in the IMS registration procedure. That is, the terminal device can carry the first indication information in the message in the IMS registration procedure. For example, the first indication information can be carried in the registration request message (e.g., the RIGISTER message described in step S101 above) in the IMS registration procedure. In the case where the first message is a message in the registration procedure, the method shown in FIG. 4 can also be referred to as enhancement for the registration procedure.

[0092] It should be noted that the first message can be sent through the first radio access type or based on the non-first radio access type.

[0093] Optionally, the first indication information can be determined by the radio access type through which the first message is sent.

[0094] For example, the terminal device can send the registration request message through the first radio access type to indicate that the terminal device performs voice communication through the first radio access type. For another example, the terminal device can send the registration request message through the non-first radio access type (e.g., the radio access type based on TN) to indicate that the terminal device does not perform voice communication through the first radio access type.

[0095] Optionally, whether the terminal device makes voice call through the first radio access type can be determined by the radio access type through which the first message is sent and the information carried in the first message.

[0096] For example, the terminal device sends a registration request message through a certain radio access type (e.g., the first radio access type), and the registration request message carries first indication information. The first indication information can indicate that the terminal device makes voice call through the radio access type, or the first indication information can indicate that the terminal device does not make voice call through the radio access type.

[0097] Optionally, the first message can carry the first indication information, i.e., the first message can include a field indicating the first indication information. In this case, the first indication information can be independent of the radio access type through which the first message is sent.

[0098] For example, the terminal device can send a registration request message through any radio access type, and the registration request message can carry first indication information. The first indication information can indicate whether the terminal device makes voice call through the first radio access type.

[0099] In some embodiments, the first indication information indicates that the terminal device makes voice call through the first radio access type when the first message satisfies a first condition.

[0100] As a possible implementation, the first condition can include one or more of the following: the first message is sent in response to the terminal device moving into a network coverage area of the first radio access type; the first message is sent in response to the terminal device initiating first registration in the network coverage area of the first radio access type.

[0101] Taking the first radio access type as NTN for example, when the terminal device initiates first IMS registration and is in the NTN coverage area, or when the terminal device moves into the NTN coverage area, the terminal device can send the first indication information indicating that the terminal device makes voice call through the NTN.

[0102] In some embodiments, the first indication information indicates that the terminal device does not make voice call through the first radio access type, i.e., makes voice call through a non-first radio access type, when the first message satisfies a second condition.

[0103] As a possible implementation, the second condition can include that the first message is sent in response to the terminal device entering a network coverage area of a non-first radio access type from a network coverage area of the first radio access type.

[0104] Taking the first radio access type as an example, when the terminal device leaves the NTN coverage area and enters the TN coverage area, reinitiates the registration request, the terminal device can send the first indication information to indicate that the terminal device accesses through the TN.

[0105] In some embodiments, the encoding information can be carried in the first message. As described above, the first message can be a message in the registration procedure, i.e., the encoding information can be carried in a message in the registration procedure. For example, the encoding information can be carried in a SIP registration message.

[0106] Exemplarily, the encoding information can be carried in one or more fields (or domains) in the SIP registration message header. As a possible implementation, the encoding information can be carried in one or more fields shown in Table 1. For example, the encoding information can be placed in the Contact field and / or the User-Agent (UA) field.

[0107] Exemplarily, the encoding information can be carried in a session description protocol (SDP) offer included in the SIP registration message.

[0108] Therefore, by the present application, the pre-negotiation of the encoding information can be realized in the registration procedure, i.e., the negotiation of the encoding information can be completed before the call procedure. This helps to reduce the signaling overhead and save communication resources in the call procedure.

[0109] As described above, the first indication information can be transmitted in the IMS registration procedure. The IMS registration procedure can be implemented by a SIP message. It is proposed in the present application that the header domain of the SIP message can not carry part or all of the fields related to routing. In other words, part of the fields in the header domain of the SIP message can be omitted, thereby reducing the SIP message load.

[0110] The header domain of the SIP message can not carry one or more of the following fields: starting line field, From field, To field, Call-ID field, Via field, Route field, Contact field, Record-Route field. These fields are described below in Table 1.

[0111] Table 1

[0112] In some embodiments, the first indication information can be used to indicate the type of satellite for voice service of the terminal device. Exemplarily, the type of satellite can include one or more of the following: LEO, MEO, GEO.

[0113] In some embodiments, the terminal device can receive second indication information sent by the network device. The second indication information can include one or more of the following: a coding strategy suggested or allowed by the network device for the terminal device to use; a message type and / or a status code that the terminal device needs to send or receive when initiating a registration request and / or call establishment; a field that can not be carried in a SIP header field.

[0114] The coding strategy can include one or more of the following: a coding type, a code rate, a frame format, a transmission protocol, a service type. Illustratively, the coding strategy can include one or more of the following: the coding type is Codec-2; the code rate is 0.7 kbps or 0.45 kbps; the frame format is RTP packet format; the transmission protocol is RTP / AVP over UDP; the service type is voice.

[0115] The coding strategy can be carried in a message in the registration process. For example, the coding strategy can be carried in a reply message in the registration process. The reply message may, for example, include 200 OK. Illustratively, the coding strategy can be carried in one or more fields in the reply message header (e.g., a Contact field or a UA field). Illustratively, the coding strategy can be carried in an SDP offer in the reply message.

[0116] In some embodiments, the coding strategy and the coding information can have a corresponding relationship. For example, the coding strategy can be a response to the coding information. For example, the network device can determine the coding strategy according to the received coding information and issue the coding strategy to the terminal device.

[0117] In some embodiments, the network device can accept (or allow) or reject (or not allow) the coding information sent by the terminal device. In this case, the network device can not send the coding strategy. For example, if the network device accepts or allows the coding information, it only needs to normally reply with a 200 OK message, without the need to include the corresponding coding strategy in the 200 OK message.

[0118] The encoding strategy suggested or allowed by the network device for the terminal device to use can include one or more encoding types or codecs. Among them, a codec can refer to a device or software capable of encoding or decoding a digital stream or a signal for transmission over a data network (A codec is a device or piece of software capable of encoding or decoding a digital stream or a signal for transmission over a data network). The terminal device can select part or all of the one or more codecs to carry in the voice call establishment process. The encoding strategy suggested or allowed by the network device for the terminal device to use can be determined based on the type of satellite through which the terminal device conducts voice services. For example, LEO or MEO can support more codecs than GEO, so the codecs that the LEO or MEO network device can suggest or allow the terminal device to use can be more.

[0119] For example, in the case where the first indication information indicates that the terminal device conducts voice services through the first radio access type, the second indication information can send fewer codecs for the terminal device to select and use. For example, in the case where the first radio access type is NTN, based on the fact that NTN supports fewer types of codecs for voice services, if the terminal device carries a codec that NTN cannot support in the voice call establishment process, it will cause problems such as waste of communication resources or redundancy of the voice call establishment process. By indicating the suggested or allowed codecs to the terminal device through the second indication information, the terminal device can avoid sending a message carrying a codec that NTN cannot support, thereby reducing or avoiding problems such as waste of communication resources or redundancy of the voice call establishment process.

[0120] For another example, in the case where the first indication information indicates the type of satellite through which the terminal device conducts voice services, the network device can determine the codecs supported by the corresponding satellite according to the type of the satellite, and carry part or all of the codecs supported by the corresponding satellite as the codecs suggested or allowed by the network device for the terminal device to use, and indicate the same through the second indication information, thereby avoiding the terminal device sending a message carrying a codec that the satellite cannot support, and further reducing or avoiding problems such as waste of communication resources or redundancy of the voice call establishment process.

[0121] In some embodiments, the message type indicated by the second indication information can comprise one or more of the following: Register, Invite, provisional response acknowledgement (PRACK), acknowledgement (Ack).

[0122] In some embodiments, the status code indicated by the second indication information can comprise one or more of the following: 1xx, 2xx, 3xx, 4xx, 6xx.

[0123] As described above, in the case that the terminal device is engaged in voice communication through the first radio access type, the network device and / or the terminal device can perform a registration procedure and / or a call setup procedure for the first radio access type. The message type and / or the status code that the terminal device needs to send or receive when initiating a registration request and / or a call setup through the second indication information can enable the terminal device to know which message type and / or status code to perform the registration procedure and / or the call setup procedure subsequently, thereby performing the registration procedure and / or the call setup procedure for the first radio access type.

[0124] The second indication information can indicate a field that can not be carried in a SIP header field during the call setup procedure. As described above, the call setup procedure can be implemented by a SIP message, and the SIP message can comprise a SIP header field. The field that can not be carried in the SIP header field can be indicated by the second indication information. The terminal device can determine the field that can not be carried in the SIP header field during the call setup procedure according to the second indication information.

[0125] In some embodiments, the second indication information can be carried in a reply message sent by the network device to the terminal device during the registration procedure. For example, the reply message can be the 200 OK message in step S124.

[0126] It can be understood that, based on the second indication information, the network device can configure the behavior of the terminal device as needed, for example, configure the behavior of the terminal device in the voice call setup procedure.

[0127] Based on the first indication information and / or the second indication information, the terminal device and the network device can determine how to perform the voice call setup and / or registration procedure and the like subsequently, thereby facilitating the terminal device and the network device to determine the consistency of the behavior.

[0128] For example, according to the received second indication information, the terminal device can perform a corresponding voice call establishment process. Illustratively, the terminal device can perform the voice call flow establishment process shown in FIG. 5 below according to the second indication information, that is, the terminal device can perform process simplification in the voice call establishment process according to the second indication information.

[0129] For another example, according to the received first indication information, the network device can perform a corresponding voice call establishment process. Illustratively, the network device can perform the voice call flow establishment process shown in FIG. 5 below according to the first indication information, that is, the network device can perform process simplification in the voice call establishment process according to the first indication information.

[0130] The present application also provides an improved voice call flow establishment process. The following is described in conjunction with FIG. 5. The method shown in FIG. 5 can be performed by a network device or a terminal device. The network device can include one or more of a control plane network element and a user plane network element. For example, the network device can include a P-CSCF and an S-CSCF. The terminal device can include a mobile originated user equipment (MO UE) and a mobile terminated user equipment (MT UE).

[0131] The method shown in FIG. 5 can include step S510.

[0132] In step S510, the terminal device or the network device skips a first step in a voice call establishment process. The voice call establishment process can be implemented by IMS, that is, an IMS voice call establishment process. For example, the first step can be one or more steps in FIG. 3.

[0133] It can be understood that in the present application, part of the steps in the voice call establishment process can be omitted, that is, the present application can implement process simplification in the voice call establishment process.

[0134] It should be noted that in the voice call establishment process, one or both of the terminal device and the network device can skip part of the steps. The steps skipped by the terminal device and the steps skipped by the network device can be the same or different, that is, the first step skipped by the terminal device and the first step skipped by the network device can be the same or different.

[0135] By skipping the first step, the voice call establishment process can be shortened, thereby reducing the waiting time for voice call establishment.

[0136] In some embodiments, step S510 can be performed in case the voice call is implemented through the first radio access type. For example, step S510 can be performed in case the voice call is implemented through NTN. As described above, the distance between the terminal device and the NTN network device is long, and the bandwidth of the NTN is limited, so a long time is needed to wait when establishing a voice call, and the present application can skip some steps, thereby reducing the waiting time for establishing an NTN voice call.

[0137] In some embodiments, the first step can include one or more of the following: a step related to called domain selection; a step related to secondary confirmation in the media negotiation process; a resource reservation confirmation step; a step of establishing a voice dedicated bearer or QoS data flow. The following are described respectively.

[0138] The step related to called domain selection can include part or all of the steps in T-ADS. That is, the terminal device or the network device can omit part or all of the steps in T-ADS. The step related to called domain selection can include one or more of the following: judging the domain in which the called user recently camps; querying the domain in which the called user currently camps; sending a message to the specified domain based on the called user's selected specified domain.

[0139] In the case of a voice call by the terminal device based on NTN, there are fewer domains that can be used by the voice call based on NTN. For example, there is no possibility of using a 2 / 3G CS domain for a voice call based on NTN. Therefore, it is feasible for the voice call establishment process based on NTN to omit the step related to called domain selection.

[0140] The step related to secondary confirmation in the media negotiation process can include one or more of steps S209-S215, steps S309-S315 shown in FIG. 3.

[0141] In some embodiments, in the case of skipping the step related to secondary confirmation in the media negotiation process, the reply message of the first confirmation in the media negotiation process can include a success response message. That is, the reply message can be a 200 OK PRACK, rather than a 183 Session Progress. In this case, for FIG. 3, the first invitation (Invite) message is completed after being sent by the MO UE and receiving a reply (i.e., steps S201-S208, S301-S308 shown in FIG. 3), and there is no need for secondary confirmation (steps S209-S215, S309-S315).

[0142] In some embodiments, the step of establishing a voice dedicated bearer or QoS data flow may, for example, include S207 and / or S306 in FIG. 3.

[0143] In the case of skipping the step of establishing a voice dedicated bearer, the voice call can share a bearer with other data. Taking the voice call implemented based on the NTN as an example, the limitation of the NTN bandwidth does not necessarily require a dedicated bearer for the voice call, and sharing a bearer with other data is more in line with the characteristics of the NTN.

[0144] In some embodiments, the resource reservation confirmation step can include one or more of S216-S221, S316-S322 shown in FIG. 3.

[0145] In the registration process, it can be determined whether the terminal device / network device skips the first step in the voice call establishment process and / or which step(s) are skipped in the first step (e.g., determined by the first indication information and / or the second indication information sent in the registration process).

[0146] In some embodiments, the terminal device can send third indication information to the network device. The third indication information can be used to indicate one or a first number of codecs that can be selected in the call establishment process. For example, the third indication information can only carry codec2. It can be understood that based on the third indication information, the number of codecs that the terminal device indicates can be selected in the call establishment process is limited, i.e., the codec is relatively simple, and the resources for processing the codec later are easier to reserve.

[0147] It should be noted that the first number is a positive integer. The first number can satisfy one or more of the following: pre-negotiated by the terminal device and the network device, specified by a protocol, predefined.

[0148] In some embodiments, the third indication information can be sent during the media negotiation process. For example, the third indication information is carried in the SDP offer message in the media negotiation process.

[0149] Optionally, the third indication information can be determined based on the second indication information. For example, based on the second indication information, the network device can indicate the recommended or allowed codec to the terminal device, the terminal device can select one or a first number of codecs from the recommended or allowed codec, and feed back the selected codec to the network device through the third indication information.

[0150] As described above, the call establishment process can be implemented through a SIP message, and the header field of the SIP message can not carry part of the fields related to routing. For example, the header field of the SIP message can not carry one or more of the following fields: start line field, initiation field, reception field, call identification field, passage field, routing field, contact field, and record routing field. The related fields have been described in detail above and will not be repeated here.

[0151] The method shown in FIG. 4 and FIG. 5 can be implemented in combination.

[0152] Exemplarily, the network device can determine, according to the first indication information, whether to skip the first step and / or which step or steps are included in the skipped first step. For example, the network device can determine, according to the first indication information, whether to omit part or all steps in the T-ADS procedure in the call setup procedure. For another example, the network device can determine, according to the first indication information, whether to omit the step of establishing a voice dedicated bearer or a QoS data flow in the call setup procedure.

[0153] Exemplarily, the terminal device can determine, according to the second indication information, whether to skip the first step and / or which step or steps are included in the skipped first step. For example, the terminal device can determine, according to the second indication information, which field or fields can not be carried in the SIP header field. For another example, the terminal device can determine, according to the second indication information, whether to omit the step of establishing a voice dedicated bearer or a QoS data flow, part or all steps in the T-ADS procedure, and the step related to the secondary confirmation in the call setup procedure.

[0154] For the convenience of understanding, the present application is described in detail below by Embodiment 1 and Embodiment 2 in combination with FIG. 2 and FIG. 3.

[0155] Embodiment 1

[0156] Embodiment 1 is an improvement of FIG. 3, which realizes the simplification of the IMS call setup procedure based on NTN.

[0157] The NTN call setup procedure can omit the T-ADS step, because there is no possibility to use the 2 / 3G CS domain for NTN voice.

[0158] The NTN call setup procedure can simplify one or more steps in the media negotiation procedure, and the simplified steps in the media negotiation procedure can specifically include one or more of the following 3 items.

[0159] 1. Only one or fewer codec selections are carried in the SDP offer message, such as only codec 2 is carried.

[0160] 2. The first Invite message is sent by the MO UE and the reply is received, and then the procedure is completed (steps S201-S208, S301-S308), without the need for secondary confirmation (steps S209-S215). The reply message of step S208 can be 200 OK PRACK instead of 183 Session Progress.

[0161] 3. The step S306 and S207 can be omitted, i.e. the step of setting up a dedicated voice bearer can be omitted. The limitation of voice bandwidth in NTN does not necessarily require to set up a dedicated bearer, a shared bearer with other data can be used.

[0162] The call setup procedure in NTN can omit the step of resource reservation confirmation (step S216-S221, S316-S322). Because the codec is relatively simple, the resources for processing the codec are easier to reserve, and confirmation is not necessary.

[0163] The routing of SIP messages in IMS is completed by the SIP header field information. The important SIP fields in the header field are shown in Table 1. In the call setup procedure, some SIP fields do not need to be carried. For example, the Record-Route field and / or the Contact field can not need to be carried.

[0164] Embodiment 2

[0165] Embodiment 2 is an improvement of Figure 2, which realizes the enhancement of the IMS registration procedure. The steps and functions that can be enhanced in Embodiment 2 are described below.

[0166] In step S101, when the UE initiates the first IMS registration and is in the NTN coverage area, or when the UE moves into the NTN coverage area, the first indication information and / or the encoding information are added in the REGISTER message.

[0167] The first indication information is used to indicate that the UE performs voice operation through SAT access, and the first indication information can further indicate which kind of SAT access (such as Leo, Meo or Geo) the UE uses.

[0168] The encoding information can include one or more parameters such as encoding type, code rate, frame format, transmission protocol, service type, etc. The parameters contained in the encoding information can have one or more values. For example, the encoding information indicates: encoding type: Codec-2; code rate: 0.7 kbps or 0.45 kbps; frame format: RTP packet format; transmission protocol: RTP / AVP over UDP; service type: Audio.

[0169] The encoding information can be carried in one or more fields in the SIP Register message header. For example, the encoding information can be placed in the Contact field or the UA field. The encoding information can be carried in the SDP Offer contained in the SIP Register message.

[0170] When the UE leaves the NTN coverage area and enters the TN coverage area, the registration request is re-initiated, and the REGISTER message can indicate that it is through TN access.

[0171] In addition, the P-CSCF receiving the REGISTER message can determine whether to omit the establishment of the QoS dedicated bearer in the call setup procedure according to the first indication information (as described in Embodiment 1).

[0172] In step S107, the S-CSCF receiving the REGISTER message can determine whether to omit the T-ADS procedure in the call setup procedure according to the content corresponding to the first indication information (as described in Embodiment 1).

[0173] In step S124, the UE receives a reply message (200 OK). The reply message can carry one or more of the following information related to the call setup procedure: one or more codecs; message types and / or status codes that need to be sent or received in the case that the UE initiates the call setup procedure; fields that can not be carried in the SIP header. The following describes each of them.

[0174] If the reply message can indicate one or more codecs, the one or more codecs indicate codecs that the IMS network suggests or allows to use, the UE can select one or more of them to carry when initiating the call setup procedure.

[0175] The reply message can include an encoding policy. The encoding policy can include one or more parameters such as encoding type, code rate, frame format, transmission protocol, and service type. The encoding policy can include one or more values for the parameters.

[0176] Optionally, the encoding policy can be carried in one or more fields in the Header of the reply message (such as 200 OK). For example, the encoding policy can be placed in the Contact field or the UA field.

[0177] Optionally, the encoding policy can be carried by including an SDP Offer in the reply message.

[0178] The reply message can carry the following information: message types and / or status codes that need to be sent or received in the case that the UE initiates the call setup procedure. For example, the message types can include one or more of Register, Invite, PRACK, and Ack. The status codes can include one or more of 1xx, 2xx, 3xx, 4xx, and 6xx.

[0179] The reply message can carry the following information: fields that can not be carried in the SIP header. The fields that can not be carried in the SIP header can be one or more of the fields in Table 1. For example, the fields that can not be carried in the SIP header can include one or more of Route, Record-Route, and Contact.

[0180] The UE can implement a call setup simplified procedure (as described in Embodiment 1) according to the reply message.

[0181] The method embodiments of the present application are described in detail above, and the device embodiments of the present application are described in detail below. It should be understood that the description of the method embodiments corresponds to the description of the device embodiments, and therefore, the parts not described in detail can be referred to the method embodiments described above.

[0182] FIG. 6 is a schematic structural diagram of a terminal device 600 according to an embodiment of the present application. The terminal device 600 can include a first sending unit 610.

[0183] The first sending unit 610 is configured to send first indication information and / or encoding information to a network device; wherein the first indication information is used to indicate whether the terminal device makes voice calls through a first radio access type; and the encoding information is used to indicate an encoding mode supported or requested by the terminal device.

[0184] In some embodiments, the encoding information is used to indicate one or more of the following: an encoding type, a code rate, a frame format, a transmission protocol, a service type.

[0185] In some embodiments, the encoding information is carried in one or more of the following: one or more fields in a SIP registration message header; a session description protocol offer included in a SIP registration message.

[0186] In some embodiments, the first indication information is carried in a first message, and the first indication information indicates that the terminal device makes voice calls through the first radio access type in a case where the first message satisfies a first condition, and the first condition includes one or more of the following: the first message is sent in response to the terminal device moving into a network coverage area of the first radio access type; the first message is sent in response to the terminal device initiating a first registration in the network coverage area of the first radio access type.

[0187] In some embodiments, the first indication information is carried in a first message, and the first indication information indicates that the terminal device does not make voice calls through the first radio access type in a case where the first message satisfies a second condition; and the second condition includes: the first message is sent in response to the terminal device entering a network coverage area of a type different from the first radio access type from the network coverage area of the first radio access type.

[0188] In some embodiments, the first indication information is carried in a registration request message in an IMS registration procedure.

[0189] In some embodiments, the IMS registration procedure is implemented by a Session Initiation Protocol (SIP) message, and a header field of the SIP message is capable of not carrying a part of fields related to routing.

[0190] In some embodiments, the header field of the SIP message is capable of not carrying one or more of the following fields: a start line field, an originating field, a receiving field, a call identification field, a passing field, a routing field, a contact field, and a record routing field.

[0191] In some embodiments, the terminal device 600 is further configured to receive second indication information sent by the network device, wherein the second indication information comprises one or more of the following: a coding strategy suggested or allowed by the network device for the terminal device to use; a message type and / or a status code that needs to be sent or received by the terminal device when initiating a registration request and / or call establishment; and one or more fields in a header field of a SIP message in an IMS registration procedure that can not be carried.

[0192] In some embodiments, the coding strategy comprises one or more of the following: a coding type, a code rate, a frame format, a transmission protocol, and a service type.

[0193] In some embodiments, the first indication information is used to indicate a type of satellite for voice service of the terminal device.

[0194] In some embodiments, the type of satellite comprises one or more of the following: a low earth orbit (LEO), a medium earth orbit (MEO), and a geostationary earth orbit (GEO).

[0195] In some embodiments, the network device comprises a P-CSCF.

[0196] In some embodiments, the first radio access type is an NTN-based radio access type.

[0197] In optional embodiments, the first sending unit 610 can be a transceiver 1030. The terminal device 600 can further comprise a processor 1010 and a memory 1020, as shown in FIG. 10.

[0198] FIG. 7 is a schematic structural diagram of a network device 700 according to an embodiment of the present application. The network device 700 can comprise a first receiving unit 710.

[0199] The first receiving unit 710 is configured to receive first indication information and / or coding information sent by a terminal device, wherein the first indication information is used to indicate whether the terminal device performs voice communication through a first radio access type, and the coding information is used to indicate a coding mode supported or requested by the terminal device.

[0200] In some embodiments, the encoding information is used to indicate one or more of: encoding type, code rate, frame format, transmission protocol, service type.

[0201] In some embodiments, the encoding information is carried in one or more of: one or more fields in a SIP registration message header; a session description protocol offer included in a SIP registration message.

[0202] In some embodiments, the first indication information is carried in a first message, and the first indication information indicates that the terminal device performs voice communication through the first radio access type if the first message satisfies a first condition, and the first condition comprises one or more of: the first message is sent in response to the terminal device moving into a network coverage area of the first radio access type; the first message is sent in response to the terminal device initiating first registration in the network coverage area of the first radio access type.

[0203] In some embodiments, the first indication information is carried in a first message, and the first indication information indicates that the terminal device does not perform voice communication through the first radio access type if the first message satisfies a second condition, and the second condition comprises: the first message is sent in response to the terminal device entering a network coverage area of a type other than the first radio access type from the network coverage area of the first radio access type.

[0204] In some embodiments, the first indication information is carried in a registration request message in an IMS registration procedure.

[0205] In some embodiments, the IMS registration procedure is implemented through a SIP message, and a header field of the SIP message is capable of not carrying a part field related to routing.

[0206] In some embodiments, the header field of the SIP message is capable of not carrying one or more of the following fields: a starting line field, an initiation field, a receiving field, a call identification field, a passing field, a routing field, a contact field, a record routing field.

[0207] In some embodiments, the network device 700 is further configured to determine, according to the first indication information, whether to skip one or more of the following: a step of establishing a voice dedicated bearer or a quality of service (QoS) data flow; a step related to called domain selection.

[0208] In some embodiments, in a case where the step of establishing a voice dedicated bearer is skipped, the voice communication shares a bearer with other data.

[0209] In some embodiments, the step related to called domain selection comprises one or more of the following: determining a domain in which the called user has recently camped; querying a domain in which the called user is currently camped; sending a message to a specified domain based on a selection of the specified domain by the called user.

[0210] In some embodiments, the network device 800 is further configured to: send second indication information to the terminal device; wherein the second indication information comprises one or more of the following: a coding strategy suggested or allowed by the network device for the terminal device; a message type and / or a status code that needs to be sent or received by the terminal device when initiating a registration request and / or a call setup; one or more fields that can not be carried in a header of a SIP message in an IMS registration process.

[0211] In some embodiments, the first indication information is used to indicate a type of satellite for voice service of the terminal device.

[0212] In some embodiments, the type of satellite comprises one or more of the following: LEO, MEO, GEO.

[0213] In some embodiments, the network device comprises a P-CSCF.

[0214] In some embodiments, the first radio access type is an NTN-based radio access type.

[0215] In optional embodiments, the first receiving unit 710 can be a transceiver 1030. The network device 700 can further comprise a processor 1010 and a memory 1020, as shown in FIG. 10.

[0216] FIG. 8 is a schematic structural diagram of a terminal device 800 according to an embodiment of the present application. The terminal device 800 can comprise a first skipping unit 810.

[0217] The first skipping unit 810 is configured to skip a first step in a voice call setup process; wherein the first step comprises one or more of the following: a step related to called domain selection; a step related to secondary confirmation in a media negotiation process; a resource reservation confirmation step; a step of establishing a voice dedicated bearer or a quality of service (QoS) data flow.

[0218] In some embodiments, the step related to called domain selection comprises one or more of the following: determining a domain in which the called user has recently camped; querying a domain in which the called user is currently camped; sending a message to a specified domain based on a selection of the specified domain by the called user.

[0219] In some embodiments, the reply message that is first confirmed in the media negotiation process comprises a success response message in the case that the step of second confirmation related to the media negotiation process is skipped.

[0220] In some embodiments, the voice call shares a bearer with other data in the case that the step of establishing a voice dedicated bearer is skipped.

[0221] In some embodiments, the terminal device 800 is further configured to: send third indication information to the network device; wherein the third indication information is used to indicate one or a first number of codecs that can be selected in the call establishment process.

[0222] In some embodiments, the call establishment process is implemented through an SIP message, and a header field of the SIP message can not carry a part of fields related to routing.

[0223] In some embodiments, the header field of the SIP message can not carry one or more of the following fields: a starting line field, an initiation field, a receiving field, a call identification field, a passing field, a routing field, a contact field, and a record routing field.

[0224] In some embodiments, the voice call is implemented through an NTN.

[0225] In optional embodiments, the first skipping unit 810 can be a processor 1010. The terminal device 800 can further include a memory 1020 and a transceiver 1030, as shown in FIG. 10.

[0226] FIG. 9 is a schematic structural diagram of a network device 900 according to an embodiment of the present application. The network device 900 can include a second skipping unit 910.

[0227] The second skipping unit 910 is configured to skip a first step in a voice call establishment process; wherein the first step comprises one or more of the following: a step related to called domain selection; a step related to second confirmation in a media negotiation process; a resource reservation confirmation step; a step of establishing a voice dedicated bearer or a QoS data flow.

[0228] In some embodiments, the step related to called domain selection comprises one or more of the following: judging a domain in which a called user recently camps; querying a domain in which the called user currently camps; sending a message to a specified domain based on a selection of the called user.

[0229] In some embodiments, the reply message that is first confirmed in the media negotiation process comprises a success response message in the case that the step of second confirmation related to the media negotiation process is skipped.

[0230] In some embodiments, the voice call shares a bearer with other data in the case that the step of establishing a voice dedicated bearer is skipped.

[0231] In some embodiments, the network device 900 is further configured to receive third indication information sent by the terminal device, wherein the third indication information is used to indicate one or a first number of codecs that can be selected in the call establishment process.

[0232] In some embodiments, the call establishment process is implemented through an SIP message, and a header of the SIP message can not carry part of fields related to routing.

[0233] In some embodiments, the header of the SIP message can not carry one or more of the following fields: a start line field, an initiation field, a receiving field, a call identification field, a passing field, a routing field, a contact field, and a record routing field.

[0234] In some embodiments, the network device comprises one or more of the following: a P-CSCF and an S-CSCF.

[0235] In some embodiments, the voice call is implemented through an NTN.

[0236] In optional embodiments, the second skipping unit 910 can be a processor 1010. The network device 900 can further include a memory 1020 and a transceiver 1030, as shown in FIG. 10.

[0237] FIG. 10 is a schematic structural diagram of an apparatus for communication according to an embodiment of the present application. The dashed line in FIG. 10 indicates that the unit or module is optional. The apparatus 1000 can be used to implement the method described in the above method embodiments. The apparatus 1000 can be a chip, a terminal device, or a network device.

[0238] The apparatus 1000 can include one or more processors 1010. The processor 1010 can support the apparatus 1000 to implement the methods described in the foregoing method embodiments. The processor 1010 can be a general processor or a special-purpose processor. For example, the processor can be a central processing unit (CPU). Alternatively, the processor can also be other general processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, etc. The general processor can be a microprocessor or the processor can also be any conventional processor.

[0239] The apparatus 1000 can also include one or more memories 1020. The memory 1020 stores a program, which can be executed by the processor 1010, so that the processor 1010 performs the methods described in the foregoing method embodiments. The memory 1020 can be independent of the processor 1010 or integrated in the processor 1010.

[0240] The apparatus 1000 can also include a transceiver 1030. The processor 1010 can communicate with other devices or chips through the transceiver 1030. For example, the processor 1010 can perform data transceiving with other devices or chips through the transceiver 1030.

[0241] The embodiments of the present application also provide a computer readable storage medium for storing a program. The computer readable storage medium can be applied to the terminal or network device provided by the embodiments of the present application, and the program causes the computer to execute the method performed by the terminal or network device in the various embodiments of the present application.

[0242] The embodiments of the present application also provide a computer program product. The computer program product includes a program. The computer program product can be applied to the terminal or network device provided by the embodiments of the present application, and the program causes the computer to execute the method performed by the terminal or network device in the various embodiments of the present application.

[0243] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided by the embodiments of the present application, and the computer program causes the computer to execute the method performed by the terminal or network device in the various embodiments of the present application.

[0244] It should be understood that the terms "system" and "network" can be used interchangeably in this application. In addition, the terms used in this application are only used to explain the specific embodiments of the application, and are not intended to limit the application. The terms "first", "second", "third", and "fourth" and the like in the specification and claims of the application and the drawings are used to distinguish different objects, and are not used to describe a particular order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion.

[0245] In embodiments of the present application, the term "indicate" can be direct indication or indirect indication, or can represent an associated relationship. For example, A indicates B, which can mean that B can be obtained through A; or A indirectly indicates B, for example, A indicates C, and B can be obtained through C; or A and B have an associated relationship.

[0246] In embodiments of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean that B is determined only according to A, but B can also be determined according to A and / or other information.

[0247] In embodiments of the present application, the term "corresponding" can represent a direct or indirect corresponding relationship between the two, or can represent an associated relationship between the two, or can represent an indication and being indicated, configuration and being configured, and the like.

[0248] In embodiments of the present application, "predefined" or "preconfigured" can be implemented by pre-saving corresponding codes, tables or other information that can be used to indicate related information in devices (such as terminal devices and network devices), and the specific implementation manner of the present application is not limited. For example, predefinition can refer to definition in a protocol.

[0249] In embodiments of the present application, the "protocol" can refer to a standard protocol in the communication field, which can include, for example, an LTE protocol, an NR protocol, and a related protocol applied to a future communication system, and the present application is not limited thereto.

[0250] In embodiments of the present application, the term "and / or" is only used to describe the associated relationship between the associated objects, which means that there can be three relationships, for example, A and / or B, which can mean that A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in this paper generally represents an "or" relationship between the front and rear associated objects.

[0251] In the embodiments of the present application, the "comprising" can mean directly comprising or indirectly comprising. Alternatively, the "comprising" mentioned in the embodiments of the present application can be replaced by "indicating" or "for determining". For example, A comprising B can be replaced by A indicating B, or A for determining B.

[0252] In various embodiments of the present application, the size of the serial number of the above processes does not mean the order of execution, the execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0253] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0254] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on multiple network units. According to actual needs, part or all of the units can be selected to achieve the purpose of the present embodiment.

[0255] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically independently, or two or more units can be integrated into one unit.

[0256] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode. The computer readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server, data center and the like integrated with one or more available media sets. The available media can be magnetic media (for example, floppy disk, hard disk, magnetic tape), optical media (for example, digital video disc (DVD)) or semiconductor media (for example, solid state disk (SSD)) and the like.

[0257] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method of wireless communication, the method comprising: Comprising: The terminal device sends first indication information and / or encoding information to the network device; The first indication information is used to indicate whether the terminal device makes voice call through a first radio access type; and the encoding information is used to indicate an encoding mode supported or requested by the terminal device.

2. The method of claim 1, wherein, The encoding information is used to indicate one or more of the following: encoding type, code rate, frame format, transmission protocol, service type.

3. The method according to claim 1 or 2, characterized in that, The encoding information is carried in one or more of the following: One or more fields in a session initiation protocol (SIP) registration message header; A session description protocol offer included in the SIP registration message.

4. The method according to any one of claims 1-3, characterized in that, The first indication information is carried in a first message, and in a case where the first message meets a first condition, the first indication information indicates that the terminal device makes voice call through the first radio access type, and the first condition includes one or more of the following: The first message is sent in response to the terminal device moving into a network coverage area of the first radio access type; The first message is sent in response to the terminal device initiating first registration in the network coverage area of the first radio access type.

5. The method according to any one of claims 1-4, characterized in that, The first indication information is carried in a first message, and in a case where the first message meets a second condition, the first indication information indicates that the terminal device does not make voice call through the first radio access type; The second condition includes: The first message is sent in response to the terminal device entering a network coverage area other than the first radio access type from the network coverage area of the first radio access type.

6. The method according to any one of claims 1-4, characterized in that, The first indication information is carried in a registration request message in an IP multimedia subsystem (IMS) registration procedure.

7. The method of claim 6, wherein, The IMS registration procedure is implemented through a session initiation protocol (SIP) message, and a header of the SIP message can not carry part of fields related to routing.

8. The method of claim 7, wherein, The header of the SIP message can not carry one or more of the following fields: starting line field, initiation field, receiving field, call identification field, passing field, routing field, contact field, and record routing field.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: The terminal device receives second indication information sent by the network device; The second indication information includes one or more of the following: An encoding strategy suggested or allowed by the network device for the terminal device to use; A message type and / or status code required to be sent or received by the terminal device when initiating a registration request and / or call establishment; One or more fields in a SIP message in an IMS registration procedure, which can not be carried by the header of the SIP message.

10. The method of claim 9, wherein, The encoding strategy includes one or more of the following: encoding type, code rate, frame format, transmission protocol, and service type.

11. The method according to any one of claims 1-10, characterized in that, The first indication information is used to indicate a type of satellite through which the terminal device makes voice service.

12. The method of claim 11, wherein, The type of satellite includes one or more of the following: low earth orbit (LEO), medium earth orbit (MEO), and geostationary earth orbit (GEO).

13. The method according to any one of claims 1-12, characterized in that, The network device includes a proxy call session control function (P-CSCF).

14. The method of any one of claims 1-13, wherein, The first radio access type is a non-terrestrial network (NTN) based radio access type.

15. A method of wireless communication, the method comprising: Comprising: The network device receives first indication information and / or encoding information sent by the terminal device; The first indication information is used to indicate whether the terminal device makes voice call through a first radio access type; and the encoding information is used to indicate an encoding mode supported or requested by the terminal device.

16. The method of claim 15, wherein, The encoding information is used to indicate one or more of the following: encoding type, code rate, frame format, transmission protocol, and service type.

17. The method according to claim 15 or 16, characterized in that, The encoding information is carried in one or more of the following: One or more fields in a session initiation protocol (SIP) registration message header; A session description protocol offer included in the SIP registration message.

18. The method according to any one of claims 15-17, characterized by, The first indication information is carried in a first message, and the first indication information indicates that the terminal device makes voice call through the first radio access type when the first message meets a first condition, the first condition including one or more of the following: The first message is sent in response to the terminal device moving into a network coverage area of the first radio access type; The first message is sent in response to the terminal device initiating first registration in the network coverage area of the first radio access type.

19. The method according to any one of claims 15-18, characterized by, The first indication information is carried in a first message, and the first indication information indicates that the terminal device does not make voice call through the first radio access type when the first message meets a second condition. The second condition includes: The first message is sent in response to the terminal device moving from the network coverage area of the first radio access type to a network coverage area of a type other than the first radio access type.

20. The method of any one of any one of claims 15-19, wherein, The first indication information is carried in a registration request message in an IP multimedia subsystem (IMS) registration procedure.

21. The method of claim 20, wherein, The IMS registration procedure is implemented through a session initiation protocol (SIP) message, and a header of the SIP message can not carry part of fields related to routing.

22. The method of claim 21, wherein, The header of the SIP message can not carry one or more of the following fields: starting line field, initiation field, receiving field, call identification field, passing field, routing field, contact field, and record routing field.

23. The method of any one of claims 15-22, wherein, The method further includes: The network device determines whether to skip one or more of the following according to the first indication information: A step of establishing a voice dedicated bearer or a quality of service (QoS) data flow; A step related to called domain selection.

24. The method of claims 15-23, wherein, In the case of skipping the step of establishing a voice dedicated bearer, the voice call shares a bearer with other data.

25. The method of claim 23 or 24, wherein, The step related to called domain selection includes one or more of the following: Judging a domain in which a called user recently camps; Querying a domain in which the called user currently camps; Sending a message to a specified domain based on a selection of the called user.

26. The method of any one of claims 15-25, wherein, The method further includes: The network device sends second indication information to the terminal device; The second indication information includes one or more of the following: An encoding strategy suggested or allowed by the network device for the terminal device to use; A message type and / or status code required to be sent or received by the terminal device when initiating a registration request and / or call establishment. One or more fields in a header of a SIP message in an IMS registration procedure can not be carried.

27. The method of claim 26, wherein, The encoding strategy comprises one or more of the following: encoding type, code rate, frame format, transmission protocol, service type.

28. The method of any one of claims 15-27, wherein, The first indication information is used to indicate a type of satellite for voice service of the terminal device.

29. The method of claim 28, wherein, The type of satellite comprises one or more of the following: low earth orbit (LEO), medium earth orbit (MEO), and geostationary earth orbit (GEO).

30. The method of any one of claims 15-29, wherein, The network device comprises a proxy call session control function (P-CSCF).

31. The method of any one of claims 15-30, wherein, The first radio access type is a non-terrestrial network (NTN) based radio access type.

32. A method of wireless communication, the method comprising: The method comprises: The terminal device skips a first step in a voice call setup procedure. The first step comprises one or more of the following: a step related to called domain selection; a step related to secondary confirmation in a media negotiation process; a resource reservation confirmation step; a step of establishing a voice dedicated bearer or a quality of service (QoS) data flow.

33. The method of claim 32, wherein, The step related to called domain selection comprises one or more of the following: judging a domain in which a called user has recently camped; inquiring a domain in which the called user currently camps; sending a message to a specified domain based on a selection of the called user.

34. The method of claim 32 or 33, wherein, In the case of skipping the step related to secondary confirmation in the media negotiation process, a reply message of a first confirmation in the media negotiation process comprises a success response message.

35. The method of any one of claims 32-34, wherein, In the case of skipping the step of establishing a voice dedicated bearer, the voice call shares a bearer with other data.

36. The method of any one of claims 32-35, wherein, The method further comprises: The terminal device sends third indication information to a network device. The third indication information is used to indicate one or a first number of codecs (codec) that can be selected in a call setup procedure.

37. The method of any one of claims 32-36, wherein, The call setup procedure is implemented through a session initiation protocol (SIP) message, and a header of the SIP message can not carry part of fields related to routing.

38. The method of claim 37, wherein, The header of the SIP message can not carry one or more of the following fields: a start line field, an initiation field, a reception field, a call identification field, a passage field, a routing field, a contact field, and a record routing field.

39. The method of any one of claims 32-38, wherein, The voice call is implemented through a non-terrestrial network (NTN).

40. A method for wireless communication, comprising: The method comprises: A network device skips a first step in a voice call setup procedure. The first step comprises one or more of the following: a step related to called domain selection; a step related to secondary confirmation in a media negotiation process; a resource reservation confirmation step; a step of establishing a voice dedicated bearer or a quality of service (QoS) data flow.

41. The method of claim 40, wherein, The step related to called domain selection comprises one or more of the following: judging a domain in which a called user has recently camped; inquiring a domain in which the called user currently camps; sending a message to a specified domain based on a selection of the called user.

42. The method of claim 40 or 41, wherein, In the case of skipping the step related to secondary confirmation in the media negotiation process, a reply message of a first confirmation in the media negotiation process comprises a success response message.

43. The method of any one of claims 40-42, wherein, In the case of skipping the step of establishing a voice dedicated bearer, the voice call shares a bearer with other data.

44. The method of any one of claims 40-43, wherein, The method further comprises: The network device receives third indication information sent by a terminal device. The third indication information is used for indicating one or a first number of codecs codec that can be selected in a call establishment process.

45. The method of any one of claims 40-44, wherein, The call establishment process is implemented through a session initiation protocol SIP message, and a header field of the SIP message can not carry a part field related to routing.

46. The method of claim 45, wherein, The header field of the SIP message can not carry one or more of the following fields: a start line field, a field of initiation, a field of reception, a call identification field, a field of passage, a routing field, a contact field, and a recorded routing field.

47. The method of any one of claims 40-46, wherein, The network device includes one or more of the following: a proxy call session control function P-CSCF, and a service call session control function S-CSCF.

48. The method of any one of claims 40-47, wherein, The voice call is implemented through an NTN.

49. A terminal device, comprising: The terminal device includes: A first sending unit configured to send first indication information and / or encoding information to a network device. The first indication information is used for indicating whether the terminal device performs voice call through a first radio access type; and the encoding information is used for indicating an encoding mode supported or requested by the terminal device.

50. The terminal device of claim 49, wherein, The encoding information is used for indicating one or more of the following: an encoding type, a code rate, a frame format, a transmission protocol, and a service type.

51. The terminal device of claim 49 or 50, wherein, The encoding information is carried in one or more of the following: One or more fields in a header of a session initiation protocol SIP registration message; A session description protocol proposal included in a SIP registration message.

52. The terminal device of any one of claims 49-51, wherein, The first indication information is carried in a first message, and in a case where the first message meets a first condition, the first indication information indicates that the terminal device performs voice call through the first radio access type, and the first condition includes one or more of the following: The first message is sent in response to the terminal device moving into a network coverage area of the first radio access type; The first message is sent in response to the terminal device initiating first registration in a network coverage area of the first radio access type.

53. The terminal device of any one of claims 49-52, wherein, The first indication information is carried in a first message, and in a case where the first message meets a second condition, the first indication information indicates that the terminal device does not perform voice call through the first radio access type. The second condition includes: The first message is sent in response to the terminal device entering a network coverage area other than the first radio access type from the network coverage area of the first radio access type.

54. The terminal device of any one of claims 49-53, wherein, The first indication information is carried in a registration request message in an IP multimedia subsystem IMS registration process.

55. The terminal device of claim 54, wherein, The IMS registration process is implemented through a session initiation protocol SIP message, and a header field of the SIP message can not carry a part field related to routing.

56. The terminal device of claim 55, wherein, The header field of the SIP message can not carry one or more of the following fields: a start line field, a field of initiation, a field of reception, a call identification field, a field of passage, a routing field, a contact field, and a recorded routing field.

57. The terminal device of any one of claims 49-56, wherein, The terminal device is further configured to: Receive second indication information sent by the network device. The second indication information includes one or more of the following: An encoding strategy suggested or allowed by the network device for the terminal device to use. A message type and / or a status code that needs to be sent or received by the terminal device when initiating a registration request and / or a call setup; One or more fields in a SIP message header in an IMS registration procedure that can not be carried.

58. The terminal device of claim 57, wherein, The encoding strategy comprises one or more of the following: encoding type, code rate, frame format, transmission protocol, service type.

59. The terminal device of any one of claims 49-58, wherein, The first indication information is used to indicate a type of satellite through which the terminal device performs voice service.

60. The terminal device of claim 59, wherein, The type of satellite comprises one or more of the following: low earth orbit (LEO), medium earth orbit (MEO), and geostationary earth orbit (GEO).

61. The terminal device of any one of claims 49-60, wherein, The network device comprises a proxy call session control function (P-CSCF).

62. The terminal device of any one of claims 49-61, wherein, The first radio access type is a non-terrestrial network (NTN) based radio access type. 63.A network device, characterized by, Comprise: A first receiving unit configured to receive first indication information and / or encoding information sent by a terminal device; The first indication information is used to indicate whether the terminal device performs voice communication through a first radio access type; and the encoding information is used to indicate an encoding mode supported or requested by the terminal device.

64. The network device of claim 63, wherein, The encoding information is used to indicate one or more of the following: encoding type, code rate, frame format, transmission protocol, and service type.

65. The network device of claim 63 or 64, wherein, The encoding information is carried in one or more of the following: One or more fields in a session initiation protocol (SIP) registration message header; A session description protocol offer included in a SIP registration message.

66. The network device of any of claims 63-65, wherein, The first indication information is carried in a first message, and in a case where the first message satisfies a first condition, the first indication information indicates that the terminal device performs voice communication through the first radio access type, and the first condition comprises one or more of the following: The first message is sent in response to the terminal device moving into a network coverage area of the first radio access type; The first message is sent in response to the terminal device initiating a first registration in a network coverage area of the first radio access type.

67. The network device of any of claims 63-66, wherein, The first indication information is carried in a first message, and in a case where the first message satisfies a second condition, the first indication information indicates that the terminal device does not perform voice communication through the first radio access type. The second condition comprises: The first message is sent in response to the terminal device moving from a network coverage area of the first radio access type to a network coverage area of a type other than the first radio access type.

68. The network device of any of claims 63-67, wherein, The first indication information is carried in a registration request message in an IP multimedia subsystem (IMS) registration procedure.

69. The network device of claim 68, wherein, The IMS registration procedure is implemented through a session initiation protocol (SIP) message, and a header of the SIP message can not carry part of fields related to routing.

70. The network device of claim 69, wherein, The header of the SIP message can not carry one or more of the following fields: starting line field, initiation field, receiving field, call identification field, passing field, routing field, contact field, and record routing field.

71. The network device of any of claims 63-70, wherein, The network device is further configured to: Determine, according to the first indication information, whether to skip one or more of the following: A step of establishing a voice dedicated bearer or a quality of service (QoS) data flow; A step related to called domain selection.

72. The network device of claim 71, wherein, In a case that the step of establishing the voice dedicated bearer is skipped, the voice call shares a bearer with other data.

73. The network device of claim 71 or 72, wherein, The steps related to the called domain selection include one or more of the following: judging a domain where the called user recently camps; inquiring a domain where the called user currently camps; sending a message to a specified domain based on a selection of the called user.

74. The network device of any of claims 63-73, wherein, The network device is further configured to: send second indication information to the terminal device; The second indication information includes one or more of the following: a coding strategy that the network device suggests or allows the terminal device to use; a message type and / or a status code that the terminal device needs to send or receive when initiating a registration request and / or a call establishment; one or more fields that a header of a SIP message in an IMS registration procedure can not carry.

75. The network device of claim 74, wherein, The coding strategy includes one or more of the following: a coding type, a code rate, a frame format, a transmission protocol, and a service type.

76. The network device of any of claims 63-75, wherein, The first indication information is used to indicate a type of satellite for voice service of the terminal device.

77. The network device of claim 76, wherein, The type of satellite includes one or more of the following: low earth orbit (LEO), medium earth orbit (MEO), and geostationary earth orbit (GEO).

78. The network device of any of claims 63-77, wherein, The network device includes a proxy call session control function (P-CSCF).

79. The network device of any of claims 63-78, wherein, The first radio access type is a non-terrestrial network (NTN) based radio access type.

80. A terminal device, comprising: The terminal device includes: a first skipping unit configured to skip a first step in a voice call establishment procedure; The first step includes one or more of the following: steps related to called domain selection; steps related to secondary confirmation in a media negotiation process; a resource reservation confirmation step; a step of establishing a voice dedicated bearer or a quality of service (QoS) data flow.

81. The terminal device of claim 80, wherein, The steps related to called domain selection include one or more of the following: judging a domain where the called user recently camps; inquiring a domain where the called user currently camps; sending a message to a specified domain based on a selection of the called user.

82. The terminal device of claim 80 or 81, wherein, In a case that the step of skipping the secondary confirmation in the media negotiation process is skipped, a reply message of a first confirmation in the media negotiation process includes a success response message.

83. The terminal device of any one of claims 80-82, wherein, In a case that the step of establishing the voice dedicated bearer is skipped, the voice call shares a bearer with other data.

84. The terminal device of any one of claims 80-83, wherein, The terminal device is further configured to: send third indication information to the network device; The third indication information is used to indicate one or a first number of codecs (codec) that can be selected in a call establishment procedure.

85. The terminal device of any one of claims 80-84, wherein, The call establishment procedure is implemented through a session initiation protocol (SIP) message, and a header of the SIP message can not carry part of fields related to routing.

86. The terminal device of claim 85, wherein, The header of the SIP message can not carry one or more of the following fields: a start line field, an initiation field, a reception field, a call identification field, a passage field, a routing field, a contact field, and a record routing field.

87. The terminal device of any one of claims 80-86, wherein, The voice call is implemented through a non-terrestrial network (NTN).

88. A network device, comprising: includes: a second skipping unit configured to skip a first step in a voice call establishment procedure; The first step includes one or more of the following: steps related to called domain selection; steps related to secondary confirmation in a media negotiation process; a resource reservation acknowledgement step; a step of establishing a voice dedicated bearer or a quality of service (QoS) data flow.

89. The network device of claim 88, wherein, The steps related to the called domain selection include one or more of the following: judging a domain in which the called user recently camps; inquiring a domain in which the called user currently camps; sending a message to a specified domain based on a selection of the called user.

90. The network device of claim 88 or 89, wherein, In the case of the steps related to the secondary confirmation in the media negotiation process, the reply message of the first confirmation in the media negotiation process includes a success response message.

91. The network device of any of claims 88-90, wherein, In the case of skipping the step of establishing a voice dedicated bearer, the voice call shares a bearer with other data.

92. The network device of any of claims 88-91, wherein, The network device is further configured to: receive third indication information sent by the terminal device; The third indication information is used to indicate one or a first number of codecs (codec) that can be selected in a call establishment process.

93. The network device of any of claims 88-92, wherein, The call establishment process is implemented through a session initiation protocol (SIP) message, and a header of the SIP message can not carry a part of fields related to routing.

94. The network device of claim 93, wherein, The header of the SIP message can not carry one or more of the following fields: a start line field, an initiation field, a receiving field, a call identification field, a passing field, a routing field, a contact field, and a record routing field.

95. The network device of any of claims 88-94, wherein, The network device includes one or more of the following: a proxy call session control function (P-CSCF) and a serving call session control function (S-CSCF).

96. The network device of any of claims 88-95, wherein, The voice call is implemented through an NTN.

97. A terminal device, comprising: The terminal device includes a transceiver, a memory, and a processor. The memory is configured to store a program, and the processor is configured to invoke the program in the memory and control the transceiver to receive or send a signal, so that the terminal device performs the method in any one of claims 1-14 and 32-39.

98. A network device, comprising: The network device includes a transceiver, a memory, and a processor. The memory is configured to store a program, and the processor is configured to invoke the program in the memory and control the transceiver to receive or send a signal, so that the network device performs the method in any one of claims 15-31 and 40-48.

99. An apparatus, comprising: The apparatus includes a processor configured to invoke a program from a memory, so that the apparatus performs the method in any one of claims 1-48.

100. A chip, comprising: The apparatus includes a processor configured to invoke a program from a memory, so that the apparatus performs the method in any one of claims 1-48.

101. A computer readable storage medium, characterized in that, The apparatus includes a processor configured to invoke a program from a memory, so that the apparatus performs the method in any one of claims 1-48.

102. A computer program product, characterized in that, The apparatus includes a processor configured to invoke a program from a memory, so that the apparatus performs the method in any one of claims 1-48.

103. A computer program characterised in that, The apparatus includes a processor configured to invoke a program from a memory, so that the apparatus performs the method in any one of claims 1-48. The apparatus includes a processor configured to invoke a program from a memory, so that the apparatus performs the method in any one of claims 1-48.

Images