CN114650578B - Terminal voice service connection method, device, equipment and storage medium - Google Patents

Terminal voice service connection method, device, equipment and storage medium Download PDF

Info

Publication number
CN114650578B
CN114650578B CN202210419131.8A CN202210419131A CN114650578B CN 114650578 B CN114650578 B CN 114650578B CN 202210419131 A CN202210419131 A CN 202210419131A CN 114650578 B CN114650578 B CN 114650578B
Authority
CN
China
Prior art keywords
attach request
cell
delay timer
timer
voice service
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.)
Active
Application number
CN202210419131.8A
Other languages
Chinese (zh)
Other versions
CN114650578A (en
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.)
China Telecom Corp Ltd
Original Assignee
China Telecom Corp 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 China Telecom Corp Ltd filed Critical China Telecom Corp Ltd
Priority to CN202210419131.8A priority Critical patent/CN114650578B/en
Publication of CN114650578A publication Critical patent/CN114650578A/en
Application granted granted Critical
Publication of CN114650578B publication Critical patent/CN114650578B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/24Reselection being triggered by specific parameters
    • H04W36/30Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/305Handover due to radio link failure

Landscapes

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

Abstract

The disclosure provides a terminal voice service connection method, and relates to the technical field of communication. The method comprises the following steps: initiating an initial access procedure in a first cell; initiating an attachment request flow in a first cell, and completing the release of a terminal context message by a base station when the attachment request fails in the attachment request flow; if it is determined that the attachment request can be reinitiated, starting a preset delay timer, and reinitiating the attachment request flow in the first cell when the delay timer is overtime; when the attach request fails, restarting the delay timer, and repeating the steps until the number of times of restarting the attach request flow reaches a preset number of times. Wherein the time delay timer is increased from the last time after each attach request failure. According to the method, the starting time of the timer T3402 (default 12 min) is prolonged through the delay timer, and the probability that the terminal cannot fall back to the LTE through the EPS FB mode to use the VoLTE voice service is reduced.

Description

