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

Abstract

The application discloses a terminal voice capability reporting method and device, electronic equipment and a storage medium. Wherein, the method comprises: in the scene that the non-ground network Internet of Things terminal and the satellite network communicate, adding a target identification bit to the non-access layer message, wherein the target identification bit is used to represent whether the terminal supports IP multimedia subsystem packet switching voice; the non-access layer message after adding the target identification bit is sent to the network side. The application solves the technical problem that the current communication standard cannot meet the demand of terminal voice capability reporting in the non-ground network Internet of Things scene.

Description

TECHNICAL FIELD

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

[0002] IoT NTN (Internet of Things over Non-Terrestrial Networks) is initially mainly for data services, and later supports voice services. For IoT NTN access satellite scenarios, the terminal needs to indicate its voice scenario access capability. However, the current communication standard cannot meet the needs of the terminal reporting voice capability in the IoT NTN scenario.

[0003] At present, there is no effective solution to the above problems. SUMMARY

[0004] The embodiments of the present application provide a terminal voice capability reporting method and device, electronic equipment and storage medium, to at least solve the technical problem that the current communication standard cannot meet the needs of the terminal reporting voice capability in the IoT NTN scenario.

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

[0006] Optionally, the non-access layer message comprises an attachment request or a tracking area update request; the target identification bit comprises a voice domain preference indication bit; adding the target identification bit to the non-access layer message comprises adding a voice domain preference and use setting information element to the attachment request or the tracking area update request, wherein the voice domain preference and use setting information element comprises a user equipment use setting indication bit and a voice domain preference indication bit, the user equipment use setting indication bit is used to represent a behavior mode type corresponding to the terminal, the behavior mode type comprises a voice call center and a data transmission center, and the voice domain preference indication bit is used to represent a support condition of the terminal for voice services in an evolved universal mobile communication system terrestrial wireless access network, the support condition comprises support for IP multimedia subsystem packet switching voice and no support for IP multimedia subsystem packet switching voice.

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

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

[0009] Optionally, the target identification bit includes a voice domain preference indication bit; and the adding of the target identification bit into the non-access stratum message further includes: rewriting a free bit in an information element included in the non-access stratum message as 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 represent a support condition of the terminal for a voice service in an evolved universal mobile telecommunications system terrestrial radio access network, and the support condition includes: support of IP multimedia subsystem packet switched voice and no support of IP multimedia subsystem packet switched voice.

[0010] Optionally, the target identification bit includes a voice domain preference information element parameter; and the adding of the target identification bit into the non-access stratum message further includes: adding the voice domain preference information element parameter into the attach request or the tracking area update request, wherein the voice domain preference information element parameter is optional or mandatory in terms of existence, a format of the voice domain preference information element parameter includes a type-length-value (TLV) type and a type-value (TV) type, and the voice domain preference information element parameter is used to represent a support condition of the terminal for a voice service in an evolved universal mobile telecommunications system terrestrial radio access network, and the support condition includes: support of IP multimedia subsystem packet switched voice and no support of IP multimedia subsystem packet switched voice.

[0011] Optionally, the adding of the target identification bit into the non-access stratum message further includes: adding the voice domain preference information element parameter into the attach request or the tracking area update request, and deleting a spare supplemental bit in the attach request or the tracking area update request, wherein the spare supplemental bit is a field reserved in the attach request or the tracking area update request for extension or as a padding bit, the voice domain preference information element parameter is mandatory in terms of existence, and a format of the voice domain preference information element parameter is a value (V) type.

[0012] According to another aspect of the embodiments of the present application, a terminal voice capability reporting apparatus is further provided, which includes: an identification adding module, configured to add a target identification bit into a non-access stratum message in a scenario in which a non-terrestrial network Internet of Things terminal communicates with a satellite network, wherein the target identification bit is used to represent whether the terminal supports IP multimedia subsystem packet switched voice; and a capability reporting module, configured to send the non-access stratum message after the target identification bit is added to a network side.

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

