Terminal voice capability reporting method and device, electronic equipment and storage medium

Abstract

The invention discloses a terminal voice capability reporting method and device, electronic equipment and a storage medium. The method comprises the following steps: in a scene that a non-ground network Internet of Things terminal communicates with a satellite network, a target identification bit is added to a non-access stratum message, and the target identification bit is used for representing whether the terminal supports IP multimedia subsystem packet switching voice or not; and sending the non-access stratum message added with the target identification bit to a network side. The technical problem that the current communication standard cannot meet the requirement of the voice reporting capability of the terminal in a non-ground internet of things scene is solved.

Description

Technical Field

[0001] The present application relates to the field of satellite communication technology, and in particular to a method, device, electronic device and storage medium for reporting terminal voice capability. Background Art

[0002] IoT NTN (Internet of Things over Non-Terrestrial Networks) will initially focus on data services, and will subsequently support voice services. For IoT NTN to access satellite scenarios, the terminal needs to indicate its ability to access voice scenarios. However, the current communication standards cannot meet the needs of terminals reporting voice capabilities in non-terrestrial network IoT scenarios.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of the present application provide a method, device, electronic device and storage medium for reporting the voice capability of a terminal, so as to at least solve the technical problem that the current communication standards cannot meet the requirements for reporting the voice capability of the terminal in the non-terrestrial network Internet of Things scenario.

[0005] According to one aspect of an embodiment of the present application, a method for reporting terminal voice capabilities is provided, including: in a scenario where a non-terrestrial network Internet of Things terminal communicates with a satellite network, adding a target identification bit to a non-access layer message, wherein the target identification bit is used to characterize whether the terminal supports IP multimedia subsystem packet switched voice; and sending the non-access layer message to which the target identification bit is added to the network side.

[0006] Optionally, the non-access layer message includes: an attachment request, a tracking area update request; the target identification bit includes: a voice domain preference indicator bit; adding a target identification bit to the non-access layer message includes: adding a voice domain preference and usage setting information element in the attachment request or the tracking area update request, wherein the voice domain preference and usage setting information element includes: a user equipment usage setting indicator bit, a voice domain preference indicator bit, the user equipment usage setting indicator bit is used to characterize the behavior type corresponding to the terminal, and the behavior types include: voice call-centric and data transmission-centric, and the voice domain preference indicator bit is used to characterize the terminal's support for voice services in the evolved universal mobile communications system terrestrial radio access network, and the support status includes: supporting IP multimedia subsystem packet switched voice and not supporting IP multimedia subsystem packet switched voice.

[0007] Optionally, the user equipment usage setting indication bit or the voice domain preference indication bit only occupies one bit in the voice domain preference and usage setting information element.

[0008] Optionally, the position of the bits occupied by the user equipment usage setting indication bit in the voice domain preference and usage setting information element is consistent with the position of the user equipment usage setting indication bit in the voice domain preference and usage setting information element in a terrestrial network scenario.

[0009] Optionally, the target identification bit includes: a voice domain preference indication bit; adding a target identification bit to the non-access layer message also includes: rewriting the idle bits in the information element contained in the non-access layer message into the voice domain preference indication bit, wherein the information element includes at least one of the following: a user equipment network capability information element, and the voice domain preference indication bit is used to characterize the terminal's support for voice services in the evolved universal mobile communications system terrestrial radio access network, and the support status includes: supporting IP multimedia subsystem packet switched voice and not supporting IP multimedia subsystem packet switched voice.

[0010] Optionally, the target identification bit includes: a voice domain preference information element parameter; when the non-access layer message is an attachment request or a tracking area update request, adding a target identification bit to the non-access layer message also includes: adding a voice domain preference information element parameter to the attachment request or the tracking area update request, wherein the existence of the voice domain preference information element parameter is: optional or mandatory, and the format of the voice domain preference information element parameter includes: type-length-value TLV type, type-value TV type, and the voice domain preference information element parameter is used to characterize the terminal's support for voice services in the evolved universal mobile communications system terrestrial radio access network, and the support status includes: supporting IP multimedia subsystem packet switched voice and not supporting IP multimedia subsystem packet switched voice.