Terminal voice service connection method, device, equipment and storage medium
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a computer readable storage medium for connecting a terminal voice service.
Background
At present, a China telecom SA (independent networking) network does not support voice service VoNR (Voice Over NR) running in a 5G frequency band temporarily, and when a 5G terminal user has voice requirements, the voice service needs to be completed by an EPS FB mode and an LTE (Long Term Evolution ) network in a VoLTE mode. The EPS FB refers to that, when the 5G does not have the VoNR condition, the voice service falls back from the 5G to the 4G, and relies on VoLTE (Voice over LTE) to ensure the continuity of the voice service.
Currently, in the existing LTE network, when a 5G terminal performs LTE network attachment (Attach), after the attachment fails 5 times due to poor cell signal or temporary cell failure, according to protocol planning, the terminal starts a T3402 timer (default 12 minutes), and the terminal can be restarted after temporarily closing the LTE module for 12 minutes. If the terminal successfully attaches to the SA network within 12 minutes, the LTE signal in the area is improved or the temporary fault cell is recovered. However, at this time, since the LTE module of the terminal is turned off, the terminal cannot fall back to LTE through the EPS FB mode to use the VoLTE voice service.
It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
An object of the present disclosure is to provide a terminal voice service connection method, apparatus, device, and storage medium for overcoming one or more of the problems due to the limitations and disadvantages of the related art, at least to some extent.
According to a first aspect of an embodiment of the present disclosure, there is provided a terminal voice service connection method, including:
initiating an initial access procedure in a first cell, wherein the initial access procedure completes a base station to send a Radio Resource Control (RRC) connection establishment message to a terminal, and the message comprises signaling bearing establishment information and radio resource configuration information;
initiating an attach request flow in the first cell, wherein the attach request flow finishes releasing a terminal context message by a base station when the attach request fails;
in one cycle, the following steps are performed:
if it is determined that the attach request can be reinitiated, starting a predetermined delay timer, wherein the delay timer is configured to:
delay timer = first timer + n x M;
in the delay timer, n represents the number of times of reinitiating the attachment request flow, and n is more than or equal to 0; m represents a delay time unit;
reinitiating the attach request flow in the first cell when the delay timer expires;
and when the attach request fails, repeatedly executing the steps in the loop until the number of times of reinitiating the attach request flow reaches a preset number of times.
In an exemplary embodiment of the present disclosure, after the number of times of reinitiating the attach request procedure reaches a predetermined number of times in the first cell, if the attach request fails, the method further includes the following steps:
acquiring a second cell;
initiating the initial access procedure in the second cell;
initiating the attach request procedure at the second cell;
in one cycle, the following steps are performed:
if it is determined that the attachment request can be reinitiated, starting the delay timer;
reinitiating the attach request flow in the second cell when the delay timer expires;
and when the attach request fails, repeatedly executing the steps in the loop until the number of times of reinitiating the attach request flow reaches a preset number of times.
In an exemplary embodiment of the present disclosure, after the number of times of reinitiating the attach request procedure reaches a predetermined number of times in the second cell, if the attach request fails, the method further includes the steps of:
a second timer is started.
In one exemplary embodiment of the present disclosure, the second timer is configured as a T3402 timer.
In one exemplary embodiment of the present disclosure, the first timer is configured as a T3411 timer.
In one exemplary embodiment of the present disclosure, the delay time unit M is 5 to 20s.
According to a second aspect of the embodiments of the present disclosure, there is provided a terminal voice service connection device, including:
the first initial access module is used for initiating an initial access flow in a first cell, wherein the initial access flow finishes that a base station sends an RRC connection establishment message to a terminal, and the establishment of SRB1 signaling bearing information and radio resource configuration information is included;
the first attach request module is used for initiating an attach request flow in the first cell, and the attach request flow finishes releasing a terminal context message by the base station when the attach request fails;
the first delay module is used for executing the following steps in one cycle: if it is determined that the attach request can be reinitiated, starting a predetermined delay timer, wherein the delay timer is configured to:
delay timer = first timer + n x M;
in the delay timer, n represents the number of times of reinitiating the attachment request flow, and n is more than or equal to 0; m represents a delay time unit;
a first reinitiation module, configured to reinitiate the attach request procedure in the first cell when the delay timer expires;
and the first repeated execution module is used for repeatedly executing the steps in the loop when the attach request fails until the number of times of reinitiating the attach request flow reaches a preset number of times.
In an exemplary embodiment of the present disclosure, the terminal voice service connection apparatus further includes:
the second cell acquisition module is used for acquiring a second cell if the attachment request fails after the number of times of reinitiating the attachment request flow reaches the preset number of times in the first cell;
a second initial access module, configured to initiate the initial access procedure in the second cell;
a second attach request module, configured to initiate the attach request procedure in the second cell;
the second delay module is used for executing the following steps in one cycle: if it is determined that the attachment request can be reinitiated, starting the delay timer;
a second reinitiation module, configured to reinitiate the attach request procedure in the second cell when the delay timer expires;
and the second repeated execution module is used for repeatedly executing the steps in the loop until the number of times of reinitiating the attach request flow reaches a preset number of times when the attach request fails.
According to a third aspect of embodiments of the present disclosure, there is provided an electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the terminal voice service connection method according to any one of the preceding claims via execution of the executable instructions.
According to a fourth aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the terminal voice service connection method according to any one of the above.
The method, the device, the equipment and the readable storage medium for connecting the terminal voice service start a delay timer when the attachment request fails, wherein the delay timer is configured as a first timer plus n multiplied by M. The timing time of the delay timer is adjusted by the number n of reinitiations of the attach request, and the timing time of the delay timer is increased compared with the last time. Through the setting, the waiting time after each attachment request failure is prolonged compared with the last waiting time, so that the starting time of a timer T3402 (default 12 min) is prolonged, the probability that the terminal cannot fall back to LTE through an EPS FB mode to use VoLTE voice service is reduced, and user experience is effectively improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort.
Fig. 1 schematically shows a flow chart of an LTE attachment procedure in the related art.
Fig. 2 schematically illustrates a flowchart of a terminal voice service connection method in one example of the present disclosure.
Fig. 3 schematically illustrates a flowchart of a terminal voice service connection method in another exemplary embodiment of the present disclosure.
Fig. 4 schematically illustrates a flowchart of a specific scenario of a terminal voice service connection method in one of the exemplary embodiments of the present disclosure.
Fig. 5 schematically illustrates a schematic diagram of a terminal voice service apparatus in an exemplary embodiment of the present disclosure.
Fig. 6 schematically illustrates a schematic diagram of a terminal voice service apparatus in another exemplary embodiment of the present disclosure.
Fig. 7 schematically illustrates a block diagram of an electronic device in an exemplary embodiment of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the present disclosure. One skilled in the relevant art will recognize, however, that the aspects of the disclosure may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.
Furthermore, the drawings are only schematic illustrations of the present disclosure, in which the same reference numerals denote the same or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.
In the related art, the attachment flow of the LTE network is shown in fig. 1, and specifically includes:
1) The UE (terminal) transmits a random access Preamble (Preamble symbol), i.e., an Msg1 message. The Preamble is used to identify the UE identity.
2) After detecting the Msg1 message, the eNB (base station) sends a random access response message, i.e. an Msg2 message, to the UE.
3) After receiving the random access response, the UE adjusts the uplink transmission timing according to the TA (Tracking Area) of Msg2, and transmits RRC Connection Request message to the eNB to apply for establishing RRC connection.
The RRC Connection Request message is a radio resource control connection message.
4) The eNB sends RRC Connection Setup a message to the UE containing the setup SRB1 signaling bearer information and radio resource configuration information. SRB1 is a communication interface between an LTE eNB and an EPC (core network).
The RRC Connection Setup message is a radio resource control connection establishment message.
5) The UE completes SRB1 signaling bearer and radio resource configuration, and sends RRC Connection Setup Complete a message to the eNB, including a NAS layer (non-access stratum) Attach request message.
The RRC Connection Setup Complete message is a radio resource control connection establishment completion message; the Attach request message is an Attach request message.
6) The eNB selects MME (mobility management entity), sends INITIAL UE MESSAGE message to MME requesting to establish default bearer, including NAS layer attach request message.
Wherein the INITIAL UE MESSAGE message is an initial context setup request message.
7) The MME or S-GW (Serving gateway) refuses the attach request. The network cannot accept the Attach request, and the Attach request is refused due to reasons such as failure of default EPS bearer setting, failure of ESM procedure, and the like.
8) The core network sends a message containing the Attach reject or PDN connectivity reject to the eNB.
Wherein the PDN connectivity reject message is a PDN connection reject message.
9) The eNB transmits a message containing the Attach reject or PDN connectivity reject to the UE.
10 MME sends UE CONTEXT RELEASE COMMAND message to eNB requesting eNB release UE context information.
Wherein the UE CONTEXT RELEASE COMMAND message is a UE context release command message.
11 The eNB sends RRC Connection Release a message to the UE, releasing the RRC connection.
The RRC Connection Release message is a radio resource control connection release message.
12 The eNB receives UE CONTEXT RELEASE COMMAND message, releases the UE context information, and sends UE CONTEXT RELEASE COMPLETE a message to the MME for response.
13 If it is available for retransmission, a T3411 timer is started.
The T3411 timer is a NAS (non access stratum) timer, and the timer length defaults to 10s, and starts when the attach request fails.
14 When timer T3411 expires, the attach request is resent.
15 5 times the attach request fails, the T3402 timer is started.
The T3402 timer starts when 5 attach request failures, the timer length defaults to 12min.
When the terminal repeats the attachment failure in one cell for five times, the T3402 timer is started, and the terminal temporarily closes the LTE module, so that the LTE network is not available within 12 minutes. If the terminal successfully attaches to the SA network within 12 minutes, the LTE signal in the area is improved or the temporary fault cell is recovered. However, at this time, since the LTE module of the terminal is turned off, the terminal cannot fall back to LTE through the EPS FB mode to use the VoLTE voice service. Based on the above-mentioned problems, the embodiment of the present disclosure proposes a terminal voice service connection method 200.
The following describes example embodiments of the present disclosure in detail with reference to the accompanying drawings.
Fig. 2 schematically illustrates a flowchart of a terminal voice service connection method 200 in an exemplary embodiment of the present disclosure. Referring to fig. 2, the terminal voice service connection method 200 may include:
step S201, initiating an initial access flow in a first cell, wherein the initial access flow finishes a base station to send a Radio Resource Control (RRC) connection establishment message to a terminal, and the message comprises establishment signaling bearing information and radio resource configuration information;
step S202, initiating an attachment request flow in the first cell, wherein the attachment request flow finishes releasing a terminal context message by a base station when the attachment request fails;
step S203, in one cycle, the following steps are performed:
if it is determined that the attach request can be reinitiated, starting a predetermined delay timer, wherein the delay timer is configured to:
delay timer = first timer + n x M;
in the delay timer, n represents the number of times of reinitiating the attachment request flow, and n is more than or equal to 0; m represents a delay time unit;
step S204, when the delay timer expires, the attachment request flow is reinitiated in the first cell;
step S205, when the attach request fails, repeatedly executing the steps in the loop until the number of times of reinitiating the attach request flow reaches a preset number of times.
According to the terminal voice service connection method, when an attachment request fails, a delay timer is started, and the delay timer is configured to be a first timer plus n multiplied by M. The timing time of the delay timer is adjusted by the number n of reinitiations of the attach request, and the timing time of the delay timer is increased compared with the last time. Through the setting, the waiting time after each attachment request failure is prolonged compared with the last waiting time, so that the starting time of a timer T3402 (default 12 min) is prolonged, the probability that the terminal cannot fall back to LTE through an EPS FB mode to use VoLTE voice service is reduced, and user experience is effectively improved.
Next, each step of the terminal voice service connection method 200 will be described in detail.
Step S201, initiating an initial access procedure in a first cell, where the initial access procedure completes a base station sending a radio resource control RRC connection establishment message to a terminal, including establishing signaling bearer information and radio resource configuration information.
In an exemplary embodiment of the present disclosure, a terminal initiates an initial access procedure in a first cell, where the initial access procedure completes steps 1) to 4) shown in fig. 1, and specifically includes the following steps:
1) The UE (terminal) transmits a random access Preamble (Preamble symbol), i.e., an Msg1 message. The Preamble is used to identify the UE identity.
2) After detecting the Msg1 message, the eNB (base station) sends a random access response message, i.e. an Msg2 message, to the UE.
3) After receiving the random access response, the UE adjusts the uplink transmission timing according to the TA (Tracking Area) of Msg2, and transmits RRC Connection Request message to the eNB to apply for establishing RRC connection.
4) The eNB sends RRC Connection Setup a message to the UE containing the setup SRB1 signaling bearer information and radio resource configuration information. SRB1 is a communication interface between an LTE eNB and an EPC (core network).
Step S202, an attachment request flow is initiated in the first cell, and when the attachment request fails, the attachment request flow finishes releasing the terminal context message by the base station.
In an exemplary embodiment of the present disclosure, a terminal initiates an attach request procedure in a first cell, where the attach request procedure completes steps 5) to 12) shown in fig. 1, specifically as follows:
5) The UE completes SRB1 signaling bearer and radio resource configuration, and sends RRC Connection Setup Complete a message to the eNB, including a NAS layer (non-access stratum) Attach request message.
6) The eNB selects MME (mobility management entity), sends INITIAL UE MESSAGE message to MME requesting to establish default bearer, including NAS layer Attach request message.
7) The MME or S-GW (Serving gateway) refuses the attach request.
8) The core network sends a message containing the Attach reject or PDN connectivity reject to the eNB.
9) The eNB transmits a message containing the Attach reject or PDN connectivity reject to the UE.
10 MME sends UE CONTEXT RELEASE COMMAND message to eNB requesting eNB release UE context information.
11 The eNB sends RRC Connection Release a message to the UE, releasing the RRC connection.
12 The eNB receives UE CONTEXT RELEASE COMMAND message, releases the UE context information, and sends UE CONTEXT RELEASE COMPLETE a message to the MME for response.
Step S203, in one cycle, the following steps are performed:
if it is determined that the attach request can be reinitiated, starting a predetermined delay timer, wherein the delay timer is configured to:
delay timer = first timer + n x M;
in the delay timer, n represents the number of times of reinitiating the attachment request flow in the first cell, and n is more than or equal to 0; m represents a delay time unit.
Specifically, the number of times the attach request flow is reinitiated n=0, 1, 2, 3, 4, 5 …. For example, when the first attach request fails, a delay timer=first timer+n×m is started, where n=0; when the second attach request fails, starting a delay timer=first timer+n×m, where n=1; and so on, so that the time length of the delay timer is sequentially increased when each attachment request fails.
In an exemplary embodiment of the present disclosure, the first timer is configured as a T3411 timer. The timer length of the T3411 timer defaults to 10s.
In an exemplary embodiment of the present disclosure, the delay time unit M of the delay timer is 5 to 20s. M may be, for example, 5s, 10s, 15s, 20s, etc., and is not particularly limited in the disclosure.
Step S204, when the delay timer expires, the attach request procedure is reinitiated in the first cell.
Specifically, step S204 is specifically: when the delay timer expires, the terminal completes steps 5) to 12) as shown in fig. 1 in the first cell.
Step S205, when the attach request fails, repeatedly executing the steps in the loop until the number of times of reinitiating the attach request flow reaches a preset number of times.
Specifically, in step S205, when the attach request fails, the above steps S203 to S204 are repeatedly performed until the number of times of restarting the attach request flow reaches a predetermined number of times. The predetermined number of times may be, for example, 1 time, 2 times, 3 times, 4 times, 5 times, or the like.
In an exemplary embodiment of the present disclosure, referring to fig. 3, after the number of times of reinitiating the attach request procedure reaches a predetermined number of times, if the attach request fails, the method further includes:
step S301, a second cell is acquired. The second cell is acquired by re-searching the network.
Step S302, initiating the initial access procedure in the second cell.
Specifically, the initial access flow refers to steps 1) to 4) shown in fig. 1.
Step S303, initiating the attach request procedure in the second cell.
Specifically, the attach request flow refers to steps 5) to 12) shown in fig. 1.
Step S304, in one cycle, the following steps are performed:
and if the adhesion request can be reinitiated, starting the delay timer.
Specifically, the delay timer is configured to:
delay timer = first timer + n x M;
in the delay timer, n represents the number of times of reinitiating the attachment request flow in a second cell, wherein n is more than or equal to 0; m represents a delay time unit;
step S305, when the delay timer expires, re-initiating the attach request procedure in the second cell.
Specifically, the attach request flow refers to steps 5) to 12) shown in fig. 1.
Step S306, when the attach request fails, repeating the steps in the loop until the number of times of reinitiating the attach request flow reaches a predetermined number of times.
Specifically, in step S306, when the attach request fails, steps S304 to S305 are repeatedly executed until the number of times of reinitiating the attach request flow reaches a predetermined number of times. The predetermined number of times may be, for example, 1 time, 2 times, 3 times, 4 times, 5 times, or the like.
In an exemplary embodiment of the present disclosure, after the number of times of reinitiating the attach request procedure reaches a predetermined number of times in the second cell, if the attach request fails, the method further includes the steps of:
step S307, a second timer is started.
Specifically, the second timer is configured as a T3402 timer.
In one specific scenario of the present disclosure, as shown in fig. 4, the delay time unit M is configured to be 10s, and the delay timer is configured as follows: delay timer=t3411+n×10s. The terminal voice service connection process is as follows:
1. performing an initial access procedure in cell 1 (first cell);
2. performing an attach request flow in cell 1, wherein the first attach request fails;
3. if retransmission is possible, the delay timer T3411 (10 s) +n×10s is started, n=0;
4. when the delay timer times out, resending an attach request;
5. performing an attach request flow in the cell 1, wherein the second attach request fails;
6. if retransmission is possible, the delay timer T3411 (10 s) +n×10s is started, n=1;
7. when the delay timer times out, resending an attach request;
8. performing an attach request flow in the cell 1, wherein the third attach request fails;
9. after the attach request fails, searching the network again to obtain a cell 2 (a second cell);
10. performing an initial access flow in the cell 2;
11. performing an attach request flow in cell 2, wherein the first attach request fails;
12. if retransmission is possible, the delay timer T3411 (10 s) +n×10s is started, n=0;
13. when the delay timer times out, resending an attach request;
14. performing an attach request flow in the cell 2, wherein the second attach request fails;
15. if retransmission is possible, the delay timer T3411 (10 s) +n×10s is started, n=1;
16. when the delay timer times out, resending an attach request;
17. performing an attach request flow in the cell 2, wherein the third attach request fails;
18. steps 16-17 are repeated until 5 attach request failures, starting the T3402 timer (12 min default).
Fig. 5 schematically illustrates a schematic diagram of a terminal voice service connection device in an exemplary embodiment of the present disclosure. Referring to fig. 5, a terminal voice service connection apparatus 500 includes:
a first initial access module 510, configured to initiate an initial access procedure in a first cell, where the initial access procedure completes sending, by a base station, an RRC connection establishment message to a terminal, including establishing SRB1 signaling bearer information and radio resource configuration information;
a first attach request module 520, configured to initiate an attach request procedure in the first cell, where the attach request procedure completes releasing a terminal context message by a base station when an attach request fails;
a first delay module 530, configured to perform the following steps in one cycle: if it is determined that the attach request can be reinitiated, starting a predetermined delay timer, wherein the delay timer is configured to:
delay timer = first timer + n x M;
in the delay timer, n represents the number of times of reinitiating the attachment request flow, and n is more than or equal to 0; m represents a delay time unit;
a first reinitiation module 540, configured to reinitiate the attach request procedure in the first cell when the delay timer expires;
the first repeat execution module 550 is configured to repeatedly execute the steps in the loop until the number of times of reinitiating the attach request process reaches a predetermined number of times when the attach request fails.
The terminal voice service connecting device of the embodiment of the disclosure starts a delay timer when an attachment request fails, and the delay timer is configured as a first timer +n×m. The timing time of the delay timer is adjusted by the number n of reinitiations of the attach request, and the timing time of the delay timer is increased compared with the last time. Through the setting, the waiting time after each attachment request failure is prolonged compared with the last waiting time, so that the starting time of a timer T3402 (default 12 min) is prolonged, the probability that the terminal cannot fall back to LTE through an EPS FB mode to use VoLTE voice service is reduced, and user experience is effectively improved.
In an exemplary embodiment of the present disclosure, referring to fig. 6, the terminal voice service connection device further includes:
a second cell obtaining module 610, configured to obtain a second cell if the attach request fails after the number of times of reinitiating the attach request procedure reaches a predetermined number of times in the first cell;
a second initial access module 620, configured to initiate the initial access procedure in the second cell;
a second attach request module 630, configured to initiate the attach request procedure in the second cell;
a second delay module 640, configured to perform the following steps in one cycle: if it is determined that the attachment request can be reinitiated, starting the delay timer;
a second reinitiation module 650, configured to reinitiate the attach request procedure in the second cell when the delay timer expires;
the second repeat execution module 660 is configured to repeatedly execute the steps in the loop until the number of times of reinitiating the attach request procedure reaches a predetermined number of times when the attach request fails.
In an embodiment of the present disclosure, the terminal voice service connection device 500 may further include modules that implement other flow steps of the above-described processing method embodiments. The specific principles of the respective modules and sub-modules may be referred to the above description of the embodiment of the terminal voice service connection method 200, and will not be repeated here.
Since each function of the voice service connection device 500 of the terminal is described in detail in the corresponding method embodiment, the disclosure is not repeated here.
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.
Those skilled in the art will appreciate that the various aspects of the invention may be implemented as a system, method, or program product. Accordingly, aspects of the invention may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system.
An electronic device 700 according to this embodiment of the invention is described below with reference to fig. 7. The electronic device 700 shown in fig. 7 is merely an example, and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.
As shown in fig. 7, the electronic device 700 is embodied in the form of a general purpose computing device. Components of electronic device 700 may include, but are not limited to: the at least one processing unit 710, the at least one memory unit 720, and a bus 730 connecting the different system components, including the memory unit 720 and the processing unit 710.
Wherein the storage unit stores program code that is executable by the processing unit 710 such that the processing unit 710 performs steps according to various exemplary embodiments of the present invention described in the above-mentioned "exemplary methods" section of the present specification.
For example, in one embodiment of the present disclosure, the processing unit 710 may perform the base station sending a radio resource control RRC connection setup message to the terminal as shown in fig. 1, including setup signaling bearer information and radio resource configuration information; step S102, initiating an attachment request flow in the first cell, wherein the attachment request flow finishes releasing a terminal context message by a base station when the attachment request fails; in one cycle, the following steps are performed: step S104, if it is determined that the attach request can be reinitiated, starting a predetermined delay timer, where the delay timer is configured to: delay timer = first timer + n x M; in the delay timer, n represents the number of times of reinitiating the attachment request flow, and n is more than or equal to 0; m represents a delay time unit; step S105, when the delay timer expires, the attachment request flow is reinitiated in the first cell; and step S106, when the attach request fails, repeatedly executing the steps in the loop until the number of times of reinitiating the attach request flow reaches a preset number of times.
The memory unit 720 may include readable media in the form of volatile memory units, such as Random Access Memory (RAM) 7201 and/or cache memory 7202, and may further include Read Only Memory (ROM) 7203.
The storage unit 720 may also include a program/utility 7204 having a set (at least one) of program modules 7205, such program modules 7205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
Bus 730 may be a bus representing one or more of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.
The electronic device 700 may also communicate with one or more external devices 800 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 700, and/or any device (e.g., router, modem, etc.) that enables the electronic device 700 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 750. Also, electronic device 700 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, through network adapter 760. As shown, network adapter 760 communicates with other modules of electronic device 700 over bus 730. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 700, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (may be a personal computer, a server, a terminal device, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.
In an exemplary embodiment of the present disclosure, a computer-readable storage medium having stored thereon a program product capable of implementing the method described above in the present specification is also provided. In some possible embodiments, the various aspects of the invention may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the steps according to the various exemplary embodiments of the invention as described in the "exemplary methods" section of this specification, when said program product is run on the terminal device.
The program product for implementing the above-described method according to an embodiment of the present invention may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may be run on a terminal device such as a personal computer. However, the program product of the present invention is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
Furthermore, the above-described drawings are only schematic illustrations of processes included in the method according to the exemplary embodiment of the present invention, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

Claims (10)

1. A terminal voice service connection method, comprising:
initiating an initial access procedure in a first cell, wherein the initial access procedure completes a base station to send a Radio Resource Control (RRC) connection establishment message to a terminal, and the message comprises signaling bearing establishment information and radio resource configuration information;
initiating an attach request flow in the first cell, wherein the attach request flow finishes releasing a terminal context message by a base station when the attach request fails;
in one cycle, the following steps are performed:
if it is determined that the attach request can be reinitiated, starting a predetermined delay timer, wherein the delay timer is configured to:
delay timer = first timer + n x M;
in the delay timer, n represents the number of times of reinitiating the attachment request flow, and n is more than or equal to 0; m represents a delay time unit;
reinitiating the attach request flow in the first cell when the delay timer expires;
and when the attach request fails, repeatedly executing the steps in the loop until the number of times of reinitiating the attach request flow reaches a preset number of times.
2. The terminal voice service connection method according to claim 1, wherein after the number of times of reinitiating the attach request procedure reaches a predetermined number of times in the first cell, if the attach request fails, further comprising the steps of:
acquiring a second cell;
initiating the initial access procedure in the second cell;
initiating the attach request procedure at the second cell;
in one cycle, the following steps are performed:
if it is determined that the attachment request can be reinitiated, starting the delay timer;
reinitiating the attach request flow in the second cell when the delay timer expires;
and when the attach request fails, repeatedly executing the steps in the loop until the number of times of reinitiating the attach request flow reaches a preset number of times.
3. The terminal voice service connection method according to claim 2, wherein after the number of times of reinitiating the attach request procedure reaches a predetermined number of times in the second cell, if the attach request fails, further comprising the steps of:
a second timer is started.
4. The terminal voice service connection method according to claim 3, wherein the second timer is configured as a T3402 timer.
5. The terminal voice service connection method according to claim 1, wherein the first timer is configured as a T3411 timer.
6. The terminal voice service connection method according to claim 1, wherein the delay time unit M is 5-20 s.
7. A terminal voice service connection device, comprising:
the first initial access module is used for initiating an initial access flow in a first cell, wherein the initial access flow finishes that a base station sends an RRC connection establishment message to a terminal, and the establishment of SRB1 signaling bearing information and radio resource configuration information is included;
the first attach request module is used for initiating an attach request flow in the first cell, and the attach request flow finishes releasing a terminal context message by the base station when the attach request fails;
the first delay module is used for executing the following steps in one cycle: if it is determined that the attach request can be reinitiated, starting a predetermined delay timer, wherein the delay timer is configured to:
delay timer = first timer + n x M;
in the delay timer, n represents the number of times of reinitiating the attachment request flow, and n is more than or equal to 0; m represents a delay time unit;
a first reinitiation module, configured to reinitiate the attach request procedure in the first cell when the delay timer expires;
and the first repeated execution module is used for repeatedly executing the steps in the loop when the attach request fails until the number of times of reinitiating the attach request flow reaches a preset number of times.
8. The terminal voice service connecting device according to claim 7, wherein the terminal voice service connecting device further comprises:
the second cell acquisition module is used for acquiring a second cell if the attachment request fails after the number of times of reinitiating the attachment request flow reaches the preset number of times in the first cell;
a second initial access module, configured to initiate the initial access procedure in the second cell;
a second attach request module, configured to initiate the attach request procedure in the second cell;
the second delay module is used for executing the following steps in one cycle: if it is determined that the attachment request can be reinitiated, starting the delay timer;
a second reinitiation module, configured to reinitiate the attach request procedure in the second cell when the delay timer expires;
and the second repeated execution module is used for repeatedly executing the steps in the loop until the number of times of reinitiating the attach request flow reaches a preset number of times when the attach request fails.
9. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the terminal voice service connection method of any one of claims 1 to 6 via execution of the executable instructions.
10. A computer-readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the terminal voice service connection method of any one of claims 1 to 6.
CN202210419131.8A 2022-04-20 2022-04-20 Terminal voice service connection method, device, equipment and storage medium Active CN114650578B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210419131.8A CN114650578B (en) 2022-04-20 2022-04-20 Terminal voice service connection method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210419131.8A CN114650578B (en) 2022-04-20 2022-04-20 Terminal voice service connection method, device, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN114650578A CN114650578A (en) 2022-06-21
CN114650578B true CN114650578B (en) 2024-04-05

Family

ID=81997320

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210419131.8A Active CN114650578B (en) 2022-04-20 2022-04-20 Terminal voice service connection method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114650578B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103119971A (en) * 2010-08-13 2013-05-22 英特尔公司 Techniques for managing mobility management signaling in a wireless network
JP2015170878A (en) * 2014-03-05 2015-09-28 株式会社日立製作所 Operation management device for managing plural data communication devices in network
WO2017171920A1 (en) * 2016-03-28 2017-10-05 Intel IP Corporation Trigger for attach-tau for pending ims call request in radio access networks
CN112492704A (en) * 2020-12-11 2021-03-12 Oppo(重庆)智能科技有限公司 Session management method, session management device, terminal equipment and computer-readable storage medium

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112543477B (en) * 2019-09-23 2022-04-22 北京小米移动软件有限公司 Method, device, terminal and storage medium for sending measurement report
KR20210049585A (en) * 2019-10-25 2021-05-06 삼성전자주식회사 Electronic device for providing communication service and method thereof

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103119971A (en) * 2010-08-13 2013-05-22 英特尔公司 Techniques for managing mobility management signaling in a wireless network
JP2015170878A (en) * 2014-03-05 2015-09-28 株式会社日立製作所 Operation management device for managing plural data communication devices in network
WO2017171920A1 (en) * 2016-03-28 2017-10-05 Intel IP Corporation Trigger for attach-tau for pending ims call request in radio access networks
CN112492704A (en) * 2020-12-11 2021-03-12 Oppo(重庆)智能科技有限公司 Session management method, session management device, terminal equipment and computer-readable storage medium

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
3GPP.Universal Mobile Telecommunications System (UMTS) *
LTE ; Non-Access-Stratum (NAS)protocol for Evolved Packet System (EPS) *
Stage 3.ETSI TS 124 301 V13.11.0 (3GPP TS 24.301 version 13.11.0 Release 13).2018,第5.5.1.2节. *
Starting Timer T3440 in service request procedure for CS Fallback;InterDigital;3GPP TSG-CT WG1 Meeting #95 C1-154682;20151120;全文 *

Also Published As

Publication number Publication date
CN114650578A (en) 2022-06-21

Similar Documents

Publication Publication Date Title
CN110139387B (en) Uplink small data transmission method, network side DU and network side CU
TW201831031A (en) Device and Method of Handling a State Mismatch in a Wireless Communication System
CN110493876B (en) Data transmission method, device, equipment and storage medium
JP2019534619A (en) COMMUNICATION METHOD, DEVICE, AND SYSTEM
CN112543468B (en) Disaster recovery method for gateway equipment and communication equipment
WO2018171584A1 (en) Method, apparatus and device for establishing interface between base stations and storage medium
US8954054B2 (en) Method for processing and testing of called terminal and long term evolution system
US11576097B2 (en) Method and terminal for redirecting network
US11343738B2 (en) Handover-based connection resume technique
CN114650578B (en) Terminal voice service connection method, device, equipment and storage medium
CN112040538B (en) Data communication method and related device
WO2021249477A1 (en) Multicast service switching method and device
CN114557042A (en) Reducing signaling upon handover of IAB node
CN112291848A (en) Terminal capability configuration method and communication device
CN112788790A (en) Communication method and related equipment
CN112911623B (en) Process overtime monitoring method and device
CN114071658B (en) Registration method and device of terminal equipment
CN113766675B (en) Method, device and terminal for leaving network
CN112166644B (en) Information acquisition method and equipment
CN110475387B (en) RRC connection recovery method, base station, terminal and readable medium
CN112689326B (en) Method, terminal and network side equipment for indicating NSSAI carrying
CN113810955B (en) Processing method and device in transmitting or receiving process and communication equipment
WO2023213140A1 (en) Communication method, resource configuration method, device, network node, system, and medium
US10390383B2 (en) Timer-based handling of multiple connection requests
CN109982394B (en) Signaling interaction method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant