Wireless communication method, terminal device, and network device
By sending instruction information during the registration process, indicating the encoding information and access capabilities of the terminal device, the problem of the inapplicability of voice encoding methods in satellite communication is solved, and the effects of simplifying signaling interaction and improving communication efficiency are achieved.
Patent Information
- Application Number
- PCT/CN2025/092874
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-06
- Publication Date
- 2026-11-12
AI Technical Summary
In satellite communication networks, the voice coding methods of terminal devices are difficult to apply, resulting in increased signaling transmission delays, instability, or loss, which affects the quality and efficiency of voice communication. Especially in complex and ever-changing network environments, existing technologies are unable to improve the efficiency and accuracy of media negotiation and resource reservation.
By sending instruction information during the registration process, the terminal device's encoding information, access capabilities, and access device type are indicated, enabling advance negotiation of encoding information, simplifying the call setup process, and improving communication efficiency.
It simplifies signaling interaction, improves communication efficiency, enhances voice communication quality and efficiency, and adapts to diverse communication needs and complex network environments.
Smart Images

Figure CN2025092874_12112026_PF_FP_ABST
Abstract
Description
Wireless communication methods, terminal devices, and network devices Technical Field
[0001] This application relates to the field of communication technology, and more specifically, to a wireless communication method, terminal device, and network device. Background Technology
[0002] With the development of communication technology, terminal devices can access communication networks through different networks. For example, terminal devices can access networks via non-terrestrial networks (NTN) or terrestrial networks (TN). In related technologies, terminal devices need to complete a registration process and establish a communication relationship with the network before they can access the network and use related services.
[0003] Taking the IP Multimedia Subsystem (IMS) as an example, when a terminal device accesses the network, it can first execute the IMS registration process. In the IMS registration process, the terminal device sends a registration message to the network to complete user network authorization, authentication, and other operations, ultimately establishing a communication relationship between the terminal and the network so that the terminal device can use IMS voice services. When a terminal device calls other terminal devices through IMS, it can initiate the IMS call setup process. The IMS call setup process may include media negotiation, dedicated QoS stream / bearer establishment, final call domain selection, resource reservation, and ringing.
[0004] However, there is still room for improvement in the above process. For example, in the face of complex and ever-changing network environments, the efficiency and accuracy of media negotiation and resource reservation need to be improved, especially when accessing via NTN. When terminal devices access the network via satellite, due to the inherent technical characteristics and physical environment of satellite communication, the access rate is typically low, making commonly used voice coding methods (such as Enhanced Voice Services Codec (EVS codec) and Adaptive Multi-Rate Codec (AMR codec)) difficult to apply in this scenario. Low satellite access rates can also cause increased signaling transmission delays, instability, or even signal loss when terminal devices register on the network or use related network services, severely impacting voice communication quality and efficiency. These issues urgently need optimization to adapt to diverse communication needs and complex network environments. Summary of the Invention
[0005] This application provides a wireless communication method, a terminal device, and a network device. The various aspects covered by this application are described below.
[0006] In a first aspect, a wireless communication method is provided, the method comprising: a first network device receiving first indication information sent by a first terminal device; wherein the first indication information is sent during a registration process, and the first indication information is used to indicate one or more of the following: encoding information supported by the first terminal device; whether the first terminal device supports the capability to perform a first service through a first wireless access type; the first terminal device performing the first service through the first wireless access type; and the type of wireless access communication device used by the first terminal device to perform the first service.
[0007] In a second aspect, a wireless communication method is provided, the method comprising: a first terminal device sending first indication information to a first network device; wherein the first indication information is sent during a registration process, and the first indication information is used to indicate one or more of the following: encoding information of the first terminal device supporting a first service; whether the first terminal device supports the ability to access the first service through a non-terrestrial communication device; the first terminal device accessing the first service through a non-terrestrial communication device; and the type of non-terrestrial communication device used by the first terminal device to perform the first service.
[0008] Thirdly, a network device is provided, which is a first network device. The network device includes: a first receiving unit, configured to receive first indication information sent by a first terminal device; wherein the first indication information is sent during a registration process, and the first indication information is used to indicate one or more of the following: encoding information supported by the first terminal device; whether the first terminal device supports the capability to perform a first service through a first wireless access type; the first terminal device performing the first service through the first wireless access type; and the type of wireless access communication device used by the first terminal device to perform the first service.
[0009] Fourthly, a terminal device is provided, which is a first terminal device. The terminal device includes: a first sending unit, configured to send first indication information to a first network device; wherein the first indication information is sent during a registration process, and the first indication information is used to indicate one or more of the following: encoding information supporting a first service performed by the first terminal device; whether the first terminal device supports the ability to access the first service through a non-terrestrial communication device; the first terminal device accessing the first service through a non-terrestrial communication device; and the type of non-terrestrial communication device used by the first terminal device to perform the first service.
[0010] Fifthly, a terminal device is provided, including a processor and a memory, the memory being used to store one or more computer programs, the processor being used 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 second aspect.
[0011] In a sixth aspect, a network device is provided, including a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used 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 first aspect.
[0012] Seventhly, embodiments of this application provide a communication system including the aforementioned terminal device and / or network device. In another possible design, the system may further include other devices that interact with the terminal device or network device as described in the embodiments of this application.
[0013] Eighthly, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a terminal device and / or a network device to perform some or all of the steps in the methods described above.
[0014] Ninthly, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a terminal device and / or a network device to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.
[0015] In a tenth aspect, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.
[0016] In this application, during the registration process, the first network device can directly or indirectly obtain information related to the encoding information supported by the first terminal device through the first instruction information. This allows the first terminal device and the first network device to negotiate the encoding information in advance during the registration process, thereby simplifying the signaling interaction in the subsequent execution of the first service and improving communication efficiency. Attached Figure Description
[0017] Figure 1 is a schematic diagram of the wireless communication system used in the embodiments of this application.
[0018] Figure 2 is an example diagram of a registration process.
[0019] Figure 3 is an example diagram of a call setup process.
[0020] Figure 4A is a schematic diagram of a communication link scenario.
[0021] Figure 4B is a schematic diagram of another communication link scenario.
[0022] Figure 4C is a schematic diagram of another communication link scenario.
[0023] Figure 5 is a schematic flowchart of a wireless communication method provided in an embodiment of this application.
[0024] Figure 6 is a schematic flowchart of another wireless communication method provided in an embodiment of this application.
[0025] Figure 7 is a schematic flowchart of another wireless communication method provided in an embodiment of this application.
[0026] Figure 8 is a schematic flowchart of another wireless communication method provided in an embodiment of this application.
[0027] Figure 9A is a schematic flowchart of another wireless communication method provided in an embodiment of this application.
[0028] Figure 9B is a schematic flowchart of another wireless communication method provided in an embodiment of this application.
[0029] Figure 10A is a schematic flowchart of another wireless communication method provided in an embodiment of this application.
[0030] Figure 10B is a schematic flowchart of another wireless communication method provided in an embodiment of this application.
[0031] Figure 11 is a schematic flowchart of another wireless communication method provided in an embodiment of this application.
[0032] Figure 12 is a schematic structural diagram of a network device provided in an embodiment of this application.
[0033] Figure 13 is a schematic structural diagram of a terminal device provided in an embodiment of this application.
[0034] Figure 14 is a schematic structural diagram of a communication device provided in an embodiment of this application. Detailed Implementation
[0035] The technical solutions in this application will now be described with reference to the accompanying drawings.
[0036] Communication system
[0037] Figure 1 illustrates a wireless communication system 100 according to an embodiment of this application. The wireless communication system 100 may include communication devices. These communication devices may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120.
[0038] Figure 1 illustrates an exemplary network device and two terminals. Optionally, the wireless communication system 100 may include multiple network devices, and each network device may include other terminal devices within its coverage area. This application embodiment does not limit this.
[0039] Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment.
[0040] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: 5th generation (5G) systems or new radio (NR), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as 6th generation mobile communication systems, and satellite (SAT) communication systems, etc.
[0041] The terminal device in this application embodiment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as a handheld device with wireless connectivity, in-vehicle equipment, etc. The terminal device in the embodiments of this application can be a mobile phone, tablet computer, laptop computer, PDA, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, 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, providing sidelink signals between UEs in vehicle-to-everything (V2X) or device-to-device (D2D) communication. For example, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices communicate without relaying communication signals through a base station.
[0042] The network device in this application embodiment can be a device for communicating with terminal devices. The network device may also include an access network device. The access network device can provide communication coverage for a specific geographical area and can communicate with the terminal device 120 located within that coverage area. The access network device can also be called a wireless access network device or a base station, etc. In this application embodiment, the access network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. Access network equipment can broadly encompass various names listed below, or be interchangeable with them, such as: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, 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. Base stations can be macro base stations, micro base stations, relay nodes, donor nodes, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the access network equipment.
[0043] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.
[0044] Wireless communication systems involve communication equipment that can include not only access network equipment and terminal equipment, but also core network elements. Core network elements can be implemented through devices; that is, core network elements are core network devices. It can be understood that core network devices can also be a type of network device.
[0045] The core network elements in this embodiment may include network elements that process and forward user signaling and data. For example, core network equipment may include core access and mobility management functions (AMF), session management functions (SMF), user plane gateways, location management functions (LMF), and other core network equipment. The user plane gateway may be a server with functions such as mobility management, routing, and forwarding of user plane data, generally located on the network side, such as a serving gateway (SGW), packet data network gateway (PGW), or user plane function (UPF). Of course, the core network may also include other network elements, which are not listed here.
[0046] In some deployments, the network device in this application embodiment may refer to a CU or a DU, or the network device may include both a CU and a DU. The gNB may also include an AAU.
[0047] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.
[0048] It should be understood that all or part of the functions of the communication device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).
[0049] IMS Registration Process
[0050] The registration process is a crucial step in establishing a communication relationship between a terminal device and the network. The IMS registration process allows the terminal device to use the services provided by IMS.
[0051] The IMS registration process is explained below with reference to Figure 2.
[0052] As shown in Figure 2, the IMS registration process may include steps S101 to S126.
[0053] Step S101: The caller UE sends an initial registration request. The initial registration request can be a register message. This registration message can carry indications of public user identity (PUI), private user identity (PVI), return domain name, instance ID, and globally routable user agent URI (GRUU).
[0054] In steps S102-S103, the proxy-call session control function (P-CSCF) looks up the domain name system (DNS) based on the home domain to obtain the address of the interrogating call session control function (I-CSCF). Steps S102-S103 are implemented based on DNS query messages and DNS query response messages, respectively.
[0055] In step S104, the P-CSCF sends a registration message to the I-CSCF. This registration message carries the P-CSCF address / name, PUI, PVI, P-CSCF identifier, and UE IP address.
[0056] Steps S105 and S106 are the service-call session control function (S-CSCF) allocation process.
[0057] In step S105, the I-CSCF sends a Diameter message: User Authorization Request (UAR) to the Home Subscriber Server (HSS). This Diameter message carries the PUI, PVI, and P-CSCF identifier. Based on this Diameter message, the HSS checks whether the UE is allowed to register with the P-CSCF.
[0058] In step S106, the HSS returns a Diameter message: User Authorization Answer (UAA). This Diameter message includes S-CSCF information (such as name or capability set).
[0059] Step S107: I-CSCF obtains S-CSCF based on HSS interaction, i.e., S-CSCF allocation process.
[0060] Steps S108 and S109 are the process of downloading the authentication vector set.
[0061] In step S108, the S-CSCF sends a Diameter message to the HSS: Multimedia Auth Request (MAR). This Diameter message includes the PUI, PVI, and S-CSCF name.
[0062] In step S109, the HSS replies with a Diameter message: Multimedia Auth Answer (MAA). This Diameter message includes authentication data (authentication method (Digest), authentication vector (username and password)).
[0063] Steps S110-S119 are the authentication process. In steps S110-S112, the authentication parameters are returned to the UE. Steps S113 and S116 are the authentication response. Steps S117 and S118 are the S-CSCF allocation process.
[0064] Steps S120-S121: Download user contract information. Contract information can also be called a contract profile. The contract profile may include initial filter criteria (iFC) information, etc.
[0065] Steps S122-S124: After successful signing, the HSS can send a 200 OK message to the I-CSCF / P-CSCF / Caller UE.
[0066] In steps S125-S126, after successful registration, S-CSCF checks iFC and notifies the application server (AS) serving the user that the user has registered and is reachable.
[0067] IMS Call Setup Process
[0068] In communication systems, voice calls between terminal devices can be achieved through the IMS call setup process, which is called IMS-based voice (VoIMS).
[0069] The key steps in the IMS call setup process are explained below with reference to Figure 3.
[0070] The IMS call setup process mainly includes the following key steps: media negotiation process, dedicated QoS stream / bearer setup process, terminating-access domain selection (T-ADS) process, resource reservation process, and ringing process. These are explained in detail below.
[0071] The media negotiation process can include steps S201-S212 and S301-S312 in Figure 3. The media negotiation process mainly uses the Session Description Protocol (SDP) to carry the media types and encoding schemes supported by the calling (mobile originated, MO) UE and negotiates with the called (mobile terminated, MT) UE (through two SDP request-response pairs).
[0072] The dedicated QoS flow / bearer establishment process may include steps S207 and S306 in Figure 3. The dedicated QoS flow / bearer establishment process is the dedicated bearer / data flow establishment process triggered by the S-CSCF for the UE, and triggers the core network session modification procedure after the first SDP request response.
[0073] The T-ADS process may include step S302 in Figure 3. The T-ADS process can determine which domain the called UE is currently camped in (e.g., 2 / 3G core network (CN), evolved packet system (EPS), or 5G system (5GS)), and trigger the AS to query the HSS through the S-CSCF to determine the domain in which the called UE is currently camped (e.g., evolved packet core (EPC) or circuit switched (CS)). Then, the S-CSCF selects to send a message to the designated domain according to the domain of the called UE.
[0074] The resource reservation process may include steps S210 and S313 as shown in Figure 3. To ensure the successful establishment of the negotiated media plane, resources need to be reserved on both the calling and called sides. Resource reservation typically occurs after the media negotiation process is completed (after two SDP request-response procedures).
[0075] The ringing process may include steps S323-S325 and S222-S224. The ringing process may occur after resource reservation is successful.
[0076] Non-terrestrial networks (NTN)
[0077] NTN can provide communication services to users via non-terrestrial methods. That is, it can communicate with terminal devices through non-terrestrial network equipment such as satellites (SAT) and unmanned aerial vehicle (UAS) platforms. Based on their altitude, orbit, and beam footprint characteristics, satellites can belong to several types, including low Earth orbit (LEO), medium Earth orbit (MEO), and geostationary Earth orbit (GEO).
[0078] For terrestrial network communication, it's impossible to deploy communication equipment in scenarios like oceans, mountains, and deserts. Alternatively, considering the costs of setting up and operating communication equipment, terrestrial communication typically doesn't cover sparsely populated areas. Compared to terrestrial network communication, NTN (Network Telecommunication) has many advantages. First, NTN communication networks are not limited by geographical location. Theoretically, satellites can orbit the Earth, so every corner of the globe can be covered by satellite communication. Furthermore, the area covered by non-terrestrial network equipment is far greater than that covered by terrestrial communication equipment. In other words, NTN cells can cover a much wider area.
[0079] Communication links based on NTN networks
[0080] When terrestrial network coverage is poor and there is a need for satellite communication (such as in remote areas, marine areas, or airspace), terminal devices can access the NTN network for communication. The following explanation, using Figures 4A to 4C, illustrates different communication link scenarios of the NTN network.
[0081] Scenario 1: The MO UE is in the NTN network coverage area, and the MT UE is in the terrestrial network coverage area.
[0082] As shown in Figure 4A, during communication, MO UEs can access the network via satellite, while MT UEs can access the communication link with the core network via a terrestrial base station. Specifically, MO UEs can communicate with the terrestrial gateway (station) via satellite and then access the IMS. MT UEs access the network via a terrestrial base station and then establish a connection with the IMS, thereby receiving call requests from MO UEs.
[0083] Scenario 2: Both MO UE and MT UE are located within the NTN network coverage area.
[0084] As shown in Figure 4B, during the communication process, MO UE and MT UE can respectively access the communication link with the core network via satellite.
[0085] Access can be via satellite, while MT UEs can access the core network through a terrestrial base station. Specifically, MO UEs can communicate with a terrestrial gateway (station) via satellite and then access the IMS. MT UEs access the network through satellite communication with a terrestrial gateway (station) and then establish a connection with the IMS, thereby enabling them to receive call requests from MO UEs.
[0086] Scenario 3: The MO UE is in the terrestrial network coverage area, and the MT UE is in the NTN network coverage area.
[0087] As shown in Figure 4C, during communication, MO UEs can access the network via terrestrial base stations, while MT UEs can access the core network via satellite. Specifically, MO UEs can establish a connection with IMS via terrestrial base stations, while MT UEs can communicate with terrestrial gateways (stations) via satellite and then access IMS, thereby receiving call requests from MO UEs.
[0088] Voice coding
[0089] IMS supports various speech coding methods, each with different coding rates and sound quality, which may directly affect the quality of voice communication in the IMS network. In the relevant voice communication field, EVS codec and AMR codec are currently commonly used speech coding methods, which will be explained below.
[0090] The EVS codec offers a flexible encoding rate range. For example, the EVS codec's rate range can cover from 5.9 kilobits per second (kbps) to 128.0 kbps, specifically including: 5.9, 7.2, 8.0, 9.6, 13.2, 16.4, 24.4, 32.0, 48.0, 64.0, 96.0, and 128.0 (kbps). This broad rate range allows for dynamic adaptation of encoding strategies based on different network conditions and service requirements. For instance, when network conditions are good and bandwidth is ample, a higher encoding rate such as 96.0 kbps or 128.0 kbps can be used to achieve near-original high-definition voice quality; when network conditions are poor and bandwidth is limited, a lower encoding rate such as 5.9 kbps or 7.2 kbps can be used to ensure basic voice communication functions and call continuity.
[0091] AMR codecs can be divided into two types: narrowband speech coding and wideband speech coding.
[0092] The narrowband voice coding rates of AMR codecs can include: 12.2, 10.2, 7.95, 7.4, 6.7, 5.9, 5.5, and 4.75 (kbps). It is understandable that when the bandwidth of the current network environment is limited, using AMR codecs can maintain basic voice communication services with limited bandwidth resources.
[0093] The AMR codec's wideband voice coding format can be divided into several configurations, each corresponding to a different coding rate. Specific wideband voice coding formats are: configuration 0 / 1: 12.65, 8.85, 6.6 (kbps); configuration 2 / 3: 15.85, 8.85, 6.6 (kbps); configuration 4 / 5: 23.85, 12.65, 8.85, 6.6 (kbps). The AMR codec can adopt different configuration formats in different application scenarios and network conditions. For example, when high voice quality is required and bandwidth allows, the 23.85 kbps rate in configuration 4 / 5 can be selected to achieve high-quality bandwidth voice communication.
[0094] However, when terrestrial network coverage is poor, and the communication equipment is located in an NTN network coverage area, the equipment can access the communication network through non-terrestrial network devices to ensure voice communication functionality. These non-terrestrial network devices can be satellites. For example, in the specific communication scenario where the terminal device accesses via satellite, due to the inherent technical characteristics and physical environment of satellite communication, the access rate is typically extremely low, often only 1-3 kbps, or even lower. The minimum coding rates covered by the aforementioned EVS codec and AMR codec are far higher than the rate range supported by satellite access. This makes it difficult to directly apply the commonly used EVS codec and AMR codec in related voice technologies in satellite access scenarios.
[0095] The related technology also proposes an encoding method called Codec-2, which can be considered a low-bit-rate speech audio codec (speech coding) that is patent-free and open-source. Codec-2 uses sinusoidal coding to compress speech, which can be considered a coding method specifically designed for human speech. It can process speech signals according to the characteristics and rules of human language. Codec-2 can include different encoding modes at various rates, specifically 3.2, 2.4, 1.6, 1.4, 1.3, 1.2, 0.7, and 0.45 (kbps).
[0096] However, in some situations, such as when terminal devices need to access communication networks via satellite, the data transmission rate achievable through satellite access is limited. During terminal device communication, the low satellite access rate restricts the transmission of a large amount of signaling data, potentially leading to increased signaling transmission delays, unstable transmission, or even data loss, severely impacting voice communication quality and efficiency. Furthermore, due to the low satellite access rate, terminal devices cannot properly use encoding methods with higher encoding rates, such as the aforementioned EVS codec and AMR codec. This forces the terminal device to choose lower encoding methods, limiting its encoding capabilities and affecting voice quality and communication efficiency. These issues urgently require optimization to adapt to diverse communication needs and complex network environments.
[0097] To address the aforementioned problems, this application proposes a wireless communication method. Figure 5 is a schematic flowchart of a wireless communication method provided in an embodiment of this application. The method shown in Figure 5 can be executed by a first terminal device and a first network device. For example, the first network device may include one or more of the following: P-CSCF, S-CSCF, and AF.
[0098] The method shown in Figure 5 may include step S510.
[0099] In step S510, the first network device can receive the first instruction information.
[0100] The first indication information can be sent by the first terminal device. In other words, the sender of the first indication information can be the first terminal device. The first terminal device can directly send the first indication information to the first network device. For example, the first network device includes a P-CSCF. The first terminal device can directly send the first indication information to the P-CSCF. Alternatively, the first network device may include an AF, and the first indication information received by the AF can be forwarded through other network elements.
[0101] As one possible implementation, the first indication information may be used to indicate one or more of the following: the encoding information supported by the first terminal device; whether the first terminal device supports the capability to perform the first service through the first wireless access type; the first terminal device performing the first service through the first wireless access type; the type of wireless access communication equipment used by the first terminal device to perform the first service; and whether the first terminal device supports processing a simplified call setup procedure. These will be explained separately below.
[0102] The first indication information can be used to indicate the encoding information supported by the first terminal device.
[0103] The encoding information can be encoding information that supports the first service. For example, when the service type of the first service is a voice service, the first indication information can be used to indicate the voice encoding information supported by the first terminal device. When the service type of the first service is a video service, the first indication information can be used to indicate the video encoding information supported by the first terminal device.
[0104] A simplified call setup process refers to a process where some steps of the call setup procedure can be omitted on the terminal device side. Figure 3 shows a call setup process without simplification. Taking the MO UE shown in Figure 3 as an example, in the simplified call setup process, the MO UE side can omit one or more of steps S208, S209, S210, S215, S216, and S221.
[0105] In some embodiments, if the terminal device supports a simplified call setup process, the terminal device can process SIP messages (such as INVITE messages) without pre-condition settings. Pre-conditioning includes, for example, requesting pre-conditioning in the SIP header (“require: precondition”), and / or including “a=current:”, “a=des:”, or “a=conf:” in the SDP offer.
[0106] It should be noted that the first network device can act as a back-to-back user agent (B2BUA). For example, AF can act as a B2BUA. Alternatively, P-CSCF can act as a B2BUA.
[0107] In some embodiments, when the first terminal device accesses the network via a first wireless access type, the first terminal device may carry encoded information in the first indication information. For example, when the terminal device accesses the core network and / or IMS via GEO, the first indication information may carry encoded information (such as Codec2) corresponding to the first service (such as voice service).
[0108] The first indication information can be used to indicate whether the first terminal device supports the ability to perform a first service through a first wireless access type. For example, the first indication information can be used to indicate whether the first terminal device supports the ability to access and perform services through a first wireless access type.
[0109] It should be noted that in this application, "access" may include access to the core network and / or IMS.
[0110] The first wireless access type can be understood as the type of wireless network accessed by the first terminal device. For example, the first wireless access type may include an NTN-based wireless access type and / or a terrestrial network-based wireless access type.
[0111] In this application, the first service may include one or more of the following: voice call, emergency service, video call, and messaging service.
[0112] Taking voice service as an example, the first indication information can be used to indicate whether the first terminal device supports the ability to conduct voice service through NTN; and / or, the first indication information can be used to indicate whether the first terminal device supports the ability to conduct voice service through terrestrial network access type.
[0113] It is important to understand that when the first indication information indicates that the first terminal device has the capability to support the first service through the first wireless access type, the first terminal device does not necessarily mean that it is actually performing the first service through the first wireless access type. For example, when the first indication information indicates that the first terminal device supports the capability to perform voice services through the NTN access type, it means that the first terminal device can support voice calls through the NTN access type, but it does not mean that the first terminal device can only perform voice calls through the NTN access type. The first terminal device could also perform voice calls through a terrestrial network.
[0114] The first instruction information can be used to instruct the first terminal device to perform a first service through a first wireless access type. For example, the first instruction information can be used to instruct the first terminal device to access and perform the first service through a first wireless access type.
[0115] For example, when the first service is a voice service, the first indication information can be used to instruct the first terminal device to access the network through the NTN access type when performing a voice service.
[0116] It should be understood that when the first indication information is used to instruct the first terminal device to perform the first service through the first radio access type, then it is assumed that the first terminal device has the capability to support performing the first service through the first radio access type, and / or, the content of the encoding information supported by the first terminal device for performing the first service is the default content (e.g., a predefined or pre-configured encoding type, such as Codec-2), and / or, the first terminal device supports processing a simplified call setup procedure. For example, when the first indication information instructs the first terminal device to access the NTN access type for voice service, it is assumed that the first terminal device has the capability to support performing voice service through NTN access, and it is assumed that the encoding type supported by the first terminal device for voice service includes Codec-2.
[0117] The first indication information can be used to indicate the type of wireless access communication equipment used by the first terminal device to perform the first service. The type of wireless access communication equipment may include, for example, a satellite type. For instance, the type of wireless access communication equipment may include one or more of the following: LEO, MEO, GEO. Taking voice service as an example, the first indication information can be used to indicate that the first terminal device accesses and performs voice service via LEO, MEO, or GEO. When the first indication information indicates that the first terminal device performs the first service via a first type (e.g., GEO) wireless access communication equipment, it can be assumed that the first terminal device supports a simplified call setup procedure, and / or that the first terminal device supports a specific encoding type (e.g., Codec-2).
[0118] It should be noted that the first terminal device supporting Codec-2 for the first service (e.g., voice) via a first type (e.g., GEO) wireless access communication device is merely one example proposed in this application. This application does not limit the encoding information (encoding type, rate, protocol type, etc.) supported by the first terminal device for the first service via the first type of wireless access communication device. For example, the encoding type of the first terminal device for the first service via the first type of wireless access communication device may include other types besides Codec-2.
[0119] In some embodiments, the first indication information may be sent during the registration process. For example, the first indication information may be carried in the information sent by the first terminal device to the first network device during the IMS registration process. That is, the first terminal device may carry the first indication information in the message during the IMS registration process. For example, the first indication information may be carried in the registration information sent in step S101 of the IMS registration process. Alternatively, the first indication information may be carried in the authentication process message of steps S110-S119 of the IMS registration process. It is understood that when the first indication information is sent during the registration process, the first network device obtains relevant information about the first terminal device in advance compared to the call process, such as the encoding information of the first terminal device, or whether the first terminal device supports the capability of performing the first service through the first wireless access type, or whether the first terminal device performs the first service through the first wireless access type, or the type of wireless access communication device used by the first terminal device when performing the first service. The method shown in Figure 5 can be referred to as an enhancement or capability pre-negotiation for the registration process.
[0120] In this application, during the registration process, the first network device can directly or indirectly obtain information related to the encoding information supported by the first terminal device through the first instruction information. This allows the first terminal device and the first network device to negotiate the encoding information in advance during the registration process, thereby simplifying the signaling interaction in the subsequent execution of the first service and improving communication efficiency.
[0121] It should be noted that this application does not limit the name of the first instruction information. For example, since the first instruction information directly or indirectly indicates the capabilities of the first terminal device, the first instruction information can also be called capability information, pre-negotiation coding information, pre-negotiation capability information, or coding information corresponding to capability negotiation.
[0122] It should be noted that the first terminal device can be understood as any terminal device accessing the network. For example, the first terminal device can be the calling terminal device performing the first service, or it can be the called terminal device performing the first service. This application embodiment does not impose any restrictions here.
[0123] In some embodiments, encoding information may include one or more of the following: encoding type, bit rate, frame format, transport protocol, and service type. These concepts are explained below.
[0124] Encoding type can be understood as the encoding rules and methods supported by the first terminal device. For example, encoding type can include the EVS codec, AMR codec, or Codec-2 mentioned above. Optionally, encoding type can also include a combination of multiple encodings. For example, when encoding type includes EVS codec and AMR codec, it can be considered that the first terminal device can use either EVS codec or AMR codec for voice encoding.
[0125] Bitrate refers to the amount of data transmitted per unit of time. For example, when the Codec-2 bitrate mentioned above is 0.7 kbps, it means that it can transmit 0.7 kilobits of data per second. Optionally, bitrate can include a single rate. For example, when the encoding type is Codec-2 and the bitrate is 0.7 kbps, it can be assumed that the first terminal device can encode voice data using Codec-2 at a rate of 0.7 kilobits per second. Optionally, bitrate can include multiple rates. For example, when the encoding type is EVS codec, the bitrate can be 5.9 kbps or 32.0 kbps. The first terminal device can encode voice data using EVS codec at a rate of 5.9 kilobits per second, or it can encode data at a rate of 32 kilobits per second.
[0126] A frame format can be considered the data packet format used to transmit data during communication. For example, when transmitting voice data, the Real-Time Transport Protocol (RTP) packet format can be used. Optionally, a frame format may include one or more formats.
[0127] A transport protocol can be considered a set of rules and conventions that must be followed to achieve data transmission. For example, a transport protocol can specify the data format, transmission method, flow control, and other related aspects. For instance, a transport protocol can be based on the Real-Time Protocol (RTP) and Audio-Video Profile (AVP). In other words, RTP and AVP can be used to standardize the data transmission format and related parameters, and the characteristics of UDP can be utilized to achieve data transmission over the network. Optionally, a transport protocol may include one or more protocols.
[0128] Service type can be understood as the service supported by the first terminal device, such as the first service mentioned above. For example, when the first service is a voice service, the service type can be voice. Service types can include one or more. For example, the first service can include only voice services. Or, for example, the first service can include both voice and video services.
[0129] When the encoding information includes encoding type, bit rate, frame format, transmission protocol, and service type, the first network device can more accurately determine the configuration information of the first terminal device and select appropriate encoding information for the first terminal device more accurately based on the network conditions.
[0130] As mentioned above, the first indication information can be carried in the information sent by the first network device to the first terminal device during the IMS registration process. In this case, the first indication information can be carried in the SIP registration message of the first terminal device. A detailed example follows.
[0131] As one possible implementation, the first indication information can be carried in one or more fields of the SIP registration message header. The SIP registration message header typically includes multiple fields, each indicating different information to complete the registration process for the first terminal device. For example, the SIP registration message header may include a contact field, which can specify the first terminal device's current IP address, port number, and other information. The SIP registration message header may also include a user-agent (UA) field, which can be used to represent the name and version of the first terminal device. The first indication information can be carried in one or more fields of the SIP registration message header; for example, the first indication information can be carried in the contact field of the SIP registration message, or it can be carried in the UA field of the SIP registration message.
[0132] As one possible implementation, the first indication information can be carried within an SDP offer in the SIP registration message. This can also be understood as the SIP registration message including an SDP offer, with the first indication information carried within it. SDP is a protocol used to describe session formats and attributes. By including an SDP offer in the SIP registration message, the network device can obtain detailed information about the first terminal device's session during the registration process. The SDP offer, with the first indication information carried within the SIP registration message, facilitates the transmission of encoded information and capability negotiation during the registration phase of the first terminal device, thus optimizing the subsequent first service establishment process for the first terminal device.
[0133] The first indication information is carried in the SIP registration message, which can reuse the current system signaling. There is no need to create new signaling separately to transmit the first indication information, thereby saving system resources and improving system performance.
[0134] In some embodiments, the type of non-terrestrial communication device used by the first terminal device to perform the first service can correspond to the encoding information that the first terminal device supports for performing the first service. For example, when the first network device confirms the type of non-terrestrial communication device used by the first terminal device to perform the first service through the first indication information, it can assume that the first terminal device already possesses the encoding information to support access to the first service through that type of non-terrestrial communication device. For example, when the first network device confirms that the satellite communication type of the first terminal device is GEO based on the received first indication information, it can assume that the first terminal device supports one or more encoding information corresponding to GEO voice, such as Codec-2, with a rate of 0.7kbps. That is, when the first indication information is used to indicate that the type of non-terrestrial communication device used by the first terminal device to perform voice service is GEO, the first network device can assume that the first terminal device can use Codec-2 for voice service.
[0135] As one possible implementation, when the first terminal device accesses the first service via a non-terrestrial communication device, the first terminal device uses specific encoding information. For example, the specific encoding information may include Codec-2. For instance, when the first terminal device accesses the voice service via GEO, the first network device may default to supporting Codec-2 as the encoding type supported by the first terminal device at this time.
[0136] This design allows the first network device to determine the encoding information supported by the first terminal device when it obtains the type of non-terrestrial communication equipment used by the first terminal device to perform the first service, and / or when the first terminal device accesses the first service through a non-terrestrial communication equipment. This eliminates the need for the first terminal device to send its specific encoding information to the first network device, thereby saving signaling overhead and improving communication efficiency.
[0137] In some embodiments, the first network device may send feedback information. The first terminal device may receive the feedback information.
[0138] As one possible implementation, the feedback information can be used to indicate one or more of the following: coding information that allows the first terminal device to use for the first service; whether the first terminal device is allowed to access the first service via a non-terrestrial communication device; and the type of service that the first terminal device is allowed to perform. In other words, the feedback information can be considered as the coding information that the first network device can use when performing the first service, and / or, determining whether the first terminal device is allowed to access the first service via a non-terrestrial communication device, and / or, the type of service that the first terminal device is allowed to perform.
[0139] In some embodiments, the coded information in the feedback information indicating permission for the first terminal device to use the first service can be understood as the coded information determined after the first terminal device and the first network device negotiate capabilities during the registration process. In other words, this coded information is the same as the coded information corresponding to the capability negotiation.
[0140] For example, if the first terminal device supports EVS codec and Codec-2 voice encoding types, but the feedback information only indicates that the first terminal device is allowed to use Codec-2 when conducting voice services, then the first terminal device can only use Codec-2 encoding when conducting voice services.
[0141] Based on feedback information and the type of the first service, the first terminal device can optimize its own coding selection and determine the network access strategy to effectively improve service adaptability and communication success rate.
[0142] In some embodiments, the feedback information may be determined based on the first indication information.
[0143] When the feedback information can be used to indicate the encoding information that the first terminal device is allowed to use for the first service, the first network device can obtain the encoding information supported by the first terminal device based on the first indication information. The first network device can then determine whether the first terminal device can use the encoding information when performing the first service. For example, in an NTN network environment, if the encoding type supported by the first terminal device obtained by the first network device does not include Codec-2, the first network device believes that the first terminal device cannot normally transmit voice data in the NTN network environment. That is, the feedback information can indicate that the first terminal device is not allowed to use the EVS codec when performing voice services. As another example, if the first network device obtains the encoding type supported by the first terminal device as Codec-2, then the first network device believes that the first terminal device can normally transmit voice data in the NTN network environment. Therefore, the feedback information can indicate that the first terminal device is allowed to use Codec-2 when performing voice services.
[0144] When feedback information indicates whether the first terminal device is allowed to access the first service via a non-terrestrial communication device, the first network device obtains the encoding information supported by the first terminal device based on the first indication information. The first network device can then determine whether to allow the first terminal device to access the first service via a non-terrestrial communication device based on this encoding information. For example, in an NTN network environment, if the encoding type supported by the first terminal device does not include Codec-2, the first network device will not allow the first terminal device to access the voice service via a non-terrestrial communication device. Conversely, if the encoding type supported by the first terminal device includes Codec-2, in an NTN network environment, the first network device will allow the first terminal device to access the voice service via a non-terrestrial communication device.
[0145] When the feedback information indicates the type of service allowed for the first terminal device, the first network device obtains the encoding information supported by the first terminal device based on the first indication information. This includes encodings that support both voice and video services. However, when the network environment does not support video services, the feedback information may indicate that only voice services are allowed for the first terminal device. In other words, in the current network environment, the first network device only allows the first terminal device to perform voice services, and does not allow it to perform video services.
[0146] In some embodiments, the feedback information may be determined based on the subscription information of the first terminal device.
[0147] The subscription information of the first terminal device can be obtained by the first network device from other network devices. These other network devices can be different from the first network device; for example, they may include an HSS and / or a UDM. The first network device can include the unique identifier of the first terminal device (e.g., UE ID) in the subscription request information and send it out. Other devices can use this unique identifier to locate and obtain the subscription data of the terminal device corresponding to that identifier. The subscription information can be data that the first terminal device has already stored in other network devices before registration. For example, when the first terminal device applies for network access, it may activate relevant services. This activation information can be entered into the system, converted into subscription information, and stored in network devices such as HSS / UDM. If the first terminal device subscribes to video services when applying for network access, the subscription information may include permission for the first terminal device to conduct video services.
[0148] When feedback information indicates the encoding information that allows the first terminal device to perform the first service, the first network device can determine the encoding information supported by the first terminal device based on the acquired subscription information. The first network device can then determine whether the first terminal device can use this encoding information when performing the first service. For example, if the subscription information includes that the first terminal device can access the network via non-terrestrial devices, such as satellite, then the first network device believes that the first terminal device can use encoding information that supports non-terrestrial device network access, such as Codec-2, when performing voice services.
[0149] When feedback information is used to indicate whether a first terminal device is allowed to access the first service via a non-terrestrial communication device, the first network device can determine whether to allow the first terminal device to access the first service via a non-terrestrial communication device based on the subscription information. For example, if the first service is a voice service, and the subscription information includes that the first terminal device has subscribed to a voice service via a non-terrestrial communication device, such as satellite, then the first network device, based on the subscription information, allows the first terminal device to access the voice service via a non-terrestrial communication device.
[0150] In some embodiments, the feedback information can be determined based on the first instruction information of the first terminal device and the subscription information of the first terminal device. That is, the first network device can jointly determine the content of the feedback information based on the content of the first instruction information and the subscription information of the first terminal device.
[0151] For example, the first network device may determine one or more of the following based on the first instruction information and the subscription information: the encoding information that allows the first terminal device to use the first service; whether the first terminal device is allowed to access the first service through a non-terrestrial communication device; and the type of service that the first terminal device is allowed to perform.
[0152] For example, the first indication information indicates that the encoding types supported by the first terminal device include EVS codec and Codec-2. If the subscription information of the first terminal device indicates that the first terminal device does not include voice services accessed through non-terrestrial communication devices, the first network device can determine that the first terminal device can only use EVS codec when performing voice services; that is, the feedback information indicates that the first terminal device can only use EVS codec when performing voice services. If the subscription information of the first terminal device indicates that the first terminal device can access voice services through non-terrestrial communication devices, then the first network device can determine that the first terminal device can use Codec-2 when performing voice services; that is, the feedback information indicates that the first terminal device can use Codec-2 when performing voice services.
[0153] For example, if the first indication information indicates that the encoding type supported by the first terminal device is EVS codec, and the subscription information of the first terminal device indicates that the first terminal device includes voice services accessed through non-terrestrial communication devices, since the rate of EVS codec is too high and it is not suitable for accessing the network through non-terrestrial communication devices, the first network device can determine that the first terminal device is not allowed to access the voice service through non-terrestrial communication devices, that is, the feedback information indicates that the first terminal device is not allowed to access the voice service through non-terrestrial communication devices.
[0154] For example, the first indication information may indicate that the encoding information supported by the first terminal device includes voice encoding information and video encoding information, and the subscription information of the first terminal device indicates that the first terminal device only supports voice services. Therefore, the first network device can determine that the service that the first terminal device is allowed to perform is a voice service, that is, the feedback information indicates that the service that the first terminal device is allowed to perform is a voice service.
[0155] In some embodiments, based on one or more of the first indication information, subscription information, and feedback information, the first network device can determine whether it is necessary to configure transcoding functionality for the first terminal device during the execution of the first service. For example, if the first indication information indicates that the first terminal device supports the encoding type Codec-2, and the subscription information indicates that the first terminal device cannot support accessing voice services through non-terrestrial devices, but only supports accessing voice services through terrestrial devices, then the first network device can configure transcoding functionality for the first terminal device during the execution of the first service, such as transcoding between Codec-2 and other encoding types, which may include, for example, EVS codec.
[0156] As one implementation, if the first network device includes a P-CSCF, the P-CSCF can be configured with transcoding functionality. If the first network device includes an AF, the AF can be configured with transcoding functionality. Exemplarily, the P-CSCF can act as a B2BUA and be configured with transcoding functionality. Exemplarily, the AF can act as a B2BUA and be configured with transcoding functionality. Exemplarily, one of the P-CSCF and the AF can act as a B2BUA, and the other can be configured with transcoding functionality.
[0157] In some embodiments, based on one or more of the first instruction information, subscription information, and feedback information, the first network device may modify the encoding type list (also known as the Codec list) during the establishment of the first service, etc., during the execution of the first service. The encoding type list can be a candidate list of encoding types used for the first service. The encoding type list may include one or more encoding types. The encoding type list may be carried in the SDP offer.
[0158] For example, if the first instruction information indicates that the first terminal device supports the encoding type Codec-2, and the subscription information indicates that the first terminal device cannot support accessing voice services through non-terrestrial devices, but only supports accessing voice services through terrestrial devices, then the first network device can modify the encoding type list during the first service establishment process. For instance, the original encoding type list of the first terminal device might only include Codec-2, but the modified encoding type list could also include commonly used encoding information for voice services, such as EVS codec or AMR codec. How to modify the encoding type list will be explained in detail later.
[0159] The first network device determines, based on one or more of the first instruction information, subscription information, and feedback information, whether it is necessary to configure transcoding function for the first terminal device and / or modify the encoding type list in the first service establishment process. This can avoid communication failure caused by different encoding information supported by MO UE and MT UE during the first service establishment process, and can improve communication compatibility and stability.
[0160] The embodiments of this application will be described below with reference to Figure 6.
[0161] Figure 6 is a schematic flowchart of a wireless communication method provided in an embodiment of this application. In Figure 6, the first network device may include a P-CSCF and / or an S-CSCF; the first terminal device may include an MO UE.
[0162] The method shown in Figure 6 may include steps S610 to S660.
[0163] In step S610, the MO UE can send a SIP registration message to the P-CSCF. It should be understood that step S610 can occur when the MO UE is registered with IMS and is in the NTN coverage area, or when the MO UE moves into the NTN coverage area.
[0164] SIP registration messages may include MO UE encoding information and / or first information. These will be explained below.
[0165] The encoding information of an MO UE may include one or more of the following: encoding type, bitrate, frame format, transport protocol, and service type. Each item may have one or more values. For example, the encoding information may include the following: encoding type is Codec-2, bitrate is 0.7kbps and / or 0.45kbps, frame format is RTP packet format, transport protocol is RTP / AVP over UDP, and service type is audio.
[0166] The first information is used to indicate the MO UE's ability to perform voice operations via SAT access and / or to provide voice services via SAT access. The first information may further include capability information indicating which type of SAT (such as LEO, MEO, or GEO) is being used for access.
[0167] The aforementioned encoded information and / or first information can be carried in the following ways: for example, through one or more fields in the SIP registration message, such as placing the encoded information and / or first information in the Contact field or UA field. Another example is including an SDP Offer in the SIP registration message, where the SDP Offer carries the aforementioned encoded information.
[0168] Different access methods can be assigned different encoding information by default. For example, when the MO UE reports the first information, it can be assumed by default that the MO UE supports one or more encoding information corresponding to Geo voice (such as Codec-2 / 0.7kbps). This correspondence can be configured by default on the network and terminal sides. Based on this, the signaling overhead of transmitting specific encoding parameters can be eliminated.
[0169] In step S620, the P-CSCF or S-CSCF can interact with the HSS / UDM. The subscription request message sent by the P / S-CSCF to the HSS / UDM contains the MO UE's identification information, through which the MO UE's subscription information can be obtained. The subscription information may include one or more of the following: whether satellite voice is allowed; whether GEO, MEO, or LEO voice is allowed; whether "capability negotiation" coding pre-negotiation is allowed; and the coding information corresponding to the MO UE (which may be consistent with the coding information defined in step S610).
[0170] Optionally, Figure 6 may include steps S630 and S640.
[0171] In steps S630 and S640, according to the configuration, the P-CSCF / S-CSCF can send an authentication request to the MO UE, and the MO UE replies with a SIP registration message carrying relevant authentication information.
[0172] In step S650, P-CSCF / S-CSCF can determine the encoding information of MO UE.
[0173] If the MO UE's encoding information is not carried in step S610, the P-CSCF or S-CSCF can use the encoding information in the MO UE's subscription information and send it to the MO UE in the reply message in step S660.
[0174] If step S610 carries the encoding information of the MO UE, then the P-CSCF or S-CSCF determines the encoding information that the MO UE can use (i.e., the allowed encoding information) based on the encoding information in the subscription information. For example, it takes the minimum set between the subscription information and the requested encoding information, or if the two conflict, it takes the parameter in the subscription information as the higher priority, that is, it determines the encoding information that the MO UE can use based on the subscription information.
[0175] It should be noted that the location and time of the MO UE can also be considered when determining the allowed encoding information, but this application embodiment does not limit this.
[0176] It should also be noted that step S640 can also be completed by P-CSCF.
[0177] In step S660, the P-CSCF can reply with a 200 OK message to the MO UE. This 200 OK message may include one or more of the following: whether the MO UE is allowed to perform satellite voice, or further specify GEO, MEO, or LEO voice; the allowed encoding information for the MO UE; and the services allowed for the MO UE (such as voice, video, SMS, etc.).
[0178] The method shown in Figure 6 may also include other steps in the IMS registration process shown in Figure 2, which will not be described in detail here.
[0179] It should be noted that the method shown in Figure 6 can occur when the first terminal device initiates the IMS registration process for the first time, and the first terminal device is within the coverage area of the NTN network. Alternatively, the method shown in Figure 6 can occur when the first terminal device moves from a non-NTN network to an NTN network coverage area and initiates the IMS registration process.
[0180] In some embodiments, after the first terminal device completes the registration process with the first network device, the first terminal device may send a first invitation message to the first network device to execute the first service process. For example, after the first terminal device completes the IMS registration process, the first terminal device may send a first invitation message to the first network device to implement the IMS call establishment process.
[0181] The following explanation is based on Figure 7.
[0182] Figure 7 is a schematic flowchart of a wireless communication method provided in an embodiment of this application. The method shown in Figure 7 can be executed by a first terminal device and a first network device. The first network device may include one or more of control plane network elements and user plane network elements. For example, the first network device may include a P-CSCF and / or an S-CSCF. The method shown in Figure 7 can be a method for the first terminal device to perform a first service, such as a voice service.
[0183] The method shown in Figure 7 may include step S710.
[0184] In step S710, the first network device receives the first invitation information. The first invitation information may be sent by the first terminal device.
[0185] The first invitation message can be sent by the first terminal device during the execution of the first service process. For example, the first terminal device can be the calling UE, the first service can be a voice service, and the first invitation message can be carried in the SIP invitation message in step S2101 of Figure 3.
[0186] In some embodiments, the first invitation information can be used by a first terminal device to request a second terminal device to perform a first service. For example, the first terminal device is a calling terminal device, and the second terminal device can be a called terminal device. The calling terminal device can send the first invitation information to request the second terminal device to perform the first service. For example, when the first service is a voice service, the first terminal device can be an MO UE, and the second terminal device can be an MT UE. The calling UE invites the called UE to participate in the voice service by sending the first invitation information.
[0187] The invitation message received by the second terminal device may be initiated by the first terminal device and forwarded by the first network device. The first network device may process the first invitation message before forwarding it. The second terminal device may receive the processed first invitation message. Alternatively, the first network device may directly forward the first invitation message, i.e., forward it without processing it. The second terminal device may receive the unprocessed first invitation message.
[0188] In some embodiments, the first terminal device can notify the second terminal device of its own information through a network device by sending a first invitation message, and the second terminal device can participate in the process of the first service based on the content indicated by the first invitation message.
[0189] In some embodiments, the first invitation information may be carried in an SDP offer within a SIP INVITE message.
[0190] In some embodiments, the first invitation information may include third instruction information.
[0191] The third instruction information may include one or more of the following: encoding information used by the first terminal device to perform the first service; the first terminal device accessing the first service through a non-terrestrial communication device; and the type of non-terrestrial communication device used by the first terminal device to perform the first service.
[0192] The third indication information may include encoding information used by the first terminal device for the first service. Optionally, this encoding information may be encoding information determined or obtained by the first terminal device after capability negotiation during the registration process. For example, when the first service is a voice service, if the encoding type corresponding to the capability negotiation of the first terminal device during the registration stage includes Codec-2, then the third indication information including the encoding type used by the first terminal device to access the voice service may include Codec-2.
[0193] The third indication information may include the first terminal device accessing the first service via a non-terrestrial communication device. In other words, the third indication information can be used to indicate whether the first terminal device is accessing the first service via a non-terrestrial communication device. For example, the third indication information may include the first terminal device accessing a voice service via satellite.
[0194] The third indication information may include the type of non-terrestrial communication equipment used by the first terminal device to perform the first service. When the third indication information indicates that the first terminal device can access the first service through a non-terrestrial communication equipment, the third indication information may include the type of non-terrestrial communication equipment used by the first terminal device to perform the first service, such as the type of satellite the first terminal device uses to access the voice service, such as GEO, MEO, or LEO.
[0195] In this embodiment, using the third indication information to carry the encoding information corresponding to capability negotiation can skip or simplify some steps when the first terminal device performs the first service. For example, when the encoding corresponding to capability negotiation is relatively simple, or there are only one or a few encoding options, the first terminal device can skip or simplify the media negotiation work in the call setup process of voice service.
[0196] In some embodiments, in the method shown in FIG7, after receiving the first invitation information sent by the first terminal device, the first network device may send the second invitation information.
[0197] The second invitation message can be sent by the first network device during the first service process of the first terminal device. For example, the second invitation message can be carried in the SIP invitation message in step S2102 of Figure 3.
[0198] In some embodiments, the second invitation information may be used to request the second terminal device to perform the first service, and the second invitation information may include the encoding information used by the first service.
[0199] In some embodiments, the second invitation information, including the coded information used by the first terminal device for the first service, may be determined based on one or more of the following: first invitation information; first instruction information; and the subscription information of the first terminal device.
[0200] For example, the encoding information used by the first terminal device for the first service, as indicated by the second invitation information, can be determined based on the first invitation information. The first terminal device can carry the encoding information for the first service, determined through capability negotiation, in the first invitation information. The first network device can determine the encoding information used by the first terminal device for the first service based on the first invitation information. For example, during the registration process, the first terminal device can confirm the encoding information it is allowed to use for the first service, such as Codec-2, through feedback information sent by the first network device after capability negotiation. Therefore, during the process of establishing a voice call, the first terminal device can carry Codec-2 in the first invitation information, and the first network device can determine the encoding information used by the first terminal device when performing voice services based on the first invitation information.
[0201] For example, the encoding information used by the first terminal device in the first service, as indicated by the second invitation information, can be determined based on the first instruction information. During the registration phase of the first terminal device, the first network device can negotiate and determine the encoding information used by the first terminal device for the first service based on the first instruction information sent by the first terminal device. When the first terminal device performs the first service, when it sends the first invitation information to the first network device, the first terminal device can determine the encoding information used by the first terminal device for the first service based on the information about the first terminal device in the first invitation information. For instance, during the registration process, if the first instruction information sent by the first terminal device instructs it to use Codec-2 in the voice service, and the encoding type is pre-negotiated and determined to be Codec-2, then during the establishment of a voice call by the first terminal device, when the first network device receives the first invitation information from the first terminal device, it can determine that the encoding type used by the first terminal device in the voice service is Codec-2.
[0202] For example, the coding information for the first terminal device to use the first service, as indicated by the second invitation information, can be determined based on the subscription information of the first terminal device. The first network device can confirm the unique identifier of the first terminal device based on the received first invitation information, determine the subscription information of the first terminal device based on the unique identifier, and confirm the coding information for the first terminal device to use the first service based on the subscription information.
[0203] In some embodiments, if the third instruction information does not indicate the coding information used by the first terminal device for the first service, the first network device adds the coding information for the first service to the second invitation information based on the first instruction information and / or subscription information. In other words, when the first terminal device is establishing a first service process, and the first network device does not obtain the coding information for the first terminal device to use the first service based on the third instruction information in the first invitation information, the first network device can confirm the coding information for the first service based on the first instruction information and / or subscription information, and add the coding information to the second invitation information.
[0204] For example, if the first network device does not obtain the encoding information used by the first terminal device for voice services from the first invitation information it receives, then the first network device can obtain the encoding information for voice services, such as Codec-2, from the first instruction information sent by the first terminal device during the registration process. Alternatively, the first network device can also obtain the first terminal device's subscription information based on its unique identifier, and then obtain the encoding information for voice services based on the subscription information. The first network device can then add the encoding information used by the first terminal device for the first service obtained from the first instruction information to the second invitation information, or it can add the encoding information used by the first terminal device for the first service obtained from the subscription information to the second invitation information.
[0205] In some embodiments, if the encoded information obtained by the first network device according to the first instruction information and the subscription information are different, the first network device can take the minimum set between the subscription information and the encoded information obtained according to the first instruction information, or, in the case of a conflict between the two, take the encoded information in the subscription information as the higher priority.
[0206] In some embodiments, the encoding type used by the first terminal device for the first service is a first encoding type, and the second invitation information includes a list of first encoding types, which includes a second encoding type, which is an encoding type other than the first encoding type. For example, when the first terminal device uses EVS codec for voice service, EVS codec can be considered the first encoding type. When the first terminal device uses Codec-2 for voice service, Codec-2 can be considered the second encoding type. When the first terminal device uses Codec-2 for voice service, the second invitation information may include the list of first encoding types, which may include EVS codec. It is understood that the list of first encoding types may also include Codec-2.
[0207] In some embodiments, the first network device may send a third invitation message. The first terminal device may receive the third invitation message.
[0208] The third invitation information may be received by the first terminal device during the execution of the first service process. For example, the first terminal device may be the called UE, the first network device may include the P-SCSF of the called home network, and the third invitation information may be the SIP invitation information in step S304 of Figure 3.
[0209] In some embodiments, the third invitation information can be used by a third terminal device to request a first terminal device to participate in a first service. The third invitation information includes coded information used by the third terminal device to participate in the first service. For example, when the first service is a voice service, the first terminal device can be a called UE, the third terminal device can be a calling UE, and the first network device can be a network device in the called UE's home network, such as a P-SCSF in the called UE's home network. The third invitation information can be used by the calling UE to request the called UE to participate in a voice service, and the third invitation information can include coded information used by the calling UE to participate in the first service.
[0210] The invitation information received by the first terminal device may be initiated by the third terminal device and forwarded by the first network device. The first network device may process the third invitation information before forwarding it. Alternatively, the first network device may forward the third invitation information directly, that is, forward it without processing the third invitation information.
[0211] In some embodiments, the encoding type used by the third terminal device for performing the first service may be a third encoding type, and the third invitation information may include a list of second encoding types.
[0212] In some embodiments, when the first terminal device does not support a third encoding type, the first network device can add a first encoding type to the second encoding type list. The first encoding type can be an encoding type supported by the first terminal device. Alternatively, it can be understood that if the encoding information used by the first terminal device for the first service and the encoding information used by the third terminal device for the first service do not match, the first network device can add an encoding type supported by the first terminal device to the second encoding type list. For example, the first terminal device is the called UE, the third terminal device can be the calling UE, and the calling UE uses Codec-2 as its encoding type when performing voice services. Codec-2 can be a third encoding type. The P-SCSF can be the first network device, and the third invitation information can include the second encoding type list. The second encoding type list can include encoding information that the calling UE can use when performing voice services, such as Codec-2. When the called UE does not support Codec-2, the P-SCSF can add a first encoding type to the second type list. The first encoding type can be an encoding type supported by the calling UE, such as EVS codec.
[0213] In some embodiments, the first network device may be configured with transcoding functionality. For example, when the first encoding type used by the first terminal device for a first service is different from the second encoding type, the first network device may be configured with transcoding functionality.
[0214] In some embodiments, the transcoding function can be used for transcoding between a second encoding type and a first encoding type. For example, a first network device can convert a first encoding type to a second encoding type, or vice versa. For instance, if the first encoding type is Codec-2 and the second encoding type is EVS codec, the first network device can convert Codec-2 to EVS codec, or vice versa.
[0215] In some embodiments, the first network device can configure transcoding functionality for the second network device. For example, if the terminal device served by the first network device does not support the encoding information in the first invitation information and / or the third invitation information, the first network device can configure transcoding functionality for the second network device. For example, if the first terminal device does not support a third encoding type, the first network device can configure transcoding functionality for the second network device. If the first terminal device is a called UE, and the called UE does not support a third terminal device, such as a third encoding type supported by the calling UE, such as Codec-2, then the first network device can configure transcoding functionality for the gateway network element. The first network device can be a P-SCSF.
[0216] In some embodiments, the second network device may include a gateway network element. For example, the second network device may include an access gateway (AGW). It should be noted that the second network device may include other network elements with similar functions to an AGW. For example, if other IMS media plane network elements are configured to have network elements with functions similar to an AGW, the second network device may include that network element.
[0217] In some embodiments, the transcoding function can be used for transcoding between a third encoding type and a first encoding type. For example, the transcoding function can be used to convert a third encoding type into a first encoding type, or the first network device can convert a first encoding type into a third encoding type. For instance, if the first encoding type is Codec-2 and the third encoding type is EVS codec, the first network device can convert Codec-2 into EVS codec, or vice versa.
[0218] For ease of understanding, the following explanation is provided with reference to Figure 8. In Figure 8, the first network device may include the P-CSCF, the second network device may be the AGW, and the first terminal device may be the MT UE. The network shown in Figure 8 is the MT UE's home network; it can also be understood that the S / P-CSCF and AGW in Figure 8 are both network devices within the MT UE's home network. The process shown in Figure 8 may include step S810a.
[0219] In step S810a, the P-CSCF can determine the encoding information of the MO UE based on the received INVITE message. When the P-CSCF determines that the MO UE and the MT UE support different encoding information (e.g., Codec-2 and AMR-NB respectively), the P-CSCF can interact with the AGW to configure the transcoding function. For example, if the encoding type of the MO UE is Codec-2 and the encoding type supported by the MT UE is AMR, the P-CSCF can configure the conversion between Codec-2 and AMR-NB and the corresponding rate and other encoding information, and then change the encoding information to AMR-NB related configuration information in the SDP Offer and send it to the next hop, such as the MT UE.
[0220] In some embodiments, when the first terminal device supports a third encoding type, the first network device may delete some or all of the encoding types other than the third encoding type from the second encoding type list. Alternatively, if the encoding information used by the first terminal device for the first service matches the encoding information used by the third terminal device for the first service, the first network device may delete some or all of the encoding types other than the third encoding type from the second encoding type list. For example, if the first terminal device is the called UE, and the third terminal device is the calling UE, and the calling UE uses Codec-2 for voice service (Codec-2 can be a third encoding type), when the called UE supports Codec-2, the P-SCSF may delete some, or all, of the encoding types other than Codec-2 from the second encoding type list. If the second encoding type list includes Codec-2, EVS codec, and AMR codec, and the called UE can support Codec-2, P-SCSF can delete both EVS codec and AMR codec from the second encoding type list, or it can delete only EVS codec, or only AMR codec.
[0221] For ease of understanding, the possible communication process on the MO network side is described below with reference to Figures 9A and 9B. In Figure 9A, the first network device includes a P-CSCF. In Figure 9B, the first network device includes an AF. In Figures 9A and 9B, the first terminal device can be an MO UE, and the MO UE accesses the network via a GEO.
[0222] The following is an explanation of Figure 9A.
[0223] In step S910, the MO UE sends an INVITE message to the P-CSCF. Optionally, the INVITE message may carry an SDP offer. The SDP offer may carry the MO UE's encoding information, such as Codec-2.
[0224] When the P-CSCF receives the INVITE message, it can determine whether to add or modify the list of encoding types for the MO UE based on the MO UE's capability information (i.e., the first indication information).
[0225] For example, if the encoding type for voice services of the MO UE negotiated by the P-CSCF during the MO UE registration process is Codec-2, the P-CSCF can add encoding information such as EVS and AMR to the encoding type list to form an updated encoding type list. If the INVITE message sent by the MO UE does not carry encoding information, the P-CSCF can add Codec-2 to the encoding type list.
[0226] In step S920, the P-CSCF can send the updated list of encoding types to the S-CSCF. As shown in Figure 9A, the updated list of encoding types can be carried in the SDP offer*.
[0227] In step S930, the S-CSCF of the MO UE can send an INVITE message to the network of the MT UE, which includes an SDP offer*.
[0228] In step S940, the S-CSCF can receive a reply message from the MT UE. This reply message can be a 200 OK message. The reply message may include the encoding type selected by the MT UE.
[0229] In step S950, the S-CSCF can send the reply message from step S940 to the P-CSCF.
[0230] If the encoding type in the reply message differs from the encoding types supported by the MO UE, the P-CSCF can interact with the AGW to configure transcoding functionality. For example, if the MO UE uses Codec-2 and the MT UE uses AMR, the P-CSCF can interact with the AGW to configure transcoding between Codec-2 and AMR.
[0231] It should be noted that Figure 9A is for illustrative purposes only. Some steps in the communication process shown in Figure 9A can be omitted. Alternatively, one or more steps can be added to the communication process shown in Figure 9A.
[0232] The communication process shown in Figure 9A can be applied to both simplified and non-simplified call setup procedures.
[0233] Figure 9B shows a simplified call setup process. In Figure 9B, the MO UE accesses via GEO.
[0234] In Figure 9B, in step S1910, the MO UE sends an INVITE message. This message includes the SDP offer but not the pre-condition.
[0235] Optionally, the P-CSCF can perform step S1920.
[0236] In step S1920, the P-CSCF can determine whether to add / modify the encoding type list after receiving the INVITE message from step S1910. Alternatively, the P-CSCF can choose not to add or modify the encoding type list.
[0237] If the P-CSCF adds / modifies the encoding type list in the INVITE message, the INVITE message sent by the P-CSCF will include the updated SDP offer. The updated SDP offer can be represented as SDP offer*.
[0238] In the simplified call setup procedure, the AF can receive an INVITE message. The SDF offer in this INVITE message can be either an updated SDP offer or the original SDP offer sent by the MO UE.
[0239] Upon receiving an INVITE message, AF can terminate the original INVITE (without pre-condition) and initiate a new INVITE message with a pre-condition. The new INVITE message is represented as INVITE*. For example, AF can add "Require:precondition" to the SIP header and "a=curr:", "a=des:", and "a=conf:" to the SDP offer.
[0240] In step S1930, the AF can determine whether to add / modify the encoding type list in the new INVITE message. If the addition / modification of the encoding type list is confirmed, the SDP offer in the new INVITE message will be the updated SDP offer, i.e., SDP offer*. If the encoding type list is not added / modified, the SDP offer in the new INVITE message will be the SDP offer in the INVITE message received by the AF.
[0241] In addition, AF can configure transcoding functionality for AGW.
[0242] It should be noted that only one of steps S1920 and S1930 needs to be performed.
[0243] Step S1940: P-CSCF configures transcoding function for AGW.
[0244] It should be noted that Figure 9B is for illustrative purposes only. Some steps in the communication process shown in Figure 9B can be omitted. For example, one or more 180-ringing steps can be omitted. Alternatively, one or more steps can be added to the communication process shown in Figure 9B.
[0245] The following detailed description uses Figures 10A and 10B to illustrate the possible communication process on the MT network side.
[0246] In Figure 10A, the first network device may include a P-CSCF. In Figure 10B, the first network device may include an AF. In Figures 10A and 10B, the first terminal device may be an MT UE, and the MT UE accesses the network via GEO.
[0247] The following is an explanation of Figure 10A.
[0248] In step S1010, the S-CSCF can receive the INVITE message sent by the MO UE network and forward it to the P-CSCF. The INVITE message may include an SDP offer. The SDP offer may include encoding information requested by the MO UE, such as the encoding type requested by the MO UE. This encoding type can be represented by a list of encoding types.
[0249] Upon receiving the INVITE message, the P-CSCF can determine whether to add or modify the list of encoding types based on the MT UE's capability information (i.e., the MT UE's first indication information) obtained during the registration process.
[0250] For example, if the capability information of the MT UE indicates that the MO UE supports the encoding type Codec-2 under GEO voice, and if the encoding type list of the SDP offer in step S1010 does not include Codec-2, then the P-CSCF can add Codec-2 to the encoding list to form an updated encoding type list.
[0251] For example, if the capability information of the MT UE indicates that the MO UE supports the encoding type Codec-2 under GEO voice, and if the encoding type list of the SDP offer in step S1010 includes Codec-2, then the P-CSCF can delete other encoding types besides Codec-2 from the encoding list, that is, only retain the encoding type corresponding to DEO voice, forming an updated encoding type list.
[0252] For example, if the MO UE accesses via TN, and the SDP offer encoding type list in step S1010 includes encoding and decoding commonly used by terrestrial NR base stations such as AMR and EVS, but does not include encoding for GEO voice (e.g., Codec-2), then the P-CSCF can add Codec-2 to the encoding list to form an updated encoding type list.
[0253] For example, if the MO UE accesses via TN, and the SDP offer encoding type list in step S1010 includes commonly used encoding and decoding methods of terrestrial NR base stations such as AMR and EVS, as well as encoding corresponding to GEO voice (e.g., Codec-2), then the P-CSCF can delete other encoding types besides Codec-2 from the encoding list, that is, only retain the encoding type corresponding to DEO voice, to form an updated encoding type list.
[0254] It should be noted that the updated list of encoding types can be contained in the SDP offer*.
[0255] In step S1020, the P-CSCF can send the updated encoding type list to the MT UE. As shown in Figure 10A, the updated encoding type list can be carried in the SDP offer*.
[0256] In steps S1030 and S1040, the MT UE can confirm the encoding information used based on the received encoding type list.
[0257] In step S1050, the P-CSCF can receive a reply message sent by the MT UE. The reply message can be, for example, 200 OK. The SDP offer in the reply message can carry the encoding information selected by the MT UE.
[0258] If the encoding information requested by the MO UE (e.g., the encoding information indicated in step S1010) is different from the encoding information selected by the MT UE in the reply message, the P-CSCF can interact with the AGW to configure the transcoding function.
[0259] For example, if in step S1050 the MT UE selects to use Codec-2, but step S1010 indicates that the MO UE requests AMR, then the P-CSCF can configure transcoding between Codec-2 and AMR to the AGW.
[0260] It should be noted that Figure 10A is merely an example. Some steps in the communication process shown in Figure 10A can be omitted. Alternatively, one or more steps can be added to the communication process shown in Figure 10A.
[0261] The communication process shown in Figure 10A can be applied to both the simplified and non-simplified call setup procedures. Figure 10B shows the simplified call setup procedure. In Figure 10B, the MT UE accesses via GEO.
[0262] In step S11010, the S-CSCF can receive an INVITE message. This INVITE message contains a pre-condition.
[0263] In step S11020, S-CSCF sends an INVITE message to AF.
[0264] S-CSCF can terminate the original INVITE message and initiate a new INVITE message without pre-conditions.
[0265] Optionally, AF can perform step S11030.
[0266] Step S11030: AF determines the list of added / modified encoding types.
[0267] If the addition / modification of the encoding type list is confirmed, the SDP offer in the new INVITE message will be the updated SDP offer, i.e., SDP offer*. If the encoding type list is not added / modified, the SDP offer in the new INVITE message will be the SDP offer in the INVITE message received by AF.
[0268] In addition, AF can configure transcoding functionality for AGW.
[0269] Optionally, the P-CSCF can perform step S11040.
[0270] In step S11040, the P-CSCF may determine to add / modify the encoding type list after receiving the INVITE message from step S1910. Alternatively, the P-CSCF may choose not to add or modify the encoding type list.
[0271] If the P-CSCF adds / modifies the list of encoding types in the INVITE message, the updated SDP offer will be included in the INVITE message sent by the P-CSCF.
[0272] Optionally, only one of steps S11030 and S11040 may be performed.
[0273] Step S11050: P-CSCF configures transcoding function for AGW.
[0274] It should be noted that Figure 10B is merely an example. Some steps in the communication process shown in Figure 10B can be omitted. For example, one or more 180-degree ringing steps can be omitted. Alternatively, one or more steps can be added to the communication process shown in Figure 10B.
[0275] It is understood that the methods shown in Figures 9A, 9B, 10A, and 10B can be combined in this application. For ease of understanding, the call flow will be explained below with reference to Figure 11.
[0276] Figure 11 is a schematic flowchart of a wireless communication method provided in an embodiment of this application. The method shown in Figure 11 can be executed by MO UE, P-CSCF (MO P-CSCF) serving MO UE, S-CSCF (MO S-CSCF) serving MO UE, MT UE, S-CSCF (MT S-CSCF) serving MT UE, and P-CSCF (MT P-CSCF) serving MT UE.
[0277] For the home network of MO UE, MO UE can be the first terminal device and MT UE can be the second terminal device. The first network device can include MO P-CSCF and / or MO S-CSCF.
[0278] For the MT UE home network, the MT UE can be the first terminal device, and the MO UE can be the third terminal device. The first network device can include MT P-CSCF and / or MT S-CSCF.
[0279] In step S1110, the MO UE can send a SIP INVITE message to the P-CSCF.
[0280] The SIP INVITE message may include information indicating that the MO UE is accessing via satellite, or further indicating that the MO UE can access via GEO, MEO, or LEO. The SIP INVITE message may also include pre-negotiated coding information, which is the allowed coding information determined by the MO UE during the registration process. This information can be carried within the SDP Offer in the SIP INVITE message.
[0281] It should be noted that pre-negotiation coding information is generally quite simple, that is, there is only one or a few coding options. This allows the media negotiation work to be skipped or simplified in the IMS call setup process.
[0282] For MO IMS network elements, if the MO UE does not add the corresponding encoding information for capability negotiation in step S1110, then a certain IMS network element in the MO UE's home network (such as MO S-CSCF, MO P-CSCF) can add the corresponding encoding for capability negotiation to the SIP INVITE message and send the SIP INVITE message to the next hop.
[0283] As one possible approach, in step S1120, after the MO S-CSCF receives the SIP INVITE message, it can interact with the HSS / UDM to accept the corresponding capability negotiation code, or directly add the capability negotiation code saved during MO UE registration into the SIP INVITE message, and then send it to the MT UE through other IMS network elements.
[0284] As one possible approach, in step S1140, the IMS network element (such as MO P-CSCF) in the home network of the MO UE can directly update the encoding type list in the SDP after receiving the SIP INVITE. That is, it can further add other encoding information (such as AMR, EVS and other encoding information commonly used in ordinary voice) and the corresponding bit rate to the received encoding type list, and then send the modified SIP INVITE message to the next hop.
[0285] Step S1130, MO S-CSCF performs service control.
[0286] In step S1150, NT S-CSCF performs service control.
[0287] In the MT UE's home network, for MT IMS network elements, it can be determined whether transcoding is necessary based on the encoding information supported by the MT UE, which is determined after capability negotiation during the MT UE registration process. If transcoding is necessary, the MT P-CSCF updates the encoding type list in the SDP offer and sends it to the next hop.
[0288] For example, when the MT UE does not support the encoding information corresponding to GEO voice, the MT S-CSCF can further add other encoding type lists (such as AMR, EVS and other encoding information commonly used for ordinary voice) and corresponding bit rates to the received encoding type list, and then send the modified SIP INVITE message to the MT P-CSCF (i.e. step S1150).
[0289] For example, when the MT UE does not support the encoding information corresponding to GEO voice, the MT P-CSCF can further add other encoding type lists (such as AMR, EVS and other encoding information commonly used for ordinary voice) and corresponding bit rates to the received encoding type list, and then send the modified SIP INVITE message to the MT UE (i.e. step S1160).
[0290] It should be noted that updating the encoding type list on the MO side and MT side can be performed by only one of them.
[0291] In steps S1170 and S1180, when the MT UE receives a SIP INVITE message sent by the network element S-CSCF in the MT UE's home network, it can determine whether the MT UE accesses the IMS voice service via satellite (such as GEO STA) through the following methods 1 to 3.
[0292] In Method 1, the SIP INVITE message in step S1170 contains encoding information corresponding to the MT UE's capability negotiation during the registration process. This encoding information indicates the MT UE's ability to conduct voice services via satellite access. Furthermore, this encoding information may include the type of satellite the MT UE can access, such as GEO. Therefore, when the MT UE receives this SIP INVITE message, it knows the encoding information and thus does not need to negotiate further. It only needs to decide whether to accept or reject, thereby determining whether to access IMS voice services via satellite.
[0293] Method 2: During the IMS registration process, the MT UE has already negotiated and determined the encoding information with the network device through encoding capability. For example, if the MT UE's encoding information supports satellite access voice, then when the SIP INVITE message in step S1170 contains encoding information that supports satellite access voice, it can be considered that the scenario is a satellite access voice service, and the encoding information can be directly accepted.
[0294] Method 3: If the encoding information supported by the MT UE and the MO UE does not match, then a certain network element in steps S1120-S1170 needs to configure transcoding function for the IMS media plane and send the transcoded encoding information to the MT UE via SIP INVITE message in step S1170.
[0295] For example, based on the SDP Offer in the SIP INVITE message received in step 1160, the MT P-CSCF determines that the MO UE's encoding information (such as Codec-2) cannot be supported by the MT UE. Therefore, it interacts with the AGW to configure transcoding capabilities, converting Codec-2 into AMR-NB and corresponding rate configurations (which the MT UE can support). Then, the encoding information is changed to AMR-NB related configurations in the SDP Offer and sent to the next hop (MT UE).
[0296] It is important to note that the network elements within the home network of both the MO UE and MT UE are aware of their encoding information and related capabilities. This information can be obtained through encoding capability negotiation during the registration process between the MO UE and MT UE, or it can be determined automatically by the network device in the absence of prior knowledge. If the network device does not obtain the encoding information of the MO UE and MT UE during registration, it can make a judgment based on the actual encoding information received from the MO UE and MT UE when the MO UE invites the MT UE to establish a voice service process.
[0297] In steps S1190 to S11140, the MT UE sends a reply message to the MO UE. The reply message may or may not carry the encoding information of the MT UE.
[0298] It should be noted that Figure 11 is merely an example. Some steps in the communication process shown in Figure 11 can be omitted. For example, one or more of steps S1190 and S11130 can be omitted. Alternatively, one or more steps can be added to the communication process shown in Figure 11.
[0299] It should be noted that in this application, the MO / MT UE may support one or more of the following: capability negotiation during the IMS REGISTER process; access via GEO; GEO voice codec; and SIP INVITE without pre-condition.
[0300] It should be noted that in this application, the P-CSCF may support one or more of the following: capability negotiation during IMS REGISTER; codec transcoding of GEO voice; processing SIP INVITE without pre-conditions, such as skipping “authorized QoS resources” during IMS call setup; and acting as a B2BUA for interaction with ordinary MO / MT UEs.
[0301] It should be noted that in this application, S-CSCF can support one or more of the following: iFC-based SIP message rerouting; GEO voice service control; IMS HSS; and GEO voice new subscription parameters. The method embodiments of this application have been described in detail above; the apparatus embodiments of this application are described in detail below. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.
[0302] Figure 12 is a schematic structural diagram of a network device 1200 provided in an embodiment of this application. The network device 1200 may be a first network device, and the first network device 1200 may include a first receiving unit 1210.
[0303] The first receiving unit 1210 is configured to receive first indication information sent by the first terminal device; wherein the first indication information is sent during the registration process, and the first indication information is used to indicate one or more of the following: encoding information supported by the first terminal device; whether the first terminal device supports the ability to perform the first service through the first wireless access type; the first terminal device performing the first service through the first wireless access type; and the type of wireless access communication device used by the first terminal device to perform the first service.
[0304] In some embodiments, the encoding information may include one or more of the following: encoding type, bit rate, frame format, transmission protocol, and service type.
[0305] In some embodiments, the encoding information includes encoding information used for performing the first service.
[0306] In some embodiments, the first indication information is carried in one or more of the following: one or more fields in the SIP registration message header; or the SDP offer in the SIP registration message.
[0307] In some embodiments, the type of non-terrestrial communication device used by the first terminal device to perform the first service corresponds to the encoding information that the first terminal device supports for performing the first service; and / or, when the first terminal device accesses the first service through a non-terrestrial communication device, the first terminal device uses specific encoding information.
[0308] In some embodiments, the network device is further configured to send feedback information to the first terminal device; wherein the feedback information is configured to indicate one or more of the following: encoding information that allows the first terminal device to perform a first service; whether the first terminal device is allowed to access the first service through a non-terrestrial communication device; and the type of service that the first terminal device is allowed to perform.
[0309] In some embodiments, the feedback information is determined based on the first instruction information and / or the subscription information of the first terminal device.
[0310] In some embodiments, the network device is further configured to determine, based on one or more of the first instruction information, subscription information, and feedback information, whether it is necessary to configure transcoding function for the first terminal device and / or modify the encoding type list in the first service establishment process during the first service process.
[0311] In some embodiments, the network device is further configured to receive a first invitation message sent by a first terminal device; wherein the first invitation message is used by the first terminal device to request the second terminal device to perform a first service.
[0312] In some embodiments, the first invitation information includes third instruction information, which includes one or more of the following: encoding information used by the first terminal device to perform the first service; the first terminal device accessing the first service through a non-terrestrial communication device; and the type of non-terrestrial communication device used by the first terminal device to perform the first service.
[0313] In some embodiments, the network device is further configured to send a second invitation message; wherein the second invitation message is used to request the second terminal device to perform a first service, and the second invitation message includes encoding information used by the first service.
[0314] In some embodiments, the second invitation information includes coded information used by the first terminal device for the first service, which is determined based on one or more of the following: first invitation information; first instruction information; and subscription information of the first terminal device.
[0315] In some embodiments, the network device is further configured to add the encoding information for the first service to the second invitation information based on the first instruction information and / or subscription information, in the case that the third instruction information does not instruct the first terminal device to use the encoding information for the first service.
[0316] In some embodiments, the encoding type used by the first terminal device for performing the first service is a first encoding type, and the second invitation information includes a list of first encoding types, the list of first encoding types includes a second encoding type, and the second encoding type is an encoding type other than the first encoding type.
[0317] In some embodiments, the network device is further configured to perform transcoding; wherein the transcoding function is used for transcoding between a second encoding type and a first encoding type.
[0318] In some embodiments, the network device is further configured to send a third invitation message to the first terminal device; wherein the third invitation message is used by the third terminal device to request the first terminal device to perform a first service, and the third invitation message includes coded information used by the third terminal device to perform the first service.
[0319] In some embodiments, the encoding type used by the third terminal device for performing the first service is a third encoding type, the third invitation information includes a second encoding type list, and the network device is further configured to add a first encoding type to the second encoding type list if the first terminal device does not support the third encoding type; wherein, the first encoding type is an encoding type supported by the first terminal device.
[0320] In some embodiments, the encoding type used by the third terminal device for performing the first service is a third encoding type, the third invitation information includes a second encoding type list, and the network device is further configured to delete some or all of the encoding types other than the third encoding type from the second encoding type list when the first terminal device supports the third encoding type.
[0321] In some embodiments, the network device is further configured to configure a transcoding function to the second network device; wherein the transcoding function is used for transcoding between a third encoding type and a first encoding type.
[0322] In some embodiments, the second network device includes a gateway element.
[0323] In some embodiments, the first network device includes one or more of the following: P-CSCF, S-CSCF.
[0324] In some embodiments, the first service includes one or more of the following: voice, voice, emergency services, video, and messaging services.
[0325] In some embodiments, the first wireless access type includes non-terrestrial communication.
[0326] In an optional embodiment, the first receiving unit 1210 may be a transceiver 1430. The network device 1200 may also include a processor 1410 and a memory 1420, as shown in FIG14.
[0327] Figure 13 is a schematic structural diagram of a terminal device 1300 provided in an embodiment of this application. The terminal device 1300 may include a first transmitting unit 1310.
[0328] The first sending unit 1310 is used to send first indication information to the first network device; wherein the first indication information is sent during the registration process, and the first indication information is used to indicate one or more of the following: encoding information of the first terminal device supporting the first service; whether the first terminal device supports the ability to access the first service through non-terrestrial communication equipment; the first terminal device accessing the first service through non-terrestrial communication equipment; and the type of non-terrestrial communication equipment used by the first terminal device to perform the first service.
[0329] In some embodiments, the encoding information includes one or more of the following: encoding type, bit rate, frame format, transmission protocol, and service type of the first service.
[0330] In some embodiments, the first indication information is carried in one or more of the following: one or more fields in the SIP registration message header; or the SDP offer in the SIP registration message.
[0331] In some embodiments, the type of non-terrestrial communication device used by the first terminal device to perform the first service corresponds to the encoding information that the first terminal device supports for performing the first service; and / or, when the first terminal device accesses the first service through a non-terrestrial communication device, the first terminal device uses specific encoding information.
[0332] In some embodiments, the terminal device is further configured to receive feedback information sent by the first network device; wherein the feedback information is configured to indicate one or more of the following: encoding information that allows the first terminal device to perform a first service; whether the first terminal device is allowed to access the first service through a non-terrestrial communication device; and the type of service that the first terminal device is allowed to perform.
[0333] In some embodiments, the feedback information is determined based on the first instruction information and / or the subscription information of the first terminal device.
[0334] In some embodiments, the feedback information is used by the first network device to determine whether to configure transcoding function for the first terminal device during the first service.
[0335] In some embodiments, the terminal device is further configured to send a first invitation message to a first network device; wherein the first invitation message is used by the first terminal device to invite a second terminal device to participate in a first service, and the first invitation message includes third indication information, which includes one or more of the following: encoding information used by the first terminal device to perform the first service; the first terminal device accessing the first service through a non-terrestrial communication device; and the type of non-terrestrial communication device used by the first terminal device to perform the first service.
[0336] In some embodiments, the terminal device is further configured to receive third invitation information; the third invitation information is used by the third terminal device to invite the first terminal device to participate in the first service, and the third invitation information includes coded information used by the third terminal device to perform the first service.
[0337] In some embodiments, the encoding type used by the third terminal device to perform the first service is a third encoding type, and the third invitation information includes a second encoding type list. If the first terminal device does not support the third encoding type, the second encoding type list includes the first encoding type, which is an encoding type supported by the first terminal device.
[0338] In some embodiments, the first network device includes one or more of the following: P-CSCF, S-CSCF.
[0339] In some embodiments, the first service includes voice service.
[0340] In an optional embodiment, the first transmitting unit 1310 may be a transceiver 1430. The terminal device 1300 may also include a processor 1410 and a memory 1420, as shown in FIG14.
[0341] Figure 14 is a schematic structural diagram of a communication apparatus according to an embodiment of this application. The dashed lines in Figure 14 indicate that the unit or module is optional. This apparatus 1400 can be used to implement the methods described in the above method embodiments. The apparatus 1400 can be a chip, a terminal device, or a network device.
[0342] Apparatus 1400 may include one or more processors 1410. The processor 1410 may support apparatus 1400 in implementing the methods described in the preceding method embodiments. The processor 1410 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.
[0343] The apparatus 1400 may further include one or more memories 1420. The memories 1420 store a program that can be executed by the processor 1410, causing the processor 1410 to perform the methods described in the preceding method embodiments. The memories 1420 may be independent of the processor 1410 or integrated within the processor 1410.
[0344] The device 1400 may also include a transceiver 1430. The processor 1410 can communicate with other devices or chips via the transceiver 1430. For example, the processor 1410 can send and receive data with other devices or chips via the transceiver 1430.
[0345] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal device or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.
[0346] This application also provides a computer program product. The computer program product includes a program. This computer program product can be applied to a terminal device or network device provided in the embodiments of this application, and the program causes a computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.
[0347] This application also provides a computer program. This computer program can be applied to the terminal device or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal device or network device in various embodiments of this application.
[0348] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.
[0349] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.
[0350] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.
[0351] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.
[0352] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.
[0353] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.
[0354] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.
[0355] In the embodiments of this application, "comprising" can refer to direct inclusion or indirect inclusion. Optionally, "comprising" mentioned in the embodiments of this application can be replaced with "indicating" or "used to determine". For example, "A includes B" can be replaced with "A indicates B" or "A is used to determine B".
[0356] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0357] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0358] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0359] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0360] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially 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 this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.
[0361] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A wireless communication method, characterized in that, include: The first network device receives the first instruction information; The first indication information is sent during the registration process of the first terminal device, and the first indication information is used to indicate one or more of the following: The encoding information supported by the first terminal device; Whether the first terminal device supports the ability to perform the first service through the first wireless access type; The first terminal device performs the first service through the first wireless access type; The type of wireless access communication device used by the first terminal device to perform the first service.
2. The method according to claim 1, characterized in that, The encoded information includes one or more of the following: Encoding type, bit rate, frame format, transmission protocol, and service type.
3. The method according to claim 1 or 2, characterized in that, The encoding information includes encoding information used for performing the first service.
4. The method according to claim 1 or 2, characterized in that, The first indication information carries one or more of the following: One or more fields in the SIP Registration message header; The Session Description Protocol (SDP) request in the SIP registration message.
5. The method according to any one of claims 1-4, characterized in that, The type of non-terrestrial communication equipment used by the first terminal device to perform the first service corresponds to the encoding information that the first terminal device supports for performing the first service; and / or, When the first terminal device accesses the first service through the non-terrestrial communication device, the first terminal device uses specific encoding information.
6. The method according to any one of claims 1-5, characterized in that, The method further includes: The first network device sends feedback information; The feedback information is used to indicate one or more of the following: The first terminal device is allowed to access the encoded information used by the first service; Whether to allow the first terminal device to access and perform the first service through non-terrestrial communication equipment; The types of services that the first terminal device is allowed to perform.
7. The method according to claim 6, characterized in that, The feedback information is determined based on the first indication information and / or the subscription information of the first terminal device.
8. The method according to claim 6 or 7, characterized in that, The method further includes: Based on one or more of the first instruction information, contract information, and feedback information, the first network device determines whether it is necessary to configure transcoding function for the first terminal device and / or modify the encoding type list in the first service establishment process during the first service process.
9. The method according to any one of claims 1-8, characterized in that, The method further includes: The first network device receives the first invitation information; The first invitation information is used by the first terminal device to request the second terminal device to perform the first service.
10. The method according to claim 9, characterized in that, The first invitation information includes third instruction information, which includes one or more of the following: The encoding information used by the first terminal device to perform the first service; The first terminal device accesses and performs the first service through a non-terrestrial communication device. The type of non-terrestrial communication device used by the first terminal device to perform the first service.
11. The method according to claim 10, characterized in that, The method further includes: The first network device sends a second invitation message; The second invitation information is used to request the second terminal device to perform the first service, and the second invitation information includes the encoding information used by the first service.
12. The method according to claim 11, characterized in that, The second invitation information, including the encoding information used by the first terminal device for the first service, is determined based on one or more of the following: The first invitation information; The first indication information; The subscription information of the first terminal device.
13. The method according to claim 12, characterized in that, The method further includes: If the third instruction information does not instruct the first terminal device to use the encoding information for the first service, the first network device adds the encoding information for the first service to the second invitation information according to the first instruction information and / or the subscription information.
14. The method according to any one of claims 9-13, characterized in that, The encoding type used by the first terminal device to perform the first service is a first encoding type, and the second invitation information includes a first encoding type list. The first encoding type list includes a second encoding type, and the second encoding type is an encoding type other than the first encoding type.
15. The method according to claim 14, characterized in that, The method further includes: The first network device is configured with transcoding functionality; The transcoding function is used for transcoding between the second encoding type and the first encoding type.
16. The method according to any one of claims 1-8, characterized in that, The method further includes: The first network device sends a third invitation message; The third invitation information is used by the third terminal device to request the first terminal device to perform the first service, and the third invitation information includes the encoding information used by the third terminal device to perform the first service.
17. The method according to claim 16, characterized in that, The encoding type used by the third terminal device to perform the first service is a third encoding type, the third invitation information includes a list of second encoding types, and the method further includes: If the first terminal device does not support the third encoding type, the first network device adds the first encoding type to the second encoding type list; The first encoding type is the encoding type supported by the first terminal device.
18. The method according to claim 16 or 17, characterized in that, The encoding type used by the third terminal device to perform the first service is a third encoding type, the third invitation information includes a list of second encoding types, and the method further includes: If the first terminal device supports the third encoding type, the first network device deletes some or all of the other encoding types from the second encoding type list, excluding the third encoding type.
19. The method according to claim 17, characterized in that, The method further includes: The first network device configures transcoding functionality to the second network device; The transcoding function is used for transcoding between the third encoding type and the first encoding type.
20. The method according to claim 19, characterized in that, The second network device includes an access gateway.
21. The method according to any one of claims 1-12, characterized in that, The first network device includes one or more of the following: Proxy Call Session Control Function (P-CSCF), Service Call Session Control Function (S-CSCF), and Application Function (AF).
22. The method according to any one of claims 1-13, characterized in that, The first service includes one or more of the following: voice, voice, emergency services, video, and messaging services.
23. The method according to any one of claims 1-22, characterized in that, The first wireless access type includes non-terrestrial communication.
24. A wireless communication method, characterized in that, include: The first terminal device sends the first instruction information; The first indication information is sent during the registration process of the terminal device, and the first indication information is used to indicate one or more of the following: The encoding information for the first terminal device to support the first service; Whether the first terminal device supports the ability to access the first service through non-terrestrial communication devices; The first terminal device accesses and performs the first service through the non-terrestrial communication equipment. The type of non-terrestrial communication equipment used by the first terminal device to perform the first service.
25. The method according to claim 24, characterized in that, The encoded information includes one or more of the following: Encoding type, bit rate, frame format, transmission protocol, and service type of the first service.
26. The method according to claim 24 or 25, characterized in that, The first indication information carries one or more of the following: One or more fields in the SIP registration message header; The SDP request in the SIP registration message.
27. The method according to any one of claims 24-26, characterized in that, The type of non-terrestrial communication equipment used by the first terminal device to perform the first service corresponds to the encoding information that the first terminal device supports for performing the first service; and / or, When the first terminal device accesses the first service through the non-terrestrial communication device, the first terminal device uses specific encoding information.
28. The method according to any one of claims 24-27, characterized in that, The method further includes: The first terminal device receives feedback information; The feedback information is used to indicate one or more of the following: The first terminal device is allowed to access the encoded information used by the first service; Whether to allow the first terminal device to access and perform the first service through non-terrestrial communication equipment; The types of services that the first terminal device is allowed to perform.
29. The method according to claim 28, characterized in that, The feedback information is determined based on the first indication information and / or the subscription information of the first terminal device.
30. The method according to claim 28 or 29, characterized in that, The feedback information is used by the first network device to determine whether to configure transcoding function for the first terminal device during the first service.
31. The method according to any one of claims 24-30, characterized in that, The method further includes: The first terminal device sends the first invitation message; The first invitation information is used by the first terminal device to invite the second terminal device to participate in the first service. The first invitation information includes third indication information, which includes one or more of the following: The encoding information used by the first terminal device to perform the first service; The first terminal device accesses and performs the first service through a non-terrestrial communication device. The type of non-terrestrial communication device used by the first terminal device to perform the first service.
32. The method according to any one of claims 24-30, characterized in that, The method further includes: The first terminal device receives the third invitation information; The third invitation information is used by the third terminal device to invite the first terminal device to participate in the first service. The third invitation information includes the encoding information used by the third terminal device to perform the first service.
33. The method according to claim 32, characterized in that, The encoding type used by the third terminal device to perform the first service is a third encoding type. The third invitation information includes a second encoding type list. If the first terminal device does not support the third encoding type, the second encoding type list includes a first encoding type, which is an encoding type supported by the first terminal device.
34. The method according to any one of claims 24-33, characterized in that, The first network device includes one or more of the following: P-CSCF, S-CSCF, AF.
35. The method according to any one of claims 24-34, characterized in that, The first service includes voice services.
36. A network device, characterized in that, The network device is a first network device, which includes: The first receiving unit is used to receive the first instruction information; The first indication information is sent during the registration process of the first terminal device, and the first indication information is used to indicate one or more of the following: The encoding information supported by the first terminal device; Whether the first terminal device supports the ability to perform the first service through the first wireless access type; The first terminal device performs the first service through the first wireless access type; The type of wireless access communication device used by the first terminal device to perform the first service.
37. The network device according to claim 36, characterized in that, The encoded information includes one or more of the following: Encoding type, bit rate, frame format, transmission protocol, and service type.
38. The network device according to claim 36 or 37, characterized in that, The encoding information includes encoding information used for performing the first service.
39. The network device according to claim 36 or 37, characterized in that, The first indication information carries one or more of the following: One or more fields in the SIP registration message header; The SDP request in the SIP registration message.
40. The network device according to any one of claims 36-39, characterized in that, The type of non-terrestrial communication equipment used by the first terminal device to perform the first service corresponds to the encoding information that the first terminal device supports for performing the first service; and / or, When the first terminal device accesses the first service through the non-terrestrial communication device, the first terminal device uses specific encoding information.
41. The network device according to any one of claims 36-40, characterized in that, The network device is also used to send feedback information; The feedback information is used to indicate one or more of the following: The first terminal device is allowed to access the encoded information used by the first service; Whether to allow the first terminal device to access and perform the first service through non-terrestrial communication equipment; The types of services that the first terminal device is allowed to perform.
42. The network device according to claim 41, characterized in that, The feedback information is determined based on the first indication information and / or the subscription information of the first terminal device.
43. The network device according to claim 41 or 42, characterized in that, The network device is further configured to determine, based on one or more of the first indication information, subscription information, and feedback information, whether it is necessary to configure transcoding function for the first terminal device and / or modify the encoding type list in the first service establishment process during the first service process.
44. The network device according to any one of claims 36-43, characterized in that, The network device is also used to receive the first invitation information; The first invitation information is used by the first terminal device to request the second terminal device to perform the first service.
45. The network device according to claim 44, characterized in that, The first invitation information includes third instruction information, which includes one or more of the following: The encoding information used by the first terminal device to perform the first service; The first terminal device accesses and performs the first service through a non-terrestrial communication device. The type of non-terrestrial communication device used by the first terminal device to perform the first service.
46. The network device according to claim 45, characterized in that, The network device is also used to send a second invitation message; The second invitation information is used to request the second terminal device to perform the first service, and the second invitation information includes the encoding information used by the first service.
47. The network device according to claim 46, characterized in that, The second invitation information, including the encoding information used by the first terminal device for the first service, is determined based on one or more of the following: The first invitation information; The first indication information; The subscription information of the first terminal device.
48. The network device according to claim 47, characterized in that, The network device is further configured to, when the third indication information does not instruct the first terminal device to use the encoding information for the first service, add the encoding information for the first service to the second invitation information according to the first indication information and / or the subscription information.
49. The network device according to any one of claims 44-48, characterized in that, The encoding type used by the first terminal device to perform the first service is a first encoding type, and the second invitation information includes a first encoding type list. The first encoding type list includes a second encoding type, and the second encoding type is an encoding type other than the first encoding type.
50. The network device according to claim 49, characterized in that, The network device is also used to configure transcoding functions; The transcoding function is used for transcoding between the second encoding type and the first encoding type.
51. The network device according to any one of claims 36-43, characterized in that, The network device is also used to send third invitation information; The third invitation information is used by the third terminal device to request the first terminal device to perform the first service, and the third invitation information includes the encoding information used by the third terminal device to perform the first service.
52. The network device according to claim 51, characterized in that, The encoding type used by the third terminal device to perform the first service is a third encoding type, the third invitation information includes a second encoding type list, and the network device is further used to add a first encoding type to the second encoding type list when the first terminal device does not support the third encoding type; The first encoding type is the encoding type supported by the first terminal device.
53. The network device according to claim 51 or 52, characterized in that, The encoding type used by the third terminal device to perform the first service is a third encoding type. The third invitation information includes a second encoding type list. The network device is also used to delete some or all of the encoding types other than the third encoding type from the second encoding type list when the first terminal device supports the third encoding type.
54. The network device according to claim 52, characterized in that, The network device is also used to configure transcoding functionality to the second network device; The transcoding function is used for transcoding between the third encoding type and the first encoding type.
55. The network device according to claim 54, characterized in that, The second network device includes an access gateway.
56. The network device according to any one of claims 36-47, characterized in that, The first network device includes one or more of the following: P-CSCF, S-CSCF, AF.
57. The network device according to any one of claims 36-48, characterized in that, The first service includes one or more of the following: voice, voice, emergency services, video, and messaging services.
58. The network device according to any one of claims 36-57, characterized in that, The first wireless access type includes non-terrestrial communication.
59. A terminal device, characterized in that, The terminal device is a first terminal device, and the terminal device includes: The first transmitting unit is used to transmit the first indication information; The first indication information is sent during the registration process of the first terminal device, and the first indication information is used to indicate one or more of the following: The encoding information for the first terminal device to support the first service; Whether the first terminal device supports the ability to access the first service through non-terrestrial communication devices; The first terminal device accesses and performs the first service through the non-terrestrial communication equipment. The type of non-terrestrial communication equipment used by the first terminal device to perform the first service.
60. The terminal device according to claim 59, characterized in that, The encoded information includes one or more of the following: Encoding type, bit rate, frame format, transmission protocol, and service type of the first service.
61. The terminal device according to claim 59 or 60, characterized in that, The first indication information carries one or more of the following: One or more fields in the SIP registration message header; The SDP request in the SIP registration message.
62. The terminal device according to any one of claims 59-61, characterized in that, The type of non-terrestrial communication equipment used by the first terminal device to perform the first service corresponds to the encoding information that the first terminal device supports for performing the first service; and / or, When the first terminal device accesses the first service through the non-terrestrial communication device, the first terminal device uses specific encoding information.
63. The terminal device according to any one of claims 59-62, characterized in that, The terminal device is also used to receive feedback information; The feedback information is used to indicate one or more of the following: The first terminal device is allowed to access the encoded information used by the first service; Whether to allow the first terminal device to access and perform the first service through non-terrestrial communication equipment; The types of services that the first terminal device is allowed to perform.
64. The terminal device according to claim 63, characterized in that, The feedback information is determined based on the first indication information and / or the subscription information of the first terminal device.
65. The terminal device according to claim 63 or 64, characterized in that, The feedback information is used by the first network device to determine whether to configure transcoding function for the first terminal device during the first service.
66. The terminal device according to any one of claims 59-65, characterized in that, The terminal device is also used to send a first invitation message; The first invitation information is used by the first terminal device to invite the second terminal device to participate in the first service. The first invitation information includes third indication information, which includes one or more of the following: The encoding information used by the first terminal device to perform the first service; The first terminal device accesses and performs the first service through a non-terrestrial communication device. The type of non-terrestrial communication device used by the first terminal device to perform the first service.
67. The terminal device according to any one of claims 59-65, characterized in that, The terminal device is also used to receive third invitation information; The third invitation information is used by the third terminal device to invite the first terminal device to participate in the first service. The third invitation information includes the encoding information used by the third terminal device to perform the first service.
68. The terminal device according to claim 67, characterized in that, The encoding type used by the third terminal device to perform the first service is a third encoding type. The third invitation information includes a second encoding type list. If the first terminal device does not support the third encoding type, the second encoding type list includes a first encoding type, which is an encoding type supported by the first terminal device.
69. The terminal device according to any one of claims 59-68, characterized in that, The first network device includes one or more of the following: P-CSCF, S-CSCF, AF.
70. The terminal device according to any one of claims 59-69, characterized in that, The first service includes voice services.
71. A terminal device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or send signals so that the terminal device performs the method as described in any one of claims 24-35.
72. A network device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the network device performs the method as described in any one of claims 1-23.
73. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as described in any one of claims 1-35.
74. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1-35.
75. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-35.
76. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-35.
77. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-35.