[0011] Optionally, adding a target identification bit to the non-access layer message also includes: adding a voice domain preference information element parameter to the attachment request or the tracking area update request, and deleting the spare supplementary bit in the attachment request or the tracking area update request, wherein the spare supplementary bit is a field reserved in the attachment request or the tracking area update request for extension or as a fill bit, the existence of the voice domain preference information element parameter is mandatory, and the format of the voice domain preference information element parameter is a value V type.

[0012] According to another aspect of an embodiment of the present application, a terminal voice capability reporting device is also provided, including: an identification adding module, used to add a target identification bit to a non-access layer message in a scenario where a non-ground network Internet of Things terminal communicates with a satellite network, wherein the target identification bit is used to characterize whether the terminal supports IP multimedia subsystem packet switched voice; a capability reporting module, used to send the non-access layer message after adding the target identification bit to the network side.

[0013] According to another aspect of the embodiments of the present application, there is also provided an electronic device, including: a memory and a processor, the processor being configured to run a program stored in the memory, wherein the terminal voice capability reporting method is executed when the program is run.

[0014] According to another aspect of the embodiments of the present application, a non-volatile storage medium is provided, the non-volatile storage medium includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the terminal voice capability reporting method by running the computer program.

[0015] According to another aspect of the embodiments of the present application, a computer program product is provided, including a computer program, which implements the steps of the terminal voice capability reporting method when the computer program is executed by a processor.

[0016] In an embodiment of the present application, in a scenario where a non-terrestrial network IoT terminal communicates with a satellite network, a target identification bit is added to a non-access layer message, wherein the target identification bit is used to characterize whether the terminal supports IP multimedia subsystem packet switching voice; the non-access layer message after the target identification bit is added is sent to the network side, and a parameter carrying a terminal voice capability identification based on terrestrial network optimization is added to the UE (User Equipment) reporting parameter of the IoT NTN, thereby achieving the purpose of ensuring the interaction between the terminal and the network capabilities and meeting the voice capability reporting requirements, thereby solving the technical problem that the current communication standards cannot meet the terminal reporting voice capability requirements in the non-terrestrial network IoT scenario. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0018] Figure 1 It is a hardware structure block diagram of a computer terminal (or electronic device) for implementing a method for reporting terminal voice capability according to an embodiment of the present application;

[0019] Figure 2 It is a schematic diagram of a method flow for reporting terminal voice capability according to an embodiment of the present application;

[0020] Figure 3 It is a structural diagram of a terminal voice capability reporting device provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0021] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0022] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0023] In the mobile communication technical specifications of the relevant technologies, there are the following provisions for the voice service preference settings of UE in different network environments:

[0024] If the UE supports CS (Circuit Switched) fallback, or the UE is configured to support IMS (IP Multimedia Subsystem) voice, or both, the UE shall include the information element "Voice domain preference and UE's usage setting" in the Attach Request, Tracking Area Update Request and Routing Area Update Request messages. The purpose of this information element is to signal to the network the UE's usage setting and the E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) voice domain preference. The UE's usage setting indicates whether the UE behaves in a voice-centric or data-centric manner. The E-UTRAN voice domain preference indicates whether the UE is configured for CS voice only, CS voice first and IMS PS voice as secondary, IMS PS (Packet Switched) voice first and CS voice as secondary, or IMS PS voice only.

[0025] In this version of the specification, interoperability with NB-IoT RAT (NarrowBand Internet of Things Radio Access Technology) is not supported, nor is GBR (Guaranteed Bit Rate) bearer supported in NB-IoT RAT. Therefore, when sending an Attach Request or Tracking Area Update Request on NB-IoT RAT, the UE shall not include the "Voice Domain Preference and UE Usage Settings" IE (Information Element).

[0026] The purpose of the voice domain preference and UE usage settings information element is to provide the network with the UE usage settings and the voice domain preference in broadband S1 mode. The network uses the UE usage settings and the E-UTRAN voice domain preference to select the RFSP (Radio Frequency Selection Policy) index.

[0027] The UE's usage setting bit indicates the value configured on the mobile equipment (ME), and the voice domain preference for E-UTRAN bit indicates the value of the E-UTRAN voice domain preference configured on the mobile equipment (ME). The encoding method of them in the information element is shown in Table 1 and Table 2 below:

[0028] Table 1

[0029]

