CN112911623B - Process overtime monitoring method and device - Google Patents
Process overtime monitoring method and device Download PDFInfo
- Publication number
- CN112911623B CN112911623B CN201911229196.0A CN201911229196A CN112911623B CN 112911623 B CN112911623 B CN 112911623B CN 201911229196 A CN201911229196 A CN 201911229196A CN 112911623 B CN112911623 B CN 112911623B
- Authority
- CN
- China
- Prior art keywords
- timer
- duration
- flow
- initiator
- timer duration
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/08—Testing, supervising or monitoring using real traffic
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The application discloses a process overtime monitoring method and a device, aiming at the problem that in the prior art, as a mobile manager sends a response message when a timer of a process initiator overflows, the process state is asynchronous, the method comprises the following steps: the mobile manager receives a request message sent by a process initiator, wherein the request message carries a first timer duration; triggering a second flow between the mobile manager and other network element equipment based on the request message, and monitoring the second flow by adopting the duration of a second timer; and when the time length of the second timer is determined to be overtime, sending a notification message for judging the second process failure to the process initiator, and triggering the process initiator to judge the first process failure. In the application, the mobility manager sets the timer duration the same as that of the process initiator through the received request message, so that the flow states of the mobility manager and the process initiator are kept consistent, resource consumption is reduced, and system efficiency is improved.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for monitoring process timeout.
Background
In the current communication system, for some signaling flows, such as a handover flow, a registration flow, an attach flow, and the like, a flow initiator and a mobility manager both start corresponding timers, so that the flow does not proceed indefinitely, thereby protecting normal operation of the flow, where the flow initiator may be a User Equipment (UE) or a base station.
In the prior art, referring to fig. 1, after a flow initiator sends a request message to a mobility manager, a timer T1 is started. After receiving the request message, the mobility manager interacts with other network element devices according to the request message, and then sends a corresponding response message to the process initiator. If the flow initiator receives the response message before the timer T1 overflows, the timer T1 is stopped, and the flow is considered to be successful, otherwise, the flow is considered to be failed.
For example, referring to fig. 2, taking the handover procedure as an example, after the base station sends a handover Request Pathswitch Request to the mobility manager, the base station starts a timer T1. And after receiving the switching Request PathSwitch Request, the mobile manager informs other network element equipment to update the bearing information, and after updating the bearing information, sends a switching response PathSwitch Request Ack to the base station. The base station receives the handoff response Pathswitch Request Ack before the timer T1 overflows, and stops the timer T1.
For another example, referring to fig. 3, taking an Attach procedure as an example, after the UE sends an Attach Request to the mobility manager, the UE starts a timer T1. And after receiving the Attach Request, the mobility manager informs other network element equipment to update the bearer information, and after updating the bearer information, sends an Attach response Attach Accept to the UE. And the UE receives the Attach response Attach Accept before the timer T1 overflows, and then stops the timer T1.
If the mobility manager sends the response message to the flow initiator after the timer T1 overflows, at this time, the mobility manager considers that the flow is successful, however, the flow initiator discards the received response message after the timer T1 overflows, and the flow initiator considers that the flow is failed, which causes unsynchronized flow states of the flow initiator and the mobility manager, and may result in that resources cannot be released. In addition, after receiving the request message, the mobility manager interacts with other network elements according to the request message, and the process initiator discards the response message sent by the mobility manager, which results in that the user resource statuses of the process initiator, the mobility manager, and other network element devices are not synchronized.
It follows that a new solution needs to be devised to overcome the above drawbacks.
Disclosure of Invention
The application provides a process overtime monitoring method and a process overtime monitoring device, which are used for solving the problems that the process states of a mobile manager and a process initiator are asynchronous and resources cannot be released because the mobile manager sends a response message when a timer of the mobile manager overflows.
The embodiment of the application provides the following specific technical scheme:
a process timeout monitoring method, comprising:
the method comprises the steps that a mobile manager receives a request message sent by a process initiator, wherein the request message carries a first timer duration, and the process initiator monitors a first process triggered by the process initiator by adopting the first timer duration;
the mobility manager triggers a second process between the mobility manager and other network element devices based on the request message, sets a second timer duration, and monitors the second process by adopting the second timer duration, wherein the second timer duration is not greater than the first timer duration, and the second process is a sub-process of the first process;
and when the mobile manager determines that the second timer duration is over, sending a notification message for judging the second flow failure to the flow initiator, wherein the notification message is used for triggering the flow initiator to judge the first flow failure.
Optionally, the request message carries a first timer field, where the first timer field at least includes a first timer duration, and further includes any one or a combination of the following:
a first timer type;
a first timer operation type;
a first timer coding mode;
a first timer field length.
Optionally, the duration of the second timer is not greater than the duration of the first timer, and the duration of the second timer is not less than a set threshold.
Optionally, the triggering, by the mobility manager, a second procedure between the mobility manager and another network element device, and after setting the duration of a second timer, before determining that the duration of the second timer is overtime, further includes:
the mobility manager sequentially triggers a plurality of third flows between the mobility manager and other network element devices, sets a third timer duration corresponding to each third flow based on the second timer duration, and monitors the corresponding third flow by using each third timer duration, wherein the third flows Cheng Junwei are sub-flows of the second flow, and the sum of the third timer durations is not greater than the second timer duration.
Optionally, after the sending, by the mobility manager, a notification message for determining that the second process fails to be sent to the process initiator, the method further includes:
and the mobile manager releases the resources distributed to the process initiator, wherein the resources are used for completing the first process.
A process timeout monitoring apparatus comprising:
a memory for storing executable instructions;
a processor for reading and executing the executable instructions stored in the memory, performing the following processes:
receiving a request message sent by a process initiator, wherein the request message carries a first timer duration, and the process initiator monitors a first process triggered by the process initiator by using the first timer duration;
triggering a second process between the mobile manager and other network element equipment based on the request message, setting the duration of a second timer, and monitoring the second process by adopting the duration of the second timer, wherein the duration of the second timer is not greater than the duration of the first timer, and the second process is a sub-process of the first process;
and when the time length of the second timer is determined to be overtime, sending a notification message for judging the second flow failure to the flow initiator, wherein the notification message is used for triggering the flow initiator to judge the first flow failure.
Optionally, the request message carries a first timer field, where the first timer field at least includes a first timer duration, and further includes any one or a combination of the following:
a first timer type;
a first timer operation type;
a first timer coding mode;
a first timer field length.
Optionally, the duration of the second timer is not greater than the duration of the first timer, and the duration of the second timer is not less than a set threshold.
Optionally, after triggering a second procedure between the mobility manager and another network element device, and after setting a second timer duration, and before determining that the second timer duration is overtime, the processor is further configured to:
sequentially triggering a plurality of third flows between the mobility manager and other network element devices, respectively setting a third timer duration corresponding to each third flow based on the second timer duration, and respectively monitoring the corresponding third flows by adopting the third timer durations, wherein the third flows Cheng Junwei are sub-flows of the second flow, and the sum of the third timer durations is not greater than the second timer duration.
Optionally, after sending the notification message for determining that the second process has failed to the process initiator, the processor is further configured to:
and the mobile manager releases the resources distributed to the process initiator, wherein the resources are used for completing the first process.
A process timeout monitoring device comprising:
the receiving unit is used for receiving a request message sent by a process initiator, wherein the request message carries a first timer duration, and the process initiator monitors a first process triggered by the process initiator by using the first timer duration;
a monitoring unit, configured to trigger a second procedure between the mobility manager and another network element device based on the request message, set a second timer duration, and monitor the second procedure by using the second timer duration, where the second timer duration is not greater than the first timer duration, and the second procedure is a sub-procedure of the first procedure;
and the sending unit is used for sending a notification message for judging the failure of the second flow to the flow initiator when the time length of the second timer is determined to be overtime, and the notification message is used for triggering the flow initiator to judge the failure of the first flow.
A storage medium having instructions which, when executed by a processor, enable the processor to perform a process timeout monitoring method as in any one of the above.
In the embodiment of the application, a mobile manager receives a request message sent by a process initiator, the request message carries a first timer duration, then, based on the request message, a second process between the mobile manager and other network element devices is triggered, the second timer duration is adopted to monitor the second process, further, when the duration of the second timer is determined to be overtime, a notification message for determining that the second process fails is sent to the process initiator, and the process initiator is triggered to determine that the first process fails. Therefore, the mobile manager acquires the time length of the first timer through the received request message, so that the time length of a second timer which is the same as the time length of the first timer can be set, the time length of the mobile manager and the time length of the timer of the process initiator are consistent, the situation that the mobile manager still sends a response message when the time length of the first timer of the process initiator is over is avoided, further, when the mobile manager determines that the time length of the second timer is over, a notification message for judging the second process failure is sent to the process initiator, and the process initiator is triggered to judge the first process failure, so that the process states of the mobile manager and the process initiator are consistent, resource consumption is reduced, and system efficiency is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a schematic diagram illustrating a process between a process initiator and a mobility manager in the prior art;
FIG. 2 is a flow chart illustrating a prior art method between a base station and a mobility manager;
FIG. 3 is a flowchart illustrating a process between a UE and a mobility manager in the prior art;
fig. 4 is a schematic flowchart of a process timeout monitoring method provided in an embodiment of the present application;
fig. 5 is a schematic flow chart of overtime monitoring of an attach procedure in a 4G scenario in the embodiment of the present application;
fig. 6 is a specific flowchart illustrating overtime monitoring of an attach procedure in a 4G scenario in this embodiment;
fig. 7 is a schematic flowchart of switching process timeout monitoring in a 5G scenario in the embodiment of the present application;
fig. 8 is a schematic flowchart of specific handover procedure timeout monitoring in a 5G scenario in the embodiment of the present application;
fig. 9 is a schematic structural diagram of a process timeout monitoring device provided in an embodiment of the present application;
fig. 10 is a schematic structural diagram of a process timeout monitoring device provided in an embodiment of the present application.
Detailed Description
Aiming at the problem that the flow states of a mobile manager and a flow initiator are not synchronous because the mobile manager sends a response message when a timer of the mobile manager and the flow initiator overflow in the prior art, in order to keep the flow states synchronous and reduce resource consumption, the embodiment of the application provides a solution for monitoring the flow overtime.
The scheme is as follows: a mobile manager receives a request message sent by a process initiator, wherein the request message carries a first timer duration; then, the mobility manager triggers a second process between the mobility manager and other network element devices based on the request message, sets a second timer duration, and monitors the second process by using the second timer duration; further, when the mobility manager determines that the duration of the second timer is exceeded, the flow initiator is triggered to determine that the first flow fails.
In order to make the technical solutions of the present application better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.
Referring to fig. 4, in the embodiment of the present application, the process of monitoring the process timeout is as follows.
Step S401: the method comprises the steps that a mobile manager receives a request message sent by a process initiator, wherein the request message carries a first timer duration, and the process initiator monitors a first process triggered by the process initiator by adopting the first timer duration.
It should be noted that, in the embodiment of the present application, the flow initiator may be a UE or a base station, and for convenience of description, only the UE is taken as an example for description.
For example, the mobility manager receives a request message 1 sent by the UE, where the request message carries a first timer duration, the first timer duration is 3 seconds, and the UE monitors a first process triggered by the UE by using the first timer duration of 3 seconds.
Specifically, the request message carries a first timer field, where the first timer field at least includes a first timer duration, and further includes any one or a combination of the following:
a first timer type;
a first timer operation type;
a first timer coding mode;
a first timer field length.
For example, as shown in table 1, the request message 1 carries a first timer field, where the first timer field includes a first timer duration, a first timer Type, a first timer operation Type, a first timer coding mode, and a first timer field Length, where the first timer duration is 3 seconds, the first timer Type is GPRS timer 2, the first timer operation Type is optional, the first timer coding mode is Type-Length-Value coding (TLV), and the first timer field Length is 3.
Table 1 first timer field structure in request message
| Serial number | Information element | Type (B) | Type of operation | Coding method | Length of |
| 33 | The first timer has a duration of 3 seconds | GPRS timer 2 | Optionally | TLV | 3 |
Step S402: and the mobility manager triggers a second process between the mobility manager and other network element equipment based on the request message, sets the duration of a second timer, and monitors the second process by adopting the duration of the second timer, wherein the duration of the second timer is not more than the duration of the first timer, and the second process is a sub-process of the first process.
In the embodiment of the present application, when step S402 is executed, the following operations may be executed:
a1, the mobility manager triggers a second process between the mobility manager and other network element devices based on the request message, and sets a second timer duration, wherein the second process is a sub-process of the first process, the second timer duration is not greater than the first timer duration, and the second timer duration is not less than a set threshold.
For example, after receiving a request message 1 sent by the UE, the mobility manager triggers a second flow between the mobility manager and a Serving GateWay (SGW) and a Packet Data Network GateWay (PGW), where the second flow is a sub-flow of the first flow, and then, based on a time length of a first timer carried in the request message 1, the mobility manager assumes that a threshold is set to 1 second, and sets a time length of a second timer to 3 seconds.
And A2, the mobile manager monitors the second flow by adopting the duration of the second timer.
Specifically, the mobility manager sequentially triggers a plurality of third flows between the mobility manager and other network element devices, sets a third timer duration corresponding to each third flow based on the second timer duration, and monitors the corresponding third flow by using each third timer duration, wherein the third flows Cheng Junwei are sub-flows of the second flow, and a sum of the third timer durations is not greater than the second timer duration.
For example, the mobility manager monitors the second flow by using a second timer with a duration of 3 seconds, where the second flow includes a plurality of sub-flows, and the mobility manager sequentially triggers the plurality of sub-flows of the second flow, e.g., the mobility manager first triggers a third flow 1 between the mobility manager and the SGW, and then triggers a third flow 2 between the mobility manager and the PGW, and sets a third timer with a duration of 1 second corresponding to the third flow 1 and a third timer with a duration of 2 seconds corresponding to the third flow 2 based on the duration of 3 seconds of the second timer, and then monitors the third flow 1 by using the duration of 1 second of the third timer and monitors the third flow 2 by using the duration of 2 seconds of the third timer.
Step S403: and when the mobile manager determines that the second timer duration is over, sending a notification message for judging the second flow failure to the flow initiator, wherein the notification message is used for triggering the flow initiator to judge the first flow failure.
For example, when the mobility manager determines that the duration of the second timer exceeds 3 seconds, it determines that the second procedure fails, and sends a notification message of the second procedure failure to the UE, triggering the UE to determine that the first procedure fails.
Further, the mobility manager releases the resource allocated to the process initiator, where the resource is used to complete the first process.
For example, when the mobility manager determines that the duration of the second timer exceeds 3 seconds, it determines that the second procedure fails and sends a notification message of the second procedure failure to the UE, and after triggering the UE to determine that the first procedure fails, the mobility manager initiates a UE context release process, thereby releasing resources allocated to the UE for completing the first procedure.
The following will describe a flow of timeout monitoring in the embodiment of the present application by taking an attach flow in a 4G scenario as an example, where a flow initiator is a UE and a Mobility Management Entity (MME).
Referring to fig. 5, in the embodiment of the present application, the attachment process in the 4G scenario is as follows:
step 501: the UE applies to a base station (eNB) for establishing an RRC connection.
Step 502: the UE establishes an RRC connection with the eNB.
Step 503: and the UE establishes RRC connection with the eNB to complete.
Step 504: and the UE sends an attachment request to the MME, wherein the attachment request carries the first timer duration.
Specifically, the attach request carries a first timer duration of 10 seconds, and the structure of the attach request is shown in table 1.
Step 505: and the UE monitors the first attachment process by adopting the duration of the first timer.
Specifically, the UE monitors a first attach procedure triggered by the UE by using a first timer duration of 10 seconds, and waits for receiving an attach response within the first timer duration.
Step 506: and the MME monitors a second attachment process by adopting the duration of a second timer.
Specifically, the MME triggers, based on the attach request, a second attach flow between the MME and other network elements such as a Home Subscriber Server (HSS) and an SGW, and sets a second timer duration to 10 seconds, then the MME monitors the second attach flow by using the second timer duration of 10 seconds, where the second attach flow includes multiple sub-flows, and the MME sequentially triggers multiple sub-flows of the second attach flow, e.g., the MME triggers a third attach flow 1 between the MME and the HSS, sets a third timer duration corresponding to the third attach flow 1 for 1 second based on the second timer duration of 10 seconds, and then triggers a third attach flow 2 between the MME and the SGW, sets a third timer duration corresponding to the third attach flow 2 for 1 second based on the second timer duration of 10 seconds, then monitors the third attach flow 1 by using the third timer duration of 1 second, and monitors the third attach flow 1 by using the third timer duration of 1 second.
Step 507: and when the duration of the second timer is overtime, the MME judges that the second attachment process fails.
Specifically, when the MME determines that the duration of the second timer exceeds 15 seconds, it determines that the second attach procedure fails, and sends a notification message of the second attach procedure failure to the UE, and triggers the UE to determine that the first attach procedure fails.
Step 508: the MME initiates UE context release.
Specifically, the MME initiates a UE context release to release resources for the first attach procedure.
Step 509: the eNB informs the MME that the UE context release is complete.
Step 510: the eNB informs the UE to release the RRC connection.
Referring to fig. 6, in the 4G scenario, a specific attachment procedure is as follows.
Step 601: the UE sends an attach request to the eNB, where the attach request further includes a Public Data Network (PDN) connection request.
Specifically, the attach request carries a first timer duration of 10 seconds, and the format of the attach request is shown in table 1. And step 601 to step 621, in which the UE adopts the first timer duration of 10 seconds, monitors UE triggering, and waits for receiving an attachment response within the first timer duration.
Step 602: the eNB sends an attach request to the MME.
Step 603: and the MME allocates each third timer duration according to the second timer durations.
Specifically, the MME triggers, based on the attach request, steps 603 to 620 between the MME and other network element devices such as a Home Subscriber Server (HSS), an SGW, an Equipment Identity Register (EIR), and the like, and sets the duration of the second timer to 10 seconds, then the MME adopts the duration of the second timer for 3 seconds, and monitors steps 603 to 620.
Step 603 to step 620: for each third flow in this embodiment of the application, the MME sequentially triggers steps 603 to 620, and sets a third timer duration corresponding to steps 603 to 620, based on the second timer duration being 10 seconds, and the third timer duration T 3 1 to T 3 7 are set to 1, 3, respectively, and a third timer duration T is used 3 1 monitoring step 603 to step 604, using a third timer duration T 3 2 monitoring steps 605 to 606, using a third timer duration T 3 3 monitoring step 607 to step 608, using the third timer duration T 3 4 monitoring step 609 to step 610, using a third timer duration T 3 5 monitoring step 611 to step 612, using a third timer duration T 3 6 monitor step 613 to step 614, using a third timer duration T 3 Step 616 to step 620 are monitored by 7.
If step 603 to step 620 are not completed within 10 seconds of the second timer, it is determined that step 603 to step 620 fail, and a notification message of the failure of step 603 to step 620 is sent to the UE, triggering the UE to determine that step 601 to step 621 fail, and then the MME initiates the UE context release to release the resources used in step 601 to step 621.
If steps 603 to 620 are all completed within 10 seconds of the second timer, the following steps are continuously executed:
step 621: the MME sends an attach response or PND attach response or a common default bearer request to the eNB.
Step 622: the eNB configures an RRC connection for the UE.
Step 623: the UE informs the eNB that the configuration RRC connection is complete.
Step 624: the eNB sends a create default bearer response to the MME.
Step 625: the UE initiates a direct transfer to the eNB.
Step 626: the eNB informs the MME of the attachment completion.
Step 627: the MME sends a bearer update request to the SGW.
Step 628: the SGW sends a bearer update request to the PGW.
Step 629: the PGW sends a bearer update response to the SGW.
Step 630: the SGW sends a bearer update response to the MME.
Step 631: the MME sends a notification request to the HSS.
Step 632: the HSS sends a notification response to the MME.
The following will describe a process of monitoring timeout of the process in the embodiment of the present application by taking a handover process in a 5G scenario as an example, where a process initiator is a UE, and a Mobility manager is an Access and Mobility Management Function (AMF).
Referring to fig. 7, in the embodiment of the present application, a registration process in a 5G scenario is as follows:
step 701: the UE applies for establishing an RRC connection to a base station (gNB).
Step 702: the UE establishes an RRC connection with the gNB.
Step 703: and the UE establishes RRC connection with the gNB to complete.
Step 704: and the UE sends a registration request to the AMF, wherein the registration request carries the time length of a first timer.
Specifically, the registration request carries a first timer duration of 15 seconds, and a field structure of the first timer in the registration request is shown in table 1.
Step 705: and the UE monitors the first registration process by adopting the duration of the first timer.
Specifically, the UE monitors a first registration process triggered by the UE by using a first timer for 15 seconds, and waits for receiving a registration response within the first timer.
Step 706: and the AMF monitors a second registration process by adopting the duration of the second timer.
Specifically, the AMF triggers, based on the registration request, a second registration procedure between the AMF and other network elements such as a Policy Control FuncTIon (PCF), a Session Management FuncTIon (SMF), and the like, sets a duration of a second timer to 15 seconds, and then the AMF uses the duration of the second timer to monitor the second registration procedure, where the second registration procedure includes a plurality of sub-procedures, and the AMF sequentially triggers the plurality of sub-procedures of the second registration procedure, such that the AMF triggers a third registration procedure 1 between the AMF and the PCF, sets a duration of a third timer 1 corresponding to the third registration procedure 1 based on the duration of the second timer of 15 seconds, triggers a third registration procedure 2 between the AMF and the SMF, sets a third timer 3 seconds corresponding to the third registration procedure 2 based on the duration of the second timer of 15 seconds, then monitors the third registration procedure 1 second by using the third timer, and monitors the third registration procedure 1 second by using the third timer 2 seconds.
Step 707: and when the duration of the second timer is overtime, the AMF judges that the second registration process fails.
Specifically, when the AMF determines that the duration of the second timer exceeds 15 seconds, it determines that the second registration procedure fails, and sends a notification message of the second registration procedure failure to the UE, and triggers the UE to determine that the first registration procedure fails.
Step 708: the AMF initiates UE context release.
Specifically, the AMF initiates a UE context release to release resources for the first registration procedure.
Step 709: the gNB informs the AMF that the UE context release is complete.
Step 710: the gNB informs the UE to release the RRC connection.
Referring to fig. 8, in the 5G scenario, a specific registration process is as follows.
Step 801: the UE sends a registration request to the gNB.
Specifically, the registration request carries the first timer duration of 15 seconds, and the structure of the registration request is shown in table 1. The UE adopts the first timer duration of 15 seconds, monitors the triggering of the UE in steps 801 to 821, and waits for receiving a registration response within the first timer duration.
Step 802: and g NB performs AMF selection.
Step 803: the gNB sends a registration request to the new AMF.
Specifically, the new AMF triggers, based on the registration request, steps 804 to 820 between the new AMF and the PCF, the SMF, the Authentication Server Function (AUSF), and the Unified Data Management Function (UDM), sets the duration of the second timer to 15 seconds, and then the new AMF adopts the duration of the second timer for 15 seconds to monitor steps 804 to 820.
If the step 804 to the step 820 are not completed within 15 seconds of the second timer, it is determined that the step 804 to the step 820 fail, and a notification message of the failure of the step 804 to the step 820 is sent to the UE, triggering the UE to determine that the step 804 to the step 820 fail, and then the new AMF initiates the UE context release to release the resources used in the step 804 to the step 820.
If all of steps 804 to 820 are completed within 15 seconds of the second timer, the following steps are continuously executed:
step 821 (b): and the new AMF and the PCF carry out UE policy association establishment.
Step 822: the PCF sends a registration completion to the new AMF.
Step 823: the new AMF acknowledges the receipt indication to the UDM.
Step 824: the new AMF sends an update indication to the UDM.
Based on the same inventive concept, in the embodiment of the present application, a flow timeout monitoring apparatus is provided, as shown in fig. 9, and at least includes:
a memory 901 for storing executable instructions;
a processor 902 for reading and executing executable instructions stored in the memory, performing the following processes:
receiving a request message sent by a process initiator, wherein the request message carries a first timer duration, and the process initiator monitors a first process triggered by the process initiator by using the first timer duration;
triggering a second process between the mobile manager and other network element equipment based on the request message, setting the duration of a second timer, and monitoring the second process by adopting the duration of the second timer, wherein the duration of the second timer is not greater than the duration of the first timer, and the second process is a sub-process of the first process;
when the time length of the second timer is determined to be overtime, sending a notification message for judging the failure of the second process to the process initiator, wherein the notification message is used for triggering the process initiator to judge the failure of the first process;
a transceiver 903 for receiving and transmitting data under the control of the processor 902.
Where, in fig. 9, the bus architecture may include any number of interconnected buses and bridges, particularly where one or more processors, represented by the processor 902, and various circuits, represented by the memory 901, are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 903 may be a number of elements including a transmitter and a transceiver providing a means for communicating with various other apparatus over a transmission medium. The processor 902 is responsible for managing the bus architecture and general processing, and the memory 901 may store data used by the processor 902 in performing operations.
The processor 902 is responsible for managing the bus architecture and general processing, and the memory 901 may store data used by the processor 902 in performing operations.
Optionally, the request message carries a first timer field, where the first timer field at least includes a first timer duration, and further includes any one or a combination of the following:
a first timer type;
a first timer operation type;
a first timer coding mode;
a first timer field length.
Optionally, the duration of the second timer is not greater than the duration of the first timer, and the duration of the second timer is not less than a set threshold.
Optionally, after triggering a second procedure between the mobility manager and another network element device, and after setting a second timer duration, and before determining that the second timer duration is overtime, the processor 902 is further configured to:
sequentially triggering a plurality of third flows between the mobility manager and other network element devices, respectively setting a third timer duration corresponding to each third flow based on the second timer duration, and respectively monitoring the corresponding third flows by adopting the third timer durations, wherein the third flows Cheng Junwei are sub-flows of the second flow, and the sum of the third timer durations is not greater than the second timer duration.
Optionally, after sending a notification message for determining that the second process fails to the process initiator, the processor 902 is further configured to:
and the mobile manager releases the resources distributed to the process initiator, wherein the resources are used for completing the first process.
Based on the same inventive concept, in the embodiment of the present application, a process timeout monitoring apparatus is provided, as shown in fig. 10, and at least includes: a receiving unit 1001, a monitoring unit 1002, and a transmitting unit 1003, wherein,
a receiving unit 1001, configured to receive a request message sent by a process initiator, where the request message carries a first timer duration, and the process initiator monitors a first process triggered by the process initiator by using the first timer duration;
a monitoring unit 1002, configured to trigger a second procedure between the mobility manager and another network element device based on the request message, set a duration of a second timer, and monitor the second procedure by using the duration of the second timer, where the duration of the second timer is not greater than the duration of the first timer, and the second procedure is a sub-procedure of the first procedure;
a sending unit 1003, configured to send a notification message for determining that the second flow fails to be sent to the flow initiator when it is determined that the duration of the second timer expires, where the notification message is used to trigger the flow initiator to determine that the first flow fails.
The receiving unit 1001, the monitoring unit 1002, and the sending unit 1003 cooperate with each other to implement the functions of the process timeout monitoring apparatus in the above-described embodiments.
Based on the same inventive concept, the embodiment of the present application provides a storage medium, and when instructions in the storage medium are executed by a processor, the processor can execute any method implemented by the flow Cheng Chaoshi monitoring device in the above flow.
In the embodiment of the application, a mobile manager receives a request message sent by a process initiator, the request message carries a first timer duration, then, based on the request message, triggers a second process with other network element devices, monitors the second process by adopting the second timer duration, further, when the second timer duration is determined to be overtime, sends a notification message for determining that the second process fails to the process initiator, and triggers the process initiator to determine that the first process fails.
Thus, the application has at least the following beneficial effects:
the mobile manager acquires the time length of the first timer through the received request message, so that the time length of a second timer which is the same as the time length of the first timer can be set, the time length of the mobile manager and the time length of the timer of the process initiator are consistent, the situation that the mobile manager still sends a response message when the time length of the first timer of the process initiator is exceeded is avoided, further, when the mobile manager determines that the time length of the second timer is exceeded, a notification message for judging the failure of the second process is sent to the process initiator, and the process initiator is triggered to judge the failure of the first process, so that the process states of the mobile manager and the process initiator are consistent, resource consumption is reduced, and system efficiency is improved.
For the system/apparatus embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference may be made to some descriptions of the method embodiments for relevant points.
It is to be noted that, in this document, relational terms such as first and second, and the like are used solely to distinguish one entity or operation from another entity or operation without necessarily requiring or implying any actual such relationship or order between such entities or operations.
In this embodiment of the present application, a User Equipment (UE) includes, but is not limited to, a Mobile Station (MS), a Mobile Terminal (MS), a Mobile phone (Mobile Telephone), a handset (handset), a portable device (portable Equipment), and the like, and the User Equipment may communicate with one or more core networks through a Radio Access Network (RAN), for example, the User Equipment may be a Mobile phone (or "cellular" phone), a computer with a wireless communication function, and the User Equipment may also be a portable, pocket, hand-held, computer-built-in, or vehicle-mounted Mobile device.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (10)
1. A process timeout monitoring method, comprising:
the method comprises the steps that a mobile manager receives a request message sent by a process initiator, wherein the request message carries a first timer duration, and the process initiator monitors a first process triggered by the process initiator by adopting the first timer duration;
the mobility manager triggers a second process between the mobility manager and other network element devices based on the request message, and sets a second timer duration, wherein the second timer duration is not greater than the first timer duration, and the second process is a sub-process of the first process;
the mobility manager sequentially triggers a plurality of third flows between the mobility manager and other network element devices, respectively sets a third timer duration corresponding to each third flow based on the second timer duration, and respectively monitors the corresponding third flow by using each third timer duration, wherein the third flows Cheng Junwei are sub-flows of the second flow, and the sum of the third timer durations is not greater than the second timer duration;
and when the mobile manager determines that the second timer duration is over, sending a notification message for judging the second flow failure to the flow initiator, wherein the notification message is used for triggering the flow initiator to judge the first flow failure.
2. The method of claim 1, wherein the request message carries a first timer field, and wherein the first timer field at least includes a first timer duration, and further includes any one or a combination of:
a first timer type;
a first timer operation type;
a first timer coding mode;
a first timer field length.
3. The method of claim 2, wherein the second timer duration is not greater than the first timer duration, and wherein the second timer duration is not less than a set threshold.
4. The method of any of claims 1-3, wherein after the mobility manager sends a notification message to the flow initiator that the second flow has failed, further comprising:
and the mobile manager releases the resources distributed to the process initiator, wherein the resources are used for completing the first process.
5. A process timeout monitoring apparatus, comprising:
a memory for storing executable instructions;
a processor for reading and executing the executable instructions stored in the memory, performing the following processes:
receiving a request message sent by a process initiator, wherein the request message carries a first timer duration, and the process initiator monitors a first process triggered by the process initiator by using the first timer duration;
triggering a second process between the mobility manager and other network element equipment based on the request message, and setting a second timer duration, wherein the second timer duration is not greater than the first timer duration, and the second process is a sub-process of the first process;
sequentially triggering a plurality of third flows between the mobility manager and other network element devices, respectively setting a third timer duration corresponding to each third flow based on the second timer duration, and respectively monitoring the corresponding third flows by adopting the third timer durations, wherein the third flows Cheng Junwei are sub-flows of the second flow, and the sum of the third timer durations is not more than the second timer duration;
and when the time length of the second timer is determined to be overtime, sending a notification message for judging the failure of the second process to the process initiator, wherein the notification message is used for triggering the process initiator to judge the failure of the first process.
6. The apparatus of claim 5, wherein the request message carries a first timer field, and wherein the first timer field at least comprises a first timer duration, and further comprises any one or a combination of:
a first timer type;
a first timer operation type;
a first timer coding mode;
a first timer field length.
7. The apparatus of claim 6, wherein the second timer duration is not greater than the first timer duration, and wherein the second timer duration is not less than a set threshold.
8. The apparatus of any of claims 5-7, wherein after sending a notification message to the flow initiator that determines that the second flow failed, the processor is further configured to:
and the mobile manager releases the resources distributed to the process initiator, wherein the resources are used for completing the first process.
9. A process timeout monitoring device, comprising:
the receiving unit is used for receiving a request message sent by a process initiator, wherein the request message carries a first timer duration, and the process initiator monitors a first process triggered by the process initiator by using the first timer duration;
a monitoring unit, configured to trigger a second procedure between the mobility manager and another network element device based on the request message, and set a second timer duration, where the second timer duration is not greater than the first timer duration, and the second procedure is a sub-procedure of the first procedure; the mobile manager is used for triggering a plurality of third flows between the mobile manager and other network element devices in sequence, setting a third timer duration corresponding to each third flow based on the second timer duration, and monitoring the corresponding third flows by adopting the third timer durations, wherein the third flows Cheng Junwei are sub-flows of the second flow, and the sum of the third timer durations is not greater than the second timer duration;
and the sending unit is used for sending a notification message for judging the failure of the second flow to the flow initiator when the time length of the second timer is determined to be overtime, and the notification message is used for triggering the flow initiator to judge the failure of the first flow.
10. A storage medium, wherein instructions in the storage medium, when executed by a processor, enable the processor to perform the process timeout monitoring method of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911229196.0A CN112911623B (en) | 2019-12-04 | 2019-12-04 | Process overtime monitoring method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911229196.0A CN112911623B (en) | 2019-12-04 | 2019-12-04 | Process overtime monitoring method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112911623A CN112911623A (en) | 2021-06-04 |
| CN112911623B true CN112911623B (en) | 2023-03-14 |
Family
ID=76111134
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911229196.0A Active CN112911623B (en) | 2019-12-04 | 2019-12-04 | Process overtime monitoring method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112911623B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102448042A (en) * | 2010-09-30 | 2012-05-09 | 电信科学技术研究院 | Method for rejecting mobility management process and network side device |
| CN105309035A (en) * | 2014-04-30 | 2016-02-03 | 华为技术有限公司 | Mobility management entity and method for processing downlink circuit switched cs service |
| CN105409182A (en) * | 2013-04-05 | 2016-03-16 | 瑞典爱立信有限公司 | Handling of timers |
| WO2016148452A1 (en) * | 2015-03-13 | 2016-09-22 | 삼성전자 주식회사 | Method and device for calling terminal in wireless communication system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10567986B2 (en) * | 2016-09-06 | 2020-02-18 | Qualcomm Incorporated | Back-off mechanisms for fair joint access of unlicensed sidelink |
-
2019
- 2019-12-04 CN CN201911229196.0A patent/CN112911623B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102448042A (en) * | 2010-09-30 | 2012-05-09 | 电信科学技术研究院 | Method for rejecting mobility management process and network side device |
| CN105409182A (en) * | 2013-04-05 | 2016-03-16 | 瑞典爱立信有限公司 | Handling of timers |
| CN105309035A (en) * | 2014-04-30 | 2016-02-03 | 华为技术有限公司 | Mobility management entity and method for processing downlink circuit switched cs service |
| WO2016148452A1 (en) * | 2015-03-13 | 2016-09-22 | 삼성전자 주식회사 | Method and device for calling terminal in wireless communication system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112911623A (en) | 2021-06-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20220248254A1 (en) | Method of processing network slice based congestion, device and system thereof | |
| US8818381B2 (en) | Operation in case of radio link failure | |
| CN108391321B (en) | Apparatus and method for handling status mismatch in wireless communication system | |
| CN107666691B (en) | Terminal state conversion method and device | |
| CN110199568B (en) | Connection recovery method, access and mobility management functional entity and user equipment | |
| US20100099402A1 (en) | Method of improving radio resource control connenction establishment in a wireless communication system and related communication device | |
| CN111818662B (en) | User equipment, base station, access base station and wireless link monitoring method | |
| CN104115454A (en) | Enhancement procedure of suspending and resuming UE data in mobile communication networks | |
| CN111556589B (en) | Communication method, terminal and access network equipment | |
| KR20190099308A (en) | Communication methods, access network devices, and terminals | |
| CN109429366B (en) | PDU session processing method and device | |
| CN109246811B (en) | Data transmission method and device | |
| CN116491218A (en) | Synchronization of RRC state of multi-SIM user equipment with base station | |
| CN111148280B (en) | RRC connection release method and system based on terminal equipment and terminal equipment | |
| KR20230008781A (en) | Method and apparatus for sidelink communication during fast MCG link recovery procedure | |
| US20230083832A1 (en) | Information indication method and apparatus and communication device | |
| CN112911623B (en) | Process overtime monitoring method and device | |
| US20110141946A1 (en) | Reestablishment of the Interface between MME and Node B Using a Backoff time | |
| US10383169B2 (en) | Base station and terminal connection management method of base station | |
| CN110876208B (en) | User Equipment (UE) for efficient communication with a wireless network and method therefor | |
| CN113825186A (en) | Control method and device for leaving network and communication equipment | |
| CN102651902A (en) | Method, eNB (evolved Node B) and MME (Mobility Management Entity) equipment for handling NAS (Non-Access Stratum) instruction transmission failure | |
| CN110121215B (en) | Data connection establishment method and device of 5G terminal and 5G terminal | |
| JP5466270B2 (en) | Base station and control method in mobile communication system | |
| CN112788790A (en) | Communication method and related equipment |
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 |