A communication method, device and storage medium

Abstract

A communication method, device, and storage medium are disclosed, relating to the field of communication technology. The method includes: when initiating a detach procedure, starting a first timer, the duration of which is less than the duration of a T3421 timer, and / or the maximum allowed consecutive start count of the first timer is greater than the maximum allowed consecutive start count of the T3421 timer; if a detach accept message is not received before the first timer expires, the detach procedure is considered to have failed; after the first timer expires, re-initiating the detach procedure is allowed; when the consecutive start count of the first timer reaches the maximum allowed consecutive start count, the detach procedure is terminated. Using this method, a more flexible detach retry mechanism is provided when the detach procedure fails, facilitating timely service recovery by the terminal device.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method, device and storage medium. Background Technology

[0002] In a Long Term Evolution (LTE) network, when a User Equipment (UE) initiates a detach procedure, the UE sends a detach request to the network device and starts a T3421 timer, which lasts for 15 seconds. If the network device does not respond with a detachAccept message, the UE will resend the detach request after the T3421 timer expires, restarting the T3421 timer again. This process continues until the fifth timeout, at which point the UE stops the procedure.

[0003] According to current regulations, the maximum number of consecutive cumulative starts of the T3421 timer is 5. In extreme scenarios, if the UE does not receive a Detach Accept message from the network device in 5 Detach processes, the entire process will take up to 75 seconds. The retry mechanism is not flexible and greatly affects the recovery of services. Summary of the Invention

[0004] To address the aforementioned issues, this application provides a communication method, device, and storage medium that offers a more flexible Detach retry mechanism when the Detach process fails, facilitating timely service recovery for terminal devices.

[0005] In a first aspect, this application provides a communication method applicable to a terminal device, comprising: when initiating a Detach procedure, starting a first timer, wherein the duration of the first timer is less than the duration of a T3421 timer, and / or the maximum allowed consecutive start count of the first timer is greater than the maximum allowed consecutive start count of the T3421 timer; if a Detach Accept message is not received before the first timer expires, the Detach procedure is considered to have failed; after the first timer expires, the Detach procedure is allowed to be re-initiated; when the consecutive start count of the first timer reaches the maximum allowed consecutive start count of the first timer, the Detach procedure is terminated.

[0006] Using this method, when initiating a detach process, the terminal device does not start the T3421 timer, but instead starts the first timer. When the duration of the first timer is less than the duration of the T3421 timer, the retry interval of the detach process can be shortened; when the maximum allowed consecutive starts of the first timer are greater than the maximum allowed consecutive starts of the T3421 timer, the number of retries in the detach process can be increased; when the duration of the first timer is less than the duration of the T3421 timer, and the maximum allowed consecutive starts of the first timer are greater than the maximum allowed consecutive starts of the T3421 timer, the retry interval of the detach process can be shortened while increasing the number of retries. This solution provides a more flexible detach process mechanism, preventing the terminal device from being in a detach failure state for a long time, enabling the terminal device to complete the detach process in a timely manner, facilitating timely service recovery.

[0007] In one possible implementation, terminating the Detach process includes: starting a second timer with a duration longer than the first timer, and allowing the Detach process to be re-initiated after the second timer expires.

[0008] In this implementation, a second timer is set to prevent excessively frequent air interface signaling between the terminal device and the base station. Furthermore, the Detach procedure is allowed to be re-initiated after the second timer expires, further increasing the number of retries and enhancing the flexibility of the Detach procedure.

[0009] In one possible implementation, the duration of the second timer is greater than the duration of the T3421 timer.

[0010] In one possible implementation, when initiating the Detach process, before starting the first timer, the method further includes: receiving first configuration information, the first configuration information indicating the duration of the first timer, and / or the maximum allowed number of consecutive starts of the first timer.

[0011] In one possible implementation, when initiating the Detach process, before starting the first timer, the method further includes: receiving first configuration information, the first configuration information indicating the duration of the first timer, and / or the maximum allowed number of consecutive starts of the first timer; the first configuration information also indicating the duration of the second timer.

[0012] In one possible implementation, the first configuration information is carried in the Attach Accept message, that is, the first configuration information is carried in the Radio Resource Control (RRC) message.

[0013] In one possible implementation, the method further includes: when the number of consecutive failures of the Detach process due to the timeout of the first timer reaches a first value, recording failure information, wherein the failure information includes one or more of the following: the name of the timer that timed out, the Cell Global Identifier (CGI) of the current cell, and the Physical Cell Identifier (PCI) of the current cell.

[0014] In practical applications, if the detach process is initiated and the detach acceptance message is not received after the first timer expires, it may be due to a problem with the access network equipment or MME. In this case, the UE can record the failure information locally and use the failure information to troubleshoot the problem.

[0015] In one possible implementation, the method further includes: when a failure message exists locally, sending a first indication message, the first indication message indicating the existence of a failure message. The first indication message may be carried in an RRC message.

[0016] In one possible implementation, the first indication information is carried in the Radio Resource Control Connection Setup Complete message.

[0017] In one possible implementation, the method further includes: when a first request message is received, sending a first response message carrying failure information, wherein the first request message is used to query the failure information.

[0018] In this implementation, the terminal device can send the recorded failure information to the network device, which can partially replace the drive test and realize the automatic collection of measurement data from the terminal device to promote network optimization.

[0019] Secondly, this application provides a communication method applied to a network device, which may be a base station, comprising: sending first configuration information, wherein the first configuration information indicates the duration of a first timer and / or the maximum allowed number of consecutive starts of the first timer; wherein if the terminal device does not receive a Detach Accept message before the first timer expires, it is considered that the Detach process has failed; after the first timer expires, the Detach process is allowed to be re-initiated; and when the number of consecutive starts of the first timer reaches the maximum allowed number of consecutive starts of the first timer, the Detach process is terminated.