[0014] According to a further aspect of the embodiments of the present application, a non-volatile storage medium is also provided, comprising a stored computer program, wherein a device in which the non-volatile storage medium is located performs the terminal voice capability reporting method by executing the computer program.

[0015] According to a further aspect of the embodiments of the present application, a computer program product is also provided, comprising a computer program, the computer program being configured to perform the steps of the terminal voice capability reporting method when executed by a processor.

[0016] In the embodiments of the present application, in the scenario of communication between a non-terrestrial network Internet of Things terminal and a satellite network, a target identification bit is added to a non-access layer message, wherein the target identification bit is used to represent whether the terminal supports IP multimedia subsystem packet switching voice; the non-access layer message after adding the target identification bit is sent to the network side, thereby increasing a parameter carrying an identification terminal voice capability based on ground network optimization in the UE (User Equipment, user equipment) reporting parameter of IoT NTN, so as to achieve the purpose of guaranteeing the interaction of terminal and network capability and meeting the voice capability reporting demand, thereby solving the technical problem that the current communication standard cannot meet the terminal voice capability reporting demand in the non-terrestrial network Internet of Things scenario. BRIEF DESCRIPTION OF DRAWINGS

[0017] The accompanying drawings, which are included to provide a further understanding of the present application, constitute a part of the present application and illustrate the illustrative embodiments of the present application and their description serve to explain the present application, but do not constitute improper limitations on the present application. In the drawings:

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

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

[0020] Figure 3 is a structural schematic diagram of a terminal voice capability reporting device according to the embodiments of the present application. DETAILED DESCRIPTION

[0021] In the following, the technical solutions in the embodiments of the present application will be described clearly and completely in conjunction with the drawings in the embodiments of the present application, so that those skilled in the art can better understand the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work should belong to the protection scope of the present application.

[0022] It should be noted that the terms "first", "second", and the like in the specification and claims of the present application and the above-described drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or a chronological sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but can include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0023] In the related art mobile communication technical specification, for the voice service preference setting of UE in different network environment, there are the following provisions:

