WO2023109205A1 - 呼叫接收方法和通信装置 - Google Patents

呼叫接收方法和通信装置 Download PDF

Info

Publication number
WO2023109205A1
WO2023109205A1 PCT/CN2022/117661 CN2022117661W WO2023109205A1 WO 2023109205 A1 WO2023109205 A1 WO 2023109205A1 CN 2022117661 W CN2022117661 W CN 2022117661W WO 2023109205 A1 WO2023109205 A1 WO 2023109205A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
domain
call
time period
message
Prior art date
Application number
PCT/CN2022/117661
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 WO2023109205A1 publication Critical patent/WO2023109205A1/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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure

Definitions

  • the present application relates to the field of wireless communication, in particular to a call receiving method and a communication device.
  • Embodiments of the present application provide a call receiving method and a communication device, which are used to improve the call success rate of a terminal device in SA mode.
  • a method for receiving a call comprising: a terminal device in an independent networking mode receives a call message from a network in a new air interface (new radio, NR) domain, and the call message is used to request a call terminal device; If the terminal device does not receive expected information from the network within the first time period after the preset call flow, the terminal device falls back to the long term evolution (long term evolution, LTE) domain to receive the call after the first time period.
  • NR new air interface
  • the call receiving method when a terminal device in SA mode receives a call message from the network in the NR domain, when a failure occurs on the 5G network, it will cause the terminal to The device cannot receive the expected information from the network, so the terminal device actively falls back to the LTE domain after the first time period to receive the call. Since terminal devices usually wait for the network side to indicate whether to fall back to the LTE domain, when the 5G network fails, the 5G network cannot instruct the terminal device to fall back to the LTE domain. Therefore, the call receiving method provided by the embodiment of the present application can improve the calling success rate of the terminal device in SA mode by actively falling back to the LTE domain to try to receive the call in the LTE domain.
  • the preset call process is a radio resource control (radio resource control, RRC) reconfiguration process between the terminal device and the fifth-generation 5G access network device, and the RRC reconfiguration process is performed by the terminal device
  • RRC radio resource control
  • the service request process with the 5G core network is triggered, and the expected information includes an INVITE message. That is to say, after the RRC reconfiguration process triggered by the service request process is completed between the terminal device and the 5G core network, the terminal device expects to receive an INVITE message from the 5G core network. Due to network failures and other reasons, the terminal device cannot receive the invitation ( INVITE) message, the terminal device actively falls back to the LTE domain to receive the call after the first time period.
  • INVITE invitation
  • the preset call flow is that the terminal device sends a 183 session progress message to the service centralization and continuity application server (service centralization and continuity application server, SCC AS) through the 5G access network device and the 5G core network , the expected information is bearer indication information or fallback indication information, the bearer indication information is used to instruct the terminal device to establish or modify a dedicated voice bearer in the NR domain, and the fallback indication information is used to instruct the terminal device to fall back to the LTE domain. That is to say, after the terminal device sends the 183 session progress message to the service centralization and continuity application server through the 5G access network device and the 5G core network, the terminal device expects to receive bearer indication information or fallback indication information from the 5G core network. For reasons such as failure or sudden interference leading to uplink transmission difficulties, the terminal device cannot receive the bearer indication information or the fallback indication information, and the terminal device actively falls back to the LTE domain to receive the call after the first time period.
  • the service centralization and continuity application server service centralization and continuity application server
  • the method further includes: within a second time period after the terminal device falls back to the LTE domain, if the terminal device does not receive a call in the LTE domain, the terminal device returns to the LTE domain after the second time period.
  • NR domain so that the terminal device can receive an incoming call from the opposite end to redial in the LTE domain.
  • the terminal device returning to the NR domain after the second time period includes: the terminal device receives a redialed call in the LTE domain within a third time period after the second time period; The NR domain is returned after the time period. The terminal device returns to the NR domain after a delay in the LTE domain for a period of time, so as to receive the redialed call from the opposite end in the LTE domain.
  • the length of the third time period is determined by the number of times the terminal device does not receive the expected information. The greater the number of times, the longer the length of the third time period; The shorter the time length of the three time periods. The more times the terminal device fails to receive the expected information, the greater the impact of the network failure in the NR domain, so the longer the time it spends in the LTE domain to receive incoming calls.
  • the terminal device if the terminal device does not receive a call in the LTE domain within the second time period after the terminal device falls back to the LTE domain, the terminal device returns to the NR domain after the second time period, including: Within the second time period after the terminal device falls back to the LTE domain, if the terminal device does not receive the indication information instructing the terminal device to establish a dedicated voice bearer in the LTE domain after sending the 183 session progress message in the LTE domain, and does not receive If the call is received, the terminal equipment returns to the NR domain after the second time period. That is to say, when the terminal device cannot establish a dedicated bearer in the LTE domain and receive the call, the terminal device returns to the NR domain after the second time period, so as to receive the call in the NR domain.
  • the method further includes: the terminal device counts the success rate of falling back to the LTE domain, and the success rate refers to the ratio of the number of times the terminal device successfully falls back to the LTE domain to the total number of times the terminal device falls back to the LTE domain.
  • the successful fallback of the device to the LTE domain means that the terminal device receives a call within the second time period after falling back to the LTE domain; the terminal device determines whether to fall back to the LTE domain within a certain period of time according to the success rate.
  • the terminal device does not actively fall back to the LTE domain within a certain period of time; if the success rate of falling back to the LTE domain and receiving calls in the LTE domain is very low High, the terminal device can actively fall back to the LTE domain within a certain period of time and receive calls in the LTE domain.
  • the terminal device determines whether to fall back to the LTE domain within a certain period of time according to the success rate, including: if the success rate is less than a success rate threshold, the terminal device does not fall back to the LTE domain within a certain period of time. That is to say, if the success rate of falling back to the LTE domain and receiving calls in the LTE domain is very low, the terminal device does not actively fall back to the LTE domain within a certain period of time.
  • the method further includes: when the terminal device does not fall back to the LTE domain within a certain period of time, if the terminal device receives a paging message, and the terminal device receives the paging message in the fourth No INVITE message or power leakage reminder message from the network is received within the time period, and the terminal device receives the power leakage reminder message within the fifth time period after receiving the paging message, then the terminal device falls back to the LTE domain to receive the call; wherein , the fourth time period does not overlap with the fifth time period.
  • the terminal device can determine the missed call by analyzing the electric leakage reminder text message (the short message including the electric leakage reminder keyword), and actively falls back to the LTE domain to receive the call.
  • a communication device in an independent networking mode, and the communication device includes a transceiver module and a processing module.
  • the transceiver module is used to receive a call message from the network in the NR domain, and the call message is used to request to call the communication device; if within the first time period after the preset call flow, the transceiver module does not receive the expected information from the network , the processing module falls back to the LTE domain to receive the call after the first time period.
  • the preset call process is the RRC reconfiguration process between the terminal device and the fifth-generation 5G access network device, and the RRC reconfiguration process consists of the service request process between the terminal device and the 5G core network Triggered, the expected information includes an INVITE message.
  • the preset call flow is that the communication device sends a 183 session progress message to the service centralization and continuity application server through the 5G access network equipment and the 5G core network, and the expected information is bearer indication information or fallback indication information
  • the bearer instruction information is used to instruct the communication device to establish or modify a dedicated voice bearer in the NR domain, and the fallback instruction information is used to instruct the communication device to fall back to the LTE domain.
  • the processing module is further configured to: return to the NR domain after the second time period if the transceiver module does not receive a call in the LTE domain within a second time period after falling back to the LTE domain.
  • the transceiver module receives the redialed call in the LTE domain within a third time period after the second time period; the processing module returns to the NR domain after the third time period.
  • the length of the third time period is determined by the number of times the transceiver module does not receive expected information.
  • the processing module within the second period of time after the processing module falls back to the LTE domain, if the transceiver module does not receive a dedicated notification instructing the communication device to establish voice in the LTE domain after sending the 183 session progress message in the LTE domain If there is bearer indication information and no call is received, the processing module returns to the NR domain after the second time period.
  • the processing module is also used to count the success rate of falling back to the LTE domain.
  • the success rate refers to the ratio of the number of times the communication device successfully falls back to the LTE domain to the total number of times the communication device falls back to the LTE domain. Going to the LTE domain means that the communication device receives a call within the second time period after falling back to the LTE domain; the processing module is also used to determine whether to fall back to the LTE domain within a certain period of time according to the success rate.
  • the processing module does not fall back to the LTE domain within a certain period of time.
  • the processing module when the processing module does not fall back to the LTE domain within a certain period of time, if the transceiver module receives a paging message and does not receive a message from The INVITE message of the network or the leakage reminder message, and the leakage reminder message is received within the fifth time period after receiving the paging message, then the processing module falls back to the LTE domain to receive the call; wherein, the fourth time period and the fifth time period Segments do not overlap.
  • a communication device including a processor and a transceiver, the transceiver is used to communicate with other communication devices, when the processor executes instructions, the method described in the first aspect and any of its implementations is executed implement.
  • a computer-readable storage medium includes instructions, and when the instructions are run on the above-mentioned communication device, the communication device executes the above-mentioned communication device as described in the first aspect and any implementation thereof. Methods.
  • a computer program product including instructions is provided, and when the instructions are run on the aforementioned communication device, the communication device is made to execute the method described in the first aspect and any implementation manner thereof.
  • a chip system in a sixth aspect, includes a processor, configured to support a communication device to implement the functions involved in the first aspect above.
  • the device further includes an interface circuit, which can be used to receive signals from other devices (such as a memory) or send signals to other devices (such as a communication interface).
  • the chip system may include a chip, and may also include other discrete devices.
  • FIG. 1 is a schematic structural diagram of a wireless communication system provided by an embodiment of the present application.
  • FIG. 2 is a schematic structural diagram of a terminal device provided in an embodiment of the present application.
  • FIG. 3 is a schematic flow diagram of a terminal device in SA mode being called according to an embodiment of the present application
  • FIG. 4 is a schematic flow diagram of another terminal device in SA mode being called according to the embodiment of the present application.
  • FIG. 5 is a schematic flow diagram of a terminal device in SA mode provided by an embodiment of the present application that the called party cannot be connected;
  • FIG. 6 is a schematic flow diagram of another terminal device in SA mode provided by the embodiment of the present application that the called party cannot be connected;
  • FIG. 7 is a schematic flowchart of a call receiving method provided in an embodiment of the present application.
  • FIG. 8 is a schematic diagram of an interface change in which a terminal device falls back from the NR domain to the LTE domain according to an embodiment of the present application;
  • FIG. 9 is a schematic flowchart of another call receiving method provided in the embodiment of the present application.
  • FIG. 10 is a schematic flowchart of another call receiving method provided in the embodiment of the present application.
  • FIG. 11 is a schematic flowchart of another call receiving method provided in the embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a chip system provided by an embodiment of the present application.
  • Words such as “exemplary” or “for example” involved in the embodiments of the present application are used to represent examples, illustrations or descriptions. Any embodiment or design described herein as “exemplary” or “for example” is not to be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as “exemplary” or “such as” is intended to present related concepts in a concrete manner.
  • NSA refers to the fourth generation (4th generation, 4G) communication (also known as long term evolution (long term evolution, LTE)) and the fourth generation 5th generation (5th generation, 5G) communication (also known as new radio (NR, NR)) joint networking
  • SA refers to 5G independent networking.
  • There is no independent 5G core network in NSA but a dual connection method is adopted, that is, 5G access network equipment and 4G access network equipment coexist on the wireless side, and 5G and 4G share the 4G core network on the core network side.
  • the 5G core network is independent from the 4G core network, and the 4G access network equipment and 5G access network equipment are also independent.
  • the embodiment of the present application takes SA as an example, but it is not intended to be limited thereto.
  • IP multimedia subsystem IP multimedia subsystem
  • IMS Internet protocol
  • IP multimedia subsystem IP multimedia subsystem
  • SIP session initialization protocol
  • LTE or NR long-term evolution voice bearer
  • VoLTE new air interface voice bearer
  • the wireless communication system 100 includes a first terminal device 101, a second terminal device 102, a core network 105, and an IMS 106, providing the first terminal device 101 with a first access to a 5G network
  • the network device 103, and the second access network device 104 that provides the 4G network and the 5G network for the second terminal device 102.
  • the first terminal device 101 may be a calling terminal device
  • the second terminal device 102 may be a called terminal device.
  • devices other than terminal devices such as the first terminal device 101 and the second terminal device 102
  • NW the network (network, NW).
  • the IMS 106 may include a proxy-call session control function (proxy-call session control function, P-CSCF) entity 1061, an inquiry call session control function (interrogating-call session control function, I-CSCF) entity 1062, a service call session control function ( serving-call session control function (S-CSCF) entity 1063 and home subscriber server (home subscriber server, HSS) 1064.
  • proxy-call session control function proxy-call session control function
  • I-CSCF inquiry call session control function
  • I-CSCF inquiry call session control function
  • S-CSCF serving-call session control function
  • HSS home subscriber server
  • the P-CSCF entity 1061 is the first connection point from the access network to the IMS 106, and all session messages initiated from the terminal equipment supporting IMS and session messages terminated at the terminal equipment supporting the IMS must be forwarded through the P-CSCF entity 1061.
  • the P-CSCF entity 1061 may be configured to forward the IMS registration request from the terminal device to the S-CSCF entity 1063, and forward the registration response information to the terminal device.
  • the I-CSCF entity 1062 may be connected to the S-CSCF entity 1063 and the P-CSCF entity 1061, and is used for providing an entrance to the home network for the terminal equipment.
  • the P-CSCF entity 1061 can forward the IMS registration request from the terminal device to the I-CSCF entity 1062, and the I-CSCF entity 1062 can query the HSS 1064 in the IMS 106, and select an S-CSCF for the terminal device Entity 1063.
  • the call message to the IMS network is first routed to the I-CSCF entity 1062, and the I-CSCF entity 1062 can query the address of the S-CSCF entity 1063 registered by the user through the HSS 1064 in the IMS 106 for the terminal equipment information before routing the message to the S-CSCF entity 1063.
  • the S-CSCF entity 1063 is the control core of the IMS 106, providing functions such as session control and registration for terminal equipment.
  • the S-CSCF entity 1063 is used to receive the IMS registration request forwarded by the P-CSCF entity 1061, and cooperate with the HSS 1064 to authenticate the terminal equipment.
  • the S-CSCF entity 1063 obtains the subscription information of the terminal device from the HSS 1064 after determining that the authentication is passed.
  • the S-CSCF entity 1063 is also used to connect to each application server, and the S-CSCF entity 1063 is also used to trigger the application server to perform an operation, and route the request of the terminal device to the corresponding application server.
  • HSS 1064 is used to store all data related to users and services, such as user identity, subscription information, access information, etc.
  • the wireless communication system 100 shown in FIG. 1 only includes two terminal devices and two access network devices, the wireless communication system 100 may include fewer and/or more terminal devices, and may also include more network access equipment.
  • the wireless communication system 100 may also include an access network device that provides a 2G/3G/4G network for the first terminal device 101, and the wireless communication system 100 may also include an access network device that provides a 2G/3G network for the second terminal device 102. equipment.
  • the second terminal device 102 can be switched on, restarted, exiting the flight mode, hot-swapping a card, public land mobile network (public land mobile network, PLMN) change, tracking area update (tracking area update) , TAU), IMS registration failure and other events occur, generate an IMS registration request. Then, the second terminal device 102 may send the IMS registration request to the P-CSCF entity 1061 in the IMS 106 through the second access network device 102 and the core network 105. The second terminal device 102 may also receive a registration response message from the IMS 106 through the second access network device 102 and the core network 105. For example, an IMS registration request may be an initial registration request.
  • the initial registration request may include user information, terminal capability information, and the like.
  • the registration response message may be a session initiation protocol (session initialization protocol, SIP) 401 message.
  • the 401 message may include authentication information, and is used to require the second terminal device 102 to perform authentication.
  • the IMS registration request may be a challenging (challenging) registration request.
  • the challenge registration request may include authentication information.
  • the registration response message may be a SIP 200OK message, which is used to indicate that the IMS registration is successful.
  • the second terminal device 102 can implement the voice service through the IMS.
  • the second terminal device 102 can call other terminal devices (such as the first terminal device 101 ) by dialing the mobile phone number of the other terminal device, or answer calls from other terminal devices (such as the first terminal device 101 ).
  • the terminal device involved in this embodiment of the present application may be a device with a wireless transceiver function, and the terminal device may be mobile or fixed.
  • Terminal devices can be deployed on land (such as indoors or outdoors, handheld or vehicle-mounted, etc.), can also be deployed on water (such as ships, etc.), and can also be deployed in the air (such as aircraft, balloons and satellites, etc.).
  • the terminal equipment may be user equipment (user equipment, UE), access terminal, terminal unit, subscriber unit (subscriber unit), Terminal station, mobile station (mobile station, MS), mobile station, remote station, remote terminal, mobile device, wireless communication device, terminal agent or terminal device, etc.
  • the terminal device can be a mobile phone, a tablet computer, a laptop computer, a smart bracelet, a smart watch, a headset, a smart speaker, a virtual reality (virtual reality, VR) device, an augmented reality (augmented reality, AR) device, an industrial control (industrial Wireless terminals in control, wireless terminals in self driving, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety Terminals, wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • VR virtual reality
  • AR augmented reality
  • industrial control industrial Wireless terminals in control, wireless terminals in self driving, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety Terminals, wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • the embodiment of the present application does not limit the specific type and structure of the terminal device.
  • FIG. 2 shows a possible structure of the terminal device.
  • the terminal device 200 may include a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (universal serial bus, USB) interface 230, a power management module 240, a battery 241, a wireless charging coil 242, an antenna 1, an antenna 2.
  • Mobile communication module 250 wireless communication module 260, audio module 270, speaker 270A, receiver 270B, microphone 270C, earphone jack 270D, sensor module 280, button 290, motor 291, indicator 292, camera 293, display screen 294 and A subscriber identification module (subscriber identification module, SIM) card interface 295 and the like.
  • SIM subscriber identification module
  • the sensor module 280 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.
  • the structure shown in the embodiment of the present application does not constitute a specific limitation on the terminal device 200 .
  • the terminal device 200 may include more or fewer components than shown in the figure, or combine certain components, or separate certain components, or arrange different components.
  • the illustrated components can be realized in hardware, software or a combination of software and hardware.
  • the processor 210 may include one or more processing units, for example: the processor 210 may include a central processing unit (central processing unit, CPU), an application processor (application processor, AP), a modem processor, a graphics processor ( graphics processing unit (GPU), image signal processor (image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor and neural network processor ( neural-network processing unit, NPU), etc. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.
  • the processor 210 may be an application processor AP.
  • the above-mentioned processor 210 may be integrated in a system on chip (system on chip, SoC).
  • the above processor 210 may be integrated in an integrated circuit (integrated circuit, IC) chip.
  • the processor 210 may include an analog front end (analog front end, AFE) and a micro-controller unit (MCU) in an IC chip.
  • the controller may be the nerve center and command center of the terminal device 200 .
  • the controller can generate an operation control signal according to the instruction opcode and timing signal, and complete the control of fetching and executing the instruction.
  • a memory may also be provided in the processor 210 for storing instructions and data.
  • the memory in processor 210 is a cache memory.
  • the memory may hold instructions or data that the processor 210 has just used or recycled. If the processor 210 needs to use the instruction or data again, it can be called directly from the memory. Repeated access is avoided, and the waiting time of the processor 210 is reduced, thereby improving the efficiency of the system.
  • processor 210 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 transmitter (universal asynchronous receiver/transmitter, UART) interface, mobile industry processor interface (mobile industry processor interface, MIPI), general-purpose input and output (general-purpose input/output, GPIO) interface, subscriber identity module (subscriber identity module, SIM) interface and / or USB interface etc.
  • I2C integrated circuit
  • I2S integrated circuit built-in audio
  • PCM pulse code modulation
  • PCM pulse code modulation
  • UART universal asynchronous transmitter
  • MIPI mobile industry processor interface
  • GPIO general-purpose input and output
  • subscriber identity module subscriber identity module
  • SIM subscriber identity module
  • the interface connection relationship between the modules shown in the embodiment of the present application is only a schematic illustration, and does not constitute a structural limitation of the terminal device 200 .
  • the terminal device 200 may also adopt different interface connection manners in the foregoing implementation manners, or a combination of multiple interface connection manners.
  • the power management module 240 is configured to receive charging input from the charger.
  • the charger may be a wireless charger (such as a wireless charging base of the terminal device 200 or other devices capable of wirelessly charging the terminal device 200 ), or a wired charger.
  • the power management module 240 may receive a charging input from a wired charger through the USB interface 230 .
  • the power management module 240 may receive wireless charging input through the wireless charging coil 242 of the electronic device.
  • the power management module 240 can also supply power for electronic equipment while charging the battery 241 .
  • the power management module 240 receives the input of the battery 241 to supply power for the processor 210 , the internal memory 221 , the external memory interface 220 , the display screen 294 , the camera 293 and the wireless communication module 260 .
  • the power management module 240 can also be used to monitor parameters such as the battery capacity of the battery 241 , the number of battery cycles, and the state of health of the battery (leakage, impedance). In some other implementation manners, the power management module 240 may also be disposed in the processor 210 .
  • the wireless communication function of the terminal device 200 may be implemented by the antenna 1, the antenna 2, the mobile communication module 250, the wireless communication module 260, a modem processor, a baseband processor, and the like.
  • Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals.
  • Each antenna in the terminal device 200 can be used to cover single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization of the antennas.
  • Antenna 1 can be multiplexed as a diversity antenna of a wireless local area network.
  • the antenna may be used in conjunction with a tuning switch.
  • the mobile communication module 250 can provide wireless communication solutions including 2G/3G/4G/5G applied on the terminal device 200 .
  • the wireless communication module 260 can provide wireless local area networks (wireless local area networks, WLAN) (such as wireless fidelity (Wireless fidelity, Wi-Fi) network), bluetooth (bluetooth, BT), global navigation satellite, etc. Wireless communication solutions such as global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared technology (IR).
  • GNSS global navigation satellite system
  • FM frequency modulation
  • NFC near field communication
  • IR infrared technology
  • the antenna 1 of the terminal device 200 is coupled to the mobile communication module 250, and the antenna 2 is coupled to the wireless communication module 260, so that the terminal device 200 can communicate with the network and other devices through wireless communication technology.
  • the terminal device 200 implements a display function through a GPU, a display screen 294, an application processor, and the like.
  • the GPU is a microprocessor for image processing, and is connected to the display screen 294 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering.
  • Processor 210 may include one or more GPUs that execute program instructions to generate or alter display information.
  • the display screen 294 is used to display images, videos and the like.
  • Display 294 includes a display panel.
  • the terminal device 200 may include 1 or N display screens 294, where N is a positive integer greater than 1.
  • the terminal device 200 can realize the shooting function through the ISP, the camera 293 , the video codec, the GPU, the display screen 294 , and the application processor.
  • the ISP is used for processing the data fed back by the camera 293 .
  • the ISP may be located in the camera 293 .
  • Camera 293 is used to capture still images or video.
  • the terminal device 200 may include 1 or N cameras 293, where N is a positive integer greater than 1.
  • the external memory interface 220 may be used to connect an external memory card, such as a micro SanDisk (Micro SD) card, so as to expand the storage capacity of the terminal device 200.
  • the external memory card communicates with the processor 210 through the external memory interface 220 to implement a data storage function. Such as saving music, video and other files in the external memory card.
  • the internal memory 221 may be used to store computer-executable program codes including instructions.
  • the processor 210 executes various functional applications and data processing of the terminal device 200 by executing instructions stored in the internal memory 221 .
  • the internal memory 221 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (universal flash storage, UFS) and the like.
  • the terminal device 200 may implement an audio function through an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, an earphone interface 270D, an application processor, and the like. Such as music playback, recording, etc.
  • the audio module 270 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signal.
  • the audio module 270 can be set in the processor 210 , or some functional modules of the audio module 270 can be set in the processor 210 .
  • Speaker 270A also referred to as a "horn” is used to convert audio electrical signals into sound signals.
  • Receiver 270B also called “earpiece”, is used to convert audio electrical signals into audio signals.
  • the microphone 270C also called “microphone” or “microphone” is used to convert sound signals into electrical signals.
  • the terminal device 200 may be provided with at least one microphone 270C.
  • the earphone interface 270D is used for connecting wired earphones.
  • the earphone interface 270D can be a USB interface 230, or a 3.5mm open mobile terminal platform (OMTP) standard interface, or a cellular telecommunications industry association of the USA (CTIA) standard interface.
  • OMTP open mobile terminal platform
  • the buttons 290 include a power button, a volume button, and the like.
  • the key 290 may be a mechanical key. It can also be a touch button.
  • the terminal device 200 may receive key input and generate key signal input related to user settings and function control of the terminal device 200 .
  • the motor 291 can generate a vibrating reminder.
  • the motor 291 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback.
  • the indicator 292 can be an indicator light, and can be used to indicate charging status, power change, and can also be used to indicate messages, missed calls, notifications, and the like.
  • the SIM card interface 295 is used for connecting a SIM card.
  • the SIM card can be connected and separated from the terminal device 200 by inserting it into the SIM card interface 295 or pulling it out from the SIM card interface 295 .
  • the terminal device 200 may support 1 or N SIM card interfaces, where N is a positive integer greater than 1.
  • SIM card interface 195 can support receiving SIN (Nano SIM) card, Micro SIM (Micro SIM) card, SIM card etc.
  • the terminal device 200 adopts an embedded SIM (eSIM) card, and the eSIM card can be embedded in the terminal device 200 and cannot be separated from the terminal device 200.
  • eSIM embedded SIM
  • FIG. 3 shows a normal flow for a terminal device (that is, the second terminal device mentioned above) to fall back to the LTE domain to receive a called party, including steps S101-S113, wherein steps S102-S106 are optional.
  • the service centralization and continuity application server receives the IMS call request message from the calling party (that is, the first terminal device mentioned above), and sends the message to the 5G core network (attached to this application) In the figure, it is represented by a core network) to send an INVITE message.
  • the SCC AS is used to implement terminal equipment access to the IMS domain to complete IMS session establishment and control.
  • the INVITE message is used to request to call the terminal equipment.
  • the invitation (INVITE) message includes from (From) label, to (To) label, call identification (Call-ID) label. From (From) tag is used to indicate the source address of the call. To (To) tag is used to indicate the destination address of the call.
  • a call identification (Call-ID) tag serves as a globally unique identifier for a call.
  • the 5G core network sends a paging (paging) message to the 5G access network device.
  • the paging message is used to establish a session between the 5G core network and the 5G access network equipment.
  • the 5G access network device sends a mobile terminal paging (MT paging) message to the terminal device.
  • MT paging mobile terminal paging
  • a mobile terminal paging message is used to request a call to a terminal device.
  • the paging message of the mobile terminal includes the identifier of the called terminal device (such as a temporary mobile subscriber identity (TMSI)).
  • TMSI temporary mobile subscriber identity
  • the terminal device establishes an RRC connection with the 5G access network device.
  • the terminal device executes a service request procedure (service request procedure) through the 5G access network device and the 5G core network.
  • the purpose of the service request process is to change the 5G system mobility management (5GMM) of the terminal device from the 5GMM idle state (5GMM-IDLE) to the 5GMM connected state (5GMM-CONNECTED), and to establish or restore the 5G quality identification
  • a bearer with a (5G quality identity, 5QI) of 5, and a bearer with a 5QI of 5 refers to a non-guaranteed bit rate (guaranteed bit rate, Non-GBR) bearer used to transmit IMS signaling.
  • the 5G access network device and the terminal device perform an RRC reconfiguration (reconfiguration) process to establish a data resource bearer (data resource bearer, DRB) of the IMS.
  • RRC reconfiguration reconfiguration
  • the RRC reconfiguration procedure is triggered by a service request procedure.
  • steps S102-S106 are optional, and if the 5GMM of the terminal device is already in the 5GMM-CONNECTED state, it is not necessary to perform steps S102-S106.
  • the terminal device can determine that the network side will send an incoming call or short message, and receive IMS data through the DRB.
  • the 5G core network sends an INVITE message to the terminal device through the 5G access network device.
  • the terminal device sends a 100 Trying (100 Trying) message to the SCC AS through the 5G access network device and the 5G core network.
  • the 100 Trying (100Trying) message is used to indicate that the INVITE message has been received.
  • the 100 try (100Trying) message includes the same from (From) label, to (To) label, and call identification (Call-ID) label as in the invite (INVITE) message so that the SCC AS can send the 100 try (100Trying) message with the The INVITE message is associated.
  • the terminal device sends a 183 session progress (183 session progress) message to the SCC AS through the 5G access network device and the 5G core network.
  • the 183 session progress (183 session progress) message is used to indicate the progress information of establishing a session.
  • the message includes a reason phrase (reason-phrase), header field and message body.
  • the reason phrase is used to indicate the reason, and the header field or message body can be used to indicate More information on the progress of establishing a session.
  • the SCC AS sends the indication information of falling back to the LTE domain to the terminal equipment through the 5G core network and the 5G access network equipment, or sends the indication information of establishing or modifying the dedicated voice bearer.
  • the indication information of falling back to the LTE domain is for a scenario where the terminal equipment does not support VoNR.
  • the terminal device If the terminal device receives the indication information of falling back to the LTE domain, the terminal device falls back to the LTE domain, and establishes a dedicated voice bearer in the LTE domain.
  • the terminal device can fall back to the LTE domain through the TAU process with the 4G access network device, and the terminal device also sends a 183 session progress (183 session progress) message to the SCC AS through the 4G access network device and the 4G core network. (183session progress) message is described above.
  • the terminal device establishes a dedicated voice bearer with the 4G core network through the 4G access network device.
  • the terminal device sends a 180 Ringing (180 Ringing) message to the SCC AS through the 4G access network device and the 4G core network.
  • the 180 ringing (180Ringing) message is used to indicate that the terminal device is ringing. If the user chooses to answer, the call is successful, and the voice data of the call will be transmitted on the dedicated voice bearer.
  • the terminal device communicates with the opposite end (calling party).
  • the terminal device communicates with the opposite end (caller) through 4G access network equipment, 4G core network and SCC AS.
  • FIG. 4 shows a normal flow of a terminal device in SA mode (that is, the second terminal device mentioned above) receiving a call in the LTE domain, including steps S201-S213, wherein steps S201-S209 refer to steps S101-S109.
  • the SCC AS sends instruction information for establishing or modifying a dedicated voice bearer to the terminal device through the 5G core network and the 5G access network device.
  • establishing or modifying the voice-specific bearer indication information is aimed at a scenario in which the terminal device supports VoNR.
  • the terminal device If the terminal device receives instruction information for establishing or modifying a dedicated voice bearer, the terminal device establishes or modifies a dedicated voice bearer in the NR domain.
  • the terminal device also sends a 183 session progress (183 session progress) message to the SCC AS through the 5G access network device and the 5G core network.
  • 183 session progress (183 session progress) message see the previous description.
  • the terminal device establishes or modifies the dedicated voice bearer through the 5G access network device and the 5G core network.
  • the terminal device sends a 180 ringing (180Ringing) message to the SCC AS through the 5G access network device and the 5G core network.
  • 180Ringing 180 ringing
  • the 180 ringing (180Ringing) message is used to indicate that the terminal device is ringing. If the user chooses to answer, the call is successful, and the voice data of the call will be transmitted on the dedicated voice bearer.
  • the terminal device communicates with the opposite end (calling party).
  • the terminal device communicates with the opposite end (calling party) through the 5G access network equipment, 5G core network and SCC AS.
  • a possible scenario in which the terminal device in SA mode cannot be connected to the called party is: due to network failure and other reasons, although steps S101-S106 (or S201-S206) in Figure 3 are executed successfully, but the steps In S107 (or S207), the invitation (INVITE) message sent by the SCC AS cannot be received by the 5G access network equipment. After the SCC AS retransmits the invitation (INVITE) message multiple times, it will perform circuit switching retry (CS Retry). ) to page terminal devices in the circuit switching (CS) domain.
  • CS Retry circuit switching retry
  • steps S101-S108 in Figure 3 are executed successfully, but when the terminal device sends the 183 session progress (183 session progress) message in step S109 (or S209), it does not receive the instruction information to fall back to the LTE domain, or establish or modify the dedicated voice bearer
  • the terminal device will retransmit the 183 session progress (183 session progress) message several times until the timeout occurs, and the terminal device will send a 580 resource reservation failure (precondition failure) message, indicating paging failure.
  • the reason for the paging failure in this scenario is that the evolved packet system fallback (EPS FB) process is completely controlled by the network side. Even if the EPS FB process is abnormal due to a network failure, the terminal device side can only wait passively for instructions from the network side.
  • EPS FB evolved packet system fallback
  • the embodiment of the present application provides a method for receiving a call to solve the problem that the called party cannot be connected as shown in FIG. 5. As shown in FIG. The steps S101-S106 will not be repeated here.
  • the INVITE message sent by the SCC AS cannot be received by the 5G access network device, and the SCC AS retransmits the INVITE message multiple times.
  • the terminal device After the RRC reconfiguration process triggered by the service request procedure (service request procedure) is completed, the terminal device starts the timer T1. If the terminal device has not received IMS data such as an INVITE message after the timer T1 expires, the terminal device actively falls back to the LTE domain to receive the call, and starts the timer T2.
  • timer T1 and timer T2 can be determined according to the retransmission behavior of the network side, timer T1 is less than the total time of network retransmission, and timer T2 is greater than the total time of network retransmission. For example, the timer T1 is 4 seconds, and the timer T2 is 20 seconds.
  • the terminal device can determine whether the service request procedure is completed by receiving the service accept message. When receiving the service accept message, it can determine that the service request procedure is completed. .
  • the terminal device receives the RRC reconfiguration message from the network side, and feeds back the RRC reconfiguration complete message, indicating that the RRC reconfiguration process is completed. And the terminal device can determine that the network side will send an incoming call or a short message through the establishment of the DRB corresponding to the IMS.
  • the terminal device can determine whether there is an incoming call or a short message by detecting whether there is IMS data such as an INVITE message in the DRB corresponding to the IMS bearer (packet data unit (packet data unit, PDU) session identifier).
  • IMS data such as an INVITE message in the DRB corresponding to the IMS bearer (packet data unit (packet data unit, PDU) session identifier).
  • the terminal device can actively fall back to the LTE domain by initiating a TAU process with the 4G access network device, and the terminal device can start the timer T2 when initiating the TAU process.
  • the terminal device when the terminal device falls back from the NR domain to the LTE domain, the network identifier changes from 5G to 4G.
  • the terminal device receiving a call on the LTE domain means that the terminal device receives an invitation (INVITE) message or a CS fallback (CS fallback, CSFB) indication message on the LTE domain (via a 4G access network device).
  • INVITE invitation
  • CS fallback CS fallback, CSFB
  • the fallback is successful, and the terminal device actively returns to the NR domain after the call is hung up. If the terminal device does not receive a call before the timer T2 expires, the fallback fails, and the terminal device actively returns to the NR domain after the timer T2 expires.
  • the SCC AS After the SCC AS retransmits the INVITE message multiple times, it will execute the circuit CS Retry to page the terminal device in the CS domain.
  • the SCC AS passes the 4G core network (represented by the core network in the figure) and the 4G access network device and the terminal device. The call is established so that the end device receives the call.
  • the terminal device actively returns to the NR domain through reselection or handover or redirection procedures. As shown in Figure 8, when the terminal device returns to the NR domain from the LTE domain, the network identifier changes from 4G to 5G.
  • the terminal device counts the success rate of falling back to the LTE domain. If the success rate is less than the success rate threshold, the terminal device does not actively fall back to the LTE domain within a certain period of time (that is, exits the active fallback mode).
  • the success rate of falling back to the LTE domain refers to the ratio of the number of times the terminal device successfully falls back to the LTE domain to the total number of times the terminal device falls back to the LTE domain.
  • the successful fallback of the terminal device to the LTE domain refers to the second time after the terminal device falls back to the LTE domain A call is received within the segment.
  • the terminal device no longer actively falls back to the LTE domain within a certain period of time means: after the RRC reconfiguration process triggered by the service request procedure (service request procedure) is completed, the terminal device starts the timer T1, If the terminal device has not received IMS data such as an INVITE message after the timer T1 expires, the terminal device will not actively fall back to the LTE domain. That is to say, if the success rate of falling back to the LTE domain and receiving calls in the LTE domain is very low, the terminal device does not actively fall back to the LTE domain within a certain period of time.
  • the terminal device may execute step S308 when the condition of step S308 is satisfied, that is, if the success rate is greater than or equal to the success rate threshold, the terminal device may execute step S308 in the service After the RRC reconfiguration process triggered by the service request procedure is completed, the terminal device starts the timer T1. If the terminal device has not received IMS data such as an INVITE message after the timer T1 expires, the terminal device actively falls back to the LTE domain to receive the next call, and starts the timer T2.
  • IMS data such as an INVITE message
  • timer T5 After the terminal device exits the fallback mode, if the mobile terminal paging (MT paging) message is received again, timer T5, timer T6 and timer T7 are started, and if the INVITE message is not received before the timer T5 expires Or the IMS data such as the electric leakage reminder message, but after the timer T6 expires and the timer T7 receives the electric leakage reminder message before the timer T7 expires, the terminal device actively falls back to the LTE domain to receive the call.
  • the timer T6 is optional, that is, the terminal device may actively fall back to the LTE domain to receive the call if the leakage reminder message is received before the timer T7 expires.
  • the duration of the timer T7 is longer than the duration of the timer T6, and the duration of the timer T6 is longer than the duration of the timer T5.
  • the duration of the timer T5, the timer T6 and the timer T7 is determined according to the leakage warning behavior of the network side.
  • This step enables the terminal device to determine the missed call by analyzing the leakage reminder text message (the short message including the leakage reminder keyword), so it can actively fall back to the LTE domain through the TAU process to receive the call. For how to fall back to the LTE domain and how to determine that IMS data is received, refer to step S308, which will not be repeated here.
  • the embodiment of the present application provides another method for receiving a call to solve the problem that the called party cannot be connected as shown in FIG. 6 .
  • the method includes steps S401-S414. Steps S101-S108 described above will not be repeated here.
  • the terminal device sends a 183 session progress (183session progress) message to the 5G access network device, starts the timer T3, and monitors the indication information of falling back to the LTE domain (ie, the fallback indication information), and establishes or modifies the voice exclusive Bearer indication information (that is, bearer indication information).
  • 183 session progress 183session progress
  • the 5G access network device starts the timer T3, and monitors the indication information of falling back to the LTE domain (ie, the fallback indication information), and establishes or modifies the voice exclusive Bearer indication information (that is, bearer indication information).
  • the duration of the timer T3 is less than the total retransmission time of 183.
  • the terminal device If the terminal device does not receive the indication information of falling back to the LTE domain and the indication information of establishing or modifying the dedicated voice bearer before the timer T3 expires, the terminal device actively falls back to the LTE domain to receive the call.
  • the terminal device can actively fall back to the LTE domain through the TAU process with the 4G access network device.
  • the terminal device sends a 183 session progress (183 session progress) message to the 4G core network through the 4G access network device, and starts a timer T4.
  • the duration of timer T4 can be customized.
  • the terminal device and the 4G core network establish or modify a dedicated voice bearer in the LTE domain.
  • the terminal device communicates with the opposite end (caller) through 4G access network equipment, 4G core network and SCC AS.
  • the fallback is successful, and the terminal device actively returns to the NR domain after the call is hung up. If the terminal device does not receive a call before the timer T4 expires, the fallback fails, and the terminal device actively returns to the NR domain after the timer T4 expires.
  • the terminal device can start the timer T8 after the timer T4 expires, and then actively return to the NR domain when the timer T8 expires, so as to avoid missing calls that may be redialed by the calling party before the timer T8 expires.
  • the terminal device may start the timer T8 after the timer T4 expires.
  • the time length of timer T8 can be determined by the number of times that the above-mentioned situation occurs, the more the number of times that the above-mentioned situation occurs, the longer the time length of the timer T8, the less the number of times that the above-mentioned situation occurs, the shorter the time length of the timer T8, In particular, the duration of the timer T8 increases in proportion to the number of occurrences of the above situations.
  • the terminal device sends a 183 session progress (183 session progress) message on the LTE domain, but fails to receive the indication information instructing the terminal device to establish a dedicated voice bearer in the LTE domain on the LTE domain, Then the terminal device can return to NR in advance (without waiting for the timer T8 to expire).
  • 183 session progress 183 session progress
  • the terminal device counts the success rate of falling back to the LTE domain. If the success rate is less than the success rate threshold, the terminal device does not actively fall back to the LTE domain within a certain period of time (that is, exits the active fallback mode).
  • step S310 Regarding the success rate of falling back to the LTE domain, reference may be made to step S310, which will not be repeated here.
  • the terminal device can perform step S410 when the condition of step S410 is satisfied, that is, if the success rate is greater than or equal to the success rate threshold, the terminal device sends a 5G
  • the access network device sends a 183 session progress (183 session progress) message to start the timer T3. If the terminal device does not receive the instruction to fall back to the LTE domain before the timer T3 expires, and establish or modify the dedicated voice bearer Instruction information, the terminal device actively falls back to the LTE domain to receive the next call.
  • the embodiment of the present application provides another method for receiving a call, as shown in FIG. 10 , the method includes:
  • the terminal device receives a call message from the network in the NR domain.
  • the end device is in SA mode.
  • the call message is used to request to call the terminal device.
  • the call message can be the mobile terminal paging (MT paging) message mentioned above.
  • the call message can be the above-mentioned message.
  • the INVITE message For details, see related descriptions in steps S101-S106.
  • the terminal device If the terminal device does not receive expected information from the network within the first time period after the preset call flow, the terminal device falls back to the LTE domain to receive the call after the first time period.
  • the preset call procedure is an RRC reconfiguration procedure triggered by a service request procedure
  • the expected information is IMS data such as an INVITE message.
  • the first time period refers to a time period from the start of the timer T1 to the timeout of the timer T1.
  • the preset call flow is to send a 183 session progress (183 session progress) message
  • the expected information is bearer indication information or fallback indication information
  • the bearer indication information is used to instruct the terminal device to establish or modify the NR domain.
  • Dedicated bearer for voice the fallback indication information is used to instruct the terminal device to fall back to the LTE domain.
  • the first time period refers to the time period from the start of the timer T3 to the timeout of the timer T3.
  • the call receiving method when a terminal device in SA mode receives a call message from the network in the NR domain, when a failure occurs on the 5G network, it will cause the terminal to The device cannot receive the expected information from the network, so the terminal device actively falls back to the LTE domain after the first time period to receive the call. Since terminal devices usually wait for the network side to indicate whether to fall back to the LTE domain, when the 5G network fails, the 5G network cannot instruct the terminal device to fall back to the LTE domain. Therefore, the call receiving method provided by the embodiment of the present application can improve the calling success rate of the terminal device in SA mode by actively falling back to the LTE domain to try to receive the call in the LTE domain.
  • the call receiving method may also include:
  • the terminal device If the terminal device does not receive a call in the LTE domain within a second time period after the terminal device falls back to the LTE domain, the terminal device returns to the NR domain after the second time period.
  • Step S503 may refer to step S309, the second time period refers to the time period from the start of the timer T2 to the timeout of the timer T2.
  • step S503 may refer to step S413, and the second time period refers to a time period from the start of the timer T4 to the timeout of the timer T4.
  • the terminal device within the second time period after the terminal device falls back to the LTE domain, if the terminal device fails to receive an instruction terminal message in the LTE domain after sending a 183 session progress message (183 session progress) in the LTE domain
  • the device establishes the instruction information of the dedicated voice bearer in the LTE domain, and does not receive a call, then the terminal device returns to the NR domain after the second time period.
  • the terminal device may receive the redialed call in the LTE domain within a third time period after the second time period, and return to the NR domain after the third time period.
  • the time length of the third time period is determined by the number of times that the terminal device does not receive the expected information in the NR domain. The shorter the length of time.
  • the third time period refers to the time period from the start of the timer T8 to the timeout of the timer T8.
  • This step enables the terminal device to stay in the LTE domain for a period of time so that it will not miss receiving the redialed call from the opposite end.
  • the call cannot be received in the LTE domain after a period of time, it can return to the NR domain to receive the incoming call again.
  • the terminal device counts the success rate of falling back to the LTE domain, and determines whether to actively fall back to the LTE domain within a certain period of time according to the success rate.
  • step S310 Regarding the success rate of falling back to the LTE domain, reference may be made to step S310, which will not be repeated here.
  • the terminal device may execute step S502 when the condition of step S502 is satisfied, that is, if within the first time period after the preset call flow, the terminal device If the expected information is not received by the device, the terminal device falls back to the LTE domain after the first time period to receive the next call.
  • step S502 refers to step S310 or S414.
  • the terminal device will no longer actively fall back to the LTE domain within a certain period of time (that is, exit the active fallback mode), that is, if the success rate is less than the success rate threshold, even in the preset call process During the first time period after , the terminal device does not receive the expected information, and the terminal device will not actively fall back to the LTE domain after the first time period.
  • the terminal device does not receive the expected information, and the terminal device will not actively fall back to the LTE domain after the first time period.
  • the reason why the success rate is lower than the success rate threshold may be that the signal in the LTE domain is poor.
  • preventing the terminal device from actively falling back to the LTE domain for a certain period of time can prevent the terminal device from repeatedly redirecting between the LTE domain and the NR domain.
  • the terminal device can still actively fall back to the LTE domain to receive calls if certain conditions are met. For example, when the terminal device does not actively fall back to the LTE domain within a certain period of time, if the terminal device receives a paging message (such as a mobile terminal paging (MT paging) message), and the terminal device receives the paging message on the first IMS data such as INVITE messages and power leakage reminder messages from the network are not received within the fourth time period, and the terminal device receives the power leakage reminder message within the fifth time period after receiving the paging message, then the terminal device falls back to the LTE domain.
  • a paging message such as a mobile terminal paging (MT paging) message
  • the fourth time period does not overlap with the fifth time period.
  • This embodiment can refer to step S311, the fourth time period refers to the time period from the start of the timer T5 to the timeout of the timer T5, and the fifth time period refers to the time period from the timeout of the timer T5 to the timeout of the timer T7,
  • the fifth time period refers to a time period from when the timer T6 expires to when the timer T7 expires.
  • the terminal device can determine the missed call by analyzing the electric leakage reminder text message (the short message including the electric leakage reminder keyword), so it can actively fall back to the LTE domain to receive the redialed call.
  • the methods and/or steps implemented by the terminal device may also be implemented by components (such as chips or circuits) of the terminal device.
  • the embodiment of the present application also provides a communication device.
  • the communication device may be the terminal device in the above method embodiment, or an apparatus including the above terminal device, or a chip or a functional module in the terminal device. Thereby realizing above-mentioned various methods.
  • the communication device includes hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.
  • the embodiments of the present application may divide the communication device into functional modules according to the above method embodiments.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 12 shows a schematic structural diagram of a communication device 30 .
  • the communication device 30 includes a processing module 301 and a transceiver module 302 .
  • the communication device 30 may be the aforementioned terminal device.
  • the processing module 301 may also be referred to as a processing unit, and is configured to implement the processing function of the terminal device in the foregoing method embodiments. For example, steps S309, S310, and S311 in FIG. 7, steps S410, S413, and S414 in FIG. 9, step S502 in FIG. 10, and steps S502, S503, and S504 in FIG. 11 are executed.
  • the transceiver module 302 which may also be referred to as a transceiver unit, is configured to implement the transceiver function of the terminal device in the foregoing method embodiments. For example, steps S303-S311 in FIG. 7, steps S403-S414 in FIG. 9, steps S501-S502 in FIG. 10, and steps S501-S504 in FIG. 11 are executed.
  • the transceiver module 302 may be called a transceiver circuit, a transceiver, a transceiver or a communication interface.
  • the transceiver module 302 is configured to receive a call message from the network in the NR domain, and the call message is used to request to call the communication device; if within the first time period after the preset call flow, the transceiver module 302 If the expected information from the network is not received, the processing module 301 falls back to the LTE domain to receive the call after the first time period.
  • the preset call process is an RRC reconfiguration process between the communication device and the 5G access network equipment, and the RRC reconfiguration process is triggered by a service request process between the communication device and the 5G core network.
  • the preset call flow is that the communication device sends a 183 session progress message to the service centralization and continuity application server through the 5G access network equipment and the 5G core network, and the expected information is bearer indication information or fallback indication information
  • the bearer instruction information is used to instruct the communication device to establish or modify a dedicated voice bearer in the NR domain, and the fallback instruction information is used to instruct the communication device to fall back to the LTE domain.
  • the processing module 301 is further configured to: within a second time period after falling back to the LTE domain, if the transceiver module 302 does not receive a call in the LTE domain, return the NR call after the second time period. area.
  • the transceiver module 302 receives the redialed call in the LTE domain within a third time period after the second time period; the processing module 301 returns to the NR domain after the third time period.
  • the length of the third time period is determined by the number of times the transceiver module 302 fails to receive expected information.
  • the processing module 301 within the second time period after the processing module 301 falls back to the LTE domain, if the transceiver module 302 does not receive an instruction in the LTE domain to establish a voice message in the LTE domain after the transceiver module 302 sends 183 the session progress message If the indication information of the dedicated bearer is not received, and the call is not received, the processing module 301 returns to the NR domain after the second time period.
  • the processing module 301 is also used to count the success rate of falling back to the LTE domain.
  • the success rate refers to the ratio of the number of times the communication device successfully falls back to the LTE domain to the total number of times the communication device successfully falls back to the LTE domain. Falling back to the LTE domain means that the communication device receives a call within a second time period after falling back to the LTE domain; the processing module 301 is also used to determine whether to fall back to the LTE domain within a certain period of time according to the success rate.
  • the processing module 301 does not fall back to the LTE domain within a certain period of time.
  • the processing module 301 when the processing module 301 does not fall back to the LTE domain within a certain period of time, if the transceiver module 302 receives the paging message and does not receive the paging message within the fourth time period after receiving the paging message Receive an INVITE message or a power leakage reminder message from the network, and receive a power leakage reminder message within the fifth time period after receiving the paging message, then the processing module 301 falls back to the LTE domain to receive the call; wherein, the fourth time period is the same as The fifth time period has no overlap.
  • the embodiment of the present application also provides a communication device.
  • the communication device 40 includes a processor 401, a memory 402, and a transceiver 403.
  • the processor 401 is coupled to the memory 402 and the transceiver 403.
  • the transceiver 403 is used to support the communication device to communicate with other communication devices.
  • the processor 401 executes the computer programs or instructions in the memory 402, the methods corresponding to the terminal devices in FIG. 7 , FIG. 9 , FIG. 10 , and FIG. 11 are executed.
  • an embodiment of the present application further provides a chip system.
  • the chip system 50 includes at least one processor 501 and at least one interface circuit 502 . At least one processor 501 and at least one interface circuit 502 may be interconnected through wires.
  • the processor 501 is used to support the communication device to implement various functions or steps performed by the terminal device in the above method embodiments, and at least one interface circuit 502 can be used to receive signals from other devices (such as memory), or send signals to other communication devices (such as communication interface) to send the signal.
  • the chip system may include a chip, and may also include other discrete devices.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium includes instructions, and when the instructions are run on the above-mentioned communication device, the communication device is made to perform the various functions performed by the terminal device in the above-mentioned method embodiments Or steps, for example, execute the methods shown in FIG. 7 , FIG. 9 , FIG. 10 , and FIG. 11 .
  • the embodiment of the present application also provides a computer program product including an instruction.
  • the communication device When the instruction is run on the above-mentioned communication device, the communication device is made to perform various functions or steps performed by the terminal device in the above-mentioned method embodiment, for example, execute the functions or steps in FIG. 7, The method shown in Figure 9, Figure 10, and Figure 11.
  • the processor involved in this embodiment of the present application may be a chip.
  • it can be a field programmable gate array (field programmable gate array, FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), or a central processing unit.
  • It can also be a central processor unit (CPU), a network processor (network processor, NP), a digital signal processing circuit (digital signal processor, DSP), or a microcontroller (micro controller unit, MCU) , and can also be a programmable logic device (programmable logic device, PLD) or other integrated chips.
  • the memory involved in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (RAM), which acts as external cache memory.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM direct memory bus random access memory
  • direct rambus RAM direct rambus RAM
  • sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • modules and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.
  • the disclosed systems, devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the modules is only a logical function division. In actual implementation, there may be other division methods.
  • multiple modules or components can be combined or May be integrated into another device, or some features may be omitted, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or modules may be in electrical, mechanical or other forms.
  • the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one device, or may be distributed to multiple devices. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional module in each embodiment of the present application may be integrated into one device, or each module may physically exist separately, or two or more modules may be integrated into one device.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • a software program it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server, or data center Transmission to another website site, computer, server or data center via wired (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or may be a data storage device including one or more servers, data centers, etc. that can be integrated with the medium.
  • the available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (Solid State Disk, SSD)), etc.
  • a magnetic medium such as a floppy disk, a hard disk, or a magnetic tape
  • an optical medium such as a DVD
  • a semiconductor medium such as a solid state disk (Solid State Disk, SSD)

Landscapes

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

Abstract

本申请公开了一种呼叫接收方法和通信装置，涉及通信领域，用于提高处于SA模式的终端设备的被叫成功率。呼叫接收方法包括：终端设备在新空口NR域接收来自网络的呼叫消息，呼叫消息用于请求呼叫终端设备，终端设备处于独立组网模式；如果在预设呼叫流程后的第一时间段内，终端设备未接收到来自网络的预期信息，则终端设备在第一时间段之后回落至长期演进LTE域以接收呼叫。

Description

呼叫接收方法和通信装置
本申请要求于2021年12月15日提交国家知识产权局、申请号为202111534732.5、发明名称为“一种提高SA终端被叫成功率的方法”的中国专利申请的优先权，以及于2022年2月21日提交国家知识产权局、申请号为202210159154.X、发明名称为“呼叫接收方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信领域，尤其涉及一种呼叫接收方法和通信装置。
背景技术
在移动通信运营商逐步建设第五代(5th generation，5G)独立组网(stand alone，SA)的过程中，仍存在5G网络的SA功能不完善的问题，处于SA模式的终端设备在被呼叫时，经常出现因为5G网络故障导致终端设备无法接通呼叫的问题。
发明内容
本申请实施例提供一种呼叫接收方法和通信装置，用于提高处于SA模式的终端设备的被叫成功率。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，提供了一种呼叫接收方法，该方法包括：处于独立组网模式的终端设备在新空口(new radio，NR)域接收来自网络的呼叫消息，呼叫消息用于请求呼叫终端设备；如果在预设呼叫流程后的第一时间段内，终端设备未接收到来自网络的预期信息，则终端设备在第一时间段之后回落至长期演进(long term evolution，LTE)域以接收呼叫。
本申请实施例提供的呼叫接收方法，处于SA模式的终端设备在NR域接收来自网络的呼叫消息时，当5G网络发生故障时，会导致在预设呼叫流程后的第一时间段内，终端设备无法接收到来自网络的预期信息，所以终端设备在第一时间段之后主动回落至LTE域以接收呼叫。由于通常终端设备都是等待网络侧指示是否回落至LTE域的，当5G网络发生故障时，5G网络无法指示终端设备回落至LTE域。所以本申请实施例提供的呼叫接收方法通过主动回落至LTE域以尝试在LTE域接收呼叫，可以提高处于SA模式的终端设备的被叫成功率。
在一种可能的实施方式中，预设呼叫流程为终端设备与第五代5G接入网设备之间的无线资源控制(radio resource control，RRC)重配置流程，该RRC重配置流程由终端设备与5G核心网之间的服务请求流程触发，预期信息包括邀请(INVITE)消息。也就是说，终端设备与5G核心网之间完成服务请求流程触发的RRC重配置流程之后，终端设备预期从5G核心网接收邀请(INVITE)消息，由于网络故障等原因，终端设备无法接收邀请(INVITE)消息，则终端设备在第一时间段之后主动回落至LTE域以接收呼叫。
在一种可能的实施方式中，预设呼叫流程为终端设备通过5G接入网设备和5G核心网向服务集中和连续性应用服务器(service centralization and continuity application  server，SCC AS)发送183会话进度消息，预期信息为承载指示信息或回落指示信息，承载指示信息用于指示终端设备在NR域建立或修改语音的专有承载，回落指示信息用于指示终端设备回落至LTE域。也就是说，终端设备在通过5G接入网设备和5G核心网向服务集中和连续性应用服务器发送183会话进度消息后，终端设备预期从5G核心网接收承载指示信息或回落指示信息，由于网络故障或突发干扰导致上行发射困难等原因，终端设备无法接收承载指示信息或回落指示信息，则终端设备在第一时间段之后主动回落至LTE域以接收呼叫。
在一种可能的实施方式中，该方法还包括：在终端设备回落至LTE域后的第二时间段内，如果终端设备未在LTE域接收到呼叫，则终端设备在第二时间段之后返回NR域，以便终端设备能在LTE域接收到对端重拨的来电。
在一种可能的实施方式中，终端设备在第二时间段之后返回NR域，包括：终端设备在第二时间段之后的第三时间段内在LTE域接收重拨的呼叫；终端设备在第三时间段之后返回NR域。终端设备在LTE域延迟一段时间再返回NR域，以便在LTE域接收到对端重拨的来电。
在一种可能的实施方式中，第三时间段的时间长度由终端设备未接收到预期信息的次数来确定，该次数越多则第三时间段的时间长度越长，该次数越少则第三时间段的时间长度越短。终端设备未接收到预期信息的次数越多，表明NR域网络故障影响越大，因此在LTE域驻留接收来电的时间越长。
在一种可能的实施方式中，在终端设备回落至LTE域后的第二时间段内，如果终端设备未在LTE域接收到呼叫，则终端设备在第二时间段之后返回NR域，包括：在终端设备回落至LTE域后的第二时间段内，如果终端设备发送183会话进度消息之后，未在LTE域接收到指示终端设备在LTE域建立语音的专有承载的指示信息，并且未接收到呼叫，则终端设备在第二时间段之后返回NR域。也就是说，当终端设备无法在LTE域建立专有承载并接收呼叫，则终端设备在第二时间段之后返回NR域，以便在NR域接收呼叫。
在一种可能的实施方式中，该方法还包括：终端设备统计回落至LTE域的成功率，该成功率指终端设备成功回落至LTE域的次数与回落至LTE域的总次数之比，终端设备成功回落至LTE域指终端设备在回落至LTE域后的第二时间段内接收到呼叫；终端设备根据成功率确定在一定时间内是否回落至LTE域。也就是说，如果回落至LTE域并在LTE域接收呼叫的成功率很低，则终端设备在一定时间内不主动回落至LTE域；如果回落至LTE域并在LTE域接收呼叫的成功率很高，则终端设备在一定时间内可以主动回落至LTE域并在LTE域接收呼叫。
在一种可能的实施方式中，终端设备根据成功率确定在一定时间内是否回落至LTE域，包括：如果成功率小于成功率阈值，则终端设备在一定时间内不回落至LTE域。也就是说，如果回落至LTE域并在LTE域接收呼叫的成功率很低，则终端设备在一定时间内不主动回落至LTE域。
在一种可能的实施方式中，该方法还包括：当终端设备在一定时间内不回落至LTE域时，如果终端设备接收到寻呼消息，并且终端设备在接收到寻呼消息之后的第四时间段内未接收到来自网络的INVITE消息或漏电提醒短信，并且终端设备在接收到寻 呼消息之后的第五时间段内接收到漏电提醒短信，则终端设备回落至LTE域以接收呼叫；其中，第四时间段与第五时间段无重叠。终端设备通过分析漏电提醒短信(包括漏电提醒关键字的短信)可以确定漏接呼叫，主动回落至LTE域以接收呼叫。
第二方面，提供了一种通信装置，该通信装置处于独立组网模式，该通信装置包括收发模块和处理模块。其中，收发模块用于在NR域接收来自网络的呼叫消息，呼叫消息用于请求呼叫该通信装置；如果在预设呼叫流程后的第一时间段内，收发模块未接收到来自网络的预期信息，则处理模块在第一时间段之后回落至LTE域以接收呼叫。
在一种可能的实施方式中，预设呼叫流程为终端设备与第五代5G接入网设备之间的RRC重配置流程，RRC重配置流程由终端设备与5G核心网之间的服务请求流程触发，预期信息包括邀请(INVITE)消息。
在一种可能的实施方式中，预设呼叫流程为通信装置通过5G接入网设备和5G核心网向服务集中和连续性应用服务器发送183会话进度消息，预期信息为承载指示信息或回落指示信息，承载指示信息用于指示通信装置在NR域建立或修改语音的专有承载，回落指示信息用于指示通信装置回落至LTE域。
在一种可能的实施方式中，处理模块还用于：在回落至LTE域后的第二时间段内，如果收发模块未在LTE域接收到呼叫，则在第二时间段之后返回NR域。
在一种可能的实施方式中，收发模块在第二时间段之后的第三时间段内在LTE域接收重拨的呼叫；处理模块在第三时间段之后返回NR域。
在一种可能的实施方式中，第三时间段的时间长度由收发模块未接收到预期信息的次数来确定。
在一种可能的实施方式中，在处理模块回落至LTE域后的第二时间段内，如果收发模块发送183会话进度消息之后，未在LTE域接收到指示通信装置在LTE域建立语音的专有承载的指示信息，并且未接收到呼叫，则处理模块在第二时间段之后返回NR域。
在一种可能的实施方式中，处理模块还用于统计回落至LTE域的成功率，成功率指通信装置成功回落至LTE域的次数与回落至LTE域的总次数之比，通信装置成功回落至LTE域指通信装置在回落至LTE域后的第二时间段内接收到呼叫；处理模块还用于根据成功率确定在一定时间内是否回落至LTE域。
在一种可能的实施方式中，如果成功率小于成功率阈值，则处理模块在一定时间内不回落至LTE域。
在一种可能的实施方式中，当处理模块在一定时间内不回落至LTE域时，如果收发模块接收到寻呼消息，并且在接收到寻呼消息之后的第四时间段内未接收到来自网络的INVITE消息或漏电提醒短信，并且在接收到寻呼消息之后的第五时间段内接收到漏电提醒短信，则处理模块回落至LTE域以接收呼叫；其中，第四时间段与第五时间段无重叠。
第三方面，提供了一种通信装置，包括处理器和收发器，收发器用于与其他通信装置进行通信，当处理器执行指令时，如第一方面及其任一实施方式所述的方法被执行。
第四方面，提供了一种计算机可读存储介质，该计算机可读存储介质包括指令，当指令在上述通信装置上运行时，使得该通信装置执行如第一方面及其任一实施方式所述的方法。
第五方面，提供了一种包含指令的计算机程序产品，当指令在上述通信装置上运行时，使得该通信装置执行如第一方面及其任一实施方式所述的方法。
第六方面，提供了一种芯片系统，该芯片系统包括处理器，用于支持通信装置实现上述第一方面中所涉及的功能。在一种可能的设计中，该装置还包括接口电路，接口电路可用于从其它装置(例如存储器)接收信号，或者，向其它装置(例如通信接口)发送信号。该芯片系统可以包括芯片，还可以包括其他分立器件。
第二方面至第六方面的技术效果参照第一方面及其任一实施方式的技术效果，在此不再重复。
附图说明
图1为本申请实施例提供的一种无线通信系统的架构示意图；
图2为本申请实施例提供的一种终端设备的结构示意图；
图3为本申请实施例提供的一种处于SA模式的终端设备被叫的流程示意图；
图4为本申请实施例提供的另一种处于SA模式的终端设备被叫的流程示意图；
图5为本申请实施例提供的一种处于SA模式的终端设备被叫无法接通的流程示意图；
图6为本申请实施例提供的另一种处于SA模式的终端设备被叫无法接通的流程示意图；
图7为本申请实施例提供的一种呼叫接收方法的流程示意图；
图8为本申请实施例提供的一种终端设备从NR域回落LTE域的界面变化示意图；
图9为本申请实施例提供的另一种呼叫接收方法的流程示意图；
图10为本申请实施例提供的又一种呼叫接收方法的流程示意图；
图11为本申请实施例提供的再一种呼叫接收方法的流程示意图；
图12为本申请实施例提供的一种通信装置的结构示意图；
图13为本申请实施例提供的另一种通信装置的结构示意图；
图14为本申请实施例提供的一种芯片系统的结构示意图。
具体实施方式
需要说明的是，本申请实施例涉及的术语“第一”、“第二”等仅用于区分同一类型特征的目的，不能理解为用于指示相对重要性、数量、顺序等。
本申请实施例涉及的术语“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本申请的实施方式部分使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请，下面将结合附图对本申请的实施例进行详细描述。
首先对本申请涉及的概念进行描述。
独立组网(stand alone，SA)和非独立组网(non-stand alone，NSA)：NSA指第 四代(4th generation，4G)通信(也称长期演进(long term evolution，LTE))与第五代(5th generation，5G)通信(也称新空口(new radio，NR))联合组网，SA指5G独立组网。在NSA中没有独立的5G核心网，而是采用双连接的方式，即在无线侧5G接入网设备和4G接入网设备共存，在核心网侧5G与4G共用4G核心网。在SA中，5G核心网与4G核心网是独立的，4G接入网设备和5G接入网设备也是独立的。本申请实施例以SA为例，但并不意在限定于此。
互联网协议(internet protocol，IP)多媒体子系统(IP multimedia subsystem，IMS)：是一种全新的多媒体业务形式，它能够满足客户更新颖、更多样化的多媒体业务的需求。IMS被认为是下一代通信网络的核心技术，能够实现移动网络与固网融合。在IMS中采用会话初始协议(session initialization protocol，SIP)，从而在LTE或NR中可以实现基于IP的语音传输(voice over internet protocol，VoIP)，在LTE中称为长期演进语音承载(voice over LTE，VoLTE)，在NR中称为新空口语音承载(voice over NR，VoNR)。
如图1所示，本申请实施例提供的无线通信系统100包括第一终端设备101、第二终端设备102、核心网105、IMS 106、为第一终端设备101提供5G网络的第一接入网设备103、为第二终端设备102提供4G网络和5G网络的第二接入网设备104。其中，第一终端设备101可以为主叫终端设备、第二终端设备102可以为被叫终端设备。本申请中可以将终端设备(例如第一终端设备101和第二终端设备102)以外的设备(例如第一接入网设备103、第二接入网设备104、核心网105和IMS 106)统称为网络(network，NW)。
IMS 106可以包括代理呼叫会话控制功能(proxy-call session control function，P-CSCF)实体1061、查询呼叫会话控制功能(interrogating-call session control function，I-CSCF)实体1062、服务呼叫会话控制功能(serving-call session control function，S-CSCF)实体1063和归属地用户服务器(home subscriber server，HSS)1064。
P-CSCF实体1061是接入网到IMS 106的最先连接点，所有发起于支持IMS的终端设备的会话消息以及终止于支持IMS的终端设备的会话消息都要通过P-CSCF实体1061转发。P-CSCF实体1061可用于将来自终端设备的IMS注册请求转发给S-CSCF实体1063，以及，将注册响应信息转发给终端设备。
I-CSCF实体1062可以连接S-CSCF实体1063和P-CSCF实体1061，用于为终端设备提供到归属网络的入口。在IMS注册过程中，P-CSCF实体1061可以将来自终端设备的IMS注册请求转发给I-CSCF实体1062，I-CSCF实体1062可以查询IMS 106中的HSS 1064，为终端设备选择一个S-CSCF实体1063。在呼叫过程中，去往IMS网络的呼叫消息首先路由到I-CSCF实体1062，I-CSCF实体1062可以通过IMS 106中的HSS 1064为终端设备查询到用户所注册的S-CSCF实体1063的地址信息，之后再将消息路由到S-CSCF实体1063。
S-CSCF实体1063为IMS 106的控制核心，为终端设备提供会话控制和注册等功能。S-CSCF实体1063用于接收P-CSCF实体1061转发的IMS注册请求，与HSS 1064配合对终端设备进行鉴权。S-CSCF实体1063在确定鉴权通过后，从HSS 1064获取终端设备的签约信息。S-CSCF实体1063还用于与各应用服务器相连，S-CSCF实体 1063还用于触发应用服务器执行操作，将终端设备的请求路由到相应的应用服务器。
HSS 1064用于存储所有与用户和服务相关的数据，例如用户身份、签约信息、接入信息等。
应该理解，虽然图1所示的无线通信系统100仅包括两个终端设备以及两个接入网设备，但无线通信系统100可以包括更少和/或更多终端设备，也可以包括更多接入网设备。此外，无线通信系统100还可以包括为第一终端设备101提供2G/3G/4G网络的接入网设备，无线通信系统100还可以包括为第二终端设备102提供2G/3G网络的接入网设备。
以第二终端设备102为例，第二终端设备102可以在开机、重启、退出飞行模式、热插拔卡、公共陆地移动网络(public land mobile network，PLMN)变更、跟踪区域更新(tracking area update，TAU)、IMS注册失败等事件发生时，生成IMS注册请求。然后，第二终端设备102可以将该IMS注册请求通过第二接入网设备102以及核心网105发送给IMS 106中的P-CSCF实体1061。第二终端设备102还可以通过第二接入网设备102以及核心网105，从IMS 106接收注册响应消息。例如，IMS注册请求可以是初始注册请求。该初始注册请求可以包括用户信息、终端能力信息等。相应地，注册响应消息可以是会话初始协议(session initialization protocol，SIP)401消息。该401消息可以包括鉴权信息，用于要求第二终端设备102进行鉴权。又例如，IMS注册请求可以是挑战(challenging)注册请求。该挑战注册请求可以包括鉴权信息。相应地，注册响应消息可以是SIP 200OK消息，用于指示IMS注册成功。
在第二终端设备102成功注册IMS的情况下，第二终端设备102可以通过IMS来实现语音业务。例如第二终端设备102可以通过拨打其他终端设备(例如第一终端设备101)的手机号码来呼叫其他终端设备，或者接听来自其他终端设备(例如第一终端设备101)的呼叫。
本申请实施例所涉及的终端设备(例如第一终端设备101或第二终端设备102)，可以是一种具有无线收发功能的设备，终端设备可以是移动的，也可以是固定的。终端设备可以部署在陆地上(例如室内或室外、手持或车载等)，也可以部署在水面上(例如轮船等)，还可以部署在空中(例如飞机、气球和卫星等)。终端设备可以是4G网络、5G网络或者未来演进的公共陆地移动网(public land mobile network，PLMN)中的用户设备(user equipment，UE)、接入终端、终端单元、用户单元(subscriber unit)、终端站、移动站(mobile station，MS)、移动台、远方站、远程终端、移动设备、无线通信设备、终端代理或终端装置等。例如，终端设备可以是手机、平板电脑、笔记本电脑、智能手环、智能手表、耳机、智能音箱、虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。本申请实施例对终端设备的具体类型和结构等不作限定。
以终端设备为手机为例，图2示出了终端设备的一种可能的结构。该终端设备200可以包括处理器210、外部存储器接口220、内部存储器221、通用串行总线(universal  serial bus，USB)接口230、电源管理模块240、电池241、无线充电线圈242、天线1、天线2、移动通信模块250、无线通信模块260、音频模块270、扬声器270A、受话器270B、麦克风270C、耳机接口270D、传感器模块280、按键290、马达291、指示器292、摄像头293、显示屏294以及用户标识模块(subscriber identification module，SIM)卡接口295等。
其中，传感器模块280可以包括压力传感器、陀螺仪传感器、气压传感器、磁传感器、加速度传感器、距离传感器、接近光传感器、指纹传感器、温度传感器、触摸传感器、环境光传感器、骨传导传感器等。
可以理解的是，本申请实施例示意的结构并不构成对终端设备200的具体限定。在本申请另一些实施方式中，终端设备200可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
处理器210可以包括一个或多个处理单元，例如：处理器210可以包括中央处理单元(central processing unit，CPU)、应用处理器(application processor，AP)、调制解调处理器、图形处理器(graphics processing unit，GPU)、图像信号处理器(image signal processor，ISP)、控制器、存储器、视频编解码器、数字信号处理器(digital signal processor，DSP)、基带处理器以及神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。例如，处理器210可以是应用处理器AP。或者，上述处理器210可以集成在片上系统(system on chip，SoC)中。或者，上述处理器210可以集成在集成电路(integrated circuit，IC)芯片中。该处理器210可以包括IC芯片中的模拟前端(analog front end，AFE)和微处理单元(micro-controller unit，MCU)。
其中，控制器可以是终端设备200的神经中枢和指挥中心。控制器可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。
处理器210中还可以设置存储器，用于存储指令和数据。在一些实施方式中，处理器210中的存储器为高速缓冲存储器。该存储器可以保存处理器210刚用过或循环使用的指令或数据。如果处理器210需要再次使用该指令或数据，可从所述存储器中直接调用。避免了重复存取，减少了处理器210的等待时间，因而提高了系统的效率。
在一些实施方式中，处理器210可以包括一个或多个接口。接口可以包括集成电路(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)接口和/或USB接口等。
可以理解的是，本申请实施例示意的各模块间的接口连接关系，只是示意性说明，并不构成对终端设备200的结构限定。在本申请另一些实施方式中，终端设备200也可以采用上述实施方式中不同的接口连接方式，或多种接口连接方式的组合。
电源管理模块240用于从充电器接收充电输入。其中，充电器可以是无线充电器(如终端设备200的无线充电底座或者其他可以为终端设备200无线充电的设备)， 也可以是有线充电器。例如，电源管理模块240可以通过USB接口230接收有线充电器的充电输入。电源管理模块240可以通过电子设备的无线充电线圈242接收无线充电输入。
其中，电源管理模块240为电池241充电的同时，还可以为电子设备供电。电源管理模块240接收电池241的输入，为处理器210、内部存储器221、外部存储器接口220、显示屏294、摄像头293和无线通信模块260等供电。电源管理模块240还可以用于监测电池241的电池容量、电池循环次数、电池健康状态(漏电、阻抗)等参数。在其他一些实施方式中，电源管理模块240也可以设置于处理器210中。
终端设备200的无线通信功能可以通过天线1、天线2、移动通信模块250、无线通信模块260、调制解调处理器以及基带处理器等实现。
天线1和天线2用于发射和接收电磁波信号。终端设备200中的每个天线可用于覆盖单个或多个通信频带。不同的天线还可以复用，以提高天线的利用率。例如：可以将天线1复用为无线局域网的分集天线。在另外一些实施方式中，天线可以和调谐开关结合使用。
移动通信模块250可以提供应用在终端设备200上的包括2G/3G/4G/5G等无线通信的解决方案。无线通信模块260可以提供应用在终端设备200上的包括无线局域网(wireless local area networks，WLAN)(如无线保真(wireless fidelity，Wi-Fi)网络)、蓝牙(bluetooth，BT)、全球导航卫星系统(global navigation satellite system，GNSS)、调频(frequency modulation，FM)、近距离无线通信技术(near field communication，NFC)、红外技术(infrared，IR)等无线通信的解决方案。在一些实施方式中，终端设备200的天线1和移动通信模块250耦合，天线2和无线通信模块260耦合，使得终端设备200可以通过无线通信技术与网络以及其他设备通信。
终端设备200通过GPU、显示屏294以及应用处理器等实现显示功能。GPU为图像处理的微处理器，连接显示屏294和应用处理器。GPU用于执行数学和几何计算，用于图形渲染。处理器210可包括一个或多个GPU，其执行程序指令以生成或改变显示信息。
显示屏294用于显示图像，视频等。显示屏294包括显示面板。在一些实施方式中，终端设备200可以包括1个或N个显示屏294，N为大于1的正整数。
终端设备200可以通过ISP、摄像头293、视频编解码器、GPU、显示屏294以及应用处理器等实现拍摄功能。ISP用于处理摄像头293反馈的数据。在一些实施方式中，ISP可以设置在摄像头293中。摄像头293用于捕获静态图像或视频。在一些实施方式中，终端设备200可以包括1个或N个摄像头293，N为大于1的正整数。
外部存储器接口220可以用于连接外部存储卡，例如微闪迪(micro SanDisk，Micro SD)卡，实现扩展终端设备200的存储能力。外部存储卡通过外部存储器接口220与处理器210通信，实现数据存储功能。例如将音乐，视频等文件保存在外部存储卡中。
内部存储器221可以用于存储计算机可执行程序代码，所述可执行程序代码包括指令。处理器210通过运行存储在内部存储器221的指令，从而执行终端设备200的各种功能应用以及数据处理。此外，内部存储器221可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、通用闪存存储 器(universal flash storage，UFS)等。
终端设备200可以通过音频模块270、扬声器270A、受话器270B、麦克风270C、耳机接口270D以及应用处理器等实现音频功能。例如音乐播放，录音等。
音频模块270用于将数字音频信息转换成模拟音频信号输出，也用于将模拟音频输入转换为数字音频信号。在一些实施方式中，音频模块270可以设置于处理器210中，或将音频模块270的部分功能模块设置于处理器210中。扬声器270A，也称“喇叭”，用于将音频电信号转换为声音信号。受话器270B，也称“听筒”，用于将音频电信号转换成声音信号。麦克风270C，也称“话筒”，“传声器”，用于将声音信号转换为电信号。终端设备200可以设置至少一个麦克风270C。耳机接口270D用于连接有线耳机。耳机接口270D可以是USB接口230，也可以是3.5mm的开放移动电子设备平台(open mobile terminal platform，OMTP)标准接口，美国蜂窝电信工业协会(cellular telecommunications industry association of the USA，CTIA)标准接口。
按键290包括开机键、音量键等。按键290可以是机械按键。也可以是触摸式按键。终端设备200可以接收按键输入，产生与终端设备200的用户设置以及功能控制有关的键信号输入。马达291可以产生振动提示。马达291可以用于来电振动提示，也可以用于触摸振动反馈。指示器292可以是指示灯，可以用于指示充电状态，电量变化，也可以用于指示消息、未接来电、通知等。SIM卡接口295用于连接SIM卡。SIM卡可以通过插入SIM卡接口295，或从SIM卡接口295拔出，实现和终端设备200的接触和分离。终端设备200可以支持1个或N个SIM卡接口，N为大于1的正整数。SIM卡接口195可以支持纳SIN(Nano SIM)卡、微SIM(Micro SIM)卡、SIM卡等。在一些实施方式中，终端设备200采用嵌入式(embedded SIM，eSIM)卡，eSIM卡可以嵌在终端设备200中，不能和终端设备200分离。
图3示出了终端设备(即前文所述的第二终端设备)回落至LTE域接收被叫的正常流程，包括步骤S101-S113，其中，步骤S102-S106是可选的。
S101、服务集中和连续性应用服务器(service centralization and continuity application server，SCC AS)接收来自主叫方(即前文所述的第一终端设备)的IMS呼叫请求消息，向5G核心网(本申请附图中用核心网表示)发送邀请(INVITE)消息。
SCC AS用于实现终端设备接入IMS域以完成IMS会话建立和控制。
在本申请中邀请(INVITE)消息用于请求呼叫终端设备。邀请(INVITE)消息包括来自(From)标签、至(To)标签、呼叫标识(Call-ID)标签。来自(From)标签用于指示呼叫的源地址。至(To)标签用于指示呼叫的目的地址。呼叫标识(Call-ID)标签作为呼叫的全球唯一标识符。
S102、5G核心网向5G接入网设备发送寻呼(paging)消息。
寻呼(paging)消息用于在5G核心网与5G接入网设备之间建立会话。
S103、5G接入网设备向终端设备发送移动终端寻呼(mobile terminal paging，MT paging)消息。
移动终端寻呼消息用于请求呼叫终端设备。移动终端寻呼消息包括被叫的终端设备的标识(例如临时移动用户识别码(temporary mobile subscriber identity，TMSI))。
S104、终端设备与5G接入网设备建立RRC连接。
S105、终端设备通过5G接入网设备与5G核心网执行服务请求流程(service request procedure)。
服务请求流程的目的是将终端设备的5G系统移动性管理(5G system mobility management，5GMM)从5GMM空闲态(5GMM-IDLE)改变为5GMM连接态(5GMM-CONNECTED)，并建立或恢复5G质量标识(5G quality identity，5QI)为5的承载，5QI为5的承载指用于传输IMS信令的不保证比特速率(guaranteed bit rate，Non-GBR)承载。
S106、5G接入网设备与终端设备执行RRC重配置(reconfiguration)流程，以建立IMS的数据资源承载(data resource bearer，DRB)。
该RRC重配置流程是由服务请求流程所触发。
需要说明的是，步骤S102-S106是可选的，如果终端设备的5GMM已经处于5GMM连接态(5GMM-CONNECTED)则不必执行步骤S102-S106。
终端设备通过该DRB的建立可以判断网络侧将要发送来电或短信，并通过该DRB接收IMS数据。
S107、5G核心网通过5G接入网设备向终端设备发送邀请(INVITE)消息。
关于邀请(INVITE)消息参照步骤S101中邀请(INVITE)消息的描述，在此不再赘述。
S108、终端设备通过5G接入网设备和5G核心网向SCC AS发送100尝试(100Trying)消息。
100尝试(100Trying)消息用于表示已经接收到邀请(INVITE)消息。100尝试(100Trying)消息包括与邀请(INVITE)消息中相同的来自(From)标签、至(To)标签、呼叫标识(Call-ID)标签使得SCC AS能够将该100尝试(100Trying)消息与发送的邀请(INVITE)消息相关联。
S109、终端设备通过5G接入网设备和5G核心网向SCC AS发送183会话进度(183session progress)消息。
183会话进度(183session progress)消息用于指示建立会话的进度信息，该消息包括原因短语(reason-phrase)、头字段和消息体，原因短语用于指示原因，头字段或消息体可以用于指示建立会话的进度的更多信息。
S110、SCC AS通过5G核心网和5G接入网设备向终端设备发送回落至LTE域的指示信息，或者，发送建立或修改语音的专有承载的指示信息。
其中，回落至LTE域的指示信息针对终端设备不支持VoNR的场景。
S111、如果终端设备接收到回落至LTE域的指示信息，则终端设备回落至LTE域，并在LTE域建立语音的专用承载。
终端设备可以通过与4G接入网设备之间的TAU流程回落至LTE域，终端设备还通过4G接入网设备和4G核心网向SCC AS发送183会话进度(183session progress)消息，关于183会话进度(183session progress)消息见前面描述。终端设备通过4G接入网设备与4G核心网建立语音的专用承载。
S112、终端设备通过4G接入网设备和4G核心网向SCC AS发送180响铃(180 Ringing)消息。
该180响铃(180Ringing)消息用于表示终端设备进行响铃。如果用户选择接听则呼叫成功，呼叫的语音数据将在语音的专用承载上传输。
S113、终端设备与对端(呼叫方)进行通话。
终端设备通过4G接入网设备、4G核心网和SCC AS与对端(呼叫方)进行通话。
图4示出了处于SA模式的终端设备(即前文所述的第二终端设备)在LTE域接收被叫的正常流程，包括步骤S201-S213，其中，步骤S201-S209参照步骤S101-S109。
S210、SCC AS通过5G核心网和5G接入网设备向终端设备发送建立或修改语音的专有承载的指示信息。
其中，建立或修改语音的专有承载指示信息针对终端设备支持VoNR的场景。
S211、如果终端设备接收到建立或修改语音的专有承载的指示信息，则终端设备在NR域建立或修改语音的专有承载。
终端设备还通过5G接入网设备和5G核心网向SCC AS发送183会话进度(183session progress)消息，关于183会话进度(183session progress)消息见前面描述。终端设备通过5G接入网设备和5G核心网建立或修改语音的专有承载。
S212、终端设备通过5G接入网设备和5G核心网向SCC AS发送180响铃(180Ringing)消息。
该180响铃(180Ringing)消息用于表示终端设备进行响铃。如果用户选择接听则呼叫成功，呼叫的语音数据将在语音的专用承载上传输。
S213、终端设备与对端(呼叫方)进行通话。
终端设备通过5G接入网设备、5G核心网和SCC AS与对端(呼叫方)进行通话。
在移动通信运营商逐步建设SA的过程中仍存在网络侧的SA功能不完善的问题，处于SA模式的终端设备在被呼叫时，经常出现因为网络侧故障导致终端设备无法接通呼叫的问题。
如图5所示，处于SA模式的终端设备被叫无法接通的一种可能场景是：由于网络故障等原因，虽然图3中的步骤S101-S106(或S201-S206)执行成功，但是步骤S107(或S207)中SCC AS发送的邀请(INVITE)消息无法被5G接入网设备接收，SCC AS多次重传邀请(INVITE)消息以后，会执行电路交换重试(circuit switching retry，CS Retry)来在电路交换(circuit switching，CS)域寻呼终端设备。但是由于终端设备处于SA模式，只注册了IMS域未注册CS域，所以无法接收CS域的寻呼。
如图6所示，处于SA模式的终端设备被叫无法接通的另一种可能场景是：由于网络故障或突发干扰导致上行发射困难等原因，虽然图3中的步骤S101-S108(或S201-S208)执行成功，但是当终端设备在步骤S109(或S209)发送183会话进度(183session progress)消息后，未接收到回落至LTE域的指示信息，或者，建立或修改语音的专有承载的指示信息，终端设备会多次重传183会话进度(183session progress)消息，直至超时后终端设备会发送580资源预留失败(precondition failure)消息，表示寻呼失败。该场景下寻呼失败的原因在于演进分组系统回落(evolved packet system fallback，EPS FB)流程完全由网络侧控制，即使网络故障导致EPS FB流程异常，终端设备侧只能被动等待网络侧的指示。
本申请实施例提供了一种呼叫接收方法，以解决图5中所示的被叫无法接通的问题，如图7所示，该方法包括步骤S301-S311，其中，步骤S301-S306参照前文所述的步骤S101-S106，在此不再赘述。
S307、SCC AS发送的邀请(INVITE)消息无法被5G接入网设备接收，SCC AS多次重传邀请(INVITE)消息。
S308、在服务请求流程(service request procedure)所触发的RRC重配置流程完成后，终端设备启动定时器T1。如果定时器T1超时后终端设备还未接收到邀请(INVITE)消息等IMS数据，则终端设备主动回落至LTE域以接收呼叫，并启动定时器T2。
定时器T1和定时器T2的时长可以根据网络侧的重传行为来确定，定时器T1小于网络重传的总时间，定时器T2大于网络重传的总时间。例如定时器T1为4秒，定时器T2为20秒。
终端设备可以通过是否接收到服务接受(service accept)消息来确定服务请求流程(service request procedure)是否完成，当接收到服务接受(service accept)消息时则可以确定服务请求流程(service request procedure)完成。终端设备从网络侧接收到RRC重配置消息，并且反馈RRC重配置完成消息，即表明完成RRC重配置流程。并且终端设备通过IMS对应的DRB的建立可以判断网络侧将要发送来电或短信。终端设备可以通过检测IMS承载(分组数据单元(packet data unit，PDU)会话标识)对应的DRB中是否有邀请(INVITE)消息等IMS数据来确定是否有来电或短信。
终端设备可以通过发起与4G接入网设备之间的TAU流程来主动回落至LTE域，终端设备可以在发起TAU流程时启动定时器T2。如图8所示，当终端设备从NR域回落至LTE域后，网络标识从5G变为4G。
终端设备在LTE域上接收呼叫指终端设备在LTE域(通过4G接入网设备)上接收邀请(INVITE)消息或者CS回落(CS fallback，CSFB)指示消息。
S309、如果终端设备在定时器T2超时前接收到呼叫，则回落成功，终端设备在通话挂断后主动回到NR域。如果终端设备在定时器T2超时前没有接收到呼叫，则回落失败，终端设备在定时器T2超时后主动回到NR域。
SCC AS多次重传邀请(INVITE)消息以后，会执行电路CS Retry来在CS域寻呼终端设备，SCC AS通过4G核心网(图中用核心网表示)和4G接入网设备与终端设备建立呼叫，使得终端设备接收呼叫。
终端设备通过重选或切换或重定向流程主动回到NR域。如图8所示，当终端设备从LTE域回到NR域后，网络标识从变4G为5G。
S310、终端设备统计回落至LTE域的成功率，如果成功率小于成功率阈值，终端设备在一定时间段内不再主动回落至LTE域(即退出主动回落模式)。
回落至LTE域的成功率指终端设备成功回落至LTE域的次数与终端设备回落至LTE域的总次数之比，终端设备成功回落至LTE域指终端设备在回落至LTE域后的第二时间段内接收到呼叫。
终端设备在一定时间段内不再主动回落至LTE域(即退出主动回落模式)是指：在服务请求流程(service request procedure)所触发的RRC重配置流程完成后，终端 设备启动定时器T1，如果定时器T1超时后终端设备还未接收到邀请(INVITE)消息等IMS数据，则终端设备也不会主动回落至LTE域。也就是说，如果回落至LTE域并在LTE域接收呼叫的成功率很低，则终端设备在一定时间内不主动回落至LTE域。
另外，如果该成功率大于或等于成功率阈值，则在下一次呼叫中，终端设备可以在步骤S308的条件满足时执行步骤S308，也就是说，如果该成功率大于或等于成功率阈值，在服务请求流程(service request procedure)所触发的RRC重配置流程完成后，终端设备启动定时器T1。如果定时器T1超时后终端设备还未接收到邀请(INVITE)消息等IMS数据，则终端设备主动回落至LTE域以接收下一次呼叫，并启动定时器T2。
S311、终端设备退出回落模式后(即当终端设备统计出成功率小于成功率阈值时)，如果满足一定条件终端设备仍会主动回落至LTE域以接收呼叫。
终端设备退出回落模式后，如果再次接收到移动终端寻呼(MT paging)消息，则启动定时器T5、定时器T6和定时器T7，如果在定时器T5超时前未收到邀请(INVITE)消息或者漏电提醒短信等IMS数据，而是在定时器T6超时后定时器T7超时前接收到漏电提醒短信，则终端设备主动回落至LTE域以接收呼叫。其中，定时器T6是可选的，即也可以在定时器T7超时前接收到漏电提醒短信，则终端设备主动回落至LTE域以接收呼叫。定时器T7的时长大于定时器T6的时长，定时器T6的时长大于定时器T5的时长。定时器T5、定时器T6和定时器T7的时长根据网络侧的漏电提醒行为来确定。
该步骤使得终端设备通过分析漏电提醒短信(包括漏电提醒关键字的短信)可以确定漏接呼叫，所以可以通过TAU流程主动回落至LTE域以接收呼叫。关于如何回落至LTE域以及如何确定接收到IMS数据见步骤S308，以此不再赘述。
本申请实施例提供了另一种呼叫接收方法，以解决图6中所示的被叫无法接通的问题，如图9所示，该方法包括步骤S401-S414，其中，步骤S401-S408参照前文所述的步骤S101-S108，在此不再赘述。
S409、终端设备向5G接入网设备发送183会话进度(183session progress)消息，启动定时器T3，并监测回落至LTE域的指示信息(即回落指示信息)，以及，建立或修改语音的专有承载的指示信息(即承载指示信息)。
定时器T3的时长小于183的重传总时间。
S410、如果终端设备在定时器T3超时前，未接收到回落至LTE域的指示信息，以及，建立或修改语音的专有承载的指示信息，则终端设备主动回落至LTE域以接收呼叫。
终端设备可以通过与4G接入网设备之间的TAU流程主动回落至LTE域。
S411、终端设备通过4G接入网设备向4G核心网发送183会话进度(183session progress)消息，并启动定时器T4。
定时器T4的时长自定义。
S412、终端设备与4G核心网在LTE域上建立或修改语音的专有承载。
终端设备通过4G接入网设备、4G核心网和SCC AS与对端(呼叫方)进行通话。
S413、如果终端设备在定时器T4超时前接收到呼叫，则回落成功，终端设备在 通话挂断后主动回到NR域。如果终端设备在定时器T4超时前没有接收到呼叫，则回落失败，终端设备在定时器T4超时后主动回到NR域。
可选的，终端设备可以在定时器T4超时后启动定时器T8，当定时器T8超时后再主动回到NR域，以避免在定时器T8超时前漏接主叫方可能重拨的呼叫。
进一步地，如果(连续)多次出现(即出现次数大于次数阈值)：终端设备向5G接入设备发送183会话进度(183session progress)消息后，在定时器T3超时前未接收到回落指示信息以及承载指示信息，则终端设备可以在定时器T4超时后启动定时器T8。定时器T8的时间长度可以由上述情况出现的次数来确定，上述情况出现的次数越多则定时器T8的时间长度越长，上述情况出现的次数越少则定时器T8的时间长度越短，特别地，定时器T8的时间长度与上述情况出现的次数成比例增加。
另外，如果终端设备在LTE域上也出现了终端设备发送了183会话进度(183session progress)消息，但是未能在LTE域上接收到指示终端设备在LTE域建立语音的专有承载的指示信息，则终端设备可以提前回NR(无需等定时器T8超时)。
S414、终端设备统计回落至LTE域的成功率，如果成功率小于成功率阈值，终端设备在一定时间段内不再主动回落至LTE域(即退出主动回落模式)。
关于回落至LTE域的成功率可以参照步骤S310，在此不再赘述。
如果该成功率大于或等于成功率阈值，则在下一次呼叫中，终端设备可以在步骤S410的条件满足时执行步骤S410，也就是说，如果该成功率大于或等于成功率阈值，终端设备向5G接入网设备发送183会话进度(183session progress)消息，启动定时器T3，如果终端设备在定时器T3超时前，未接收到回落至LTE域的指示信息，以及，建立或修改语音的专有承载的指示信息，则终端设备主动回落至LTE域以接收下一次呼叫。
综上所述，本申请实施例提供了另一种呼叫接收方法，如图10所示，该方法包括：
S501、终端设备在NR域接收来自网络的呼叫消息。
终端设备处于SA模式。呼叫消息用于请求呼叫终端设备，当终端设备为5GMM空闲态时，呼叫消息可以为前文所述的移动终端寻呼(MT paging)消息，当终端设备为5GMM连接态时，呼叫消息可以为前文所述的邀请(INVITE)消息。具体见步骤S101-S106中的相关描述。
S502、如果在预设呼叫流程后的第一时间段内，终端设备未接收到来自网络的预期信息，则终端设备在第一时间段之后回落至LTE域以接收呼叫。
在一种可能的实施方式中，预设呼叫流程为服务请求流程(service request procedure)所触发的RRC重配置流程，预期信息为邀请(INVITE)消息等IMS数据。该实施方式可以参照步骤S308，第一时间段指从定时器T1启动到定时器T1超时之间的时间段。
在另一种可能的实施方式中，预设呼叫流程为发送183会话进度(183session progress)消息，预期信息为承载指示信息或回落指示信息，承载指示信息用于指示终端设备在NR域建立或修改语音的专有承载，回落指示信息用于指示终端设备回落至LTE域。该实施方式可以参照步骤S409-S410，第一时间段指从定时器T3启动到定时器T3超时之间的时间段。
本申请实施例提供的呼叫接收方法，处于SA模式的终端设备在NR域接收来自网络的呼叫消息时，当5G网络发生故障时，会导致在预设呼叫流程后的第一时间段内，终端设备无法接收到来自网络的预期信息，所以终端设备在第一时间段之后主动回落至LTE域以接收呼叫。由于通常终端设备都是等待网络侧指示是否回落至LTE域的，当5G网络发生故障时，5G网络无法指示终端设备回落至LTE域。所以本申请实施例提供的呼叫接收方法通过主动回落至LTE域以尝试在LTE域接收呼叫，可以提高处于SA模式的终端设备的被叫成功率。
可选的，如图11所示，该呼叫接收方法还可以包括：
S503、在终端设备回落至LTE域后的第二时间段内，如果终端设备未在LTE域接收到呼叫，则终端设备在第二时间段之后回到NR域。
步骤S503可以参照步骤S309，第二时间段指从定时器T2启动到定时器T2超时之间的时间段。或者，步骤S503可以参照步骤S413，第二时间段指从定时器T4启动到定时器T4超时之间的时间段。
在一种可能的实施方式中，在终端设备回落至LTE域后的第二时间段内，如果终端设备在LTE域发送183会话进度消息(183session progress)之后，未能在LTE域接收到指示终端设备在LTE域建立语音的专有承载的指示信息，并且未接收到呼叫，则终端设备在第二时间段之后回到NR域。
在一种可能的实施方式中，终端设备可以在第二时间段之后的第三时间段内在LTE域接收重拨的呼叫，并在第三时间段之后回到NR域。其中，第三时间段的时间长度由终端设备在NR域未接收到预期信息的次数来确定，该次数越多则第三时间段的时间长度越长，该次数越少则第三时间段的时间长度越短。该实施方式可以参照步骤S413，第三时间段指从定时器T8启动到定时器T8超时之间的时间段。
该步骤使得终端设备能在LTE域驻留一段时间以便不会错过接收对端重拨的来电，当一段时间后在LTE域无法接收到呼叫时可以回到NR域重新接收来电。
S504、终端设备统计回落至LTE域的成功率，并根据成功率来确定在一定时间内是否主动回落至所述LTE域。
关于回落至LTE域的成功率可以参照步骤S310，在此不再赘述。
如果该成功率大于或等于成功率阈值，则在下一次呼叫中，终端设备可以在步骤S502的条件满足时执行步骤S502，也就是说，如果在预设呼叫流程后的第一时间段内，终端设备未接收到预期信息，则终端设备在第一时间段之后回落至LTE域以接收下一次呼叫。该实施方式可以参照步骤S310或S414。
如果该成功率小于成功率阈值，则终端设备在一定时间段内不再主动回落至LTE域(即退出主动回落模式)，也就是说，如果成功率小于成功率阈值，即使在预设呼叫流程后的第一时间段内，终端设备未接收到预期信息，终端设备在第一时间段之后也不会主动回落至LTE域。该实施方式可以参照步骤S310或S414。成功率小于成功率阈值的原因可能是LTE域的信号较差导致，此时在一定时间段避免终端设备主动回落LTE域可以避免终端设备在LTE域和NR域之间反复重定向。
但是，当终端设备一定时间段内不主动回落至LTE域时，如果满足一定条件终端设备仍可以主动回落至LTE域以接收呼叫。例如，当终端设备一定时间段内不主动回 落至LTE域时，如果终端设备接收到寻呼消息(例如移动终端寻呼(MT paging)消息)，并且终端设备在接收到寻呼消息之后的第四时间段内未接收到来自网络的INVITE消息、漏电提醒短信等IMS数据，并且终端设备在接收到寻呼消息之后的第五时间段内接收到漏电提醒短信，则终端设备回落至LTE域以接收呼叫，第四时间段与第五时间段无重叠。该实施方式可以参照步骤S311，第四时间段指从定时器T5启动到定时器T5超时之间的时间段，第五时间段指从定时器T5超时到定时器T7超时之间的时间段，可选的，第五时间段指从定时器T6超时到定时器T7超时之间的时间段。终端设备通过分析漏电提醒短信(包括漏电提醒关键字的短信)可以确定漏接呼叫，所以可以主动回落至LTE域以接收重拨的呼叫。
可以理解的是，以上各个实施例中，由终端设备实现的方法和/或步骤，也可以由终端设备的部件(例如芯片或者电路)实现。
本申请实施例还提供了一种通信装置。该通信装置可以为上述方法实施例中的终端设备，或者包含上述终端设备的装置，或者为终端设备内的芯片或功能模块。从而实现上述各种方法。
该通信装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员可以很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法实施例对通信装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
图12示出了一种通信装置30的结构示意图。该通信装置30包括处理模块301和收发模块302。该通信装置30可以为前文所述的终端设备。处理模块301也可以称为处理单元，用以实现上述方法实施例中终端设备的处理功能。例如执行图7中的步骤S309、S310、S311，图9中的步骤S410、S413、S414，图10中的步骤S502，图11中的步骤S502、S503、S504。收发模块302，也可以称为收发单元，用以实现上述方法实施例中终端设备的收发功能。例如执行图7中的步骤S303-S311，图9中的步骤S403-S414，图10中的步骤S501-S502，图11中的步骤S501-S504。收发模块302可以称为收发电路、收发机、收发器或者通信接口。
以通信装置30为上述方法实施例中的终端设备为例。
在一种可能的实施方式中，收发模块302用于在NR域接收来自网络的呼叫消息，呼叫消息用于请求呼叫该通信装置；如果在预设呼叫流程后的第一时间段内，收发模块302未接收到来自网络的预期信息，则处理模块301在第一时间段之后回落至LTE域以接收呼叫。
在一种可能的实施方式中，预设呼叫流程为通信装置与5G接入网设备之间的RRC 重配置流程，该RRC重配置流程由通信装置与5G核心网之间的服务请求流程触发。
在一种可能的实施方式中，预设呼叫流程为通信装置通过5G接入网设备和5G核心网向服务集中和连续性应用服务器发送183会话进度消息，预期信息为承载指示信息或回落指示信息，承载指示信息用于指示通信装置在NR域建立或修改语音的专有承载，回落指示信息用于指示通信装置回落至LTE域。
在一种可能的实施方式中，处理模块301还用于：在回落至LTE域后的第二时间段内，如果收发模块302未在LTE域接收到呼叫，则在第二时间段之后返回NR域。
在一种可能的实施方式中，收发模块302在第二时间段之后的第三时间段内在LTE域接收重拨的呼叫；处理模块301在第三时间段之后返回NR域。
在一种可能的实施方式中，第三时间段的时间长度由收发模块302未接收到预期信息的次数来确定。
在一种可能的实施方式中，在处理模块301回落至LTE域后的第二时间段内，如果收发模块302发送183会话进度消息之后，未在LTE域接收到指示通信装置在LTE域建立语音的专有承载的指示信息，并且未接收到呼叫，则处理模块301在第二时间段之后返回NR域。
在一种可能的实施方式中，处理模块301还用于统计回落至LTE域的成功率，成功率指通信装置成功回落至LTE域的次数与回落至LTE域的总次数之比，通信装置成功回落至LTE域指通信装置在回落至LTE域后的第二时间段内接收到呼叫；处理模块301还用于根据成功率确定在一定时间内是否回落至LTE域。
在一种可能的实施方式中，如果成功率小于成功率阈值，则处理模块301在一定时间内不回落至LTE域。
在一种可能的实施方式中，当处理模块301在一定时间内不回落至LTE域时，如果收发模块302接收到寻呼消息，并且在接收到寻呼消息之后的第四时间段内未接收到来自网络的INVITE消息或漏电提醒短信，并且在接收到寻呼消息之后的第五时间段内接收到漏电提醒短信，则处理模块301回落至LTE域以接收呼叫；其中，第四时间段与第五时间段无重叠。
如图13所示，本申请实施例还提供了一种通信装置。该通信装置40包括处理器401、存储器402和收发器403，处理器401与存储器402和收发器403相耦合，收发器403用于支持通信装置与其他通信装置进行通信。当处理器401执行存储器402中的计算机程序或指令时，图7、图9、图10、图11中终端设备对应的方法被执行。
如图14所示，本申请实施例还提供一种芯片系统。该芯片系统50包括至少一个处理器501和至少一个接口电路502。至少一个处理器501和至少一个接口电路502可通过线路互联。处理器501用于支持通信装置实现上述方法实施例中由终端设备执行的各个功能或者步骤，至少一个接口电路502可用于从其它装置(例如存储器)接收信号，或者，向其它通信装置(例如通信接口)发送信号。该芯片系统可以包括芯片，还可以包括其他分立器件。
本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质包括指令，当指令在上述通信装置上运行时，使得该通信装置执行上述方法实施例中由终端设备执行的各个功能或者步骤，例如执行图7、图9、图10、图11所示的方法。
本申请实施例还提供一种包括指令的计算机程序产品，当指令在上述通信装置上运行时，使得该通信装置执行上述方法实施例中由终端设备执行的各个功能或者步骤，例如执行图7、图9、图10、图11所示的方法。
关于通信装置、芯片系统、计算机可读存储介质、计算机程序产品的技术效果参照前面方法实施例的技术效果。
本申请实施例涉及的处理器可以是一个芯片。例如，可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application specific integrated circuit，ASIC)，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
本申请实施例涉及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的模块及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和模块的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、设备和方法，可以通过其它的方式实现。例如，以上所描述的设备实施例仅仅是示意性的，例如，所述模块的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个模块或组件可以结合或者可以集成到另一个设备，或一些特征可以忽略，或不执 行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，设备或模块的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理模块，即可以位于一个设备，或者也可以分布到多个设备上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能模块可以集成在一个设备中，也可以是各个模块单独物理存在，也可以两个或两个以上模块集成在一个设备中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (12)

  1. 一种呼叫接收方法，其特征在于，包括：
    终端设备在新空口NR域接收来自网络的呼叫消息，所述呼叫消息用于请求呼叫所述终端设备，所述终端设备处于独立组网模式；
    如果在预设呼叫流程后的第一时间段内，所述终端设备未接收到来自所述网络的预期信息，则所述终端设备在所述第一时间段之后回落至长期演进LTE域以接收呼叫。
  2. 根据权利要求1所述的方法，其特征在于，所述预设呼叫流程为所述终端设备与第五代5G接入网设备之间的无线资源控制RRC重配置流程，所述RRC重配置流程由所述终端设备与5G核心网之间的服务请求流程触发，所述预期信息包括邀请INVITE消息。
  3. 根据权利要求1所述的方法，其特征在于，所述预设呼叫流程为所述终端设备通过5G接入网设备和5G核心网向服务集中和连续性应用服务器发送183会话进度消息，所述预期信息为承载指示信息或回落指示信息，所述承载指示信息用于指示所述终端设备在所述NR域建立或修改语音的专有承载，所述回落指示信息用于指示所述终端设备回落至所述LTE域。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述方法还包括：
    在所述终端设备回落至所述LTE域后的第二时间段内，如果所述终端设备未在所述LTE域接收到所述呼叫，则所述终端设备在所述第二时间段之后返回所述NR域。
  5. 根据权利要求4所述的方法，其特征在于，所述终端设备在所述第二时间段之后返回所述NR域，包括：
    所述终端设备在所述第二时间段之后的第三时间段内在所述LTE域接收重拨的所述呼叫；
    所述终端设备在所述第三时间段之后返回所述NR域。
  6. 根据权利要求5所述的方法，其特征在于，所述第三时间段的时间长度由所述终端设备未接收到所述预期信息的次数来确定。
  7. 根据权利要求4所述的方法，其特征在于，所述在所述终端设备回落至所述LTE域后的第二时间段内，如果所述终端设备未在所述LTE域接收到所述呼叫，则所述终端设备在所述第二时间段之后返回所述NR域，包括：
    在所述终端设备回落至所述LTE域后的第二时间段内，如果所述终端设备发送183会话进度消息之后，未在所述LTE域接收到指示所述终端设备在所述LTE域建立语音的专有承载的指示信息，并且未接收到所述呼叫，则所述终端设备在所述第二时间段之后返回所述NR域。
  8. 根据权利要求4-7任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备统计回落至LTE域的成功率，所述成功率指所述终端设备成功回落至所述LTE域的次数与回落至所述LTE域的总次数之比，所述终端设备成功回落至所述LTE域指所述终端设备在回落至所述LTE域后的所述第二时间段内接收到所述呼叫；
    所述终端设备根据所述成功率确定在一定时间内是否回落至所述LTE域。
  9. 根据权利要求8所述的方法，其特征在于，所述终端设备根据所述成功率确定 在一定时间内是否回落至所述LTE域，包括：
    如果所述成功率小于成功率阈值，则所述终端设备在一定时间内不回落至所述LTE域。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    当所述终端设备在一定时间内不回落至所述LTE域时，如果所述终端设备接收到寻呼消息，并且所述终端设备在接收到所述寻呼消息之后的第四时间段内未接收到来自所述网络的INVITE消息或漏电提醒短信，并且所述终端设备在接收到所述寻呼消息之后的第五时间段内接收到漏电提醒短信，则所述终端设备回落至所述LTE域以接收所述呼叫；其中，所述第四时间段与所述第五时间段无重叠。
  11. 一种通信装置，其特征在于，包括处理器和收发器，所述收发器用于与其他通信装置进行通信，当所述处理器执行指令时，如权利要求1-10任一项所述的方法被执行。
  12. 一种计算机可读存储介质，其特征在于，包括指令，当所述指令在通信装置上运行时，使得所述通信装置执行如权利要求1-10任一项所述的方法。
