WO2025112573A1 - 一种通信方法和终端设备 - Google Patents

一种通信方法和终端设备 Download PDF

Info

Publication number
WO2025112573A1
WO2025112573A1 PCT/CN2024/107089 CN2024107089W WO2025112573A1 WO 2025112573 A1 WO2025112573 A1 WO 2025112573A1 CN 2024107089 W CN2024107089 W CN 2024107089W WO 2025112573 A1 WO2025112573 A1 WO 2025112573A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
terminal
mobility update
cause value
terminal device
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/CN2024/107089
Other languages
English (en)
French (fr)
Inventor
丁明
张涵
薛飞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Honor Device Co Ltd
Original Assignee
Honor Device Co Ltd
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 Honor Device Co Ltd filed Critical Honor Device Co Ltd
Priority to CN202480040701.XA priority Critical patent/CN121400014A/zh
Publication of WO2025112573A1 publication Critical patent/WO2025112573A1/zh
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Definitions

  • the embodiments of the present application relate to the technical field of electronic devices, and in particular, to a communication method and terminal equipment.
  • the terminal device (referred to as the terminal) can communicate with networks of different standards to achieve communication functions.
  • the networks of different standards may include 3G networks, 4G networks, or 5G networks.
  • the network side can instruct the terminal to change to reside in the 4G network for communication.
  • the terminal can try to change to reside in the 4G network according to the instructions of the network side.
  • the terminal can send a mobility update request such as a TAU (Tracking Area Update) request to the 4G network device in order to try to access the 4G network for communication.
  • a TAU Reject rejection message can be sent to the terminal.
  • the rejection message can carry a corresponding reason value.
  • the reason value may include #111, which indicates that the network rejects terminal access due to unknown reasons.
  • the terminal will attempt to access a network with a lower standard than the 4G network (such as a 3G network) based on the rejection message with the reason value #111 received from the 4G network. At the same time, the terminal will also configure the 4G network to be disabled.
  • 3GPP protocol 24.301 specifically: 3GPP TS 24.301 V18.4.0 (2023-09)
  • the terminal will attempt to access a network with a lower standard than the 4G network (such as a 3G network) based on the rejection message with the reason value #111 received from the 4G network.
  • the terminal will also configure the 4G network to be disabled.
  • a lower-standard network such as a 3G network or a 2G network
  • Some embodiments of the present application provide a communication method and a terminal device, which enable the terminal to quickly access a high-standard network (such as a 4G network) after receiving a rejection message with a reason value of #111, thereby avoiding staying in a low-standard network for a long time.
  • a high-standard network such as a 4G network
  • a communication method which is applied to a terminal device, and the method includes:
  • the terminal device resides in the first network
  • the terminal device receives a first indication message sent by the first network, where the first indication message includes an identifier of the second network and/or an access frequency of the second network, and the first indication message is used to instruct the terminal device to access the second network;
  • the terminal device sends a first mobility update request to the second network, where the first mobility update request includes an identifier of the second network;
  • the terminal device receives a first mobility update rejection message from the second network, wherein the first mobility update rejection message indicates that the second network device of the second network rejects the terminal from accessing the second network, wherein the rejection reason value carried in the first mobility update rejection message is a first reason value, wherein in the label
  • the quasi-protocol stipulates that: in response to receiving the first mobility update rejection message carrying the first cause value from the second network, the terminal device should initiate access to a third network, where the network standard of the third network is lower than that of the second network;
  • the terminal device In response to receiving the first mobility update reject message carrying the first cause value from the second network, the terminal device sends a first initial registration request to the second network, where the first initial registration request is used to request attachment to the second network.
  • the terminal device can attempt to access the second network by initiating an initial registration process when receiving a rejection message with the first cause value, thereby preventing the terminal from residing on the third network according to the existing standard protocol, which in turn causes the terminal to be unable to return to the high-standard network for a long time.
  • the method further includes: receiving a first initial registration success message, the first initial registration success message indicating that the terminal is successfully attached to the second network.
  • the method further includes: receiving a first initial registration success message, the first initial registration success message indicating that the terminal is successfully attached to the second network.
  • the first indication message includes: a network redirection message indicating that the terminal device is redirected to the second network.
  • a network switching indication indicating that the terminal device switches to reside in the second network.
  • This example provides two different possibilities of the first indication message. It is understandable that in other embodiments, the network can also indicate that the terminal changes to reside in the second network in other forms. This application is not limited to this.
  • the first cause value includes #111.
  • Existing standard protocols such as 3GPP protocol 24.301 (specifically: 3GPP TS 24.301 V18.4.0 (2023-09)) stipulate the following:
  • the UE should set the tracking area updating attempt counter to 5.
  • the UE may disable the E-UTRA capability as specified in clause 4.5. If No E-UTRA Disabling In 5GS i s enabled at the UE(see 3GPP TS 24.368[50]or 3GPP TS 31.102[17])and the UE selects NG-RAN radio access technology,it shall not disable the E-UTRA capability; otherwise, the UE may disable the E-UTRA capability as specified in clause 4.5.
  • a terminal receives an original signal from a 4G network
  • the terminal After receiving the rejection message with the value #111, the terminal will try to access a network with a lower standard than the 4G network (such as a 3G network, etc.) to reside.
  • the terminal will also configure the 4G network to be disabled. If the existing protocol is followed, the terminal will reside in the 2G or 3G network for a long time, resulting in poor communication quality. In some cases, the terminal receives the rejection message #111 often due to temporary failures within the network, and these temporary failures will be quickly repaired.
  • the terminal can reside in the 4G network, but because the terminal simply executes the process specified by the protocol for #111 according to the existing protocol, the communication quality is reduced. Based on the implementation of each solution provided in the embodiment of the present application, the above problems can be solved.
  • the method before sending the first initial registration request, further includes: converting the cause value of the first mobility update rejection message from the first cause value to a second cause value, wherein the standard protocol stipulates that: in response to receiving the first mobility update rejection message carrying the second cause value from the second network, the terminal device should send the first initial registration request to the second network device.
  • the standard protocol stipulates that: in response to receiving the first mobility update rejection message carrying the second cause value from the second network, the terminal device should send the first initial registration request to the second network device.
  • the second reason value includes #9, or #10, or #40.
  • the terminal device sending a first initial registration request to the second network includes:
  • the terminal device In response to receiving the first mobility update reject message carrying the first cause value from the second network, when the terminal device is not currently in a call, the terminal device sends a first initial registration request to the second network.
  • the method before converting the cause value of the first TAU rejection message into a second value, the method also includes: determining that the terminal device is not currently in a call.
  • the terminal needs to ensure that the IP address remains unchanged for calls on high-standard networks (such as 5G networks and 4G networks).
  • the network may configure a new IP address for the terminal, which will cause the call to be interrupted. Therefore, in this example, if the terminal supports the call function, it can be determined whether it is in a call before initiating the initial registration process, and then the initial registration process can be executed for network access when it is not in a call. This avoids the problem of successful network access but interrupted calls.
  • the first initial registration request includes: Attach Request. That is, the first initial registration request is used to attach to the second network (or second network device).
  • the initial registration process may include an attachment process.
  • the first TAU request includes: TAU Request.
  • the first TAU rejection message includes: TAU reject.
  • the method further includes: in response to receiving the first mobility update reject message carrying the first cause value from the second network, when the terminal device is currently in a call, the terminal device sends a third mobility update request to the second network.
  • the method further includes: sending a second mobility update request, where the second mobility update request is used to initiate a mobility update process to the second network device to facilitate access to the second network.
  • the terminal may attempt to initiate a mobility update flow multiple times after receiving the first indication message. Procedure.
  • the method further includes: receiving a second mobility update reject message, wherein the second mobility update reject message indicates that the second network device rejects the terminal from accessing the second network, wherein the cause value of the second mobility update reject message is the first cause value.
  • the second network is an LTE network (i.e., a 4G network);
  • the first/second/third mobility update request includes: TAU Request;
  • the first/second/third mobility update rejection message includes: TAU reject; or,
  • the second network is an NR network (i.e., a 5G network);
  • the first/second/third mobility update request includes: a registration request with a registration type of MRU;
  • the first/second/third mobility update rejection message includes: a registration rejection message with a registration type of MRU.
  • the UE can send a registration request with a registration type of MRU (mobility registration updating) to implement mobility registration updating.
  • a registration type of MRU mobility registration updating
  • the first/second/third mobility update request is used to initiate a mobility update process to the second network device to facilitate access to the second network.
  • the method further includes:
  • the sending the first mobility update request comprises:
  • the first mobility update request is sent.
  • the method before sending the first mobility update request, further includes: converting the cause value of the second mobility update rejection message into a third cause value.
  • the third cause value corresponds to the terminal sending the first mobility update request to the second network device.
  • the sending of the second mobility update request and the receiving of the second mobility update rejection message may correspond to the terminal performing a mobility update procedure to attempt to access the second network.
  • the terminal may convert the cause value of the mobility update rejection message into a third cause value when receiving the mobility update rejection message for the first time, thereby allowing the terminal to attempt to perform the mobility update procedure to access the second network multiple times.
  • the third reason value includes #17.
  • 3GPP protocol 24.301 stipulates the following:
  • the UE shall proceed as follows:
  • Timer T3430 shall be stopped if still running.
  • the tracking area updating attempt counter shall be incremented,unless it was already set to 5.
  • the first duration is less than 10 seconds.
  • the terminal can flexibly configure the waiting time for initiating the mobility update process again.
  • the terminal can initiate the mobility update process faster.
  • the method further includes: starting a first counter, the first counter being configured with a first threshold.
  • the method further includes: configuring the value of the first timer to be increased by 1.
  • the method before converting the cause value of the second mobility update reject message into a third cause value, the method further includes: determining that the value of the first counter is less than the first threshold.
  • the first threshold is less than 5.
  • the terminal can flexibly configure the number of times the mobility update process is initiated again.
  • the first network is a 5G network
  • the second network is a 4G network
  • the third network is a 3G or 2G network.
  • the first network is a 6G network
  • the second network is a 4G network or a 5G network
  • the third network is a 3G or 2G network.
  • the present application further provides an electronic device, which may also be referred to as a terminal device.
  • the electronic device includes: a memory and one or more processors.
  • the memory and the processor are coupled.
  • the memory is used to store computer program code, and the computer program code includes computer instructions.
  • the processor executes the computer instructions, the electronic device executes the technical solution provided in the above-mentioned first aspect and any possible implementation thereof.
  • the present application also provides a chip system, which is applied to electronic devices;
  • the chip system may include one or more interface circuits and one or more processors.
  • the interface circuit and the processor are interconnected by lines, and the interface circuit is used to receive a signal from the memory of the electronic device and send the signal to the processor, and the signal includes a computer instruction stored in the memory.
  • the processor executes the above-mentioned computer instructions
  • the electronic device executes the technical solution provided in the above-mentioned first aspect and any possible implementation thereof.
  • the chip system may include a Modem (baseband processor, or modulation and demodulation processor).
  • the present application also provides a computer-readable storage medium, including computer instructions.
  • the computer instructions When the computer instructions are executed on an electronic device, the electronic device executes the technical solution provided in the above-mentioned first aspect and any possible implementation thereof.
  • the present application also provides a computer program product, which, when executed on a computer, enables the computer to execute the technical solution provided in the above-mentioned first aspect and any possible implementation thereof.
  • FIG1 is a schematic diagram of a communication scenario
  • FIG2 is a schematic diagram of the composition of a network device
  • FIG3 is a schematic diagram of an interaction flow of a communication method
  • FIG4 is a schematic diagram of the percentage of reason values of rejection messages counted in the existing network
  • FIG5 is a schematic diagram of an interaction flow of a communication method
  • FIG6 is a schematic diagram of the composition of a terminal device provided in an embodiment of the present application.
  • FIG7 is a schematic diagram of an interaction flow of a communication method provided in an embodiment of the present application.
  • FIG8 is a schematic diagram of an interaction flow of a communication method provided in an embodiment of the present application.
  • FIG9 is a schematic diagram of an interaction flow of a communication method provided in an embodiment of the present application.
  • FIG10 is a schematic diagram of an interaction flow of a communication method provided in an embodiment of the present application.
  • FIG11 is a schematic diagram of the composition of an electronic device provided in an embodiment of the present application.
  • FIG12 is a schematic diagram of the composition of a chip system provided in an embodiment of the present application.
  • GSM global system for mobile communication
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • UMTS universal mobile telecommunication system
  • GPRS general packet radio service
  • the network corresponding to the LTE (or LTE-A) system is referred to as a 4G network, and the NR network is referred to as a 5G network. Others are similar and will not be described one by one.
  • UE User Equipment
  • terminal equipment terminal equipment
  • the current location of the terminal can be covered by 3G network, 4G network and 5G network at the same time.
  • the terminal can provide the user with the communication function of the 3G network by accessing the 3G network.
  • the terminal can also provide the user with the communication function of the 4G network by accessing the 4G network.
  • the terminal can also provide the user with the communication function of the 5G network by accessing the 5G network.
  • the terminal can prioritize access to 4G or 5G networks with higher data transmission rates to provide better communication services.
  • the dwell time on each network can be marked by parameters such as the dwell ratio (such as the 4G dwell ratio), and the dwell strategy of the terminal in each standard network can be optimized accordingly. This allows the terminal to stay longer on a higher standard network, thereby providing users with better communication functions.
  • the dwell ratio such as the 4G dwell ratio
  • a network of a certain standard may be constructed and initiated by corresponding network devices.
  • a 3G network may correspond to a 3G network device
  • a 4G network may correspond to a 4G network device
  • a 5G network may correspond to a 5G network device.
  • 3G network equipment may include 3G base stations, 3G core network equipment, etc.
  • a terminal accesses a 3G network, it may communicate uplink with the 3G core network equipment through the 3G base station, or the 3G core network equipment may communicate downlink with the terminal through the 3G base station.
  • 4G network equipment may include 4G base stations, 4G core network equipment, etc.
  • uplink communication can be performed with the 4G core network equipment through the 4G base station, or the 4G core network equipment can perform downlink communication with the terminal through the 4G base station.
  • 5G network equipment may include 5G base stations, 5G core network equipment, etc.
  • a terminal accesses a 5G network, it can communicate uplink with the 5G core network equipment through the 5G base station, or the 5G core network equipment can communicate downlink with the terminal through the 5G base station.
  • the 5G network equipment may instruct the terminal to switch to other networks.
  • the 5G network device may execute S301 to send an indication message 11 to the terminal.
  • the indication message 11 is used to instruct the terminal to change from the currently accessed 5G network to the 4G network.
  • the indication message 11 may specifically include a network redirection message (such as RRCConnectionRelease), or a network switching indication (such as HandoverCommand).
  • a network redirection message such as RRCConnectionRelease
  • a network switching indication such as HandoverCommand
  • the indication message 11 may carry information such as the standard identifier corresponding to the 4G network and the access frequency of the 4G network.
  • the terminal can try to access the 4G network according to the received indication message 11.
  • the terminal may execute S302 to send a mobility update request 12 to the 4G network device.
  • the mobility update request 12 may be sent by the terminal to the 4G core network device through the 4G base station after the terminal completes the establishment of the RRC connection with the 4G base station in the 4G network device.
  • the mobility update request 12 may include a Tracking Area Update (TAU) Request, i.e., a TAU Request.
  • the TAU Request may include information such as an identifier of the network to be accessed.
  • the terminal wants to access a 4G network, and correspondingly, the mobility update request 12 may include an identifier of the 4G network, such as an LTE field.
  • the 4G network device may determine that the terminal can reside in the current 4G network according to the mobility update request 12. Correspondingly, the 4G network device may send a mobility update acceptance message (such as TAU Accept) to the terminal.
  • a mobility update acceptance message such as TAU Accept
  • the terminal cannot Access to the current 4G network.
  • the 4G network device executes S303 to send a mobility update rejection message 13 to the terminal.
  • the mobility update reject message 13 received by the terminal may carry a reject cause value.
  • the mobility update reject message 13 may include a reject cause value of #111.
  • #111 is defined as protocol error, unspecified. That is, the reason value #111 corresponds to a protocol error, and the cause is unknown.
  • the existing protocol also stipulates the execution strategy of the terminal when the cause value is #111:
  • the UE may disable the E-UTRA capability.
  • the terminal may attempt to select GERAN, UTRAN or NG-RAN radio access technology.
  • the UE may disable E-UTRA functions.
  • GERAN and UTRAN radio technologies are also the aforementioned 2G/3G network technologies.
  • the terminal since the terminal is disconnected from the 5G network before executing S302 to attempt to access the 4G network, the terminal may no longer select the NG-RAN radio access technology to attempt to access the 5G network when receiving the mobility update rejection message 13 including the cause value #111. Correspondingly, the terminal may attempt to select GERAN, UTRAN to access the 2G or 3G network.
  • the terminal may execute S304 to initiate a registration request 14 to the 3G network device, and attempt to access the 3G network to reside therein.
  • the terminal When the terminal successfully registers to the 3G network, the terminal can complete the network change from 5G to 3G.
  • the E-UTRA function when the terminal attempts to access a 2G or 3G network, the E-UTRA function will be disabled, that is, the 4G network is configured to be disabled.
  • Figure 4 provides examples of 6 rejection reason values with a relatively large proportion.
  • the terminal can try to quickly re-resident in a higher-standard network, which can significantly and effectively improve the communication quality of the terminal.
  • the cause value may be converted from #111 to #17 so that the terminal can perform subsequent processing according to the processing strategy corresponding to #17 in the existing protocol.
  • the terminal can perform multiple (e.g., 5) attempts to register with the 4G network.
  • the terminal can be configured with more attempts to access the 4G network before staying in the 2G/3G network for a long time, thereby increasing the probability of accessing the 4G network.
  • the terminal and the network device perform S301- Take the interaction of S303 as an example.
  • the terminal may trigger the following steps: S401 , the terminal converts the rejection cause value to #17.
  • the terminal can perform subsequent processing according to the response strategy corresponding to the rejection reason value #17 as specified in the protocol.
  • the process may include:
  • S402 The terminal starts the T3411 timer and the counter C11.
  • the T3411 timer can provide a 10s timing function.
  • the counter C11 can be used to count subsequent message sending.
  • the terminal may trigger execution of S403 according to the expiration of the T3411 timer.
  • S403 The terminal sends a mobility update request 15 to the 4G network device.
  • the mobility update request 15 is similar to the mobility update request 12 sent in the aforementioned S302.
  • the mobility update request 15 may include a TAU Request.
  • a terminal when a terminal receives an access rejection message with a reason value of #17, it can send a TAU Request to the 4G network device again to try to access the 4G network again.
  • the terminal can wait for 10 seconds by initiating the T3411 timer before sending the TAU Request again. This prevents the terminal from immediately sending the TAU Request repeatedly to the 4G network device, thereby avoiding the problem that the mobility update request 15 is not responded to by the 4G network device.
  • the terminal may execute S402 - S403 multiple times to implement multiple attempts to access the 4G network device.
  • the terminal may record the number of access attempts to the 4G network device through the counter C11 started in S402. For example, after executing S403, the terminal may execute S404 to configure the counter C11 to add 1.
  • the terminal can jump to execute S304 shown in FIG3 and send a registration request 14 to the 3G network device, so that the terminal can ensure basic communication by residing on the 3G network.
  • the terminal may repeatedly execute S402 - S403 .
  • the terminal may receive a mobility update confirmation message 16 sent from the 4G network device.
  • the mobility update confirmation message 16 may include TAU Accept. That is, after one retry, the terminal can successfully access the 4G network.
  • the terminal in order to enable the 4G network device to normally respond to the TAU Request (such as the mobility update request 15) sent again, it is necessary to wait for the T3411 timer to expire before sending the TAU Request. Mobility update request 15. Then, even if the terminal accesses the 4G network after retrying the 4G network once as shown in FIG5 , the terminal will still have a communication interruption of at least 10 seconds.
  • the technical solution provided by the embodiment of the present application can prevent the terminal from staying in the 2G/3G network for a long time, compared with the existing solution shown in Figure 3.
  • the technical solution provided by the embodiment of the present application compared with the technical implementation shown in Figure 5, can enable the terminal to stay on the 4G network faster, reducing or eliminating the communication interruption problem before staying on the 4G network.
  • the terminal in the embodiment of the present application may include at least one of a mobile phone, a foldable electronic device, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) device, a virtual reality (VR) device, an artificial intelligence (AI) device, a wearable device, a vehicle-mounted device, a smart home device, or a smart city device.
  • PDA personal digital assistant
  • AR augmented reality
  • VR virtual reality
  • AI artificial intelligence
  • the embodiment of the present application does not impose any special restrictions on the specific type of the terminal.
  • FIG6 is a schematic diagram of the composition of a terminal provided in an embodiment of the present application.
  • the terminal may include a processor 610, an external memory interface 620, an internal memory 621, a universal serial bus (USB) connector 630, a charging management module 640, a power management module 641, a battery 642, an antenna 1, an antenna 2, a mobile communication module 650, a wireless communication module 660, an audio module 670, a sensor module 680, a camera module 693, a display screen 694, etc.
  • the sensor module 680 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, etc.
  • the processor 610 may include one or more processing units, for example, the processor 610 may include an application processor (application processor, AP), a modem processor (Modem), a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor (baseband processor, BP or BBP), and/or a neural-network processing unit (neural-network processing unit, NPU), etc.
  • different processing units may be independent devices or integrated into one or more processors.
  • a modem may be integrated into a baseband processor, etc.
  • the internal processing logic of the terminal can be implemented directly or indirectly by the baseband processor.
  • the processor 610 can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.
  • the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the terminal.
  • the terminal may include more or fewer components than those shown in FIG6, or combine certain components, or split certain components, or arrange the components differently.
  • the components shown in FIG6 may be implemented in hardware, software, or a combination of software and hardware.
  • the interaction between the terminal and the network device may include the interaction between the terminal and the core network device of the corresponding network.
  • the TAU process between the terminal and the network device (such as including sending a TAU request, etc.) may be the TAU process between the terminal and the core network device of the corresponding network.
  • the attachment process between the terminal and the network device (such as including sending an Attach request, etc.) may be the Attach process between the terminal and the core network device of the corresponding network.
  • the interaction between the terminal and the core network device can be achieved through the access network device of the corresponding network.
  • the interaction between the terminal and the 5G core network device can be achieved through message transparent transmission through the 5G base station.
  • the interaction between the terminal and the 4G core network device can be achieved through message transparent transmission through the 4G base station.
  • the interaction between the terminal and the 6G core network device can be achieved through message transparent transmission through the 6G base station.
  • Other networks are similar.
  • FIG7 a schematic diagram of an interaction process of a communication method provided in an embodiment of the present application is shown.
  • the scheme may include:
  • a terminal receives a first instruction message.
  • the first instruction message is used to instruct the terminal to re-resident on a network.
  • the first indication message may be sent to the terminal by a network device (such as network device 71) of the network to which the terminal is currently connected.
  • a network device such as network device 71
  • the first indication message is used to instruct the terminal to re-resident in a heterogeneous system network or a homogeneous system network.
  • re-residence in a different system network may include: switching/redirecting from a currently resided 5G network to a 4G network, or switching/redirecting from a currently resided 4G network to a 2G or 3G network, or switching/redirecting from a currently resided 6G network to a 5G or 4G or 3G network, etc.
  • Re-residence in the same system network may include: switching/redirecting from the currently resided 5G network to other 5G networks, or switching/redirecting from the currently resided 4G network to other 4G networks, or switching/redirecting from the currently resided 6G network to other 6G networks, etc.
  • the first indication message is used to instruct the terminal to re-resident on a heterogeneous system network.
  • the first indication message may include information indicating the target network where the terminal re-residents. For example, taking the first indication message indicating that the terminal re-residents in the 4G network as an example.
  • the first indication message includes information of the 4G network, such as a network identifier of the 4G network (such as an LTE field) and/or an access frequency of the 4G network.
  • S702 The terminal sends a first mobility update request.
  • the first mobility update request may include a TAU Request.
  • the first mobility update request may include an identifier of a network to which the network device 72 belongs.
  • the identifier of the network to which the network device 72 belongs may be an identifier of a 4G network, such as LTE.
  • the first mobility update request may be sent by the terminal to the network device (such as network device 72) indicating re-resident according to the first indication message.
  • the network device such as network device 72
  • the first mobility update request may be used to request access to a network corresponding to the network device 72 .
  • S703 The terminal receives a first mobility update reject message.
  • the first mobility update reject message may include TAU Reject.
  • the first mobility update rejection message may be sent by the network device 72 to the terminal.
  • the first mobility update rejection message may include a reason value for rejecting this network access.
  • the cause value of the first mobility update reject message may be #111.
  • S704 The terminal sends a first initial registration request.
  • the first initial registration request may include an Attach Request.
  • the first initial registration request may be used to initiate an initial registration with the network corresponding to the network device 72.
  • the terminal can access the network corresponding to the current location through initial registration.
  • the terminal can initiate initial registration with the network corresponding to the network device 72 after receiving the first mobility update rejection message with the cause value #111.
  • the Attach Request may include the International Mobile Equipment Identity (IMSI) of the current terminal, the current location identifier of the terminal (such as the TAI identifier), capability information supported by the terminal (such as frequency band information supported by the terminal, etc.), etc.
  • IMSI International Mobile Equipment Identity
  • the current location identifier of the terminal such as the TAI identifier
  • capability information supported by the terminal such as frequency band information supported by the terminal, etc.
  • the TAU process and the Attach process are two independent interactive processes, even if the TAU process fails, the Attach process may still successfully access the network.
  • the terminal when the terminal receives the first mobility update request with the cause value #111 (ie, the TAU process fails), it can initiate the Attach process again and try to access the network corresponding to the network device 72 again.
  • the terminal may execute S705 : the terminal receives a first initial registration success message.
  • the first initial registration success message may include Attach Accept.
  • the first initial registration success message is used to indicate that the terminal has successfully attached/accessed the network corresponding to the network device 72.
  • the terminal successfully accesses the network corresponding to the network device 72, the network standard will not continue to drop.
  • the terminal may be configured to implement various different implementations, so that after receiving the first mobility update reject message with the cause value #111 in S703 , S704 is triggered.
  • the terminal may replace the reason value #111 with other reason values (such as #9, #10 or #40, etc.), so that the terminal triggers S704 based on the replaced reason value according to existing protocol provisions.
  • other reason values such as #9, #10 or #40, etc.
  • the terminal after receiving the first mobility update reject message with cause value #111, the terminal may be configured to trigger execution of S704.
  • the terminal triggers S704 by replacing the cause value as an example.
  • the terminal when the solution shown in FIG. 7 is applied to the scenario shown in FIG. 1 , compared with the processing mechanism in the existing solution shown in FIG. 3 , the terminal will not fall to 2G or 3G and disable the 4G network after receiving a rejection message with a reason value of #111. Accordingly, the terminal can be implemented based on the solution shown in FIG. 7 , and after receiving a rejection message with a reason value of #111, it can try to access the 4G network again through the Attach process. This increases the probability that the terminal continues to reside in the 4G network.
  • the terminal can trigger the execution of S704 to send the first initial registration request to the network device 72. Since the Attach process corresponding to the first initial registration request is different from the TAU process corresponding to the first mobility update request, the terminal does not need to wait and can directly send the first initial registration request. This can also avoid communication interruption within the duration (eg, 10 seconds) of the T3411 timer in the solution shown in FIG. 6 .
  • the network device 71 may be a 5G network device
  • the network device 72 may be a 4G network device.
  • the solution may include:
  • the terminal receives an indication message 11.
  • the execution of this step may refer to S301 shown in FIG3 or S701 shown in FIG7 .
  • the indication message 11 may correspond to the first indication message shown in FIG7 .
  • the first indication message may be sent by a 5G network device of the currently accessed 5G network (such as a core network device in the 5G network device), and is used to instruct the terminal to switch/redirect from the 5G network to the 4G network.
  • a 5G network device of the currently accessed 5G network such as a core network device in the 5G network device
  • the terminal sends a mobility update request 12 to the 4G network device.
  • the execution of this step may refer to S302 shown in FIG3 or S702 shown in FIG7 .
  • the mobility update request 12 may correspond to the first mobility update request shown in FIG7 .
  • the mobility update request 12 may include a TAU Request.
  • the mobility update request 12 may be used to attempt to access a 4G network.
  • the execution of this step may refer to S303 shown in FIG3 or S703 shown in FIG7 .
  • the mobility update reject message 13 may correspond to the first mobility update reject message shown in FIG7 .
  • the mobility update reject message 13 may include TAU Reject.
  • the reason value of the mobility update reject message 13 may be #111, i.e., protocol error, unspecified.
  • the terminal may trigger the execution of S804 according to the reason value of the rejection message being #111.
  • cause value #9 is also one of the multiple cause values specified in the existing protocol.
  • the terminal after receiving a rejection message with a reason value of #9, the terminal can trigger the execution of the initial registration process, that is, the Attach process.
  • the terminal may convert the rejection reason value from #111 to other reason values.
  • the reason value replacing #111 may be: a reason value that triggers the execution of the initial registration process according to the existing protocol.
  • the terminal may convert the rejection reason value from #111 to #10 or #40, etc.
  • the terminal can perform subsequent operations according to the received mobility update reject message with reason value #9 and in accordance with the existing protocol.
  • the terminal sends an initial registration request 17 to the 4G network device.
  • the execution of this step may refer to S704 shown in FIG7 .
  • the initial registration request 17 may correspond to the first initial registration request shown in FIG7 .
  • the initial registration request 17 may include an Attach Request.
  • the terminal triggers the execution of the initial registration process according to the reason value #9.
  • the initial registration process may correspond to the Attach registration process or be called the Attach process.
  • the terminal may execute S805 to send an initial registration request 17 to the 4G network device.
  • the initial registration request 17 may be used to request attachment to the 4G network device for communication.
  • the terminal receives an initial registration success message 18.
  • the initial registration success message 18 may be sent by a 4G network device.
  • the execution of this step may refer to S705 shown in FIG7 .
  • the initial registration success message 18 may correspond to the first initial registration success message shown in FIG7 .
  • the initial registration success message 18 may include Attach Accept.
  • the terminal can complete the Attach process to the 4G network device based on the received initial registration success message 18.
  • the terminal can also complete the communication with the 4G network device based on the Attach process, and then provide the user with the communication service of the 4G network.
  • the terminal after receiving the mobility update rejection message 13, the terminal triggers the initial registration process to the 4G network by converting the cause value and registers successfully. In this process, the terminal does not need to wait, so that access to the 4G network can be quickly achieved. Correspondingly, the terminal will not be configured to disable 4G due to network rejection with a cause value of #111, and thus stay on the low-standard 2G/3G network for a long time.
  • the solution example shown in Figure 8 provides a specific implementation of the solution shown in Figure 7. In other embodiments of the present application, the solution shown in Figure 7 may also include other implementations.
  • FIG9 is a schematic diagram of an interaction flow of another communication method provided in an embodiment of the present application.
  • the interaction between the network elements can be expanded and obtained in combination with the example of FIG. 8 .
  • the execution process of S801 - S806 may refer to the example shown in FIG. 8 , and the details are not repeated here.
  • the terminal may execute S901. Specifically:
  • the terminal determines whether it is in a call.
  • the terminal is in a call, that is, the terminal is making a voice call.
  • the voice call may include a VoNR call based on the currently resident 5G network.
  • the voice call may include a VoLTE call based on the currently resident 4G network.
  • the voice call of the terminal can be realized based on a fixed IP.
  • the fixed IP of the terminal can be assigned to the terminal by the network device during the registration (such as initial registration) with the current resident network device.
  • the terminal After the terminal is turned on, it can receive the IP address configured by the 5G network device for the terminal during the initial registration process with the current 5G network. After that, the terminal can make a VoNR call in the 5G network based on the IP address. Correspondingly, if the IP address changes during the terminal call, the VoNR call will be disconnected.
  • the terminal triggers the execution of the initial registration process according to the converted reason value #9.
  • the 4G network device may configure a new IP address for the terminal. This may cause the current call to be disconnected.
  • the terminal can execute S804 corresponding to converting the rejection reason value to #9 before executing S901 to determine whether the call is currently in progress.
  • the terminal If the terminal is currently in a call, in order to avoid abnormal disconnection of the call, the terminal jumps to execute S902.
  • the terminal converts the rejection reason value to #17.
  • this step may refer to the description of S401 in FIG. 5 .
  • the terminal can no longer use the initial registration process to access the 4G network during the call to avoid abnormal call disconnection caused by this. Conversely, the terminal can convert the rejection reason value to #17 to trigger the TAU process again and try to access the 4G network.
  • the terminal can try to access the 4G network through the TAU process while maintaining the call.
  • the terminal may be pre-configured with a timer 91 and a counter C12.
  • the timer 91 can be configured with a timing duration according to specific circumstances.
  • the timing duration of the timer 91 can be less than the timing duration of the T3411 timer.
  • the timing duration of the timer 91 can be less than 10s.
  • the initial value of the counter C12 is 0.
  • the terminal may configure a corresponding threshold m for the counter C12 according to specific circumstances.
  • m may be an integer less than 5.
  • m may be configured as 1.
  • the timer 91 is different from the T3411 timer specified in the existing protocol shown in FIG5 .
  • the counter C12 is also different from the counter C11 specified in the existing protocol shown in FIG5 .
  • the terminal may start timer 91 and counter C12 according to S903.
  • the terminal may also start timer T3411 and counter C11 according to an existing protocol.
  • the terminal may wait for 1 second until timer 91 expires, triggering execution of S904.
  • timer 91 since the timing duration of timer 91 is less than 10s corresponding to timer T3411, timer 91 must end before timer T3411, and the terminal is triggered to execute S904 accordingly.
  • the terminal may start timer 91 and counter C12 according to S903.
  • the terminal may be configured not to start timer T3411 and counter C11.
  • S904 The terminal sends a mobility update request 19.
  • the mobility update request 19 may correspond to the mobility update request 15 as shown in FIG. 5 .
  • the terminal may try to access the 4G network device again through a mobility update request 19.
  • the mobility update request 19 may be the same as the mobility update request 12.
  • the terminal configuration counter C12 is incremented by 1.
  • the terminal can start the counter C12. Then correspondingly, after starting the counter C12, each time the terminal sends a mobility update request (TAU Request), the terminal configuration counter C12 is incremented by 1. Therefore, the value of the counter C12 can be used to indicate the number of times the TAU is repeated.
  • the counter C11 is started as an example.
  • the terminal configures the counter C12 to increase by 1, and can also configure the counter C11 to increase by 1.
  • the 4G network device After the 4G network device receives the mobility request 19, it sends a mobility update rejection message 20 to the terminal. That is, the terminal fails to make a TAU request.
  • the mobility update reject message 20 may include TAU Reject.
  • the reason value of the mobility update reject message 20 may include #111.
  • the terminal may receive a mobility update confirmation message (such as TAU Accept) from the 4G network device after executing S904. In this way, the terminal successfully accesses the 4G network and correspondingly jumps out of the process shown in FIG. 9 .
  • a mobility update confirmation message such as TAU Accept
  • the following takes the case where the terminal receives a mobility update rejection message 20 after sending a mobility update request 19 as an example.
  • S907 The terminal determines whether the value of the counter C12 reaches m.
  • m may be a threshold value corresponding to the counter C12.
  • the terminal may determine that a mobility update reject message (such as mobility update reject message 20) is received before executing S907. As a possible implementation, the terminal may determine that a mobility update reject message is received based on receiving a TAU Reject after sending a TAU Request.
  • a mobility update reject message such as mobility update reject message 20
  • the terminal may read the value of the counter C12 to determine whether the current value of the counter C12 reaches m.
  • m may be less than 5.
  • the terminal may jump to execute S908 after failing the TAU process for a maximum of 4 times (for example, m is configured as 4).
  • the terminal can control the number of times the TAU process is repeated to attempt to access the 4G network according to the configured threshold m, thereby avoiding problems such as excessive power consumption and time consumption caused by excessive attempts to access the 4G network.
  • the terminal sends a registration request 21.
  • the terminal may send a registration request 21 to the 3G network device.
  • the terminal may try to access by lowering the standard to ensure that the terminal can provide the most basic communication function.
  • the terminal determines whether the call is in progress. That is, the solution shown in FIG. 9 can be applied to a terminal with a call function. middle.
  • the terminal may execute S803 and no longer execute S901 , but directly jump to execute S804 .
  • processing strategy A the TAU process is performed again to try to access the 4G network by converting the rejection reason value to #17.
  • processing strategy B is referred to as processing strategy
  • processing strategy A is triggered first. If it is determined in processing strategy A that the terminal is in a call, processing strategy B is triggered.
  • the terminal may also trigger the execution of processing strategy A after processing strategy B.
  • FIG10 is a schematic diagram of an interaction flow of another communication method provided in an embodiment of the present application.
  • the terminal can implement steps S801-S803 through interaction with network devices (such as 5G network devices, 4G network devices, etc.).
  • network devices such as 5G network devices, 4G network devices, etc.
  • the terminal may trigger the execution of processing strategy B according to receiving the mobility update rejection message 13 with the cause value #111.
  • the terminal may sequentially execute S902, S903, S904, S905, S906, and S907.
  • the specific implementation of each step can refer to the description in FIG9, which will not be repeated here.
  • the terminal can attempt the TAU process within a preset number of times (such as m times) to increase the probability of re-accessing the 4G network through the TAU process.
  • a preset number of times such as m times
  • the processing strategy B can be used to pass the TAU process as soon as possible after the temporary failure of the 4G network device is repaired, so that the terminal can access the 4G network for communication.
  • the example of the failure of m TAU processes performed by processing strategy B is used for explanation.
  • a successful TAU process such as the terminal receiving a TAU Accept reply from the 4G network
  • the process shown in FIG. 10 is correspondingly jumped out, that is, the terminal can communicate normally on the connected 4G network.
  • processing strategy B fails to enable the terminal to access the 4G network, it means that the terminal fails in all attempts to reconnect to the 4G network through the TAU process m times, and processing strategy A is triggered.
  • the terminal may continue to execute S901 when the value of the counter C12 reaches m.
  • the terminal can execute steps S804, S805, S806, etc. according to the fact that the terminal is not currently in a call (e.g., the terminal is not currently performing a call service but performing a data service).
  • the terminal can execute S908 according to the fact that the terminal is currently in a call.
  • the terminal may attempt to perform multiple TAU processes to the 4G network after receiving a rejection message with a reason value of #111 in reply from the 4G network. If a TAU process is successful, the terminal can communicate normally on the 4G network. If multiple TAU processes all fail (such as initiating multiple TAU requests and receiving rejection messages with a reason value of #111), the terminal may initiate an initial registration with the 4G network (for example, after receiving a rejection message with a reason value of #111 in reply from the 4G network, the terminal may perform an initial registration process with the network in accordance with the processing strategy for receiving a rejection message with a reason value of #9 in reply from a certain network as specified in the existing protocol).
  • the terminal after receiving the rejection message #111, the terminal can trigger the processing strategy B and the processing strategy A in sequence, so that the terminal can trigger the initial registration process, combined with the TAU registration process, to achieve rapid access to the 4G network.
  • the implementation of the solution provided in the embodiments of the present application is described by taking the case where the terminal resides in the 5G network, changes to reside in the 4G network under the instruction of the network device, and receives a rejection message of TAU Reject carrying the reason value #111 as an example.
  • the technical solutions provided in the embodiments of the present application can be applied to other scenarios.
  • the terminal resides in a 6G network and changes to reside in a 5G network or a 4G network under the instruction of the network device.
  • the terminal can initiate a TAU process for the 5G network or the 4G network accordingly.
  • the terminal After receiving a rejection message of TAU Reject carrying the reason value #111, the terminal can quickly access the 5G network or the 4G network according to any of the solutions provided in the embodiments of the present application.
  • the terminal resides in the 3G network and changes to reside in the 4G network or 5G network under the instruction of the network device.
  • the terminal can send the TAU process of the 4G network or 5G network accordingly.
  • the terminal After receiving the rejection message of TAU Reject carrying the reason value #111, the terminal can quickly access the 4G network or 5G network according to any of the solutions provided in the embodiments of the present application.
  • the terminal resides in a 5G network and changes to reside in another 5G network under the instruction of the network device.
  • the terminal can initiate a TAU process to the new 5G network accordingly.
  • the terminal can implement any of the solutions provided in the embodiments of the present application, and quickly access the new 5G network again through the initial registration process (such as the above-mentioned processing strategy A), or the initial registration and TAU process (such as the above-mentioned processing strategy A and processing strategy B).
  • the electronic device provided in the embodiment of the present application includes a hardware structure and/or software module corresponding to each function in order to realize the above functions.
  • the embodiment of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the embodiment of the present application.
  • the embodiment of the present application can divide the functional modules of the above-mentioned electronic device according to the above-mentioned method example.
  • each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module.
  • the above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional 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. There may be other division methods in actual implementation.
  • Fig. 11 shows a schematic diagram of the composition of an electronic device 1100.
  • the electronic device 1100 may correspond to the terminal in any of the above embodiments.
  • the electronic device 1100 may include: a processor 1101 and a memory 1102.
  • the memory 1102 is used to store computer-executable instructions.
  • the processor 1101 executes the instructions stored in the memory 1102
  • the electronic device 1100 may execute any of the methods shown in the above embodiments.
  • FIG12 shows a schematic diagram of the composition of a chip system 1200.
  • the chip system 1200 may include: a processor 1201 and a communication interface 1202, which are used to support related devices (such as terminals) to implement the functions involved in the above embodiments.
  • the chip system also includes a memory for storing program instructions and data necessary for the terminal.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the communication interface 1202 may also be referred to as an interface circuit.
  • the functions or actions or operations or steps in the above embodiments can be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • a software program When implemented using a software program, it can 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. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that can be integrated with one or more media.
  • the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.
  • a magnetic medium e.g., a floppy disk, a hard disk, a magnetic tape
  • an optical medium e.g., a DVD
  • a semiconductor medium e.g., a solid state disk (SSD)