[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 the UE's usage setting and the E-UTRAN's (Evolved UMTS Terrestrial Radio Access Network) voice domain preference to the network. The UE's usage setting indicates whether the UE is voice centric or data centric in its behavior. The E-UTRAN's voice domain preference indicates whether the UE is configured for CS voice only, CS voice preferred and IMS PS (Packet Switched) voice as secondary, IMS PS voice preferred and CS voice as secondary, or IMS PS voice only.

[0025] In this version of the specification, interworking with NB-IoT RAT (NarrowBand Internet of Things Radio Access Technology) is not supported, nor are GBR (Guaranteed Bit Rate) bearers in NB-IoT RAT. Therefore, the UE shall not include the "Voice domain preference and UE's usage setting" IE (Information Element) when sending an Attach Request or Tracking Area Update Request on NB-IoT RAT.

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

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

[0028] Table 1

[0029]

[0030] As shown in Table 1, the overall structure of the information element is shown, including the length and various fields. For the "Voice domain preference and UE's usage setting" information element, it contains the following parts: Octet 1: contains the identifier and length indication of the information element. Octet 2 and 3: contain the specific values of the UE's usage setting and voice domain preference. The encoding details of each byte (octet) in the information element are shown in Table 2.

[0031] Table 2

[0032]

[0033] The 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 behavior. The voice domain preference for E-UTRAN occupies two bits, which can have four combinations, representing different voice service preferences: CS voice only, CS voice preferred and IMS PS voice as secondary, IMS PS voice preferred and CS voice as secondary, and IMS PS voice only.

[0034] Currently, based on the long-term development plan of the telecommunications operator, the IoT NTN is initially mainly for data services, and will subsequently support voice services. The IoT NTN is based on the evolution of NB IoT, and in the future, based on the current development status of the ground network, it will access the EPC and IMS network to support voice services for the IoT NTN.

[0035] In the related art, when the UE performs attachment or TAU (Tracking Area Update), the Voice domain preference and UE's usage setting parameter is not carried, but for the IoT NTN access satellite scenario, the terminal needs to indicate its capability of accessing the voice scenario, mainly the capability of accessing the IMS network. That is, the current technology does not match the technical requirements of the terminal reporting voice capability in the IoT NTN supporting voice service scenario; and if the voice is supported, simply increasing the Voice domain preference and UE's usage setting parameter in the NAS (Non-Access Stratum) message will cause signaling redundancy, but due to the existing parameter definition involving CSFB (Circuit Switched Fallback) value and limited air interface resources, directly applying this parameter to the IoT NTN will cause redundant transmission of air interface signaling and waste of resources.

[0036] To solve the above problems, the related solutions are provided in the embodiments of the present application, which are described in detail below.

[0037] According to the embodiments of the present application, a terminal voice capability reporting method embodiment 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 the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order from that shown here.

[0038] The method embodiment provided by the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 A hardware structure block diagram of a computer terminal (or electronic equipment) for implementing the terminal voice capability reporting method is shown. As shown in Figure 1 The computer terminal 10 (or electronic equipment) can include one or more processors 102 (the processor 102 can include but is not limited to a microprocessor MCU or a programmable logic device FPGA processing device), a memory 104 for storing data, and a transmission device 106 for communication function. In addition, it can also include a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which can be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. Those skilled in the art can understand that the computer terminal 10 (or electronic equipment) can further include other components necessary for the computer terminal 10 (or electronic equipment) to perform the terminal voice capability reporting method.Figure 1 The illustrated configurations are merely exemplary and are not intended to limit the scope of the electronic device described above. For example, the computer terminal 10 can include more or fewer components than shown, or have a different configuration of components than shown. Figure 1 Figure 1

[0039] It should be noted that the one or more processors 102 and / or other data processing circuitry described above can be referred to herein generally as "data processing circuitry". The data processing circuitry can be embodied in whole or in part as software, hardware, firmware, or any combination thereof. In addition, the data processing circuitry can be a single standalone processing module, or incorporated in whole or in part within any one of the other elements of the computer terminal 10 (or electronic device). As referred to in embodiments of the present application, the data processing circuitry functions as a processor to control, for example, selection of the variable resistance terminal path connected to the interface.

[0040] The memory 104 can be used to store software programs of application software and modules, such as program instructions / data storage means corresponding to the terminal voice capability reporting method of embodiments 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, i.e. implements the terminal voice capability reporting method described above. The memory 104 can include a high-speed random access memory, and can further include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 can further include a memory disposed remotely with respect to the processor 102, which can be connected to the computer terminal 10 through a network. Examples of the 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 configured to receive or send data via a network. Examples of the network can include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a network interface controller (NIC) that can be connected to other network devices through a base station to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module configured to communicate with the Internet in a wireless manner.

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

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

[0044] Step S202, in the scenario of the non-terrestrial network Internet of Things terminal and satellite network communication, adding a target identification bit in the non-access layer message, wherein the target identification bit is used to represent whether the terminal supports IP multimedia subsystem packet switched voice;

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

[0046] Through the above steps, by increasing the parameter for carrying the identification terminal voice capability based on the ground network optimization in the UE reporting parameter of the IoT NTN, the interaction of the terminal and the network capability is guaranteed, the voice capability reporting demand is met, and the technical problem that the current communication standard cannot meet the terminal voice capability reporting demand in the non-terrestrial network Internet of Things scenario is solved.

[0047] The terminal voice capability reporting method in steps S202 to S204 of the embodiment of the present application is further introduced below.

[0048] The embodiment of the present application can increase a voice capability parameter different from the ground in the non-access layer message, which is used to represent the IMS voice capability of the IoT-NTN terminal. For example, a newly defined identification bit can be added in the non-access layer message, which can be: a spare bit existing in other IEs, or realized by defining a new parameter in the attachment request, and the various implementation manners are specifically described below.

[0049] Method one

[0050] In some embodiments of the present application, the non-access layer message comprises: an attachment request, a tracking area update request; the target identification bit comprises: a voice domain preference indication bit; adding a target identification bit in the non-access layer message comprises the following steps: adding a voice domain preference and use setting information element in the attachment request or the tracking area update request, wherein the voice domain preference and use setting information element contains: a user equipment use setting indication bit and a voice domain preference indication bit, the user equipment use setting indication bit is used to represent the behavior mode type corresponding to the terminal, the behavior mode type comprises: voice call center and data transmission center, the voice domain preference indication bit is used to represent the support situation of the terminal for the voice service in the evolved universal mobile communication system terrestrial wireless access network, the support situation comprises: supporting IP multimedia subsystem packet switched voice and not supporting IP multimedia subsystem packet switched voice.​

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

[0052] Table 3

[0053]

[0054] Table 4

[0055]

[0056] As can be seen from Table 3 and Table 4, in the embodiment, the voice domain preference and UE's usage setting information element uses two bit positions of bit1 and bit2 to respectively correspond to the voice domain preference indication bit (Voice domain preference for E-UTRAN) and the UE's usage setting indication bit (UE's usage setting), that is, the UE's usage setting indication bit or the voice domain preference indication bit only occupies one bit position in the voice domain preference and UE's usage setting information element.

[0057] Among them, in the case of the voice domain preference indication bit being 0, it represents that the terminal supports IP multimedia subsystem packet switched voice, and in the case of the voice domain preference indication bit being 1, it represents that the terminal does not support IP multimedia subsystem packet switched voice; in the case of the UE's usage setting indication bit being 0, it represents that the terminal is voice call centered, and in the case of the UE's usage setting indication bit being 1, it represents that the terminal is data transmission centered.

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

[0059] Method two

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

[0061] Table 5

[0062]

[0063] Table 6

[0064]

[0065] From Table 5 and Table 6, in the embodiment, the voice domain preference and usage setting information element uses two bit positions, bit1 and bit3, to correspond to the voice domain preference indication bit (Voice domain preference for E-UTRAN) and the UE's usage setting indication bit respectively, and the difference from the first mode is that the embodiment does not change the original position of the UE's usage setting (as shown in Table 1), that is, the position of the bit position occupied by the UE's usage setting indication bit in the voice domain preference and usage setting information element is consistent with the position of the UE's usage setting indication bit in the voice domain preference and usage setting information element in the ground network scenario, and the change for the ground network parameters is small.

[0066] The meanings corresponding to the different positions of the voice domain preference indication bit and the UE's usage setting indication bit, and the adaptive adjustment of the network side are the same as described in the first mode, and will not be described 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 indication bit in the voice domain preference and usage setting information element, for example, it can also be in the position of octet3 bit2.

[0068] Mode three

[0069] In some embodiments of the present application, the target identification bit includes a voice domain preference indication bit, and adding a target identification bit to the non-access layer message further includes the following steps: rewriting a spare bit in an information element contained in the non-access layer message as the voice domain preference indication bit, wherein the information element includes at least one of the following: a user equipment network capability information element, the voice domain preference indication bit is used to represent the support of the terminal for the voice service in the evolved universal mobile communication system terrestrial wireless access network, and the support includes: supporting IP multimedia subsystem packet switched voice, 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 a spare bit in the non-access layer message, and the embodiment of the present application does not limit this, for example, there are multiple spare bits in the UE network capability IE (user equipment network capability information element), and for the IoT NTN, the voice domain preference indication bit can be added to the position of spare=0 in the information element.

[0071] The different setting values of the voice domain preference indication bit correspond to the meanings described in the manner one, which will not be repeated here.

[0072] Manner four

[0073] In the embodiments of the present application, to realize the terminal reporting voice capability, the manner of adding a new parameter in the NAS message can also be used, and 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, and in the case that 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 further includes the following steps: adding a voice domain preference information element parameter to the attachment request or the tracking area update request, wherein the presence of the voice domain preference information element parameter is optional or mandatory, the format of the voice domain preference information element parameter includes a type-length-value (TLV) type and a type-value (TV) type, the voice domain preference information element parameter is used to represent the support of the terminal for voice service in the evolved universal mobile communication system terrestrial wireless access network, and the support 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 the non-access layer message further includes the following steps: adding a voice domain preference information element parameter to the attachment request or the tracking area update request, and deleting a backup supplemental bit in the attachment request or the tracking area update request, wherein the backup supplemental bit is a field reserved in the attachment request or the tracking area update request for extension or as a padding bit, the presence 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 the attachment request / reply message as an example for illustration.

[0077] Example one

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

[0079] Table 7

[0080]

[0081] Example two

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

[0083] Table 8

[0084]

[0085] Example Three

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

[0087] Table 9

[0088]

[0089] For the manner of adding the voice domain preference information element parameter to other non-access stratum messages, reference can be made to the manners in the above examples, which will not be described herein again.

[0090] The scheme solves the problem of terminal voice capability reporting when an IoT NTN implements voice, which helps the network to understand the capability of the terminal to decide to establish or reject the voice request of the terminal, thereby meeting the front-end network construction needs of a telecom operator; based on ground network carrying parameters, the parameters in the IoT NTN scenario are optimized, which is beneficial to saving satellite air interface resources while guaranteeing the interaction of terminal and network capability, and improving network interaction capability and efficiency.

[0091] According to the embodiments of the present application, an embodiment of a terminal voice capability reporting device is also provided. Figure 3 is a structural schematic diagram of a terminal voice capability reporting device provided by the embodiments of the present application. As shown in Figure 3 The device comprises:

[0092] An identity adding module 30 is configured to add a target identity bit to a non-access stratum message in a scenario in which a non-terrestrial network Internet of Things terminal communicates with a satellite network, wherein the target identity bit is used to represent whether the terminal supports IP multimedia subsystem packet switched voice.

[0093] A capability reporting module 32 is configured to send the non-access stratum message after adding the target identity bit to a network side.

[0094] Optionally, the non-access stratum message comprises: an attach request, a tracking area update request; the target identity bit comprises: a voice domain preference indication bit; adding one target identity bit into the non-access stratum message comprises: adding the voice domain preference and usage setting information element into the attach request or the tracking area update request, wherein the voice domain preference and usage setting information element comprises: a user equipment usage setting indication bit and a voice domain preference indication bit, the user equipment usage setting indication bit is used to represent a behavior mode type corresponding to the terminal, the behavior mode type comprises: a voice call center mode and a data transmission center mode, the voice domain preference indication bit is used to represent a support condition of the terminal for a voice service in an evolved universal mobile telecommunications system terrestrial radio access network, and the support condition comprises: 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, a 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 a position of the user equipment usage setting indication bit in a voice domain preference and usage setting information element in a ground network scenario.

[0097] Optionally, the target identity bit comprises: a voice domain preference indication bit; adding one target identity bit into the non-access stratum message further comprises: rewriting an idle bit in an information element contained in the non-access stratum message into the voice domain preference indication bit, wherein the information element comprises at least one of the following: a user equipment network capability information element, and the voice domain preference indication bit is used to represent a support condition of the terminal for a voice service in an evolved universal mobile telecommunications system terrestrial radio access network, and the support condition comprises: supporting IP multimedia subsystem packet switched voice and not supporting IP multimedia subsystem packet switched voice.

[0098] Optionally, the target identity bit comprises: a voice domain preference information element parameter; in a case where the non-access stratum message is an attach request or a tracking area update request, adding one target identity bit into the non-access stratum message further comprises: adding the voice domain preference information element parameter into the attach request or the tracking area update request, wherein the voice domain preference information element parameter is optional or mandatory in existence, a format of the voice domain preference information element parameter comprises: a type-length-value (TLV) type and a type-value (TV) type, and the voice domain preference information element parameter is used to represent a support condition of the terminal for a voice service in an evolved universal mobile telecommunications system terrestrial radio access network, and the support condition comprises: supporting IP multimedia subsystem packet switched voice and not supporting IP multimedia subsystem packet switched voice.

[0099] Optionally, adding a target identification bit into the non-access layer message further includes adding a voice domain preference information element parameter into the attach request or the tracking area update request, and deleting a spare supplemental bit in the attach request or the tracking area update request, wherein the spare supplemental bit is a field reserved in the attach request or the tracking area update request for extension or as a padding bit, the voice domain preference information element parameter is mandatory in terms of presence, and the format of the voice domain preference information element parameter is value V type.

[0100] It should be noted that each module in the terminal voice capability reporting apparatus described above can be a program module (for example, a program instruction set for implementing a certain specific function) or a hardware module. For the latter, it can be in the following forms, but is not limited thereto: the forms of each module described above are a processor, or the functions of each module described above are implemented by a processor.

[0101] It should be noted that the terminal voice capability reporting apparatus provided in the embodiment can be used to execute the terminal voice capability reporting method shown in the embodiment. Figure 2 Therefore, the related explanations and descriptions of the terminal voice capability reporting method described above are also applicable to the embodiments of the present application, and will not be described here again.

[0102] The embodiments of the present application further provide a non-volatile storage medium, which includes a stored computer program. A device in which the non-volatile storage medium is located executes the following terminal voice capability reporting method by running the computer program: in a scenario in which a non-terrestrial network Internet of Things terminal communicates with a satellite network, adding a target identification bit into a non-access layer message, wherein the target identification bit is used to represent whether the terminal supports IP multimedia subsystem packet switched voice; and sending the non-access layer message after the target identification bit is added to a network side.

[0103] The embodiments of the present application further provide a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps of the terminal voice capability reporting method described in various embodiments of the present application are implemented: in a scenario in which a non-terrestrial network Internet of Things terminal communicates with a satellite network, adding a target identification bit into a non-access layer message, wherein the target identification bit is used to represent whether the terminal supports IP multimedia subsystem packet switched voice; and sending the non-access layer message after the target identification bit is added to a network side.

[0104] The serial numbers of the embodiments of the present application described above are only for description, 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 focus, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments.

[0106] In several embodiments provided in the present application, it should be understood that the disclosed technology can be implemented by other ways. Among them, the above-described device embodiments are only schematic, for example, the division of the units can be a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed units can be indirect coupling or communication connection through some interfaces, units or modules, and can be electrical or other forms.

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

[0108] In addition, the functional units in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0109] The integrated unit, if realized in the form of a software functional unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the part of the prior art that contributes to the technical solutions or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The foregoing storage medium includes: a U disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store program codes.

[0110] The above is only the preferred embodiment of the present application, and it should be pointed out that for ordinary skilled in the art, without departing from the principles of the present application, a number of improvements and refinements can be made, and these improvements and refinements should be considered as the protection scope of the present application.

Claims

1. A method for reporting terminal voice capabilities, 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 stratum message, wherein the target identification bit is used to indicate whether the terminal supports IP multimedia subsystem packet switched voice. If the terminal supports at least one of circuit switched fallback and / or IP multimedia subsystem voice, a target identification bit is added to the non-access stratum message, and the non-access stratum message includes at least one of the following: an attach request, a tracking area update request, and a routing area update request; 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, wherein: 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 layer 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, 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-centered and data transmission-centered, and the voice domain preference indicator bit is used to characterize the terminal's support for voice services in the evolved universal mobile telecommunications 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 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 the terrestrial network scenario.

5. The method for reporting terminal voice capability according to claim 1, wherein: The target identification bit includes: a voice domain preference indication bit; adding a target identification bit to the non-access layer message also includes: The idle bits in the information element contained in the non-access layer message are rewritten as 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 telecommunications 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, wherein: The target identification bit includes: a voice domain preference information element parameter; when the non-access layer message is an attach 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 terminal's support for voice services in the evolved universal mobile telecommunications 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 stratum 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 configured to add a target identification bit to a non-access stratum message in a scenario where a non-terrestrial network Internet of Things 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. If the terminal supports at least one of circuit switched fallback and / or IP multimedia subsystem voice, a target identification bit is added to the non-access stratum message, and the non-access stratum message includes at least one of the following: an attach request, a tracking area update request, and a routing area update request; 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 according to any one of claims 1 to 7 is executed when the program is run.

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 according to any one of claims 1 to 7 are implemented.

Images