[0030] As shown in Table 1, the overall structure of the information element, including its length and various fields, is shown. For the "Voice Domain Preference and UE Usage Settings" information element, it contains the following parts: Octet 1: Contains the identifier and length indication of the information element. Octet 2 and 3: Contains the specific values ​​of the UE usage settings and voice domain preference. The encoding details of each octet in the information element are shown in Table 2.

[0031] Table 2

[0032]

[0033] Among them, UE's usage setting occupies one bit, indicating the value configured on the mobile equipment (ME), indicating whether the UE is voice-centric or data-centric. Voice domain preference (Voice domain preference for E-UTRAN) occupies two bits and can have four combinations, representing different voice service preferences: CS voice only, CS voice priority and IMS PS voice as secondary, IMS PS voice priority and CS voice as secondary, and IMS PS voice only.

[0034] At present, based on the long-term development plan of telecom operators, IoT NTN initially focuses on data services, and will later support voice services. Among them, IoT NTN is based on the evolution of NB IoT, and in the future, based on the current development status of terrestrial networks, it will access EPC and IMS networks to support voice services.

[0035] In the related art, when the UE attaches or performs TAU (Tracking Area Update), the Voice domain preference and UE's usage setting parameters are not carried. However, for the IoT NTN access to satellite scenarios, the terminal needs to indicate its ability to access voice scenarios, mainly the ability to access the IMS network. In other words, the current technology does not match the technical requirements for the terminal to report voice capabilities in the IoT NTN support voice service scenario; and if it is to support voice, simply adding the voice domain preference and UE usage setting parameters in the NAS (Non-Access Stratum) message, although compared with the definition and standard planning of IoT NTN support for voice, the network tendency of the terminal to support voice can be reported, but it will cause signaling redundancy. However, since the existing parameter definition involves CSFB (Circuit Switched Fallback) and other values, as well as the limited air interface resources, the direct application of this parameter to IoT NTN will cause redundant transmission of air interface signaling, resulting in resource waste.

[0036] In order to solve the above problems, relevant solutions are provided in the embodiments of the present application, which are described in detail below.

[0037] According to an embodiment of the present application, an embodiment of a method for reporting terminal voice capabilities is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0038] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 The hardware structure block diagram of a computer terminal (or electronic device) for implementing the terminal voice capability reporting method is shown. Figure 1 As shown, the computer terminal 10 (or electronic device) may include one or more (102a, 102b, ..., 102n are used to illustrate) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0039] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10 (or electronic device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0040] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the terminal voice capability reporting method in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the above-mentioned terminal voice capability reporting method is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0041] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0042] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 (or electronic device).

[0043] In the above operating environment, the embodiment of the present application provides a method for reporting terminal voice capability. Figure 2 is a schematic diagram of a method flow for reporting terminal voice capability according to an embodiment of the present application, such as Figure 2 As shown, the method comprises the following steps:

[0044] Step S202, in a scenario where a non-terrestrial network IoT terminal communicates with a satellite network, adding a target identification bit to a non-access layer message, wherein the target identification bit is used to indicate whether the terminal supports IP multimedia subsystem packet switched voice;

[0045] Step S204: Send the non-access layer message with the target identification bit added to the network side.

[0046] Through the above steps, by adding parameters that carry the terminal voice capability identification based on ground network optimization to the UE reporting parameters of IoT NTN, the purpose of ensuring the interaction between terminal and network capabilities and meeting the voice capability reporting requirements is achieved, thereby solving the technical problem that the current communication standards cannot meet the terminal reporting voice capability requirements in non-ground network IoT scenarios.

[0047] The following further introduces the method for reporting the voice capability of the terminal in steps S202 to S204 of the embodiment of the present application.

[0048] In an embodiment of the present application, a voice capability parameter different from that on the ground can be added to the non-access layer message to indicate the IMS voice capability of the IoT-NTN terminal. For example, a newly defined identification bit can be added to the non-access layer message. The identification bit can be: a spare bit existing in other IEs, or implemented by defining a new parameter in an attachment request, etc. Various implementation methods are described in detail below.

[0049] Method 1

