Wireless communication method, terminal device, and network device

Abstract

Provided are a wireless communication method, a terminal device, and a network device. The method comprises: a terminal device sending first indication 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. By means of first indication information, a network device can be aware of whether a terminal device performs a voice call by means of a first radio access type, thereby executing a corresponding voice call establishment process.

Description

Wireless communication method, terminal device and network device TECHNICAL FIELD

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

[0002] 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 (such as satellites) has increased significantly.

[0003] 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 to a network device; wherein the first indication information is used to indicate whether the terminal device makes voice calls through a first wireless access type.

[0006] In a second aspect, a wireless communication method is provided, which includes: a network device receiving first indication information sent by a terminal device; wherein the first indication information is used to indicate whether the terminal device makes voice calls through a first wireless access type.

[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; a step of establishing a voice dedicated bearer or a quality of service (QoS) data flow.

[0008] In a fourth aspect, a wireless communication method is provided, which includes: a network 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; a step of establishing a voice dedicated bearer or a QoS data flow.

[0009] In a fifth aspect, a terminal device is provided, which includes: a first sending unit configured to send first indication information to a network device; wherein the first indication information is used to indicate whether the terminal device makes voice calls through a first wireless access type.

[0010] In a sixth aspect, a network device is provided, which comprises: a first receiving unit configured to receive first indication 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.

[0011] In a seventh aspect, a terminal device is provided, which comprises: 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 the following: 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 establishing a voice dedicated bearer or a QoS data flow.

[0012] In an eighth aspect, a network device is provided, which comprises: 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 the following: 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 establishing a voice dedicated bearer or a QoS data flow.

[0013] In a ninth aspect, a terminal device is provided, which comprises a processor and a memory, wherein the memory is configured to store one or more computer programs, and 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, which comprises a processor, a memory and a transceiver, wherein the memory is configured to store one or more computer programs, and 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 an 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, and the computer program causes a terminal device and / or a network device to perform some or all of the steps in the methods of the 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 operable to cause an end device and / or a network device to perform some or all of the steps in the methods of 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 of 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 a 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 according to an embodiment of the present application.

[0024] FIG. 5 is a schematic flowchart of another wireless communication method according to an embodiment of the present application.

[0025] FIG. 6 is a schematic structural diagram of a terminal device according to an embodiment of the present application.

[0026] FIG. 7 is a schematic structural diagram of a network device according to an embodiment of the present application.

[0027] FIG. 8 is a schematic structural diagram of another terminal device according to an embodiment of the present application.

[0028] FIG. 9 is a schematic structural diagram of another network device according to an embodiment of the present application.

[0029] FIG. 10 is a schematic structural diagram of an apparatus for communication provided by an embodiment 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 by 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 by embodiments of the present application.

[0035] It should be understood that the technical solutions of 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 devices 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 to the network device.

[0076] The first indication information can be used to indicate a wireless access type. The wireless 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 wireless access type. In other words, the first indication information can be used to indicate the wireless access type through which the terminal device makes a voice call, voice operation, or voice service. The wireless access type can include the first wireless 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 wireless access type can be, for example, a wireless access type based on an NTN. 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 know 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 that the terminal device makes voice call through NTN through the first indication information, 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 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 process. That is, the terminal device can carry the first indication information in the message in the IMS registration process. For example, the first indication information can be carried in the registration request message (for example, the RIGISTER message described in step S101 in the foregoing) in the IMS registration process. In the case where the first message is a message in the registration process, the method shown in FIG. 4 can also be referred to as enhancement for the registration process.

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

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

[0083] For example, the terminal device can send the registration request message through the first radio access type to indicate that the terminal device makes voice call through the first radio access type. For another example, the terminal device can send the registration request message through a non-first radio access type (for example, a TN-based radio access type) to indicate that the terminal device does not make voice call through the first radio access type.

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

[0085] For example, the terminal device sends the registration request message through a certain radio access type (for example, the first radio access type), and the registration request message carries the 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.

[0086] 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 of the first message.

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

[0088] 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.

[0089] 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.

[0090] 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.

[0091] 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.

[0092] 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.

[0093] Taking the first radio access type as NTN for example, when the terminal device leaves the NTN coverage area and enters a TN coverage area, and re-initiates a registration request, the terminal device can send the first indication information to indicate that the terminal device accesses through the TN.

[0094] As described above, the first indication information can be transmitted in the IMS registration process. The IMS registration process can be implemented through a SIP message. It is proposed in the present application that the header field 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 field of the SIP message can be omitted, thereby reducing the load of the SIP message.

[0095] The header of the SIP message can not carry one or more of the following fields: a start line field, a from (From) field, a to (To) field, a call-ID (Call-ID) field, a via (Via) field, a route (Route) field, a contact (Contact) field, a record-route (Record-Route) field. These fields are described below in Table 1.

[0096] Table 1

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

[0098] 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 needs to be sent or received by the terminal device when initiating a registration request and / or a call establishment; a field that can not be carried by a SIP header.

[0099] The coding strategy suggested or allowed by the network device for the terminal device to use can include one or more coding types or codecs. Among them, a codec refers 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 process of initiating a voice call establishment. The coding 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 performs voice service. Exemplarily, compared with GEO, LEO or MEO can support more codecs, so the network device in LEO or MEO can suggest or allow the terminal device to use more codecs.

[0100] For example, in a case where the first indication information indicates that the terminal device performs voice communication through the first radio access type, the second indication information can send less codec for the terminal device to select and use. Illustratively, in a case where the first radio access type is NTN, the codec type supported by NTN-based communication is less, and the terminal device carries a codec that NTN cannot support in the voice call establishment process initiated by the terminal device, which will cause problems such as waste of communication resources or redundancy of the voice call establishment process. By indicating the recommended or allowed codec 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.

[0101] For another example, in a case where the first indication information indicates the type of satellite through which the terminal device performs voice service, the network device can determine the codec supported by the corresponding satellite according to the type of the satellite, and part or all of the codec supported by the corresponding satellite as the codec recommended or allowed by the network device for the terminal device to use, and indicated 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.

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

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

[0104] As described above, in a case where the terminal device performs voice communication through the first radio access type, the network device and / or the terminal device can perform a registration process and / or a call establishment process for the first radio access type. By indicating 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 establishment through the second indication information, the terminal device can know which message type and / or status code to use to perform the registration process and / or the call establishment process subsequently, thereby performing the registration process and / or the call establishment process for the first radio access type.

[0105] The second indication information can indicate a field that can not be carried in a SIP header field during a call setup procedure. As described above, the call setup procedure can be implemented by a SIP message, and the SIP message can include 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.

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

[0107] 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.

[0108] Based on the first indication information and / or the second indication information, the terminal device and the network device can determine how to perform subsequent voice call setup and / or registration procedures, thereby helping the terminal device and the network device to determine the consistency of the behavior.

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

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

[0111] The present application also provides an improved voice call setup procedure. The following will be 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).

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