Landscapes

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

Abstract

本申请实施例提供一种通信方法和终端设备，涉及电子设备技术领域。该方法可以应用于电子设备，能够使得终端快速实现对高制式网络的接入，避免驻留到低制式的网络中。该方法可以包括：终端设备驻留在第一网络，方法包括：接收第一指示消息。发送第一移动性更新TAU请求。接收第一TAU拒绝消息，第一TAU拒绝消息表示第二网络的第二网络设备拒绝终端接入第二网络。其中，第一TAU拒绝消息的原因值为第一原因值。第一原因值对应于，终端向第三网络发起接入，第三网络的网络制式低于第二网络。发送第一初始注册请求，第一初始注册请求用于请求附着在第二网络。

Description

一种通信方法和终端设备
本申请要求于2023年11月30日提交国家知识产权局、申请号为202311641684.9、发明名称为“一种通信方法和终端设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及电子设备技术领域，尤其涉及一种通信方法和终端设备。
背景技术
终端设备(简称为终端)可以与不同制式的网络进行通信，实现通信功能。其中，不同制式的网络可以包括3G网络、4G网络、或5G网络等。
以终端驻留在5G网络为例。在5G网络通信质量下降时，网络侧可以指示终端变更驻留到4G网络进行通信。终端可以根据网络侧的指示，尝试变更驻留到4G网络。例如，终端可以向4G网络设备发送移动性更新请求如TAU(Tracking Area Update,跟踪区域更新)请求，以便尝试接入到4G网络进行通信。在4G网络设备确认当前终端不可接入4G网络的情况下，可以向终端发送TAU Reject的拒绝消息。在该拒绝消息中可以携带对应的原因值。例如，该原因值可以包括#111，该原因值表示由于不可知原因，网络拒绝终端接入。
按照现有的标准协议如3GPP协议24.301(具体如：3GPP TS 24.301 V18.4.0(2023-09))的规定，终端会根据接收到来自4G网络的原因值为#111的拒绝消息，尝试接入到比4G网络更低制式的网络(如3G网络等)驻留。同时，终端还会将4G网络配置为禁用(disable)。
这样就会导致终端长时间驻留在较低制式的网络(如3G网络、或2G网络等)，无法快速回到4G网络提供较好的通信服务。
发明内容
本申请一些实施例提供了一种通信方法和终端设备，能够使得终端在接收到原因值为#111的拒绝消息后，快速实现对高制式网络(如4G网络)的接入，避免长时间驻留在低制式的网络中。
第一方面，提供了一种通信方法，应用于终端设备，该方法包括：
所述终端设备驻留在第一网络；
所述终端设备接收所述第一网络发送的第一指示消息，所述第一指示消息包括第二网络的标识和/或第二网络的接入频点，所述第一指示消息用于指示所述终端设备接入到所述第二网络；
所述终端设备向所述第二网络发送第一移动性更新请求，所述第一移动性更新请求包括所述第二网络的标识；
所述终端设备接收来自所述第二网络的第一移动性更新拒绝消息，所述第一移动性更新拒绝消息表示所述第二网络的第二网络设备拒绝所述终端接入所述第二网络，其中，所述第一移动性更新拒绝消息中携带的拒绝原因值为第一原因值，其中，在标 准协议中规定了：所述终端设备响应于接收到来自所述第二网络的所述携带所述第一原因值的所述第一移动性更新拒绝消息，所述终端设备应向第三网络发起接入，所述第三网络的网络制式低于所述第二网络；
响应于接收到来自所述第二网络的所述携带所述第一原因值的所述第一移动性更新拒绝消息，所述终端设备向所述第二网络发送第一初始注册请求，所述第一初始注册请求用于请求附着在所述第二网络。
这样，终端设备可以在接收到第一原因值的拒绝消息的情况下，通过发起初始注册流程，尝试接入到第二网络中。由此避免终端根据现有的标准协议驻留到第三网络，进而导致终端长时间无法重新回到高制式网络。
可选的，该方法还包括：接收第一初始注册成功消息，该第一初始注册成功消息表示该终端成功附着在该第二网络。这样，通过触发初始注册流程，实现向第二网络的成功接入。进而避免长时间驻留在第三网络导致的通信质量差的问题。
可选的，该第一指示消息包括：指示该终端设备重定向到该第二网络的网络重定向消息。或者，指示该终端设备切换驻留到该第二网络的网络切换指示。该示例提供了两种不同的第一指示消息的可能。可以理解的是，在另一些实施例中，网络还可以通过其他形式指示终端变更驻留到第二网络。本申请对此不作限定。
可选的，该第一原因值包括#111。现有的标准协议如3GPP协议24.301(具体如：3GPP TS 24.301 V18.4.0(2023-09))中规定了如下内容：
#111:protocol error,unspecified.
……
d)TRACKING AREA UPDATE REJECT,other causes than those treated in clause 5.5.3.2.5,and cases of EMM cause values#22,#25,#31 and#78,if considered as abnormal cases according to clause 5.5.3.2.5
If the tracking area updating request is not for initiating a PDN connection for emergency bearer services,upon reception of the EMM causes #95,#96,#97,#99 and #111 the UE should set the tracking area updating attempt counter to 5.
……
If the tracking area updating attempt counter is equal to 5:
……
-attempt to select GERAN,UTRAN or NG-RAN radio access technology.Additionally,if the UE selects GERAN or UTRAN radio access technology,the UE may disable the E-UTRA capability as specified in clause 4.5.If No E-UTRA Disabling In 5GS is enabled at the UE(see 3GPP TS 24.368[50]or 3GPP TS 31.102[17])and the UE selects NG-RAN radio access technology,it shall not disable the E-UTRA capability；otherwise,the UE may disable the E-UTRA capability as specified in clause 4.5.
本领域技术人员基于上述现有协议的规定可知，终端在接收到来自4G网络的原 因值为#111的拒绝消息后，会尝试接入到比4G网络更低制式的网络(如3G网络等)驻留，同时，终端还会将4G网络配置为禁用(disable)。如果按照现有协议，就会使得终端长时间驻留在2G或3G网络，进而导致通信质量差。而在一些情况下，终端接收到#111的拒绝消息往往是由于网络内部的临时故障导致，而这些临时故障会被快速修复。因此，实际上终端是可以驻留在4G网络的，但是由于终端简单地按照现有的协议执行对#111的协议规定的流程，导致通信质量的下降。基于本申请实施例提供的各个方案实现，就可以解决上述问题。
可选的，在该发送第一初始注册请求之前，该方法还包括：将所述第一移动性更新拒绝消息的原因值由所述第一原因值转换为第二原因值，其中，在标准协议中规定了：所述终端设备响应于接收到来自所述第二网络的所述携带所述第二原因值的所述第一移动性更新拒绝消息，所述终端设备应向所述第二网络设备发送所述第一初始注册请求。由此提供了一种可能的实现，使得终端可以按照协议规定的第二原因值的响应逻辑，尝试通过初始注册流程，向第二网络发起接入。
可选的，该第二原因值包括#9，或者#10，或者#40。
在一种实现方式中，所述响应于接收到来自所述第二网络的所述携带所述第一原因值的所述第一移动性更新拒绝消息，所述终端设备向所述第二网络发送第一初始注册请求，包括：
响应于接收到来自所述第二网络的所述携带所述第一原因值的所述第一移动性更新拒绝消息，在所述终端设备当前不在通话中的情况下，所述终端设备向所述第二网络发送第一初始注册请求。
可选的，在将该第一TAU拒绝消息的原因值转换为第二值之前，该方法还包括：确定该终端设备当前不在通话中。
在现网环境中，终端在高制式网络(如5G网络、4G网络)的通话都需要保证IP地址固定不变。而在本申请中，通过初始注册流程，网络可能会向终端配置新的IP地址，这样就会导致通话的中断。因此，在本示例中，在终端支持通话功能的情况下，可以在发起初始注册流程之前，判断是否处于通话中，进而在不处于通话中的情况下执行初始注册流程进行网络接入。由此避免网络接入成功，但是通话中断的问题出现。
可选的，该第一初始注册请求包括：Attach Request。也即，该第一初始注册请求用于附着在第二网络(或第二网络设备)上。该初始注册流程可以包括附着流程。
可选的，该第一TAU请求包括：TAU Request。该第一TAU拒绝消息包括：TAU reject。
在一种实现方式中，所述方法还包括：响应于接收到来自所述第二网络的所述携带所述第一原因值的所述第一移动性更新拒绝消息，在所述终端设备当前在通话中的情况下，所述终端设备向所述第二网络发送第三移动性更新请求。
可选的，在接收第一指示消息之后，发送第一移动性更新请求之前，该方法还包括：发送第二移动性更新请求，该第二移动性更新请求用于向该第二网络设备发起移动性更新流程，以便于接入到该第二网络。
在该示例中，终端可以在接收到第一指示消息之后，多次尝试发起移动性更新流 程。
可选的，该方法还包括：接收第二移动性更新拒绝消息，该第二移动性更新拒绝消息表示该第二网络设备拒绝该终端接入该第二网络。其中，该第二移动性更新拒绝消息的原因值为该第一原因值。
在一种实现方式中，所述第二网络为LTE网络(即4G网络)；所述第一/第二/第三移动性更新请求包括：TAU Request；所述第一/第二/第三移动性更新拒绝消息包括：TAU reject；或者，
所述第二网络为NR网络(即5G网络)；所述第一/第二/第三移动性更新请求包括：注册类型为MRU的注册请求；所述第一/第二/第三移动性更新拒绝消息包括：注册类型为MRU的注册拒绝消息。
UE可以发送注册类型为MRU(mobility registration updating，移动性注册更新)的注册请求，实现移动性注册更新。
在一种实现方式中，所述第一/第二/第三移动性更新请求用于向该第二网络设备发起移动性更新流程，以便于接入到该第二网络。
可选的，在接收到所述第二移动性更新拒绝消息之后，所述方法还包括：
启动第一定时器，所述第一定时器的时长为第一时长；
所述发送所述第一移动性更新请求，包括：
在所述第一定时器计时结束后，发送所述第一移动性更新请求。
可选的，在该发送第一移动性更新请求之前，该方法还包括：将该第二移动性更新拒绝消息的原因值转换为第三原因值。该第三原因值对应于，该终端向该第二网络设备发送所述第一移动性更新请求。
该第二移动性更新请求的发送和第二移动性更新拒绝消息的接收，可以对应到终端执行一次移动性更新流程尝试接入第二网络。在该示例中，终端可以在第一次接收到移动性更新拒绝消息的情况下，将该移动性更新拒绝消息的原因值转换为第三原因值，进而使得终端可以多次尝试进行移动性更新流程接入第二网络。
可选的，该第三原因值包括#17。
现有的标准协议如3GPP协议24.301(具体如：3GPP TS 24.301 V18.4.0(2023-09))中规定了如下内容：
#17:Network failure
……
d)TRACKING AREA UPDATE REJECT,other causes than those treated in clause 5.5.3.2.5,and cases of EMM cause values#22,#25,#31 and#78,if considered as abnormal cases according to clause 5.5.3.2.5
For the cases b,c,d,k,ka,l and la,the UE shall proceed as follows:
Timer T3430 shall be stopped if still running.
For the cases b,c,d,la k when the"Extended wait time"is ignored,and ka when the"Extended wait time CP data"is ignored,if the tracking area updating request is not for initiating a PDN  connection for emergency bearer services,the tracking area updating attempt counter shall be incremented,unless it was already set to 5.
本领域技术人员基于上述现有协议的规定可知，终端在接收到来自4G网络的原因值为#17的拒绝消息后，会继续向4G网络发起TAU流程。
可选的，该第一时长小于10s。
这样，通过配置终端私有的计时器(如第一定时器)，使得终端可以灵活配置再次发起移动性更新流程的等待时长。相比于现有协议规定的10s，由于该第一定时器的计时时长更短，因此终端可以更快地发起移动性更新流程。
可选的，在将该第二移动性更新拒绝消息的原因值转换为第三原因值之后，该方法还包括：启动第一计数器，该第一计数器配置有第一阈值。在该发送该第一移动性更新请求之后，该方法还包括：配置该第一计时器的值加1。
可选的，在将该第二移动性更新拒绝消息的原因值转换为第三原因值之前，该方法还包括：确定该第一计数器的值小于该第一阈值。
可选的，该第一阈值小于5。
这样，通过配置终端私有的计数器(如第一计数器)，使得终端可以灵活配置再次发起移动性更新流程的次数。
可选的，第一网络为5G网络，第二网络为4G网络，第三网络为3G或2G网络。或者，第一网络为6G网络，第二网络为4G网络或5G网络，第三网络为3G或2G网络。
第二方面，本申请还提供一种电子设备，该电子设备也可称为终端设备。该电子设备包括：存储器和一个或多个处理器。存储器和处理器耦合。其中，存储器用于存储计算机程序代码，计算机程序代码包括计算机指令，当处理器执行计算机指令时，使得电子设备执行上述第一方面及其任一种可能的实现中提供的技术方案。
第三方面，本申请还提供一种芯片系统，该芯片系统应用于电子设备；芯片系统可以包括一个或多个接口电路和一个或多个处理器。接口电路和处理器通过线路互联，接口电路用于从电子设备的存储器接收信号，并向处理器发送该信号，该信号包括存储器中存储的计算机指令。当处理器执行上述的计算机指令时，使得电子设备执行上述第一方面及其任一种可能的实现中提供的技术方案。所述芯片系统可以包括Modem(基带处理器，或称之为调制解调处理器)。
第四方面，本申请还提供一种计算机可读存储介质，包括计算机指令，当计算机指令在电子设备上运行时，使得电子设备执行上述第一方面及其任一种可能的实现中提供的技术方案。
第五方面，本申请还提供一种计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面及其任一种可能的实现中提供的技术方案。
可以理解的是，上述本申请提供的第二方面到第五方面提供的方案，可以分别对应到第一方面及其任一种可能的设计，因此能够达到的有益效果类似，此处不再赘述。
附图说明
图1为一种通信场景的示意图；
图2为一种网络设备的组成示意图；
图3为一种通信方法的交互流程示意图；
图4为现网中统计的拒绝消息的原因值占比的示意图；
图5为一种通信方法的交互流程示意图；
图6为本申请实施例提供的一种终端设备的组成示意图；
图7为本申请实施例提供的一种通信方法的交互流程示意图；
图8为本申请实施例提供的一种通信方法的交互流程示意图；
图9为本申请实施例提供的一种通信方法的交互流程示意图；
图10为本申请实施例提供的一种通信方法的交互流程示意图；
图11为本申请实施例提供的一种电子设备的组成示意图；
图12为本申请实施例提供的一种芯片系统的组成示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本申请实施例提供的技术方案可以应用于各种无线通信网络，例如：全球移动通信(global system for mobile communication，简称为GSM)系统、码分多址(code division multiple access，简称为CDMA)系统、宽带码分多址(wideband code division multiple access，简称为WCDMA)系统、通用移动通信(universal mobile telecommunication system，简称为UMTS)系统、通用分组无线业务(general packet radio service，简称为GPRS)系统、长期演进(long term evolution，简称为LTE)系统、先进的长期演进(long term evolution advanced，简称为LTE-A)系统、全球互联微波接入(worldwide interoperability for microwave access，简称为WiMAX)系统、第五代移动通信技术(5th Generation Mobile Communication Technology，5G)的新空口(New Radio)网络、第六代移动通信技术(6th generation mobile networks，6G)的网络等。术语“网络”和“系统”可以相互替换。
以下说明中，将LTE(或LTE-A)系统对应网络称为4G网络，NR网络称为5G网络。其他类似，不再一一说明。
用户设备(User Equipment，简称为UE)或称为终端设备(简称为终端)可以通过接入不同制式的网络，向用户提供对应制式网络的通信功能。
随着网络技术的发展，同一位置可能被多种制式的网络覆盖。
示例性的，参考图1。在该场景中，终端当前所处位置可以同时被3G网络、4G网络和5G网络覆盖。那么对应的，终端可以通过接入3G网络，向用户提供3G网络的通信功能。终端还可以通过接入4G网络，向用户提供4G网络的通信功能。终端还可以通过接入5G网络，向用户提供5G网络的通信功能。
在一些情况下，终端可以优先接入具有更高数据传输速率的4G或5G网络，以便提供更好通信服务。
对于终端而言，可以通过驻留比(如4G驻留比)等参数，标识在各个网络上的驻留时间，进而据此优化终端在各个制式网络中的驻留策略。由此使得终端能够更久驻留在更高制式的网络上，进而向用户提供较好的通信功能。
需要说明的是，在本申请实施例中，某一制式的网络可以是由对应的网络设备构建发起的。
示例性的，3G网络可以对应于3G网络设备，4G网络可以对应于4G网络设备，5G网络可以对应于5G网络设备。
参考图2,3G网络设备可以包括3G基站、3G核心网设备等。这样，在终端接入到3G网络的情况下，可以通过3G基站与3G核心网设备进行上行通信，或者，3G核心网设备可以通过3G基站与终端进行下行通信。
类似的，4G网络设备可以包括4G基站、4G核心网设备等。这样，在终端接入到4G网络的情况下，可以通过4G基站与4G核心网设备进行上行通信，或者，4G核心网设备可以通过4G基站与终端进行下行通信。
5G网络设备可以包括5G基站、5G核心网设备等。这样，在终端接入到5G网络的情况下，可以通过5G基站与5G核心网设备进行上行通信，或者，5G核心网设备可以通过5G基站与终端进行下行通信。
以下示例中，以如图1所示场景为例，对本申请实施例提供的方案涉及场景以及具体方案实现进行说明。
参考图3，以终端驻留在5G网络为例。
在一些情况下，由于终端的移动或5G网络侧的临时故障等原因，5G网络设备可以指示终端向其他网络进行切换。
在如图3的示例中，5G网络设备可以执行S301，向终端发送指示消息11。该指示消息11用于指示终端从当前接入的5G网络变更驻留到4G网络。
在一些实施例中，该指示消息11具体可以包括网络重定向消息(如RRCConnectionRelease)，或者，网络切换指示(如HandoverCommand)。
在该指示消息11中，可以携带有4G网络对应的制式标识，4G网络的接入频点等信息。
对应的，终端可以根据该接收到的指示消息11，尝试接入到4G网络中。
示例性的，终端可以执行S302，向4G网络设备发送移动性更新请求12。
该移动性更新请求12可以是终端在完成与4G网络设备中的4G基站之间的RRC连接建立之后，通过4G基站，向4G核心网设备发送的。
在一些实现中，该移动性更新请求12可以包括Tracking Area Update(简称为TAU)Request，也即TAU Request。该TAU Request可以包括想要接入网络的标识等信息。例如，在该示例中，终端想要接入到4G网络中，对应的，移动性更新请求12可以包括4G网络的标识，如LTE字段等。
在一些情况下，4G网络设备可以根据移动性更新请求12，确定终端可以驻留到当前4G网络。那么对应的，4G网络设备可以向终端发送移动性更新接受消息(如TAU Accept)。
而在另一些情况下，在4G网络设备存在兼容性异常等问题的情况下，终端无法 接入到当前4G网络。那么对应，如图3所示，4G网络设备执行S303，向终端发送移动性更新拒绝消息13。
示例性的，该移动性更新拒绝消息13可以包括TAU Reject。
在一些实现中，终端接收到的移动性更新拒绝消息13中可以携带有拒绝原因值。
例如，移动性更新拒绝消息13中可以包括拒绝原因值为#111。
在现有协议规定中，#111被定义为protocol error,unspecified。也即，原因值为#111则对应于协议错误，原因未知。
相应的，在现有协议中还规定了原因值为#111的情况下，终端的执行策略：
attempt to select GERAN,UTRAN or NG-RAN radio access technology.Additionally,if the UE selects GERAN or UTRAN radio access technology,the UE may disable the E-UTRA capability。
也即，终端可以尝试选择GERAN，UTRAN或NG-RAN无线电接入技术。此外，如果UE选择GERAN或UTRAN无线接入技术，UE可能会禁用E-UTRA功能。
其中，GERAN，UTRAN无线电技术也即前述2G/3G网络技术。
可以理解的是，在该如图3所示的场景中，由于终端执行S302尝试接入4G网络之前，从5G网络断连。因此，终端可以在接收到包括原因值为#111的移动性更新拒绝消息13的情况下，不再选择NG-RAN无线电接入技术尝试接入5G网络。对应的，终端可以尝试选择GERAN，UTRAN接入到2G或3G网络。
示例性的，如图3所示，终端可以执行S304，向3G网络设备发起注册请求14，尝试接入到3G网络中进行驻留。
在终端成功注册到3G网络的情况下，则终端就可以完成5G到3G的网络变更。
基于前述协议规定的说明，在终端尝试接入到2G或3G网络的情况下，会禁用E-UTRA功能。也即配置为禁用4G网络。
这样，就会导致终端长时间驻留在2G或3G网络，而不会快速变更驻留到更高制式的网络(如4G网络或5G网络等)中。由此则对应于终端的4G驻留比或5G驻留比较低。这显然会影响终端向用户提供通信服务的质量。
通过对现网的监测统计，图4提供了拒绝原因值占比较大的6个原因值的示例。
如图4所示，在终端接收到的众多网络拒绝接入的消息中，携带#111的原因值的拒绝接入消息占比已经进入前6。因此，通过优化拒绝原因值为#111的场景，使得终端可以尝试快速重新驻留到更高制式的网络中，能够较为显著有效地提升终端的通信质量。
为了解决上述问题，在一些实现中，可以通过将原因值由#111转换为#17，以便于终端可以根据现有协议中，#17对应的处理策略执行后续处理。
在现有协议中，原因值为#17时，终端可以再次执行多次(如5次)向4G网络的移动性注册尝试。这样，相比于如图3所示的方案实现，终端可以在长时间驻留在2G/3G网络之前，被配置更多次向4G网络的接入尝试，从而提升接入4G网络的概率。
作为一种示例，参考图5。结合图3的说明，以终端和网络设备之间执行S301- S303的交互为例。
如图5所示，终端在接收到原因值为#111的移动性更新拒绝消息13之后，可以触发执行以下步骤：S401、终端将拒绝原因值转换为#17。
这样，终端就可以根据协议规定的，接收到拒绝原因值为#17对应的响应策略执行后续处理。
示例性的，该过程可以包括：
S402、终端启动T3411定时器以及计数器C11。
其中，T3411定时器可以提供10s时长的计时功能。计数器C11可以用于进行后续消息发送的计数。
终端可以根据T3411定时器计时结束，触发执行S403。
S403、终端向4G网络设备发送移动性更新请求15。
示例性的，该移动性更新请求15类似于前述S302中发送的移动性更新请求12。该移动性更新请求15中可以包括TAU Request。
在现有协议规定中，终端可以在接收到原因值为#17的拒绝接入消息的情况下，再次向4G网络设备发送TAU Request，由此尝试再次接入到4G网络。
可以理解的是，对于网络而言，在较短时间内连续接收到多个相同的消息，可能会被认定为无效消息。从而基于网络中配置的安全策略，不对后续消息进行响应。
在该如图5所示的方案实现中，终端可以在再次发送TAU Request之前，通过发起T3411定时器等待10s。由此使得终端不会立即向4G网络设备重复发送TAU Request。进而避免移动性更新请求15不被4G网络设备响应的问题。
在如图5的示例中，终端可以多次执行S402-S403，实现多次向4G网络设备的尝试性接入。
在具体执行过程中，终端可以通过S402中启动的计数器C11，记录向4G网络设备的接入尝试的次数。例如，在执行S403之后，终端可以执行S404，配置计数器C11加1。
这样，在计数器C11的数值达到一定数值(如5次)的情况下，则表明多次尝试后依然无法接入到4G网络。那么终端就可以跳转执行图3所示的S304，向3G网络设备发送注册请求14，以便于终端通过驻留到3G网络，保证基本的通信。
对应的，在计数器C11的数值未达到5次的情况下，则终端可以反复多次执行S402-S403。
在如图5的示例中，终端可以在执行S403之后，接收到来自4G网络设备发送的移动性更新确认消息16。
示例性的，该移动性更新确认消息16可以包括TAU Accept。也即，在进行一次重新尝试后，终端就可以成功接入到4G网络中。
这样，也就避免了如图3所示的一次接入4G网络失败之后，长时间驻留在3G网络中的问题。
然而，如图5所示的方案实现中依然存在一些问题。
如图5所示，对于终端而言，为了能够使得4G网络设备可以正常响应再次发送的TAU Request(如移动性更新请求15)，需要等待T3411定时器计时结束再发送该 移动性更新请求15。那么，即使如图5所示的，在进行1次重新向4G网络尝试后即接入4G网络，终端也会存在至少10s的通信中断。
基于此，本申请实施例提供的技术方案，相较于如图3所示的现有方案，能够避免终端长时间驻留在2G/3G网络中。此外，本申请实施例提供的技术方案，相比于如图5所示的技术实现，能够使得终端可以更快地驻留到4G网络上，降低或消除驻留到4G网络之前的通信中断问题。
以下结合附图对本申请实施例提供的方案进行详细说明。
需要说明的，本申请实施例中的终端可以包括手机、可折叠电子设备、平板电脑、桌面型计算机、膝上型计算机、手持计算机、笔记本电脑、超级移动个人计算机(ultra-mobile personal computer，UMPC)、上网本、蜂窝电话、个人数字助理(personal digital assistant，PDA)、增强现实(augmented reality，AR)设备、虚拟现实(virtual reality，VR)设备、人工智能(artificial intelligence,AI)设备、可穿戴式设备、车载设备、智能家居设备、或智慧城市设备中的至少一种。本申请实施例对终端的具体类型不作特殊限制。
作为一种示例，参考图6，为本申请实施例提供的一种终端的组成示意图。
如图6所示，终端可以包括处理器610，外部存储器接口620，内部存储器621，通用串行总线(universal serial bus，USB)接头630，充电管理模块640，电源管理模块641，电池642，天线1，天线2，移动通信模块650，无线通信模块660，音频模块670，传感器模块680，摄像模组693，显示屏694等。在一些实现中，传感器模块680可以包括压力传感器，陀螺仪传感器，气压传感器，磁传感器，加速度传感器，距离传感器，接近光传感器，指纹传感器，温度传感器，触摸传感器，环境光传感器，骨传导传感器等。
处理器610可以包括一个或多个处理单元，例如：处理器610可以包括应用处理器(application processor，AP)，调制解调处理器(Modem)，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，控制器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器(baseband processor，BP或BBP)，和/或神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。例如，调制解调器可以集成在基带处理器中等。
本申请实施例提供的方案实现中，终端的内部处理逻辑可以由基带处理器直接或间接实现。
在终端工作时，处理器610可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。
需要说明的是，本申请实施例示意的结构并不构成对终端的具体限定。在本申请另一些实施例中，终端可以包括比图6所示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图6所示的部件可以以硬件，软件或软件和硬件的组合实现。
本申请实施例提供的各个具体实现，均可以应用于如图6所示的电子设备中。
需要指出的是，以下说明中，终端与网络设备之间的交互，可以包括终端与对应网络的核心网设备的交互。例如，终端与网络设备之间的TAU流程(如包括发送TAU请求等)，可以是终端与对应网络的核心网设备之间的TAU流程。又如，终端与网络设备之间的附着(Attach)流程(如包括发送Attach请求等)，可以是终端与对应网络的核心网设备之间的Attach流程。
其中，终端与核心网设备之间的交互可以是通过对应网络的接入网络设备实现的。
例如，终端与5G核心网设备之间的交互，可以是通过5G基站进行消息透传实现的。又如，终端与4G核心网设备之间的交互，可以是通过4G基站进行消息透传实现的。又如，终端与6G核心网设备之间的交互，可以是通过6G基站进行消息透传实现的。其他网络类似。
在一些实施例中，参考图7，为本申请实施例提供的一种通信方法的交互流程示意图。如图7所示，该方案可以包括：
S701、终端接收第一指示消息。第一指示消息用于指示终端进行网络的重新驻留。
第一指示消息可以是终端当前所接入网络的网络设备(如网络设备71)发送给终端的。
该第一指示消息用于指示终端进行异系统网络或同系统网络的重新驻留。
示例性的，异系统网络的重新驻留可以包括：从当前驻留的5G网络切换/重定向到4G网络，或者，从当前驻留的4G网络切换/重定向到2G或3G网络，或者，从当前驻留的6G网络切换/重定向到5G或4G或3G网络等。
同系统网络的重新驻留可以包括：从当前驻留的5G网络切换/重定向到其他5G网络，或者，从当前驻留的4G网络切换/重定向到其他4G网络，或者，从当前驻留的6G网络切换/重定向到其他6G网络等。
本示例中，以第一指示消息用于指示终端进行异系统网络的重新驻留为例。
在一些实施例中，第一指示消息可以包括指示终端重新驻留的目标网络的信息。例如，以第一指示消息指示终端重新驻留在4G网络为例。第一指示消息包括4G网络的信息，如4G网络的网络标识(如LTE字段)和/或4G网络的接入频点等。
S702、终端发送第一移动性更新请求。
示例性的，该第一移动性更新请求可以包括TAU Request。在一些实施例中，该第一移动性更新请求可以包括网络设备72所属网络的标识。例如，网络设备72为4G网络设备，网络设备72所属网络的标识可以为4G网络的标识，如LTE等。
可选的，该第一移动性更新请求可以是终端根据第一指示消息，发送给指示重新驻留的网络设备(如网络设备72)的。
该第一移动性更新请求可以用于请求接入驻留到网络设备72对应的网络中。
S703、终端接收第一移动性更新拒绝消息。
示例性的，该第一移动性更新拒绝消息可以包括TAU Reject。
可选的，该第一移动性更新拒绝消息可以是网络设备72发送给终端的。
在本示例中，第一移动性更新拒绝消息可以包括拒绝此次网络接入的原因值。例 如，第一移动性更新拒绝消息的原因值可以为#111。
S704、终端发送第一初始注册请求。
示例性的，第一初始注册请求可以包括Attach Request。第一初始注册请求可以用于向网络设备72对应的网络发起初始注册。
可以理解的是，在终端开机之后，可以通过初始注册，实现向当前所处位置对应网络的接入。在本示例中，终端可以在接收到原因值为#111的第一移动性更新拒绝消息之后，向网络设备72对应的网络发起初始注册。
在一些实施例中，该Attach Request可以包括当前终端的国际移动设备识别码(International Mobile Equipment Identity，IMSI)，终端当前位置标识(如TAI标识)，终端支持的能力信息(如终端支持的频段信息等)等。
需要指出的是，由于TAU流程和Attach流程是两个互相独立的交互流程。因此，即使TAU流程没有成功，Attach流程也可能成功接入网络。
这样，本申请中，终端在接收到原因值为#111的第一移动性更新请求(即TAU流程失败)的情况下，可以再次发起Attach流程，尝试再次接入到网络设备72对应的网络中。
如图7所示，在本示例中，可选的，终端可以执行S705：终端接收第一初始注册成功消息。
示例性的，该第一初始注册成功消息可以包括Attach Accept。该第一初始注册成功消息用于指示终端成功附着/接入到网络设备72对应的网络中。
对应的，由于终端成功接入到网络设备72对应的网络中，也就不会出现网络制式继续掉落的情况出现。
需要说明的是，在如图7所示方案执行的过程中，终端可以配置为多种不同实现，使得在执行S703接收到原因值为#111的第一移动性更新拒绝消息之后，实现S704的触发。
示例性的，在一些实施例中，终端可以将原因值#111替换为其他原因值(如#9、#10或#40等)，以便于终端根据现有协议规定，基于替换后的原因值，触发S704。
在另一些实施例中，终端可以在接收到原因值#111的第一移动性更新拒绝消息之后，可以配置为触发S704的执行。
以下说明中，以终端通过替换原因值触发S704为例。
由此，将该如图7所示的方案应用于如图1所示场景中时，相比于图3示出的现有方案中的处理机制，终端不会在接收到原因值为#111的拒绝消息后掉落到2G或3G，并禁用4G网络。相应的，终端可以基于如图7所示的方案实现，在接收到原因值为#111的拒绝消息后，再次通过Attach流程尝试接入到4G网络中。进而提升终端继续驻留在4G网络中的概率。
此外，相比于如图5所示的方案实现，该如图7所示的方案执行过程中，终端在接收到第一移动性更新拒绝消息之后，可以触发执行S704，向网络设备72发送第一初始注册请求。由于第一初始注册请求对应的Attach流程与第一移动性更新请求对应的TAU流程并不相同，因此，终端不需要等待可以直接发送第一初始注册请求。由 此也就能够避免如图6所示方案中T3411定时器计时的时长(如10s)内的通信中断。
需要说明的是，如图7所示的流程交互仅为一种实现。在本申请的另一些实施例中，该如图7所示的发明构思还可以具有其他具体实现。
示例性的，参考图8，以本申请实施例提供的技术方案应用于如图1所示场景为例，对如图7所示的方案实现进行详细说明。本示例中，网络设备71可以为5G网络设备，网络设备72可以为4G网络设备。
如图8所示，该方案可以包括：
S801、终端接收指示消息11。
示例性的，该步骤的执行可以参考如图3所示的S301或图7所示的S701。其中，指示消息11可以对应于如图7所示的第一指示消息。
本示例中，该第一指示消息可以是当前接入的5G网络的5G网络设备(如5G网络设备中的核心网设备)发送的，用于指示终端从5G网络切换/重定向到4G网络。
S802、终端向4G网络设备发送移动性更新请求12。
示例性的，该步骤的执行可以参考如图3所示的S302或图7所示的S702。其中，移动性更新请求12可以对应于如图7所示的第一移动性更新请求。
本示例中，该移动性更新请求12可以包括TAU Request。该移动性更新请求12可以用于尝试接入到4G网络中。
S803、终端接收移动性更新拒绝消息13。
示例性的，该步骤的执行可以参考如图3所示的S303或图7所示的S703。其中，移动性更新拒绝消息13可以对应于如图7所示的第一移动性更新拒绝消息。
本示例中，该移动性更新拒绝消息13可以包括TAU Reject。该移动性更新拒绝消息13的原因值可以为#111，即protocol error,unspecified。
S804、终端将拒绝原因值转换为#9。
本示例中，终端可以接收到移动性更新拒绝消息13后，根据该拒绝消息的原因值为#111，触发执行该S804。
可以理解的是，原因值#9也是现有协议中规定的多种原因值之一。
基于现有协议规定，终端在接收到原因值为#9的拒绝消息后，可以触发执行初始注册流程，也即Attach流程。
在本申请的另一些实施例中，该S804中，终端可以将拒绝原因值由#111转换为其他原因值。其中，替换#111的原因值可以为：根据现有协议规定的，触发执行初始注册流程的原因值。
例如，终端可以将拒绝原因值由#111转换为#10或#40等。
接着，终端就可以根据接收到#9原因值的移动性更新拒绝消息，按照现有协议，执行后续操作。
S805、终端向4G网络设备发送初始注册请求17。
示例性的，该步骤的执行可以参考如图7所示的S704。该初始注册请求17可以对应于如图7所示的第一初始注册请求。
在该示例中，初始注册请求17可以包括Attach Request。
结合S804中的说明，该S804中，终端根据原因值为#9，触发执行初始注册流程。该初始注册流程可以对应于Attach注册流程或称为Attach流程。
基于该Attach流程，终端可以执行该S805，向4G网络设备发送初始注册请求17。该初始注册请求17可以用于请求附着在4G网络设备上进行通信。
S806、终端接收初始注册成功消息18。
示例性的，该初始注册成功消息18可以是由4G网络设备发送的。
该步骤的执行可以参考如图7所示的S705。该初始注册成功消息18可以对应于如图7所示的第一初始注册成功消息。
本示例中，该初始注册成功消息18可以包括Attach Accept。
由此，终端可以根据接收到初始注册成功消息18，完成向4G网络设备的Attach流程。对应的，终端也就可以基于该Attach流程完成，实现与4G网络设备的通信。进而据此向用户提供4G网络的通信服务。
可以理解的是，在如图8的示例中，终端在接收到移动性更新拒绝消息13之后，通过转换原因值，触发向4G网络的初始注册流程并注册成功。在该过程中，终端不需要进行等待，由此可以快速实现向4G网络的接入。也就对应的，终端不会由于原因值为#111的网络拒绝，配置为禁用4G，进而长时间驻留在低制式的2G/3G网络上。
如图8所示的方案示例，提供了一种如图7所示方案的具体实现。在本申请的另一些实施例中，如图7所示方案还可以包括其他实施方式。
示例性的，参考图9，为本申请实施例提供的又一种通信方法的交互流程示意图。
如图9所示，该示例中，各个网元之间的交互可以结合图8的示例进行扩展获取。
在如图9的示例中，S801-S806的执行过程可以参考如图8中的示例，具体不再赘述。
需要指出的是，如图9的示例中，终端在接收到原因值为#111的移动性更新拒绝消息13之后，在执行S804之前，可以执行S901。具体的：
S901、终端判断是否在通话中。其中，终端处于通话中，也即终端正在进行语音通话。示例性的，语音通话可以包括基于当前驻留的5G网络的VoNR通话。在另一些实施例中，终端当前驻留网络为4G网络的情况下，则该语音通话可以包括基于当前驻留的4G网络的VoLTE通话。
可以理解的是，在4G网络或5G网络中，终端的语音通话可以是基于固定IP实现的。该终端的固定IP可以是在向当前驻留网络设备进行注册(如初始注册)过程中，网络设备分配给终端的。
以终端当前驻留网络为5G网络为例。
终端可以在开机后，向当前5G网络进行初始注册过程中，接收到5G网络设备为终端配置的IP地址。此后，终端可以基于该IP地址，进行5G网络中的VoNR通话。由此对应的，在终端通话过程中，IP地址如果发生变化，则会出现VoNR通话断开的情况。
可以理解的是，在如图8所示的S804-S806的执行过程中，由于终端根据转换后的原因值#9，触发执行初始注册流程。在初始注册流程执行过程中，4G网络设备可能会为终端配置新的IP地址。这样，就可能会导致当前通话断开。
为了避免通话过程异常断开，在该如图9的示例中，终端可以在接收到原因值为#111的移动性跟新拒绝消息13之后，执行S804对应的将拒绝原因值转换为为#9之前，执行该S901，判断当前是否在通话中。
若终端当前在通话中，则为了避免通话异常断开，终端跳转执行S902。
对应的，若终端当前不再通话中，则执行S804-S806。
S902、终端将拒绝原因值转换为#17。
示例性的，该步骤可以参考如图5中的S401的说明。
在本示例中，终端可以在通话过程中，不再使用初始注册流程接入4G网络，以避免由此引起的通话异常断开。相对的，终端可以通过将拒绝原因值转换为#17，以便触发再次进行TAU流程，尝试接入4G网络。
由此，终端可以在保持通话的同时，尝试通过TAU流程，尝试接入4G网络。
需要说明的是，本示例中提供的方案实现，与如图5所示的方案实现并不相同。以下结合具体步骤进行说明。
S903、终端启动定时器91以及计数器C12。
示例性的，终端中可以预配置有定时器91和计数器C12。
其中，定时器91可以根据具体情况配置计时时长。在一些实施例中，定时器91的计时时长可以小于T3411定时器的计时时长。例如，定时器91的计时时长可以小于10s。
计数器C12初始值为0。终端可以根据具体情况为计数器C12配置对应阈值m。在一些实施例中，m可以为小于5的整数。例如，m可以配置为1。
需要说明的是，该如图9的示例中，定时器91并不同于如图5所示的现有协议规定的T3411定时器。计数器C12也不同于如图5所示的现有协议规定的计数器C11。
在一些实施例中，在执行S902之后，响应于原因值为#17的拒绝消息，终端可以根据S903，启动定时器91以及计数器C12。终端还可以根据现有协议，启动定时器T3411以及计数器C11。
由此，在定时器91或T3411定时器计时结束，终端触发执行S904。
例如，定时器91的计时时长为1s为例。则执行S902之后，终端可以等待1s，定时器91计时结束，触发执行S904。
可以理解的是，由于定时器91的计时时长小于T3411定时器对应的10s，因此，定时器91必然在T3411定时器之前计时结束，对应触发终端执行S904。
在另一些实施例中，在执行S902之后，响应于原因值为#17的拒绝消息，终端可以根据S903，启动定时器91以及计数器C12。此外，终端可以配置为不启动定时器T3411以及计数器C11。
S904、终端发送移动性更新请求19。
示例性的，该移动性更新请求19可以对应于如图5的移动性更新请求15。
在本示例中，终端可以通过移动性更新请求19，再次尝试向4G网络设备进行接入。在一些实施例中，移动性更新请求19可以与移动性更新请求12相同。
S905、终端配置计数器C12加1。
结合S903中的说明，终端可以启动计数器C12。那么对应的，启动计数器C12之后，终端每发送一次移动性更新请求(TAU Request)，则终端配置计数器C12加1。由此，计数器C12的值就可以用于表示当前重复进行TAU的次数。
需要说明的是，在一些实施例中，以终端将拒绝原因值转换为#17之后，启动计数器C11为例。在该S905中，终端配置计数器C12加1，还可以配置计数器C11加1。
S906、终端接收移动性更新拒绝消息20。
本示例中，以4G网络设备接收到移动性请求19之后，向终端发送移动性更新拒绝消息20为例。也即，终端进行TAU请求失败。
在一些实施例中，移动性更新拒绝消息20可以包括TAU Reject。该移动性更新拒绝消息20的原因值可以包括#111。
在另一些实施例中，终端可以在执行S904之后，接收到来自4G网络设备的移动性更新确认消息(如包括TAU Accept)。这样，终端也就成功接入到4G网络中，对应跳出执行如图9所示的流程。
以下以终端发出移动性更新请求19之后，接收到移动性更新拒绝消息20为例。
S907、终端判断计数器C12的值是否达到m。
示例性的，结合S903中的说明，m可以为与计数器C12对应的阈值。
在一些实施例中，终端可以在执行S907之前，确定接收到移动性更新拒绝消息(如移动性更新拒绝消息20)。作为一种可能的实现，终端可以根据发出TAU Request之后，接收到TAU Reject，确定接收到移动性更新拒绝消息。
在该S907中，终端可以读取计数器C12的值，判断计数器C12当前的值是否达到m。
在计数器C12当前的值达到m的情况下，则执行S908。对应的，在计数器C12当前的值未达到m(即小于m)的情况下，则返回执行S903。
在一些实施例中，m可以小于5。这样，在接收到移动性更新拒绝消息13之后，终端可以在进行最多4次(如m配置为4)TAU流程失败后，终端就可以跳转执行S908。
由此，通过该S907，终端可以根据配置的阈值m，控制重复进行TAU流程尝试接入4G网络的次数。进而避免尝试接入4G网络次数过多导致的功耗以及耗时过大等问题。
S908、终端发送注册请求21。
示例性的，在终端向4G网络执行多次(如m次)TAU流程并失败的情况下，终端可以向3G网络设备发送注册请求21。由此，终端可以尝试通过降低制式进行接入，以便保证终端能够提供最基本的通信功能。
需要说明的是，在如图9的示例中，终端在接收到移动性更新拒绝消息13之后，判断是否在通话。也就是说，在如图9的方案可以应用于具有通话功能的终端 中。
而对于其他不具有通话功能的终端，或者通话功能暂不可用的终端，在执行如图9所示的方案实现时，终端可以执行S803之后，不再执行S901，直接跳转执行S804。
此外，在如图9的示例中，终端在接收到移动性更新拒绝消息13之后，如果终端没有在通话中，则可以直接执行S804，将拒绝原因值转换为#9，进而触发执行S805进入初始注册流程。该处理策略简称为处理策略A。对应的，在终端处于通话中，则通过将拒绝原因值转换为#17再次进行TAU流程尝试接入4G网络。该处理策略简称为处理策略B。
也即，在如图9的示例中，在终端接收到原因值为#111的移动性更新拒绝消息13之后，首先触发处理策略A的执行，在处理策略A中判断正在通话中，则触发处理策略B。
在本申请的另一些实施例中，终端还可以在处理策略B之后触发处理策略A的执行。
示例性的，参考图10，为本申请实施例提供的又一种通信方法的交互流程示意图。
如图10所示，终端可以通过与网络设备(如5G网络设备、4G网络设备等)之间的交互，实现S801-S803的步骤。
本示例中，终端可以根据接收到原因值为#111的移动性更新拒绝消息13，触发执行处理策略B。
示例性的，终端可以在执行S803之后，顺序执行S902、S903、S904、S905、S906，以及S907。各个步骤的具体实现可以参考如图9中的说明，此处不再赘述。
由此，终端可以在一次TAU流程失败后，进行预设次数(如m次)内的TAU流程的尝试，以便于提高通过TAU流程重新接入到4G网络的概率。可以理解的是，在4G网络设备由于临时故障导致向终端发送#111的拒绝消息的情况下，则可以通过该处理策略B，就可以在4G网络设备临时故障修复后，尽快通过TAU流程，使得终端接入到4G网路中进行通信。
在如图10的示例中，是以处理策略B进行的m次TAU流程均失败为例进行说明的。在另一些实施例中，在该预设次数(如m次)内TAU流程执行的过程中，如果有一次TAU流程成功，如终端接收到4G网络回复的TAU Accept，那么对应的则跳出该如图10所示的流程，即终端可以在接入的4G网络上进行正常通信。
如图10的示例中，在处理策略B没有使得终端接入到4G网络的情况下，表示终端通过m次TAU流程尝试重连到4G网络均失败，则触发执行处理策略A。
示例性的，终端可以在计数器C12的值达到m的情况下，继续执行S901。
结合图9中的说明，在触发执行S901后，终端可以根据终端当前没有处于通话(如终端当前没有进行通话业务而在进行数据业务)中，执行S804、S805、S806等步骤。对应的，终端可以根据终端当前处于通话中，执行S908。
可以理解的是，如图10中各个步骤的执行以及相关扩展和变形，都可以对应到如图9中相应步骤的说明，此处不再一一赘述。
根据图10，在另一些可能的实现方式中，终端可以在接收到4G网络回复的原因值为#111的拒绝消息后，尝试向4G网络进行多次TAU流程，若某次TAU流程成功则终端就可以在4G网络上正常通信，若多次TAU流程均失败(如发起多次TAU请求，均收到原因值为#111的拒绝消息)，则终端可以向4G网络发起初始注册(如，终端可以在接收到4G网络回复的原因值为#111的拒绝消息后，按照现有协议中规定的接收到某一网络回复的原因值为#9的拒绝消息的处理策略，向该网络执行初始注册流程)。
由此，通过如图10的方案实现，终端可以在接收到#111的拒绝消息后，通过处理策略B和处理策略A的顺序触发，使得终端可以触发初始注册流程，结合TAU注册流程，实现向4G网络的快速接入。
需要说明的是，上述各个实施例中，均以终端驻留在5G网络，在网络设备的指示下变更驻留到4G网络后，接收到携带#111原因值的TAU Reject的拒绝消息为例，对本申请实施例提供的方案实现进行说明的。在另一些实施例中，本申请实施例提供的技术方案均可以应用于其他场景下。
例如，终端驻留在6G网络，在网络设备的指示下变更驻留到5G网络或4G网络。终端可以据此发起5G网络或4G网络的TAU流程。在接收到携带#111原因值的TAU Reject的拒绝消息后，终端可以根据本申请实施例提供的任一个方案实现，快速接入到5G网络或4G网络。
又如，终端驻留在3G网络，在网络设备的指示下变更驻留到4G网络或5G网络。终端可以据此发4G网络或5G网络的TAU流程。在接收到携带#111原因值的TAU Reject的拒绝消息后，终端可以根据本申请实施例提供的任一个方案实现，快速接入到4G网络或5G网络。
又如，终端驻留在5G网络，在网络设备的指示下变更驻留到其他5G网络。终端可以据此发起向新的5G网络的TAU流程。在接收到携带#111原因值的TAU Reject的拒绝消息后，终端可以根据本申请实施例提供的任一个方案实现，再次通过初始注册流程(如上述处理策略A)，或者初始注册以及TAU流程，(如上述处理策略A和处理策略B)，快速接入到新的5G网络中。
可以理解的是，本申请实施例提供的电子设备为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请实施例的范围。
本申请实施例可以根据上述方法示例对上述电子设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
示例性的，图11示出了的一种电子设备1100的组成示意图。该电子设备1100可以对应于前述任意实施例中的终端。
如图11所示，该电子设备1100可以包括：处理器1101和存储器1102。该存储器1102用于存储计算机执行指令。示例性的，在一些实施例中，当该处理器1101执行该存储器1102存储的指令时，可以使得该电子设备1100执行上述实施例中任一种所示的方法。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
图12示出了的一种芯片系统1200的组成示意图。该芯片系统1200可以包括：处理器1201和通信接口1202，用于支持相关设备(如终端)实现上述实施例中所涉及的功能。在一种可能的设计中，芯片系统还包括存储器，用于保存终端必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。需要说明的是，在本申请的一些实现方式中，该通信接口1202也可称为接口电路。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在上述实施例中的功能或动作或操作或步骤等，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包括这些改动和变型在内。

Claims (18)

  1. 一种通信方法，其特征在于，应用于终端设备，所述方法包括：
    所述终端设备驻留在第一网络；
    所述终端设备接收所述第一网络发送的第一指示消息，所述第一指示消息包括第二网络的标识和/或第二网络的接入频点，所述第一指示消息用于指示所述终端设备接入到所述第二网络；
    所述终端设备向所述第二网络发送第一移动性更新请求，所述第一移动性更新请求包括所述第二网络的标识；
    所述终端设备接收来自所述第二网络的第一移动性更新拒绝消息，所述第一移动性更新拒绝消息表示所述第二网络的第二网络设备拒绝所述终端接入所述第二网络，其中，所述第一移动性更新拒绝消息中携带的拒绝原因值为第一原因值，其中，在标准协议中规定了：所述终端设备响应于接收到来自所述第二网络的所述携带所述第一原因值的所述第一移动性更新拒绝消息，所述终端设备应向第三网络发起接入，所述第三网络的网络制式低于所述第二网络；
    响应于接收到来自所述第二网络的所述携带所述第一原因值的所述第一移动性更新拒绝消息，所述终端设备向所述第二网络发送第一初始注册请求，所述第一初始注册请求用于请求附着在所述第二网络。
  2. 根据权利要求1所述的方法，其特征在于，所述第一指示消息包括：
    指示所述终端设备重定向到所述第二网络的网络重定向消息；或者，
    指示所述终端设备切换驻留到所述第二网络的网络切换指示。
  3. 根据权利要求1-2中任一项所述的方法，其特征在于，所述第一原因值包括#111。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，在所述发送第一初始注册请求之前，所述方法还包括：
    将所述第一移动性更新拒绝消息的原因值由所述第一原因值转换为第二原因值，其中，在标准协议中规定了：所述终端设备响应于接收到来自所述第二网络的所述携带所述第二原因值的所述第一移动性更新拒绝消息，所述终端设备应向所述第二网络设备发送所述第一初始注册请求。
  5. 根据权利要求4所述的方法，其特征在于，所述第二原因值包括#9，或者#10，或者#40。
  6. 根据权利要求1-5任一所述的方法，其特征在于，所述响应于接收到来自所述第二网络的所述携带所述第一原因值的所述第一移动性更新拒绝消息，所述终端设备向所述第二网络发送第一初始注册请求，包括：
    响应于接收到来自所述第二网络的所述携带所述第一原因值的所述第一移动性更新拒绝消息，在所述终端设备当前不在通话中的情况下，所述终端设备向所述第二网络发送第一初始注册请求。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：响应于接收到来自所述第二网络的所述携带所述第一原因值的所述第一移动性更新拒绝消息，在所述终端设备当前在通话中的情况下，所述终端设备向所述第二网络发送第三移动性更 新请求。
  8. 根据权利要求1-7中任一项所述的方法，其特征在于，
    所述第二网络为LTE网络；所述第一移动性更新请求包括：TAU Request；所述第一移动性更新拒绝消息包括：TAU reject；或者，
    所述第二网络为NR网络；所述第一移动性更新请求包括：注册类型为MRU的注册请求；所述第一移动性更新拒绝消息包括：注册类型为MRU的注册拒绝消息。
  9. 根据权利要求1-8中任一项所述的方法，其特征在于，在接收第一指示消息之后，发送所述第一移动性更新请求之前，所述方法还包括：
    发送第二移动性更新请求，所述第二移动性更新请求用于向所述第二网络设备发起移动性更新流程，以便于接入到所述第二网络；
    接收第二移动性更新拒绝消息，所述第二移动性更新拒绝消息表示所述第二网络设备拒绝所述终端接入所述第二网络；
    其中，所述第二移动性更新拒绝消息的原因值为所述第一原因值。
  10. 根据权利要求9所述的方法，其特征在于，在接收到所述第二移动性更新拒绝消息之后，所述方法还包括：
    启动第一定时器，所述第一定时器的时长为第一时长；
    所述发送所述第一移动性更新请求，包括：
    在所述第一定时器计时结束后，发送所述第一移动性更新请求。
  11. 根据权利要求9或10所述的方法，其特征在于，在所述发送第一移动性更新请求之前，所述方法还包括：
    将所述第二移动性更新拒绝消息的原因值转换为第三原因值；所述第三原因值对应于，所述终端向所述第二网络设备发送所述第一移动性更新请求。
  12. 根据权利要求11所述的方法，其特征在于，所述第三原因值包括#17。
  13. 根据权利要求10-12任一所述的方法，其特征在于，所述第一时长小于或等于10s。
  14. 根据权利要求11-13中任一项所述的方法，其特征在于，在将所述第二移动性更新拒绝消息的原因值转换为第三原因值之后，所述方法还包括：
    启动第一计数器，所述第一计数器配置有第一阈值；
    在所述发送所述第一移动性更新请求之后，所述方法还包括：
    配置所述第一计时器的值加1。
  15. 根据权利要求14所述的方法，其特征在于，在将所述第二移动性更新拒绝消息的原因值转换为第三原因值之前，所述方法还包括：
    确定所述第一计数器的值小于所述第一阈值。
  16. 根据权利要求14或15所述的方法，其特征在于，所述第一阈值小于5。
  17. 一种终端设备，其特征在于，所述终端设备包括：存储器和一个或多个处理器；所述存储器和所述处理器耦合；
    其中，所述存储器用于存储计算机程序代码，所述计算机程序代码包括计算机指令，当所述处理器执行所述计算机指令时，使所述终端设备执行如权利要求1-16中任一项权利要求中所述的方法。
  18. 一种芯片系统，其特征在于，所述芯片系统应用于终端设备；所述芯片系统包括一个或多个接口电路和一个或多个处理器；所述接口电路和所述处理器通过线路互联；所述接口电路用于从所述终端设备的存储器接收信号，并向所述处理器发送所述信号，所述信号包括所述存储器中存储的计算机指令；当所述处理器执行所述计算机指令时，所述终端设备执行如权利要求1-16中任一项所述的方法。
PCT/CN2024/107089 2023-11-30 2024-07-23 一种通信方法和终端设备 Pending WO2025112573A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202480040701.XA CN121400014A (zh) 2023-11-30 2024-07-23 一种通信方法和终端设备

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202311641684.9A CN120111623A (zh) 2023-11-30 2023-11-30 一种通信方法和终端设备
CN202311641684.9 2023-11-30

Publications (1)

Publication Number Publication Date
WO2025112573A1 true WO2025112573A1 (zh) 2025-06-05

Family

ID=95882709

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/107089 Pending WO2025112573A1 (zh) 2023-11-30 2024-07-23 一种通信方法和终端设备

Country Status (2)

Country Link
CN (2) CN120111623A (zh)
WO (1) WO2025112573A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106416378A (zh) * 2014-12-05 2017-02-15 华为技术有限公司 一种接入方法、装置和系统
CN109104719A (zh) * 2018-08-23 2018-12-28 南京佰联信息技术有限公司 获取移动设备标识信息的方法、装置和系统
CN110741677A (zh) * 2017-12-15 2020-01-31 Oppo广东移动通信有限公司 保障切换的方法、终端设备和网络设备
WO2022196936A1 (ko) * 2021-03-18 2022-09-22 삼성전자주식회사 전자 장치 및 전자 장치의 무선 통신 방법

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106416378A (zh) * 2014-12-05 2017-02-15 华为技术有限公司 一种接入方法、装置和系统
CN110741677A (zh) * 2017-12-15 2020-01-31 Oppo广东移动通信有限公司 保障切换的方法、终端设备和网络设备
CN109104719A (zh) * 2018-08-23 2018-12-28 南京佰联信息技术有限公司 获取移动设备标识信息的方法、装置和系统
WO2022196936A1 (ko) * 2021-03-18 2022-09-22 삼성전자주식회사 전자 장치 및 전자 장치의 무선 통신 방법

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 (Release 17))", 3GPP DRAFT; DRAFT_24301-H40, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 20 September 2021 (2021-09-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052055514 *