PCT/CN2022/117661 2021-12-15 2022-09-07 呼叫接收方法和通信装置 WO2023109205A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202111534732 2021-12-15
CN202111534732.5 2021-12-15
CN202210159154.XA CN114698046B (zh) 2021-12-15 2022-02-21 呼叫接收方法和通信装置
CN202210159154.X 2022-02-21

Publications (1)

Publication Number Publication Date
WO2023109205A1 true WO2023109205A1 (zh) 2023-06-22

Family

ID=82137612

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/117661 WO2023109205A1 (zh) 2021-12-15 2022-09-07 呼叫接收方法和通信装置

Country Status (2)

Country Link
CN (2) CN114698046B (zh)
WO (1) WO2023109205A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114698046B (zh) * 2021-12-15 2024-05-14 荣耀终端有限公司 呼叫接收方法和通信装置
CN115580945A (zh) * 2022-10-11 2023-01-06 维沃移动通信有限公司 寻呼方法、装置、电子设备及存储介质
CN116684046A (zh) * 2023-07-03 2023-09-01 国广顺能(上海)能源科技有限公司 一种低通信质量下数据上传异常处理系统
CN117835173A (zh) * 2024-03-05 2024-04-05 荣耀终端有限公司 语音呼叫方法、通信装置及计算机可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190281506A1 (en) * 2018-03-06 2019-09-12 T-Mobile Usa, Inc. Controlling fallback procedures for different user groups or device groups
CN111372327A (zh) * 2020-02-18 2020-07-03 华为技术有限公司 基于5g sa网络的呼叫方法、电子设备及系统
CN113438679A (zh) * 2021-05-31 2021-09-24 荣耀终端有限公司 用于提升sa网络下电话呼通率的通信系统及用户设备
CN114698046A (zh) * 2021-12-15 2022-07-01 荣耀终端有限公司 呼叫接收方法和通信装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3065379A1 (en) * 2015-03-06 2016-09-07 Openet Telecom Ltd. System and method for volte session continuation using logical scalable units
US10327126B2 (en) * 2015-06-26 2019-06-18 Nec Corporation Communication apparatus, terminal, and communication method
CN107820716B (zh) * 2017-09-30 2021-01-08 深圳市欢太科技有限公司 一种csfb的回落结果检测方法及装置、计算机存储介质
CN113498123B (zh) * 2020-03-20 2023-06-02 华为技术有限公司 一种网络接入系统、方法及终端
CN113709903A (zh) * 2020-05-21 2021-11-26 华为技术有限公司 一种通信方法、设备及系统
CN113242583B (zh) * 2021-06-21 2023-10-13 维沃移动通信有限公司 一种呼叫方法、终端和网络侧设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190281506A1 (en) * 2018-03-06 2019-09-12 T-Mobile Usa, Inc. Controlling fallback procedures for different user groups or device groups
CN111372327A (zh) * 2020-02-18 2020-07-03 华为技术有限公司 基于5g sa网络的呼叫方法、电子设备及系统
CN113438679A (zh) * 2021-05-31 2021-09-24 荣耀终端有限公司 用于提升sa网络下电话呼通率的通信系统及用户设备
CN114698046A (zh) * 2021-12-15 2022-07-01 荣耀终端有限公司 呼叫接收方法和通信装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
WI RAPPORTEUR (ERICSSON): "RAN1 agreements for Rel-16 Additional MTC Enhancements for LTE", 3GPP DRAFT; R1-1811736 RAN1 AGREEMENTS FOR REL-16 ADDITIONAL MTC ENHANCEMENTS FOR LTE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Chengdu, China; 20181008 - 20181012, 16 October 2018 (2018-10-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051519125 *

Also Published As

Publication number Publication date
CN116896772B (zh) 2024-05-17
CN114698046A (zh) 2022-07-01
CN114698046B (zh) 2024-05-14
CN116896772A (zh) 2023-10-17

Similar Documents

Publication Publication Date Title
WO2023109205A1 (zh) 呼叫接收方法和通信装置
CN110622617B (zh) 信息处理方法、装置及计算机存储介质
CN111404873A (zh) 在支持mec的网络环境中提供ims服务的电子装置
WO2019061414A1 (zh) 一种业务路径的切换方法、设备、存储介质及系统
WO2021030974A1 (zh) 寻呼配置方法、装置、通信设备及存储介质
WO2023246248A1 (zh) 一种被叫寻呼方法和装置
KR20200011137A (ko) 다중 sim을 지원하는 전자 장치 및 이를 위한 방법
WO2020248140A1 (zh) 跟踪区更新方法及装置、通信设备及存储介质
WO2021057776A1 (zh) 互联网协议多媒体子系统呼叫方法、终端和网络功能
WO2021063153A1 (zh) 信息处理方法、网元设备、终端及存储介质
WO2023147754A1 (zh) 一种用于用户设备发起ims注册的方法以及相应的用户设备
CN114286301B (zh) 语音业务控制方法及装置、存储介质、终端设备
US11849067B2 (en) Method for playing multimedia customized ringing signal and customized alerting tone, and application server
WO2023050362A1 (zh) 下行传输配置、接收方法及装置、通信设备及存储介质
US20240163696A1 (en) Measurement gap pre-configuration processing method and apparatus, communication device and storage medium
CN116170415B (zh) 呼叫处理方法、设备及存储介质
WO2021057774A1 (zh) 互联网协议多媒体子系统信息传输方法、终端和网络功能
WO2021212430A1 (zh) 发送数据的方法、装置、用户设备及存储介质
WO2024108759A1 (zh) 建立通话的方法及装置
WO2024007337A1 (zh) 信息处理方法及装置、通信设备及存储介质
WO2022183348A1 (zh) 用户设备的远程配置方法及远程配置方式的确定方法
WO2023065127A1 (zh) 一种传输寻呼消息的方法、装置及存储介质
WO2024060057A1 (zh) 信息处理方法及装置、通信设备及存储介质
WO2022178728A1 (zh) Drx周期的处理方法、装置、通信设备及存储介质
WO2023164796A1 (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: 22905960

Country of ref document: EP

Kind code of ref document: A1