[0020] Using this method, network devices can configure the duration of a first timer and / or the maximum allowed consecutive starts of the first timer for terminal devices. This ensures that when a terminal device initiates a detach process, the T3421 timer is not activated; instead, the first timer is activated. When the duration of the first timer is less than the duration of the T3421 timer, the retry interval of the detach process can be shortened. When the maximum allowed consecutive starts of the first timer is greater than the maximum allowed consecutive starts of the T3421 timer, the number of detach process retries can be increased. When the duration of the first timer is less than the duration of the T3421 timer, and the maximum allowed consecutive starts of the first timer is greater than the maximum allowed consecutive starts of the T3421 timer, the retry interval of the detach process can be shortened while increasing the number of detach process retries. This method provides a more flexible detach process mechanism, preventing terminal devices from being in a detach failure state for extended periods, enabling timely completion of the detach process and facilitating timely service recovery.

[0021] In one possible implementation, the first configuration information also indicates the duration of the second timer, which starts when the number of consecutive starts of the first timer reaches the maximum allowed number of consecutive starts of the first timer. The duration of the second timer is longer than the duration of the first timer, and the Detach process is allowed to be re-initiated after the second timer expires.

[0022] In this implementation, a second timer is set to prevent excessively frequent air interface signaling between the terminal device and the terminal.

[0023] In one possible implementation, the duration of the second timer is greater than the duration of the T3421 timer.

[0024] In one possible implementation, the method further includes: when receiving a first indication message, sending a first request message, wherein the first indication message indicates the existence of failure information, the first request message is used to query the failure information, and when the number of times the Detach process fails due to the first timer timeout reaches a first value, the failure information includes one or more of the following: the name of the timer that timed out, the Cell Global Identifier (CGI) of the current cell, and the Physical Cell Identifier (PCI) of the current cell; and receiving a first response message, which carries the failure information.

[0025] In one possible implementation, the first request information is carried in a Radio Resource Control (RRC) message.

[0026] In one possible implementation, after receiving the first response information, the method further includes sending a report message carrying failure information to the Mobility Management Entity (MME). The interface between the base station and the MME is S1-AP, and the report information can be carried in the S1-AP message, enabling the MME to identify abnormal base station equipment by collecting report information from each base station, thereby achieving fault diagnosis.

[0027] Thirdly, this application provides a communication method that can be applied to a mobility management entity (MME). The method includes: receiving report information sent by one or more network devices, the report information carrying failure information, and when the number of times the Detach process fails due to the timeout of the first timer reaches a first value, the failure information includes one or more of the following: the name of the timer that timed out, the Cell Global Identifier (CGI) of the current cell, and the Physical Cell Identifier (PCI) of the current cell; and troubleshooting based on the failure information in all the report information.

[0028] In one possible implementation, the failure information includes the name of the timer that timed out, the Cell Global Identifier (CGI) of the current cell, and the Physical Cell Identifier (PCI) of the current cell. Fault investigation is performed based on the failure information in all reports, specifically including: identifying the base station where the Detach process failure occurred as the target network device based on each failure information; investigating whether there is a fault in the S1 interface between the target network device and the Mobility Management Entity (MME); and determining the reason for the detach failure.

[0029] In this implementation, the base stations most likely to fail can be identified based on PCI and CGI, and troubleshooting can be performed on these base stations. Specifically, troubleshooting the S1 interface between the target network device and the MME is crucial because an S1 interface failure could prevent the base station from receiving S1-AP messages from the MME, thus preventing the NAS message from being directly transmitted to the UE, and consequently, the UE's inability to receive the Detach Accept message.

[0030] Fourthly, this application also provides a network device, which can be a base station, including a processor and a memory; the processor is coupled to the memory; the memory is used to store instructions; the processor is used to execute the computer program or instructions stored in the memory to implement the communication method as described in the second aspect and any implementation thereof above.

[0031] Fifthly, this application also provides a network device, which can be a mobility management entity (MME), including a processor and a memory; the processor is coupled to the memory; the memory is used to store instructions; the processor is used to execute the computer program or instructions stored in the memory to implement the communication method as described in the third aspect and any implementation thereof above.

[0032] In a sixth aspect, this application also provides a terminal device, including a processor and a memory; the processor is coupled to the memory; the memory is used to store instructions; the processor is used to execute the computer program or instructions stored in the memory to implement the communication method as described in the first aspect and any implementation thereof above.

[0033] Seventhly, this application also provides a computer-readable storage medium for storing a computer program, which, when executed, implements the communication method described in the first aspect and any implementation thereof, or the communication method described in the second aspect and any implementation thereof, or the communication method described in the third aspect and any implementation thereof.

[0034] Eighthly, this application also provides a computer program product, which includes instructions that, when executed, implement the communication method described in the first aspect and any implementation thereof, or the communication method described in the second aspect and any implementation thereof, or the communication method described in the third aspect and any implementation thereof. Attached Figure Description

[0035] Figure 1 A flowchart for Detach failure;

[0036] Figure 2 The flowchart shows the Detach failure caused by the T3421 timer timeout.

[0037] Figure 3 A flowchart illustrating a communication method provided in an embodiment of this application;

[0038] Figure 4 A flowchart illustrating another communication method provided in an embodiment of this application;

[0039] Figure 5 A flowchart illustrating a method for configuring timer parameters by a network device, provided in an embodiment of this application;

[0040] Figure 6 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0041] Figure 7 A schematic diagram of a network device provided in an embodiment of this application;

[0042] Figure 8 A schematic diagram of another network device provided in the embodiments of this application;

[0043] Figure 9This is a schematic diagram of a terminal device provided in an embodiment of this application. Detailed Implementation

[0044] To enable those skilled in the art to better understand the solution of this application, the application scenario of the technical solution of this application will be described first below.

[0045] See Figure 1 The diagram shows the flowchart of a successful Detach.

[0046] Taking the terminal device as UE and the base station as an evolved Node B (eNB) as an example, the method includes the following steps:

[0047] S10: The UE initiates the Detach procedure and starts the T3421 timer.