[0113] At step S510, the terminal device or the network device skips a first step in a voice call setup procedure. The voice call setup procedure can be implemented by IMS, i.e., an IMS voice call setup procedure. For example, the first step can be one or more steps in FIG. 3.

[0114] It can be understood that, in the present application, some steps in the voice call setup procedure can be omitted, i.e., the present application can implement procedure simplification in the voice call setup process.

[0115] It should be noted that, in the voice call setup procedure, one or both of the terminal device and the network device can skip some steps. The steps skipped by the terminal device and the steps skipped by the network device can be the same or different, i.e., the first step skipped by the terminal device and the first step skipped by the network device can be the same or different.

[0116] By skipping the first step, the voice call setup procedure can be shortened, thereby reducing the waiting time for voice call setup.

[0117] In some embodiments, step S510 can be performed in a case where the voice call is implemented by a first radio access type. For example, step S510 can be performed in a case where the voice call is implemented by 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 setting up a voice call, and the present application can skip some steps, thereby reducing the waiting time for NTN voice call setup.

[0118] 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 a media negotiation process; a resource reservation confirmation step; a step of establishing a voice dedicated bearer or a QoS data flow. The following will be described respectively.

[0119] The step related to called domain selection can include some or all steps in T-ADS. That is, the terminal device or the network device can omit some or all steps in T-ADS. The step related to called domain selection can include one or more of the following: determining 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.

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

[0121] The steps related to the second confirmation in the media negotiation procedure can include one or more of steps S209-S215, S309-S315 shown in FIG. 3.

