CN115134823A - Fallback flow triggering method and device and network side equipment - Google Patents
Fallback flow triggering method and device and network side equipment Download PDFInfo
- Publication number
- CN115134823A CN115134823A CN202110316216.9A CN202110316216A CN115134823A CN 115134823 A CN115134823 A CN 115134823A CN 202110316216 A CN202110316216 A CN 202110316216A CN 115134823 A CN115134823 A CN 115134823A
- Authority
- CN
- China
- Prior art keywords
- flow
- fallback
- triggering
- network
- terminal
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 195
- 238000012545 processing Methods 0.000 claims abstract description 90
- 230000008569 process Effects 0.000 claims abstract description 73
- 230000001960 triggered effect Effects 0.000 claims abstract description 61
- 230000007246 mechanism Effects 0.000 claims abstract description 27
- 238000004590 computer program Methods 0.000 claims description 22
- 238000003860 storage Methods 0.000 claims description 22
- 238000005111 flow chemistry technique Methods 0.000 claims description 14
- 230000006870 function Effects 0.000 description 23
- 238000010586 diagram Methods 0.000 description 13
- 230000005540 biological transmission Effects 0.000 description 9
- 238000007726 management method Methods 0.000 description 9
- 230000003287 optical effect Effects 0.000 description 4
- FFBHFFJDDLITSX-UHFFFAOYSA-N benzyl N-[2-hydroxy-4-(3-oxomorpholin-4-yl)phenyl]carbamate Chemical compound OC1=C(NC(=O)OCC2=CC=CC=C2)C=CC(=C1)N1CCOCC1=O FFBHFFJDDLITSX-UHFFFAOYSA-N 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000007774 longterm Effects 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000001514 detection method Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 230000005484 gravity Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000010079 rubber tapping Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000005236 sound signal Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000010897 surface acoustic wave method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
- H04W36/023—Buffering or recovering information during reselection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the invention discloses a fallback flow triggering method, a fallback flow triggering device and network side equipment, wherein the method is applied to the network side equipment and comprises the following steps: in the process of triggering a fallback flow for a terminal, if a processing request for a preset conflict flow for the terminal is received, processing the preset conflict flow, wherein the fallback flow is a flow for switching or redirecting the terminal from a first network to a second network so that the terminal processes a target service in the second network; determining whether to trigger the fallback flow again based on a preset cache triggering mechanism; and under the condition that the fallback flow is determined to be triggered again, triggering the fallback flow based on a pre-stored cache message corresponding to the fallback flow, wherein the cache message comprises a target parameter required for triggering the fallback flow. By the method, the success rate of the fallback flow can be improved, and the use experience of a terminal user is improved.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a fallback flow triggering method and apparatus, and a network device.
Background
Fifth generation (5) th Generation, 5G) mobile communication systems are also New Radio (NR) systems, and at the early stage of 5G network deployment or in the case of 5G network congestion, a 5G network may not be able to support Voice over NR (VoNR) and the 5G network needs to trigger from the 5G network to the fourth Generation (4G network) th Generation, 4G) network, and completes the Voice service of the terminal through Voice over Long Term Evolution (VoLTE) of the 4G network.
If other processing requests of service flows (such as a registration flow) which may cause that a fallback flow cannot be normally triggered are received in a calling process, a terminal cannot fall back to VoLTE, so that the calling flow is terminated, and the problems that the triggering success rate of the fallback flow is low and the voice calling experience of a terminal user is poor exist.
Disclosure of Invention
Embodiments of the present invention provide a fallback flow triggering method, an apparatus, and a network side device, so as to solve the problems in the prior art that a triggering success rate of a loop flow is low, and a voice call experience of a terminal user is poor.
To solve the above technical problem, the embodiment of the present invention is implemented as follows:
in a first aspect, a method for triggering a fallback procedure provided in an embodiment of the present invention is applied to a network device, and the method includes: in the process of triggering a fallback flow for a terminal, if a processing request for a preset conflict flow for the terminal is received, processing the preset conflict flow, where the fallback flow is a flow for switching or redirecting the terminal from a first network to a second network so that the terminal processes a target service in the second network, and the preset conflict flow is a service flow that causes the fallback flow not to be normally triggered; determining whether to trigger the fallback flow again based on a preset cache triggering mechanism; and under the condition that the fallback flow is determined to be triggered again, triggering the fallback flow based on a pre-stored cache message corresponding to the fallback flow, wherein the cache message comprises a target parameter required for triggering the fallback flow.
In a second aspect, an embodiment of the present invention provides a fall-back procedure triggering apparatus, where the apparatus includes: the processing module is used for processing a preset conflict flow if a processing request for the preset conflict flow of a terminal is received in the process of triggering the fallback flow of the terminal, wherein the fallback flow is a flow for switching or redirecting the terminal from a first network to a second network so that the terminal processes a target service in the second network, and the preset conflict flow is a service flow which can not be normally triggered; the determining module is used for determining whether to trigger the fallback flow again based on a preset cache triggering mechanism; and the triggering module is used for triggering the fallback flow based on a pre-stored cache message corresponding to the fallback flow under the condition that the fallback flow is determined to be re-triggered, wherein the cache message comprises a target parameter required for triggering the fallback flow.
In a third aspect, an embodiment of the present invention provides a network-side device, which includes a processor, a memory, and a computer program that is stored in the memory and is executable on the processor, and when the computer program is executed by the processor, the steps of the fallback flow triggering method provided in the foregoing embodiment are implemented.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements the steps of the fallback flow triggering method provided in the foregoing embodiment.
As can be seen from the above technical solutions provided in the embodiments of the present invention, in the process of triggering a fallback flow for a terminal, if a processing request for a preset conflict flow for the terminal is received, the preset conflict flow is processed, where the fallback flow is a flow for switching or redirecting the terminal from a first network to a second network, so that the terminal processes a target service in the second network, and the preset conflict flow is a service flow that causes the fallback flow not to be normally triggered, it is determined whether to re-trigger the fallback flow based on a preset cache trigger mechanism, and in a case that the fallback flow is determined to be re-triggered, the fallback flow is triggered based on a pre-stored cache message corresponding to the fallback flow, where the cache message includes a target parameter required for processing the fallback flow. Therefore, whether the fallback flow is triggered again or not can be determined based on the preset cache triggering mechanism, and the fallback flow is triggered again under the condition that the fallback flow is determined to be triggered again, so that the fallback flow triggering failure caused by processing the preset conflict processing flow is avoided, the triggering success rate of the fallback flow is improved, and the voice call experience of a terminal user is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a schematic flow chart of a fallback flow triggering method according to the present invention;
FIG. 2 is a schematic flow chart of another fallback flow triggering method according to the present invention;
FIG. 3 is a schematic diagram of a fallback procedure triggering method according to the present invention;
FIG. 4 is a diagram illustrating a comparison between the success rate of triggering a fallback procedure by a fallback procedure triggering method and the success rate of triggering a fallback procedure without the fallback procedure triggering method according to the present invention;
FIG. 5 is a schematic structural diagram of a fall-back procedure triggering apparatus according to the present invention;
fig. 6 is a schematic structural diagram of a network-side device according to the present invention.
Detailed Description
The embodiment of the invention provides a fallback flow triggering method and device and network side equipment.
In order to make those skilled in the art better understand the technical solution of the present invention, the technical solution in the embodiment of the present invention will be clearly and completely described below with reference to the drawings in the embodiment of the present invention, and it is obvious that the described embodiment is only a part of the embodiment of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example one
As shown in fig. 1, an execution main body of the method may be a network element side device, where the network element side device may be a server with Access and Mobility Management Function (AMF), and the server may be an independent server or a server cluster composed of multiple servers. The method may specifically comprise the following steps. The method may specifically comprise the steps of:
in S102, in the process of triggering the fallback flow for the terminal, if a processing request for the preset conflict flow for the terminal is received, the preset conflict flow is processed.
Wherein, the fallback procedure may be a procedure of switching the terminal from the first network to the second network or redirecting the terminal from the first network to the second network, so that the terminal processes the target service in the second network, a data processing capability of the first network may be higher than a data processing level of the second network, and the data processing capability may be determined by a data transmission rate, a data transmission delay, security and reliability of data transmission, for example, the data transmission rate of the first network may be higher than the data transmission rate of the second network, the data transmission delay of the first network may be lower than the data transmission delay of the second network, or the security and reliability of the first network may be higher than the second network, for example, the first network may be a 5G network, the second network may be a 4G network, when the terminal is at a coverage edge of a 5G network signal, or a weak coverage area of the 5G network signal, the terminal may be switched from the 5G network to the 4G network, or may be redirected from the 5G network to the 4G network, and subsequently, a process of a target service such as a voice call service may be processed in the 4G network, the terminal may be any terminal capable of processing the target service using a second network, specifically, a mobile terminal such as a mobile phone and a tablet computer, the preset conflict process may be a service process that causes a fallback process not to be triggered normally, for example, the preset conflict process may be a registration process.
In practice, the fifth generation (5) th Generation, 5G) mobile communication system also becomes a New Radio (NR) system, and at the initial deployment stage of a 5G network or in the case of congestion of the 5G network, the 5G network may not be able to support Voice over NR (VoNR), and the 5G network needs to trigger from the 5G network to a fourth networkGeneration (4) th Generation, 4G) network, and completes the Voice service of the terminal through Voice over Long Term Evolution (VoLTE) of the 4G network.
If other processing requests of service flows (such as a registration flow) which may cause that a fallback flow cannot be normally triggered are received in a calling process, a terminal cannot fall back to VoLTE, so that the calling flow is terminated, and the problems that the triggering success rate of the fallback flow is low and the voice calling experience of a terminal user is poor exist. Therefore, another implementation scheme is provided in the embodiments of the present invention, which may specifically include the following:
taking the target service as the voice call service, the first network as the 5G network, and the second network as the 4G network as an example, the user may use the terminal to make a voice call through the 5G network (i.e., the voice call service is processed through the terminal), and when the user is located at the coverage edge of the 5G network signal or in the weak coverage area of the 5G network signal, the network element side device may trigger the 5G network to the fourth generation (4G network) th Generation, 4G) network, and completes the Voice call service of the terminal through Voice over Long Term Evolution (VoLTE) of the 4G network, that is, the network element side device may trigger a fallback procedure for the terminal.
In the process of triggering the fallback flow for the terminal, the network element side device may receive one or more processing requests for the preset conflict flows for the terminal, and in the case of receiving the processing requests for the preset conflict flows, the network element side may process the received preset conflict flows, and in the process of processing the preset conflict flows, the fallback flow for the terminal fails to be triggered.
In S104, it is determined whether to re-trigger the fallback procedure based on a preset cache trigger mechanism.
In implementation, the preset cache triggering mechanism may be a triggering mechanism set for a preset conflict flow to determine whether to re-trigger the fallback flow and ensure a success rate of re-triggering.
For example, the historical processing time of the conflict flow may be acquired, the due completion time of the conflict flow may be determined according to the historical processing time, the target time of the conflict flow may be determined according to the start processing time and the due completion time of the conflict flow, and the drop-back flow may be determined to be retriggered when the target time is reached.
For example, if the time to be completed of conflict process 1 is 1 minute and the processing start time of conflict process 1 is 12:00, the target time of conflict process 1 is 12:01, that is, when 12:01 is reached, it may be determined to trigger the fallback process again.
In addition, when there are multiple conflict flows received by the network element side device, the target time of each conflict flow may be obtained, and when the maximum target time is reached, the fallback flow is determined to be triggered again.
For example, if the conflict flow 1 and the conflict flow 2 arrive at 12:00 at the same time, the target time corresponding to the conflict flow 1 is 12:03, the target time corresponding to the conflict flow 2 is 12:02, the conflict flow 3 arrives at 12:02, and the corresponding target time is 12:05, it may be determined that the fallback flow is triggered again when the latest target time is 12: 05.
The preset cache triggering mechanism is an optional and realizable triggering mechanism, and in a time application scenario, a plurality of different cache triggering processing mechanisms may be provided, which may be different according to different actual application scenarios.
In S106, when it is determined that the fallback flow is to be retriggered, the fallback flow is triggered based on a cache message corresponding to the fallback flow, which is stored in advance.
The cache message may include target parameters required for processing the fallback procedure, for example, the target parameters may be a Protocol Data Unit (PDU) session message parameter, a radio message parameter, a network quality message parameter, a priority parameter, and the like.
In implementation, when the drop-back flow is determined to be triggered again, whether a cache message corresponding to the terminal or the drop-back flow is stored locally may be searched for, and if the cache message is stored, the cache message may be acquired, and the drop-back flow is triggered again based on a target parameter in the cache message.
The embodiment of the invention provides a fallback procedure triggering method, which comprises the steps of processing a preset conflict procedure if a processing request for the preset conflict procedure of a terminal is received in the process of triggering the fallback procedure of the terminal, wherein the fallback procedure is a procedure of switching or redirecting the terminal from a first network to a second network so that the terminal processes a target service in the second network, the preset conflict procedure is a service procedure which causes the fallback procedure not to be normally triggered, determining whether to trigger the fallback procedure again based on a preset cache triggering mechanism, and triggering the fallback procedure based on a pre-stored cache message corresponding to the fallback procedure under the condition that the fallback procedure is determined to be triggered again, wherein the cache message comprises a target parameter required for processing the fallback procedure. Therefore, whether the fallback flow is triggered again or not can be determined based on the preset cache triggering mechanism, and the fallback flow is triggered again under the condition that the fallback flow is determined to be triggered again, so that the fallback flow triggering failure caused by processing the preset conflict processing flow is avoided, the triggering success rate of the fallback flow is improved, and the voice call experience of a terminal user is improved.
Example two
As shown in fig. 2, an execution main body of the method may be a network element side device, where the network element side device may be a server with Access and Mobility Management Function (AMF), and the server may be an independent server or a server cluster composed of multiple servers. The method may specifically comprise the following steps. The method may specifically comprise the steps of:
in S202, a trigger request for a fallback procedure of the terminal is received.
The trigger request may include target parameters required for triggering the fallback procedure.
In implementation, a cache queue may be locally stored, and the network element side device may receive a trigger request for a fallback procedure of a terminal, where the trigger request is issued by an IP Multimedia System (IMS).
For example, the network element side device may receive a trigger request for a fallback procedure of the terminal, which is issued by the DNN of the IMS (for example, the trigger request may be a Namf _ Communication _ N1N2message transfer message, where N1 and N2 may be preset interfaces used by the terminal).
In S204, a cache message is generated and stored based on the trigger request.
In implementation, the network element side device may generate a buffer message based on the trigger request, and store the buffer message in the buffer queue.
In S206, the trigger request is sent to the target base station corresponding to the first network.
In S208, when a fallback processing instruction returned by the target base station is received, a fallback procedure is triggered.
In S210, in the process of triggering the fallback procedure for the terminal, if a processing request for a preset conflict procedure for the terminal is received, the preset conflict procedure is processed,
the conflict process may include one or more of a registration process, a service request process, and a handover cancellation process.
As shown in fig. 2, after S210, execution may continue with S212; alternatively, after S210, S214 and S216 may be continuously performed; still alternatively, S214 and S218 may be continuously performed after S210.
In S212, in the case where the preset trigger period is reached, it is determined that the fallback procedure is retriggered.
The preset trigger period may be any trigger period, such as 10s, 20s, and the like.
In S214, a flow processing state of the preset conflict flow is acquired.
In S216, in the case where the flow processing status of the preset conflict flow is processing completion, it is determined that the fallback flow is retriggered.
In implementation, when there are a plurality of preset conflict processing flows, it may be determined that the fallback flow is retriggered when all the flow processing states of the plurality of preset conflict processing flows are processing completion.
In S218, when the process processing status of the preset conflict processing process is not completed and reaches the preset trigger period, it is determined to re-trigger the fallback process.
In S220, if it is determined that the fallback flow is to be triggered again, the fallback flow is triggered based on a pre-stored cache message corresponding to the fallback flow.
For the specific processing procedure of S220, reference may be made to the related content of S106 in the first embodiment, which is not described herein again.
As shown in fig. 3, taking the first network as a 5G network and the second network as a 4G network as an example, the IMS voice call (i.e., the target service) of the 5G network is started to establish a Quality of service (QoS) wave, the 5G network starts a PDU session and modifies and sets the IMS voice QoS wave, a fallback procedure may be triggered, a measurement report may be collected, or a PDU session modification is aggregated, which is only an IMS voice fallback procedure.
The network element side device may receive a trigger request for a fallback procedure of the terminal issued by the DNN of the IMS, and generate a corresponding cache message based on the trigger request, and store the cache message in the cache queue.
For the FALLBACK procedure, the network element side device may add a corresponding variable (for example, EPS _ fault _ STATUS), and set an initial value of the variable to NULL. The network element side device may send the trigger request to the 5G network base station, and trigger a fallback procedure (i.e., redirect or switch to the 4G network) when receiving a fallback processing instruction (e.g., may receive a #36 cause value returned by the 5G network base station) returned by the 5G network base station.
While triggering the FALLBACK procedure, the parameter value of EPS _ fault _ STATUS may be set to EPS _ fault _ done, and a timer T-epsfarlbck may be started.
In the process of triggering a fallback flow for a terminal, if one or more processing requests for a preset conflict flow for the terminal are received, the network element side device processes the preset conflict flow.
In case the timer times out (i.e. reaches the preset trigger period), it may be determined that the fallback procedure is retriggered. Or, in a case where the flow processing state of the preset conflict flow is processing completion, it may be determined to re-trigger the fallback flow. Or, although the flow processing status of the preset conflict processing flow is not completed, if the timer is over time, it may be determined to trigger the fallback flow again.
After determining to trigger the FALLBACK procedure again, the parameter value of EPS _ fault _ STATUS may be set to NULL, and the cache message in the cache queue is obtained, so as to trigger the FALLBACK procedure again based on the target parameter required for triggering the FALLBACK procedure included in the cache message, that is, send a trigger request to the 5G network base station, and trigger the FALLBACK procedure again when receiving the FALLBACK processing instruction returned by the 5G network base station.
After the fallback procedure is triggered again, a tracking area location update procedure may be triggered, where the request type may be a switched Packet Data Network (PDN) connection attach request, and the Network starts a PDN connection to modify and set a dedicated voice bearer.
The UE may be a terminal, the NG RAN may be a 5G network base station, the E-UTRAN may be a 4G network base station, the MME may be a Mobility Management Entity (Mobility Management Entity), the SGW is a serving gateway, the PGW is a packet forwarding gateway (PND gateway), the SMF is a Session Management Function (Session Management Function), the UPF is a User Plane Function (User Plane Function), and the PCF is a Policy Control Function (Policy Control Function).
In addition, after the back-off process is successfully re-triggered, the AMF may send a back-off process success message to the MME (for example, the back-off process success message may be a forward relocation complete ack), and the network element side device may delete the timer, so as to avoid repeatedly triggering the back-off process.
As shown in fig. 4, the success rate of triggering the fallback flow by the fallback flow triggering method is greater than the success rate of triggering the fallback flow by the non-fallback flow triggering method.
The embodiment of the invention provides a fallback procedure triggering method, which comprises the steps of processing a preset conflict procedure if a processing request for the preset conflict procedure of a terminal is received in the process of triggering the fallback procedure of the terminal, wherein the fallback procedure is a procedure of switching or redirecting the terminal from a first network to a second network so that the terminal processes a target service in the second network, the preset conflict procedure is a service procedure which causes the fallback procedure not to be normally triggered, determining whether to trigger the fallback procedure again based on a preset cache triggering mechanism, and triggering the fallback procedure based on a pre-stored cache message corresponding to the fallback procedure under the condition that the fallback procedure is determined to be triggered again, wherein the cache message comprises a target parameter required for processing the fallback procedure. Therefore, whether the fallback flow is triggered again or not can be determined based on the preset cache triggering mechanism, and the fallback flow is triggered again under the condition that the fallback flow is determined to be triggered again, so that the fallback flow triggering failure caused by processing the preset conflict processing flow is avoided, the triggering success rate of the fallback flow is improved, and the voice call experience of a terminal user is improved.
EXAMPLE III
Based on the same idea, the fallback flow triggering method provided in the embodiment of the present invention further provides a fallback flow triggering device, as shown in fig. 5.
The fall-back flow triggering device comprises: a processing module 501, a determining module 502 and a triggering module 503, wherein:
a processing module 501, configured to, in a process of triggering a fallback flow for a terminal, if a processing request for a preset conflict flow for the terminal is received, process the preset conflict flow, where the fallback flow is a flow in which the terminal is switched from a first network or redirected to a second network so that the terminal processes a target service in the second network, and the preset conflict flow is a service flow that causes the fallback flow to be unable to be normally triggered;
a determining module 502, configured to determine whether to trigger the fallback procedure again based on a preset cache trigger mechanism;
a triggering module 503, configured to trigger the fallback flow based on a pre-stored cache message corresponding to the fallback flow when it is determined that the fallback flow is triggered again, where the cache message includes a target parameter required for triggering the fallback flow.
In the embodiment of the present invention, the conflict flow includes one or more of a registration flow, a service request flow, and a handover cancel flow.
In this embodiment of the present invention, the determining module 502 is configured to:
and determining to trigger the fallback flow again under the condition that a preset trigger period is reached.
In this embodiment of the present invention, the determining module 502 is configured to:
acquiring a flow processing state of the preset conflict flow;
and determining to re-trigger the fallback flow under the condition that the flow processing state of the preset conflict flow is processing completion.
In an embodiment of the present invention, the apparatus further includes:
and the flow determining module is used for determining to trigger the fallback flow again when the flow processing state of the preset conflict processing flow is unfinished and a preset trigger period is reached.
In an embodiment of the present invention, the apparatus further includes:
a request receiving module, configured to receive a trigger request for a fallback procedure of the terminal, where the trigger request includes a target parameter required for triggering the fallback procedure;
and the message generation module is used for generating and storing the cache message based on the trigger request.
In an embodiment of the present invention, the apparatus further includes:
a sending module, configured to send the trigger request to a target base station corresponding to the first network;
and the first triggering module is used for triggering the fallback procedure under the condition of receiving the fallback processing instruction returned by the target base station.
The embodiment of the invention provides a fallback flow triggering device, which is used for processing a preset conflict flow by a terminal if a processing request of the preset conflict flow for the terminal is received in the process of triggering the fallback flow for the terminal, wherein the fallback flow is a flow for switching or redirecting the terminal from a first network to a second network so that the terminal processes a target service in the second network, the preset conflict flow is a service flow which causes the fallback flow not to be normally triggered, whether the fallback flow is retriggered or not is determined based on a preset cache triggering mechanism, and the fallback flow is triggered based on a pre-stored cache message corresponding to the fallback flow under the condition that the fallback flow is determined to be retriggered, and the cache message comprises a target parameter required for processing the fallback flow. Therefore, whether the fallback flow is triggered again or not can be determined based on the preset cache triggering mechanism, and the fallback flow is triggered again under the condition that the fallback flow is determined to be triggered again, so that the fallback flow triggering failure caused by processing the preset conflict processing flow is avoided, the triggering success rate of the fallback flow is improved, and the voice call experience of a terminal user is improved.
Example four
Figure 6 is a schematic diagram of a hardware architecture of a network side device implementing various embodiments of the present invention,
the network side device 600 includes but is not limited to: a radio frequency unit 601, a network module 602, an audio output unit 603, an input unit 604, a sensor 605, a display unit 606, a user input unit 607, an interface unit 608, a memory 609, a processor 610, and a power supply 611. Those skilled in the art will appreciate that the network-side device architecture shown in fig. 6 does not constitute a limitation of the network-side device, and that the network-side device may include more or fewer components than those shown, or combine certain components, or arrange different components. In the embodiment of the present invention, the network-side device includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, and a pedometer.
Wherein, the processor 610 is configured to: in the process of triggering a fallback flow for a terminal, if a processing request for a preset conflict flow for the terminal is received, processing the preset conflict flow, where the fallback flow is a flow for switching or redirecting the terminal from a first network to a second network so that the terminal processes a target service in the second network, and the preset conflict flow is a service flow that causes the fallback flow not to be normally triggered; determining whether to trigger the fallback flow again based on a preset cache triggering mechanism; and under the condition that the fallback flow is determined to be triggered again, triggering the fallback flow based on a pre-stored cache message corresponding to the fallback flow, wherein the cache message comprises a target parameter required for triggering the fallback flow.
In addition, the conflict process includes one or more of a registration process, a service request process and a handover cancellation process.
Further, the processor 610 is further configured to: and determining to trigger the fallback flow again under the condition that a preset trigger period is reached.
In addition, the processor 610 is further configured to: acquiring a flow processing state of the preset conflict flow; and determining to trigger the fallback flow again under the condition that the flow processing state of the preset conflict flow is processing completion.
In addition, the processor 610 is further configured to: and determining to re-trigger the fallback flow under the condition that the flow processing state of the preset conflict processing flow is unfinished and a preset trigger period is reached.
In addition, the processor 610 is further configured to: receiving a triggering request aiming at a fallback procedure of the terminal, wherein the triggering request comprises a target parameter required for triggering the fallback procedure; and generating and storing the cache message based on the trigger request.
In addition, the processor 610 is further configured to: sending the trigger request to a target base station corresponding to the first network; and triggering the fallback procedure under the condition of receiving the fallback processing instruction returned by the target base station.
The embodiment of the invention provides a network side device, which processes a preset conflict flow if a processing request of the preset conflict flow for a terminal is received in the process of triggering the fallback flow for the terminal, wherein the fallback flow is a flow for switching or redirecting the terminal from a first network to a second network so that the terminal processes a target service in the second network, the preset conflict flow is a service flow which causes the fallback flow not to be normally triggered, whether the fallback flow is triggered again is determined based on a preset cache triggering mechanism, and the fallback flow is triggered based on a prestored cache message corresponding to the fallback flow under the condition that the fallback flow is determined to be triggered again, and the cache message comprises a target parameter required for processing the fallback flow. Therefore, whether the fallback flow is triggered again or not can be determined based on the preset cache triggering mechanism, and the fallback flow is triggered again under the condition that the fallback flow is determined to be triggered again, so that the fallback flow triggering failure caused by processing the preset conflict processing flow is avoided, the triggering success rate of the fallback flow is improved, and the voice call experience of a terminal user is improved.
It is understood that, in the embodiment of the present invention, the radio frequency unit 601 may be used for receiving and sending signals during a message transmission or call process, and specifically, receives downlink data from a base station and then processes the received downlink data to the processor 610; in addition, uplink data is transmitted to the base station. Generally, radio frequency unit 601 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. Further, the radio frequency unit 601 may also communicate with a network and other devices through a wireless communication system.
The network side device provides the user with wireless broadband internet access through the network module 602, such as helping the user send and receive e-mails, browse webpages, access streaming media, and the like.
The audio output unit 603 may convert audio data received by the radio frequency unit 601 or the network module 602 or stored in the memory 609 into an audio signal and output as sound. Also, the audio output unit 603 can also provide audio output related to a specific function performed by the network-side device 600 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 603 includes a speaker, a buzzer, a receiver, and the like.
The input unit 604 is used to receive audio or video signals. The input Unit 604 may include a Graphics Processing Unit (GPU) 6061 and a microphone 6042, and the Graphics processor 6041 processes image data of a still picture or video obtained by an image capturing apparatus (such as a camera) in a video capture mode or an image capture mode. The processed image frames may be displayed on the display unit 606. The image frames processed by the graphic processor 6041 may be stored in the memory 609 (or other storage medium) or transmitted via the radio frequency unit 601 or the network module 602. The microphone 6042 can receive sounds and can process such sounds into audio data. The processed audio data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 601 in case of the phone call mode.
The network-side device 600 further includes at least one sensor 605, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the luminance of the display panel 6061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 6061 and/or the backlight when the network-side device 600 is moved to the ear. As one type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used to identify the device attitude (such as horizontal and vertical screen switching, related games, magnetometer attitude calibration), vibration identification related functions (such as pedometer, tapping), and the like; the sensors 605 may also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., which are not described in detail herein.
The display unit 606 is used to display information input by the user or information provided to the user. The Display unit 606 may include a Display panel 6061, and the Display panel 6061 may be configured by a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.
The user input unit 607 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the apparatus. Specifically, the user input unit 607 includes a touch panel 6071 and other input devices 6072. Touch panel 6071, also referred to as a touch screen, may collect touch operations by a user on or near it (e.g., operations by a user on or near touch panel 6071 using a finger, stylus, or any other suitable object or attachment). The touch panel 6071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 610, receives a command from the processor 610, and executes the command. In addition, the touch panel 6071 can be implemented by various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. The user input unit 607 may include other input devices 6072 in addition to the touch panel 6071. Specifically, the other input devices 6072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a track ball, a mouse, and a joystick, which are not described herein again.
Further, the touch panel 6071 can be overlaid on the display panel 6061, and when the touch panel 6071 detects a touch operation on or near the touch panel 6071, the touch operation is transmitted to the processor 610 to determine the type of the touch event, and then the processor 610 provides a corresponding visual output on the display panel 6061 according to the type of the touch event. Although in fig. 6, the touch panel 6071 and the display panel 6061 are two independent components to implement the input and output functions of the apparatus, in some embodiments, the touch panel 6071 and the display panel 6061 may be integrated to implement the input and output functions of the apparatus, and is not limited herein.
The interface unit 608 is an interface for connecting an external device to the network-side apparatus 600. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 608 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the network-side apparatus 600 or may be used to transmit data between the network-side apparatus 600 and the external device.
The memory 609 may be used to store software programs as well as various data. The memory 609 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 609 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
The processor 610 is a control center of the apparatus, connects various parts of the entire apparatus using various interfaces and lines, performs various functions of the apparatus and processes data by running or executing software programs and/or modules stored in the memory 609, and calling up data stored in the memory 609, thereby performing overall monitoring of the apparatus. Processor 610 may include one or more processing units; preferably, the processor 610 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 610.
The network side device 600 may further include a power supply 611 (such as a battery) for supplying power to each component, and preferably, the power supply 611 may be logically connected to the processor 610 through a power management system, so as to implement functions of managing charging, discharging, and power consumption management through the power management system.
Preferably, an embodiment of the present invention further provides a network-side device, which includes a processor 610, a memory 609, and a computer program that is stored in the memory 609 and can be run on the processor 610, and when being executed by the processor 610, the computer program implements each process of the fallback flow triggering method embodiment, and can achieve the same technical effect, and is not described herein again to avoid repetition.
EXAMPLE five
The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the above fallback flow triggering method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
The embodiment of the invention provides a computer-readable storage medium, which processes a preset conflict flow if a processing request of a preset conflict flow for a terminal is received in the process of triggering the fallback flow for the terminal, wherein the fallback flow is a flow for switching or redirecting the terminal from a first network to a second network so that the terminal processes a target service in the second network, the preset conflict flow is a service flow which causes the fallback flow not to be normally triggered, and determines whether to trigger the fallback flow again based on a preset cache triggering mechanism. Therefore, whether the fallback flow is triggered again or not can be determined based on the preset cache triggering mechanism, and the fallback flow is triggered again under the condition that the fallback flow is determined to be triggered again, so that the fallback flow triggering failure caused by processing the preset conflict processing flow is avoided, the triggering success rate of the fallback flow is improved, and the voice call experience of a terminal user is improved.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention 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 invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. 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.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention 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 above description is only an example of the present invention and is not intended to limit the present invention. Various modifications and alterations to this invention will become apparent to those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the scope of the claims of the present invention.
Claims (10)
1. A fall-back procedure triggering method is applied to a network element side device, and the method comprises the following steps:
in the process of triggering a fallback flow for a terminal, if a processing request for a preset conflict flow for the terminal is received, processing the preset conflict flow, where the fallback flow is a flow for switching or redirecting the terminal from a first network to a second network so that the terminal processes a target service in the second network, and the preset conflict flow is a service flow that causes the fallback flow not to be normally triggered;
determining whether to trigger the fallback flow again based on a preset cache triggering mechanism;
and under the condition that the fallback flow is determined to be triggered again, triggering the fallback flow based on a pre-stored cache message corresponding to the fallback flow, wherein the cache message comprises a target parameter required for triggering the fallback flow.
2. The method of claim 1, wherein the conflict flow comprises one or more of a registration flow, a service request flow, and a handover cancellation flow.
3. The method of claim 2, wherein the determining whether to re-trigger the fallback flow based on a preset cache triggering mechanism comprises:
and determining to trigger the fallback flow again under the condition that a preset trigger period is reached.
4. The method of claim 2, wherein the determining whether to re-trigger the fallback flow based on a preset cache triggering mechanism comprises:
acquiring a flow processing state of the preset conflict flow;
and determining to re-trigger the fallback flow under the condition that the flow processing state of the preset conflict flow is processing completion.
5. The method of claim 4, further comprising:
and determining to trigger the fallback flow again under the condition that the flow processing state of the preset conflict processing flow is not finished and a preset trigger period is reached.
6. The method according to claim 2, wherein in the process of triggering the fallback flow for the terminal, before processing the preset conflict flow if a processing request for the preset conflict flow for the terminal is received, further comprising:
receiving a triggering request aiming at a fallback flow of the terminal, wherein the triggering request comprises a target parameter required for triggering the fallback flow;
and generating and storing the cache message based on the trigger request.
7. The method of claim 6, further comprising:
sending the trigger request to a target base station corresponding to the first network;
and triggering the fallback procedure under the condition of receiving the fallback processing instruction returned by the target base station.
8. A fall back procedure triggering apparatus, the apparatus comprising:
the processing module is used for processing a preset conflict flow if a processing request for the preset conflict flow of a terminal is received in the process of triggering the fallback flow of the terminal, wherein the fallback flow is a flow for switching or redirecting the terminal from a first network to a second network so that the terminal processes a target service in the second network, and the preset conflict flow is a service flow which can not be normally triggered;
the determining module is used for determining whether to trigger the fallback flow again based on a preset cache triggering mechanism;
and the triggering module is used for triggering the fallback flow based on a pre-stored cache message corresponding to the fallback flow under the condition that the fallback flow is determined to be triggered again, wherein the cache message comprises a target parameter required for triggering the fallback flow.
9. A network-side device comprising a processor, a memory, and a computer program stored on the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the fallback flow triggering method according to any one of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the fallback procedure triggering method according to one of the claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110316216.9A CN115134823B (en) | 2021-03-24 | 2021-03-24 | Fallback flow triggering method and device and network side equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110316216.9A CN115134823B (en) | 2021-03-24 | 2021-03-24 | Fallback flow triggering method and device and network side equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115134823A true CN115134823A (en) | 2022-09-30 |
| CN115134823B CN115134823B (en) | 2024-08-27 |
Family
ID=83375105
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110316216.9A Active CN115134823B (en) | 2021-03-24 | 2021-03-24 | Fallback flow triggering method and device and network side equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115134823B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105309035A (en) * | 2014-04-30 | 2016-02-03 | 华为技术有限公司 | Mobility management entity and method for processing downlink circuit switched cs service |
| CN107211329A (en) * | 2015-05-05 | 2017-09-26 | 华为技术有限公司 | Method, the network equipment and the system of circuit domain dropping |
| CN110876169A (en) * | 2018-09-03 | 2020-03-10 | 中国移动通信集团设计院有限公司 | Method and device for saving call after circuit switched fallback abnormity |
-
2021
- 2021-03-24 CN CN202110316216.9A patent/CN115134823B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105309035A (en) * | 2014-04-30 | 2016-02-03 | 华为技术有限公司 | Mobility management entity and method for processing downlink circuit switched cs service |
| CN107211329A (en) * | 2015-05-05 | 2017-09-26 | 华为技术有限公司 | Method, the network equipment and the system of circuit domain dropping |
| CN110876169A (en) * | 2018-09-03 | 2020-03-10 | 中国移动通信集团设计院有限公司 | Method and device for saving call after circuit switched fallback abnormity |
Non-Patent Citations (3)
| Title |
|---|
| MEDIATEK INC. / MARKO: "C1-207731 "UE procedures when a request for emergency services fallback not accepted"", 3GPP TSG_CT\\WG1_MM-CC-SM_EX-CN1, no. 1, 19 November 2020 (2020-11-19) * |
| NEC: "R2-1906755 "Details on fallback mechanisms"", 3GPP TSG_RAN\\WG2_RL2, no. 2, 3 May 2019 (2019-05-03) * |
| 彭家兵;: "一种CSFB性能提升方法", 信息通信, no. 08, 15 August 2018 (2018-08-15) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115134823B (en) | 2024-08-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210168690A1 (en) | Information processing method for a radio link failure, terminal, and network device | |
| CN108509299B (en) | Message processing method, device and computer readable storage medium | |
| CN108768775B (en) | Information processing method, electronic device, and computer storage medium | |
| CN107749919B (en) | Application program page display method and device and computer readable storage medium | |
| CN107959952B (en) | Method and terminal for detecting inter-system cell | |
| CN109819489B (en) | Terminal calling method and terminal | |
| CN110167041B (en) | Beam failure recovery request sending method and user equipment | |
| CN107172605B (en) | Emergency call method, mobile terminal and computer readable storage medium | |
| CN107124428B (en) | Method, equipment and storage medium for improving VoLTE call success rate | |
| CN113973326B (en) | Wireless capability identifier transmission method, terminal equipment and network node | |
| US20210014922A1 (en) | Connection re-establishment method and related device | |
| WO2023060988A1 (en) | Reestablishment method in communication abnormality, terminal device, and storage medium | |
| JP2021511727A (en) | Service instruction method, terminal, network unit and storage medium | |
| CN113301603A (en) | Data transmission method, device and medium | |
| CN112494932A (en) | Game frame supplementing method and device, terminal and computer readable storage medium | |
| CN109587260B (en) | Resource acquisition method, device and system | |
| CN109818967B (en) | Notification method, server, mobile terminal and computer readable storage medium | |
| US11412433B2 (en) | Method of processing beam failure recovery and user equipment | |
| CN113438652A (en) | Authorization and policy parameter configuration method, terminal and network function | |
| CN107404568B (en) | Control switch management method and mobile terminal | |
| CN115134823B (en) | Fallback flow triggering method and device and network side equipment | |
| KR102589489B1 (en) | Random access method and terminal device | |
| CN111615158B (en) | Updating method, reconstruction request processing method, terminal and network equipment | |
| CN110839298B (en) | Mobility management method and related equipment | |
| CN108304302B (en) | Interface merging method, equipment and computer readable storage medium |
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 |