WO2022048375A1 - 一种网络系统和终端设备 - Google Patents

一种网络系统和终端设备 Download PDF

Info

Publication number
WO2022048375A1
WO2022048375A1 PCT/CN2021/110225 CN2021110225W WO2022048375A1 WO 2022048375 A1 WO2022048375 A1 WO 2022048375A1 CN 2021110225 W CN2021110225 W CN 2021110225W WO 2022048375 A1 WO2022048375 A1 WO 2022048375A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
call
capability
message
cell
Prior art date
Application number
PCT/CN2021/110225
Other languages
English (en)
French (fr)
Inventor
沈玉娟
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2022048375A1 publication Critical patent/WO2022048375A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/142—Reselecting a network or an air interface over the same radio air interface technology
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a network system and terminal equipment.
  • 5G New Radio is a new radio access technology (RAT) developed by the 3rd Generation Partnership Project (3GPP) for 5G mobile communication networks. It is a global standard for the air interface of 5G networks.
  • the 5G mobile communication network provides voice services based on the IP multimedia subsystem (IMS), and the voice call service carried on it is called voice on NR (VoNR).
  • VoIPNR voice on NR
  • There are different access methods such as voice call service on the bearer) and VoNR.
  • VoLTE is used as a transition solution for voice services
  • VoNR is used as the final voice service solution for 5G independent networking (SA). evolution.
  • VoNR cannot guarantee stable voice services in the early stage of 5G network deployment.
  • Various call exceptions occur.
  • the embodiments of the present application provide a network system and terminal equipment, which can solve the problem that the UE is prone to abnormal calls in the 5G network in the initial stage of networking of the 5G NR system.
  • an embodiment of the present application provides a network system, including: a first base station, and a terminal device UE residing in a first new air interface NR cell of the first base station; the UE is configured to detect an abnormal VoNR call when the UE is abnormal , sending a registration request message to the first base station; the first base station is used to send a UE capability query message to the UE in response to the registration request message; the UE is also used to respond to the UE capability query message, and send the first UE capability information to the first base station , the first UE capability information is used to indicate to the first base station that the UE does not support the VoNR capability and/or does not support the robust header compression RoHC capability.
  • the first base station may consider that the UE does not have the VoNR capability or the UE does not have the RoHC capability according to the first UE capability information. Then, when the user makes a call again, the first base station will trigger the EPS FB process according to the indication of the first UE capability information, and the EPC and the eNB will establish a call under the 4G network through VoLTE, or the RoHC function may not be enabled, so as to avoid abnormal VoNR calls phenomenon occurs, improving the call completion rate and call quality.
  • the abnormal VoNR call includes a failure to establish a VoNR call in a UE calling or called scenario
  • the first UE capability information is used to indicate to the first base station that the UE does not support the VoNR capability.
  • the first base station may consider that the UE does not have the VoNR capability according to the first UE capability information.
  • the first base station will reject the request for establishing a dedicated bearer 5QI1 initiated by the 5GC, but trigger the EPS FB process to initiate a redirection to the 5GC or Inter-RAT handover request, and wait for UE to fall back to LTE network, voice service is provided by EPC and eNB through VoLTE. Thereby, the abnormal situation of failing to establish a VoNR call is avoided from happening again, and the UE recovers from the abnormality of the VoNR call.
  • the abnormality of the VoNR call includes a RoHC abnormality during the VoNR call
  • the first UE capability information is used to indicate to the first base station that the UE does not support the RoHC capability.
  • the first base station may consider that the UE does not have the RoHC capability according to the first UE capability information. Then, when the user makes a call again, neither the first base station nor the UE will enable the RoHC function, so as to avoid RoHC abnormality during the call, so as to improve the call quality.
  • the abnormal VoNR call includes a failure to establish a VoNR call in a UE calling or called scenario or a RoHC abnormality during the VoNR call
  • the first UE capability information is used to indicate to the first base station that the UE does not support the VoNR capability and RoHC capability is not supported.
  • the first base station may consider that the UE does not have the VoNR capability and that the UE does not have the RoHC capability according to the capability information of the first UE.
  • the first base station will trigger the EPS FB process, and the EPC and the eNB will establish a call under the 4G network through VoLTE, and the RoHC function will not be enabled, so as to avoid abnormal VoNR calls and improve calls. connection rate and call quality.
  • the UE is specifically configured to send a registration request message to the first base station when the consecutive times of failure to establish a VoNR call in a UE calling or called scenario is greater than a preset first threshold.
  • the UE is specifically configured to send a registration request message to the first base station in the mobility management idle 5GMM-IDLE mode after the VoNR call ends when it detects that the VoNR call is abnormal.
  • the UE is further configured to detect whether the NR cell where it resides is switched from the first NR cell to the second NR cell after sending the first UE capability information to the first base station, the first NR cell and the second NR cell The tracking areas of the NR cells are different; the UE is further configured to send a registration request message to the second base station corresponding to the second NR cell when detecting that the NR cell it resides on is switched from the first NR cell to the second NR cell; the second The base station is configured to send a UE capability query message to the UE in response to the registration request message; the UE is further configured to send a second UE capability information to the second base station in response to the UE capability query message, and the second UE capability information is used to send the second UE capability information to the second base station.
  • the second base station Indicates that the UE supports VoNR capability and/or supports RoHC capability. In this way, when the UE resides in the NR cell of the new tracking area, when the user makes a call again, since the second base station believes that the UE currently supports the VoNR capability, the second base station will start the voice dedicated bearer 5QI1 for establishing a VoNR call, and will not Triggering the EPS FB restores the VoNR calling capability.
  • the UE is specifically configured to wait for a first preset time period when the consecutive times of failure to establish a VoNR call is greater than a preset second threshold, and then detect whether the NR cell where it resides is switched from the first NR cell to The second NR cell. In this way, the UE can avoid the failure to establish a VoNR call in a short time, and improve the connection rate.
  • an embodiment of the present application provides a network system, including: a first base station, and a terminal device UE residing in a first NR cell of the first base station;
  • the first voice codec is the voice codec scheme currently used by the UE and the first base station, and the first request message is used to request the first base station to use the second voice codec , the quality standard of the second voice codec is lower than the quality standard of the first voice codec;
  • the first base station is used to respond to the first request message and send a first response message to the UE, and the first response message is used to indicate to the UE the first response message.
  • a base station agrees to use the second voice codec;
  • the UE is further configured to adjust the currently used voice codec scheme to the second voice codec in response to the first response message.
  • the UE and the first base station can use the low-level second voice codec scheme to encode, decode and transmit voice data, which implements the degraded processing of the voice codec scheme and avoids the use of high-level voice codecs.
  • the codec scheme is used, abnormal calls such as noise occur.
  • the UE is further configured to wait for a second preset time period after the currently used voice codec scheme is adjusted to the second voice codec, and then send a second request message to the first base station, the second request message It is used to request the first base station to use the first voice codec; the first base station is also used to send a second response message to the UE in response to the second request message, and the second response message is used to indicate to the UE that the first base station agrees to use the first voice codec.
  • Voice codec the UE is further configured to adjust the currently used voice codec scheme to the first voice codec in response to the second response message.
  • the UE can no longer negotiate the voice codec scheme with the first base station within a period of time after downgrading the voice codec scheme.
  • the UE considers that the network environment has changed, so it negotiates with the network device to upgrade the voice codec scheme again. If the negotiation is successful, when the VoNR call is performed again, the UE and the first base station can use the high-level first base station.
  • a voice codec scheme encodes, decodes and transmits voice data to achieve higher bandwidth and reduce delay jitter and packet loss during calls.
  • the first base station is configured to send a first rejection message to the UE in response to the first request message, where the first rejection message is used to indicate to the UE that the first base station does not agree to use the second voice codec; the UE further for continuing to use the first speech codec in response to the first rejection message.
  • the first base station is further configured to send a second rejection message to the UE in response to the second request message, where the second rejection message is used to indicate to the UE that the first base station does not agree to use the first voice codec; the UE It is also used for continuing to use the second speech codec in response to the second rejection message.
  • the UE is further configured to detect whether the NR cell where it resides is switched from the first NR cell to the second NR cell after the currently used voice codec scheme is adjusted to the second voice codec.
  • the tracking areas of the NR cell and the second NR cell are different; the UE is further configured to send the first NR cell to the second base station corresponding to the second NR cell when detecting that the NR cell it resides on is switched from the first NR cell to the second NR cell.
  • the third request message is used to request the second base station to use the first voice codec; the second base station is further used to send a third response message to the UE in response to the third request message, and the third response message is used to send the UE to the UE Instructing the second base station to agree to use the first voice codec; the UE is further configured to adjust the currently used voice codec scheme to the first voice codec in response to the third response message.
  • the UE can negotiate with the network device to upgrade the voice codec scheme again when the tracking area of the NR cell it camps on changes. If the negotiation is successful, when the VoNR call is performed again, the UE and the second base station can use the high-level voice codec.
  • the first voice codec scheme encodes, decodes and transmits voice data to achieve higher bandwidth and reduce delay jitter and packet loss during calls.
  • the abnormal call based on the first voice codec includes: noise occurs in the call based on the first voice codec, and the number of calls of the noise is continuously greater than a preset second threshold.
  • the UE when the UE initiates a call hold hold during a call: the UE is further configured to send a fourth request message to the first base station, where the fourth request message is used to request the first base station to use the first base station during the call hold period Voice codec; the first base station is further configured to send a fourth response message to the UE in response to the fourth request message, where the fourth response message is used to indicate to the UE that the first base station agrees to use the first voice codec during the call hold period.
  • the first base station is further configured to send a fourth rejection message to the UE in response to the fourth request message, where the fourth rejection message is used to indicate to the UE that the first base station does not agree to use the first voice during the call hold period codec; the UE is further configured to send a fifth request message to the first base station in response to the fourth rejection message, where the fifth request message is used to request the first base station to use the second voice codec during the call hold period.
  • the UE and the first base station can negotiate to use a lower-level voice codec scheme to perform the call hold task to avoid call hold failure.
  • the UE when the UE initiates the call hold release unhold during the call: the UE is further configured to send a sixth request message to the first base station, and the sixth request message is used to request the first base station to use the call hold release after the call hold is released.
  • the first voice codec; the first base station is further configured to send a sixth response message to the UE in response to the sixth request message, and the sixth response message is used to indicate to the UE that the first base station agrees to use the first voice codec after the call hold is released. decoding.
  • the first base station is further configured to send a sixth rejection message to the UE in response to the sixth request message, where the sixth rejection message is used to indicate to the UE that the first base station does not agree to use the first base station after the call hold is released Voice codec; the UE is further configured to send a seventh request message to the first base station in response to the sixth rejection message, where the seventh request message is used to request the first base station to use the second voice codec after the call hold is released.
  • the UE and the first base station can negotiate to use the lower-level voice codec scheme to perform the call-hold task to avoid call hold release failure.
  • an embodiment of the present application provides a network system, including: a first base station, and a terminal device UE residing in an NR cell of the first base station; the UE is used to detect an abnormality of the EPS FB during domain switching and redialing , to turn off the NR capability; the UE is further configured to wait for a third preset time period after turning off the NR capability, and then turn on the NR capability.
  • the UE does not camp on the NR cell, but only searches for the LTE cell, and chooses to camp on the LTE cell, and does not support the N1NAS signaling mode.
  • the UE directly initiates a VoLTE call request or a call request in the CS domain to the first base station, avoiding the EPS FB process, thereby improving the call completion rate.
  • the UE is further configured to enable the NR capability after the NR capability is disabled, if it is detected that packet data transmissions are continuously generated and the total data traffic generated by the packet data transmission is greater than a preset traffic threshold.
  • the UE is further configured to enable the NR capability if it detects that the distance of its own position change is greater than a preset distance threshold after the NR capability is disabled.
  • the UE turning off the NR capability includes: the UE no longer camps on the NR cell, searches for a long-term evolution technology LTE cell at the same time, and camps on the LTE cell.
  • enabling the NR capability for the UE includes: the UE searches for an NR cell and camps on the NR cell.
  • the EPS FB is abnormal, including: in a call scenario where the UE is calling or being called, the UE fails to release the dedicated 5G voice bearer with the first base station, or the UE establishes a dedicated LTE voice bearer with the second base station. If it fails, the second base station is the base station corresponding to the LTE cell.
  • the abnormal EPS FB includes: in a call scenario where the UE is calling or being called, the UE fails to release the dedicated 5G voice bearer with the first base station, and the number of consecutive failures is greater than a preset fourth threshold, Alternatively, the UE fails to establish a dedicated LTE voice bearer with the second base station, and the number of consecutive failures is greater than the preset fifth threshold.
  • the present application provides a terminal device, including: a transceiver, a memory, and a processor, wherein the memory stores computer program instructions, and when the program instructions are executed by the processor, the terminal device implements the following method steps:
  • the terminal device When the VoNR call is abnormal, send a registration request message to the first base station; in response to the UE capability query message, send the first UE capability information to the first base station, wherein the UE capability query message is the first base station in response to the registration request message to the UE.
  • Sent the first UE capability information is used to indicate to the first base station that the UE does not support the VoNR capability and/or does not support the robust header compression RoHC capability.
  • the first base station may consider that the UE does not have the VoNR capability or the UE does not have the RoHC capability according to the first UE capability information. Then, when the user makes a call again, the first base station will trigger the EPS FB process according to the indication of the first UE capability information, and the EPC and the eNB will establish a call under the 4G network through VoLTE, or the RoHC function may not be enabled, so as to avoid abnormal VoNR calls phenomenon occurs, improving the call completion rate and call quality.
  • the abnormal VoNR call includes a failure to establish a VoNR call in a UE calling or called scenario
  • the first UE capability information is used to indicate to the first base station that the UE does not support the VoNR capability.
  • the first base station may consider that the UE does not have the VoNR capability according to the capability information of the first UE.
  • the first base station will reject the request for establishing a dedicated bearer 5QI1 initiated by the 5GC, but trigger the EPS FB process to initiate a redirection to the 5GC or Inter-RAT handover request, and wait for UE to fall back to LTE network, voice service is provided by EPC and eNB through VoLTE. Thereby, the abnormal situation of failing to establish a VoNR call is avoided from happening again, and the UE recovers from the abnormality of the VoNR call.
  • the abnormality of the VoNR call includes a RoHC abnormality during the VoNR call
  • the first UE capability information is used to indicate to the first base station that the UE does not support the RoHC capability.
  • the first base station may consider that the UE does not have the RoHC capability according to the first UE capability information. Then, when the user makes a call again, neither the first base station nor the UE will enable the RoHC function, so as to avoid RoHC abnormality during the call, so as to improve the call quality.
  • the abnormal VoNR call includes a failure to establish a VoNR call in a UE calling or called scenario or a RoHC abnormality during the VoNR call
  • the first UE capability information is used to indicate to the first base station that the UE does not support the VoNR capability and RoHC capability is not supported.
  • the first base station may consider that the UE does not have the VoNR capability and that the UE does not have the RoHC capability according to the capability information of the first UE.
  • the first base station will trigger the EPS FB process, and the EPC and the eNB will establish a call under the 4G network through VoLTE, and the RoHC function will not be enabled, so as to avoid abnormal VoNR calls and improve calls. connection rate and call quality.
  • the terminal device when the program instructions are executed by the processor, the terminal device is made to specifically implement the following method steps: when the consecutive times of failure to establish a VoNR call in the UE calling or called scenario is greater than a preset first threshold, send the The first base station sends a registration request message.
  • the terminal device when the program instructions are executed by the processor, the terminal device is made to specifically implement the following method steps: when an abnormal VoNR call is detected, in the mobility management idle 5GMM-IDLE mode after the VoNR call ends, to the first The base station sends a registration request message.
  • the terminal device when the program instructions are executed by the processor, the terminal device is also made to implement the following method steps: after sending the first UE capability information to the first base station, detect whether the NR cell where it resides is from the first NR cell Handover to the second NR cell, the tracking areas of the first NR cell and the second NR cell are different; when it is detected that the NR cell it resides on is switched from the first NR cell to the second NR cell, the tracking area corresponding to the second NR cell is detected.
  • the second base station sends a registration request message; in response to the UE capability query message sent by the second base station, sends second UE capability information to the second base station, where the second UE capability information is used to indicate to the second base station that the UE supports the VoNR capability and/or Support RoHC capability.
  • the second base station will start the voice dedicated bearer 5QI1 for establishing a VoNR call, and will not Triggering the EPS FB restores the VoNR calling capability.
  • the terminal device when the program instructions are executed by the processor, the terminal device is made to specifically implement the following method steps: when the consecutive times of failure to establish a VoNR call is greater than a preset second threshold, wait for a first preset duration, and then detect Whether the NR cell it camps on is handed over from the first NR cell to the second NR cell. In this way, the UE can avoid the failure to establish a VoNR call in a short time, and improve the connection rate.
  • an embodiment of the present application provides a terminal device, including: a transceiver, a memory, and a processor, where the memory stores computer program instructions, and when the program instructions are executed by the processor, the terminal device implements the following method steps: When an abnormal call based on the first voice codec is detected, a first request message is sent to the first base station.
  • the first voice codec is the voice codec scheme currently used by the UE and the first base station, and the first request message is used to request the first base station.
  • a base station uses a second voice codec, and the quality standard of the second voice codec is lower than the quality standard of the first voice codec; in response to the first response message, the currently used voice codec scheme is adjusted to the second voice codec , wherein the first response message is sent by the first base station in response to the first request message, and the first response message is used to indicate to the UE that the first base station agrees to use the second voice codec.
  • the UE and the first base station can use the low-level second voice codec scheme to encode, decode and transmit voice data, which implements the degraded processing of the voice codec scheme and avoids the use of high-level voice codecs.
  • the codec scheme is used, abnormal calls such as noise occur.
  • the terminal device when the program instruction is executed by the processor, the terminal device is also made to implement the following method steps: after the currently used voice codec scheme is adjusted to the second voice codec, wait for a second preset time period, and then sending a second request message to the first base station, where the second request message is used to request the first base station to use the first voice codec; in response to the second response message, adjusting the currently used voice codec scheme to the first voice codec, The second response message is sent by the first base station in response to the second request message, and the second response message is used to indicate to the UE that the first base station agrees to use the first voice codec.
  • the UE can no longer negotiate the voice codec scheme with the first base station within a period of time after downgrading the voice codec scheme.
  • the UE considers that the network environment has changed, so it negotiates with the network device to upgrade the voice codec scheme again. If the negotiation is successful, when the VoNR call is performed again, the UE and the first base station can use the high-level first base station.
  • a voice codec scheme encodes, decodes and transmits voice data to achieve higher bandwidth and reduce delay jitter and packet loss during calls.
  • the terminal device when the program instructions are executed by the processor, the terminal device is further caused to implement the following method steps: in response to the first rejection message, continue to use the first voice codec, wherein the first rejection message is the first base station In response to the sending of the first request message, the first rejection message is used to indicate to the UE that the first base station does not agree to use the second speech codec.
  • the terminal device when the program instructions are executed by the processor, the terminal device is further caused to implement the following method steps: continue to use the second voice codec in response to the second rejection message, wherein the second rejection message is the first base station In response to the second request message being sent, the second reject message is used to indicate to the UE that the first base station does not agree to use the first speech codec.
  • the terminal device when the program instructions are executed by the processor, the terminal device is also made to implement the following method steps: after the currently used voice codec scheme is adjusted to the second voice codec, detect whether the NR cell where it resides is When switching from the first NR cell to the second NR cell, the tracking areas of the first NR cell and the second NR cell are different; when it is detected that the NR cell where it resides is switched from the first NR cell to the second NR cell, the first NR cell is switched to the second NR cell.
  • the second base station corresponding to the two NR cells sends a third request message, where the third request message is used to request the second base station to use the first voice codec; in response to the third reply message, the currently used voice codec scheme is adjusted to the first Voice codec, wherein the third response message is sent by the second base station in response to the third request message, and the third response message is used to indicate to the UE that the second base station agrees to use the first voice codec.
  • the UE can negotiate with the network device to upgrade the voice codec scheme again when the tracking area of the NR cell it camps on changes. If the negotiation is successful, when the VoNR call is performed again, the UE and the second base station can use the high-level voice codec.
  • the first voice codec scheme encodes, decodes and transmits voice data to achieve higher bandwidth and reduce delay jitter and packet loss during calls.
  • the abnormal call based on the first voice codec includes: noise occurs in the call based on the first voice codec, and the number of calls of the noise is continuously greater than a preset second threshold.
  • the terminal device when the program instruction is executed by the processor, the terminal device is also made to implement the following method steps: when a call is held on hold during a call, a fourth request message is sent to the first base station, and the fourth request message uses requesting the first base station to use the first voice codec during the call hold period.
  • the terminal device when the program instructions are executed by the processor, the terminal device is further caused to implement the following method steps: in response to a fourth rejection message, send a fifth request message to the first base station, wherein the fourth rejection message is the first Sent by a base station in response to a fourth request message, the fourth reject message is used to indicate to the UE that the first base station does not agree to use the first voice codec during the call hold period, and the fifth request message is used to request the first base station to use the first voice codec during the call hold period Use the second voice codec.
  • the UE and the first base station can negotiate to use a lower-level voice codec scheme to perform the call hold task to avoid call hold failure.
  • the terminal device when the program instructions are executed by the processor, the terminal device is also made to implement the following method steps: when initiating a call to hold and release the unhold during a call, send a sixth request message to the first base station, the sixth request message It is used to request the first base station to use the first voice codec after the call hold is released.
  • the terminal device when the program instructions are executed by the processor, the terminal device is further caused to implement the following method steps: in response to the sixth rejection message, send a seventh request message to the first base station, wherein the sixth rejection message is the first Sent by a base station in response to the sixth request message, the sixth reject message is used to indicate to the UE that the first base station does not agree to use the first voice codec after the call hold is released, and the seventh request message is used to request the first base station to hold the call Use the second voice codec after release.
  • the UE and the first base station can negotiate to use the lower-level voice codec scheme to perform the call-hold task to avoid call hold release failure.
  • an embodiment of the present application provides a terminal device, including: a transceiver, a memory, and a processor, where the memory stores computer program instructions, and when the program instructions are executed by the processor, the terminal device implements the following method steps: When it is detected that the EPS FB is abnormal, the NR capability is turned off; after the NR capability is turned off, the NR capability is turned on after waiting for a third preset time period.
  • the UE does not camp on the NR cell, but only searches for the LTE cell, and chooses to camp on the LTE cell, and does not support the N1NAS signaling mode.
  • the UE directly initiates a VoLTE call request or a call request in the CS domain to the first base station, avoiding the EPS FB process, thereby improving the call completion rate.
  • the terminal device when the program instructions are executed by the processor, the terminal device is further caused to implement the following method steps: after the NR capability is turned off, if it is detected that packet data transmission is continuously generated, and the total data flow generated by the packet data transmission is greater than If the preset traffic threshold is set, the NR capability is enabled.
  • the terminal device when the program instructions are executed by the processor, the terminal device is also made to implement the following method steps: after turning off the NR capability, if it detects that the distance of its own position change is greater than a preset distance threshold, turn on the NR capability .
  • the UE turning off the NR capability includes: the UE no longer camps on the NR cell, searches for a long-term evolution technology LTE cell at the same time, and camps on the LTE cell.
  • enabling the NR capability for the UE includes: the UE searches for an NR cell and camps on the NR cell.
  • the EPS FB is abnormal, including: in a call scenario where the UE is calling or being called, the UE fails to release the dedicated 5G voice bearer with the first base station, or the UE establishes a dedicated LTE voice bearer with the second base station. If it fails, the second base station is the base station corresponding to the LTE cell.
  • the abnormal EPS FB includes: in a call scenario where the UE is calling or being called, the UE fails to release the dedicated 5G voice bearer with the first base station, and the number of consecutive failures is greater than a preset fourth threshold, Alternatively, the UE fails to establish a dedicated LTE voice bearer with the second base station, and the number of consecutive failures is greater than the preset fifth threshold.
  • the embodiments of the present application further provide a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium runs on a computer, the computer is made to execute the methods of the above aspects and their respective implementations.
  • the embodiments of the present application further provide a computer program product including instructions, which, when run on a computer, enables the computer to execute the methods of the above aspects and their respective implementations.
  • an embodiment of the present application further provides a chip system, where the chip system includes a processor for supporting the above-mentioned apparatus or system to implement the functions involved in the above-mentioned aspects, for example, generating or processing the functions involved in the above-mentioned method. information.
  • Figure 1 shows the options and evolution of the 5G voice solution
  • Fig. 2 shows the schematic diagram of EPS FB by taking Option2 networking as an example
  • FIG. 3 is a schematic structural diagram of a terminal device 100 provided by an embodiment of the present application.
  • FIG. 4 is a flowchart of Embodiment (1) of the information indication method provided by the present application.
  • Fig. 5 shows the scene that UE registers 5GS service
  • FIG. 6 is a flowchart of the UE sending the second UE capability information to the gNB according to Embodiment 1 of the present application;
  • Embodiment (2) of the information indication method provided by the present application is a flowchart of Embodiment (2) of the information indication method provided by the present application.
  • FIG. 8 is a flowchart of the UE sending the second UE capability information to the gNB according to Embodiment 2 of the present application;
  • Embodiment (3) is a flowchart of Embodiment (3) of the information indication method provided by the present application.
  • FIG. 10 is a flowchart of the UE sending the second UE capability information to the gNB according to Embodiment 3 of the present application;
  • Embodiment 11 is a flowchart of Embodiment (4) of the information indication method provided by the present application.
  • FIG. 12 is a schematic diagram of UE and gNB recovering speech codec according to Embodiment 3 of the present application;
  • FIG. 13 is a schematic diagram of UE and gNB recovering speech codec according to Embodiment 3 of the present application;
  • FIG. 14 is a schematic diagram of a call hold shown in an embodiment of the present application.
  • FIG. 15 is a schematic diagram of a voice codec for initiating call hold through negotiation between a UE and a gNB according to Embodiment 3 of the present application;
  • FIG. 16 is a schematic diagram of the voice codec for releasing call hold through negotiation between the UE and the gNB according to Embodiment 3 of the present application;
  • FIG. 17 is a flowchart of Embodiment (5) of the information indication method provided by the present application.
  • FIG. 18 is a schematic structural diagram of an information indicating device provided by an embodiment of the present application.
  • FIG. 19 is a schematic structural diagram of an information indicating device provided by an embodiment of the present application.
  • the fifth generation mobile communication network (English: 5th generation mobile networks, 5G) is the latest generation of mobile communication technology. Compared with the early mobile communication technologies such as 4G, 3G and 2G, 5G can provide higher data rates and lower higher latency, full connectivity of the Internet of Everything, more energy saving, lower cost, higher system capacity and large-scale device access.
  • 5G New Radio is a new radio access technology (RAT) developed by the 3rd Generation Partnership Project (3GPP) for 5G mobile communication networks. It is a global standard for the air interface of 5G networks.
  • 3GPP 3rd Generation Partnership Project
  • the 5G mobile communication network follows the voice architecture of the 4G mobile communication network, and still provides voice services based on the IP multimedia subsystem (IMS).
  • the wireless access technology of 4G mobile communication network is Long Term Evolution (LTE), and the voice call service carried on it is called voice on LTE (VoLTE); the wireless access technology of 5G mobile communication network is as described above. It is shown as NR, and the voice call service carried on it is called voice on NR (VoNR).
  • VoLTE and VoNR exist as different access methods of 5G IMS voice service, and VoNR will be used as a 5G independent network (SA) The ultimate voice business solution.
  • SA 5G independent network
  • 5G Option3/3a/3X networking is the current implementation of 5G NSA non-independent networking.
  • NR is provided by the 5G base station gNB, and then the gNB acts as a slave station of the 4G base station's eNB to access the 4G core network EPC network.
  • the 5G Option7/7a/7X networking is an implementation method of the current 5G SA networking.
  • This method can be evolved from the Option3 series, that is, with the deployment of 5GC, the eNB that originally accessed the EPC was upgraded to ng-eNB.
  • the Option3 series network originally connected to the EPC is cut to 5GC to form the Option7 series network.
  • ng-eNB refers to the 4G LTE base station after the upgrade, which supports access to the 5G core network 5GC, also known as eLTE.
  • the 5G Option 5 networking is another implementation of the current 5G SA networking. This networking is mainly evolved from the LTE networking. With the deployment of 5GC, the eNB that originally accessed the EPC was upgraded to ng-eNB. , cut to 5GC.
  • 5G Option2 networking is the target networking solution of 5G SA, and gNB is directly connected to 5GC.
  • 5G Option 4 networking is another implementation of the current 5G SA networking, which adds ng-eNB slave base stations on the basis of 5G Option 2 networking.
  • FIG 1 also shows the voice service solutions that can be selected by various networking modes under each networking mode. It can be understood that, considering factors such as 5G network coverage scale and networking maturity, each networking mode may Only some of its options are supported. Among them, CSFB (circuit switch fallback) is a solution for falling back to 3G bearing voice services under 4G, EPS FB (EPS Fallback) and RAT FB (RAT Fallback) are solutions for falling back to 4G bearing voice services under 5G SA; VoeLTE It is a solution for carrying voice services on eLTE. The only difference between VoeLTE and VoLTE is whether the 4G base station is an eNB or an ng-eNB. For ease of description, it is hereinafter collectively referred to as VoLTE.
  • VoLTE the 4G base station is an eNB or an ng-eNB.
  • the voice of 5G Option3/3a/3X networking can use the CSFB solution in the early stage.
  • VoLTE and VoNR solutions the voice of 5G Option7/7a/7X networking can use VoLTE in the early stage.
  • the voice of the 5G Option4 networking solution uses the VoLTE solution
  • the voice of the 5G Option2 and Option3 networking can use the EPS FB or RAT FB or VoLTE solution in the early stage.
  • VoNR The voice of VoNR is carried on the 5G base station gNB.
  • VoNR is carried through 5GC and gNB
  • VoNR is carried through 4G core network EPC and gNB.
  • the terminal equipment UE Under VoNR, the terminal equipment UE resides in the NR cell, and both voice services and data services are carried on the NR network.
  • the terminal equipment UE moves to an area with poor NR signal coverage, it needs to initiate coverage-based handover to achieve interoperability with 4G, switch to LTE, and use VoLTE to provide services.
  • EPS FB It is also called redialing when changing domains.
  • the 5G NR system does not provide voice services in the initial stage of networking.
  • the gNB establishes an IMS voice channel on the NR, the handover is triggered. At this time, the gNB sends a redirection or inter-RAT handover request to the 5GC and falls back to the LTE network. , served by VoLTE.
  • the terminal equipment UE resides in the NR cell, and when making a call, both voice and data services fall back to LTE.
  • FIG. 2 shows a schematic diagram of the EPS FB by taking the Option2 networking as an example.
  • the UE initiates a voice call through SIP signaling and informs the 5GC to establish a 5G voice dedicated bearer 5QI1; then, the 5GC initiates a request to the gNB to establish a dedicated bearer 5QI1; then, when the gNB does not have VoNR capability, according to the UE NR capability, N26 interface deployment, LTE wireless conditions, and access and mobility management function (AMF) indication information to determine whether to trigger EPS FB; Directional or inter-RAT handover request, and wait for the UE to fall back to the LTE network, and the EPC and eNB provide voice services through VoLTE.
  • AMF access and mobility management function
  • RAT FB The 5G NR system does not provide voice services in the initial stage of networking.
  • a handover is triggered.
  • the gNB initiates a redirection or inter-RAT handover request to the 5GC, and falls back to the eLTE network, where VoeLTE provides services.
  • the terminal equipment UE resides in the NR cell, and when making a call, both voice and data services fall back to eLTE.
  • the implementation of the solution is similar to that of EPS FB, and will not be repeated here.
  • speech codecs currently used by 5G networks may include:
  • EVS Enhanced voice services
  • 3GPP 3rd Generation Partnership Project
  • It is the current voice coding with the best anti-packet loss and quality in 3GPP.
  • Adaptive multi-rate compression is a voice and audio coding standard developed by 3GPP.
  • AMR is a voice coding and decoding scheme adopted by VoLTE and is currently widely used in 4G networks.
  • AMR coding includes two speech coding methods, AMR-WB (adaptive multi rate wide band) and AMR-NB (adaptive multi rate narrow band). Among them, AMR-WB can have higher bandwidth and sampling rate than AMR-NB, and AMR-NB is also generally called AMR.
  • RoHC packet data convergence protocol
  • PRBs physical resource blocks
  • RoHC can compress the packet header of the voice packet into smaller bytes, making the length of the entire voice packet smaller, using fewer fragments to ensure the correct transmission of the voice packet with a higher probability, thus increasing the voice service. edge coverage.
  • the RoHC protocol defines three compression states and three decompression states, so that the RoHC can compress and decompress the IP packet header in different wireless link states, keep the compression and decompression data streams synchronized, and ensure the robustness of the RoHC protocol.
  • Initialize and refresh (IR) state Used to initialize and update static domain and dynamic domain information in the context. In this state, the compressor continuously sends all IP header information and stream association identifiers.
  • Second-order (SO) state The SO state is the highest-level compression state. At this time, the compressor only transmits the compression value of the dynamic domain according to the changing law of the dynamic domain. At this time, the compressor sends the RoHC compressed packet with the highest compression rate.
  • NC state refers to the state of the decompressor when the data stream is first transmitted.
  • the decompressor does not have the static and dynamic domain information of the IP header, and the compressor needs to send a packet containing the complete header in the IR state.
  • SC Static Context
  • FC state Refers to the state in which the decompressor obtains sufficient static domain information and dynamic domain change rule information, corresponds to the SO state of the compressor, and can receive RoHC compressed packets sent by the compressor in the SO state.
  • the existing RoHC protocol also defines the migration principle of RoHC between different decompression states and compression states to ensure compression robustness and compression ratio, for example:
  • Periodicity principle The compressor will transfer to the low-level compression state after a certain timeout in the FO and SO states.
  • Negative feedback principle When the wireless link allows sending feedback packets, when the decompressor continuously decompresses RoHC packets incorrectly, it will send negative feedback packets to the compressor to promote the low-level state transition in the compression direction, and send packets with complete information , so that the decompressor updates the decompression context information after receiving these packets, and keeps the compression and decompression contexts synchronized.
  • RoHC When there is a RoHC exception during the call, such as decompression and compression errors, according to the current RoHC protocol, it can only be performed after the compressor is in the FO, SO state for a certain time out or when the decompressor continuously decompresses RoHC packets incorrectly. The transition between the decompressed state and the compressed state may still cause the voice of the call to be interrupted.
  • gNB In the early stage of 5G network deployment, when gNB does not support VoNR, gNB needs to initiate EPS FB process when 5GC initiates a request to establish dedicated bearer 5QI1. However, if the compatibility or signaling between gNB and 5GC network elements There is a problem with the interaction, or the working state is abnormal, which will cause the EPS FB to be abnormal, so that the VoLTE call cannot be established. In the face of EPS FB exceptions, the current solution does not have the ability to automatically recover from the exception, resulting in the failure of subsequent calls to complete the EPS FB process.
  • an embodiment of the present application provides an information indication method, which can be applied to a 5G network system in any networking form as shown in FIG. 1 , such as a terminal device UE or a base station, etc.
  • the terminal equipment UE has the ability to automatically recover from the abnormal state when the call is abnormal under the 5G network.
  • the terminal devices in the embodiments of the present application may include, for example, mobile phones, tablet computers, personal computers, workstation devices, large-screen devices (eg, smart screens, smart TVs, etc.), handheld game consoles, home game consoles, virtual reality devices, and augmented reality devices. equipment, mixed reality equipment, etc., in-vehicle intelligent terminals, autonomous vehicles, customer-premises equipment (CPE), etc.
  • CPE customer-premises equipment
  • FIG. 3 is a schematic structural diagram of a terminal device 100 provided by an embodiment of the present application.
  • the terminal device 100 may include a processor 110, a memory 120, a universal serial bus (USB) interface 130, a radio frequency circuit 140, a mobile communication module 150, a wireless communication module 160, a camera 170, a display screen 180, and a subscriber identification module (subscriber identification module, SIM) card interface 190 and the like.
  • the processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural-network processing unit (neural-network processing unit, NPU), etc. Wherein, different processing units may be independent devices, or may be integrated in one or more processors, such as integrated in a system on a chip (system on a chip, SoC).
  • a memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have just been used or recycled by the processor 110.
  • the processor 110 may include one or more interfaces.
  • the interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous transceiver (universal asynchronous transmitter) receiver/transmitter, UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (SIM) interface, and / or universal serial bus (universal serial bus, USB) interface, etc.
  • I2C integrated circuit
  • I2S integrated circuit built-in audio
  • PCM pulse code modulation
  • PCM pulse code modulation
  • UART universal asynchronous transceiver
  • MIPI mobile industry processor interface
  • GPIO general-purpose input/output
  • SIM subscriber identity module
  • USB universal serial bus
  • Memory 120 may be used to store computer-executable program code, which includes instructions.
  • the memory 120 may include a stored program area and a stored data area.
  • the storage program area may store an operating system, an application program required for at least one function (such as a sound playback function, an image playback function, etc.), and the like.
  • the storage data area may store data (such as audio data, phone book, etc.) created during the use of the terminal device 100 and the like.
  • the memory 120 may include one or more storage units, for example, may include volatile memory (volatile memory), such as: dynamic random access memory (dynamic random access memory, DRAM), static random access memory (static random access memory) memory, SRAM), etc.; may also include non-volatile memory (non-volatile memory, NVM), such as: read-only memory (read-only memory, ROM), flash memory (flash memory), etc.
  • volatile memory volatile memory
  • DRAM dynamic random access memory
  • static random access memory static random access memory
  • SRAM static random access memory
  • NVM non-volatile memory
  • the processor 110 executes various functional applications and data processing of the terminal device 100 by executing the instructions stored in the memory 120 and/or the instructions stored in the memory provided in the processor.
  • the wireless communication function of the terminal device 100 may be implemented by the radio frequency circuit 140 , the mobile communication module 150 , the wireless communication module 160 , the modulation and demodulation processor, the baseband processor, and the like.
  • the radio frequency circuit 140 may include at least one antenna 141 for transmitting and receiving electromagnetic wave signals.
  • Each antenna in terminal device 100 may be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization.
  • the antenna 141 can be multiplexed as a diversity antenna of the wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.
  • the mobile communication module 150 may provide a wireless communication solution including 2G/3G/4G/5G, etc. applied on the terminal device 100 .
  • the mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA) and the like.
  • the mobile communication module 150 can receive electromagnetic waves through the antenna 141, filter, amplify, etc. the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation.
  • the mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and then convert it into electromagnetic waves for radiation through the antenna 141 .
  • at least part of the functional modules of the mobile communication module 150 may be provided in the processor 110 .
  • at least part of the functional modules of the mobile communication module 150 may be provided in the same device as at least part of the modules of the processor 110 .
  • the modem processor may include a modulator and a demodulator.
  • the modulator is used to modulate the low frequency baseband signal to be sent into a medium and high frequency signal.
  • the demodulator is used to demodulate the received electromagnetic wave signal into a low frequency baseband signal. Then the demodulator transmits the demodulated low-frequency baseband signal to the baseband processor for processing.
  • the low frequency baseband signal is processed by the baseband processor and passed to the application processor.
  • the application processor outputs sound signals through audio devices (including but not limited to speakers, receivers, etc.), or displays images or videos through the display screen 180 .
  • the modem processor may be a stand-alone device.
  • the modem processor may be independent of the processor 110, and may be provided in the same device as the mobile communication module 150 or other functional modules.
  • the wireless communication module 160 may include a Wi-Fi module, a bluetooth (BT) module, a global navigation satellite system (GNSS) module, a near field communication (NFC) module, an infrared (infrared) module , IR) module, etc.
  • the wireless communication module 160 may be one or more devices integrating at least one of the above modules.
  • the wireless communication module 160 receives electromagnetic waves via the antenna 141 , frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 .
  • the wireless communication module 160 can also receive the signal to be sent from the processor 110 , perform frequency modulation on it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 141 .
  • the wireless communication function of the terminal device 100 may include, for example, a global system for mobile communications (GSM), a general packet radio service (GPRS), a code division multiple access (CDMA) code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE) ), 5th generation mobile networks new radio (5G NR), BT, GNSS, WLAN, NFC, FM, and/or IR functions.
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • CDMA code division multiple access
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • TD-SCDMA time-division code division multiple access
  • LTE long term evolution
  • 5G NR 5th generation mobile networks new radio
  • GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (quasi-zenith) satellite system, QZSS) and/or satellite based augmentation systems (SBAS).
  • GPS global positioning system
  • GLONASS global navigation satellite system
  • BDS Beidou navigation satellite system
  • QZSS quasi-zenith satellite system
  • SBAS satellite based augmentation systems
  • Camera 170 is used to capture still images or video.
  • the camera 170 includes a lens and a photosensitive element, and the object generates an optical image through the lens and projects to the photosensitive element.
  • the photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor.
  • CMOS complementary metal-oxide-semiconductor
  • the photosensitive element converts the optical signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal.
  • the ISP outputs the digital image signal to the DSP for processing.
  • DSP converts digital image signals into standard RGB, YUV, RYYB and other formats of image signals.
  • the terminal device 100 may include 1 or N cameras 170 , where N is a positive integer greater than 1.
  • the NPU is a neural-network (NN) computing processor.
  • NN neural-network
  • Applications such as intelligent cognition of the terminal device 100 can be implemented through the NPU, such as image recognition, face recognition, speech recognition, text understanding, and the like.
  • the display screen 180 is used to display images, videos, and the like.
  • the display screen 180 includes a display panel.
  • the display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (active-matrix organic light).
  • LED diode AMOLED
  • flexible light-emitting diode flexible light-emitting diode (flex light-emitting diode, FLED), MiniLED, MicroLED, Micro-OLED, quantum dot light-emitting diode (quantum dot light emitting diodes, QLED) and so on.
  • the terminal device 100 may include 1 or N display screens 180 , where N is a positive integer greater than 1.
  • the SIM card interface 190 is used to connect a SIM card.
  • the SIM card can be contacted and separated from the terminal device 100 by inserting into the SIM card interface 190 or pulling out from the SIM card interface 190 .
  • the terminal device 100 may support 1 or N SIM card interfaces, where N is a positive integer greater than 1.
  • the SIM card interface 190 can support Nano SIM card, Micro SIM card, SIM card and so on.
  • the same SIM card interface 190 can insert multiple cards at the same time. Multiple cards can be of the same type or different.
  • the SIM card interface 190 may also be compatible with different types of SIM cards.
  • the SIM card interface 190 may also be compatible with external memory cards.
  • the terminal device 100 interacts with the network through the SIM card to realize functions such as calls and data communication.
  • the terminal device 100 adopts an eSIM, that is, an embedded SIM card.
  • the eSIM card can be embedded in the terminal device 100 and cannot be separated from the terminal device 100 .
  • the terminal device 100 may include more or less components than those shown in the drawings, or combine some components, or separate some components, or arrange different components.
  • the illustrated components may be implemented in hardware, software, or a combination of software and hardware.
  • Embodiment (1) of the present application is used to enable the UE to have the ability to automatically recover from the abnormality if both the UE and the base station (eg, gNB, ng-eNB, etc.) support VoNR, and if an abnormal situation occurs that the VoNR call fails to be established.
  • the base station eg, gNB, ng-eNB, etc.
  • FIG. 4 is a flowchart of Embodiment (1) of the information indication method provided by the present application.
  • the base station when a UE with VoNR capability registers for a 5G system (5GS) service, it can report UE capability information indicating that it has VoNR capability to the gNB.
  • 5GS 5G system
  • the scenarios in which the UE registers for the 5GS service may include:
  • the UE initially registers for the 5GS service. For example, when the UE turns on or turns off the airplane mode, the UE searches for the NR cell and initiates a registration request to the gNB, so as to realize the initial registration of the 5GS service by the UE.
  • Mobility update registration For example, after the UE has registered for the 5GS service, if it moves to a cell of a new tracking area (TA), it needs to re-register for the 5GS service.
  • TA tracking area
  • Periodic registration For example, after the UE has registered with the 5GS service, periodic registration can be triggered by a timer, so that the gNB knows the existence of the UE.
  • the UE capability information may be sent in a radio resource control (radio resource control, RRC) message.
  • RRC radio resource control
  • RRC information elements including UE capability information elements (UE capability information elements).
  • the UE capability information element contains the UE-NR-Capability parameter used to convey the radio access capability of the UE to the gNB.
  • the parameters related to the VoNR capability of the UE in the UE-NR-Capability may include the bolded part of the subbody of the following fields (for the convenience of description, hereinafter referred to as the bolded part 1):
  • the IMS-Parameters includes the IMS-related capability parameters of the UE.
  • the parameters related to the VoNR capability of the UE in the IMS-Parameters may include the bolded part of the subbody in the following fields (for the convenience of description, hereinafter referred to as the bolded part 2):
  • the UE when the UE registers for the 5GS service, it can carry voiceOverNR in the ims-Parameters parameter in the UE-NR-Capability-v1540 field in the UE capability information element sent to the gNB. Field, that is, the bold part 2 that carries the child body. In this way, the gNB knows that the UE has the VoNR capability. Then, the gNB that also has the VoNR capability will not trigger the EPS FB when it receives the request of the 5GC to initiate the establishment of the dedicated bearer 5QI1.
  • the UE initiates a voice call through SIP signaling and informs the 5GC to establish the 5G voice dedicated bearer 5QI1; then, the 5GC initiates a request to the gNB to establish the dedicated bearer 5QI1; It has been known from the UE capability information reported by the UE that the UE supports the VoNR capability. Therefore, if the gNB also supports the VoNR capability, the gNB will start the voice dedicated bearer 5QI1 for initiating VoNR calls.
  • the VoNR call will be successfully initiated; if the working status, compatibility or signaling of each network element of gNB and 5GC is normal If the interaction is abnormal, the VoNR call may fail to be established, that is, the user cannot make a call.
  • the UE when it detects that the establishment of the VoNR call fails, it can send the UE capability information to the gNB again.
  • this UE capability information is referred to as the first UE capability here.
  • the first UE capability information does not include the voiceOverNR field in the ims-Parameters parameter, that is, does not include the bolded part 2 of the above sub-body.
  • the gNB after receiving the capability information of the first UE, the gNB can determine that the UE does not have the VoNR capability according to the capability information of the first UE.
  • the action of the UE sending the first UE capability information to the gNB may be triggered according to any one of the following conditions:
  • the UE When the UE fails to establish a VoNR call continuously, and the number of consecutive failures reaches (greater than or equal to) the preset first threshold, it can send the first threshold to the gNB after the VoNR call fails to be established when the first threshold is reached.
  • UE capability information When the UE fails to establish a VoNR call continuously, and the number of consecutive failures reaches (greater than or equal to) the preset first threshold, it can send the first threshold to the gNB after the VoNR call fails to be established when the first threshold is reached.
  • the UE sends the first UE capability information to the gNB after the failure to establish the VoNR call at that time.
  • the VoNR call is successfully established, but if the UE detects abnormal voice quality during several consecutive VoNR calls, and the number of consecutive times of abnormal voice quality reaches (greater than or equal to) the preset second threshold , then the UE may send the first UE capability information to the gNB after the VoNR call that reaches the second threshold ends.
  • the UE may send the first UE capability information to the gNB in 5GS mobility management idle (5GMM-IDLE) mode.
  • 5GMM-IDLE 5GS mobility management idle
  • the 3GPP TS 24.501 technical specification defines the weeks when mobility and periodic registration updates are initiated, including that in some cases a UE in 5GS mobility management registered (5GMM-REGISTERED) mode shall send a registration request message to the AMF to Initiating the registration process for mobility and periodic registration updates, one of the cases includes when the UE in 5GMM-IDLE mode changes the radio capabilities of the NG-RAN.
  • the UE when the UE detects that the establishment of the VoNR call fails, the UE sends the first UE capability information to the gNB, which can be implemented through the following steps S101-S103:
  • Step S101 the UE sends a registration request message to the gNB.
  • the function of the registration request message is to indicate that the gNB needs to perform NG-RAN radio capability update.
  • the UE When the UE in 5GMM-IDLE mode changes the radio capability of NG-RAN, the UE shall include the 5GS update type element in the REGISTRATION REQUEST message of the registration request message and will be used in the NG-RAN-
  • the RCU bits are set to "NG-RAN radio function update required".
  • the 5GS update type element can contain the following fields:
  • NG-RAN-RCU can have two bit values:
  • the UE sends the gNB the bit value of the NG-RAN-RCU in the registration request message to the gNB in step S101 to indicate that the gNB needs to update the NG-RAN radio capability.
  • Step S102 the gNB sends a UE capability query message to the UE in response to the registration request message.
  • the gNB can send the UE capability query message to the UE through the RRC message.
  • the UE capability query message is used to request the UE's radio capability in NR or other radio capabilities.
  • the UE capability query message may be the UE Capability Enquiry message defined in the 3GPP TS36.331 technical specification, and the UE Capability Enquiry message also belongs to the RRC message.
  • the UE Capability Enquiry message is a UE Capability Enquiry message
  • the following fields may be included:
  • the UE capability query message in the embodiment of the present application can also be implemented in other message formats, which is not limited in the embodiment of the present application.
  • Step S103 the UE sends the first UE capability information to the gNB in response to the UE capability query message.
  • the first UE capability information is used to indicate to the gNB that the UE does not currently support the VoNR capability.
  • the first UE capability information when the first UE capability information is implemented with the UE-NR-Capability parameter, according to the content described earlier, the first UE capability information does not include the voiceOverNR field in the ims-Parameters parameter, that is, does not include the above sub-body plus Thick part 2. Then, for example, the IMS-Parameters parameter in the first UE capability information may only include the following content:
  • the first UE capability information in this embodiment of the present application may be implemented by other message formats besides the UE-NR-Capability parameter, which is not limited in this embodiment of the present application.
  • the gNB may consider that the UE does not have the VoNR capability according to the capability information of the first UE. Then, when the user makes a call again, since the gNB thinks that the UE does not currently support the VoNR capability, the gNB will reject the request to establish a dedicated bearer 5QI1 initiated by the 5GC, but trigger the EPS FB process to initiate a redirection or inter-RAT handover to the 5GC. Request and wait for the UE to fall back to the LTE network, and the EPC and eNB will provide voice services through VoLTE. Thereby, the abnormal situation of failing to establish a VoNR call is avoided from happening again, and the UE recovers from the abnormality of the VoNR call.
  • the first UE capability information sent by the UE to the gNB indicates to the gNB that the UE does not support the VoNR capability, this does not mean that the UE does not support the VoNR capability. In fact, the UE still Possess VoNR capability.
  • the UE just indicates a bona fide non-real information to the gNB, which makes the gNB think that the UE does not support the VoNR capability, so that the gNB handles the request to establish the dedicated bearer 5QI1 in a way that the UE does not support the VoNR capability, thereby improving the call-through rate.
  • the UE may send the first UE capability information to the gNB when it periodically registers for the 5GS service. For example, after the UE has registered to the 5GS service, the periodic registration can be triggered by a timer. Before triggering the periodic registration each time, the UE may judge whether any one of the above conditions for triggering the action of the UE to send the first UE capability information to the gNB is currently satisfied. If the conditions are met, the UE will send the first UE capability information to the gNB during this periodic registration. If the condition is not met, wait for the next cycle.
  • the following steps may also be performed:
  • Step S104 the UE detects whether the tracking area of the NR cell where it resides changes.
  • a tracking area is a concept established by the LTE system and the NR system for the location management of the UE, and its functions are similar to the location area (LA) and routing area (RA) of the 2G/3G system.
  • the 5GC can know the location of the UE in the 5GMM-IDLE mode, and page the UE when there is a data service demand.
  • a tracking area can contain one or more NR cells, and an NR cell can only belong to one tracking area. Therefore, when the NR tracking area where the UE resides changes, it means that the NR cell where the UE resides also changes. change, that is, the UE is handed over to another gNB.
  • the UE can send the UE once again to the gNB (here refers to the gNB corresponding to the NR cell currently accessed after the tracking area of the NR cell where the UE resides changes).
  • Capability information for the convenience of description, this UE capability information is referred to as the second UE capability information here, and the second UE capability information includes the field of voiceOverNR in the ims-Parameters parameter, that is, includes the bolded part 2 of the above sub-body.
  • the gNB can determine that the UE has the VoNR capability according to the capability information of the second UE.
  • the UE may send the second UE capability information to the gNB in 5GS mobility management idle (5GMM-IDLE) mode.
  • 5GMM-IDLE 5GS mobility management idle
  • the UE sending the second UE capability information to the gNB can be implemented through the following steps S105-S107:
  • Step S105 the UE sends a registration request message to the gNB.
  • Step S105 is the same as step S101, and the bit value of the NG-RAN-RCU in the 5GS update type element of the registration request message is 1, which is not repeated in this embodiment of the present application.
  • Step S106 the gNB sends a UE capability query message to the UE in response to the registration request message.
  • Step S106 is the same as step S102, which is not repeated in this embodiment of the present application.
  • Step S107 the UE sends the second UE capability information to the gNB in response to the UE capability query message.
  • the IMS-Parameters parameter of the second UE capability information includes parameters related to the VoNR capability, that is, the bolded part 2.
  • the gNB will start the voice dedicated bearer 5QI1 for initiating the VoNR call, and will not trigger the EPS FB. This enables the VoNR call capability to be restored.
  • the UE may wait for a period of time after sending the first UE capability information, and after the waiting period ends. Then check whether the NR tracking area where it resides has changed.
  • the waiting period may be, for example, 15 minutes, 30 minutes, 1 hour, 3 hours, etc., which is not limited in this embodiment of the present application. In this way, the UE can talk in the 4G network for a relatively long time, avoiding frequent occurrence of abnormal VoNR calls in a short period of time.
  • Embodiment (2) of the present application is used to enable the UE to have the ability to automatically recover from the abnormality when a RoHC abnormality occurs during a call.
  • FIG. 7 is a flowchart of Embodiment (2) of the information indication method provided by the present application.
  • the base station when a UE with RoHC capability registers for a 5GS service, it can report UE capability information indicating that it has RoHC capability to the gNB.
  • the UE registers for the 5GS service reference may be made to the content of Embodiment (1) of the present application, which will not be repeated here.
  • the UE capability information may be sent in a radio resource control RRC message.
  • the 3GPP TS 38.331 technical specification defines the RRC information parameters, which include the UE capability information element.
  • the UE capability information element contains the PDCP-Parameters parameters used to convey PDCP-related capabilities to the gNB.
  • PDCP-Parameters includes parameters related to the RoHC capability of the UE, for example:
  • the data types of parameters such as “profile0x0000” and “profile0x0001” are Boolean value BOOLEAN, TRUE means support, and FALSE means not support.
  • Different parameter items such as “profile0x0000” and “profile0x0001” represent different RoHC capabilities.
  • profile0x0001 corresponds to the real-time transport protocol (real-time transport protocol, RTP), user datagram protocol (UDP) and internet protocol (IP), when the value of "profile0x0001" is FALSE, it means that no RoHC is performed on RTP/UDP/IP packets, when "profile0x0001" When the value of ” is TRUE, it indicates that RoHC is performed on RTP/UDP/IP packets.
  • the protocol used by the IMS voice service is RTP/UDP/IP.
  • the UE has the RoHC capability
  • the UE registers for the 5GS service in the UE capability information element sent to the gNB, the PDCP-Parameters The value of "profile0x0001" in the parameter is "TRUE".
  • the gNB knows that the UE has the RoHC capability. Then, during the call, the RoHC function will be enabled between the UE and the gNB.
  • the UE can detect whether the RoHC is abnormal during the call. For example, when the RoHC decompression data stream is wrong or the compression is wrong, it is considered that the RoHC is abnormal. It can be understood that during the UE camping on 5GS, one or more calls may occur. The UE can detect whether the RoHC is abnormal during each call. If the RoHC is abnormal, it can send it to the gNB again after the call ends.
  • UE capability information for convenience of description, this UE capability information is referred to as the first UE capability information here, and the value of "profile0x0001" in the PDCP-Parameters parameter in the first UE capability information is "FALSE".
  • the gNB can determine that the UE does not have the RoHC capability according to the first UE capability information.
  • the UE may send the first UE capability information to the gNB in 5GS mobility management idle (5GMM-IDLE) mode.
  • 5GMM-IDLE 5GS mobility management idle
  • the sending of the first UE capability information by the UE to the gNB may be implemented through the following steps S201-S203:
  • Step S201 the UE sends a registration request message to the gNB.
  • Step S201 is the same as step S101, and the bit value of the NG-RAN-RCU in the 5GS update type element of the registration request message is 1, which is not repeated in this embodiment of the present application.
  • Step S202 the gNB sends a UE capability query message to the UE in response to the registration request message.
  • Step S202 is the same as step S102, which is not repeated in this embodiment of the present application.
  • Step S203 the UE sends the first UE capability information to the gNB in response to the UE capability query message.
  • the first capability message since the first capability message is used to indicate that the UE does not support the RoHC capability, the value of "profile0x0001" in the PDCP-Parameters parameter of the first UE capability information is "FALSE" (the Boolean values of other parameters in this embodiment of the present application do not detailed description).
  • the first capability message may include the following content:
  • the gNB may consider that the UE does not have the RoHC capability according to the first UE capability information. Then, when the user makes a call again, neither the gNB nor the UE will enable the RoHC function, so as to avoid the RoHC exception during the call and improve the call quality.
  • the first UE capability information sent by the UE to the gNB indicates to the gNB that the UE does not support the RoHC capability, this does not mean that the UE does not support the RoHC capability. Possess RoHC capability.
  • the UE just indicates a bona fide non-real information to the gNB, so that the gNB thinks that the UE does not support the RoHC capability.
  • the following steps may also be performed:
  • Step S204 the UE detects whether the NR tracking area where it resides changes.
  • the NR tracking area where the UE resides changes, it can send the UE capability information to the gNB again.
  • this UE capability information is referred to as the second UE capability information here.
  • the PDCP-Parameters of the second UE capability information The value of "profile0x0001" in the parameter is "TRUE". In this way, after receiving the capability information of the second UE, the gNB can determine that the UE has the RoHC capability according to the capability information of the second UE.
  • the UE may send the second UE capability information to the gNB in 5GS mobility management idle (5GMM-IDLE) mode.
  • 5GMM-IDLE 5GS mobility management idle
  • the UE sends the second UE capability information to the gNB can be implemented through the following steps S205-S207:
  • Step S205 the UE sends a registration request message to the gNB.
  • Step S205 is the same as step S201, and the bit value of the NG-RAN-RCU in the 5GS update type element of the registration request message is 1, which is not repeated in this embodiment of the present application.
  • Step S206 the gNB sends a UE capability query message to the UE in response to the registration request message.
  • Step S206 is the same as step S202, which is not repeated in this embodiment of the present application.
  • Step S206 the UE sends the second UE capability information to the gNB in response to the UE capability query message.
  • the RoHC function will be enabled to improve the transmission efficiency.
  • Embodiment (3) of the present application is used to enable the UE to automatically recover from an abnormal VoNR call when the VoNR call is abnormal, where the VoNR call here includes a failure to establish a VoNR call and an abnormal RoHC during the VoNR call.
  • FIG. 9 is a flowchart of Embodiment (3) of the information indication method provided by the present application.
  • Embodiment (3) of the present application is equivalent to the combination of Embodiment (1) and Embodiment (2).
  • the base station when a UE with VoNR capability and RoHC capability registers for a 5GS service, it can report UE capability information to the gNB to indicate that it has VoNR capability and RoHC capability.
  • the UE capability information may include, for example, the parameters related to the VoNR capability of the UE in the UE-NR-Capability (the bolded part 1) and the parameters related to the RoHC capability of the UE in the PDCP-Parameters, wherein "profile0x0001" in the PDCP-Parameters parameter is "TRUE".
  • the parameters related to the VoNR capability of the UE in the UE-NR-Capability the bolded part 1
  • the parameters related to the RoHC capability of the UE in the PDCP-Parameters wherein "profile0x0001" in the PDCP-Parameters parameter is "TRUE".
  • the gNB knows that the UE has the VoNR capability and RoHC capability. Then, when the user makes a call, the gNB will start the dedicated voice bearer for initiating the VoNR call, and the RoHC function will be enabled between the UE and the gNB during the call. And in the process of making a call, the UE can detect whether the establishment of a VoNR call fails, and whether there is a RoHC abnormality during the call. Furthermore, the sending of the capability information of the first UE to the gNB may be triggered according to the detection result, and the triggering conditions may refer to Embodiment (1) and Embodiment (2), which will not be repeated here.
  • the UE may send the first UE capability information to the gNB in 5GS mobility management idle (5GMM-IDLE) mode.
  • 5GMM-IDLE 5GS mobility management idle
  • the sending of the first UE capability information by the UE to the gNB may be implemented through the following steps S301-S303:
  • Step S301 the UE sends a registration request message to the gNB.
  • Step S301 is the same as step S101, and the bit value of the NG-RAN-RCU in the 5GS update type element of the registration request message is 1, which is not repeated in this embodiment of the present application.
  • Step S302 the gNB sends a UE capability query message to the UE in response to the registration request message.
  • Step S302 is the same as step S102, which is not repeated in this embodiment of the present application.
  • Step S303 the UE sends the first UE capability information to the gNB in response to the UE capability query message.
  • the first capability message since the first capability message is used to indicate that the UE does not support the VoNR capability and does not support the RoHC capability, the first UE capability information does not include the voiceOverNR field in the ims-Parameters parameter, and at the same time, the PDCP- The value of "profile0x0001" in the Parameters parameter is "FALSE".
  • the first capability message may include the following content:
  • the gNB may consider that the UE does not have the VoNR capability and that the UE does not have the RoHC capability according to the capability information of the first UE. Then, when the user makes a call again, the gNB will trigger the EPS FB process, and the EPC and the eNB will establish a call under the 4G network through VoLTE, and the RoHC function will not be enabled, so as to avoid abnormal VoNR calls and improve call reception. throughput and call quality.
  • the following steps may also be performed:
  • Step S304 the UE detects whether the NR tracking area where it resides changes.
  • the NR tracking area where the UE resides changes, it can send the UE capability information to the gNB again.
  • this UE capability information is referred to as the second UE capability information here, and the second UE capability information includes UE-NR.
  • the parameters related to the VoNR capability of the UE in Capability (the bolded part 1), and the parameters related to the RoHC capability of the UE in the PDCP-Parameters, where the value of "profile0x0001" in the PDCP-Parameters parameter is "TRUE".
  • the gNB may determine that the UE has the VoNR capability and the RoHC capability according to the capability information of the second UE.
  • the UE may send the second UE capability information to the gNB in 5GS mobility management idle (5GMM-IDLE) mode.
  • 5GMM-IDLE 5GS mobility management idle
  • the UE sends the second UE capability information to the gNB can be implemented through the following steps S305-S307:
  • Step S305 the UE sends a registration request message to the gNB.
  • Step S305 is the same as step S301, and the bit value of the NG-RAN-RCU in the 5GS update type element of the registration request message is 1, which is not repeated in this embodiment of the present application.
  • Step S306 the gNB sends a UE capability query message to the UE in response to the registration request message.
  • Step S306 is the same as step S302, which is not repeated in this embodiment of the present application.
  • Step S307 the UE sends the second UE capability information to the gNB in response to the UE capability query message.
  • the gNB knows that the UE currently supports the VoNR capability and the RoHC capability, it will enable the VoNR capability and the RoHC capability, so that the VoNR call capability can be recovery, and improve transmission efficiency.
  • the UE may wait for a period of time after sending the first UE capability information, and after the waiting period ends. Then check whether the NR tracking area where it resides has changed.
  • the waiting period may be, for example, 15 minutes, 30 minutes, 1 hour, 3 hours, etc., which is not limited in this embodiment of the present application. In this way, the UE can talk in the 4G network for a relatively long time, avoiding frequent occurrence of abnormal VoNR calls in a short period of time.
  • Embodiment (4) of the present application is used to enable the UE to automatically recover from the abnormality when the call between the UE and the base station (eg, gNB, ng-eNB, etc.) based on the negotiated voice codec is abnormal.
  • the base station eg, gNB, ng-eNB, etc.
  • FIG. 11 is a flowchart of Embodiment (4) of the information indication method provided by the present application.
  • Step S401 The UE detects whether the call based on the first voice codec is abnormal.
  • the UE and the gNB can establish a VoNR call.
  • the UE and the gNB will encode, decode and transmit voice data according to the negotiated voice codec scheme.
  • the voice codec based on the initial negotiation between the UE and the gNB may have abnormal conversations.
  • the voice codec based on the initial negotiation between the UE and the gNB is referred to as the first voice codec.
  • one or more VoNR calls may occur during the UE camping on the 5GS.
  • the UE can detect whether there is noise in the call. If there is noise in the call, and there are multiple consecutive calls, for example, the number of noises in multiple consecutive calls is greater than the preset third threshold, it is considered based on the first voice.
  • the codec call is abnormal.
  • Step S402 the UE sends a first request message to the gNB when detecting that the call based on the first voice codec is abnormal.
  • the first request message may be sent in a radio resource control message.
  • the UE may send a first request message to the gNB in a 5GS mobility management idle (5GMM-IDLE) mode after the call ends.
  • the first request message may be, for example, an INVITE message of a session initiation protocol (SIP), which carries the negotiated content of the second voice codec and is used to request the gNB to use the second voice codec in subsequent calls.
  • SIP session initiation protocol
  • the quality standard of the second speech codec is lower than the quality standard of the first speech codec.
  • the second voice codec may be AMR-WB.
  • the INVITE message may include, for example, the following fields, indicating that the UE wishes to negotiate with the gNB to use the AMR-WB, sampling rate 16KHz codec scheme for voice calls:
  • the second speech codec may be AMR.
  • the INVITE message may include, for example, the following fields, indicating that the UE wishes to negotiate with the gNB to use the AMR, sampling rate 8KHz codec scheme for voice calls:
  • the gNB will send a first response message to the UE, and the first response message may be a SIP 200/OK message.
  • the 200/OK message may include the following fields:
  • the 200/OK message may include the following fields:
  • the UE can continue to negotiate other voice codec schemes with the gNB by sending the INVITE message again, or continue to use the first voice codec scheme.
  • Step S403 when the UE receives the first response message, adjusts the voice codec scheme to the second voice codec.
  • the UE and the gNB can use the low-level second voice codec scheme to encode, decode and transmit voice data, which realizes the degraded processing of the voice codec scheme and avoids the use of high-level voice codecs.
  • There are abnormal communication problems such as noise, etc.
  • the following steps may also be performed:
  • Step S404 the UE sends a second request message to the gNB after waiting for the second time period.
  • the second request message is also an INVITE message, which carries the negotiated content of the first voice codec, and is used to request the gNB to use the first voice codec in subsequent calls.
  • the second voice codec may be AMR-WB.
  • the INVITE message may include, for example, the following fields, indicating that the UE wishes to negotiate with the gNB to restore from AMR-WB to using the EVS, sampling rate 16KHz codec scheme for voice calls:
  • the gNB will send a second response message to the UE, and the second response message may be a SIP 200/OK message.
  • the UE can continue to negotiate other voice codec schemes with the gNB by sending the INVITE message again, or continue to use the second voice codec scheme.
  • Step S405 when the UE receives the second response message, it adjusts the voice codec scheme to the first voice codec.
  • the UE can no longer negotiate the voice codec scheme with the gNB for a period of time after downgrading the voice codec scheme.
  • the UE considers the change of the network environment, so it negotiates with the network device to upgrade the voice codec scheme again. If the negotiation is successful, when the VoNR call is performed again, the UE and the gNB can use the high-level first voice
  • the codec scheme encodes, decodes and transmits voice data to achieve higher bandwidth and reduce delay jitter and packet loss during calls.
  • the following steps may also be performed:
  • Step S406 the UE detects whether the tracking area of the NR cell where it resides changes.
  • the UE may start to perform step S406 after adjusting the speech codec scheme to the second speech codec, or may perform step S406 after waiting for a period of time.
  • Step S407 when the tracking area changes, the UE sends a third request message to the gNB.
  • the gNB in steps S406 to S408 is performed in steps S401 to S401 to The gNBs in step S405 are different gNBs.
  • the third request message is also an INVITE message, and its format can be implemented with reference to the second request message.
  • the third request message carries the negotiated content of the first voice codec and is used to request the gNB to use the first voice codec in subsequent calls.
  • the gNB will send a third response message to the UE, and the third response message may be a SIP 200/OK message.
  • Step S408 when the UE receives the third response message, it adjusts the voice codec scheme to the first voice codec.
  • the UE can negotiate with the network device to upgrade the voice codec scheme again when the tracking area of the NR cell it camps on changes. If the negotiation is successful, when the VoNR call is performed again, the UE and the gNB can use the high-level first
  • the voice codec scheme encodes, decodes and transmits voice data to achieve higher bandwidth and reduce delay jitter and packet loss during calls.
  • the UE may negotiate with the gNB the speech codec scheme adopted by the call hold service.
  • the call hold service means that when two users use the UE for a call, one of them can make or receive a call from a third party without hanging up, and can switch between the two calls.
  • the call hold service may include a call hold hold state and a call hold release unhold state. For example, as shown in Figure 14, when user A is talking with user B, user A can talk with user C without hanging up the call. B can hear music or a "beep" call hold prompt sound in the UE; when user A ends the call with user C, user A can hang up the call with user C or put user A and user C into the hold state , and switch back to the call with user B. At this time, user A and user B enter the unhold state.
  • the UE can perform the following steps when initiating call hold:
  • Step S501 the UE sends a fourth request message to the gNB.
  • the fourth request message may be an INVITE message of a session initiation protocol (session initiation protocol, SIP), which carries the negotiated content of the first voice codec, and is used to request the gNB to use the first voice codec during the call hold period.
  • SIP session initiation protocol
  • the first speech codec is EVS.
  • the gNB may send a fourth reject message to the UE to indicate to the UE that it does not agree to use the first voice codec during call hold, the The fourth rejection message may be a 3xx to 6xx response message of the IMS; if the gNB has the ability to enable call hold under the first voice codec scheme, it may send a 200/OK response message to the UE to indicate to the UE that it agrees to During the call hold period, the first voice codec is used, so that the UE is in a call hold state under the first voice codec scheme.
  • Step S502 when the UE receives the fourth rejection message, it sends a fifth request message to the gNB.
  • the fifth request message may be an INVITE message of a session initiation protocol (SIP), which carries the negotiated content of the second voice codec and is used to request the gNB to use the second voice codec during the call hold period.
  • SIP session initiation protocol
  • the second speech codec is AMR-WB or AMR.
  • the gNB can send a 200/OK message to the UE to make the UE enter the call hold state under the second voice codec scheme; if the gNB Does not have the ability to enable call hold under the second voice codec, then the gNB can continue to send the fifth reject message to the UE, so that the UE continues to send the INVITE message for negotiating the lower-level voice codec to the gNB until the UE receives the 200/OK message.
  • the UE can also perform the following steps when the call is released from hold:
  • Step S503 the UE sends a sixth request message to the gNB.
  • the sixth request message may be an INVITE message of a session initiation protocol (SIP), which carries the negotiated content of the first voice codec, and is used to request the gNB to use the first voice codec when the call is released from hold.
  • SIP session initiation protocol
  • the first speech codec is EVS.
  • the gNB can send a sixth rejection message to the UE, and the sixth rejection message can be a 3xx to 6xx response message of the IMS; A 200/OK response message may be sent to the UE with the ability to perform call hold release under a voice codec scheme.
  • Step S504 when the UE receives the sixth rejection message, the UE sends the seventh request message to the gNB.
  • the seventh request message may be an INVITE message of a session initiation protocol (SIP), which carries the negotiated content of the second voice codec, and is used to request the gNB to use the second voice codec when the hold is released.
  • SIP session initiation protocol
  • the second speech codec is AMR-WB or AMR.
  • the gNB can send a 200/OK message to the UE to make the UE release the call hold state under the second voice codec scheme; if the gNB Does not have the ability to release the call hold under the second voice codec, then the gNB can continue to send the seventh reject message to the UE, so that the UE continues to send the INVITE message for negotiating the lower-level voice codec to the gNB until the UE receives the 200/OK message.
  • the UE and the gNB can negotiate to use the lower-level voice codec scheme to perform the call-hold task to avoid call hold or call hold release failure.
  • Embodiment (5) of the present application is used to enable the UE to have the ability to automatically recover from the abnormality when detecting that the base station (eg, gNB, ng-eNB, etc.) performs an EPS FB abnormally.
  • the base station eg, gNB, ng-eNB, etc.
  • the gNB needs to initiate a request to establish a dedicated bearer 5QI1 in the 5GC, according to the wireless access capability of the UE, the deployment of the N26 interface, the wireless conditions of LTE and The indication information of the access and mobility management function AMF determines whether the EPS FB process can be executed; if the EPS FB can be executed, it will fall back to the 4G network, and a dedicated bearer of VoLTE IMS voice will be established between the UE and the gNB.
  • EPS FB may be abnormal, for example, the IMS dedicated bearer for LTE cannot be established, resulting in call failure.
  • Embodiment (5) of the present application may include the following steps:
  • Step S701 the UE detects whether the switch domain redial EPS FB is abnormal.
  • the UE may initiate a call one or more times.
  • the abnormality of the EPS FB may include: during multiple calls, the UE fails to establish a dedicated IMS voice bearer for LTE more than a preset fourth threshold, or the UE and the gNB release a dedicated 5G voice bearer. The number of times of carrying 5QI1 is greater than the preset fifth threshold.
  • the EPS FB is abnormal.
  • Step S702 the UE turns off the NR capability when detecting that the EPS FB is abnormal in the domain switching and redialing.
  • the UE does not camp on the NR cell, but only searches for the LTE cell, and chooses to camp on the LTE cell, and does not support the N1NAS signaling mode.
  • the UE directly initiates a VoLTE call request or a call request in the CS domain to the gNB, avoiding the EPS FB process, thereby improving the call completion rate.
  • the gNB of the new NR cell may support EPS FB capability. Therefore, as shown in FIG. 17 , after turning off the NR capability, the UE can wait for a period of time and then restart the NR capability to re-search for the NR cell and camp on the NR cell.
  • the waiting period may be, for example, 15 minutes, 30 minutes, 1 hour, 3 hours, etc., which is not limited in this embodiment of the present application.
  • the waiting duration of the UE may be set by a timer, which is not described repeatedly in this embodiment of the present application.
  • the NR network is also used to transmit packet data
  • the UE capability may affect the user to use the UE to access the network, such as watching online videos and music, browsing web pages, and so on. Therefore, after the UE turns off the NR capability, the UE can detect whether the packet data transmission is continuously generated for a period of time, such as 10 seconds, 20 seconds, etc.; if the UE continuously generates the packet data transmission, the UE can turn on the NR capability again, so that Packet data is transmitted through NR to increase transmission speed.
  • the UE may also detect whether there is no packet data transmission for a period of time, or whether the total data flow of packet data transmission within a period of time is less than a flow threshold, for example, in Within 10 minutes, whether the total data flow of packet data transmission is less than 10MB; if the UE has no packet data transmission within a period of time, or the total data flow of packet data transmission within a period of time is less than a flow threshold, the UE can Turn off the NR capability again.
  • a flow threshold for example, in Within 10 minutes, whether the total data flow of packet data transmission is less than 10MB
  • the UE can detect whether the user has opened the dialing interface of the UE or the address book of the UE. The UE turns off the NR capability again, so that the UE falls back to 4G before the user completes the dialing. In this way, when the user completes the dialing and initiates a call, the UE directly initiates a request to establish a dedicated bearer to the EPC through the eNB to establish a VoLTE call, thus avoiding EPS FB. process to improve the call-through rate.
  • the UE can detect whether its own location is based on GNSS services (eg, Beidou satellite navigation system, global positioning system, etc.) or location based services (location based services, LBS). A significant change occurs, and when the location changes significantly, the NR capability is turned back on.
  • GNSS services eg, Beidou satellite navigation system, global positioning system, etc.
  • location based services location based services, LBS.
  • the UE may determine the location 1 where the NR capability is disabled based on the GNSS service or the LBS service. After that, the UE may continue to detect its own location 2 based on the GNSS service or the LBS service, and calculate The distance between location 1 and location 2. If the distance is greater than a preset distance threshold, such as 5 kilometers, 10 kilometers, etc., the NR capability is re-enabled.
  • a preset distance threshold such as 5 kilometers, 10 kilometers, etc.
  • the UE may continue to detect its own location 2 periodically based on the GNSS service or the LBS service; or, after the UE turns off the NR capability, the UE may trigger the detection of its own location 2 through certain conditions.
  • the trigger conditions may include, for example, the UE unlocks the screen, the UE opens an application APP that uses the GNSS service or the LBS service, the UE detects that the user has opened the UE dial interface or the UE address book, etc. This embodiment of the present application does not limit this.
  • the terminal device UE includes corresponding hardware structures and/or software modules for executing each function.
  • the present application can be implemented in hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • FIG. 18 is a schematic structural diagram of an information indicating device provided by an embodiment of the present application.
  • the UE may implement corresponding functions through the hardware device shown in FIG. 18 .
  • the information indicating apparatus may include: a transceiver 801 , a memory 802 and a processor 803 .
  • the processor 803 may include one or more processing units, for example, the processor 803 may include an application processor, a modem processor, a graphics processor, an image signal processor, a controller, a video Decoders, digital signal processors, baseband processors, and/or neural network processors, etc. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.
  • Memory 802 is coupled to processor 803 for storing various software programs and/or sets of instructions. In some embodiments, memory 802 may include volatile memory and/or non-volatile memory.
  • the transceiver 801 may include, for example, a radio frequency circuit, a mobile communication module, a wireless communication module, etc., for implementing the wireless communication function of the UE.
  • the UE when the software program and/or multiple sets of instructions in the memory 802 are executed by the processor 803, the UE is used to perform the following method steps: when registering for the 5GS service, reporting to the gNB to indicate that it has VoNR Capable UE capability information.
  • a registration request message is sent to the gNB.
  • the UE capability query message sent by the gNB in response to the registration request message is received.
  • the first UE capability information is sent to the gNB.
  • the first UE capability information does not include the voiceOverNR field in the ims-Parameters parameter, that is, does not include the bolded part 2 of the sub-body.
  • the gNB may consider that the UE does not have the VoNR capability according to the capability information of the first UE. Then, when the user makes a call again, since the gNB thinks that the UE does not currently support the VoNR capability, the gNB will reject the request to establish a dedicated bearer 5QI1 initiated by the 5GC, but trigger the EPS FB process to initiate a redirection or inter-RAT handover to the 5GC. Request and wait for the UE to fall back to the LTE network, and the EPC and eNB will provide voice services through VoLTE. Thereby, the abnormal situation of failing to establish a VoNR call is avoided from happening again, and the UE recovers from the abnormality of the VoNR call.
  • the UE is also used to perform the following method steps: detecting whether the NR tracking area where it resides has changed.
  • a registration request message is sent to the gNB.
  • the UE capability query message sent by the gNB in response to the registration request message is received.
  • the second UE capability information is sent to the gNB.
  • the IMS-Parameters parameter of the second UE capability information includes parameters related to the VoNR capability, that is, includes the bold part 2.
  • the gNB will start the voice dedicated bearer 5QI1 for initiating the VoNR call, and will not trigger the EPS FB. This enables the VoNR call capability to be restored.
  • the UE when the software program and/or multiple sets of instructions in the memory 802 are run by the processor 803, the UE is also used to perform the following method steps: after sending the first UE capability information, wait for a period of time, and the waiting period ends. Then, check whether the NR tracking area where it resides has changed.
  • the UE when the software program and/or multiple sets of instructions in the memory 802 are executed by the processor 803, the UE is used to perform the following method steps: when registering for the 5GS service, it can report to the gNB for indicating itself RoHC capable UE capability information. When detecting whether the RoHC is abnormal during the call, it sends a registration request message to the gNB. The UE capability query message sent by the gNB in response to the registration request message is received. In response to the UE capability query message, the first UE capability information is sent to the gNB. The value of "profile0x0001" in the PDCP-Parameters parameter of the first UE capability information is "FALSE".
  • the gNB may consider that the UE does not have the RoHC capability according to the first UE capability information. Then, when the user makes a call again, neither the gNB nor the UE will enable the RoHC function, so as to avoid the RoHC exception during the call and improve the call quality.
  • the UE is also used to perform the following method steps: detecting whether the NR tracking area where it resides has changed.
  • a registration request message is sent to the gNB.
  • the UE capability query message sent by the gNB in response to the registration request message is received.
  • the second UE capability information is sent to the gNB.
  • the value of "profile0x0001" in the PDCP-Parameters parameter of the second UE capability information is "TRUE".
  • the RoHC function will be enabled to improve the transmission efficiency.
  • the UE when the software program and/or multiple sets of instructions in the memory 802 are executed by the processor 803, the UE is used to perform the following method steps: when registering for the 5GS service, reporting to the gNB for indicating that it has UE capability information for VoNR capability and RoHC capability.
  • a registration request message is sent to the gNB.
  • the UE capability query message sent by the gNB in response to the registration request message is received.
  • the first UE capability information is sent to the gNB.
  • the first UE capability information does not include the voiceOverNR field in the ims-Parameters parameter, that is, does not include the bolded part 2 of the sub-body, and the value of "profile0x0001" in the PDCP-Parameters parameter of the first UE capability information is "FALSE" .
  • the gNB may consider that the UE does not have the VoNR capability and that the UE does not have the RoHC capability according to the capability information of the first UE. Then, when the user makes a call again, the gNB will trigger the EPS FB process, and the EPC and the eNB will establish a call under the 4G network through VoLTE, and the RoHC function will not be enabled, so as to avoid abnormal VoNR calls and improve call reception. throughput and call quality.
  • the UE when the software program and/or multiple sets of instructions in the memory 802 are executed by the processor 803, the UE is also used to perform the following method steps: detecting whether the NR tracking area where it resides has changed.
  • a registration request message is sent to the gNB.
  • the UE capability query message sent by the gNB in response to the registration request message is received.
  • the second UE capability information is sent to the gNB.
  • the IMS-Parameters parameter of the second UE capability information includes parameters related to the VoNR capability, that is, the bolded part 2, and the value of "profile0x0001" in the PDCP-Parameters parameter of the second UE capability information is "TRUE" .
  • the gNB knows that the UE currently supports the VoNR capability and the RoHC capability, it will enable the VoNR capability and the RoHC capability, so that the VoNR call capability can be recovery, and improve transmission efficiency.
  • the UE when the software program and/or multiple sets of instructions in the memory 802 are executed by the processor 803, the UE is configured to perform the following method steps: detecting whether the call based on the first voice codec is abnormal. When an abnormal call based on the first voice codec is detected, a first request message is sent to the gNB. Receive the first response message sent by the gNB to the UE when it agrees to use the second voice codec scheme for a voice call, where the first response message may be a 200/OK message of SIP. When the first response message is received, the voice codec scheme is adjusted to the second voice codec.
  • the UE and the gNB can use the low-level second voice codec scheme to encode, decode and transmit voice data, which realizes the degraded processing of the voice codec scheme and avoids the use of high-level voice codecs.
  • There are abnormal communication problems such as noise, etc.
  • the UE when the software program and/or multiple sets of instructions in the memory 802 are run by the processor 803, the UE is also used to perform the following method steps: after adjusting the voice codec scheme to the second voice codec, wait for the first voice codec. For the second time period, send a second request message to the gNB.
  • the receiving gNB sends a second response message to the UE when agreeing to restore to the first voice codec scheme for a voice call, where the second response message may be a SIP 200/OK message.
  • the second response message adjust the voice codec scheme to the first voice codec.
  • the UE can no longer negotiate the voice codec scheme with the gNB for a period of time after downgrading the voice codec scheme.
  • the UE considers the change of the network environment, so it negotiates with the network device to upgrade the voice codec scheme again. If the negotiation is successful, when the VoNR call is performed again, the UE and the gNB can use the high-level first voice
  • the codec scheme encodes, decodes and transmits voice data to achieve higher bandwidth and reduce delay jitter and packet loss during calls.
  • the UE when the software program and/or multiple sets of instructions in the memory 802 are run by the processor 803, the UE is also used to perform the following method steps: after adjusting the voice codec scheme to the second voice codec, detect itself. Whether the resident NR tracking area has changed. When the tracking area changes, the UE sends a second request message to the gNB. The receiving gNB sends a second response message to the UE when agreeing to restore to the first voice codec scheme for a voice call, where the second response message may be a SIP 200/OK message. When receiving the second response message, adjust the voice codec scheme to the first voice codec.
  • the UE can negotiate with the network device to upgrade the voice codec scheme again when the tracking area of the NR cell it camps on changes. If the negotiation is successful, when the VoNR call is performed again, the UE and the gNB can use the high-level first
  • the voice codec scheme encodes, decodes and transmits voice data to achieve higher bandwidth and reduce delay jitter and packet loss during calls.
  • the UE when the software program and/or multiple sets of instructions in the memory 802 are run by the processor 803, the UE is also used to perform the following method steps: when initiating call hold, send a third request message to the gNB, and the third The request message is used to request the gNB to use the first voice codec during call hold.
  • send a fourth request message to the gNB When receiving the first rejection message from the gNB, send a fourth request message to the gNB.
  • the first rejection message is that the gNB responds to the third request message and sends the of.
  • a fourth request message is sent to the gNB, where the fourth request message is used to request the gNB to use the second voice codec during the call hold period.
  • the UE when the software program and/or multiple sets of instructions in the memory 802 are run by the processor 803, the UE is also used to perform the following method steps: when the call hold is released, send a fifth request message to the gNB, and the fifth request message is sent to the gNB.
  • the request message is used to request the gNB to use the first voice codec when the call hold is released.
  • send the sixth request message When receiving the second rejection message from the gNB, send the sixth request message to the gNB.
  • the second rejection message is that the gNB responds to the fifth request message and sends the of.
  • a sixth request message is sent to the gNB, where the sixth request message is used to request the gNB to use the second voice codec when releasing the hold.
  • the UE and the gNB can negotiate to use the lower-level voice codec scheme to perform the call-hold task to avoid call hold or call hold release failure.
  • the UE when the software program and/or multiple sets of instructions in the memory 802 are executed by the processor 803, the UE is used to perform the following method steps: detecting whether the switch domain redial EPS FB is abnormal. Turn off the NR capability when an abnormality of the EPS FB is detected.
  • the UE does not camp on the NR cell, but only searches for the LTE cell, and chooses to camp on the LTE cell, and does not support the N1NAS signaling mode.
  • the UE directly initiates a VoLTE call request or a call request in the CS domain to the gNB, avoiding the EPS FB process, thereby improving the call completion rate.
  • the UE when the software program and/or multiple sets of instructions in the memory 802 are executed by the processor 803, the UE is also used to perform the following method steps: after the NR capability is disabled, wait for a period of time, and then restart the NR capability.
  • the UE when the software program and/or multiple sets of instructions in the memory 802 are executed by the processor 803, the UE is also used to perform the following method steps: detecting whether the packet data transmission is continuously generated within a period of time, and if continuously Generate packet data transmission, restart NR capability.
  • the UE may implement corresponding functions through software modules.
  • the information indicating apparatus for realizing the above-mentioned function of the behavior of the terminal equipment UE includes: a receiving unit 901 , a processing unit 902 and a sending unit 903 .
  • the sending unit 903 is configured to report UE capability information to the gNB for indicating that it has VoNR capability when the UE registers for the 5GS service.
  • the processing unit 902 is configured to detect whether the establishment of the VoNR call fails.
  • the sending unit 903 is further configured to send a registration request message to the gNB when it is detected that the establishment of the VoNR call fails.
  • the receiving unit 901 is configured to receive the UE capability query message sent by the gNB in response to the registration request message.
  • the sending unit 903 is further configured to send the first UE capability information to the gNB in response to the UE capability query message.
  • the first UE capability information does not include the voiceOverNR field in the ims-Parameters parameter, that is, does not include the bolded part 2 of the sub-body.
  • the processing unit 902 is further configured to detect whether the NR tracking area where it resides changes.
  • the sending unit 903 is further configured to send a registration request message to the gNB when the camped NR tracking area changes.
  • the receiving unit 901 is further configured to receive the UE capability query message sent by the gNB in response to the registration request message.
  • the sending unit 903 is further configured to send the second UE capability information to the gNB in response to the UE capability query message.
  • the IMS-Parameters parameter of the second UE capability information includes parameters related to the VoNR capability, that is, includes the bold part 2.
  • the sending unit 903 is further configured to wait for a period of time after sending the capability information of the first UE, and then detect whether the NR tracking area where it resides changes after the waiting period ends.
  • the sending unit 903 is configured to report UE capability information to the gNB for indicating that it has RoHC capability when the UE registers for the 5GS service.
  • the processing unit 902 is used to detect whether the RoHC is abnormal.
  • the sending unit 903 is further configured to send a registration request message to the gNB when it is detected whether the RoHC is abnormal during the call.
  • the receiving unit 901 is configured to receive the UE capability query message sent by the gNB in response to the registration request message.
  • the sending unit 903 is further configured to send the first UE capability information to the gNB in response to the UE capability query message.
  • the value of "profile0x0001" in the PDCP-Parameters parameter of the first UE capability information is "FALSE".
  • the processing unit 902 is further configured to detect whether the NR tracking area where it resides changes.
  • the sending unit 903 is further configured to send a registration request message to the gNB when the camped NR tracking area changes.
  • the sending unit 903 is further configured to send the second UE capability information to the gNB in response to the UE capability query message.
  • the value of "profile0x0001" in the PDCP-Parameters parameter of the second UE capability information is "TRUE".
  • the sending unit 903 is configured to report UE capability information to the gNB for indicating that it has VoNR capability and RoHC capability when the UE registers for the 5GS service.
  • the processing unit 902 is configured to detect whether the establishment of the VoNR call fails or whether the RoHC is abnormal during the call.
  • the sending unit 903 is configured to send a registration request message to the gNB when it is detected that the establishment of the VoNR call fails or whether the RoHC is abnormal during the call.
  • the receiving unit 901 is configured to receive the UE capability query message sent by the gNB in response to the registration request message.
  • the sending unit 903 is further configured to send the first UE capability information to the gNB in response to the UE capability query message.
  • the first UE capability information does not include the voiceOverNR field in the ims-Parameters parameter, that is, does not include the bolded part 2 of the sub-body, and the value of "profile0x0001" in the PDCP-Parameters parameter of the first UE capability information is "FALSE" .
  • the processing unit 902 is further configured to detect whether the NR tracking area where it resides changes.
  • the sending unit 903 is further configured to send a registration request message to the gNB when the camped NR tracking area changes.
  • the receiving unit 901 is further configured to receive the UE capability query message sent by the gNB in response to the registration request message.
  • the sending unit 903 is further configured to send the second UE capability information to the gNB in response to the UE capability query message.
  • the IMS-Parameters parameter of the second UE capability information includes parameters related to the VoNR capability, that is, the bolded part 2, and the value of "profile0x0001" in the PDCP-Parameters parameter of the second UE capability information is "TRUE" .
  • the processing unit 902 is configured to detect whether the call based on the first voice codec is abnormal.
  • the sending unit 903 is configured to send a first request message to the gNB when the call based on the first voice codec is abnormal.
  • the receiving unit 901 is configured to receive a first response message sent by the gNB to the UE when it agrees to use the second voice codec scheme for a voice call, where the first response message may be a 200/OK message of SIP.
  • the processing unit 902 is further configured to adjust the voice codec scheme to the second voice codec when receiving the first response message.
  • the sending unit 903 is further configured to wait for a second time period after the voice codec scheme is adjusted to the second voice codec, and send the second request message to the gNB.
  • the receiving unit 901 is further configured to receive a second response message sent by the gNB to the UE when the gNB agrees to restore to the first voice codec scheme for a voice call, where the second response message may be a SIP 200/OK message.
  • the processing unit 902 is further configured to adjust the voice codec scheme to the first voice codec when receiving the second response message.
  • the sending unit 903 is further configured to send a fourth request message to the gNB when the call hold is initiated, where the fourth request message is used to request the gNB to use the first voice codec during the call hold period.
  • the sending unit 903 is further configured to send a fifth request message to the gNB when the receiving unit 901 receives the fourth rejection message of the gNB, and the fourth rejection message is that the gNB does not have the ability to enable call hold under the first voice codec scheme.
  • the fifth request message is used to request the gNB to use the second voice codec during the call hold period in response to the fourth request message being sent.
  • the sending unit 903 is further configured to send a sixth request message to the gNB when the call hold is released, where the sixth request message is used to request the gNB to use the first voice codec when the call hold is released.
  • the sending unit 903 is further configured to send the seventh request message to the gNB when the receiving unit 901 receives the sixth rejection message of the gNB, and the sixth rejection message is that the gNB does not have the ability to release the call hold under the first voice codec scheme.
  • the seventh request message is used to request the gNB to use the second voice codec when releasing the hold.
  • the processing unit 902 is configured to detect whether the swap domain redial EPS FB is abnormal.
  • the processing unit 902 is further configured to disable the NR capability when an abnormality of the switch domain redial EPS FB is detected.
  • the embodiments of the present application further provide a computer storage medium, where computer instructions are stored in the computer storage medium, and when the computer storage medium runs on the computer, the computer can execute the methods of the above aspects.
  • Embodiments of the present application also provide a computer program product containing instructions, which, when run on a computer, cause the computer to execute the methods of the above aspects.
  • the present application also provides a chip system.
  • the chip system includes a processor for supporting the above-mentioned apparatus or device to implement the functions involved in the above-mentioned aspects, for example, generating or processing the information involved in the above-mentioned methods.
  • the chip system further includes a memory for storing necessary program instructions and data of the above-mentioned apparatus or device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供了一种网络系统和终端设备UE。其中，UE能够在检测到VoNR通话异常时，向其驻留的NR小区对应的第一基站发送注册请求消息；第一基站能够响应于注册请求消息，向UE发送UE能力查询消息；UE还能够响应于UE能力查询消息，向第一基站发送第一UE能力信息，第一UE能力信息用于向第一基站指示UE不支持VoNR能力和/或者不支持鲁棒头压缩RoHC能力。这样，第一基站在接收到第一UE能力信息之后，就可以根据第一UE能力信息认为UE不具备VoNR能力或RoHC能力。那么，当用户再次拨打电话时，第一基站会根据第一UE能力信息的指示触发EPS FB流程，由EPC和eNB通过VoLTE在4G网络下建立通话，或者不启用RoHC功能，从而避免VoNR通话异常的现象发生，提高通话的接通率和通话质量。