[0050] In some embodiments of the present application, a non-access layer message includes: an attachment request, a tracking area update request; a target identification bit includes: a voice domain preference indicator bit; adding a target identification bit to a non-access layer message includes the following steps: adding a voice domain preference and usage setting information element in an attachment request or a tracking area update request, wherein the voice domain preference and usage setting information element includes: a user equipment usage setting indicator bit, a voice domain preference indicator bit, the user equipment usage setting indicator bit is used to characterize the behavior type corresponding to the terminal, and the behavior types include: voice call-centric and data transmission-centric, and the voice domain preference indicator bit is used to characterize the terminal's support for voice services in the evolved universal mobile communications system terrestrial radio access network, and the support status includes: supporting IP multimedia subsystem packet switched voice and not supporting IP multimedia subsystem packet switched voice.

[0051] Specifically, when enhancing the parameters reported on the UE side, the terrestrial voice domain preference and usage setting (Voice domain preference and UE's usage setting) parameters can be referred to, and a voice domain preference and usage setting information element can be added to the non-access layer message of IoT NTN (taking the attachment request as an example). The specific parameters of the information element are shown in Tables 3 and 4 below.

[0052] Table 3

[0053]

[0054] Table 4

[0055]

[0056] It can be seen from Table 3 and Table 4 that in this embodiment, the voice domain preference and usage setting information element uses two bits, bit 1 and bit 2, to correspond to the voice domain preference indication bit (Voice domain preference for E-UTRAN) and the user equipment usage setting indication bit (UE's usage setting), that is, the user equipment usage setting indication bit or the voice domain preference indication bit only occupies one bit in the voice domain preference and usage setting information element.

[0057] Among them, when the voice domain preference indicator bit is 0, it represents that the terminal supports IP multimedia subsystem packet switched voice, and when the voice domain preference indicator bit is 1, it represents that the terminal does not support IP multimedia subsystem packet switched voice; when the user equipment usage setting indicator bit is 0, it represents that the terminal is centered on voice calls, and when the user equipment usage setting indicator bit is 1, it represents that the terminal is centered on data transmission.

[0058] Correspondingly, for the network side, it is also necessary to follow the ground technology so that the network can recognize the voice domain preference and usage setting information element added in the non-access layer message, and identify the voice capabilities supported by the UE based on the information element parameters. Specifically, the network side needs to align and identify the optimized parameters shown in Tables 3 and 4 above.

[0059] Method 2

[0060] A voice domain preference and usage setting information element is added to the non-access layer message of IoT NTN (taking the attachment request as an example). The specific parameters of the information element are shown in Tables 5 and 6 below.

[0061] Table 5

[0062]

[0063] Table 6

[0064]

[0065] It can be seen from Table 5 and Table 6 that in this embodiment, the voice domain preference and usage setting information element uses two bits, bit 1 and bit 3, to correspond to the voice domain preference indicator (Voice domain preference for E-UTRAN) and the user equipment usage setting indicator (UE's usage setting), respectively. Compared with method 1, the difference is that this embodiment does not change the location of the original UE's usage setting (as shown in Table 1), that is, the position of the bit occupied by the user equipment usage setting indicator in the voice domain preference and usage setting information element is consistent with the position of the user equipment usage setting indicator in the voice domain preference and usage setting information element in the terrestrial network scenario. For the terrestrial network parameters, the change is small.

[0066] The meanings corresponding to the different settings of the voice domain preference indicator and the user equipment usage setting indicator, as well as the adaptive adjustment on the network side, are the same as those described in the above method 1 and will not be repeated here.

[0067] In addition, it should be noted that the embodiment of the present application does not limit the position of the voice domain preference indicator bit in the voice domain preference and usage setting information element. For example, it can also be at the position of octet3 bit2.

[0068] Method 3

[0069] In some embodiments of the present application, the target identification bit includes: a voice domain preference indicator bit; adding a target identification bit to the non-access layer message also includes the following steps: rewriting the idle bits in the information element contained in the non-access layer message into the voice domain preference indicator bit, wherein the information element includes at least one of the following: a user equipment network capability information element, and the voice domain preference indicator bit is used to characterize the terminal's support for voice services in the evolved universal mobile communications system terrestrial radio access network, and the support status includes: supporting IP multimedia subsystem packet switched voice and not supporting IP multimedia subsystem packet switched voice.

[0070] Specifically, the voice domain preference indication bit can be set in the spare bit of any information element containing spare bits (spare) in the non-intervention layer message. The embodiment of the present application is not limited to this. For example, there are multiple spare bits in a NAS parameter such as UE networkcapability IE (user equipment network capability information element). For IoT NTN, the voice domain preference indication bit can be added to the position of spare=0 in the information element.

[0071] The meanings corresponding to the different setting values ​​of the voice domain preference indicator can be referred to the description in the above-mentioned method 1, and will not be repeated here.

[0072] Method 4

[0073] In the embodiment of the present application, in order to enable the terminal to report voice capabilities, a method of adding new parameters in the NAS message can also be adopted. The specific steps are as follows.

[0074] In some embodiments of the present application, the target identification bit includes: a voice domain preference information element parameter; when the non-access layer message is an attachment request or a tracking area update request, adding a target identification bit to the non-access layer message also includes the following steps: adding a voice domain preference information element parameter to the attachment request or the tracking area update request, wherein the existence of the voice domain preference information element parameter is: optional or mandatory, and the format of the voice domain preference information element parameter includes: type-length-value TLV type, type-value TV type, and the voice domain preference information element parameter is used to characterize the terminal's support for voice services in the evolved universal mobile communications system terrestrial radio access network, and the support status includes: supporting IP multimedia subsystem packet switched voice and not supporting IP multimedia subsystem packet switched voice.

[0075] In some embodiments of the present application, adding a target identification bit to a non-access layer message also includes the following steps: adding a voice domain preference information element parameter to an attachment request or a tracking area update request, and deleting a spare supplementary bit in the attachment request or the tracking area update request, wherein the spare supplementary bit is a field reserved in the attachment request or the tracking area update request for extension or as a fill bit, the existence of the voice domain preference information element parameter is mandatory, and the format of the voice domain preference information element parameter is a value V type.

[0076] The following takes adding a voice domain preference information element parameter to an attach request / reply message as an example for explanation.

[0077] Example 1

[0078] Add a voice domain preference information element parameter and set the presence of the parameter to mandatory (M). The format is TLV (corresponding Length is 3) or TV (corresponding Length is 2), as shown in Table 7 below.

[0079] Table 7

[0080]

[0081] Example 2

[0082] Add a voice domain preference information element parameter and set the presence of the parameter to optional (O). The format is TLV (corresponding Length is 3) or TV (corresponding Length is 2), as shown in Table 8 below.

[0083] Table 8

[0084]

[0085] Example 3

[0086] Add a voice domain preference information element parameter, and set the existence of the parameter to mandatory, with a format of V, and delete the supplementary byte bit (ie, spare supplementary bit, Spare half octet), as shown in Table 9 below.

[0087] Table 9

[0088]

[0089] For the method of adding voice domain preference information element parameters to other non-intervention layer messages, reference may be made to the method in the above example, which will not be repeated here.

[0090] This application solution solves the problem of the terminal reporting voice capabilities when implementing voice in IoT NTN, which helps the network understand the capabilities of the terminal to decide whether to establish or reject the terminal's voice request, thereby meeting the front-end network construction needs of telecom operators; it optimizes the parameters carried by the ground network, so that the parameters in the IoT NTN scenario are streamlined, which is conducive to saving satellite air interface resources while ensuring the interaction between terminal and network capabilities, and improving network interaction capabilities and efficiency.

[0091] According to an embodiment of the present application, an embodiment of a terminal voice capability reporting device is also provided. Figure 3 1 is a schematic diagram of the structure of a terminal voice capability reporting device provided according to an embodiment of the present application. Figure 3 As shown, the device comprises:

[0092] The identification adding module 30 is used to add a target identification bit to the non-access layer message in the scenario where the non-terrestrial network Internet of Things terminal communicates with the satellite network, wherein the target identification bit is used to indicate whether the terminal supports IP multimedia subsystem packet switched voice;

[0093] The capability reporting module 32 is used to send the non-access layer message with the target identification bit added to the network side.

[0094] Optionally, the non-access layer message includes: an attachment request, a tracking area update request; the target identification bit includes: a voice domain preference indicator bit; adding a target identification bit to the non-access layer message includes: adding a voice domain preference and usage setting information element in the attachment request or the tracking area update request, wherein the voice domain preference and usage setting information element includes: a user equipment usage setting indicator bit, a voice domain preference indicator bit, the user equipment usage setting indicator bit is used to characterize the behavior type corresponding to the terminal, and the behavior types include: voice call-centric and data transmission-centric, and the voice domain preference indicator bit is used to characterize the terminal's support for voice services in the evolved universal mobile communications system terrestrial radio access network, and the support status includes: supporting IP multimedia subsystem packet switched voice and not supporting IP multimedia subsystem packet switched voice.

[0095] Optionally, the user equipment usage setting indication bit or the voice domain preference indication bit only occupies one bit in the voice domain preference and usage setting information element.

[0096] Optionally, the position of the bits occupied by the user equipment usage setting indication bit in the voice domain preference and usage setting information element is consistent with the position of the user equipment usage setting indication bit in the voice domain preference and usage setting information element in a terrestrial network scenario.

[0097] Optionally, the target identification bit includes: a voice domain preference indication bit; adding a target identification bit to the non-access layer message also includes: rewriting the idle bits in the information element contained in the non-access layer message into the voice domain preference indication bit, wherein the information element includes at least one of the following: a user equipment network capability information element, and the voice domain preference indication bit is used to characterize the terminal's support for voice services in the evolved universal mobile communications system terrestrial radio access network, and the support status includes: supporting IP multimedia subsystem packet switched voice and not supporting IP multimedia subsystem packet switched voice.

[0098] Optionally, the target identification bit includes: a voice domain preference information element parameter; when the non-access layer message is an attachment request or a tracking area update request, adding a target identification bit to the non-access layer message also includes: adding a voice domain preference information element parameter to the attachment request or the tracking area update request, wherein the existence of the voice domain preference information element parameter is: optional or mandatory, and the format of the voice domain preference information element parameter includes: type-length-value TLV type, type-value TV type, and the voice domain preference information element parameter is used to characterize the terminal's support for voice services in the evolved universal mobile communications system terrestrial radio access network, and the support status includes: supporting IP multimedia subsystem packet switched voice and not supporting IP multimedia subsystem packet switched voice.

[0099] Optionally, adding a target identification bit to the non-access layer message also includes: adding a voice domain preference information element parameter to the attachment request or the tracking area update request, and deleting the spare supplementary bit in the attachment request or the tracking area update request, wherein the spare supplementary bit is a field reserved in the attachment request or the tracking area update request for extension or as a fill bit, the existence of the voice domain preference information element parameter is mandatory, and the format of the voice domain preference information element parameter is a value V type.

[0100] It should be noted that the various modules in the above-mentioned terminal voice capability reporting device can be program modules (for example, a set of program instructions that implement a certain specific function) or hardware modules. For the latter, it can be expressed in the following forms, but is not limited to this: the expression form of each of the above-mentioned modules is a processor, or the functions of each of the above-mentioned modules are implemented by a processor.

[0101] It should be noted that the terminal voice capability reporting device provided in this embodiment can be used to perform Figure 2 The terminal voice capability reporting method shown, therefore, the relevant explanations and instructions on the above-mentioned terminal voice capability reporting method are also applicable to the embodiments of the present application and will not be repeated here.

[0102] An embodiment of the present application also provides a non-volatile storage medium, the non-volatile storage medium includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the following terminal voice capability reporting method by running the computer program: in a scenario where a non-ground network Internet of Things terminal communicates with a satellite network, a target identification bit is added to a non-access layer message, wherein the target identification bit is used to indicate whether the terminal supports IP multimedia subsystem packet switching voice; and the non-access layer message after the target identification bit is added is sent to the network side.

[0103] An embodiment of the present application also provides a computer program product, including a computer program. When the computer program is executed by a processor, it implements the steps of the terminal voice capability reporting method described in each embodiment of the present application: in a scenario where a non-ground network Internet of Things terminal communicates with a satellite network, a target identification bit is added to a non-access layer message, wherein the target identification bit is used to indicate whether the terminal supports IP multimedia subsystem packet switching voice; and the non-access layer message after the target identification bit is added is sent to the network side.

[0104] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0105] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

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

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

[0108] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0109] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0110] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for reporting terminal voice capability, characterized in that: include: In a scenario where a non-terrestrial network IoT terminal communicates with a satellite network, a target identification bit is added to a non-access layer message, wherein the target identification bit is used to indicate whether the terminal supports IP multimedia subsystem packet switched voice; The non-access layer message after adding the target identification bit is sent to the network side.