[0048] In this application, "attach" refers to a terminal device registering in a Public Land Mobile Network (PLMN) to establish its own profile, i.e., a terminal context. A security context is generated during the attachment process to protect Non-Access Stratum (NAS) signaling. A UE-initiated detach procedure allows the UE to notify the network side that it will no longer enter the Evolved Packet System (EPS).

[0049] The T3421 timer is a normal control timer. The T3421 timer is triggered when the UE sends a Detach Request. If the T3421 timer expires without receiving a Detach Accept message, the detach process has failed. If a Detach Accept message is received before the T3421 timer expires, the detach process has succeeded. The relevant protocol stipulates that the maximum number of consecutive cumulative triggers of the T3421 timer is 5, which means the maximum number of consecutive cumulative detach failures is 5.

[0050] S11: The UE sends a Detach Request message to the eNB.

[0051] When a UE in RRC connection state initiates a Detach procedure, it sends a NAS layer Detach Request message to the eNB.

[0052] S12: The eNB sends a Detach Request message to the MME.

[0053] S13: The MME sends a Detach Accept message to the eNB.

[0054] In one possible implementation, the Mobility Management Entity (MME) can send a DeleteSession Request message to the Serving Gateway (Serving-GW or SGW) to request the deletion of the UE's EPS session and default bearer. The SGW then sends a DeleteSession Response message to the MME to confirm that the EPS session and default bearer have been deleted. The MME then sends a Detach Accept message to the eNB to indicate that detach is accepted.

[0055] S14: The eNB sends a Detach Accept message to the UE.

[0056] S15: A Detach Accept message is received before the T3421 timer expires. The Detach is successful and the T3421 timer stops.

[0057] If the UE receives a Detach Accept message before the T3421 timer expires, the UE can determine that the Detach was successful and stop the T3421 timer.

[0058] See Figure 2 The diagram shows the flowchart of Detach failure caused by T3421 timer timeout.

[0059] S20: The UE initiates the Detach procedure and starts the T3421 timer.

[0060] S21: The UE sends a Detach Request message to the eNB.

[0061] S22: The eNB sends a Detach Request message to the MME.

[0062] S23: Timer T3421 timed out and no Detach Accept message was received.

[0063] S24: The number of failed Detach processes recorded on the UE side is incremented by 1.

[0064] S25: The UE side determines whether the cumulative number of consecutive failures in the Detach process has reached 5.

[0065] If not, proceed to S20; otherwise, proceed to S26.

[0066] The Detach process's cumulative failure count is also the number of consecutive starts of the T3421 timer. The relevant protocol currently specifies a maximum of 5 consecutive cumulative starts for the T3421 timer.

[0067] S26: Abort the Detach process.

[0068] When the T3421 timer times out for the fifth time, the Detach process is terminated and the UE can continue with the following operations:

[0069] If the Detach procedure is executed due to the disabling of EPS service, the UE should enter the EMM-NULL state;

[0070] If the request for "EPSDetach" is made for reasons other than disabling EPS service, the UE enters the EMM-DEREGISTERED state.

[0071] If a request for "International Mobile Subscriber Identity (IMSI) Separation" is made, the UE should enter the EMM-REGISTERED.NORMAL-SERVICE state and the MM-NULL state; or,

[0072] If a request is made to "separate EPS / IMSI", the UE should enter EMM-deregister state and MM-NULL state.

[0073] based on Figure 2 In the scenario shown, under extreme circumstances, if the UE does not receive a Detach Accept message from the network device in 5 Detach processes, the entire process can take up to 75 seconds. The retry mechanism is not flexible enough and may prevent the terminal device from completing the Detach process in a timely manner, which will greatly affect the recovery of services.

[0074] To address the above issues, this application provides a communication method, device, and storage medium. When a terminal device initiates a detach procedure, it does not activate the T3421 timer but instead starts a first timer. The duration of the first timer is shorter than the duration of the T3421 timer, and / or the maximum allowed consecutive starts of the first timer are greater than the maximum allowed consecutive starts of the T3421 timer. This solution provides a more flexible detach procedure mechanism, preventing the terminal device from remaining in a detach failure state for an extended period, enabling the terminal device to complete the detach procedure promptly and facilitating timely service recovery.

[0075] The solutions provided in this application can be applied to cellular communication systems related to the 3rd Generation Partnership Project (3GPP), such as 4th generation (4G) communication systems, such as Long Term Evolution (LTE) communication systems, and can also be applied to 5th generation (5G) cellular communication systems. th 5G communication systems, such as 5G New Radio (NR) communication systems, or various future communication systems, such as 6th generation (6G) communication systems.

[0076] The network equipment described below can be access network equipment for 3GPP-related cellular systems, such as 4G or 5G mobile communication systems. The network equipment can also be access network equipment in open RAN (O-RAN or ORAN) or cloud radio access network (CRAN). Alternatively, the network equipment can be access network equipment in a communication system formed by the integration of two or more of the above communication systems.

[0077] Network equipment includes, but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home-evolved NodeB, or home Node eB, HNB), base band unit (BBU), access point (AP) in a Wi-Fi system, macro base station, micro base station, wireless relay node, donor node, radio controller in a CR AN scenario, wireless backhaul node, transmission point (TP), or transmission and receiving point (TRP). Network equipment can also be access network equipment in 5G mobile communication systems. For example, next-generation Node B (gNB), TRP, TP in a new radio (NR) system, or one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G mobile communication system. Alternatively, network devices can also be network nodes constituting a gNB or transmission point. Examples include centralized units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs). CUs and DUs can be separate entities or included in the same network element, such as a BBU. RUs can be included in radio equipment or radio units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). Alternatively, network devices can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in V2X technology, network devices can be roadside units (RSUs).

[0078] It should be noted that the network device can be the device or apparatus shown above, or a component (e.g., a chip), module, or unit in the device or apparatus shown above; this application does not limit the specifics.