Description

一种网络系统和终端设备
本申请要求于2020年09月07日提交到国家知识产权局、申请号为202010928283.1、发明名称为“一种网络系统和终端设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种网络系统和终端设备。
背景技术
5G新空口(new radio，NR)是一种新的无线接入技术(radio access technology，RAT)，由第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)开发，用于5G移动通信网络，是5G网络空中接口的全球通用标准。5G移动通信网络基于IP多媒体子系统(IP multimedia subsystem，IMS)提供语音业务，其上面承载的语音通话业务称之为voice on NR(VoNR)，目前，5G的IMS话音业务以VoLTE(在4G网络承载上语音通话业务)、VoNR等不同接入方式存在。具体来说，就是在5G NR系统组网初期不提供语音业务时，以VoLTE等作为语音业务的过渡方案，将VoNR作为5G独立组网(SA)的最终语音业务解决方案，由VoLTE逐渐向VoNR演进。
那么，在5G NR系统组网初期，由于5G组网部署选项不同、5G网络覆盖规模不同、网络侧的基站和核心网的各网元的兼容性和工作状态好坏、终端设备UE生态系统的成熟度不同、5G语音业务的编码标准不同、以及鲁棒性的头域压缩RoHC的能力不同等因素的影响，VoNR在5G网络的部署前期无法保证提供稳定的语音服务，导致UE在5G网络下出现各种通话异常的情况。
发明内容
本申请实施例提供了一种网络系统和终端设备，能够解决5G NR系统组网初期，UE在5G网络下容易出现通话异常的问题。
第一方面，本申请实施例提供了一种网络系统，包括：第一基站，以及驻留在第一基站的第一新空口NR小区的终端设备UE；UE用于在检测到VoNR通话异常时，向第一基站发送注册请求消息；第一基站用于响应于注册请求消息，向UE发送UE能力查询消息；UE还用于响应于UE能力查询消息，向第一基站发送第一UE能力信息，第一UE能力信息用于向第一基站指示UE不支持VoNR能力和/或者不支持鲁棒头压缩RoHC能力。
这样，第一基站在接收到第一UE能力信息之后，就可以根据第一UE能力信息认为UE不具备VoNR能力或者UE不具备RoHC能力。那么，当用户再次拨打电话时，第一基站会根据第一UE能力信息的指示触发EPS FB流程，由EPC和eNB通过VoLTE在4G网络下建立通话，或者不启用RoHC功能，从而避免VoNR通话异常的现象发生，提高通话的接通率和通话质量。
在一种实现方式中，VoNR通话异常包括在UE主叫或者被叫场景下建立VoNR通话失败，第一UE能力信息用于向第一基站指示UE不支持VoNR能力。这样，第一基站在接收到第一 UE能力信息之后，就可以根据第一UE能力信息认为UE不具备VoNR能力。那么，当用户再次拨打电话时，由于第一基站认为UE当前不支持VoNR能力，因此第一基站会拒绝5GC发起的建立专用承载5QI1的请求，而是触发EPS FB流程，向5GC发起重定向或者inter-RAT切换请求，并等待UE回落到LTE网络，由EPC和eNB通过VoLTE提供语音服务。由此，避免建立VoNR通话失败的异常情况再次发生，UE从VoNR通话异常中恢复。
在一种实现方式中，VoNR通话异常包括VoNR通话过程中出现RoHC异常，第一UE能力信息用于向第一基站指示UE不支持RoHC能力。这样，第一基站在接收到第一UE能力信息之后，就可以根据第一UE能力信息认为UE不具备RoHC能力。那么，当用户再次拨打电话时，第一基站和UE都不会启用RoHC功能，避免在通话过程中出现RoHC异常，以提高通话质量。
在一种实现方式中，VoNR通话异常包括UE主叫或者被叫场景下建立VoNR通话失败或者VoNR通话过程中出现RoHC异常，第一UE能力信息用于向第一基站指示UE不支持VoNR能力和不支持RoHC能力。这样，第一基站在接收到第一UE能力信息之后，就可以根据第一UE能力信息认为UE不具备VoNR能力，以及认为UE不具备RoHC能力。那么，当用户再次拨打电话时，第一基站会触发EPS FB流程，由EPC和eNB通过VoLTE在4G网络下建立通话，并且也不会启用RoHC功能，从而避免VoNR通话异常的现象发生，提高通话的接通率和通话质量。
在一种实现方式中，UE具体用于在UE主叫或者被叫场景下建立VoNR通话失败的连续次数大于预设第一阈值时，向第一基站发送注册请求消息。
在一种实现方式中，UE具体用于在检测到VoNR通话异常时，在VoNR通话结束之后的移动管理空闲5GMM-IDLE模式下向第一基站发送注册请求消息。
在一种实现方式中，UE还用于向第一基站发送第一UE能力信息之后，检测自身驻留的NR小区是否从第一NR小区切换到第二NR小区，第一NR小区和第二NR小区的跟踪区不同；UE还用于在检测到自身驻留的NR小区从第一NR小区切换到第二NR小区时，向第二NR小区对应的第二基站发送注册请求消息；第二基站用于响应于注册请求消息，向UE发送UE能力查询消息；UE还用于响应于UE能力查询消息，向第二基站发送第二UE能力信息，第二UE能力信息用于向第二基站指示UE支持VoNR能力和/或者支持RoHC能力。这样，在UE驻留在新的跟踪区的NR小区期间，当用户再次拨打电话时，由于第二基站认为UE当前支持VoNR能力，第二基站会启动建立VoNR通话的语音专用承载5QI1，不会触发EPS FB，使得VoNR通话能力得以恢复。
在一种实现方式中，UE具体用于在建立VoNR通话失败的连续次数大于预设第二阈值时，等待第一预设时长，然后检测自身驻留的NR小区是否从第一NR小区切换到第二NR小区。这样，UE可以避免自身在短时间内继续出现建立VoNR通话失败的情况发生，提高接通率。
第二方面，本申请实施例提供了一种网络系统，包括：第一基站，以及驻留在第一基站的第一NR小区的终端设备UE；UE用于在检测到基于第一语音编解码的通话异常时，向第一基站发送第一请求消息，第一语音编解码是UE与第一基站当前使用的语音编解码方案，第一请求消息用于请求第一基站使用第二语音编解码，第二语音编解码的质量标准低于第一语音编解码的质量标准；第一基站用于响应于第一请求消息，向UE发送第一应答消息，第一应答消息用于向UE指示第一基站同意使用第二语音编解码；UE还用于响应于第一应答消息，将当前使用的语音编解码方案调整为第二语音编解码。
这样，当再一次执行VoNR通话时，UE和第一基站就可以使用低级别的第二语音编解码方案编解码和传输语音数据，实现了语音编解码方案的降级处理，避免采用高等级的语音编解码方案而出现杂音等通话异常问题。
在一种实现方式中，UE还用于在当前使用的语音编解码方案调整为第二语音编解码之后，等待第二预设时长，然后向第一基站发送第二请求消息，第二请求消息用于请求第一基站使用第一语音编解码；第一基站还用于响应于第二请求消息，向UE发送第二应答消息，第二应答消息用于向UE指示第一基站同意使用第一语音编解码；UE还用于响应于第二应答消息，将当前使用的语音编解码方案调整为第一语音编解码。这样，通过等待第二时长，UE可以在降级语音编解码方案之后的一段时间内不再与第一基站协商语音编解码方案。在等待第二时长之后，UE考虑到网络环境发生变化，因此再次与网络设备协商升级语音编解码方案，如果协商成功，当再次执行VoNR通话时，UE和第一基站就可以使用高级别的第一语音编解码方案编解码和传输语音数据，以实现更高的带宽和减少通话时的延迟抖动和丢包。
在一种实现方式中，第一基站用于响应于第一请求消息，向UE发送第一拒绝消息，第一拒绝消息用于向UE指示第一基站不同意使用第二语音编解码；UE还用于响应于第一拒绝消息，继续使用第一语音编解码。
在一种实现方式中，第一基站还用于响应于第二请求消息，向UE发送第二拒绝消息，第二拒绝消息用于向UE指示第一基站不同意使用第一语音编解码；UE还用于响应于第二拒绝消息，继续使用第二语音编解码。
在一种实现方式中，UE还用于在当前使用的语音编解码方案调整为第二语音编解码之后，检测自身驻留的NR小区是否从第一NR小区切换到第二NR小区，第一NR小区和第二NR小区的跟踪区不同；UE还用于在检测到自身驻留的NR小区从第一NR小区切换到第二NR小区时，向第二NR小区对应的第二基站发送第三请求消息，第三请求消息用于请求第二基站使用第一语音编解码；第二基站还用于响应于第三请求消息，向UE发送第三应答消息，第三应答消息用于向UE指示第二基站同意使用第一语音编解码；UE还用于响应于第三应答消息，将当前使用的语音编解码方案调整为第一语音编解码。这样，UE可以在驻留的NR小区的跟踪区发生变化时，再次与网络设备协商升级语音编解码方案，如果协商成功，当再次执行VoNR通话时，UE和第二基站就可以使用高级别的第一语音编解码方案编解码和传输语音数据，以实现更高的带宽和减少通话时的延迟抖动和丢包。
在一种实现方式中，基于第一语音编解码的通话异常包括：基于第一语音编解码的通话出现杂音，并且杂音的通话次数连续地大于预设第二阈值。
在一种实现方式中，当UE在通话过程中发起呼叫保持hold时：UE还用于向第一基站发送第四请求消息，第四请求消息用于请求第一基站在呼叫保持期间使用第一语音编解码；第一基站还用于响应于第四请求消息，向UE发送第四应答消息，第四应答消息用于向UE指示第一基站同意在呼叫保持期间使用第一语音编解码。
在一种实现方式中，第一基站还用于响应于第四请求消息，向UE发送第四拒绝消息，第四拒绝消息用于向UE指示第一基站不同意在呼叫保持期间使用第一语音编解码；UE还用于响应于第四拒绝消息，向第一基站发送第五请求消息，第五请求消息用于请求第一基站在呼叫保持期间使用第二语音编解码。
这样，在第一基站不支持更高级的语音编解码方案下的呼叫保持业务时，UE和第一基站可以协商使用更低级的语音编解码方案执行呼叫保持任务，以避免呼叫保持失败。
在一种实现方式中，当UE在通话过程中发起呼叫保持解除unhold时：UE还用于向第一基站发送第六请求消息，第六请求消息用于请求第一基站在呼叫保持解除之后使用第一语音编解码；第一基站还用于响应于第六请求消息，向UE发送第六应答消息，第六应答消息用于向UE指示第一基站同意在呼叫保持解除之后使用第一语音编解码。
在一种实现方式中，第一基站还用于响应于第六请求消息，向UE发送第六拒绝消息，第六拒绝消息用于向UE指示第一基站不同意在呼叫保持解除之后使用第一语音编解码；UE还用于响应于第六拒绝消息，向第一基站发送第七请求消息，第七请求消息用于请求第一基站在呼叫保持解除之后使用第二语音编解码。
这样，在第一基站不支持更高级的语音编解码方案下的呼叫保持业务时，UE和第一基站可以协商使用更低级的语音编解码方案执行呼叫保持任务，以避免呼叫保持解除失败。
第三方面，本申请实施例提供了一种网络系统，包括：第一基站，以及驻留在第一基站的NR小区的终端设备UE；UE用于在检测到换域重拨EPS FB异常时，关闭NR能力；UE还用于在关闭NR能力之后，等待第三预设时长，然后开启NR能力。
这样，UE就不会驻留在NR小区，而是只搜索LTE小区，并且选择在LTE小区驻留，同时不支持N1NAS信令模式。当用户拨打电话时，UE直接向第一基站发起VoLTE通话请求或者CS域的通话请求，避免执行EPS FB流程，从而提高呼通率。
在一种实现方式中，UE还用于在关闭NR能力之后，如果检测到连续产生分组数据传输，并且分组数据传输产生的总数据流量大于预设的流量阈值，则开启NR能力。
在一种实现方式中，UE还用于在关闭NR能力之后，如果检测到自身的位置变化距离大于预设的距离阈值，则开启NR能力。
在一种实现方式中，UE关闭NR能力，包括：UE不再驻留NR小区，同时搜索长期演进技术LTE小区，并且在LTE小区驻留。
在一种实现方式中，UE开启NR能力，包括：UE搜索NR小区，并且在NR小区驻留。
在一种实现方式中，EPS FB异常，包括：在UE主叫或者被叫的通话场景下，UE释放与第一基站的5G语音专用承载失败，或者，UE与第二基站建立LTE语音专用承载失败，第二基站为LTE小区对应的基站。
在一种实现方式中，EPS FB异常，包括：在UE主叫或者被叫的通话场景下，UE释放与第一基站的5G语音专用承载失败，并且连续失败的次数大于预设第四阈值，或者，UE与第二基站建立LTE语音专用承载失败，并且连续失败的次数大于预设第五阈值。
第四方面，本申请实施提供了一种终端设备，包括：收发器、存储器和处理器，存储器存储有计算机程序指令，当程序指令被处理器执行时，使得终端设备实现如下方法步骤：在检测到VoNR通话异常时，向第一基站发送注册请求消息；响应于UE能力查询消息，向第一基站发送第一UE能力信息，其中，UE能力查询消息是第一基站响应于注册请求消息向UE发送的，第一UE能力信息用于向第一基站指示UE不支持VoNR能力和/或者不支持鲁棒头压缩RoHC能力。
这样，第一基站在接收到第一UE能力信息之后，就可以根据第一UE能力信息认为UE不具备VoNR能力或者UE不具备RoHC能力。那么，当用户再次拨打电话时，第一基站会根据第一UE能力信息的指示触发EPS FB流程，由EPC和eNB通过VoLTE在4G网络下建立通话，或者不启用RoHC功能，从而避免VoNR通话异常的现象发生，提高通话的接通率和通话质量。
在一种实现方式中，VoNR通话异常包括在UE主叫或者被叫场景下建立VoNR通话失败，第一UE能力信息用于向第一基站指示UE不支持VoNR能力。这样，第一基站在接收到第一UE能力信息之后，就可以根据第一UE能力信息认为UE不具备VoNR能力。那么，当用户再次拨打电话时，由于第一基站认为UE当前不支持VoNR能力，因此第一基站会拒绝5GC发起的建立专用承载5QI1的请求，而是触发EPS FB流程，向5GC发起重定向或者inter-RAT切换请求，并等待UE回落到LTE网络，由EPC和eNB通过VoLTE提供语音服务。由此，避免建立VoNR通话失败的异常情况再次发生，UE从VoNR通话异常中恢复。
在一种实现方式中，VoNR通话异常包括VoNR通话过程中出现RoHC异常，第一UE能力信息用于向第一基站指示UE不支持RoHC能力。这样，第一基站在接收到第一UE能力信息之后，就可以根据第一UE能力信息认为UE不具备RoHC能力。那么，当用户再次拨打电话时，第一基站和UE都不会启用RoHC功能，避免在通话过程中出现RoHC异常，以提高通话质量。
在一种实现方式中，VoNR通话异常包括UE主叫或者被叫场景下建立VoNR通话失败或者VoNR通话过程中出现RoHC异常，第一UE能力信息用于向第一基站指示UE不支持VoNR能力和不支持RoHC能力。这样，第一基站在接收到第一UE能力信息之后，就可以根据第一UE能力信息认为UE不具备VoNR能力，以及认为UE不具备RoHC能力。那么，当用户再次拨打电话时，第一基站会触发EPS FB流程，由EPC和eNB通过VoLTE在4G网络下建立通话，并且也不会启用RoHC功能，从而避免VoNR通话异常的现象发生，提高通话的接通率和通话质量。
在一种实现方式中，当程序指令被处理器执行时，使得终端设备具体实现如下方法步骤：在UE主叫或者被叫场景下建立VoNR通话失败的连续次数大于预设第一阈值时，向第一基站发送注册请求消息。
在一种实现方式中，当程序指令被处理器执行时，使得终端设备具体实现如下方法步骤：在检测到VoNR通话异常时，在VoNR通话结束之后的移动管理空闲5GMM-IDLE模式下向第一基站发送注册请求消息。
在一种实现方式中，当程序指令被处理器执行时，还使得终端设备实现如下方法步骤：向第一基站发送第一UE能力信息之后，检测自身驻留的NR小区是否从第一NR小区切换到第二NR小区，第一NR小区和第二NR小区的跟踪区不同；在检测到自身驻留的NR小区从第一NR小区切换到第二NR小区时，向第二NR小区对应的第二基站发送注册请求消息；响应于第二基站发送的UE能力查询消息，向第二基站发送第二UE能力信息，第二UE能力信息用于向第二基站指示UE支持VoNR能力和/或者支持RoHC能力。这样，在UE驻留在新的跟踪区的NR小区期间，当用户再次拨打电话时，由于第二基站认为UE当前支持VoNR能力，第二基站会启动建立VoNR通话的语音专用承载5QI1，不会触发EPS FB，使得VoNR通话能力得以恢复。
在一种实现方式中，当程序指令被处理器执行时，使得终端设备具体实现如下方法步骤：在建立VoNR通话失败的连续次数大于预设第二阈值时，等待第一预设时长，然后检测自身驻留的NR小区是否从第一NR小区切换到第二NR小区。这样，UE可以避免自身在短时间内继续出现建立VoNR通话失败的情况发生，提高接通率。
第五方面，本申请实施例提供了一种终端设备，包括：收发器、存储器和处理器，存储器存储有计算机程序指令，当程序指令被处理器执行时，使得终端设备实现如下方法步骤： 在检测到基于第一语音编解码的通话异常时，向第一基站发送第一请求消息，第一语音编解码是UE与第一基站当前使用的语音编解码方案，第一请求消息用于请求第一基站使用第二语音编解码，第二语音编解码的质量标准低于第一语音编解码的质量标准；响应于第一应答消息，将当前使用的语音编解码方案调整为第二语音编解码，其中，第一应答消息是第一基站响应于第一请求消息发送的，第一应答消息用于向UE指示第一基站同意使用第二语音编解码。
这样，当再一次执行VoNR通话时，UE和第一基站就可以使用低级别的第二语音编解码方案编解码和传输语音数据，实现了语音编解码方案的降级处理，避免采用高等级的语音编解码方案而出现杂音等通话异常问题。
在一种实现方式中，当程序指令被处理器执行时，还使得终端设备实现如下方法步骤：在当前使用的语音编解码方案调整为第二语音编解码之后，等待第二预设时长，然后向第一基站发送第二请求消息，第二请求消息用于请求第一基站使用第一语音编解码；响应于第二应答消息，将当前使用的语音编解码方案调整为第一语音编解码，其中，第二应答消息是第一基站响应于第二请求消息发送的，第二应答消息用于向UE指示第一基站同意使用第一语音编解码。这样，通过等待第二时长，UE可以在降级语音编解码方案之后的一段时间内不再与第一基站协商语音编解码方案。在等待第二时长之后，UE考虑到网络环境发生变化，因此再次与网络设备协商升级语音编解码方案，如果协商成功，当再次执行VoNR通话时，UE和第一基站就可以使用高级别的第一语音编解码方案编解码和传输语音数据，以实现更高的带宽和减少通话时的延迟抖动和丢包。
在一种实现方式中，当程序指令被处理器执行时，还使得终端设备实现如下方法步骤：响应于第一拒绝消息，继续使用第一语音编解码，其中，第一拒绝消息是第一基站响应于第一请求消息发送的，第一拒绝消息用于向UE指示第一基站不同意使用第二语音编解码。
在一种实现方式中，当程序指令被处理器执行时，还使得终端设备实现如下方法步骤：响应于第二拒绝消息，继续使用第二语音编解码，其中，第二拒绝消息是第一基站响应于第二请求消息发送的，第二拒绝消息用于向UE指示第一基站不同意使用第一语音编解码。
在一种实现方式中，当程序指令被处理器执行时，还使得终端设备实现如下方法步骤：在当前使用的语音编解码方案调整为第二语音编解码之后，检测自身驻留的NR小区是否从第一NR小区切换到第二NR小区，第一NR小区和第二NR小区的跟踪区不同；在检测到自身驻留的NR小区从第一NR小区切换到第二NR小区时，向第二NR小区对应的第二基站发送第三请求消息，第三请求消息用于请求第二基站使用第一语音编解码；响应于第三应答消息，将当前使用的语音编解码方案调整为第一语音编解码，其中，第三应答消息是第二基站响应于第三请求消息发送的，第三应答消息用于向UE指示第二基站同意使用第一语音编解码。这样，UE可以在驻留的NR小区的跟踪区发生变化时，再次与网络设备协商升级语音编解码方案，如果协商成功，当再次执行VoNR通话时，UE和第二基站就可以使用高级别的第一语音编解码方案编解码和传输语音数据，以实现更高的带宽和减少通话时的延迟抖动和丢包。
在一种实现方式中，基于第一语音编解码的通话异常包括：基于第一语音编解码的通话出现杂音，并且杂音的通话次数连续地大于预设第二阈值。
在一种实现方式中，当程序指令被处理器执行时，还使得终端设备实现如下方法步骤：在通话过程中发起呼叫保持hold时，向第一基站发送第四请求消息，第四请求消息用于请求 第一基站在呼叫保持期间使用第一语音编解码。
在一种实现方式中，当程序指令被处理器执行时，还使得终端设备实现如下方法步骤：响应于第四拒绝消息，向第一基站发送第五请求消息，其中，第四拒绝消息是第一基站响应于第四请求消息发送的，第四拒绝消息用于向UE指示第一基站不同意在呼叫保持期间使用第一语音编解码，第五请求消息用于请求第一基站在呼叫保持期间使用第二语音编解码。
这样，在第一基站不支持更高级的语音编解码方案下的呼叫保持业务时，UE和第一基站可以协商使用更低级的语音编解码方案执行呼叫保持任务，以避免呼叫保持失败。
在一种实现方式中，当程序指令被处理器执行时，还使得终端设备实现如下方法步骤：在通话过程中发起呼叫保持解除unhold时，向第一基站发送第六请求消息，第六请求消息用于请求第一基站在呼叫保持解除之后使用第一语音编解码。
在一种实现方式中，当程序指令被处理器执行时，还使得终端设备实现如下方法步骤：响应于第六拒绝消息，向第一基站发送第七请求消息，其中，第六拒绝消息是第一基站响应于第六请求消息发送的，第六拒绝消息用于向UE指示第一基站不同意在呼叫保持解除之后使用第一语音编解码，第七请求消息用于请求第一基站在呼叫保持解除之后使用第二语音编解码。
这样，在第一基站不支持更高级的语音编解码方案下的呼叫保持业务时，UE和第一基站可以协商使用更低级的语音编解码方案执行呼叫保持任务，以避免呼叫保持解除失败。
第六方面，本申请实施例提供了一种终端设备，包括：收发器、存储器和处理器，存储器存储有计算机程序指令，当程序指令被处理器执行时，使得终端设备实现如下方法步骤：在检测到换域重拨EPS FB异常时，关闭NR能力；在关闭NR能力之后，等待第三预设时长，然后开启NR能力。
这样，UE就不会驻留在NR小区，而是只搜索LTE小区，并且选择在LTE小区驻留，同时不支持N1NAS信令模式。当用户拨打电话时，UE直接向第一基站发起VoLTE通话请求或者CS域的通话请求，避免执行EPS FB流程，从而提高呼通率。
在一种实现方式中，当程序指令被处理器执行时，还使得终端设备实现如下方法步骤：在关闭NR能力之后，如果检测到连续产生分组数据传输，并且分组数据传输产生的总数据流量大于预设的流量阈值，则开启NR能力。
在一种实现方式中，当程序指令被处理器执行时，还使得终端设备实现如下方法步骤：在关闭NR能力之后，如果检测到自身的位置变化距离大于预设的距离阈值，则开启NR能力。
在一种实现方式中，UE关闭NR能力，包括：UE不再驻留NR小区，同时搜索长期演进技术LTE小区，并且在LTE小区驻留。
在一种实现方式中，UE开启NR能力，包括：UE搜索NR小区，并且在NR小区驻留。
在一种实现方式中，EPS FB异常，包括：在UE主叫或者被叫的通话场景下，UE释放与第一基站的5G语音专用承载失败，或者，UE与第二基站建立LTE语音专用承载失败，第二基站为LTE小区对应的基站。
在一种实现方式中，EPS FB异常，包括：在UE主叫或者被叫的通话场景下，UE释放与第一基站的5G语音专用承载失败，并且连续失败的次数大于预设第四阈值，或者，UE与第二基站建立LTE语音专用承载失败，并且连续失败的次数大于预设第五阈值。
第七方面，本申请实施例还提供一种计算机可读存储介质，计算机可读存储介质中存储 有指令，当其在计算机上运行时，使得计算机执行上述各方面及其各个实现方式的方法。
第八方面，本申请实施例还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面及其各个实现方式的方法。
第九方面，本申请实施例还提供了一种芯片系统，该芯片系统包括处理器，用于支持上述装置或系统实现上述方面中所涉及的功能，例如，生成或处理上述方法中所涉及的信息。
附图说明
图1示出了5G话音方案的选项和演进过程；
图2以Option2组网为例示出了EPS FB的示意图；
图3是本申请实施例提供的终端设备100的结构示意图；
图4是本申请提供的信息指示方法的实施例(一)的流程图；
图5示出了UE注册5GS服务的场景；
图6是本申请实施例一提供的UE向gNB发送第二UE能力信息的流程图；
图7是本申请提供的信息指示方法的实施例(二)的流程图；
图8是本申请实施例二提供的UE向gNB发送第二UE能力信息的流程图；
图9是本申请提供的信息指示方法的实施例(三)的流程图；
图10是本申请实施例三提供的UE向gNB发送第二UE能力信息的流程图；
图11是本申请提供的信息指示方法的实施例(四)的流程图；
图12是本申请实施例三提供的UE和gNB恢复语音编解码的示意图；
图13是本申请实施例三提供的UE和gNB恢复语音编解码的示意图；
图14是本申请实施例示出的呼叫保持示意图；
图15是本申请实施例三提供的UE和gNB协商发起呼叫保持的语音编解码的示意图；
图16是本申请实施例三提供的UE和gNB协商解除呼叫保持的语音编解码的示意图；
图17是本申请提供的信息指示方法的实施例(五)的流程图；
图18是本申请实施例提供的一种信息指示装置的结构示意图；
图19是本申请实施例提供的一种信息指示装置的结构示意图。
具体实施方式
第五代移动通信网络(英语：5th generation mobile networks，5G)是最新一代的移动通信技术，相比于早期的4G、3G、2G等移动通信技术，5G能够提供更高的数据速率、更低的延迟、万物互联的全连接、更节省能源、更低的成本、更高的系统容量和大规模设备接入。
5G新空口(new radio，NR)是一种新的无线接入技术(radio access technology，RAT)，由第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)开发，用于5G移动通信网络，是5G网络空中接口的全球通用标准。
目前，3GPP已经明确5G移动通信网络沿用4G移动通信网络的语音架构，仍然基于IP多媒体子系统(IP multimedia subsystem，IMS)提供语音业务。4G移动通信网络的无线接入技术为长期演进技术(long term evolution，LTE)，其上面承载的语音通话业务称之为voice on LTE(VoLTE)；5G移动通信网络的无线接入技术如上文所示为NR，其上面承载的语音通话业务称之为voice on NR(VoNR)，目前，VoLTE、VoNR作为5G的IMS话音业务的不同接入方式存在，而VoNR将作为5G独立组网(SA)的最终语音业务解决方案。
在目前5G系统建设的前期阶段，考虑到5G网络覆盖规模及终端设备UE生态系统的成 熟度的因素，以及5G组网部署选项的因素。5G话音方案如图1所示面临众多的选项和演进过程。其中：
5G Option3/3a/3X组网是目前5G NSA非独立组网的实现方式，NR由5G基站gNB提供，然后gNB作为4G基站的eNB的从站，接入到4G核心网EPC网络。
5G Option7/7a/7X组网是目前5G SA组网的一种实现方式，该方式可以由Option3系列演进而来，即随着5GC的部署，将原接入EPC的eNB升级为ng-eNB后，将原接入EPC的Option3系列组网割接到5GC下，形成Option7系列组网，ng-eNB是指4G的LTE基站升级之后，支持接入5G核心网5GC，也称为eLTE。
5G Option5组网是目前5G SA组网的另一种实现方式，该组网主要是从LTE的组网演变而来，随着5GC的部署，将原接入EPC的eNB升级为ng-eNB后，割接到5GC下。
5G Option2组网是5G SA的目标组网方案，gNB直接接入到5GC下。
5G Option4组网是目前5G SA组网的另一种实现方式，该方式是在5G Option2组网的基础上增加了ng-eNB从基站。
图1还示出了各个组网方式下的各种组网方式可选择的语音业务的解决方案，可以理解的是，考虑到5G网络覆盖规模和组网成熟度等因素，各个组网方式可能仅支持其可选方案中的部分方案。其中，CSFB(circuit switch fallback)是4G下回落到3G承载语音业务的解决方案，EPS FB(EPS Fallback)和RAT FB(RAT Fallback)是5G SA下回落到4G承载语音业务的解决方案；VoeLTE则是在eLTE上承载语音业务的方案，VoeLTE和VoLTE的区别的仅在于4G基站是eNB还是ng-eNB，为便于描述，以下统称为VoLTE。例如，5G Option3/3a/3X组网的语音早期可以使用CSFB方案，随着组网部署的推进，逐渐向VoLTE和VoNR方案演进；5G Option7/7a/7X组网的语音早期可以使用VoLTE，随着组网部署的推进，逐渐向VoNR方案演进；5G Option4组网方案的语音使用VoLTE方案；5G Option2和Option3组网的语音早期可以使用EPS FB或者RAT FB或者VoLTE方案，随着组网部署的推进，逐渐向VoNR方案演进。
下面对5G组网部署选项中的部分语音业务的方案进行简要说明：
1、VoNR。VoNR的语音承载在5G基站gNB上，根据不同的5G组网，VoNR可以存在两个不同的选项：通过5GC和gNB承载VoNR，以及，通过4G核心网EPC和gNB承载VoNR。在VoNR下，终端设备UE驻留在NR小区，语音业务和数据业务都承载在NR网络。当终端设备UE移动到NR信号覆盖较差的区域时，需发起基于覆盖的切换来实现和4G的互操作，切换到LTE，由VoLTE来提供服务。
2、EPS FB。也称换域重拨，5G NR系统组网初期不提供语音业务，当gNB在NR上建立IMS话音通道时触发切换，此时gNB向5GC发起重定向或者inter-RAT切换请求，回落到LTE网络，由VoLTE提供服务。在EPS FB方案中，终端设备UE驻留在NR小区，拨打电话时，话音和数据业务都回落到LTE。
图2以Option2组网为例示出了EPS FB的示意图。当用户拨打电话时，UE通过SIP信令发起语音呼叫，通知5GC建立5G语音专用承载5QI1；然后，5GC向gNB发起建立专用承载5QI1的请求；接下来，当gNB不具备VoNR能力时，根据UE的NR能力、N26接口的部署情况、LTE的无线条件以及访问与移动性管理功能(access and mobility management function，AMF)的指示信息判断是否触发EPS FB；如果触发EPS FB，则gNB向5GC发起重定向或者inter-RAT切换请求，并等待UE回落到LTE网络，由EPC和eNB通过VoLTE提 供语音服务。
3、RAT FB。5G NR系统组网初期不提供语音业务，当gNB在NR上建立IMS话音通道时触发切换，此时gNB向5GC发起重定向或者inter-RAT切换请求，回落到eLTE网络，由VoeLTE提供服务。在RAT FB方案中，终端设备UE驻留在NR小区，拨打电话时，话音和数据业务都回落到eLTE。其方案实现方式与EPS FB类似，这里不再赘述。
除了上述5G组网部署选项不同以外，在目前5G系统建设的前期阶段，其语音编解码方案的进展也可能不同。例如，目前5G网络使用的语音编解码可能包括：
增强语音服务(enhanced voice services，EVS)，是3GPP开发的一种超宽带语音音频编码标准，是3GPP当前抗丢包和质量最好的语音编码，EVS是VoNR采用的语音编解码方案，也是5G网络的语音业务的必选编码标准。
自适应多速率音频压缩(adaptive multi-rate compression，AMR)，是3GPP开发的一种语音音频编码标准，AMR是VoLTE采用的语音编解码方案，目前广泛用于4G网络。AMR编码包括AMR-WB(adaptive multi rate wide band)和AMR-NB(adaptive multi rate narrow band)两种语音编码方式。其中AMR-WB能够比AMR-NB更高的带宽和采样率，AMR-NB一般也称作AMR。
另外，为适应无线链路高误码率和长环回时间的链路特点，3GPP在UMTS/LTE/NR的无线电协议栈的分组数据汇聚协议层(packet data convergence protocol，PDCP)引入了鲁棒性的头域压缩(robust header compression，RoHC)。RoHC可以减少包头负荷，减少分组丢失，缩短交互响应时间。RoHC使语音包变得更小，节约了物理资源块(physical resource block，PRB)的开销，在PRB受限的场景下，可以提升系统的容量。同时，RoHC可以将语音报文的包头压缩为更小的字节，使整个语音报文的长度更小，使用更少的分片以更高概率保证语音包的正确传输，从而增加了语音业务的边缘覆盖。
RoHC协议定义了3种压缩状态和3种解压状态，以便RoHC在不同无线链路状态下对IP分组头进行压缩和解压，保持压缩和解压数据流同步，保证RoHC协议鲁棒性。
1、RoHC压缩状态。
初始化和刷新(IR)状态。用于初始、更新上下文中静态域和动态域信息。在此状态下，压缩方连续发送全部IP包头信息和流关联标识符。
一阶(FO)状态。压缩方仅仅需要传递完整的动态域信息。
二阶(SO)状态：SO状态是最高级压缩状态，这时压缩方根据动态域变化规律，仅传递动态域的压缩值，此时压缩方发送最高压缩率的RoHC压缩分组。
2、RoHC解压状态。
无上下文(NC)状态。是指在数据流刚开始传递时解压方所处的状态，解压方没有IP包头静态和动态域信息，需要压缩方在IR状态发送包含完整包头的分组。
静态上下文(SC)状态。指解压方获得了足够的静态域信息，与压缩方的FO状态相对应，希望接收到包含完整动态域的RoHC压缩分组。
全上下文(FC)状态。指解压方获得了足够的静态域信息和动态域的变化规律信息时所处的状态，与压缩方SO状态相对应，能够接收压缩方在SO状态所发送的RoHC压缩分组。
另外，根据RoHC工作模式的不同，现有的RoHC协议还定义了RoHC在不同解压状态和压缩状态之间的迁移原则，以保证压缩健壮性和压缩率，例如：
周期性原则：压缩方在FO、SO状态一定时间timeout后，就转移到低级压缩状态。
负反馈原则：当无线链路允许发送反馈分组的时候，解压方连续错误地解压RoHC分组时，就要向压缩方发送负反馈分组，促使压缩方向低级状态转移，并发送带有完整信息的分组，以便解压方接收到这些分组后更新解压上下文信息，保持压缩和解压上下文同步。
可以理解的是，在5G NR系统组网初期，受到5G组网部署选项不同、5G网络覆盖规模不同、网络侧的基站和核心网的各网元的兼容性和工作状态好坏、终端设备UE生态系统的成熟度不同、5G语音业务的编码标准不同、以及RoHC的能力不同等因素的影响，VoNR在5G网络的部署前期无法保证提供稳定的语音服务，导致UE在5G网络下出现各种通话异常，例如：
1、在5G网络的部署前期，当UE和gNB都支持VoNR时，如果gNB和5GC的各网元的兼容性或者信令交互存在问题，或者工作状态异常，也会导致建立VoNR通话失败。并且，由于UE和gNB都支持VoNR，gNB也不会发起EPS FB流程，因此最终会导致无法建立通话，目前的的解决方案不具备从这种通话异常中自动恢复的能力。
2、当通话过程中出现RoHC异常时，例如解压和压缩错误，按照目前的RoHC协议只能是在压缩方在FO、SO状态一定时间timeout后或者解压方连续错误地解压RoHC分组时，进行不同解压状态和压缩状态之间的迁移，依然可能导致通话语音出现断续。
3、当使用EVS、AMR、AMR-WB等编解码标准时，如果出现通话异常，目前的解决方案不具备从异常中自动恢复的能力。
4、在5G网络的部署前期，当gNB不支持VoNR时，gNB需要在5GC发起建立专用承载5QI1的请求时，发起EPS FB流程，然而，如果gNB和5GC的各网元的兼容性或者信令交互存在问题，或者工作状态异常，会导致EPS FB异常，使得VoLTE的通话无法建立。面对EPS FB异常，目前的解决方案不具备从异常中自动恢复的能力，导致后续的通话也无法完成EPS FB流程。
为解决上述问题，本申请实施例提供了一种信息指示方法，该方法可以应用于如图1所示的任意一种组网形式的5G网络系统中，例如应用于终端设备UE或者基站等，使终端设备UE在5G网络下出现通话异常时，具备从异常状态中自动恢复的能力。
本申请实施例中的终端设备例如可以包括手机、平板电脑、个人电脑、工作站设备、大屏设备(例如：智慧屏、智能电视等)、掌上游戏机、家用游戏机、虚拟现实设备、增强现实设备、混合现实设备等、车载智能终端、自动驾驶汽车、用户驻地设备(customer-premises equipment，CPE)等。
图3是本申请实施例提供的终端设备100的结构示意图。如图3所示，终端设备100可以包括处理器110，存储器120，通用串行总线(universal serial bus，USB)接口130，射频电路140，移动通信模块150，无线通信模块160，摄像头170，显示屏180，以及用户标识模块(subscriber identification module，SIM)卡接口190等。
处理器110可以包括一个或多个处理单元，例如：处理器110可以包括应用处理器(application processor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中，例如集成在系统芯片(system on a chip，SoC)中。处理器110中还可以设置存储器，用于存储指令和数据。在一些实施例中，处理器110中的存储器为高速缓冲存储器。该存储器可以保存处 理器110刚用过或循环使用的指令或数据。
在一些实施例中，处理器110可以包括一个或多个接口。接口可以包括集成电路(inter-integrated circuit，I2C)接口，集成电路内置音频(inter-integrated circuit sound，I2S)接口，脉冲编码调制(pulse code modulation，PCM)接口，通用异步收发传输器(universal asynchronous receiver/transmitter，UART)接口，移动产业处理器接口(mobile industry processor interface，MIPI)，通用输入输出(general-purpose input/output，GPIO)接口，用户标识模块(subscriber identity module，SIM)接口，和/或通用串行总线(universal serial bus，USB)接口等。
存储器120可以用于存储计算机可执行程序代码，可执行程序代码包括指令。存储器120可以包括存储程序区和存储数据区。其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能，图像播放功能等)等。存储数据区可存储终端设备100使用过程中所创建的数据(比如音频数据，电话本等)等。此外，存储器120可以包括一个或者多个存储单元，例如可以包括易失性存储器(volatile memory)，如：动态随机存取存储器(dynamic random access memory，DRAM)、静态随机存取存储器(static random access memory，SRAM)等；还可以包括非易失性存储器(non-volatile memory，NVM)，如：只读存储器(read-only memory，ROM)、闪存(flash memory)等。处理器110通过运行存储在存储器120的指令，和/或存储在设置于处理器中的存储器的指令，执行终端设备100的各种功能应用以及数据处理。
终端设备100的无线通信功能可以通过射频电路140、移动通信模块150、无线通信模块160、调制解调处理器以及基带处理器等实现。
射频电路140可以包括至少一个天线141，用于发射和接收电磁波信号。终端设备100中的每个天线可用于覆盖单个或多个通信频带。不同的天线还可以复用，以提高天线的利用率。例如：可以将天线141复用为无线局域网的分集天线。在另外一些实施例中，天线可以和调谐开关结合使用。
移动通信模块150可以提供应用在终端设备100上的包括2G/3G/4G/5G等无线通信的解决方案。移动通信模块150可以包括至少一个滤波器，开关，功率放大器，低噪声放大器(low noise amplifier，LNA)等。移动通信模块150可以由天线141接收电磁波，并对接收的电磁波进行滤波，放大等处理，传送至调制解调处理器进行解调。移动通信模块150还可以对经调制解调处理器调制后的信号放大，经天线141转为电磁波辐射出去。在一些实施例中，移动通信模块150的至少部分功能模块可以被设置于处理器110中。在一些实施例中，移动通信模块150的至少部分功能模块可以与处理器110的至少部分模块被设置在同一个器件中。
调制解调处理器可以包括调制器和解调器。其中，调制器用于将待发送的低频基带信号调制成中高频信号。解调器用于将接收的电磁波信号解调为低频基带信号。随后解调器将解调得到的低频基带信号传送至基带处理器处理。低频基带信号经基带处理器处理后，被传递给应用处理器。应用处理器通过音频设备(包括但不限于扬声器，受话器等)输出声音信号，或通过显示屏180显示图像或视频。在一些实施例中，调制解调处理器可以是独立的器件。在另一些实施例中，调制解调处理器可以独立于处理器110，与移动通信模块150或其他功能模块设置在同一个器件中。
无线通信模块160可以包括Wi-Fi模块，蓝牙(bluetooth，BT)模块、全球导航卫星系统(global navigation satellite system，GNSS)模块、近距离无线通信技术(near field  communication，NFC)模块、红外(infrared，IR)模块等。无线通信模块160可以是集成上述至少一个模块的一个或多个器件。无线通信模块160经由天线141接收电磁波，将电磁波信号调频以及滤波处理，将处理后的信号发送到处理器110。无线通信模块160还可以从处理器110接收待发送的信号，对其进行调频，放大，经天线141转为电磁波辐射出去。
本申请实施例中，终端设备100的无线通信功能例如可以包括全球移动通讯系统(global system for mobile communications，GSM)，通用分组无线服务(general packet radio service，GPRS)，码分多址接入(code division multiple access，CDMA)，宽带码分多址(wideband code division multiple access，WCDMA)，时分码分多址(time-division code division multiple access，TD-SCDMA)，长期演进(long term evolution，LTE)，第五代移动通信技术新空口(5th generation mobile networks new radio，5G NR)，BT，GNSS，WLAN，NFC，FM，和/或IR等功能。GNSS可以包括全球卫星定位系统(global positioning system，GPS)，全球导航卫星系统(global navigation satellite system，GLONASS)，北斗卫星导航系统(beidou navigation satellite system，BDS)，准天顶卫星系统(quasi-zenith satellite system，QZSS)和/或星基增强系统(satellite based augmentation systems，SBAS)。
摄像头170用于捕获静态图像或视频。摄像头170包括镜头和感光元件，物体通过镜头生成光学图像投射到感光元件。感光元件可以是电荷耦合器件(charge coupled device，CCD)或互补金属氧化物半导体(complementary metal-oxide-semiconductor，CMOS)光电晶体管。感光元件把光信号转换成电信号，之后将电信号传递给ISP转换成数字图像信号。ISP将数字图像信号输出到DSP加工处理。DSP将数字图像信号转换成标准的RGB，YUV，RYYB等格式的图像信号。在一些实施例中，终端设备100可以包括1个或N个摄像头170，N为大于1的正整数。
NPU为神经网络(neural-network，NN)计算处理器，通过借鉴生物神经网络结构，例如借鉴人脑神经元之间传递模式，对输入信息快速处理，还可以不断的自学习。通过NPU可以实现终端设备100的智能认知等应用，例如：图像识别，人脸识别，语音识别，文本理解等。
显示屏180用于显示图像，视频等。显示屏180包括显示面板。显示面板可以采用液晶显示屏(liquid crystal display，LCD)，有机发光二极管(organic light-emitting diode，OLED)，有源矩阵有机发光二极体或主动矩阵有机发光二极体(active-matrix organic light emitting diode的，AMOLED)，柔性发光二极管(flex light-emitting diode，FLED)，MiniLED，MicroLED，Micro-OLED，量子点发光二极管(quantum dot light emitting diodes，QLED)等。在一些实施例中，终端设备100可以包括1个或N个显示屏180，N为大于1的正整数。
SIM卡接口190用于连接SIM卡。SIM卡可以通过插入SIM卡接口190，或从SIM卡接口190拔出，实现和终端设备100的接触和分离。终端设备100可以支持1个或N个SIM卡接口，N为大于1的正整数。SIM卡接口190可以支持Nano SIM卡，Micro SIM卡，SIM卡等。同一个SIM卡接口190可以同时插入多张卡。多张卡的类型可以相同，也可以不同。SIM卡接口190也可以兼容不同类型的SIM卡。SIM卡接口190也可以兼容外部存储卡。终端设备100通过SIM卡和网络交互，实现通话以及数据通信等功能。在一些实施例中，终端设备100采用eSIM，即：嵌入式SIM卡。eSIM卡可以嵌在终端设备100中，不能和终端设备100分离。
可以理解的是，本申请实施例示意的结构并不构成对终端设备100的具体限定。在本申 请另一些实施例中，终端设备可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
本申请实施例的技术方案可以应用于如图1示出的独立组网SA或者非独立组网NAS的5G语音方案中，例如上述Option3/3a/3X方案、Option4/4a方案、Option7/7a/7X、Option 5方案和Option 2方案等，本申请实施例对此不做具体限定。
下面对本申请实施例提供的信息指示方法的各个实施例进行具体说明。
实施例(一)
本申请的实施例(一)用于当UE和基站(例如：gNB、ng-eNB等)都支持VoNR时，如果出现建立VoNR通话失败的异常情况，使UE具备从异常中自动恢复的能力。
图4是本申请提供的信息指示方法的实施例(一)的流程图。
以基站为gNB为例，如图4所示，具备VoNR能力的UE在注册5G系统(5GS)服务时，可以向gNB上报用于指示自身具备VoNR能力的UE能力信息。其中，如图5所示，UE注册5GS服务的场景可以包括：
UE初始注册5GS服务。例如，当UE开机或者从关闭飞行模式时，UE搜索到NR小区，并向gNB发起注册请求，以实现UE初始注册5GS服务。
移动性更新注册。例如，UE在已经注册到了5GS服务之后，如果移动到新的跟踪区(tracking area，TA)的小区，就需要重新注册5GS服务。
周期性注册。例如，UE在已经注册到了5GS服务之后，可以通过定时器触发周期性注册，以使gNB知道UE的存在。
可选的，UE能力信息可以在无线资源控制(radio resource control，RRC)消息中发送。
3GPP TS 38.331技术规范定义了RRC信息参数(RRC information elements)，其中包括UE能力信息元素(UE capability information elements)。
UE能力信息元素包含有用于向gNB传达UE的无线接入能力的UE-NR-Capability参数。其中，UE-NR-Capability中与UE的VoNR能力相关参数的可以包含以下字段的子体加粗部分(为便于描述，以下称为字体加粗部分①)：
Figure PCTCN2021110225-appb-000001
在UE-NR-Capability参数中，IMS-Parameters包含了UE的与IMS相关的能力参数。其中，IMS-Parameters中与UE的VoNR能力相关的参数可以包含以下字段中的子体加粗部分(为便于描述，以下称为字体加粗部分②)：
Figure PCTCN2021110225-appb-000002
Figure PCTCN2021110225-appb-000003
根据上述定义，如果UE具备VoNR能力，那么UE在注册5GS服务时，可以在其发送给gNB的UE能力信息元素中的UE-NR-Capability-v1540字段中的ims-Parameters参数中，携带voiceOverNR的字段，即携带子体加粗部分②。这样gNB就知道UE具备VoNR能力，那么，同样具备VoNR能力的gNB在接收到5GC的发起建立专用承载5QI1的请求时，不会触发EPS FB。
在UE驻留在5GS期间，当用户拨打电话时，UE通过SIP信令发起语音呼叫，通知5GC建立5G语音专用承载5QI1；然后，5GC向gNB发起建立专用承载5QI1的请求；接下来，由于gNB已经从UE上报的UE能力信息中得知UE支持VoNR能力，因此，在gNB也支持VoNR能力的情况下，gNB会启动发起VoNR通话的语音专用承载5QI1。一般来说，如果gNB和5GC的各网元的工作状态、兼容性和信令交互等均正常，那么VoNR通话会成功发起；如果gNB和5GC的各网元的工作状态、兼容性或者信令交互等出现异常，那么VoNR通话可能会建立失败，也就是用户无法拨通电话。
在本申请实施例(一)的技术方案中，UE在检测到建立VoNR通话失败时，可以再次向gNB发送一次UE能力信息，为便于描述，此处将这个UE能力信息称作第一UE能力信息，第一UE能力信息不包含ims-Parameters参数中的voiceOverNR的字段，即不包含上述子体加粗部分②。这样，gNB在接收到第一UE能力信息之后，可以根据第一UE能力信息认定UE不具备VoNR能力。
可选的，UE向gNB发送第一UE能力信息的动作可以根据以下条件中的任意一个触发：
1、UE在建立VoNR通话连续失败，并且连续失败的次数达到了(大于或者等于)预设的第一阈值时，可以在达到第一阈值的那一次建立VoNR通话失败之后，向gNB发送第一UE能力信息。
2、UE只要检测到建立VoNR通话失败，就在当次建立VoNR通话失败之后，向gNB发送第一UE能力信息。
3、VoNR通话成功建立，但是，如果UE在连续几次VoNR通话过程中均检测到了语音质量异常的情况，并且出现语音质量异常的连续次数达到了(大于或者等于)预设的第二阈值时，则UE可以在达到第二阈值的那一次VoNR通话结束之后，向gNB发送第一UE能力信息。
在一种实现方式中，UE可以在5GS移动管理空闲(5GMM-IDLE)模式下向gNB发送第一UE能力信息。例如，3GPP TS 24.501技术规范的定义了移动性和定期注册更新启动的星期，包括在一些情况下，处于5GS移动管理已注册(5GMM-REGISTERED)模式下的UE应通过向AMF发送注册请求消息来启动移动性和定期注册更新的注册过程，其中一种情况包括：当处于5GMM-IDLE模式的UE更改了NG-RAN的无线电能力时。据此，如图4所示，UE在检测到建立VoNR通话失败时，向gNB发送第一UE能力信息，可以通过以下步骤S101- 步骤S103实现：
步骤S101，UE向gNB发送注册请求消息。
注册请求消息的作用是用于指示gNB需要进行NG-RAN无线能力更新。
根据3GPP TS 24.501技术规范的定义：当处于5GMM-IDLE模式的UE更改了NG-RAN的无线电能力时，UE应在注册请求消息REGISTRATION REQUEST消息中包括5GS更新类型元素，并将在NG-RAN-RCU比特设置为“需要进行NG-RAN无线电功能更新”。其中，5GS更新类型元素可以包含以下字段：
Figure PCTCN2021110225-appb-000004
其中，NG-RAN-RCU可以有两种比特值：
Figure PCTCN2021110225-appb-000005
当NG-RAN-RCU的比特值为0时，对应“不需要进行NG-RAN无线电功能更新”；当NG-RAN-RCU的比特值为1时，对应“需要进行NG-RAN无线电功能更新”。
因此，在本申请实施例(一)中，UE在步骤S101向gNB发送注册请求消息中的NG-RAN-RCU的比特值为1，以指示gNB需要进行NG-RAN无线能力更新。
步骤S102，gNB响应于注册请求消息，向UE发送UE能力查询消息。
当注册请求消息中的NG-RAN-RCU的比特值为1时，其指示gNB需要进行NG-RAN无线电功能更新，因此，gNB可以通过RRC消息向UE发送UE能力查询消息。其中，UE能力查询消息用于向请求UE在NR的无线电能力或者其他的无线电能力。
可选的，UE能力查询消息可以是3GPP TS36.331技术规范定义的UE Capability Enquiry消息，UE Capability Enquiry消息同样属于RRC消息。
示例地，根据3GPP TS36.331技术规范的定义，当UE能力查询消息为UE Capability Enquiry消息时，可以包括以下字段：
Figure PCTCN2021110225-appb-000006
可以理解的是，本申请实施例中的UE能力查询消息除可以是UE Capability Enquiry消息以外，还可以通过其他的消息格式实现，本申请实施例不做限定。
步骤S103，UE响应于UE能力查询消息，向gNB发送第一UE能力信息。
其中，第一UE能力信息用于向gNB指示UE当前自身不支持VoNR能力。
示例地，当第一UE能力信息以UE-NR-Capability参数实现时，根据在先阐述的内容，第一UE能力信息不包含ims-Parameters参数中的voiceOverNR的字段，即不包含上述子体加粗部分②。那么，示例地，第一UE能力信息中的IMS-Parameters参数可以仅包含以下内容：
Figure PCTCN2021110225-appb-000007
Figure PCTCN2021110225-appb-000008
可以理解的是，本申请实施例中的第一UE能力信息除可以以UE-NR-Capability参数实现以外，还可以通过其他的消息格式实现，本申请实施例不做限定。
这样，gNB在接收到第一UE能力信息之后，就可以根据第一UE能力信息认为UE不具备VoNR能力。那么，当用户再次拨打电话时，由于gNB认为UE当前不支持VoNR能力，因此gNB会拒绝5GC发起的建立专用承载5QI1的请求，而是触发EPS FB流程，向5GC发起重定向或者inter-RAT切换请求，并等待UE回落到LTE网络，由EPC和eNB通过VoLTE提供语音服务。由此，避免建立VoNR通话失败的异常情况再次发生，UE从VoNR通话异常中恢复。
这里需要补充说明的是，虽然UE向gNB发送的第一UE能力信息指示给gNB的信息是UE不支持VoNR能力，但这并不意味着UE真的不支持VoNR能力，事实上UE此时依然具备VoNR能力。UE只是向gNB指示了一个善意性的非真实信息，让gNB以为UE不支持VoNR能力，使得gNB按照UE不支持VoNR能力的方式去处理建立专用承载5QI1的请求，以此提升呼通率。
在另一种实现方式中，UE可以在其周期性注册5GS服务时，向gNB发送第一UE能力信息。例如，UE在已经注册到了5GS服务之后，可以通过定时器触发周期性注册。在每次触发周期性注册之前，UE可以判断当前是否满足上述任意一个触发UE向gNB发送第一UE能力信息的动作的条件。如果满足条件，则UE会在这一次周期性注册时向gNB发送第一UE能力信息。如果不满足条件，则等待下一个周期。
在一些实施例中，UE向gNB发送第一UE能力信息之后，还可以执行以下步骤：
步骤S104，UE检测自身驻留的NR小区的跟踪区是否发生变化。
跟踪区(tracking area，TA)是LTE系统和NR系统为UE的位置管理设立的概念，其功能与2G/3G系统的位置区(LA)和路由区(RA)类似。通过跟踪区的信息，5GC能够获知处于5GMM-IDLE模式下UE的位置，并且在有数据业务需求时，对UE进行寻呼。通常，一个跟踪区可包含一个或多个NR小区，而一个NR小区只能归属于一个跟踪区，因此，当UE驻留的NR跟踪区发生变化时，说明UE驻留的NR小区也发生了变化，即UE切换到了另一个gNB。
UE在驻留的NR小区的跟踪区发生变化时，可以再次向gNB(这里指的是UE在驻留的NR小区的跟踪区发生变化之后，当前接入的NR小区对应的gNB)发送一次UE能力信息，为便于描述，此处将这个UE能力信息称作第二UE能力信息，第二UE能力信息包含ims-Parameters参数中的voiceOverNR的字段，即包含上述子体加粗部分②。这样，gNB在接收到第二UE能力信息之后，可以根据第二UE能力信息认定UE具备VoNR能力。
在一种实现方式中，UE可以在5GS移动管理空闲(5GMM-IDLE)模式下向gNB发送第二UE能力信息。如图6所示，与步骤S101-步骤S103类似地，UE向gNB发送第二UE能力信息可以通过以下步骤S105-步骤S107实现：
步骤S105，UE向gNB发送注册请求消息。
步骤S105与步骤S101相同，注册请求消息的5GS更新类型元素的NG-RAN-RCU的比特值为1，本申请实施例对此不再赘述。
步骤S106，gNB响应于注册请求消息，向UE发送UE能力查询消息。
步骤S106与步骤S102相同，本申请实施例对此不再赘述。
步骤S107，UE响应于UE能力查询消息，向gNB发送第二UE能力信息。
与第一能力信息不同的是，为了将UE支持VoNR能力的信息指示给gNB，第二UE能力信息的IMS-Parameters参数中包含与VoNR能力相关的参数，即包含字体加粗部分②。
这样，在UE驻留在新的跟踪区的NR小区期间，当用户再次拨打电话时，由于gNB认为UE当前支持VoNR能力，gNB会启动发起VoNR通话的语音专用承载5QI1，不会触发EPS FB，使得VoNR通话能力得以恢复。
一种实现方式中，如果UE是在建立VoNR通话连续失败多次的情况下向UE发送了第一UE能力信息，那么UE可以在发送第一UE能力信息之后等待一个时长，在等待时长结束之后再去检测自身驻留的NR跟踪区是否发生变化。该等待时长例如可以是15分钟、30分钟、1个小时、3个小时等等，本申请实施例对此不做限定。这样，UE可以相对长时间地在4G网络中进行通话，避免VoNR通话异常的现象在短时间内频繁发生。
实施例(二)
本申请的实施例(二)用于使UE在通话过程中出现RoHC异常时，具备从异常中自动恢复的能力。
图7是本申请提供的信息指示方法的实施例(二)的流程图。
以基站为gNB为例，如图7所示，具备RoHC能力的UE在注册5GS服务时，可以向gNB上报用于指示自身具备RoHC能力的UE能力信息。其中，UE注册5GS服务的场景可以参照本申请实施例(一)的内容，此处不再赘述。
可选的，UE能力信息可以在无线资源控制RRC消息中发送。
3GPP TS 38.331技术规范定义了RRC信息参数，其中包括UE能力信息元素。
UE能力信息元素包含有用于向gNB传达PDCP相关能力的PDCP-Parameters参数。其中，PDCP-Parameters中包含与UE的RoHC能力相关参数，例如：
Figure PCTCN2021110225-appb-000009
其中，“profile0x0000”“profile0x0001”等参数的数据类型为布尔值BOOLEAN，TRUE表示支持，FALSE表示不支持。“profile0x0000”“profile0x0001”等不同的参数项代表了不同的RoHC能力。其中，根据互联网工程任务组(internet engineering task force，IETF)的请求意见稿(request for comments，RFC)3095中对RoHC的配置参数的定义：“profile0x0001”对应实时传输协议(real-time transport protocol，RTP)、用户数据报协议(user datagram protocol， UDP)和网际协议(internet protocol，IP)，当“profile0x0001”的值为FALSE时，表示不对RTP/UDP/IP的报文进行RoHC，当“profile0x0001”的值为TRUE时，表示对RTP/UDP/IP的报文进行RoHC。而IMS语音业务使用的协议正是RTP/UDP/IP，因此，根据上述定义，如果UE具备RoHC能力，那么UE在注册5GS服务时，在其发送给gNB的UE能力信息元素中，PDCP-Parameters参数中的“profile0x0001”的值为“TRUE”。这样gNB就知道UE具备RoHC能力，那么，在通话过程中，UE和gNB会之间会启用RoHC功能。
UE驻留在5GS期间，当用户拨打电话时，如果VoNR通话建立成功，则UE可以在通话过程中检测RoHC是否异常。例如：当RoHC解压数据流错误或者压缩错误时，则认为RoHC异常。可以理解的是，UE驻留在5GS期间，可能产生一次或者多次通话，UE可以在每次通话时检测RoHC是否异常，如果检测到RoHC异常，则可以在通话结束之后，再次向gNB发送一次UE能力信息，为便于描述，此处将这个UE能力信息称作第一UE能力信息，并且第一UE能力信息中的PDCP-Parameters参数中的“profile0x0001”的值为“FALSE”。
这样，gNB在接收到第一UE能力信息之后，可以根据第一UE能力信息认定UE不具备RoHC能力。
在一种实现方式中，UE可以在5GS移动管理空闲(5GMM-IDLE)模式下向gNB发送第一UE能力信息。如图8所示，UE向gNB发送第一UE能力信息可以通过以下步骤S201-步骤S203实现：
步骤S201，UE向gNB发送注册请求消息。
步骤S201与步骤S101相同，注册请求消息的5GS更新类型元素的NG-RAN-RCU的比特值为1，本申请实施例对此不再赘述。
步骤S202，gNB响应于注册请求消息，向UE发送UE能力查询消息。
步骤S202与步骤S102相同，本申请实施例对此不再赘述。
步骤S203，UE响应于UE能力查询消息，向gNB发送第一UE能力信息。
其中，由于第一能力消息用于指示UE不支持RoHC能力，因此第一UE能力信息的PDCP-Parameters参数中的“profile0x0001”的值为“FALSE”(本申请实施例其他参数的布尔值不做具体展开说明)。示例地，第一能力消息可以包括以下内容：
Figure PCTCN2021110225-appb-000010
这样，gNB在接收到第一UE能力信息之后，就可以根据第一UE能力信息认为UE不具备RoHC能力。那么，当用户再次拨打电话时，gNB和UE都不会启用RoHC功能，避免在通话过程中出现RoHC异常，以提高通话质量。
这里需要补充说明的是，虽然UE向gNB发送的第一UE能力信息指示给gNB的信息是UE不支持RoHC能力，但这并不意味着UE真的不支持RoHC能力，事实上UE此时依然具 备RoHC能力。UE只是向gNB指示了一个善意性的非真实信息，让gNB以为UE不支持RoHC能力。
在一些实施例中，UE向gNB发送第一UE能力信息之后，还可以执行以下步骤：
步骤S204，UE检测自身驻留的NR跟踪区是否发生变化。
UE在驻留的NR跟踪区发生变化时，可以再次向gNB发送一次UE能力信息，为便于描述，此处将这个UE能力信息称作第二UE能力信息，第二UE能力信息的PDCP-Parameters参数中的“profile0x0001”的值为“TRUE”。这样，gNB在接收到第二UE能力信息之后，可以根据第二UE能力信息认定UE具备RoHC能力。
在一种实现方式中，UE可以在5GS移动管理空闲(5GMM-IDLE)模式下向gNB发送第二UE能力信息。如图8所示，与步骤S201-步骤S203类似地，UE向gNB发送第二UE能力信息可以通过以下步骤S205-步骤S207实现：
步骤S205，UE向gNB发送注册请求消息。
步骤S205与步骤S201相同，注册请求消息的5GS更新类型元素的NG-RAN-RCU的比特值为1，本申请实施例对此不再赘述。
步骤S206，gNB响应于注册请求消息，向UE发送UE能力查询消息。
步骤S206与步骤S202相同，本申请实施例对此不再赘述。
步骤S206，UE响应于UE能力查询消息，向gNB发送第二UE能力信息。
这样，在UE驻留在新的跟踪区的NR小区期间，当用户再次拨打电话时，由于gNB知道UE当前支持RoHC能力，因此会启用RoHC功能，以提高传输效率。
实施例(三)
本申请的实施例(三)用于使UE在VoNR通话异常时，具备从异常中自动恢复的能力，其中，这里的VoNR通话包括建立VoNR通话失败和VoNR通话过程中RoHC异常。
图9是本申请提供的信息指示方法的实施例(三)的流程图。
如图9所示，本申请实施例(三)相当于实施例(一)和实施例(二)的结合。以基站为gNB为例，具备VoNR能力和RoHC能力的UE在注册5GS服务时，可以向gNB上报用于指示自身具备VoNR能力和RoHC能力的UE能力信息。UE能力信息例如可以包括UE-NR-Capability中与UE的VoNR能力相关参数(字体加粗部分①)以及PDCP-Parameters中与UE的RoHC能力相关参数，其中，PDCP-Parameters参数中的“profile0x0001”的值为“TRUE”。例如：
Figure PCTCN2021110225-appb-000011
Figure PCTCN2021110225-appb-000012
这样gNB就知道UE具备VoNR能力和RoHC能力，那么，当用户拨打电话时，gNB会启动发起VoNR通话的语音专用承载，并且在通话过程中，UE和gNB会之间会启用RoHC功能。并且在拨打电话过程中，UE可以检测是否建立VoNR通话失败，以及通话过程中是否出现RoHC异常。并且可以根据检测结果触发向gNB发送第一UE能力信息，触发条件可以参照实施例(一)和实施例(二)，此处不再赘述。
在一种实现方式中，UE可以在5GS移动管理空闲(5GMM-IDLE)模式下向gNB发送第一UE能力信息。如图9所示，UE向gNB发送第一UE能力信息可以通过以下步骤S301-步骤S303实现：
步骤S301，UE向gNB发送注册请求消息。
步骤S301与步骤S101相同，注册请求消息的5GS更新类型元素的NG-RAN-RCU的比特值为1，本申请实施例对此不再赘述。
步骤S302，gNB响应于注册请求消息，向UE发送UE能力查询消息。
步骤S302与步骤S102相同，本申请实施例对此不再赘述。
步骤S303，UE响应于UE能力查询消息，向gNB发送第一UE能力信息。
其中，由于第一能力消息用于指示UE不支持VoNR能力和不支持RoHC能力，因此，第一UE能力信息不包含ims-Parameters参数中的voiceOverNR的字段，同时，第一UE能力信息的PDCP-Parameters参数中的“profile0x0001”的值为“FALSE”。示例地，第一能力消息可以包括以下内容：
Figure PCTCN2021110225-appb-000013
Figure PCTCN2021110225-appb-000014
这样，gNB在接收到第一UE能力信息之后，就可以根据第一UE能力信息认为UE不具备VoNR能力，以及认为UE不具备RoHC能力。那么，当用户再次拨打电话时，gNB会触发EPS FB流程，由EPC和eNB通过VoLTE在4G网络下建立通话，并且也不会启用RoHC功能，从而避免VoNR通话异常的现象发生，提高通话的接通率和通话质量。
在一些实施例中，UE向gNB发送第一UE能力信息之后，还可以执行以下步骤：
步骤S304，UE检测自身驻留的NR跟踪区是否发生变化。
UE在驻留的NR跟踪区发生变化时，可以再次向gNB发送一次UE能力信息，为便于描述，此处将这个UE能力信息称作第二UE能力信息，第二UE能力信息包括UE-NR-Capability中与UE的VoNR能力相关参数(字体加粗部分①)，以及PDCP-Parameters中与UE的RoHC能力相关参数，其中，PDCP-Parameters参数中的“profile0x0001”的值为“TRUE”。这样，gNB在接收到第二UE能力信息之后，可以根据第二UE能力信息认定UE具备VoNR能力和RoHC能力。
在一种实现方式中，UE可以在5GS移动管理空闲(5GMM-IDLE)模式下向gNB发送第二UE能力信息。如图10所示，与步骤S301-步骤S303类似地，UE向gNB发送第二UE能力信息可以通过以下步骤S305-步骤S307实现：
步骤S305，UE向gNB发送注册请求消息。
步骤S305与步骤S301相同，注册请求消息的5GS更新类型元素的NG-RAN-RCU的比特值为1，本申请实施例对此不再赘述。
步骤S306，gNB响应于注册请求消息，向UE发送UE能力查询消息。
步骤S306与步骤S302相同，本申请实施例对此不再赘述。
步骤S307，UE响应于UE能力查询消息，向gNB发送第二UE能力信息。
这样，在UE驻留在新的跟踪区的NR小区期间，当用户再次拨打电话时，由于gNB知道UE当前支持VoNR能力和RoHC能力，因此会启用VoNR能力和和RoHC功能，使得VoNR通话能力得以恢复，并且提高传输效率。
一种实现方式中，如果UE是在建立VoNR通话连续失败多次的情况下向UE发送了第一UE能力信息，那么UE可以在发送第一UE能力信息之后等待一个时长，在等待时长结束之后再去检测自身驻留的NR跟踪区是否发生变化。该等待时长例如可以是15分钟、30分钟、1个小时、3个小时等等，本申请实施例对此不做限定。这样，UE可以相对长时间地在4G网络中进行通话，避免VoNR通话异常的现象在短时间内频繁发生。
实施例(四)
本申请实施例(四)用于UE与基站(例如：gNB、ng-eNB等)基于协商的语音编解码的通话出现异常时，使UE具备从异常中自动恢复的能力。
图11是本申请提供的信息指示方法的实施例(四)的流程图。
步骤S401：UE检测基于第一语音编解码的通话是否异常。
以基站为gNB为例，在UE驻留在5GS期间，如果用户拨打电话，UE和gNB可以建立VoNR通话。在通话过程中，UE和gNB会按照协商的语音编解码方案编解码和传输语音数据。然而，受到NR性能或者gNB性能等因素的影响，UE和gNB基于初始协商的语音编解码可能出现通话异常。为便于描述，本申请实施例将UE和gNB基于初始协商的语音编解码称作第一语音编解码。
可以理解的是，在UE驻留在5GS期间可能产生一次或者多次VoNR通话。UE在每一次通话期间可以检测通话是否出现杂音，如果通话出现杂音，并且连续有多次通话都出现杂音，例如连续多次通话出现杂音的次数大于预设第三阈值，则认为基于第一语音编解码的通话出现异常。
步骤S402，UE在检测到基于第一语音编解码的通话异常时，向gNB发送第一请求消息。
在一种实现方式中，第一请求消息可以在无线资源控制消息中发送。
例如，UE可以在通话结束之后，UE可以在5GS移动管理空闲(5GMM-IDLE)模式下向gNB发送第一请求消息。其中，第一请求消息例如可以是会话发起协议(session initiation protocol，SIP)的INVITE消息，携带第二语音编解码的协商内容，用于请求gNB在后续通话时使用第二语音编解码。一般来说，第二语音编解码的质量标准低于第一语音编解码的质量标准。
示例地，当第一语音编解码是EVS时，第二语音编解码可以是AMR-WB。那么，INVITE消息中可以例如可以包括以下字段，表示UE希望与gNB协商采用AMR-WB、采样率16KHz的编解码方案进行语音通话：
Figure PCTCN2021110225-appb-000015
示例地，当第一语音编解码是AMR-WB时，第二语音编码可以是AMR。那么，INVITE消息中可以例如可以包括以下字段，表示UE希望与gNB协商采用AMR、采样率8KHz的编解码方案进行语音通话：
Figure PCTCN2021110225-appb-000016
进一步地，gNB如果同意采用第二语音编解码方案进行语音通话，会向UE发送第一应答消息，第一应答消息可以是SIP的200/OK消息。
示例地，如果gNB同意采用AMR-WB、采样率16KHz的编解码方案进行语音通话，那么200/OK消息可以包括以下字段：
Figure PCTCN2021110225-appb-000017
Figure PCTCN2021110225-appb-000018
示例地，如果gNB同意采用AMR、采样率8KHz的编解码方案进行语音通话，那么200/OK消息可以包括以下字段：
Figure PCTCN2021110225-appb-000019
另外，如果gNB以3xx～6xx的应答消息拒绝了UE的协商请求，则UE可以通过再次发送INVITE消息的方式继续与gNB协商其他的语音编解码方案，也可以继续使用第一语音编解码方案。
步骤S403，UE在接收到第一应答消息时，将语音编解码方案调整为第二语音编解码。
这样，当再一次执行VoNR通话时，UE和gNB就可以使用低级别的第二语音编解码方案编解码和传输语音数据，实现了语音编解码方案的降级处理，避免采用高等级的语音编解码方案而出现杂音等通话异常问题。
在一种实现方式中，如图12所示，UE将语音编解码方案调整为第二语音编解码之后，还可以执行以下步骤：
步骤S404，UE在等待第二时长之后，向gNB发送第二请求消息。
其中，第二请求消息同样为INVITE消息，携带第一语音编解码的协商内容，用于请求gNB在后续通话时使用第一语音编解码。
示例地，当第一语音编解码是EVS时，第二语音编解码可以是AMR-WB。那么，INVITE消息中可以例如可以包括以下字段，表示UE希望与gNB协商从AMR-WB恢复到采用EVS、采样率16KHz的编解码方案进行语音通话：
Figure PCTCN2021110225-appb-000020
进一步地，gNB如果同意恢复到第一语音编解码方案进行语音通话，会向UE发送第二应答消息，第二应答消息可以是SIP的200/OK消息。
另外，如果gNB以3xx～6xx的应答消息拒绝了UE的协商请求，则UE可以通过再次发送INVITE消息的方式继续与gNB协商其他的语音编解码方案，也可以继续使用第二语音编解码方案。
步骤S405，UE在接收到第二应答消息时，将语音编解码方案调整为第一语音编解码。
这样，通过等待第二时长，UE可以在降级语音编解码方案之后的一段时间内不再与gNB协商语音编解码方案。在等待第二时长之后，UE考虑到网络环境发生变化，因此再次与网络设备协商升级语音编解码方案，如果协商成功，当再次执行VoNR通话时，UE和gNB就可以使用高级别的第一语音编解码方案编解码和传输语音数据，以实现更高的带宽和减少通话时的延迟抖动和丢包。
在一种实现方式中，如图13所示，UE将语音编解码方案调整为第二语音编解码之后， 还可以执行以下步骤：
步骤S406，UE检测自身驻留的NR小区的跟踪区是否发生变化。
具体实现中，UE可以在调整语音编解码方案至第二语音编解码之后就开始执行步骤S406，也可以在等待一个时长之后，在执行步骤S406。
步骤S407，当跟踪区发生变化时，UE向gNB发送第三请求消息。
当UE驻留的说明UE驻留的跟踪区发生变化时，说明UE驻留的NR小区的也发生了变化，即UE切换到了另一个gNB，因此步骤S406～步骤S408中的gNB于步骤S401～步骤S405中的gNB是不同的gNB。
其中，第三请求消息同样为INVITE消息，其格式可以参照第二请求消息实施，第三请求消息携带第一语音编解码的协商内容，用于请求gNB在后续通话时使用第一语音编解码。
进一步地，gNB如果同意恢复到第一语音编解码方案进行语音通话，会向UE发送第三应答消息，第三应答消息可以是SIP的200/OK消息。
步骤S408，UE在接收到第三应答消息时，将语音编解码方案调整为第一语音编解码。
这样，UE可以在驻留的NR小区的跟踪区发生变化时，再次与网络设备协商升级语音编解码方案，如果协商成功，当再次执行VoNR通话时，UE和gNB就可以使用高级别的第一语音编解码方案编解码和传输语音数据，以实现更高的带宽和减少通话时的延迟抖动和丢包。
在一种实现方式中，UE可以与gNB协商呼叫保持业务采用的语音编解码方案。
呼叫保持业务是指两个用户使用UE进行通话时，其中一方可以在不挂断的情况下拨打或者接听第三方的通话，并且可以两个通话之间切换。呼叫保持业务可以包括呼叫保持hold状态和呼叫保持解除unhold状态。示例地，如图14所示，当用户A与用户B通话时，用户A可以在不挂断通话的情况下，与用户C通话，此时用户A与用户B之间则进入hold状态，用户B能够在UE中听到音乐或者“嘟嘟”的通话保持提示声音；当用户A结束与用户C通话时，用户A可以挂断与C的通话或者使用户A与用户C之间进入hold状态，并切换回与用户B的通话，此时用户A与用户B之间则进入unhold状态。
由于在5G系统建设的前期阶段，其语音编解码方案的进展可能不同，gNB在呼叫保持业务中支持的语音编解码方案也可能不同。例如，一些gNB不支持EVS等更高级的语音编解码方案下的呼叫保持业务，这样，如果UE在EVS方案下发起呼叫保持，就会导致呼叫保持失败。为避免这种情况发生，如图15所示，UE可以在发起呼叫保持时执行以下步骤：
步骤S501，UE向gNB发送第四请求消息。
其中，第四请求消息可以是会话发起协议(session initiation protocol，SIP)的INVITE消息，携带第一语音编解码的协商内容，用于请求gNB在呼叫保持期间使用第一语音编解码。示例地，第一语音编解码是EVS。
gNB如果不具备在第一语音编解码方案下开启呼叫保持的能力，则可以向UE发送一个第四拒绝消息，以向UE指示其不同意在呼叫保持期间使用所述第一语音编解码，该第四拒绝消息可以是IMS的3xx～6xx应答消息；gNB如果具备在第一语音编解码方案下开启呼叫保持的能力，则可以向UE发送一个200/OK应答消息，以向UE指示其同意在呼叫保持期间使用所述第一语音编解码，使UE在第一语音编解码方案下呼叫保持状态。
步骤S502，UE在接收到第四拒绝消息时，向gNB发送第五请求消息。
其中，第五请求消息可以是会话发起协议(session initiation protocol，SIP)的INVITE 消息，携带第二语音编解码的协商内容，用于请求gNB在呼叫保持期间使用第二语音编解码。示例地，第二语音编解码是AMR-WB或者AMR。
可以理解的是，gNB如果具备在第二语音编解码方案下开启呼叫保持的能力，则可以向UE发送一个200/OK消息，使UE在第二语音编解码方案下进入呼叫保持状态；如果gNB不具备在第二语音编解码下开启呼叫保持的能力，那么gNB可以继续向UE发送第五拒绝消息，使得UE继续向gNB发送用于协商更低级语音编解码方案的INVITE消息，直到UE接收到了200/OK消息。
另外，如图16所示，UE还可以在呼叫保持解除时执行以下步骤：
步骤S503，UE向gNB发送第六请求消息。
其中，第六请求消息可以是会话发起协议(session initiation protocol，SIP)的INVITE消息，携带第一语音编解码的协商内容，用于请求gNB在呼叫保持解除时使用第一语音编解码。示例地，第一语音编解码是EVS。
gNB如果不具备在第一语音编解码方案下执行呼叫保持解除的能力，则可以向UE发送一个第六拒绝消息，该第六拒绝消息可以是IMS的3xx～6xx应答消息；gNB如果具备在第一语音编解码方案下执行呼叫保持解除的能力，则可以向UE发送一个200/OK应答消息。
步骤S504，UE在接收到第六拒绝消息时，向gNB发送第七请求消息。
其中，第七请求消息可以是会话发起协议(session initiation protocol，SIP)的INVITE消息，携带第二语音编解码的协商内容，用于请求gNB在保持解除时使用第二语音编解码。示例地，第二语音编解码是AMR-WB或者AMR。
可以理解的是，gNB如果具备在第二语音编解码方案下解除呼叫保持的能力，则可以向UE发送一个200/OK消息，使UE在第二语音编解码方案下解除呼叫保持状态；如果gNB不具备在第二语音编解码下解除呼叫保持的能力，那么gNB可以继续向UE发送第七拒绝消息，使得UE继续向gNB发送用于协商更低级语音编解码方案的INVITE消息，直到UE接收到了200/OK消息。
这样，在gNB不支持更高级的语音编解码方案下的呼叫保持业务时，UE和gNB可以协商使用更低级的语音编解码方案执行呼叫保持任务，以避免呼叫保持或者呼叫保持解除失败。
实施例(五)
本申请实施例(五)用于使UE在检测到基站(例如：gNB、ng-eNB等)执行EPS FB异常时，具备从异常中自动恢复的能力。
以基站为gNB为例，一般来说，当gNB不支持VoNR时，gNB需要在5GC发起建立专用承载5QI1的请求时，根据UE的无线接入能力、N26接口的部署情况、LTE的无线条件以及访问与移动性管理功能AMF的指示信息判断是否能够执行EPS FB流程；如果能够执行EPS FB，则回落到4G网络，UE与gNB之间会建立VoLTE的IMS语音的专用承载。
然而，在5G网络的部署前期，由于5G组网部署选项中的语音业务的方案可能不同，以及受到gNB和5GC的各网元的兼容性或者信令交互存在问题，或者工作状态异常等因素的影响，EPS FB可能会出现异常，例如无法建立LTE的IMS专用承载，导致呼叫失败。
为避免呼叫失败的情况发生，如图17所示，本申请实施例(五)可以包括以下步骤：
步骤S701，UE检测换域重拨EPS FB是否异常。
可以理解的是，在UE注册5GS期间，UE可能一次或者多次地发起通话。那么，在一种实现方式中，EPS FB异常的情况可以包括：UE在多次通话期间，建立LTE的IMS语音专 用承载失败的次数大于预设第四阈值，或者，UE与gNB释放5G语音专用承载5QI1的次数大于预设第五阈值。在另一种实现方式中，只要UE与eNB建立LTE的IMS语音专用承载失败，或者只要UE与gNB释放5G语音专用承载5QI1失败，则认为EPS FB异常。
步骤S702，UE在检测到换域重拨EPS FB异常时，关闭NR能力。
这样，UE就不会驻留在NR小区，而是只搜索LTE小区，并且选择在LTE小区驻留，同时不支持N1NAS信令模式。当用户拨打电话时，UE直接向gNB发起VoLTE通话请求或者CS域的通话请求，避免执行EPS FB流程，从而提高呼通率。
在一种实现方式中，考虑到在UE关闭NR能力之后的一段时间内，UE所处的网络环境可能发生变化，例如UE驻留到了其他的NR小区下，那么新的NR小区的gNB可能支持EPS FB能力。因此，如图17所示，UE在关闭NR能力之后，可以等待一个时长，再重启NR能力，以重新搜索NR小区，并在NR小区驻留。该等待时长例如可以是15分钟、30分钟、1个小时、3个小时等等，本申请实施例对此不做限定。UE的等待时长均可以通过定时器设置，本申请实施例对此不再赘述。
在一种实现方式中，考虑到NR网络还用于传输分组数据，因此，如果长时间关闭NR能力，可能会影响用户使用UE进行访问网络，例如观看在线视频和音乐、浏览网页等。因此，在UE关闭NR能力之后，UE可以检测是否在一段时间内连续地产生分组数据传输，例如10秒、20秒等；如果UE连续地产生分组数据传输，那么UE可以重新开启NR能力，使得分组数据通过NR传输，以提升传输速度。
在一种实现方式中，在UE重新开启NR能力之后，UE还可以检测是否在一段时间内没有分组数据传输，或者在一段时间内的分组数据传输的总数据流量是否小于一个流量阈值，例如在10分钟的时间内，分组数据的传输的总数据流量是否小于10MB；如果UE在一段时间内没有分组数据传输，或者在一段时间内的分组数据传输的总数据流量小于一个流量阈值，则UE可以重新关闭NR能力。
在一种实现方式中，在UE重新开启NR能力之后的一段时间内，UE可以检测用户是否打开了UE的拨号界面或者UE的通讯录，如果检测到用户打开UE的拨号界面或者通讯录，则UE重新关闭NR能力，使得UE在用户完成拨号之前就回落到4G，这样，当用户完成拨号发起呼叫时，UE直接通过eNB向EPC发起建立专用承载的请求，建立VoLTE通话，从而避免了EPS FB流程，提升呼通率。
在一种实现方式中，在UE关闭NR能力之后，UE可以基于GNSS服务(例如：北斗卫星导航系统、全球卫星定位系统等)或者基于位置的服务(location based services，LBS)检测自身的位置是否发生明显变化，当位置发生明显变化时，重新开启NR能力。具体实现中，当UE关闭NR能力时，UE可以基于GNSS服务或者LBS服务确定关闭NR能力时所在的位置1，在此之后，UE可以基于GNSS服务或者LBS服务继续检测自身的位置2，并且计算位置1与位置2之间的距离，如果该距离大于预设的距离阈值，例如5公里、10公里等，则重新开启NR能力。
可选的，在UE关闭NR能力之后，UE可以周期性地基于GNSS服务或者LBS服务继续检测自身的位置2；或者，在UE关闭NR能力之后，UE可以通过某些条件触发检测自身的位置2，触发条件例如可以包括：UE解锁屏幕、UE开启了使用GNSS服务或者LBS服务的应用程序APP、UE检测到用户打开了UE的拨号界面或者UE的通讯录等。本申请实施例对此不作限定。
上述本申请提供的实施例中，从终端设备UE本身、以及从UE与基站gNB之间交互的角度对本申请提供的信息指示方法的各方案进行了介绍。可以理解的是，终端设备UE为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
图18是本申请实施例提供的一种信息指示装置的结构示意图。
在一个实施例中，UE可以通过图18所示的硬件装置实现相应的功能。如图18所示，该信息指示装置可以包括：收发器801、存储器802和处理器803。
在一种实现方式中，处理器803可以包括一个或多个处理单元，例如：处理器803可以包括应用处理器，调制解调处理器，图形处理器，图像信号处理器，控制器，视频编解码器，数字信号处理器，基带处理器，和/或神经网络处理器等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。存储器802与处理器803耦合，用于存储各种软件程序和/或多组指令。在一些实施例中，存储器802可包括易失性存储器和/或非易失性存储器。收发器801为例如可以包括射频电路，移动通信模块，无线通信模块等，用于实现UE的无线通信功能。
在一个实施例中，当存储器802中的软件程序和/或多组指令被处理器803运行时，使得UE用于执行如下方法步骤：在注册5GS服务时，向gNB上报用于指示自身具备VoNR能力的UE能力信息。在检测到建立VoNR通话失败时，向gNB发送注册请求消息。接收gNB响应于注册请求消息发送的UE能力查询消息。响应于UE能力查询消息，向gNB发送第一UE能力信息。第一UE能力信息不包含ims-Parameters参数中的voiceOverNR的字段，即不包含子体加粗部分②。
这样，gNB在接收到第一UE能力信息之后，就可以根据第一UE能力信息认为UE不具备VoNR能力。那么，当用户再次拨打电话时，由于gNB认为UE当前不支持VoNR能力，因此gNB会拒绝5GC发起的建立专用承载5QI1的请求，而是触发EPS FB流程，向5GC发起重定向或者inter-RAT切换请求，并等待UE回落到LTE网络，由EPC和eNB通过VoLTE提供语音服务。由此，避免建立VoNR通话失败的异常情况再次发生，UE从VoNR通话异常中恢复。
可选的，当存储器802中的软件程序和/或多组指令被处理器803运行时，还使得UE用于执行如下方法步骤：检测自身驻留的NR跟踪区是否发生变化。在驻留的NR跟踪区发生变化时，向gNB发送注册请求消息。接收gNB响应于注册请求消息发送的UE能力查询消息。响应于UE能力查询消息，向gNB发送第二UE能力信息。第二UE能力信息的IMS-Parameters参数中包含与VoNR能力相关的参数，即包含字体加粗部分②。
这样，在UE驻留在新的跟踪区的NR小区期间，当用户再次拨打电话时，由于gNB认为UE当前支持VoNR能力，gNB会启动发起VoNR通话的语音专用承载5QI1，不会触发EPS FB，使得VoNR通话能力得以恢复。
可选的，当存储器802中的软件程序和/或多组指令被处理器803运行时，还使得UE用于执行如下方法步骤：在发送第一UE能力信息之后等待一个时长，在等待时长结束之后再去检测自身驻留的NR跟踪区是否发生变化。
在另一个实施例中，当存储器802中的软件程序和/或多组指令被处理器803运行时，使得UE用于执行如下方法步骤：在注册5GS服务时，可以向gNB上报用于指示自身具备RoHC能力的UE能力信息。在通话过程中检测到RoHC是否异常时，向gNB发送注册请求消息。接收gNB响应于注册请求消息发送的UE能力查询消息。响应于UE能力查询消息，向gNB发送第一UE能力信息。第一UE能力信息的PDCP-Parameters参数中的“profile0x0001”的值为“FALSE”。
这样，gNB在接收到第一UE能力信息之后，就可以根据第一UE能力信息认为UE不具备RoHC能力。那么，当用户再次拨打电话时，gNB和UE都不会启用RoHC功能，避免在通话过程中出现RoHC异常，以提高通话质量。
可选的，当存储器802中的软件程序和/或多组指令被处理器803运行时，还使得UE用于执行如下方法步骤：检测自身驻留的NR跟踪区是否发生变化。在驻留的NR跟踪区发生变化时，向gNB发送注册请求消息。接收gNB响应于注册请求消息发送的UE能力查询消息。响应于UE能力查询消息，向gNB发送第二UE能力信息。第二UE能力信息的PDCP-Parameters参数中的“profile0x0001”的值为“TRUE”。
这样，在UE驻留在新的跟踪区的NR小区期间，当用户再次拨打电话时，由于gNB知道UE当前支持RoHC能力，因此会启用RoHC功能，以提高传输效率。
在另一个实施例中，当存储器802中的软件程序和/或多组指令被处理器803运行时，使得UE用于执行如下方法步骤：在注册5GS服务时，向gNB上报用于指示自身具备VoNR能力和RoHC能力的UE能力信息。在检测到建立VoNR通话失败或者通话过程中RoHC是否异常时，向gNB发送注册请求消息。接收gNB响应于注册请求消息发送的UE能力查询消息。响应于UE能力查询消息，向gNB发送第一UE能力信息。第一UE能力信息不包含ims-Parameters参数中的voiceOverNR的字段，即不包含子体加粗部分②，以及，第一UE能力信息的PDCP-Parameters参数中的“profile0x0001”的值为“FALSE”。
这样，gNB在接收到第一UE能力信息之后，就可以根据第一UE能力信息认为UE不具备VoNR能力，以及认为UE不具备RoHC能力。那么，当用户再次拨打电话时，gNB会触发EPS FB流程，由EPC和eNB通过VoLTE在4G网络下建立通话，并且也不会启用RoHC功能，从而避免VoNR通话异常的现象发生，提高通话的接通率和通话质量。
可选的，当存储器802中的软件程序和/或多组指令被处理器803运行时，还使得UE用于执行如下方法步骤：检测自身驻留的NR跟踪区是否发生变化。在驻留的NR跟踪区发生变化时，向gNB发送注册请求消息。接收gNB响应于注册请求消息发送的UE能力查询消息。响应于UE能力查询消息，向gNB发送第二UE能力信息。第二UE能力信息的IMS-Parameters参数中包含与VoNR能力相关的参数，即包含字体加粗部分②，以及，第二UE能力信息的PDCP-Parameters参数中的“profile0x0001”的值为“TRUE”。
这样，在UE驻留在新的跟踪区的NR小区期间，当用户再次拨打电话时，由于gNB知道UE当前支持VoNR能力和RoHC能力，因此会启用VoNR能力和和RoHC功能，使得VoNR通话能力得以恢复，并且提高传输效率。
在另一个实施例中，当存储器802中的软件程序和/或多组指令被处理器803运行时，使得UE用于执行如下方法步骤：检测基于第一语音编解码的通话是否异常。在检测到基于第一语音编解码的通话异常时，向gNB发送第一请求消息。接收gNB在同意采用第二语音编解码方案进行语音通话时，向UE发送的第一应答消息，第一应答消息可以是SIP的200/OK 消息。在接收到第一应答消息时，将语音编解码方案调整为第二语音编解码。
这样，当再一次执行VoNR通话时，UE和gNB就可以使用低级别的第二语音编解码方案编解码和传输语音数据，实现了语音编解码方案的降级处理，避免采用高等级的语音编解码方案而出现杂音等通话异常问题。
可选的，当存储器802中的软件程序和/或多组指令被处理器803运行时，还使得UE用于执行如下方法步骤：将语音编解码方案调整为第二语音编解码之后，等待第二时长，向gNB发送第二请求消息。接收gNB在同意恢复到第一语音编解码方案进行语音通话时，向UE发送第二应答消息，第二应答消息可以是SIP的200/OK消息。在接收到第二应答消息时，将语音编解码方案调整为第一语音编解码。
这样，通过等待第二时长，UE可以在降级语音编解码方案之后的一段时间内不再与gNB协商语音编解码方案。在等待第二时长之后，UE考虑到网络环境发生变化，因此再次与网络设备协商升级语音编解码方案，如果协商成功，当再次执行VoNR通话时，UE和gNB就可以使用高级别的第一语音编解码方案编解码和传输语音数据，以实现更高的带宽和减少通话时的延迟抖动和丢包。
可选的，当存储器802中的软件程序和/或多组指令被处理器803运行时，还使得UE用于执行如下方法步骤：将语音编解码方案调整为第二语音编解码之后，检测自身驻留的NR跟踪区是否发生变化。当跟踪区发生变化时，UE向gNB发送第二请求消息。接收gNB在同意恢复到第一语音编解码方案进行语音通话时，向UE发送第二应答消息，第二应答消息可以是SIP的200/OK消息。在接收到第二应答消息时，将语音编解码方案调整为第一语音编解码。
这样，UE可以在驻留的NR小区的跟踪区发生变化时，再次与网络设备协商升级语音编解码方案，如果协商成功，当再次执行VoNR通话时，UE和gNB就可以使用高级别的第一语音编解码方案编解码和传输语音数据，以实现更高的带宽和减少通话时的延迟抖动和丢包。
可选的，当存储器802中的软件程序和/或多组指令被处理器803运行时，还使得UE用于执行如下方法步骤：在发起呼叫保持时，向gNB发送第三请求消息，第三请求消息用于请求gNB在呼叫保持期间使用第一语音编解码。在接收到gNB的第一拒绝消息时，向gNB发送第四请求消息，第一拒绝消息是gNB在不具备在第一语音编解码方案下开启呼叫保持的能力时，响应第三请求消息于发送的。在接收到第一拒绝消息时，向gNB发送第四请求消息，第四请求消息用于请求gNB在呼叫保持期间使用第二语音编解码。
可选的，当存储器802中的软件程序和/或多组指令被处理器803运行时，还使得UE用于执行如下方法步骤：在呼叫保持解除时，向gNB发送第五请求消息，第五请求消息用于请求gNB在呼叫保持解除时使用第一语音编解码。在接收到gNB的第二拒绝消息时，向gNB发送第六请求消息，第二拒绝消息是gNB在不具备在第一语音编解码方案下解除呼叫保持的能力时，响应第五请求消息于发送的。在接收到第二拒绝消息时，向gNB发送第六请求消息，第六请求消息用于请求gNB在解除保持时使用第二语音编解码。
这样，在gNB不支持更高级的语音编解码方案下的呼叫保持业务时，UE和gNB可以协商使用更低级的语音编解码方案执行呼叫保持任务，以避免呼叫保持或者呼叫保持解除失败。
在另一个实施例中，当存储器802中的软件程序和/或多组指令被处理器803运行时，使得UE用于执行如下方法步骤：检测换域重拨EPS FB是否异常。在检测到换域重拨EPS FB异常时，关闭NR能力。
这样，UE就不会驻留在NR小区，而是只搜索LTE小区，并且选择在LTE小区驻留，同时不支持N1NAS信令模式。当用户拨打电话时，UE直接向gNB发起VoLTE通话请求或者CS域的通话请求，避免执行EPS FB流程，从而提高呼通率。
可选的，当存储器802中的软件程序和/或多组指令被处理器803运行时，还使得UE用于执行如下方法步骤：在关闭NR能力之后，等待一个时长，再重启NR能力。
可选的，当存储器802中的软件程序和/或多组指令被处理器803运行时，还使得UE用于执行如下方法步骤：检测是否在一段时间内连续地产生分组数据传输，如果连续地产生分组数据传输，重启NR能力。
另外，在一些实施例中，UE可以通过软件模块来实现相应的功能。如图19所示，用于实现上述终端设备UE行为的功能的信息指示装置包括：接收单元901，处理单元902和发送单元903。
在一个实施例中，发送单元903用于在UE注册5GS服务时，向gNB上报用于指示自身具备VoNR能力的UE能力信息。处理单元902用于检测建立VoNR通话是否失败。发送单元903还用于在检测到建立VoNR通话失败时，向gNB发送注册请求消息。接收单元901用于接收gNB响应于注册请求消息发送的UE能力查询消息。发送单元903还用于响应于UE能力查询消息，向gNB发送第一UE能力信息。第一UE能力信息不包含ims-Parameters参数中的voiceOverNR的字段，即不包含子体加粗部分②。
可选的，处理单元902还用于检测自身驻留的NR跟踪区是否发生变化。发送单元903还用于在驻留的NR跟踪区发生变化时，向gNB发送注册请求消息。接收单元901还用于接收gNB响应于注册请求消息发送的UE能力查询消息。发送单元903还用于响应于UE能力查询消息，向gNB发送第二UE能力信息。第二UE能力信息的IMS-Parameters参数中包含与VoNR能力相关的参数，即包含字体加粗部分②。
可选的，发送单元903还用于在发送第一UE能力信息之后等待一个时长，在等待时长结束之后再去检测自身驻留的NR跟踪区是否发生变化。
在另一个实施例中，发送单元903用于在UE注册5GS服务时，向gNB上报用于指示自身具备RoHC能力的UE能力信息。处理单元902用于检测RoHC是否异常。发送单元903还用于在通话过程中检测到RoHC是否异常时，向gNB发送注册请求消息。接收单元901用于接收gNB响应于注册请求消息发送的UE能力查询消息。发送单元903还用于响应于UE能力查询消息，向gNB发送第一UE能力信息。第一UE能力信息的PDCP-Parameters参数中的“profile0x0001”的值为“FALSE”。
可选的，处理单元902还用于检测自身驻留的NR跟踪区是否发生变化。发送单元903还用于在驻留的NR跟踪区发生变化时，向gNB发送注册请求消息。发送单元903还用于响应于UE能力查询消息，向gNB发送第二UE能力信息。第二UE能力信息的PDCP-Parameters参数中的“profile0x0001”的值为“TRUE”。
在另一个实施例中，发送单元903用于在UE注册5GS服务时，向gNB上报用于指示自身具备VoNR能力和RoHC能力的UE能力信息。处理单元902用于检测建立VoNR通话是否失败或者通话过程中RoHC是否异常。发送单元903用于在检测到建立VoNR通话失败或者通话过程中RoHC是否异常时，向gNB发送注册请求消息。接收单元901用于接收gNB响应于注册请求消息发送的UE能力查询消息。发送单元903还用于响应于UE能力查询消息，向gNB发送第一UE能力信息。第一UE能力信息不包含ims-Parameters参数中的 voiceOverNR的字段，即不包含子体加粗部分②，以及，第一UE能力信息的PDCP-Parameters参数中的“profile0x0001”的值为“FALSE”。
可选的，处理单元902还用于检测自身驻留的NR跟踪区是否发生变化。发送单元903还用于在驻留的NR跟踪区发生变化时，向gNB发送注册请求消息。接收单元901还用于接收gNB响应于注册请求消息发送的UE能力查询消息。发送单元903还用于响应于UE能力查询消息，向gNB发送第二UE能力信息。第二UE能力信息的IMS-Parameters参数中包含与VoNR能力相关的参数，即包含字体加粗部分②，以及，第二UE能力信息的PDCP-Parameters参数中的“profile0x0001”的值为“TRUE”。
在另一个实施例中，处理单元902用于检测基于第一语音编解码的通话是否异常。发送单元903用于在基于第一语音编解码的通话异常时，向gNB发送第一请求消息。接收单元901用于接收gNB在同意采用第二语音编解码方案进行语音通话时，向UE发送的第一应答消息，第一应答消息可以是SIP的200/OK消息。处理单元902还用于在接收到第一应答消息时，将语音编解码方案调整为第二语音编解码。
可选的，发送单元903还用于在语音编解码方案调整为第二语音编解码之后，等待第二时长，向gNB发送第二请求消息。接收单元901还用于接收gNB在同意恢复到第一语音编解码方案进行语音通话时，向UE发送第二应答消息，第二应答消息可以是SIP的200/OK消息。处理单元902还用于在接收到第二应答消息时，将语音编解码方案调整为第一语音编解码。
可选的，发送单元903还用于在发起呼叫保持时，向gNB发送第四请求消息，第四请求消息用于请求gNB在呼叫保持期间使用第一语音编解码。发送单元903还用于在接收单元901接收到gNB的第四拒绝消息时，向gNB发送第五请求消息，第四拒绝消息是gNB在不具备在第一语音编解码方案下开启呼叫保持的能力时，响应第四请求消息于发送的，第五请求消息用于请求gNB在呼叫保持期间使用第二语音编解码。
可选的，发送单元903还用于在呼叫保持解除时，向gNB发送第六请求消息，第六请求消息用于请求gNB在呼叫保持解除时使用第一语音编解码。发送单元903还用于在接收单元901接收到gNB的第六拒绝消息时，向gNB发送第七请求消息，第六拒绝消息是gNB在不具备在第一语音编解码方案下解除呼叫保持的能力时，响应第六请求消息于发送的，第七请求消息用于请求gNB在解除保持时使用第二语音编解码。
在另一个实施例中，处理单元902用于检测换域重拨EPS FB是否异常。处理单元902还用于在检测到换域重拨EPS FB异常时，关闭NR能力。
本申请实施例还提供一种计算机存储介质，计算机存储介质中存储有计算机指令，当其在计算机上运行时，使得计算机执行上述各方面的方法。
本申请实施例还提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面的方法。
本申请还提供了一种芯片系统。该芯片系统包括处理器，用于支持上述装置或设备实现上述方面中所涉及的功能，例如，生成或处理上述方法中所涉及的信息。在一种可能的设计中，芯片系统还包括存储器，用于保存上述装置或设备必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
以上的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡 在本发明的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明的保护范围之内。