2. The method for reporting terminal voice capability according to claim 1, characterized in that: The non-access layer message includes: an attach request and a tracking area update request; the target identification bit includes: a voice domain preference indication bit; Adding a target identification bit to the non-access stratum message includes: A voice domain preference and usage setting information element is added to the attachment request or the tracking area update request, wherein the voice domain preference and usage setting information element includes: a user equipment usage setting indicator bit and the voice domain preference indicator bit, the user equipment usage setting indicator bit is used to characterize the behavior type corresponding to the terminal, and the behavior type includes: voice call-centric and data transmission-centric, the voice domain preference indicator bit is used to characterize the support of the terminal for voice services in the evolved universal mobile communications system terrestrial radio access network, and the support status includes: supporting IP multimedia subsystem packet switched voice and not supporting IP multimedia subsystem packet switched voice.

3. The method for reporting terminal voice capability according to claim 2, characterized in that: The user equipment usage setting indication bit or the voice domain preference indication bit only occupies one bit in the voice domain preference and usage setting information element.

4. The method for reporting terminal voice capability according to claim 3, characterized in that: The position of the bit occupied by the user equipment usage setting indication bit in the voice domain preference and usage setting information element is consistent with the position of the user equipment usage setting indication bit in the voice domain preference and usage setting information element in the terrestrial network scenario.

5. The method for reporting terminal voice capability according to claim 1, characterized in that: The target identification bit includes: a voice domain preference indication bit; adding a target identification bit to the non-access layer message also includes: Rewrite the idle bits in the information element included in the non-access layer message into the voice domain preference indicator bit, wherein the information element includes at least one of the following: a user equipment network capability information element, and the voice domain preference indicator bit is used to characterize the support status of the terminal for the voice service in the evolved universal mobile communications system terrestrial radio access network, and the support status includes: supporting IP multimedia subsystem packet switched voice and not supporting IP multimedia subsystem packet switched voice.

6. The method for reporting terminal voice capability according to claim 1, characterized in that: The target identification bit includes: a voice domain preference information element parameter; when the non-access layer message is an attachment request or a tracking area update request, adding a target identification bit to the non-access layer message also includes: Add the voice domain preference information element parameter to the attachment request or the tracking area update request, wherein the existence of the voice domain preference information element parameter is: optional or mandatory, and the format of the voice domain preference information element parameter includes: type-length-value TLV type, type-value TV type, and the voice domain preference information element parameter is used to characterize the support of the terminal for the voice service in the evolved universal mobile communications system terrestrial radio access network, and the support status includes: supporting IP multimedia subsystem packet switched voice and not supporting IP multimedia subsystem packet switched voice.

7. The method for reporting terminal voice capability according to claim 6, characterized in that: Adding a target identification bit to the non-access layer message also includes: Add the voice domain preference information element parameter to the attachment request or the tracking area update request, and delete the spare supplementary bit in the attachment request or the tracking area update request, wherein the spare supplementary bit is a field reserved in the attachment request or the tracking area update request for extension or as a fill bit, the existence of the voice domain preference information element parameter is mandatory, and the format of the voice domain preference information element parameter is value V type.

8. A terminal voice capability reporting device, characterized in that: include: An identification adding module is used to add a target identification bit to a non-access layer message in a scenario where a non-terrestrial network IoT terminal communicates with a satellite network, wherein the target identification bit is used to indicate whether the terminal supports IP multimedia subsystem packet switched voice; The capability reporting module is used to send the non-access layer message after adding the target identification bit to the network side.

9. An electronic device, characterized in that: include: A memory and a processor, wherein the processor is used to run a program stored in the memory, wherein the terminal voice capability reporting method described in any one of claims 1 to 7 is executed when the program is running.

10. A non-volatile storage medium, characterized in that: The non-volatile storage medium includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the terminal voice capability reporting method according to any one of claims 1 to 7 by running the computer program.

11. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the terminal voice capability reporting method described in any one of claims 1 to 7 are implemented.

Images