[0079] The terminal equipment described below, also known as user equipment (UE), mobile station (MS), or mobile terminal (MT), is a device that provides voice or data connectivity to a user. Specifically, it includes devices that provide voice connectivity, devices that provide data connectivity, or devices that provide both voice and data connectivity. For example, it may include a handheld device with wireless connectivity or a processing device connected to a wireless modem. This terminal equipment can communicate with the core network via a radio access network (RAN), exchanging voice or data with the RAN, or interacting with the RAN to exchange voice and data. Currently, terminal devices can include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices (such as smartwatches, smart bracelets, pedometers, etc.), in-vehicle devices (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, workshop equipment, wireless terminals in autonomous driving, wireless terminals in remote surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, and flying equipment (such as intelligent robots, hot air balloons, drones, airplanes), etc. Terminal devices can also be other devices with terminal functions; for example, a terminal device can also be a device that performs terminal functions in D2D communication.Terminal devices can also include vehicle-to-everything (V2X) terminal devices, machine-to-machine / machine-type communications (M2M / MTC) terminal devices, internet of things (IoT) terminal devices, light UEs, reduced capability UEs (REDCAP UEs), subscriber units, subscriber stations, mobile stations, remote stations, access points (APs), remote terminals, access terminals, user terminals, user agents, or user devices, and drone equipment. For example, this can include mobile phones (or "cellular" phones), computers with mobile terminal devices, portable, pocket-sized, handheld, and computer-embedded mobile devices, etc. Examples include personal communication service (PCS) telephones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, and personal digital assistants (PDAs). It also includes limited devices, such as those with low power consumption, limited storage capacity, or limited computing power. Examples include information sensing devices such as barcode scanners, radio frequency identification (RFID), sensors, global positioning systems (GPS), and laser scanners. In this application, terminal devices with wireless transceiver capabilities and chips that can be installed in the aforementioned terminal devices are collectively referred to as terminal devices.

[0080] It should be noted that the terminal device may be a device or apparatus with a chip, or a device or apparatus with integrated circuitry, or a chip, module or control unit in the device or apparatus shown above. This application does not limit the specific device.

[0081] The "multiple" mentioned in the embodiments of this application refers to two or more. It should be noted that in the description of the embodiments of this application, terms such as "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance, nor should they be construed as indicating or implying order.

[0082] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0083] See Figure 3 The figure is a flowchart of a communication method provided in an embodiment of this application.

[0084] Taking the terminal device as UE and the network device as eNB as an example, the method includes the following steps:

[0085] S30: Initiate the Detach process and start the first timer.

[0086] In the existing technology, when a UE initiates a Detach procedure, a T3421 timer is started. The duration of the T3421 timer is 15 seconds. Only when 15 seconds have passed and a Detach Accept message has not been received will the UE determine that the Detach procedure has failed, which makes the time taken for a single Detach procedure failure relatively long.

[0087] In the solution provided in this application embodiment, when the UE initiates the Detach procedure, the terminal device will not start the T3421 timer, but will start the first timer. The duration of the first timer is shorter than the duration of the T3421 timer, and / or the cumulative number of consecutive starts of the first timer is greater than the maximum allowed number of starts of the T3421 timer.

[0088] The embodiments of this application do not specifically limit the duration of the first timer. For example, in order to shorten the retry interval of the Detach process, the duration of the first timer can be set to 5 seconds. The above duration is only an example and does not constitute a limitation on the technical solution of this application.

[0089] This application embodiment does not specifically limit the maximum allowed number of times the first timer can be started. For example, in order to increase the number of retries of the Detach process, the maximum allowed number of times the first timer can be started can be configured to 15 times.

[0090] The solution in this application embodiment can be configured such that the duration of the first timer is equal to the duration of the T3421 timer, and the maximum allowed number of starts of the first timer is greater than the maximum allowed number of starts of the T3421 timer, to increase the number of retries in the Detach process separately; or the duration of the first timer can be configured such that it is less than the duration of the T3421 timer, and the maximum allowed number of starts of the first timer is equal to the maximum allowed number of starts of the T3421 timer, to shorten the number of retries in the Detach process separately; or the duration of the first timer can be configured such that it is less than the duration of the T3421 timer, and the maximum allowed number of starts of the first timer is greater than the maximum allowed number of starts of the T3421 timer, thereby increasing the number of retries in the Detach process while shortening the number of retries in the Detach process, thus fully improving the flexibility of the Detach process.

[0091] S31: The first timer timed out and no Detach Accept message was received.

[0092] At this point, the UE side determines that the Detach process has failed.

[0093] S32: Increment the cumulative number of consecutive failures in the Detach process by 1.

[0094] In this embodiment of the application, the cumulative number of consecutive failures of the Detach process is the number of consecutive starts of the first timer.

[0095] S33: Determine whether the cumulative number of consecutive failures in the Detach process has reached the maximum allowed number of consecutive starts for the first timer.

[0096] If yes, execute S34; otherwise, execute S30.

[0097] If the cumulative number of consecutive failures in the Detach process reaches the maximum allowed number of consecutive starts of the first timer, it indicates that the Detach process still fails after multiple attempts, and the current access network equipment (base station) may be faulty. The Detach process should be stopped to avoid excessively frequent air interface signaling between the terminal equipment and the base station.

[0098] S34: Abort the Detach process.

[0099] It is understood that the above steps are limited only for the convenience of explanation and do not constitute a limitation on the technical solution of this application. In actual application, the above steps can be adapted. For example, S32 can also be replaced with "increase the number of consecutive starts of the first timer by 1", and S33 can be replaced with "determine whether the number of consecutive starts of the first timer has reached the maximum allowed number of consecutive starts of the first timer".

[0100] In summary, using the method provided in this application embodiment, when initiating a detach process, the terminal device does not start the T3421 timer, but instead starts a first timer. When the duration of the first timer is less than the duration of the T3421 timer, the retry interval of the detach process can be shortened; when the maximum allowed consecutive start count of the first timer is greater than the maximum allowed consecutive start count of the T3421 timer, the number of retries in the detach process can be increased; when the duration of the first timer is less than the duration of the T3421 timer, and the maximum allowed consecutive start count of the first timer is greater than the maximum allowed consecutive start count of the T3421 timer, the retry interval of the detach process can be shortened while increasing the number of retries. This solution provides a more flexible detach process mechanism, avoiding the terminal device being in a detach failure state for a long time, enabling the terminal device to complete the detach process in a timely manner, and facilitating the timely recovery of services.

[0101] In practical applications, although the failure that causes the Detach process to fail may last for a period of time, it may be repaired in time. Therefore, this application embodiment also provides another communication method to further increase the number of retries for the Detach process, which will be described in detail below with reference to the accompanying drawings.

[0102] See Figure 4 The figure is a flowchart of another communication method provided in an embodiment of this application.

[0103] Taking the terminal device as UE and the network device as eNB as an example, the method includes the following steps:

[0104] S40: Initiate the Detach process and start the first timer.

[0105] For details regarding the first timer, please refer to the corresponding record for S30, which will not be repeated here.

[0106] S41: The first timer timed out and no Detach Accept message was received.

[0107] At this point, the UE side determines that the Detach process has failed.

[0108] S42: Increment the cumulative number of consecutive failures in the Detach process by 1.

[0109] In this embodiment of the application, the cumulative number of consecutive failures of the Detach process is the number of consecutive starts of the first timer.

[0110] S43: Determine whether the cumulative number of consecutive failures in the Detach process has reached the maximum allowed number of consecutive starts for the first timer.

[0111] If yes, execute S44; otherwise, execute S40.

[0112] If the cumulative number of consecutive failures in the Detach process reaches the maximum allowed number of consecutive starts of the first timer, it indicates that the Detach process has failed after multiple attempts, and the current access network equipment (base station) may be faulty. The Detach process should be terminated to avoid excessively frequent air interface signaling between the terminal equipment and the base station. In this embodiment, the method for terminating the Detach process is to start a second timer.

[0113] S44: Start the second timer.

[0114] This application does not specifically limit the duration of the second timer. Setting the second timer can prevent excessively frequent air interface signaling between the terminal device and the base station; therefore, the duration of the second timer is relatively longer than that of the first timer. In practical applications, the duration of the second timer is generally also longer than that of the T3421 timer. The duration of the second timer can be set to the minute level; for example, it can be set to 2 minutes. These durations are merely examples and do not constitute a limitation on the technical solution of this application.

[0115] S45: The Detach process can be re-initiated after the second timer expires.

[0116] In this embodiment, the Detach process is allowed to be re-initiated after the second timer expires, further increasing the number of retries and enhancing the flexibility of the Detach process. In one possible implementation, after the second timer expires, the UE can reset the consecutive start count of the first timer to zero, i.e., set the cumulative failure count of the Detach process to zero, thereby increasing the number of retries for the Detach process.

[0117] In summary, by using the method provided in this application embodiment, when the cumulative number of consecutive failures of the Detach process reaches the maximum allowed number of consecutive starts of the first timer, a second timer is started. When the second timer expires, the Detach process is allowed to be re-initiated, which further increases the number of retries for the Detach process, further improves the flexibility of the Detach process, and increases the success rate of the Detach process.

[0118] In the above embodiments, parameters such as the duration of the first timer, the maximum number of consecutive starts allowed for the first timer, and the duration of the second timer can be pre-configured and stored locally on the terminal device, or can be configured by the network device after the terminal device completes the attachment.

[0119] When stored locally on the terminal device, the terminal device can distinguish the country / region based on the Mobile Country Code (MCC) of the current Public Land Mobile Network (PLMN) and the operator based on the Mobile Network Code (MNC) of the current PLMN. Then, based on the country / region and operator, it can obtain the corresponding duration of the first timer, the maximum allowed number of times the first timer can be started, and the duration of the second timer, and configure and update these parameters locally on the terminal device. In this implementation, if the MCC and MNC of the PLMN in which the terminal device is located remain unchanged, the duration of the first timer, the maximum allowed number of consecutive starts of the first timer, and the duration of the second timer generally remain unchanged, and subsequent Detach processes can directly use the locally stored data.

[0120] The following explains how to implement network device configuration parameters.

[0121] See Figure 5 The figure is a flowchart of a method for configuring timer parameters by a network device according to an embodiment of this application.

[0122] Taking the terminal device as UE and the base station eNB as an example, the configuration data for the first and second timers required by the UE to initiate the Attach procedure can be configured by the network device when the UE completes the Attach procedure. This method includes the following steps:

[0123] S50: The UE sends an RRC Connection Request message to the eNB.

[0124] The UE initiates the Attach procedure and sends an MSG3 (RRC Connection Setup) message to the eNB.

[0125] S51: The eNB sends an RRC Connection Setup message to the UE.

[0126] The RRC Connection Setup message contains information about establishing the Signaling Radio Bearer (SRB) and radio resource configuration.

[0127] S52: The UE sends an RRC Connection SetupComplete message carrying an Attach Request message to the eNB.

[0128] After completing the SRB1 bearer and radio resource configuration, the UE sends an RRC Connection Setup Complete message to the eNB, which includes a NAS layer Attach Request message.

[0129] At this point, an RRC connection is established, and the UE is in the RRC_CONNECTED (connected) state.

[0130] S53: UE completes AS security activation.

[0131] The UE completes the Access Stratum (AS) security activation procedure.

[0132] S54: The eNB sends an Attach Accept message carrying the first configuration information to the UE.

[0133] In this implementation, the first configuration information is carried in the RRC message.

[0134] In one possible implementation, after the UE completes AS security activation, the eNB sends an RRC ConnectionReconfiguration message to the UE for UE resource reconfiguration, which carries an Attach Accept message.

[0135] The solution in this application embodiment adds configuration content related to the timer when retrying the Detach process to the Attach Accept message.

[0136] When the duration of the first timer is less than the duration of the T3421 timer, the first configuration information indicates the duration of the first timer, which can be represented by shortRetryTimer.

[0137] When the maximum allowed consecutive start count of the first timer is greater than the maximum allowed consecutive start count of the T3421 timer, the first configuration information indicates the maximum allowed consecutive start count of the first timer, which can be represented by shortRetryCnt.

[0138] The first configuration information can indicate one or more of shortRetryTimer and shortRetryCnt.

[0139] Furthermore, if adopted Figure 4In the implementation shown, when the cumulative number of failures in the Detach process reaches the maximum allowed number of consecutive starts of the first timer, the second timer needs to be started. At this time, the first configuration information also indicates the duration of the second timer, which can be represented by longRetryTimer.

[0140] In summary, by using the method provided in the embodiments of this application, the timer-related parameters during the Detach process retry can be configured in the Attach process of the terminal device, thus avoiding additional interactions between the terminal device and the base station.

[0141] As described in the above embodiments, when a UE initiates a Detach procedure, a network-side fault may cause the Detach procedure to fail. This application also provides a communication method for network optimization, which will be described in detail below with reference to the accompanying drawings.

[0142] See Figure 6 This figure is a flowchart of another communication method provided in an embodiment of this application.

[0143] S60: When the number of times the Detach process fails due to the first timer timeout reaches the first value, the failure information is recorded.

[0144] In this embodiment of the application, the UE has the ability to record NAS failure information. When the Detach process fails multiple times due to the expiration of the first timer, the UE can record the failure information locally.

[0145] In this application embodiment, the first numerical value is not specifically limited, and the first numerical value is a positive integer.

[0146] In one possible implementation, the first value can be equal to the maximum allowed number of consecutive starts for the first timer.

[0147] In another possible implementation, the first value can be another pre-set fixed value.

[0148] Taking the first value as an example where it equals the maximum allowed consecutive starts of the first timer, if the number of failures in the Detach process does not reach the first value, it indicates that the Detach process eventually successfully received a response, and failure information does not need to be recorded. When the number of failures in the Detach process reaches the first value, it means that the Detach process has reached the maximum number of retries, and failure information is recorded at this time.

[0149] The failure information in this application embodiment may include one or more of the following:

[0150] The timer name at which the timeout occurred, the Cell Global Identity (CGI) of the current cell, and the Physical Cell Identifier (PCI) of the current cell.

[0151] The name of the timer that timed out, which is also the name of the first timer.

[0152] In another possible implementation, the name of the timer that timed out can also be replaced with the reason for failure of the Detach process, which is that the first timer timed out.

[0153] In mobile communication systems such as LTE and 5G, PCI is used to uniquely identify the physical layer identifier of a cell. Terminal devices use PCI to distinguish the wireless signals of different cells.

[0154] CGI is used to identify the area covered by a cell (base station), and the CGI can be used to correspond to a base station. TAC is the tracking area identifier within the PLMN, used for UE location management, and is unique within the PLMN.

[0155] In one possible implementation, the failure information recorded by the UE can be called VarfailNas-Report.

[0156] S61: The UE sends an RRC Connection Request message to the eNB.

[0157] When the UE finds an available cell again, including but not limited to the cell where the Detach procedure failed, RRC establishment can proceed normally.

[0158] S62: The eNB sends an RRC Connection Setup message to the UE.

[0159] The RRC Connection Setup message contains information about establishing the Signaling Radio Bearer (SRB) and radio resource configuration.

[0160] S63: The UE sends an RRC Connection Setup Complete message carrying the first indication information to the eNB.

[0161] When a local failure message exists, the UE can send a first indication message to the eNB, indicating the existence of the failure message. This first indication message can be carried in an RRC message; specifically, it is carried in the Radio Resource Control (RRC) Connection Setup Complete message.

[0162] In one possible implementation, the first indication information can be an identifier indicating that the UE currently has failure information, such as the failNas-InfoAvailable flag, to instruct the eNB to query the UE for failure information.

[0163] S64: UE completes AS security activation.

[0164] The UE completes the security activation procedure.

[0165] S65: The UE receives the first request information.

[0166] The eNB can send a first request message to the UE, which is used to query failure information. The first request message can be carried in an RRC message; for example, an RRC message carrying the first request message can be called a UE InformationRequest message.

[0167] In one possible implementation, the first request information can be a flag indicating a failed query, for example, called failNas-ReportReq, which is set to true to instruct the eNB to query the UE for failure information.

[0168] S66: The UE sends a first response message carrying failure information.

[0169] The first response information is carried in the RRC message. For example, an RRC message carrying the first response information can be called UEInformation Response information.

[0170] S67: The eNB sends a report message containing failure information to the MME.

[0171] S68: The MME troubleshoots based on the failure information in all reported information.

[0172] The MME can receive reports from multiple eNBs.

[0173] In one possible implementation, the interface between the base station and the MME is S1-AP, and the reporting information can be carried in the S1-AP message.

[0174] To accurately identify the target network device, the failure information in this embodiment may simultaneously include the name of the timer that timed out (or replaced with the reason for failure), the CGI of the current cell, and the PCI of the current cell. After obtaining different failure information, the MME analyzes all the failure information and identifies the base stations where the Detach process fails as the target network device.

[0175] Then check if there is a fault in the S1 interface between the target network device and the MME, and determine why the target network device cannot attach.

[0176] Specifically, troubleshooting the S1 interface failure between the target network device and the MME is because an S1 interface failure may prevent the base station from receiving the S1AP message sent by the MME, that is, from receiving the Detach Accept message sent by the MME, thus causing the Detach process to fail.

[0177] Furthermore, if the S1 interface between the target network device and the MME is fault-free, the reason why the MME cannot register after receiving the Detach request should be further investigated, and the configuration should be modified in a timely manner. This application embodiment does not specifically limit the reasons for the Detach process failure; for example, it could be due to communication abnormalities on the base station side or the MME side deleting the established context between the UE and the MME.