Also Published As

Publication number Publication date
CN120111623A (zh) 2025-06-06
CN121400014A (zh) 2026-01-23

Similar Documents

Publication Publication Date Title
US20240373278A1 (en) Method of processing network slice based congestion, device and system thereof
US11812318B2 (en) Preserving emergency call during failure to transfer
CN110636593B (zh) 连接模式的控制方法、终端及存储介质
CN114268609B (zh) 一种语音业务切换方法、终端设备及芯片
CN114125972B (zh) 网络连接方法及相关装置
EP3598813B1 (en) Information processing method, apparatus, computer readable storage medium and electronic device
US9986465B2 (en) Method and system for returning to long term evolution network and mobile switching center
US11405834B2 (en) Data transmission method and device
US11051268B2 (en) Service activation and deactivation method, device and computer storage medium
WO2018102964A1 (zh) 传输信息的方法和设备
US20250031117A1 (en) Communication method and apparatus
EP3399801B1 (en) Voice call processing method and terminal device
CN101730070A (zh) 注册处理方法和接入处理方法
WO2021201729A1 (en) Faster release or resume for ue in inactive state
CN111479294B (zh) 拥塞控制下的数据连接建立方法、终端及存储介质
EP4554282A1 (en) Communication control method and electronic device
JP7169379B2 (ja) 緊急通話のための装置、方法、およびコンピュータプログラム
CN118803942A (zh) 一种连接认证方法、功能、存储介质及产品
CN121400014A (zh) 一种通信方法和终端设备
WO2024207372A1 (zh) 信息传输方法、装置、通信设备及存储介质
CN113785620B (zh) 用户设备基于plmn/信道的组合利用lte/5g网络中的服务
CN105827786B (zh) 双待终端的多模互操作方法及装置
WO2025092094A1 (zh) 一种通信方法、终端设备和芯片系统
CN118413828A (zh) 无线通信方法及装置、设备、存储介质
WO2025130026A1 (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: 24895676

Country of ref document: EP

Kind code of ref document: A1