Claims (51)

  1. 一种网络系统，其特征在于，包括：
    第一基站，以及驻留在所述第一基站的第一新空口NR小区的终端设备UE；
    所述UE，用于在检测到VoNR通话异常时，向所述第一基站发送注册请求消息；
    所述第一基站，用于响应于所述注册请求消息，向所述UE发送UE能力查询消息；
    所述UE，还用于响应于所述UE能力查询消息，向所述第一基站发送第一UE能力信息，所述第一UE能力信息用于向所述第一基站指示所述UE不支持VoNR能力和/或者不支持鲁棒头压缩RoHC能力。
  2. 根据权利要求1所述的网络系统，其特征在于，所述VoNR通话异常包括在UE主叫或者被叫场景下建立VoNR通话失败，所述第一UE能力信息用于向所述第一基站指示所述UE不支持VoNR能力。
  3. 根据权利要求1所述的网络系统，其特征在于，所述VoNR通话异常包括VoNR通话过程中出现RoHC异常，所述第一UE能力信息用于向所述第一基站指示所述UE不支持RoHC能力。
  4. 根据权利要求1所述的网络系统，其特征在于，所述VoNR通话异常包括UE主叫或者被叫场景下建立VoNR通话失败或者VoNR通话过程中出现RoHC异常，所述第一UE能力信息用于向所述第一基站指示所述UE不支持VoNR能力和不支持RoHC能力。
  5. 根据权利要求2或4所述的网络系统，其特征在于，
    所述UE，具体用于在所述UE主叫或者被叫场景下建立VoNR通话失败的连续次数大于预设第一阈值时，向所述第一基站发送所述注册请求消息。
  6. 根据权利要求1-5任一项所述的网络系统，其特征在于，
    所述UE，具体用于在检测到VoNR通话异常时，在VoNR通话结束之后的移动管理空闲5GMM-IDLE模式下向所述第一基站发送所述注册请求消息。
  7. 根据权利要求1-6任一项所述的网络系统，其特征在于，
    所述UE，还用于向所述第一基站发送所述第一UE能力信息之后，检测自身驻留的NR小区是否从所述第一NR小区切换到第二NR小区，所述第一NR小区和所述第二NR小区的跟踪区不同；
    所述UE，还用于在检测到自身驻留的NR小区从所述第一NR小区切换到所述第二NR小区时，向所述第二NR小区对应的第二基站发送所述注册请求消息；
    所述第二基站，用于响应于所述注册请求消息，向所述UE发送所述UE能力查询消息；
    所述UE，还用于响应于所述UE能力查询消息，向所述第二基站发送第二UE能力信息，所述第二UE能力信息用于向所述第二基站指示所述UE支持VoNR能力和/或者支持RoHC能力。
  8. 根据权利要求7所述的网络系统，其特征在于，
    所述UE，具体用于在建立VoNR通话失败的连续次数大于预设第二阈值时，等待第一预设时长，然后检测自身驻留的NR小区是否从所述第一NR小区切换到所述第二NR小区。
  9. 一种网络系统，其特征在于，包括：
    第一基站，以及驻留在所述第一基站的第一NR小区的终端设备UE；
    所述UE，用于在检测到基于第一语音编解码的通话异常时，向所述第一基站发送第一请求消息，所述第一语音编解码是所述UE与所述第一基站当前使用的语音编解码方案，所述第一请求消息用于请求所述第一基站使用第二语音编解码，所述第二语音编解码的质量标准低于所述第一语音编解码的质量标准；
    所述第一基站，用于响应于所述第一请求消息，向所述UE发送第一应答消息，所述第一应答消息用于向所述UE指示所述第一基站同意使用所述第二语音编解码；
    所述UE，还用于响应于所述第一应答消息，将当前使用的语音编解码方案调整为第二语音编解码。
  10. 根据权利要求9所述的网络系统，其特征在于，
    所述UE，还用于在当前使用的语音编解码方案调整为第二语音编解码之后，等待第二预设时长，然后向所述第一基站发送第二请求消息，所述第二请求消息用于请求所述第一基站使用第一语音编解码；
    所述第一基站，还用于响应于所述第二请求消息，向所述UE发送第二应答消息，所述第二应答消息用于向所述UE指示所述第一基站同意使用所述第一语音编解码；
    所述UE，还用于响应于所述第二应答消息，将当前使用的语音编解码方案调整为第一语音编解码。
  11. 根据权利要求9所述的网络系统，其特征在于，
    所述第一基站，用于响应于所述第一请求消息，向所述UE发送第一拒绝消息，所述第一拒绝消息用于向所述UE指示所述第一基站不同意使用所述第二语音编解码；
    所述UE，还用于响应于所述第一拒绝消息，继续使用第一语音编解码。
  12. 根据权利要求10所述的网络系统，其特征在于，
    所述第一基站，还用于响应于所述第二请求消息，向所述UE发送第二拒绝消息，所述第二拒绝消息用于向所述UE指示所述第一基站不同意使用所述第一语音编解码；
    所述UE，还用于响应于所述第二拒绝消息，继续使用第二语音编解码。
  13. 根据权利要求9所述的网络系统，其特征在于，
    所述UE，还用于在当前使用的语音编解码方案调整为第二语音编解码之后，检测自身驻留的NR小区是否从所述第一NR小区切换到第二NR小区，所述第一NR小区和所述第二NR小区的跟踪区不同；
    所述UE，还用于在检测到自身驻留的NR小区从所述第一NR小区切换到所述第二NR 小区时，向所述第二NR小区对应的第二基站发送第三请求消息，所述第三请求消息用于请求所述第二基站使用第一语音编解码；
    所述第二基站，还用于响应于所述第三请求消息，向所述UE发送第三应答消息，所述第三应答消息用于向所述UE指示所述第二基站同意使用所述第一语音编解码；
    所述UE，还用于响应于所述第三应答消息，将当前使用的语音编解码方案调整为第一语音编解码。
  14. 根据权利要求9-13任一项所述的网络系统，其特征在于，所述基于第一语音编解码的通话异常包括：基于所述第一语音编解码的通话出现杂音，并且杂音的通话次数连续地大于预设第二阈值。
  15. 根据权利要求9所述的网络系统，其特征在于，当所述UE在通话过程中发起呼叫保持hold时：
    所述UE，还用于向所述第一基站发送第四请求消息，所述第四请求消息用于请求所述第一基站在呼叫保持期间使用第一语音编解码；
    所述第一基站，还用于响应于所述第四请求消息，向所述UE发送第四应答消息，所述第四应答消息用于向所述UE指示所述第一基站同意在呼叫保持期间使用所述第一语音编解码。
  16. 根据权利要求15所述的网络系统，其特征在于，
    所述第一基站，还用于响应于所述第四请求消息，向所述UE发送第四拒绝消息，所述第四拒绝消息用于向所述UE指示所述第一基站不同意在呼叫保持期间使用所述第一语音编解码；
    所述UE，还用于响应于所述第四拒绝消息，向所述第一基站发送第五请求消息，所述第五请求消息用于请求所述第一基站在呼叫保持期间使用第二语音编解码。
  17. 根据权利要求9所述的网络系统，其特征在于，当所述UE在通话过程中发起呼叫保持解除unhold时：
    所述UE，还用于向所述第一基站发送第六请求消息，所述第六请求消息用于请求所述第一基站在呼叫保持解除之后使用第一语音编解码；
    所述第一基站，还用于响应于所述第六请求消息，向所述UE发送第六应答消息，所述第六应答消息用于向所述UE指示所述第一基站同意在呼叫保持解除之后使用所述第一语音编解码。
  18. 根据权利要求17所述的网络系统，其特征在于，
    所述第一基站，还用于响应于所述第六请求消息，向所述UE发送第六拒绝消息，所述第六拒绝消息用于向所述UE指示所述第一基站不同意在呼叫保持解除之后使用所述第一语音编解码；
    所述UE，还用于响应于所述第六拒绝消息，向所述第一基站发送第七请求消息，所述第七请求消息用于请求所述第一基站在呼叫保持解除之后使用第二语音编解码。
  19. 一种网络系统，其特征在于，包括：
    第一基站，以及驻留在所述第一基站的NR小区的终端设备UE；
    所述UE，用于在检测到换域重拨EPS FB异常时，关闭NR能力；
    所述UE，还用于在关闭NR能力之后，等待第三预设时长，然后开启NR能力。
  20. 根据权利要求19所述的网络系统，其特征在于，
    所述UE，还用于在关闭NR能力之后，如果检测到连续产生分组数据传输，并且所述分组数据传输产生的总数据流量大于预设的流量阈值，则开启NR能力。
  21. 根据权利要求19所述的网络系统，其特征在于，
    所述UE，还用于在关闭NR能力之后，如果检测到自身的位置变化距离大于预设的距离阈值，则开启NR能力。
  22. 根据权利要求19-21任一项所述的网络系统，其特征在于，
    所述UE关闭NR能力，包括：所述UE不再驻留所述NR小区，同时搜索长期演进技术LTE小区，并且在所述LTE小区驻留。
  23. 根据权利要求19-21任一项所述的网络系统，其特征在于，
    所述UE开启NR能力，包括：所述UE搜索所述NR小区，并且在所述NR小区驻留。
  24. 根据权利要求19-23任一项所述的网络系统，其特征在于，
    所述EPS FB异常，包括：在所述UE主叫或者被叫的通话场景下，所述UE释放与所述第一基站的5G语音专用承载失败，或者，所述UE与第二基站建立LTE语音专用承载失败，所述第二基站为LTE小区对应的基站。
  25. 根据权利要求19-23任一项所述的网络系统，其特征在于，
    所述EPS FB异常，包括：在所述UE主叫或者被叫的通话场景下，所述UE释放与所述第一基站的5G语音专用承载失败，并且连续失败的次数大于预设第四阈值，或者，所述UE与第二基站建立LTE语音专用承载失败，并且连续失败的次数大于预设第五阈值。
  26. 一种终端设备，其特征在于，包括：收发器、存储器和处理器，所述存储器存储有计算机程序指令，当所述程序指令被所述处理器执行时，使得所述终端设备实现如下方法步骤：
    在检测到VoNR通话异常时，向第一基站发送注册请求消息；
    响应于UE能力查询消息，向所述第一基站发送第一UE能力信息，其中，所述UE能力查询消息是所述第一基站响应于所述注册请求消息向所述UE发送的，所述第一UE能力信息用于向所述第一基站指示所述UE不支持VoNR能力和/或者不支持鲁棒头压缩RoHC能力。
  27. 根据权利要求26所述的终端设备，其特征在于，所述VoNR通话异常包括在UE主 叫或者被叫场景下建立VoNR通话失败，所述第一UE能力信息用于向所述第一基站指示所述UE不支持VoNR能力。
  28. 根据权利要求26所述的终端设备，其特征在于，所述VoNR通话异常包括VoNR通话过程中出现RoHC异常，所述第一UE能力信息用于向所述第一基站指示所述UE不支持RoHC能力。
  29. 根据权利要求26所述的终端设备，其特征在于，所述VoNR通话异常包括UE主叫或者被叫场景下建立VoNR通话失败或者VoNR通话过程中出现RoHC异常，所述第一UE能力信息用于向所述第一基站指示所述UE不支持VoNR能力和不支持RoHC能力。
  30. 根据权利要求27或29所述的终端设备，其特征在于，当所述程序指令被所述处理器执行时，使得所述终端设备具体实现如下方法步骤：
    在所述UE主叫或者被叫场景下建立VoNR通话失败的连续次数大于预设第一阈值时，向所述第一基站发送所述注册请求消息。
  31. 根据权利要求26-30任一项所述的终端设备，其特征在于，当所述程序指令被所述处理器执行时，使得所述终端设备具体实现如下方法步骤：
    在检测到VoNR通话异常时，在VoNR通话结束之后的移动管理空闲5GMM-IDLE模式下向所述第一基站发送所述注册请求消息。
  32. 根据权利要求26-31任一项所述的终端设备，其特征在于，当所述程序指令被所述处理器执行时，还使得所述终端设备实现如下方法步骤：
    向所述第一基站发送所述第一UE能力信息之后，检测自身驻留的NR小区是否从所述第一NR小区切换到第二NR小区，所述第一NR小区和所述第二NR小区的跟踪区不同；
    在检测到自身驻留的NR小区从所述第一NR小区切换到所述第二NR小区时，向所述第二NR小区对应的第二基站发送所述注册请求消息；
    响应于所述第二基站发送的所述UE能力查询消息，向所述第二基站发送第二UE能力信息，所述第二UE能力信息用于向所述第二基站指示所述UE支持VoNR能力和/或者支持RoHC能力。
  33. 根据权利要求32所述的终端设备，其特征在于，当所述程序指令被所述处理器执行时，使得所述终端设备具体实现如下方法步骤：
    在建立VoNR通话失败的连续次数大于预设第二阈值时，等待第一预设时长，然后检测自身驻留的NR小区是否从所述第一NR小区切换到所述第二NR小区。
  34. 一种终端设备，其特征在于，包括：收发器、存储器和处理器，所述存储器存储有计算机程序指令，当所述程序指令被所述处理器执行时，使得所述终端设备实现如下方法步骤：
    在检测到基于第一语音编解码的通话异常时，向第一基站发送第一请求消息，所述第一 语音编解码是所述UE与所述第一基站当前使用的语音编解码方案，所述第一请求消息用于请求所述第一基站使用第二语音编解码，所述第二语音编解码的质量标准低于所述第一语音编解码的质量标准；
    响应于第一应答消息，将当前使用的语音编解码方案调整为第二语音编解码，其中，所述第一应答消息是所述第一基站响应于所述第一请求消息发送的，所述第一应答消息用于向所述UE指示所述第一基站同意使用所述第二语音编解码。
  35. 根据权利要求34所述的终端设备，其特征在于，当所述程序指令被所述处理器执行时，还使得所述终端设备实现如下方法步骤：
    在当前使用的语音编解码方案调整为第二语音编解码之后，等待第二预设时长，然后向所述第一基站发送第二请求消息，所述第二请求消息用于请求所述第一基站使用第一语音编解码；
    响应于第二应答消息，将当前使用的语音编解码方案调整为第一语音编解码，其中，所述第二应答消息是所述第一基站响应于所述第二请求消息发送的，所述第二应答消息用于向所述UE指示所述第一基站同意使用所述第一语音编解码。
  36. 根据权利要求34所述的终端设备，其特征在于，当所述程序指令被所述处理器执行时，还使得所述终端设备实现如下方法步骤：
    响应于第一拒绝消息，继续使用第一语音编解码，其中，所述第一拒绝消息是所述第一基站响应于所述第一请求消息发送的，所述第一拒绝消息用于向所述UE指示所述第一基站不同意使用所述第二语音编解码。
  37. 根据权利要求35所述的终端设备，其特征在于，当所述程序指令被所述处理器执行时，还使得所述终端设备实现如下方法步骤：
    响应于第二拒绝消息，继续使用第二语音编解码，其中，所述第二拒绝消息是所述第一基站响应于所述第二请求消息发送的，所述第二拒绝消息用于向所述UE指示所述第一基站不同意使用所述第一语音编解码。
  38. 根据权利要求34所述的终端设备，其特征在于，当所述程序指令被所述处理器执行时，还使得所述终端设备实现如下方法步骤：
    在当前使用的语音编解码方案调整为第二语音编解码之后，检测自身驻留的NR小区是否从所述第一NR小区切换到第二NR小区，所述第一NR小区和所述第二NR小区的跟踪区不同；
    在检测到自身驻留的NR小区从所述第一NR小区切换到所述第二NR小区时，向所述第二NR小区对应的第二基站发送第三请求消息，所述第三请求消息用于请求所述第二基站使用第一语音编解码；
    响应于所述第三应答消息，将当前使用的语音编解码方案调整为第一语音编解码，其中，所述第三应答消息是所述第二基站响应于所述第三请求消息发送的，所述第三应答消息用于向所述UE指示所述第二基站同意使用所述第一语音编解码。
  39. 根据权利要求34-38任一项所述的终端设备，其特征在于，所述基于第一语音编解码的通话异常包括：基于所述第一语音编解码的通话出现杂音，并且杂音的通话次数连续地大于预设第二阈值。
  40. 根据权利要求34所述的终端设备，其特征在于，当所述程序指令被所述处理器执行时，还使得所述终端设备实现如下方法步骤：
    在通话过程中发起呼叫保持hold时，向所述第一基站发送第四请求消息，所述第四请求消息用于请求所述第一基站在呼叫保持期间使用第一语音编解码。
  41. 根据权利要求40所述的终端设备，其特征在于，当所述程序指令被所述处理器执行时，还使得所述终端设备实现如下方法步骤：
    响应于第四拒绝消息，向所述第一基站发送第五请求消息，其中，所述第四拒绝消息是所述第一基站响应于所述第四请求消息发送的，所述第四拒绝消息用于向所述UE指示所述第一基站不同意在呼叫保持期间使用所述第一语音编解码，所述第五请求消息用于请求所述第一基站在呼叫保持期间使用第二语音编解码。
  42. 根据权利要求34所述的终端设备，其特征在于，当所述程序指令被所述处理器执行时，还使得所述终端设备实现如下方法步骤：
    在通话过程中发起呼叫保持解除unhold时，向所述第一基站发送第六请求消息，所述第六请求消息用于请求所述第一基站在呼叫保持解除之后使用第一语音编解码。
  43. 根据权利要求42所述的终端设备，其特征在于，当所述程序指令被所述处理器执行时，还使得所述终端设备实现如下方法步骤：
    响应于所述第六拒绝消息，向所述第一基站发送第七请求消息，其中，所述第六拒绝消息是所述第一基站响应于所述第六请求消息发送的，所述第六拒绝消息用于向所述UE指示所述第一基站不同意在呼叫保持解除之后使用所述第一语音编解码，所述第七请求消息用于请求所述第一基站在呼叫保持解除之后使用第二语音编解码。
  44. 一种终端设备，其特征在于，包括：收发器、存储器和处理器，所述存储器存储有计算机程序指令，当所述程序指令被所述处理器执行时，使得所述终端设备实现如下方法步骤：
    在检测到换域重拨EPS FB异常时，关闭NR能力；
    在关闭NR能力之后，等待第三预设时长，然后开启NR能力。
  45. 根据权利要求44所述的终端设备，其特征在于，当所述程序指令被所述处理器执行时，还使得所述终端设备实现如下方法步骤：
    在关闭NR能力之后，如果检测到连续产生分组数据传输，并且所述分组数据传输产生的总数据流量大于预设的流量阈值，则开启NR能力。
  46. 根据权利要求44所述的终端设备，其特征在于，当所述程序指令被所述处理器执行 时，还使得所述终端设备实现如下方法步骤：
    在关闭NR能力之后，如果检测到自身的位置变化距离大于预设的距离阈值，则开启NR能力。
  47. 根据权利要求44-46任一项所述的终端设备，其特征在于，所述UE关闭NR能力，包括：所述UE不再驻留所述NR小区，同时搜索长期演进技术LTE小区，并且在所述LTE小区驻留。
  48. 根据权利要求44-46任一项所述的终端设备，其特征在于，所述UE开启NR能力，包括：所述UE搜索所述NR小区，并且在所述NR小区驻留。
  49. 根据权利要求44-48任一项所述的终端设备，其特征在于，所述EPS FB异常，包括：在所述UE主叫或者被叫的通话场景下，所述UE释放与所述第一基站的5G语音专用承载失败，或者，所述UE与第二基站建立LTE语音专用承载失败，所述第二基站为LTE小区对应的基站。
  50. 根据权利要求44-48任一项所述的终端设备，其特征在于，所述EPS FB异常，包括：在所述UE主叫或者被叫的通话场景下，所述UE释放与所述第一基站的5G语音专用承载失败，并且连续失败的次数大于预设第四阈值，或者，所述UE与第二基站建立LTE语音专用承载失败，并且连续失败的次数大于预设第五阈值。
  51. 一种芯片系统，其特征在于，包括：存储器和处理器，所述存储器存储有计算机程序指令，所述程序指令被所述处理器执行时，使得所述芯片系统实现如权利要求1-25任一项中的终端设备或基站的功能。