[0122] In some embodiments, in the case of skipping the steps related to the second confirmation in the media negotiation procedure, the reply message of the first confirmation in the media negotiation procedure can include a success response message. That is, the reply message can be a 200 OK PRACK, instead of 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 the second confirmation (steps S209-S215, S309-S315).

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

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

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

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

[0127] 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 procedure. 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 can be selected in the call establishment procedure indicated by the terminal device is limited, i.e., the codecs are relatively simple, and the resources for processing the codecs are easier to reserve.

[0128] 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.

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

[0130] 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 to the terminal device the recommended or allowed codecs, the terminal device can select one or a first number of codecs from the recommended or allowed codecs, and feed back the selected codecs to the network device through the third indication information.

[0131] As described above, the call setup process can be implemented through SIP messages, and the header field of the SIP message can not carry the part field related to routing. For example, the header field 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. The related fields have been described in detail above, and will not be described here.

[0132] The methods shown in FIG. 4 and FIG. 5 can be implemented in combination.

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

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

[0135] For ease of understanding, the present application will be described in detail below in combination with FIG. 2 and FIG. 3 through embodiment 1 and embodiment 2.

[0136] Embodiment 1

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

[0138] The NTN call setup procedure can omit the T-ADS step, because NTN voice does not have the possibility to use 2 / 3G CS domain.

[0139] 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 include one or more of the following 3 steps.

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

[0141] 2. The first Invite message is sent by the MO UE and the reply is received after completion (steps S201-S208, S301-S308), without the need for a second confirmation (steps S209-S215). The reply message at step S208 can be a 200 OK PRACK instead of a 183 Session Progress.

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

[0143] The NTN call setup procedure can omit the resource reservation confirmation step (steps 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.

[0144] The routing of SIP messages in IMS is accomplished through SIP header field information. 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.

[0145] Embodiment 2

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

[0147] 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, first indication information is added in the REGISTER message to indicate that the UE performs voice operation through SAT access, and the first indication information can further indicate which type of SAT access (such as Leo, Meo, or Geo) is used by the UE.

[0148] 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 accessed through the TN.

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

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

[0151] 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 process: one or more codecs; message types and / or status codes that need to be sent or received in the case where the UE initiates the call setup; fields that can not be carried in the SIP header. The following will be described respectively.

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

[0153] The reply message can carry the following information: message types and / or status codes that need to be sent or received in the case where the UE initiates the call setup. 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.

[0154] 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.

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

[0156] The method embodiments of the present application are described in detail above, and the device embodiments of the present application will be described in detail below. It should be understood that the description of the method embodiments and the description of the device embodiments correspond to each other, and therefore, the parts not described in detail can be referred to the foregoing method embodiments.

[0157] 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.

[0158] The first sending unit 610 is configured to send first indication information to a network device, wherein the first indication information is used to indicate whether the terminal device performs voice communication through a first radio access type.

[0159] 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 when 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 first registration in the network coverage area of the first radio access type.

[0160] 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 when the first message satisfies a second condition; and the second condition includes that 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.

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

[0162] In some embodiments, the IMS registration procedure 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.

[0163] In some embodiments, the header field 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.

[0164] 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 includes 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 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.

[0165] In some embodiments, the first indication information is used to indicate a type of satellite through which the terminal device performs voice service.

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

[0167] In some embodiments, the network device includes a P-CSCF.

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

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

[0170] 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 include a first receiving unit 710.

[0171] The first receiving unit 710 is configured to receive first indication information sent by a terminal device; wherein the first indication information is used to indicate whether the terminal device performs voice call through a first radio access type.

[0172] 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 call 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 first registration in the network coverage area of the first radio access type.

[0173] 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 call through the first radio access type in a case where the first message satisfies a second condition; wherein 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.

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

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

[0176] 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, a record routing field.

[0177] 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.

[0178] In some embodiments, in the case of skipping the step of establishing a voice dedicated bearer, the voice call shares a bearer with other data.

[0179] In some embodiments, the step related to called domain selection includes one or more of the following: determining 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.

[0180] In some embodiments, the network device 800 is further configured to send second indication information to the terminal device, wherein 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 call establishment; one or more fields in a header field of a SIP message in an IMS registration procedure that can not be carried.

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

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

[0183] In some embodiments, the network device includes a P-CSCF.

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

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

[0186] 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 include a first skipping unit 810.

[0187] The first skipping unit 810 is configured to skip a first step in a voice call setup procedure; 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.

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

[0189] In some embodiments, 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.

[0190] In some embodiments, in the case of skipping the step of establishing a voice dedicated bearer, the voice call shares a bearer with other data.

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

[0192] In some embodiments, the call setup procedure is implemented by a session initiation protocol (SIP) message, and a header of the SIP message can not carry a part field related to routing.

[0193] 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 reception field, a call identification field, a passage field, a routing field, a contact field, and a record routing field.

[0194] In some embodiments, the voice call is implemented by a non-terrestrial network (NTN).

[0195] 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.

[0196] 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.

[0197] The second skipping unit 910 is configured to skip a first step in a voice call establishment procedure, 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 QoS data flow.

[0198] In some embodiments, the step related to called domain selection comprises one or more of the following: determining 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.

[0199] 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 comprises a success response message.

[0200] In some embodiments, in the case of skipping the step of establishing a voice dedicated bearer, the voice call shares a bearer with other data.

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

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

[0203] 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 passage field, a routing field, a contact field, and a record routing field.

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

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

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

[0207] 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.

[0208] 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.

[0209] 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.

[0210] 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.

[0211] Embodiments of the present application also provide a computer readable storage medium for storing a program. The computer readable storage medium can be applied in 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.

[0212] 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 in 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.

[0213] Embodiments of the present application also provide a computer program. The computer program can be applied in 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.

[0214] 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.

[0215] 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.

[0216] 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.

[0217] 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.

[0218] In embodiments of the present application, "predefined" or "preconfigured" can be realized 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.

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

[0220] In embodiments of the present application, the term "and / or" is only used to describe the association 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.

[0221] 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.

[0222] 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.

[0223] 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.

[0224] 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.

[0225] 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.

[0226] 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.

[0227] 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 to the network device; Wherein, the first indication information is used to indicate whether the terminal device makes voice call through a first radio access type.

2. The method of claim 1, wherein, The first indication information is carried in a first message, and in the case that 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 within a network coverage area of the first radio access type.

3. The method according to claim 1 or 2, characterized in that, The first indication information is carried in a first message, and in the case that 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; Wherein, 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.

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

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

6. The method of claim 5, wherein, The header 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.

7. The method according to any one of claims 1 to 6, characterized in that, The method further comprises: The terminal device receives second indication information sent by the network device; Wherein, the second indication information includes one or more of the following: Encoding strategy suggested or allowed by the network device for the terminal device to use; Message type and / or status code that needs to be sent or received by the terminal device when initiating a registration request and / or call establishment; One or more fields in the header of the SIP message in the IMS registration process.

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

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

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

11. The method according to any one of claims 1-10, characterized in that, The first radio access type is a non-terrestrial network (NTN) based radio access type.

12. A method of wireless communication, the method comprising: Comprising: The network device receives first indication information sent by the terminal device; Wherein, the first indication information is used to indicate whether the terminal device makes voice call through a first radio access type.

13. The method of claim 12, wherein, The first indication information is carried in a first message, and in the case that 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 a network coverage area of the first radio access type.

14. The method according to claim 12 or 13, characterized in that, 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 meets a second condition. The second condition includes: 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 a network coverage area of the first radio access type. The first indication information is carried in a registration request message in an IP multimedia subsystem (IMS) registration procedure.

15. The method according to any one of claims 12-14, characterized in that, The IMS registration procedure is implemented through a session initiation protocol (SIP) message, and a header of the SIP message can not carry a part field related to routing.

16. The method of claim 15, 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.

17. The method of claim 16, wherein, The method further includes:

18. The method according to any one of claims 12-17, characterized by, The network device determines, 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. In a case where the step of establishing a voice dedicated bearer is skipped, the voice call shares a bearer with other data.

19. The method of claim 18, wherein, The step related to called domain selection includes one or more of the following:

20. The method of claim 18 or 19, wherein, 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. The method further includes:

21. The method of any one of claims 12-20, wherein, 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 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 call establishment; one or more fields that a header of a SIP message in an IMS registration procedure can not carry. The first indication information is used to indicate a type of satellite through which the terminal device makes voice services.

22. The method of any one of claims 12-21, 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).

23. The method of claim 22, wherein, The network device includes a proxy call session control function (P-CSCF).

24. The method of any one of claims 12-23, wherein, The first radio access type is a non-terrestrial network (NTN)-based radio access type.

25. The method of any one of claims 12-24, wherein, The method includes:

26. A method of wireless communication, the method comprising: The terminal device skips a first step in a voice call establishment procedure. 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; a step of establishing a voice dedicated bearer or a quality of service (QoS) data flow. The step related to called domain selection includes one or more of the following:

27. The method of claim 26, wherein, judging a domain in which a called user has recently camped; inquiring a domain in which the called user currently camps; and sending a message to a specified domain based on a selection of the called user. query a domain where the called user currently camps; send a message to a specified domain selected by the called user based on the specified domain.

28. The method of claim 26 or 27, wherein, In a case where a step of twice confirming is skipped in the media negotiation process, a reply message of first-time confirmation in the media negotiation process includes a success response message.

29. The method of any one of claims 26-28, wherein, In a case where a step of establishing a voice dedicated bearer is skipped, the voice call shares a bearer with other data.

30. The method of any one of claims 26-29, wherein, The method further includes: The terminal device sends third indication information to the network device; The third indication information is used to indicate one or a first number of codecs that can be selected in a call setup process.

31. The method of any one of claims 26-30, wherein, The call setup process is implemented by a session initiation protocol (SIP) message, and a header field of the SIP message can not carry a part of fields related to routing.

32. The method of claim 31, wherein, The header field of the SIP message can not carry 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 recorded routing field.

33. The method of any one of claims 26-32, wherein, The voice call is implemented by a non-terrestrial network (NTN).

34. A method of wireless communication, the method comprising: The method includes: The network device skips a first step in a voice call setup process. The first step includes one or more of the following: a step related to called domain selection; a step of twice confirming 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.

35. The method of claim 34, wherein, The step related to called domain selection includes one or more of the following: judging a domain where a called user recently camps; querying a domain where the called user currently camps; sending a message to a specified domain selected by the called user based on the specified domain.

36. The method of claim 34 or 35, wherein, In a case where a step of twice confirming is skipped in the media negotiation process, a reply message of first-time confirmation in the media negotiation process includes a success response message.

37. The method of any one of claims 34-36, wherein, In a case where a step of establishing a voice dedicated bearer is skipped, the voice call shares a bearer with other data.

38. The method of any one of claims 34-37, wherein, The method further includes: The network device receives third indication information sent by a terminal device; The third indication information is used to indicate one or a first number of codecs that can be selected in a call setup process.

39. The method of any one of claims 34-38, wherein, The call setup process is implemented by a session initiation protocol (SIP) message, and a header field of the SIP message can not carry a part of fields related to routing.

40. The method of claim 39, wherein, The header field of the SIP message can not carry 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 recorded routing field.

41. The method of any one of claims 34-40, 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).

42. The method of any one of claims 34-41, wherein, The voice call is implemented by an NTN.

43. A terminal device, comprising: The terminal device includes: a first sending unit configured to send first indication information to a network device; The first indication information is used to indicate whether the terminal device performs a voice call by a first radio access type.

44. The terminal device of claim 43, wherein, 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 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 first registration in the network coverage area of the first radio access type.

45. The terminal device of claim 43 or 44, wherein, 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 in a case where the first message satisfies a second condition; The second condition includes: The first message is sent in response to the terminal device entering a network coverage area that is not of the first radio access type from the network coverage area of the first radio access type.

46. The terminal device of any one of claims 43-45, wherein, The first indication information is carried in a registration request message in an IP multimedia subsystem (IMS) registration procedure.

47. The terminal device of claim 46, wherein, The IMS registration procedure 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.

48. The terminal device of claim 47, wherein, The header field 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.

49. The terminal device of any one of claims 43-48, 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 call establishment; One or more fields in a SIP message in an IMS registration procedure that can not be carried in the header field.

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

51. The terminal device of claim 50, 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).

52. The terminal device of any one of claims 43-51, wherein, The network device includes a proxy call session control function (P-CSCF).

53. The terminal device of any one of claims 43-52, wherein, The first radio access type is a non-terrestrial network (NTN) based radio access type.

54. A network device, comprising: The network device includes: a first receiving unit configured to receive first indication 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.

55. The network device of claim 54, wherein, 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 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 first registration in the network coverage area of the first radio access type.

56. The network device of claim 54 or 55, wherein, 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 in a case where the first message satisfies a second condition. The second condition includes: The first message is sent in response to the terminal device entering a network coverage area of a network that is not of the first radio access type from a network coverage area of the network of the first radio access type.

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

58. The network device of claim 57, wherein, The IMS registration procedure is implemented through a session initiation protocol (SIP) message, and a header field of the SIP message does not carry a part field related to routing.

59. The network device of claim 58, wherein, The header field of the SIP message does 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.

60. The network device of any of claims 54-59, 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.

61. The network device of claim 60, wherein, In a case where the step of establishing a voice dedicated bearer is skipped, the voice communication shares a bearer with other data.

62. The network device of claim 60 or 61, wherein, The step related to called domain selection includes 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.

63. The network device of any of claims 54-62, 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: an encoding 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 call establishment; one or more fields that a header field of a SIP message in an IMS registration procedure does not carry.

64. The network device of any of claims 54-63, wherein, The first indication information is used to indicate a type of a satellite through which the terminal device performs voice service.

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

66. The network device of any of claims 54-65, wherein, The network device includes a proxy call session control function (P-CSCF). 67.The network device of any of claims 54-66, wherein, The first radio access type is a non-terrestrial network (NTN)-based radio access type.

68. 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: 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 QoS data flow.

69. The terminal device of claim 68, wherein, The step related to called domain selection includes 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.

70. The terminal device of claim 68 or 69, wherein, In a case where the step of twice confirming related to the media negotiation procedure is skipped, the reply message of the first time confirming in the media negotiation procedure comprises a success response message.

71. The terminal device of any one of claims 68-70, wherein, In a case where the step of establishing a voice dedicated bearer is skipped, the voice call shares a bearer with other data.

72. The terminal device of any one of claims 68-71, wherein, The terminal device further comprises: sending 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 establishment process.

73. The terminal device of any one of claims 68-72, 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 of fields related to routing.

74. The terminal device of claim 73, wherein, The header field 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.

75. The terminal device of any one of claims 68-74, wherein, The voice call is implemented through a non-terrestrial network (NTN).

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

77. The network device of claim 76, wherein, The step related to called domain selection comprises one or more of the following: determining a domain in which a called user recently resides; inquiring a domain in which the called user currently resides; sending a message to a specified domain based on a selection of the called user.

78. The network device of claim 76 or 77, wherein, In a case where the step of twice confirming related to the media negotiation procedure is skipped, the reply message of the first time confirming in the media negotiation procedure comprises a success response message.

79. The network device of any of claims 76-78, wherein, In a case where the step of establishing a voice dedicated bearer is skipped, the voice call shares a bearer with other data.

80. The network device of any of claims 76-79, wherein, The network device further comprises: receiving third indication information sent by a 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.

81. The network device of any of claims 76-80, 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 of fields related to routing.

82. The network device of claim 81, wherein, The header field 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.

83. The network device of any of claims 76-82, wherein, The network device comprises one or more of the following: a proxy call session control function (P-CSCF) and a serving call session control function (S-CSCF).

84. The network device of any of claims 76-83, wherein, The voice call is implemented through an NTN.

85. A terminal device, comprising: Comprise a transceiver, a memory and a processor, the memory is used to store a program, the processor is used to call the program in the memory, and control the transceiver to receive or send a signal, so that the terminal device executes the method in any one of claims 1-11, 26-33.

86. A network device, comprising: comprising a transceiver, a memory for storing a program, and a processor for invoking the program in the memory and controlling the transceiver to receive or send signals, so that the network device performs the method of any one of claims 12-25, 34-42.

87. An apparatus comprising: comprising a processor for invoking a program from a memory, so that the apparatus performs the method of any one of claims 1-42.

88. A chip, comprising: comprising a processor for invoking a program from a memory, so that the apparatus performs the method of any one of claims 1-42.

89. A computer-readable storage medium, characterized in that, having a program stored thereon, which causes a computer to perform the method of any one of claims 1-42.

90. A computer program product, characterised in that, comprising a program which causes a computer to perform the method of any one of claims 1-42.

91. A computer program, characterized in that, The computer program causes a computer to perform the method of any one of claims 1-42. The computer program causes a computer to perform the method of any one of claims 1-42.

Images