[0178] In summary, the solution provided in this application adds a Minimization of Drive Test (MDT) mechanism for Detach process failure scenarios. This mechanism utilizes data reported by different UEs to proxy traditional drive test operations, automatically collecting terminal measurement data to detect and optimize problems and faults in the wireless network. Through network optimization, the probability of Detach process failure can be reduced, facilitating timely service recovery by terminal devices. Current related solutions lack an MDT reporting mechanism for Detach process failures, preventing targeted optimization on the network side.

[0179] It is understood that the optimization scheme in the embodiments of this application can also be applied to existing scenarios using the T3421 timer, that is... Figure 6S60 can be replaced with "When the number of times the UE fails to complete the Detach process due to the T3421 timer timeout reaches the first count, record the failure information," where the first count can be set to 5. In this case, the timer type in the recorded failure information is T3421, or the reason for the Detach process failure is recorded as T3421 timer timeout. Using the solution provided in this application embodiment, network optimization can also be achieved, reducing the probability of Detach process failures and facilitating timely service recovery for terminal devices.

[0180] Based on the communication methods provided in the above embodiments, this application also provides a network device, which will be described in detail below with reference to the accompanying drawings.

[0181] See Figure 7 This figure is a schematic diagram of a network device provided in an embodiment of this application.

[0182] The network device 50 includes a processor 51, a communication interface 52, a memory 53, and a bus 54. The number of processor 51, communication interface 52, and memory 53 can be one or more.

[0183] The processor 51 and memory 53 communicate with each other through bus 54, and the network device 50 communicates through communication interface 52.

[0184] Processor 51 may include one or more processing units, such as a modem processor, a baseband processor, etc. Different processing units may be independent devices or integrated into one or more processors. Processor 51 may also include memory for storing instructions and data.

[0185] In one possible implementation, the network device can be a base station, specifically an eNB. In this case, the processor 51 is used to call program instructions in the memory 53 to execute the communication method implemented by the base station side in the above embodiment.

[0186] In another possible implementation, the network device can be a mobility management entity (MME), in which case the processor 51 is used to call program instructions in the memory 53 to execute the communication method implemented by the MME side in the above embodiment.

[0187] See Figure 8 This figure is a schematic diagram of another network device provided in an embodiment of this application.

[0188] This network equipment can be a base station, core network unit, or other network devices.

[0189] Taking a network device as an example, the network device includes a processor 1110, a memory 1120, and a transceiver 1130.

[0190] The processor 1110 is mainly used for baseband processing and controlling the base station; the processor 1110 is usually the control center of the base station, used to control the base station to execute the communication methods in the above method embodiments.

[0191] The memory section 1120 is mainly used to store computer program code and data.

[0192] The transceiver 1130 section is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals to baseband signals; the transceiver 1130 section is also commonly referred to as a transceiver module, transceiver, transceiver circuit, etc.

[0193] The network device also includes an antenna 1133 and radio frequency (RF) circuitry (not shown in the figure), where the RF circuitry is mainly used for RF processing. Optionally, the device in the transceiver 1130 section used to implement the receiving function can be regarded as a receiver 1032, and the device used to implement the transmitting function can be regarded as a transmitter 1031; that is, the transceiver 1130 includes a receiver 1132 and a transmitter 1131. The receiver 1032 can also be called a receiving module, receiver, or receiving circuit, etc., and the transmitter 1131 can be called a transmitting module, transmitter, or transmitting circuit, etc.

[0194] The processor 1110 section and the memory 1120 section may include one or more circuit boards, each circuit board may include one or more processors and one or more memories. The processor is used to read and execute programs in the memory to implement baseband processing functions and control the base station. If multiple circuit boards exist, they can be interconnected to enhance processing capabilities. As an optional implementation, multiple circuit boards may share one or more processors, multiple circuit boards may share one or more memories, or multiple circuit boards may simultaneously share one or more processors.

[0195] For example, in one implementation, transceiver 1130 is used to perform the process of sending and receiving related information executed by the network device in the aforementioned method embodiments. The processor in the processor 1110 portion is used to perform the process of processing related information executed by the network device in the aforementioned method embodiments.

[0196] It should be understood that Figure 8 The network device described above, including processor 1110, memory 1120, and transceiver 1130, is optional and not limiting. Figure 8 The structure shown.

[0197] Based on the communication methods provided in the above embodiments, this application also provides a terminal device.

[0198] See Figure 9 The figure is a schematic diagram of a terminal device provided in an embodiment of this application.

[0199] The terminal device 60 includes a processor 61, a communication interface 62, a memory 63, and a bus 64. The number of processor 61, communication interface 62, and memory 63 can be one or more.

[0200] The processor 61 and memory 63 communicate with each other via bus 64, and the terminal device 60 communicates with the network device via communication interface 62.

[0201] Processor 61 may include one or more processing units, such as a modem processor, a baseband processor, etc. Different processing units may be independent devices or integrated into one or more processors. Processor 61 may also include memory for storing instructions and data.

[0202] The processor 61 is used to call program instructions in the memory 63 to execute the above-described communication method.

[0203] Terminal devices 60 can be mobile phones, tablets, computers with wireless transceiver capabilities, VR terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, vehicle-mounted terminal devices, wireless terminals in autonomous driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, wearable terminal devices, and so on.

[0204] Furthermore, embodiments of this application also provide a computer-readable storage medium storing a program that, when executed by a processor, implements the communication method provided in the above embodiments.

[0205] This application also provides a communication system that may include the network devices and terminal devices described above.

[0206] Computer-readable storage media include both permanent and non-permanent, removable and non-removable media, and can be implemented using any method or technology to store information. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically-erasable programmable read-only memory (EEPROM), flash memory, or other memory technologies.

[0207] Specifically, the computer-readable storage medium includes program instructions that instruct an electronic device to perform the aforementioned communication method, or instruct a network device to perform the aforementioned communication method.