PCT/CN2021/110225 2020-09-07 2021-08-03 一种网络系统和终端设备 WO2022048375A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010928283.1A CN114158033B (zh) 2020-09-07 2020-09-07 一种网络系统和终端设备
CN202010928283.1 2020-09-07

Publications (1)

Publication Number Publication Date
WO2022048375A1 true WO2022048375A1 (zh) 2022-03-10

Family

ID=80460393

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/110225 WO2022048375A1 (zh) 2020-09-07 2021-08-03 一种网络系统和终端设备

Country Status (2)

Country Link
CN (1) CN114158033B (zh)
WO (1) WO2022048375A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115134892A (zh) * 2022-08-30 2022-09-30 荣耀终端有限公司 基于异网漫游的接入方法和装置
WO2023229264A1 (en) * 2022-05-25 2023-11-30 Samsung Electronics Co., Ltd. System and method for connection management
WO2024007975A1 (zh) * 2022-07-07 2024-01-11 维沃移动通信有限公司 通话能力监测方法、装置、终端和可读存储介质
WO2024057075A1 (en) * 2022-09-16 2024-03-21 Telefonaktiebolaget Lm Ericsson (Publ) Systems and methods enabling adaptive ue configuration at incoming handover based on incoming service(s)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114916035B (zh) * 2022-04-24 2023-06-09 荣耀终端有限公司 通信方法、电子设备及存储介质
CN115278640A (zh) * 2022-07-25 2022-11-01 Oppo广东移动通信有限公司 同步vonr通话能力的方法、装置、终端设备及存储介质
CN116723552A (zh) * 2022-10-31 2023-09-08 荣耀终端有限公司 通信方法、装置、设备和存储介质
CN115802335A (zh) * 2022-11-01 2023-03-14 中国联合网络通信集团有限公司 一种终端VoNR能力的获取方法、装置及可读存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106341803A (zh) * 2016-09-05 2017-01-18 深圳市万普拉斯科技有限公司 提高lte终端设备呼通率的方法及终端设备
CN110234141A (zh) * 2018-03-06 2019-09-13 中国移动通信集团终端有限公司 保持语音通话连续性的方法、装置、设备和介质
CN110536343A (zh) * 2019-05-16 2019-12-03 Oppo广东移动通信有限公司 模式控制方法、用户设备、网络设备及存储介质
CN110691385A (zh) * 2018-07-06 2020-01-14 中国移动通信有限公司研究院 语音业务的处理方法、装置、相关设备及存储介质
CN111372327A (zh) * 2020-02-18 2020-07-03 华为技术有限公司 基于5g sa网络的呼叫方法、电子设备及系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11477708B2 (en) * 2018-06-21 2022-10-18 Qualcomm Incorporated Packet switched voice call capability indication in wireless communications
CN109862622B (zh) * 2019-01-16 2021-02-23 维沃移动通信有限公司 上报能力信息的方法、设备及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106341803A (zh) * 2016-09-05 2017-01-18 深圳市万普拉斯科技有限公司 提高lte终端设备呼通率的方法及终端设备
CN110234141A (zh) * 2018-03-06 2019-09-13 中国移动通信集团终端有限公司 保持语音通话连续性的方法、装置、设备和介质
CN110691385A (zh) * 2018-07-06 2020-01-14 中国移动通信有限公司研究院 语音业务的处理方法、装置、相关设备及存储介质
CN110536343A (zh) * 2019-05-16 2019-12-03 Oppo广东移动通信有限公司 模式控制方法、用户设备、网络设备及存储介质
CN111372327A (zh) * 2020-02-18 2020-07-03 华为技术有限公司 基于5g sa网络的呼叫方法、电子设备及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "NR to UTRAN SRVCC Procedure", 3GPP DRAFT; R2-1906111, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, USA; 20190513 - 20190517, 2 May 2019 (2019-05-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051710438 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023229264A1 (en) * 2022-05-25 2023-11-30 Samsung Electronics Co., Ltd. System and method for connection management
WO2024007975A1 (zh) * 2022-07-07 2024-01-11 维沃移动通信有限公司 通话能力监测方法、装置、终端和可读存储介质
CN115134892A (zh) * 2022-08-30 2022-09-30 荣耀终端有限公司 基于异网漫游的接入方法和装置
CN115134892B (zh) * 2022-08-30 2023-02-28 荣耀终端有限公司 基于异网漫游的接入方法和装置
WO2024057075A1 (en) * 2022-09-16 2024-03-21 Telefonaktiebolaget Lm Ericsson (Publ) Systems and methods enabling adaptive ue configuration at incoming handover based on incoming service(s)

Also Published As

Publication number Publication date
CN114158033A (zh) 2022-03-08
CN114158033B (zh) 2024-04-26

Similar Documents

Publication Publication Date Title
WO2022048375A1 (zh) 一种网络系统和终端设备
JP6093066B2 (ja) ピアツーピア直接リンク通信にネットワーク接続を提供する方法および装置
WO2022252725A1 (zh) 用于提升sa网络下电话呼通率的通信系统及用户设备
US8199719B2 (en) Methods and apparatus for performing handover between a long term evolution (LTE) network and another type of radio access network
WO2023061324A1 (zh) 数据处理方法、装置、终端设备以及存储介质
EP3424262A1 (en) Cellular internet of things data transfer via a mobility management entity
CN114698046B (zh) 呼叫接收方法和通信装置
US20180091600A1 (en) Quick relay session management protocol
US10313941B2 (en) Apparatus, systems and methods for improved mobility between networks
WO2023246248A1 (zh) 一种被叫寻呼方法和装置
CN113498108B (zh) 基于业务类型调整数据传输策略的芯片、设备以及方法
WO2019061110A1 (zh) 一种接入链路的管理方法、设备、存储介质及系统
TWI728263B (zh) 與長期演進網路及新無線網路通訊的裝置及方法
WO2018129728A1 (zh) 非连续接收的管理方法和装置
TW201902257A (zh) 用戶設備及位置更新方法
TWI792616B (zh) 從側鏈路中繼失敗中恢復的裝置和方法
CN112368976A (zh) 用于执行组通信的终端和方法
CN113709900B (zh) 一种终端网络连接的控制方法及其介质和芯片
US11064383B2 (en) Intelligent IMS based on real-time baseband feedback
US10271185B1 (en) Method and apparatus for short message service re-transmission in mobile communications
US20230328825A1 (en) Configuration reset method and apparatus, and terminal device
TW202408278A (zh) 針對移動終止服務之避免存取禁止
CN117135775A (zh) 一种通信方法及终端设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21863443

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21863443

Country of ref document: EP

Kind code of ref document: A1