Patent Application
20240406840
The present disclosure relates to the field of communication technology and, in particular, to a path fallback method and apparatus, and a storage medium.
In a multi-hop relay network, data transmission between a user equipment (UE) and a donor base station can pass through one or more relay nodes. In 5G, the multi-hop relay network is also referred to as an integrated access and backhaul (IAB) network.
In the IAB network, for a load consideration, or based on a measurement report or the like that is reported by an edge IAB node, a source IAB donor can migrate F1 of the edge IAB node from a source path to a target path. However, current related protocols only support the migration, by the source IAB donor, on F1 of the edge IAB node from the source path to the target path, and do not support a fallback for F1 of the edge IAB node which has been migrated to the target path.
The present disclosure provides a path fallback method and apparatus, and a storage medium, realizing a path fallback for F1 of the edge IAB node which has been migrated to the target path.
In a first aspect, an embodiment of the present disclosure provides a path fallback method, including:
In an implementation, the transmitting the indication information to the target IAB donor and/or the edge IAB node includes:
In an implementation, the first message is an XnAP message.
In an implementation, the first configuration information includes any one or more of the following items:
In an implementation, the transmitting the indication information to the target IAB donor and/or the edge IAB node includes:
In an implementation, the second message is an RRC message, and the transmitting the second message to the edge IAB node includes:
In an implementation, the second message is an FIAP message, and the transmitting the second message to the edge IAB node includes:
In an implementation, the second configuration information includes any one or more of the following items:
In an implementation, the determining to migrate F1 of the edge IAB node from the target path to the first path includes:
In an implementation, the method further includes:
In an implementation, the transmitting the RRC reconfiguration message to the edge IAB node includes: transmitting the RRC reconfiguration message to the edge IAB node through the IAB parent node of the first path: the receiving the RRC reconfiguration completion message transmitted by the edge IAB node includes: receiving the RRC reconfiguration completion message which is transmitted by the edge IAB node through an IAB parent node of the target path.
In an implementation, the third configuration information includes any one or more of the following items:
In a second aspect, the present disclosure provides a path fallback apparatus, including a memory, a transceiver and a processor:
In an implementation, the processor is specifically configured to perform the following operation:
In an implementation, the first message is an XnAP message.
In an implementation, the first configuration information includes any one or more of the following items:
In an implementation, the processor is further configured to perform the following operation:
In an implementation, the second message is an RRC message, and the processor is specifically configured to perform the following operation: transmitting the second message to an MT of the edge IAB node.
In an implementation, the second message is an FIAP message, and the processor is specifically configured to perform the following operation: transmitting the second message to a DU of the edge IAB node.
In an implementation, the second configuration information includes any one or more of the following items:
In an implementation, the processor is configured to perform the following operation:
In an implementation, the processor is configured to perform the following operations:
In an implementation, the processor is specifically configured to perform the following operations:
In an implementation, the third configuration information includes any one or more of the following items:
In a third aspect, the present disclosure provides a path fallback apparatus, including:
In an implementation, the transmitting unit is configured to:
In an implementation, the first message is an XnAP message.
In an implementation, the first configuration information includes any one or more of the following items:
In an implementation, the transmitting unit is configured to:
In an implementation, the second message is an RRC message, and the transmitting unit is configured to:
In an implementation, the second message is an FIAP message, and the transmitting unit is configured to:
In an implementation, the second configuration information includes any one or more of the following items:
In an implementation, the determining unit is configured to:
In an implementation, the transmitting unit is configured to: transmit an RRC reconfiguration message to the edge IAB node, the RRC reconfiguration message being used for handing over the edge IAB node to an IAB parent node of the first path:
In an implementation, the transmitting unit is configured to: transmit the RRC reconfiguration message to the edge IAB node through the IAB parent node of the first path; and
In an implementation, the third configuration information includes any one or more of the following items:
In a fourth aspect, the present disclosure provides a computer readable storage medium, storing thereon a computer program, where the computer program is configured to enable a computer to implement the method according to the first aspect and any implementation thereof.
In a fifth aspect, the present disclosure provides a computer program product, including a computer program, where the computer program, when being executed by a processor, implements the method according to the first aspect and any implementation thereof.
The present disclosure provides a path fallback method and apparatus, and a storage medium. In the method, a source IAB donor, after migrating F1 of an edge IAB node from a source path to a target path, can further perform a fallback for F1 of the edge IAB node which has been migrated to the target path, to migrate F1 of the edge IAB node back to the source path or an else path, and give an indication to a target IAB donor and/or the edge IAB node to release or suspend configuration information for transmitting, on the target path, all or part of F1 of the edge IAB node, to realize a path fallback for F1.
It should be understood that the content described in the foregoing summary section is neither intended to limit key or important features of embodiments of the present disclosure, nor is used to limit the scope of the present disclosure. Other features of the present disclosure will become readily comprehensible through the following description.
The term “and/or” in the present disclosure describes an association relationship of associated objects, indicating that there can be three relationships, for example, A and/or B can indicate that A exists alone, A and B exist at the same time, and B exists alone. The character “/” generally indicates that the context objects are in an “or” relationship. In the embodiments of the present application, the term “a plurality of” refers to two or more, other quantifiers are similar thereto.
The embodiments of the present disclosure will be described hereunder clearly and comprehensively in conjunction with the accompanying drawings in the embodiments of the present disclosure. Apparently, the described embodiments are merely some of, rather than all of the embodiments of the present disclosure.
The embodiments of the present disclosure provide a path fallback method and apparatus which, in a scenario where a source IAB donor has migrated F1 of an edge IAB node from a source path to a target path, realize a path fallback for F1 of the edge IAB node which has been migrated to the target path. The method and apparatus are based on a same embodiments. Since the problem-solving principle for the method is similar to that for the apparatus, cross reference can be made between the implementations of the apparatus and the method, and repetitions will not be elaborated.
The embodiments of the present disclosure can be applied to various systems, especially a 5G system. For example, an applicable system can be a global system of mobile communication (GSM), a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, a long term evolution advanced (LTE-A) system, a universal mobile telecommunication system (UMTS), a worldwide interoperability for microwave access (WiMAX), 5G new radio (NR), and so on. Each of these various systems includes therein a terminal device and a network device. The system can further include a core network part such as an evolved packet system (EPS), a 5G System (5GS) or the like.
A terminal device related to embodiments of the present disclosure, can refer to a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connectivity function, or other processing devices connected to a wireless modem. In different systems, the terminal device may vary in name. For example, in a 5G system, the terminal device can be referred to as a user equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) through a radio access network (RAN). The wireless terminal device can be a mobile terminal device such as a mobile phone (or referred to as a “cellular” phone) and a computer with a mobile terminal device, for example, it can be a mobile apparatus which is portable, pocket-sized, handheld, built-in a computer or vehicle-mounted, and exchanges voice and/or data with the radio access network. For example, a personal communication service (PCS) phone, a cordless phone, a session initiated protocol (SIP) phone, wireless local loop (WLL) station, a personal digital assistant (PDA), or the like. The wireless terminal device can also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile platform, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, a user device, which is not limited in the embodiments of the present disclosure.
A base station related to the embodiments of the present disclosure can include multiple cells that provide services to the terminal. Depending on the specific application scenarios, a base station can also be referred to as an access point or a device in an access network that communicates with a wireless terminal device through one or more sectors on an air interface, or any other names. For example, the base station related to the embodiments of the present disclosure can be an evolutional network device (evolutional Node B, eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a 5G network architecture (next generation system), a home evolved Node B (HeNB), a relay node, a femto, a pico or the like, which is not limited in the embodiments of the present disclosure. In some network structures, the base station can include a centralized unit (CU) node and a distributed unit (DU) node, where the centralized unit and the distributed unit can be arranged geographically separated.
Each of the base station and the terminal device can use one or multiple antennas for Multi Input Multi Output (MIMO) transmission, where the MIMO transmission can be Single User MIMO (SU-MIMO) or Multiple User MIMO (MU-MIMO). Depending on the pattern and quantity of antennas, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, it can also be diversity transmission, precoded transmission, beamforming transmission, or the like.
Firstly, an IAB network will be introduced in the following.
As shown in
For a load consideration, or based on a measurement report or the like that is reported by an edge IAB node, the source IAB donor can migrate F1 of the edge IAB node from a source path to a target path. Exemplarily, as shown in
Therefore, it is proposed in the embodiments of the present disclosure that, the source IAB donor CU, after migrating F1 of the edge IAB node from the source path to the target path, can further perform a fallback for F1 of the edge IAB node which has been migrated to the target path, to migrate F1 of the edge IAB node back to the source path or an else path, and give an indication to the target IAB donor and/or the edge IAB node to release or suspend configuration information for transmitting, on the target path, all or part of F1 of the edge IAB node. In the following, the path fallback method according to the present disclosure will be explained in detail through specific embodiments. It should be understood that, the following specific embodiments can be combined with each other, for the same or similar concepts or processes, description may not be repeated in some embodiments.
S301, determining to migrate F1 of an edge IAB node from a target path to a first path.
The first path is a source path or an else path, the source path being a path used by F1 of the edge IAB node before using the target path, and the else path being a path other than the target path and the source path.
The source IAB donor, after migrating F1 of the edge IAB node from the source path to the target path, can determine, based on at least one item of a load of the source IAB donor, a load of the target IAB donor, a load of a neighboring cell, or a measurement report of the edge IAB node, to migrate F1 of the edge IAB node from the target path to the first path, namely, to perform a path fallback for F1 of the edge IAB node. F1 in this fallback scenario is offload traffic, which has been offloaded from the source path to the target path, and which can include F1-C, F1-U, non-F1 traffic, or the like.
In an implementation, the source IAB donor itself does not have a significant load and it is no longer necessary to offload F1 of the edge IAB node to the target path, then the source IAB donor can migrate F1 of the edge IAB node from the target path back to the source path. As an example, if the load of the source IAB donor is less than a first threshold, it is determined to migrate F1 of the edge IAB node from the target path to the source path.
In an implementation, the source IAB donor determines that the target IAB donor has an excessive load and cannot support F1 that has been offloaded to the target path, then the source IAB donor can migrate F1 of the edge IAB node from the target path back to the source path or the else path. As an example, the source IAB donor CU can receive an Xn Application Protocol (XnAP) message (resource status response, or other new XnAP messages) transmitted by the target IAB donor, to determine that the target IAB donor has an excessive load. As an example, if the load of the target IAB donor is greater than a second threshold, it is determined to migrate F1 of the edge IAB node from the target path to the first path. When it is determined to migrate F1 of the edge IAB node from the target path to the else path, the else path can be determined with reference to the load of a neighboring cell.
In an implementation, the measurement report reported by the edge IAB node indicates that signal quality of the target path is poor while signal quality of the first path is good, then the source IAB donor can migrate F1 of the edge IAB node from the target path to the first path. As an example, the measurement report of the edge IAB node indicates that the signal quality of the target path is less than a third threshold and/or the signal quality of the first path is greater than a fourth threshold, then it is determined to migrate F1 of the edge IAB node from the target path to the first path.
It should be noted that the source IAB donor can determine to migrate F1 of the edge IAB node from the target path to the first path based on a combination of multiple items of the load of the source IAB donor, the load of the target IAB donor, the load of a neighboring cell, or the measurement report of the edge IAB node.
S302, transmitting indication information to a target IAB donor and/or the edge IAB node, the indication information being used to give an indication to release or suspend configuration information for transmitting, on the target path, all or part of F1 of the edge IAB node.
When the source IAB donor determines to migrate F1 of the edge IAB node from the target path to the first path, the source IAB donor gives an indication to the target IAB donor and/or the edge IAB node to release or suspend the configuration information for transmitting, on the target path, all or part of F1 of the edge IAB node.
In an implementation, the source IAB donor gives an indication to the target IAB donor and/or the edge IAB node to release or suspend the configuration information for transmitting, on the target path, all of F1 of the edge IAB node. It should be understood that releasing or suspending the configuration information for transmitting, on the target path, all of F1 of the edge IAB node, means releasing all of the offload traffic. For example, the indication information is an All Traffic Indication which is used for releasing all of the offload traffic. In an implementation, the source IAB donor gives an indication to the target IAB donor and/or the edge IAB node to release or suspend the configuration information for transmitting, on the target path, part of F1 of the edge IAB node. It should be understood that releasing or suspending the configuration information for transmitting, on the target path, part of F1 of the edge IAB node, means releasing part of the offload traffic. For example, the indication information is Traffic to Be Released Information which is used for releasing indicated part of the offload traffic.
When the source IAB donor give an indication to the target IAB donor to release the configuration information for transmitting, on the target path, all or part of F1 of the edge IAB node, the target IAB donor can use a resource associated with such configuration information for transmitting other F1, to improve resource utilization. When the source IAB donor gives an indication to the target IAB donor to suspend the configuration information for transmitting, on the target path, all or part of F1 of the edge IAB node, the target IAB donor temporarily stores such configuration information without further use. When the source IAB donor needs to migrate F1 of the edge IAB node to the target path again, the configuration information can be quickly activated to enable a quick migration.
The source IAB donor gives an indication to the edge IAB node to release the configuration information for transmitting, on the target path, all or part of F1 of the edge IAB node, it is possible to prevent the edge IAB node from storing unnecessary information. When the source IAB donor gives an indication to the edge IAB node to suspend the configuration information for transmitting, on the target path, all or part of F1 of the edge IAB node, the edge IAB node temporarily stores such configuration information, and in case the source IAB donor needs to migrate F1 of the edge IAB node to the target path again, the information carried in a reconfiguration process of the edge IAB node following the further migration from the source path to the target path can be reduced.
In the path fallback method according to the embodiments of the present disclosure, the source IAB donor, after migrating F1 of the edge IAB node from the source path to the target path, can further perform a fallback for F1 of the edge IAB node which has been migrated to the target path, to migrate F1 of the edge IAB node back to the source path or an else path, and give an indication to the target IAB donor and/or the edge IAB node to release or suspend configuration information for transmitting, on the target path, all or part of F1 of the edge IAB node, to realize a path fallback for F1.
Based on the foregoing embodiments, further explanations are made regarding the source IAB donor migrating F1 of the edge IAB node from the target path to the source path or an else path, and giving an indication to the target IAB donor and/or the edge IAB node to release or suspend the configuration information.
With reference to
S401, a source IAB donor determines to migrate F1 of an edge IAB node from a target path to a first path.
This step is similar to S301 in the foregoing embodiment, which will not be repeated here.
S402, the source IAB donor transmits a radio resource control (RRC) reconfiguration message to the edge IAB node, the RRC reconfiguration message being used for handing over the edge IAB node to an IAB parent node of the first path.
After the source IAB donor determines to migrate F1 of the edge IAB node from the target path to the first path, the source IAB donor needs to hand over the edge IAB node to the IAB parent node of the first path, where the IAB parent node refers to an upstream node of the edge IAB node.
This process can be achieved through an RRC reconfiguration message. In an implementation, the source IAB donor can transmit the RRC reconfiguration message to the edge IAB node through the IAB parent node of the first path.
Take an example where the source IAB donor determines to migrate F1 of the edge IAB node from the target path to the source path, with reference to
S403, the edge IAB node performs random access to the IAB parent node of the first path.
Still take an example where the first path is the source path, the edge IAB node performs random access to the IAB node 1. It should be noted that the timing of random access can be determined based on a practical situation, and is not limited to immediate random access after the edge IAB node receives the RRC reconfiguration message, which is only provided as an example in the embodiment of the present disclosure.
S404, the edge IAB node transmits an RRC reconfiguration completion message to the source IAB donor.
In an implementation, the edge IAB node transmits the RRC reconfiguration completion message to the source IAB donor through the IAB parent node of the target path. Namely, the source IAB donor receives the RRC reconfiguration completion message which is transmitted by the edge IAB node through the IAB parent node of the target path. With reference to
S405, configuring or activating third configuration information of each node of the first path, the third configuration information being used for transmitting F1 of the edge IAB node.
To achieve the transmission of F1 of the edge IAB node on the first path, corresponding configuration is required. Still take an example where the first path is the source path, when the source IAB donor migrates F1 of the edge IAB node from the source path to the target path, if the third configuration information of each node on the source path is deleted, reconfiguration is required, and if the third configuration information is suspended, only activation is required. In one embodiment, the migration of F1 of the edge IAB node back to the source path is achieved.
In an implementation, the third configuration information includes any one or more of the following items:
Among them, the IP to L2 mapping is used to map F1 to a BH RLC channel: the mapping between the ingress BH RLC channel and the egress BH RLC channel refers to mapping between the ingress BH RLC channel and the egress BH RLC channel when data passes through an IAB node; and the BAP routing configuration is a BAP routing ID for F1, which consists of a path ID and a destination BAP address, used for determining a next hop.
S406, the source IAB donor transmits a first message to the target IAB donor, the first message being used to give an indication to the target IAB donor to release or suspend first configuration information which is used for transmitting all or part of F1 of the edge IAB node.
In an implementation, the first message is an XnAP message.
In an implementation, the first configuration information includes any one or more of the following items:
In an implementation, through an XnAP message, the source IAB donor gives an indication to the target IAB donor CU to release or suspend the first configuration information. Subsequently, the target IAB donor CU transmits an FIAP message to the target IAB donor DU, to give an indication to the target IAB donor DU to release or suspend the first configuration information.
S407, the source IAB donor transmits a second message to the edge IAB node, the second message being used to give an indication to the edge IAB node to release or suspend second configuration information which is used for transmitting, on the target path, all or part of F1 of the edge IAB node.
In an implementation, the second message is an RRC message, and the source IAB donor transmits the second message to an MT of the edge IAB node, to give an indication to the edge IAB node to release or suspend the second configuration information.
In an implementation, the second message is an FIAP message, and the source IAB donor transmits the second message to a DU of the edge IAB node, to give an indication to the edge IAB node to release or suspend the second configuration information.
In an implementation, the second configuration information includes any one or more of the following items:
The BAP header rewrite table is used for rewriting BAP header information belonging to a first topology into BAP header information belonging to a second topology, achieving data transmission through the target path. The BAP header information contains a BAP routing ID, that is, a BAP routing ID of the first topology is rewritten into a BAP routing ID of the second topology. As an example, when a downlink data packet arrives at the edge IAB node with the BAP header information belonging to Topology 2, rewriting into BAP header information belonging to Topology 1 is required at the edge IAB node; and when an uplink data packet arrives at the edge IAB node with the BAP header information belonging to Topology 1, rewriting into the BAP header information belonging to Topology 2 is required at the edge IAB node.
In the path fallback method according to the embodiments of the present disclosure, the source IAB donor, based on a determination on a load, a measurement report or the like, performs a fallback, for F1 which has been offloaded to the target path, to the source path or the else path. Upon the fallback of F1 to the source path or the else path, related configuration on the target path, which is associated with F1, can be released or suspended. If released, a resource associated with such configuration can be used for transmission of other F1 belonging to the target IAB donor, to improve resource utilization: if suspended, it can be achieved that F1 is migrated to the target path for a second time quickly. For example, when the source IAB donor is unstable, F1 needs to be migrated to the target path for a second time in a short term: or when the target IAB donor is in an instantaneous load peak, only a temporary fallback to the source path or the else path is needed for F1 followed by a further migration to the target path, and the suspended configuration can be quickly activated for a migration once more. In addition, the source IAB donor can give an indication to the edge IAB node to release the configuration associated with the target path, to prevent the edge IAB node from storing unnecessary information. Alternatively, it can also give an indication to the edge IAB node to suspend the configuration associated with the target path, and the information carried in a reconfiguration process of the edge IAB node following the further migration to the target path can be reduced.
The memory 501 is configured to store a computer program:
In an implementation, the processor 503 is specifically configured to perform the following operation:
In an implementation, the first message is an XnAP message.
In an implementation, the first configuration information includes any one or more of the following items:
In an implementation, the processor 503 is further configured to perform the following operation:
In an implementation, the second message is an RRC message, and the processor 503 is specifically configured to perform the following operation: transmitting the second message to an MT of the edge IAB node.
In an implementation, the second message is an FIAP message, and the processor 503 is specifically configured to perform the following operation: transmitting the second message to a DU of the edge IAB node.
In an implementation, the second configuration information includes any one or more of the following items:
In an implementation, the processor 503 is configured to perform the following operation:
In an implementation, the processor 503 is configured to perform the following operations:
In an implementation, the processor 503 is specifically configured to perform the following operations:
In an implementation, the third configuration information includes any one or more of the following items:
It should be noted that the aforementioned apparatus according to the present disclosure can implement all of the method steps in the foregoing method embodiments, and achieve a same effect. Same contents and beneficial effects of this embodiment as those of the method embodiments will not be specifically elaborated here.
In an implementation, the transmitting unit 602 is configured to:
In an implementation, the first message is an XnAP message.
In an implementation, the first configuration information includes any one or more of the following items:
In an implementation, the transmitting unit 602 is configured to:
In an implementation, the second message is an RRC message, and the transmitting unit 602 is configured to:
In an implementation, the second message is an FIAP message, and the transmitting unit 602 is configured to:
In an implementation, the second configuration information includes any one or more of the following items:
In an implementation, the determining unit 601 is configured to:
In an implementation, the transmitting unit 602 is configured to: transmit an RRC reconfiguration message to the edge IAB node, the RRC reconfiguration message being used for handing over the edge IAB node to an IAB parent node of the first path:
In an implementation, the transmitting unit 602 is configured to: transmit the RRC reconfiguration message to the edge IAB node through the IAB parent node of the first path; and
In an implementation, the third configuration information includes any one or more of the following items:
It should be noted that the aforementioned apparatus according to the present disclosure can implement all of the method steps in the foregoing method embodiments, and achieve a same effect. Same contents and beneficial effects of this embodiment as those of the method embodiments will not be specifically elaborated here.
It should be noted that, in the embodiments of the present disclosure, the partition of the units, being illustrative, is only a logical function partition, and there may be other manners for partition in an actual implementation. In addition, respective functional units in the embodiments of the present disclosure may be integrated into a processing unit, or may exist alone physically, or two or more units may be integrated into one unit. The aforementioned integrated unit can be implemented in a form of hardware, or it can also be implemented in a form of a software function unit.
The aforementioned integrated unit may be stored in a processor readable storage medium if being implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the embodiments of the present disclosure, substantively, or a part of which that makes a contribution to the prior art, or the whole or a part of which, may be embodied in the form of a software product which is stored in a storage medium, where the instructions are included to cause a computer device (which can be a personal computer, a server, a network device, etc.) or a processor to execute all or part of the steps of the methods according to the various embodiments of the present disclosure. The aforementioned storage medium includes: a USB flash disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, or other media that can store program codes.
An embodiment of the present disclosure further provides a computer readable storage medium, storing thereon a computer program, where the computer program is configured to enable a computer to implement the method according to the foregoing method embodiments.
The computer readable storage medium can be any available medium or data storage device that the computer can access, including but not limited to a magnetic memory (such as a floppy disk, a hard drive, a magnetic tape, a magneto-optical disk (MO), etc.), an optical memory (such as a CD, a DVD, a BD, an HVD, etc.), as well as a semiconductor memory (such as a ROM, an EPROM, an EEPROM, a non-volatile memory (NAND FLASH), a solid-state drive (SSD), etc.).
An embodiment of the present disclosure further provides a computer program product, including a computer program, where the computer program, when being executed by a processor, implements the method according to the foregoing method embodiments.
The embodiments of the present disclosure can be provided as a method, a system, or a computer program product. Therefore, the present disclosure can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the disclosure can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to a magnetic disk storage and an optical storage) containing computer-usable program codes therein.
Embodiments of the present disclosure are described with reference to flowcharts and/or block diagrams of the method, device (system) and computer program product according to the embodiments of the present disclosure. It should be understood that each flow and/or block in the flowchart and/or block diagram, and combinations of the flows and/or blocks in the flowchart and/or block diagram can be implemented by the computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, and the instructions executed by the processor of the computer or other programmable data processing device produce means for implementing the functions specified in one or more flows in the flowcharts and/or one or more blocks in the block diagrams.
These processor executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to function in a particular manner, and the instructions stored in the processor-readable memory produce an article of manufacture including instruction means that implement the functions specified in one or more flows in the flowcharts and/or one or more blocks in the block diagram.
These computer program instructions may also be loaded onto a computer or other programmable data processing devices, and a series of operational steps are performed on the computer or other programmable devices to produce a computer-implemented process, and the instructions executed on the computer or other programmable devices provide steps for implementing the functions specified in one or more flows in the flowcharts and/or one or more blocks in the block diagram.
Apparently, various modifications and variations can be made to the embodiments of the present disclosure. Thus, if these modifications and variations of the embodiments of the present disclosure are within the scope of the claims of the present disclosure and their equivalents, the present disclosure is also intended to include these modifications and variations.
| Number | Date | Country | Kind |
|---|---|---|---|
| 202111236259.2 | Oct 2021 | CN | national |
This disclosure is a National Stage of International Application No. PCT/CN2022/123872, filed on Oct. 8, 2022, which claims priority to Chinese Patent Application No. 202111236259.2, filed on Oct. 22, 2021, both of the applications are hereby incorporated by reference in their entireties.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/CN2022/123872 | 10/8/2022 | WO |