[0208] This application also provides a computer program product containing instructions. The computer program product may be a software or program product containing instructions, capable of running on a terminal device or stored on any usable medium. When the computer program product runs on a terminal device, it causes the terminal device to perform the aforementioned communication method; or, when the computer program product runs on a network device, it causes the network device to perform the aforementioned communication method.

[0209] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0210] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A communication method, characterized in that, The method includes: When a Detach procedure is initiated, a first timer is started. The duration of the first timer is less than the duration of the T3421 timer, and / or the maximum allowed number of consecutive starts of the first timer is greater than the maximum allowed number of consecutive starts of the T3421 timer. If a Detach Accept message is not received before the first timer expires, the Detach procedure fails. After the first timer expires, the Detach procedure can be re-initiated. When the number of consecutive starts of the first timer reaches the maximum allowed number of consecutive starts of the first timer, the Detach process is terminated.

2. The method according to claim 1, characterized in that, The termination of the Detach process includes: Start a second timer with a duration longer than the first timer. When the second timer expires, the Detach process can be re-initiated.

3. The method according to claim 2, characterized in that, The duration of the second timer is greater than the duration of the T3421 timer.

4. The method according to claim 1, characterized in that, Before starting the first timer when initiating the detach process, the method further includes: Receive first configuration information, which indicates the duration of the first timer and / or the maximum number of consecutive starts allowed for the first timer.

5. The method according to claim 2, characterized in that, Before starting the first timer when initiating the detach process, the method further includes: Receive first configuration information, the first configuration information indicating the duration of the first timer, and / or the maximum number of consecutive starts allowed for the first timer; the first configuration information also indicates the duration of the second timer.

6. The method according to claim 4 or 5, characterized in that, The first configuration information is carried in the Attach Accept message.

7. The method according to claim 1, characterized in that, The method further includes: When the first timer times out and the number of consecutive failures of the Detach process reaches a first value, failure information is recorded, which includes one or more of the following: The timer name at which the timeout occurred, the current cell global identifier (CGI), and the current cell physical identifier (PCI).

8. The method according to claim 7, characterized in that, The method further includes: When the failure information exists locally, a first indication information is sent, indicating that the failure information exists.

9. The method according to claim 8, characterized in that, The first indication information is carried in the Radio Resource Control (RRC) Connection Setup Complete message.

10. The method according to claim 9, characterized in that, The method further includes: When a first request is received, a first response is sent carrying the failure information, wherein the first request is used to query the failure information.

11. A communication method, characterized in that, The method includes: Send first configuration information, which indicates the duration of the first timer and / or the maximum number of consecutive starts allowed for the first timer; If the terminal device does not receive a Detach Accept message before the first timer expires, the Detach process fails. After the first timer expires, the Detach process can be re-initiated. When the number of consecutive starts of the first timer reaches the maximum allowed number of consecutive starts of the first timer, the Detach process is terminated.

12. The method according to claim 11, characterized in that, The first configuration information also indicates the duration of the second timer. The second timer starts when the number of consecutive starts of the first timer reaches the maximum allowed number of consecutive starts of the first timer. The duration of the second timer is longer than the duration of the first timer. When the second timer times out, the Detach process can be re-initiated.

13. The method according to claim 12, characterized in that, The duration of the second timer is greater than the duration of the T3421 timer.

14. The method according to claim 11, characterized in that, The method further includes: When the first indication information is received, the first request information is sent. The first indication information indicates that there is failure information. The first request information is used to query the failure information. When the number of consecutive failures of the Detach process caused by the first timer timeout reaches a first value, the failure information includes one or more of the following: the name of the timer that timed out, the Cell Global Identifier (CGI) of the current cell, and the Physical Cell Identifier (PCI) of the current cell. Receive a first response message, which carries the failure information.

15. The method according to claim 14, characterized in that, The first request information is carried in the Radio Resource Control (RRC) message.

16. The method according to claim 14, characterized in that, After receiving the first response information, the method further includes: Send a report containing the failure information to the Mobility Management Entity (MME).

17. A communication method, characterized in that, The method includes: Receive report information sent by one or more network devices. The report information carries failure information. When the number of consecutive failures of the Detach process caused by the first timer timeout reaches a first value, the failure information includes one or more of the following: the name of the timer that timed out, the Cell Global Identifier (CGI) of the current cell, and the Physical Cell Identifier (PCI) of the current cell. Troubleshoot based on the failure information in all the reported information.

18. The method according to claim 17, characterized in that, The failure information includes the name of the timer that timed out, the Cell Global Identifier (CGI) of the current cell, and the Physical Cell Identifier (PCI) of the current cell. The troubleshooting based on the failure information in all the reported information specifically includes: Based on the failure information provided, the base stations where the Detach process failed in a concentrated manner were identified as the target network devices. Investigate whether there is a fault in the S1 interface between the target network device and the Mobility Management Entity (MME), and determine the reason for the failure to detach.

19. A network device, characterized in that, Including processor and memory; The processor is coupled to the memory; The memory is used to store instructions; The processor is used to execute computer programs or instructions stored in the memory to implement the communication method as described in any one of claims 11 to 16.

20. A network device, characterized in that, Including processor and memory; The processor is coupled to the memory; The memory is used to store instructions; The processor is used to execute computer programs or instructions stored in the memory to implement the communication method as described in any one of claims 17 to 18.

21. A terminal device, characterized in that, Including processor and memory; The processor is coupled to the memory; The memory is used to store instructions; The processor is used to execute computer programs or instructions stored in the memory to implement the communication method as described in any one of claims 1 to 10.

22. A computer-readable storage medium for storing a computer program, which, when executed, is used to implement the method of any one of claims 1 to 10, or to implement the method of any one of claims 11 to 16, or to implement the method of any one of claims 17 to 18.

23. A computer program product, characterized in that, Includes instructions that, when executed, are used to implement the method of any one of claims 1 to 10, or to implement the method of any one of claims 11 to 16, or to implement the method of any one of claims 17 to 18.

Images