Information transmission method and device, storage medium, electronic device

Abstract

The present disclosure provides an information transmission method and apparatus, a storage medium, and an electronic device, the method including a step of sending first fallback request information to a third node or a second node, the first fallback request information including at least one of a fallback cause, functional module information of the first fallback, falling back to legacy mode, and a first fallback start time.

Description

[Technical field]

[0001] TECHNICAL FIELD Embodiments of the present disclosure relate to the field of communications, and in particular to information transmission methods and apparatus, storage media, and electronic devices. [Background technology]

[0002] In terms of related technologies, the large-scale commercialization of the 5th Generation Mobile Communication System (5G) New Radio (NR) is accelerating the digitalization, networking, and intelligentization of the economy and society, and the network is moving towards a new era of a world where everything is connected to the Internet (IoE). The rapidly emerging needs for applications in areas such as smart cities, smart transportation, and smart industrial production are continuously strengthening the development trends of differentiated network device capabilities, diversifying network functions, and intelligent network management and control, further promoting the arrival of the 6th Generation Mobile Communication System (6G), where everything is smartly connected.

[0003] In typical 6G application scenarios, such as smart cities, smart transportation, and smart homes, there will be a large number of smart automation devices with highly differentiated capabilities, and the communication requirements will be more stringent in terms of extremely low latency, extremely high reliability, ultra-wide bandwidth, and massive access. The application of smart automation types also requires high precision, high resolution, and other requirements for sensing capabilities.

[0004] On the one hand, the rapid increase in the number of wireless communication and sensing devices has made the contradiction between the infinite growth of service demand and the finite wireless resources and computing power increasingly obvious; on the other hand, the realization of the 6G vision requires closed-loop information flow processing, from obtaining environmental sensing information, interacting and sharing information, and smart information processing to the layer-by-layer distribution of control information (including control information for communication networks and control commands for application execution devices).

[0005] Conventional wireless network architectures and related technologies are already finding it difficult to meet the ever-emerging application needs of the Beyond 5G (5G and Beyond, B5G) / 6G era, making it urgent to develop new network architectures and enabling technologies that utilize resources efficiently and differentiate the application of smart adapters.

[0006] The rise of artificial intelligence (AI) technologies, including deep learning, reinforcement learning, and distributed learning, has had a wide-ranging and profound impact on the optimization of communication networks, intelligent sensing and control applications, and has greatly promoted the possibility of deep integration of communication, sensing, and computing. Based on this, if 6G realizes the integration and symbiosis of communication and sensing capabilities under the empowerment of smart computing technology, it will give 6G networks the ability to intelligently sense the physical world and mirror map the digital world at any time and anywhere. The large number of connected new smart terminals will rely on constantly increasing computing power to learn, interact, cooperate, and compete, realizing autonomous learning, autonomous operation, and autonomous maintenance of the network, and further realizing the vision of a 6G communication, sensing, and computing integrated network.

[0007] Currently, in a 5th Generation Mobile Communication System (5G) New Radio (NR), system information is transmitted as a Master Information Block (MIB) via a PBCH in a Primary Synchronization Signal (SSB), and then carries a System Information Block (SIB) via a PDSCH.

[0008] Here, the SIB can be divided into multiple blocks, each carrying different system information. In typical 6G application scenarios, such as smart cities, smart transportation, and smart homes, there are a large number of smart automation devices with highly differentiated capabilities, and communication requirements are increasing in terms of extremely low latency, extremely high reliability, ultra-wide bandwidth, and massive access. In other words, in the 6G era, the types of terminals accessing the system will be very large, and the adoption of the data channel generation method of such a limited type of combination in NR will greatly limit the data transmission efficiency of the terminal, and at the same time, it will also affect the spectrum efficiency of the system.

[0009] The related art does not disclose a means for performing an interaction process of first fallback request information between a first node (e.g., a terminal) and a second node or a third node, and therefore no solution is proposed in the prior art. Summary of the Invention [Problem to be solved by the invention]

[0010] The embodiments of the present disclosure provide an information transmission method and apparatus, a storage medium, and an electronic device to at least solve the problem that the related art does not disclose a means for performing an interaction process of first fallback request information between a first node (e.g., a terminal) and a second node or a third node. [Means for solving the problem]

[0011] According to one embodiment of the present disclosure, an information transmission method is provided, the method including a step of transmitting first fallback request information to a third node or a second node, the first fallback request information including at least one of a fallback cause, functional module information of the first fallback, falling back to legacy mode, and a first fallback start time.

[0012] According to another embodiment of the present disclosure, an information transmission device is provided, comprising: a first transmitting module configured to transmit first fallback request information to a third node or a second node, the first fallback request information including at least one of a fallback cause, functional module information of the first fallback, falling back to legacy mode, and a first fallback start time.

[0013] According to another embodiment of the present disclosure, an information transmission device is provided, the information transmission device including: a second transmitting module configured to transmit first fallback instruction information to a first node, the first fallback instruction information including at least one of functional module information of a third fallback, falling back to legacy mode, and a third fallback start time.

[0014] According to yet another embodiment of the present disclosure, there is further provided a computer readable storage medium having a computer program stored thereon, the computer program being configured, when executed, to perform the steps of any one of the method embodiments described above.

[0015] According to yet another embodiment of the present disclosure, there is further provided an electronic device, comprising a memory and a processor, wherein a computer program is stored in the memory, and wherein the processor is configured to execute the computer program to perform steps in any one of the method embodiments described above. Effect of the Invention

[0016] The present disclosure provides a method for transmitting first fallback request information to a third node or a second node, where the first fallback request information includes at least one of a fallback cause, functional module information of the first fallback, falling back to legacy mode, and a first fallback start time, thereby solving the problem that the related art does not disclose a means for performing an interaction process of the first fallback request information between a first node (e.g., a terminal) and a second node or a third node, and achieving the technical effect of the first node transmitting the first fallback request information to a third node or a second node. [Brief description of the drawings]

[0017] [Figure 1] FIG. 2 is a hardware structure block diagram of a preferred computing and terminal of the information transmission method according to an embodiment of the present disclosure; [Diagram 2] 4 is a flowchart of an information transmission method according to an embodiment of the present disclosure. [Diagram 3] 4 is a flowchart of another information transmission method according to an embodiment of the present disclosure. [Figure 4] 1 is a schematic flow chart (1) of a preferred information transmission method according to an embodiment of the present disclosure. [Diagram 5] 2 is a schematic flow chart (2) of a preferred information transmission method according to an embodiment of the present disclosure. [Figure 6] 3 is a schematic flow chart (3) of a preferred information transmission method according to an embodiment of the present disclosure. [Figure 7] 4 is a schematic flow chart (4) of a preferred information transmission method according to an embodiment of the present disclosure. [Figure 8] 5 is a schematic flow chart (5) of a preferred information transmission method according to an embodiment of the present disclosure. [Figure 9] FIG. 2 is a structural block diagram of an information transmission device according to an embodiment of the present disclosure. [Figure 10]FIG. 11 is a structural block diagram of another information transmission device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] Hereinafter, the embodiments of the present disclosure will be described in detail based on the embodiments with reference to the drawings.

[0019] In addition, terms such as "first" and "second" in the specification, claims and the above drawings of the present disclosure are intended to distinguish between similar objects and do not necessarily describe a specific order or chronology.

[0020] The embodiment of the method provided in the embodiment of the present disclosure can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking the execution in a mobile terminal as an example, FIG. 1 is a hardware structure block diagram of a mobile terminal of the information transmission method of the embodiment of the present disclosure. As shown in FIG. 1, the mobile terminal may include one or more (only one is shown in FIG. 1) processors 102 (processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic circuit FPGA) and a memory 104 for storing data, where the mobile terminal may further include a transmission device 106 and an input / output device 108 for communication functions.

[0021] Those skilled in the art will appreciate that the structure shown in Figure 1 is merely exemplary and is not intended to limit the structure of the mobile terminal described above. For example, the mobile terminal may further include more or less components than those shown in Figure 1, or may have a different configuration than that shown in Figure 1.

[0022] The memory 104 can be used to store computer programs, such as software programs and modules of application software, such as a computer program corresponding to the information transmission method of the embodiments of the present disclosure, and the processor 102 executes various functional applications and data processing, i.e., realizes the above-mentioned methods, by executing the computer programs stored in the memory 104. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.

[0023] In some examples, the memory 104 may further include memories located remotely to the processor 102, which may be connected to the mobile terminal via a network, examples of which include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0024] The transmission device 106 is used to receive or transmit data through a network. A specific example of the network may include a wireless network provided by a communication provider of the mobile terminal. In one example, the transmission device 106 includes a network adapter (abbreviated as Network Interface Controller, NIC) that can communicate with the Internet by connecting to other network devices through a base station. In one example, the transmission device 106 may be a radio frequency (abbreviated as RF) module for communicating with the Internet wirelessly.

[0025] In this embodiment, an information transmission method is provided which is executed in the mobile terminal. FIG. 2 is a flowchart of the information transmission method according to the embodiment of the present disclosure. As shown in FIG. 2, the information transmission method includes: Step S202 includes sending first fallback request information to a third node or a second node, the first fallback request information including at least one of a fallback cause, functional module information of the first fallback, falling back to legacy mode, and a first fallback start time.

[0026] Through the above steps, the first node transmits first fallback request information to the third node or the second node, where the first fallback request information includes at least one of a fallback cause, function module information of the first fallback, falling back to legacy mode, and a first fallback start time. This solves the problem that the related art does not disclose a means for performing an interaction process of the first fallback request information between the first node (e.g., a terminal) and the second node or the third node, and achieves the technical effect of the first node transmitting the first fallback request information to the third node or the second node.

[0027] Here, the execution subject of the above steps may be a terminal or the like, but is not limited to this.

[0028] It should be noted that the third node may be in the same entity as the second node, or may be in a separate, different entity.

[0029] In addition, one third node may correspond to multiple second nodes, that is, one third node may perform information interaction with multiple second nodes.

[0030] The third node may be an AI server, an AI storage device, or a node having database / server / memory functions.

[0031] In one exemplary embodiment, the step of transmitting the first fallback request information to the third node includes at least one of transmitting the first fallback request information directly to the third node and forwarding the first fallback request information to the third node via the second node by transmitting the first fallback request information to a second node.

[0032] In an exemplary embodiment, the step of receiving the first fallback confirmation information transmitted by the third node or the second node includes at least one of receiving the first fallback confirmation information transmitted directly by the third node, and receiving the first fallback confirmation information transmitted by the third node to the second node and forwarded from the second node.

[0033] In one exemplary embodiment, after sending the first fallback request information to the third node or the second node, the method further includes a step of receiving first fallback confirmation information sent by the third node or the second node, the first fallback confirmation information including at least one of instruction information on whether to agree with the first fallback request information, a second fallback start time, functional module information of the second fallback, and falling back to legacy mode.

[0034] In an embodiment of the present disclosure, preferably, when the first node receives the first fallback confirmation information, the third node or the second node indicates that it agrees with the fallback request of the first node. Furthermore, the first fallback confirmation information may further include at least one of a second fallback start time, functional module information of the second fallback, and falling back to a legacy mode.

[0035] Preferably, the first fallback confirmation information includes at least instruction information on whether to agree with the fallback request information. If the instruction information agrees with the fallback request information, the first fallback confirmation information may further include at least one of a second fallback start time, function module information of the second fallback, and falling back to a legacy mode.

[0036] If the instruction information does not agree with the fallback request information, the first node continues to use a current function module to communicate with the second node or the third node.

[0037] In an exemplary embodiment, after receiving first fallback confirmation information sent by the third node or the second node, the method further includes at least one of the following steps: if the first fallback confirmation information includes second fallback function module information, determining to download a corresponding function module using the second fallback function module information; if the first fallback confirmation information does not include second fallback function module information, determining to download the corresponding function module using the first fallback function module information; and falling back to legacy mode.

[0038] In an exemplary embodiment, the method further includes at least one of the steps of: if the first fallback confirmation information includes a second fallback start time, communicating with the second node using the functional module or adopting a legacy mode to communicate with the second node or a third node after the second fallback start time; and if the first fallback confirmation information does not include a second fallback start time, communicating with the second node using the functional module or adopting a legacy mode to communicate with the second node or a third node after the first fallback start time.

[0039] In an exemplary embodiment, the function module information includes at least one of a name of the function module, an index of the function module, version information of the function module, and a function realized by the function module.

[0040] In an exemplary embodiment, when the fallback cause is indicated by the manner of index information, the fallback cause indicates a preset fallback cause, and description information of the fallback cause is stored in at least one of a first node, a second node, and a third node.

[0041] In an exemplary embodiment, the time of sending the first fallback request information to the third node is taken as a time reference point, and the first fallback start time is characterized by a time delay.

[0042] In one exemplary embodiment, the time of receiving the first fallback confirmation information sent by the third node is taken as a time reference point, and the second fallback start time is characterized by a time delay.

[0043] An embodiment of the present disclosure further provides an information transmission method performed in a second node or a third node. FIG. 3 is a flowchart of another information transmission method according to an embodiment of the present disclosure. As shown in FIG. 3, the information transmission method includes: Step S302 includes sending first fallback instruction information to a first node, the first fallback instruction information including at least one of functional module information of a third fallback, falling back to legacy mode, and a third fallback start time.

[0044] Through the above steps, the second node or the third node can send the first fallback indication information to the first node, solving the problem in the related art of how to send the first fallback indication information to the first node (e.g., a terminal), and achieving the technical effect of sending the first fallback indication information to the first node.

[0045] In addition, the number of the third fallback function module information may be one or more, that is, the third fallback function module information may include one or more versions of function modules and / or one or more indexes of function modules, etc.

[0046] In one exemplary embodiment, the step of transmitting the first fallback indication information to the first node includes at least one of transmitting the first fallback indication information directly to the first node and forwarding the first fallback indication information to the first node via the second node by transmitting the first fallback indication information to a second node.

[0047] In one exemplary embodiment, the step of receiving the second fallback confirmation information transmitted by the first node includes at least one of receiving the second fallback confirmation information transmitted directly by the first node, and receiving the second fallback confirmation information transmitted by the first node to the second node forwarded from a second node.

[0048] In an exemplary embodiment, after receiving second fallback confirmation information sent by the first node, the method further includes at least one of the following steps: if the second fallback confirmation information includes fourth fallback function module information, determining to download a corresponding function module using fourth fallback function module information; if the second fallback confirmation information does not include fourth fallback function module information, determining to download a corresponding function module using third fallback function module information; and falling back to legacy mode.

[0049] The condition for the second fallback confirmation information not to include the fourth fallback functional module information is that the third fallback functional module information includes only one functional module.

[0050] In an exemplary embodiment, the time of sending the first fallback indication information to the first node is taken as a time reference point, and the third fallback start time is characterized by a time delay.

[0051] In one exemplary embodiment, the time of receiving the second fallback confirmation information sent by the first node is taken as a time reference point, and the fourth fallback start time is characterized by a time delay.

[0052] In an exemplary embodiment, after sending the first fallback instruction information to the first node, the method further includes a step of receiving second fallback confirmation information sent by the first node, the second fallback confirmation information including at least one of a fourth fallback start time, functional module information of a fourth fallback, and instruction information to fall back to legacy mode, where the functional module information of the fourth fallback is obtained from the functional module information of the third fallback.

[0053] In an exemplary embodiment, the method further includes: the third fallback function module information includes at least one function module information, where the at least one function module information includes at least one of a name of the function module, an index of the function module, version information of the function module, and a function realized by the function module.

[0054] The function module information of the third fallback includes four function module information, where the index information of the four function modules is 0, 1, 2, and 3, respectively. The name, version information, and realized functions of each function module are shown in Table 1 below.

[0055] [Table 1]

[0056] In this embodiment, the functions realized by the functional modules corresponding to these four functional modules are all modulation and coding, but the versions corresponding to these four functional modules and the specific number of antennas applied are different. The first node can select an applicable functional module therefrom according to its own antenna configuration, and transmit the corresponding index and / or name and / or version information and / or realized function to the second node or the third node.

[0057] In an exemplary embodiment, after receiving second fallback confirmation information sent by the first node, the method further includes at least one of the following steps: if the second fallback confirmation information includes fourth fallback function module information, determining to download a corresponding function module using fourth fallback function module information; if the second fallback confirmation information does not include fourth fallback function module information, determining to download a corresponding function module using third fallback function module information; and falling back to legacy mode.

[0058] In one exemplary embodiment, the method further includes at least one of the steps of: if the second fallback confirmation information includes a fourth fallback start time, communicating with the second node using the functional module or adopting a legacy mode to communicate with the second node after the fourth fallback start time; and if the second fallback confirmation information does not include a fourth fallback start time, communicating with the second node using the functional module or adopting a legacy mode to communicate with the second node after the third fallback start time.

[0059] In one exemplary embodiment, the method further includes a step of transmitting functional module information required by the first node in the second fallback confirmation information or in first functional module request information following the second fallback confirmation information.

[0060] In an exemplary embodiment, the method further includes a step of a third node or a second node sending a piece of response information to the functional module information required by the first node, the response information including at least one of the functional module information required by the first node and a fallback start time of the functional module information required by the first node.

[0061] In an exemplary embodiment, the method further includes a step of transmitting first fallback indication information to the first node, and a step of transmitting the first fallback indication information to the first node via control information in a control channel, specifically, transmitting the first fallback indication information to the first node via a physical downlink control channel PDCCH.

[0062] In an exemplary embodiment, the method further includes at least one of the steps of indicating whether current control information is control information that triggers the first fallback indication information based on a format of the control information, and transmitting the first fallback indication information in the control channel by including it in the control information.

[0063] Specifically, the downlink control information DCI format indicates whether the current PDCCH is the PDCCH that triggers the first fallback indication information.

[0064] In an exemplary embodiment, before indicating whether the current PDCCH is a PDCCH that triggers the first fallback indication information by the downlink control information DCI format, the method further includes a step of the second node transmitting indication information to indicate whether the corresponding DCI is a normal DCI or a fallback DCI for indicating a fallback.

[0065] The information transmission method of the above embodiment will now be further described with reference to the following embodiment.

[0066] Example 1 In this embodiment, the information transmission method is described with reference to FIG. 4. FIG. 4 is a schematic flowchart (1) of a preferred information transmission method in the embodiment of the present disclosure. As shown in FIG. 4, the specific steps include:

[0067] Step 1: The UE (corresponding to the first node) sends Fallback request information, and can choose to send it directly to the AI ​​Server (corresponding to the third node) or forward it via the TRP (corresponding to the second node), where the Fallback request information includes at least one of the following: Fallback cause, Fallback functional module information, and Fallback start time.

[0068] In addition, when the above-mentioned fallback cause is expressed in the form of index information, it represents a specific fallback cause, and specific cause description information is pre-stored in the UE (corresponding to the above-mentioned first node) / TRP (corresponding to the above-mentioned second node) / AI Server (corresponding to the above-mentioned third node).

[0069] The Fallback function module information includes at least one of the name of the function module, the index of the function module, and version information of the function module.

[0070] The fallback start time may be expressed as a time delay (corresponding to the above-mentioned time delay), and the occurrence time of step 1 is set as a reference time point (corresponding to the above-mentioned time reference point).

[0071] Step 2: The AI ​​Server (corresponding to the third node above) sends Fallback confirmation information, which can choose to send it directly to the UE (corresponding to the first node above) or forward it via the TRP (corresponding to the second node above), where the Fallback confirmation information specifically includes at least one of the following: Fallback start time, Fallback functional module version information, and Fallback to legacy mode.

[0072] The fallback start time in step 2 may be expressed as a time delay (corresponding to the above-mentioned time delay), and the occurrence time of step 2 is set as a reference time point (corresponding to the above-mentioned time reference point).

[0073] The version information of the Fallback functional module in step 2 may be different from the version applied for by the UE (corresponding to the above-mentioned first node).

[0074] Note that falling back to the legacy mode in step 2 includes predefined operation modes or operation modes that do not support the functional module.

[0075] Step 3a: After the UE (corresponding to the first node) receives the Fallback confirmation information, it downloads the corresponding version of the functional module, and after the validity time of the functional module arrives, the UE (corresponding to the first node) communicates with the TRP (corresponding to the second node) using the functional module.

[0076] Step 3b: After the UE (corresponding to the first node) receives the Fallback confirmation information, it falls back to the legacy mode and communicates with the TRP (corresponding to the second node).

[0077] It should be noted that only one of the above steps 3a and 3b is executed, and after one of the steps is executed, the other step is not executed in the current operation.

[0078] In addition, the TRP (corresponding to the second node above) and the AI ​​Server (corresponding to the third node above) may exist in the same entity.

[0079] Example 2 In this embodiment, the information transmission method is described with reference to FIG. 5, which is a schematic flowchart (2) of the preferred information transmission method of the present disclosure. As shown in FIG. 5, the specific steps include:

[0080] Step 1: The AI ​​Server (corresponding to the third node above) sends Fallback instruction information, and can choose to send it directly to the UE (corresponding to the first node above) or forward it via the TRP (corresponding to the second node above), where the Fallback instruction information includes at least one of Fallback functional module information, Fallback to legacy mode, and Fallback start time, and further, the AI ​​Server (corresponding to the third node above) can provide multiple versions of functional modules.

[0081] The Fallback function module information includes at least one of the name of the function module, the index of the function module, and version information of the function module.

[0082] The legacy mode includes a predefined operation mode or an operation mode that does not support a functional module.

[0083] The fallback start time may be expressed as a time delay (corresponding to the above-mentioned time delay), and the occurrence time of step 1 is set as a reference time point (corresponding to the above-mentioned time reference point).

[0084] In addition, the UE (corresponding to the first node) may be configured to select the version of the functional module that is most suitable for itself from the multiple versions of functional modules provided by the AI ​​Server (corresponding to the third node), and at the same time, the UE (corresponding to the first node) may choose to fall back to legacy mode.

[0085] Step 2: The UE (corresponding to the above-mentioned first node) sends Fallback confirmation information, and can choose to send it directly to the AIServer (corresponding to the above-mentioned third node) or forward it via the TRP (corresponding to the above-mentioned second node), where the Fallback confirmation information includes at least one of the following: Fallback start time, Fallback functional module version information used by the UE (corresponding to the above-mentioned first node), and instruction information to fall back to legacy mode.

[0086] The fallback start time in step 2 may be expressed as a time delay (corresponding to the above-mentioned time delay), and the occurrence time of step 2 is set as a reference time point (corresponding to the above-mentioned time reference point).

[0087] Step 3a: The UE (corresponding to the first node) downloads a corresponding version of the functional module, and after the valid time of the functional module is reached, the UE (corresponding to the first node) uses the functional module to communicate with the TRP (corresponding to the second node).

[0088] Step 3b: After the valid time has elapsed, the UE (corresponding to the first node above) falls back to the legacy mode and communicates with the TRP (corresponding to the second node above).

[0089] It should be noted that only one of the above steps 3a and 3b is executed, and after one of the steps is executed, the other step is not executed in the current operation.

[0090] In addition, the TRP (corresponding to the second node above) and the AI ​​Server (corresponding to the third node above) may exist in the same entity.

[0091] Example 3 In this embodiment, the information transmission method is described with reference to FIG. 6, which is a schematic flowchart (3) of a preferred information transmission method in the embodiment of the present disclosure. As shown in FIG. 6, the specific steps include:

[0092] Step 1: The AI ​​Server (corresponding to the third node above) sends Fallback instruction information, which can choose to send it directly to the UE (corresponding to the first node above) or forward it via the TRP (corresponding to the second node above), where the Fallback instruction information includes at least one of Fallback functional module information, Fallback to legacy mode, and Fallback start time.

[0093] The Fallback function module information includes at least one of the name of the function module, the index of the function module, and version information of the function module.

[0094] The legacy mode includes a predefined operation mode or an operation mode that does not support a functional module.

[0095] The fallback start time may be expressed as a time delay (corresponding to the above-mentioned time delay), and the occurrence time of step 1 is set as a reference time point (corresponding to the above-mentioned time reference point).

[0096] Step 2: The UE (corresponding to the above-mentioned first node) sends Fallback request information, and can choose to send it directly to the AI ​​Server (corresponding to the above-mentioned third node) or forward it via the TRP (corresponding to the above-mentioned second node), where the Fallback confirmation information includes at least one of the following: Fallback start time, Fallback function module version information used by the UE (corresponding to the above-mentioned first node).

[0097] Note that step 2 is premised on the assumption that the UE (corresponding to the first node above) has detected that the Fallback instruction information sent by the AI ​​Server (corresponding to the third node above) does not contain a functional module suitable for use by the UE (corresponding to the first node above) or a functional module of a version suitable for use by the UE (corresponding to the first node above).

[0098] The fallback start time in step 2 may be different from the fallback start time in step 1.

[0099] Step 3: The AI ​​Server (corresponding to the third node above) sends the functional module information requested by the UE (corresponding to the first node above), which may be sent directly to the UE (corresponding to the first node above) or forwarded by the TRP (corresponding to the second node above).

[0100] Step 4: After the UE (corresponding to the first node) downloads the corresponding functional module, it sends Fallback confirmation information, which may be directly sent to the AI ​​Server (corresponding to the third node) or forwarded by the TRP (corresponding to the second node), where the Fallback confirmation information includes a Fallback start time.

[0101] The fallback start time in step 4 may be expressed as a time delay (corresponding to the above-mentioned time delay), and the occurrence time of step 4 is set as a reference time point (corresponding to the above-mentioned time reference point).

[0102] Example 4 In this embodiment, the information transmission method is described with reference to FIG. 7, which is a schematic flowchart (4) of the preferred information transmission method of the present disclosure. As shown in FIG. 7, the specific steps include:

[0103] Step 0: TRP sends indication information to UE (corresponding to the above-mentioned first node), where the indication information is used to indicate whether the corresponding DCI is normal DCI or Fallback DCI, and is used to indicate whether TRP (corresponding to the above-mentioned second node) sends Fallback DCI, and further, TRP (corresponding to the above-mentioned second node) can send Fallback DCI and normal DCI simultaneously. If UE (corresponding to the above-mentioned first node) detects Fallback DCI, continue with step 1.

[0104] Note that step 0 above is the preferred functional step.

[0105] Step 1: The TRP (corresponding to the second node above) transmits a downlink control channel (PDCCH) to transmit a Fallback DCI, where the DCI format indicates whether the current DCI is a DCI that indicates a Fallback, or indicates in the DCI whether the current DCI is a Fallback DCI.

[0106] Here, the Fallback DCI carries at least one of the following: version information of the Fallback functional module, instruction information for Fallback to the legacy mode, and Fallback start time.

[0107] It should be noted that DCI refers to Downlink Control Information carried on the PDCCH.

[0108] Step 2: After the UE (corresponding to the above-mentioned first node) downloads a version of a function module that supports Fallback, it sends Fallback confirmation information to the TRP (corresponding to the above-mentioned second node).

[0109] Example 5 In this embodiment, the information transmission method is described with reference to FIG. 8, which is a schematic flowchart (5) of a preferred information transmission method according to an embodiment of the present disclosure. As shown in FIG. 8, the specific steps include:

[0110] Step 0: TRP sends indication information to UE (corresponding to the above-mentioned first node), where the indication information is used to indicate whether the corresponding DCI is normal DCI or Fallback DCI, and is used to indicate whether TRP (corresponding to the above-mentioned second node) sends Fallback DCI, and further, TRP (corresponding to the above-mentioned second node) can send Fallback DCI and normal DCI simultaneously. If UE (corresponding to the above-mentioned first node) detects Fallback DCI, continue with step 1.

[0111] Note that step 0 above is the preferred functional step.

[0112] Step 1: The TRP (corresponding to the second node above) transmits a downlink control channel (PDCCH) to transmit a Fallback DCI, where the DCI format indicates whether the current DCI is a DCI that indicates a Fallback, or indicates in the DCI whether the current DCI is a Fallback DCI.

[0113] Here, the Fallback DCI carries at least one of the following: version information of the Fallback functional module, instruction information for Fallback to the legacy mode, and Fallback start time.

[0114] It should be noted that DCI refers to Downlink Control Information carried on the PDCCH.

[0115] Step 2: After the UE (corresponding to the above-mentioned first node) receives the Fallback DCI, if it finds that the version information of the Fallback functional module does not match the capability of the UE (corresponding to the above-mentioned first node), the UE (corresponding to the above-mentioned first node) sends functional module request information to the TRP (corresponding to the above-mentioned second node). Here, the functional module request information sent by the TRP (corresponding to the above-mentioned second node) includes the functional module information of the version required by the UE (corresponding to the above-mentioned first node).

[0116] Step 3: The TRP (corresponding to the second node above) transmits functional module information of the version required by the UE (corresponding to the first node above) to the AI ​​Server (corresponding to the third node above).

[0117] Step 4: The AI ​​Server (corresponding to the third node) transmits functional module information of the version required by the UE (corresponding to the first node) to the TRP (corresponding to the second node).

[0118] Step 5: The TRP (corresponding to the above-mentioned second node) carries function module information required by the UE (corresponding to the above-mentioned first node) in the DCI.

[0119] Step 6: After the UE (corresponding to the above-mentioned first node) downloads the corresponding version of the function module, it sends Fallback confirmation information to the TRP (corresponding to the above-mentioned second node).

[0120] From the above description of the embodiments, it is clear to those skilled in the art that the methods according to the above-mentioned embodiments can be realized in a form in which a necessary general-purpose hardware platform is added to the software, and of course, it can also be realized by hardware, but the former is often a more preferable embodiment. Based on this understanding, the essential part of the technical solution of the present disclosure or the part that contributes to the prior art can be embodied in the form of a software product stored in a storage medium (e.g., ROM / RAM, magnetic disk, optical disk) that includes several instructions for causing a first node device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present disclosure.

[0121] This embodiment further provides an information transmission device, which is used to realize the above embodiments and embodiments, and the description of the device already described will be omitted. As used hereinafter, the term "module" may be a combination of software and / or hardware that realizes a certain function. The device described in the following embodiment is preferably implemented in software, but implementation in hardware or a combination of software and hardware is also possible and envisioned.

[0122] FIG. 9 is a structural block diagram of an information transmission device according to an embodiment of the present disclosure. As shown in FIG. 9, the device includes: A first transmitting module 902 configured to transmit first fallback request information to a third node or a second node, the first fallback request information including at least one of a fallback cause, functional module information of the first fallback, falling back to legacy mode, and a first fallback start time.

[0123] The above device transmits first fallback request information to a third node or a second node, where the first fallback request information includes at least one of a fallback cause, functional module information of the first fallback, falling back to legacy mode, and a first fallback start time, thereby solving the problem that the related art does not disclose a means for performing an interaction process of the first fallback request information between the first node (e.g., a terminal) and the second node or the third node, and achieving the technical effect of the first node transmitting the first fallback request information to the third node or the second node.

[0124] In an exemplary embodiment, the first transmitting module 902 is further configured to at least perform one of: transmitting the first fallback request information directly to the third node; and forwarding the first fallback request information to the third node via the second node by transmitting the first fallback request information to a second node.

[0125] In an exemplary embodiment, the first receiving module 904 is further configured to at least perform one of receiving the first fallback confirmation information directly sent by the third node and receiving the first fallback confirmation information sent by the third node to the second node forwarded from the second node.

[0126] In an exemplary embodiment, the first receiving module 904 is further configured to receive first fallback confirmation information sent by the third node or the second node, where the first fallback confirmation information includes at least one of instruction information on whether to agree to the first fallback request information, a second fallback start time, functional module information of the second fallback, and falling back to legacy mode.

[0127] In an exemplary embodiment, the first receiving module 904 is further configured to perform at least one of: determining to download a corresponding functional module using the second fallback functional module information when the first fallback confirmation information includes second fallback functional module information; determining to download a corresponding functional module using the first fallback functional module information when the first fallback confirmation information does not include second fallback functional module information; and falling back to a legacy mode.

[0128] In one exemplary embodiment, the first receiving module 904 is further configured to, if the first fallback confirmation information includes a second fallback start time, communicate with the second node using the functional module or communicate with the second node or a third node by adopting a legacy mode after the second fallback start time, and, if the first fallback confirmation information does not include a second fallback start time, communicate with the second node using the functional module or communicate with the second node by adopting a legacy mode after the first fallback start time.

[0129] In an exemplary embodiment, the function module information includes at least one of a name of the function module, an index of the function module, version information of the function module, and a function realized by the function module.

[0130] In an exemplary embodiment, the first receiving module 904 is further configured to indicate a pre-defined fallback cause by the fallback cause when the fallback cause is indicated by the manner of index information, and the description information of the fallback cause is stored in at least one of the first node, the second node, and the third node.

[0131] In an exemplary embodiment, the time of sending the first fallback request information to the third node is taken as a time reference point, and the first fallback start time is characterized by a time delay.

[0132] In one exemplary embodiment, the time of receiving the first fallback confirmation information sent by the third node is taken as a time reference point, and the second fallback start time is characterized by a time delay.

[0133] FIG. 10 is a structural block diagram of another information transmission device according to an embodiment of the present disclosure. As shown in FIG. 10, the device includes: A second transmitting module 1002 configured to transmit first fallback instruction information to the first node, the first fallback instruction information including at least one of functional module information of a third fallback, falling back to legacy mode, and a third fallback start time.

[0134] The above apparatus transmits first fallback instruction information to a first node, where the first fallback instruction information includes at least one of functional module information of a third fallback, falling back to legacy mode, and a third fallback start time, thereby solving the problem in the related art of how to transmit the first fallback instruction information to a first node (e.g., a terminal) and achieving the technical effect of transmitting the first fallback instruction information to a first node.

[0135] In an exemplary embodiment, the second transmitting module 1002 is further configured to perform one of: transmitting the first fallback indication information directly to the first node; and forwarding the first fallback indication information to the first node by the second node by transmitting the first fallback indication information to the second node.

[0136] In an exemplary embodiment, the second receiving module 1004 is further configured to perform at least one of receiving second fallback confirmation information directly sent by the first node and receiving second fallback confirmation information forwarded from the second node and sent by the first node to the second node.

[0137] In an exemplary embodiment, the second receiving module 1004 is further configured to determine, if the second fallback confirmation information includes a fourth fallback functional module information, to download a corresponding functional module using the fourth fallback functional module information; if the second fallback confirmation information does not include a fourth fallback functional module information, to determine, if the second fallback confirmation information includes a third fallback functional module information, to download a corresponding functional module, and to fall back to a legacy mode.

[0138] In an exemplary embodiment, the time of sending the first fallback indication information to the first node is taken as a time reference point, and the third fallback start time is characterized by a time delay.

[0139] In one exemplary embodiment, the time of receiving the second fallback confirmation information sent by the first node is taken as a time reference point, and the fourth fallback start time is characterized by a time delay.

[0140] In an exemplary embodiment, the second receiving module 1004 is further configured to receive second fallback confirmation information sent by the first node, where the second fallback confirmation information includes at least one of a fourth fallback start time, a fourth fallback functional module information, and an instruction information to fall back to legacy mode, where the fourth fallback functional module information is obtained from the third fallback functional module information.

[0141] In an exemplary embodiment, the third fallback function module information includes at least one function module information, where the at least one function module information includes at least one of a name of the function module, an index of the function module, version information of the function module, and a function realized by the function module.

[0142] In an exemplary embodiment, the second receiving module 1004 is further configured to perform at least one of: determining to download a corresponding functional module using fourth fallback functional module information when the second fallback confirmation information includes fourth fallback functional module information; determining to download a corresponding functional module using third fallback functional module information when the second fallback confirmation information does not include fourth fallback functional module information; and falling back to legacy mode.

[0143] In an exemplary embodiment, the second receiving module 1004 is further configured to perform at least one of: if the second fallback confirmation information includes a fourth fallback start time, communicating with the second node using the functional module or communicating with the second node by adopting a legacy mode after the fourth fallback start time; and if the second fallback confirmation information does not include a fourth fallback start time, communicating with the second node using the functional module or communicating with the second node by adopting a legacy mode after the third fallback start time.

[0144] In an exemplary embodiment, the first node transmits required functional module information in the second fallback confirmation information or in a first functional module request information following the second fallback confirmation information.

[0145] In an exemplary embodiment, the second sending module 1002 is further configured to send response information to the functional module information required by the first node, where the response information includes at least one of the functional module information required by the first node and a fallback start time of the functional module information required by the first node.

[0146] In an exemplary embodiment, the second transmitting module 1002 is further configured to transmit the first fallback indication information to the first node via control information in a control channel, specifically, transmit the first fallback indication information to the first node via a physical downlink control channel (PDCCH).

[0147] In an exemplary embodiment, the second transmitting module 1002 is further configured to perform at least one of indicating whether the current control information is control information that triggers the first fallback indication information through a format of the control information, and transmitting the first fallback indication information included in the control information in the control channel.

[0148] Specifically, downlink control information DClformat indicates whether the current PDCCH is the PDCCH that triggers the first fallback indication information.

[0149] In an exemplary embodiment, the second sending module 1002 is further configured to send indication information before indicating whether the current PDCCH is a PDCCH that triggers the first fallback indication information through the downlink control information DClformat, where the indication information is used to indicate whether the corresponding DCI is a normal DCI or a fallback DCI for instructing a fallback.

[0150] Each of the above modules may be realized by software or hardware, and in the latter case, each of the above modules may be realized either by all being located on the same processor, or by each of the above modules being located on different processors in any combination, but is not limited to this.

[0151] An embodiment of the present disclosure further provides a computer readable storage medium having a computer program stored thereon, where the computer program is configured to perform the steps of any one of the method embodiments described above when executed.

[0152] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a U disk, a read-only memory (abbreviated as ROM), a random access memory (abbreviated as RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0153] In an exemplary embodiment, the storage medium comprises: Step S1 may include transmitting first fallback request information to a third node or a second node, and the first fallback request information may be configured to be used to execute step S1 including at least one of a fallback cause, functional module information of the first fallback, falling back to legacy mode, and a first fallback start time.

[0154] In another exemplary embodiment, the storage medium comprises: Step S1 of sending first fallback instruction information to a first node, the first fallback instruction information may be configured to be used to execute step S1 including at least one of functional module information of a third fallback, falling back to legacy mode, and a third fallback start time.

[0155] For specific examples in this embodiment, reference can be made to the examples described in the above-mentioned embodiments and exemplary embodiments, and the description thereof will be omitted here in this embodiment.

[0156] An embodiment of the present disclosure further provides an electronic device, comprising a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to execute the computer program to perform steps of any one of the method embodiments described above.

[0157] In an exemplary embodiment, the electronic device may further include a transmission device coupled to the processor, and an input / output device coupled to the processor.

[0158] In one exemplary embodiment, the processor: The computer program may be configured to execute step S1 of sending first fallback request information to a third node or a second node, the first fallback request information including at least one of a fallback cause, functional module information of the first fallback, falling back to legacy mode, and a first fallback start time.

[0159] In another exemplary embodiment, the processor comprises: The computer program may be configured to execute step S1 of sending first fallback instruction information to a first node, the first fallback instruction information including at least one of functional module information of a third fallback, falling back to legacy mode, and a third fallback start time.

[0160] For specific examples in this embodiment, reference can be made to the examples described in the above-mentioned embodiments and exemplary embodiments, and the description thereof will be omitted here in this embodiment.

[0161] Clearly, those skilled in the art will understand that each module or step of the present disclosure above may be implemented by a general-purpose computing device, they may be centralized in a single computing device or distributed across a network of multiple computing devices, they may be implemented in computing device executable program code such that they may be stored in a storage device and executed on a computing device, and in some cases, the steps shown or described may be performed in a different order than that shown herein, or may be fabricated into respective integrated circuit modules, or multiple of the modules or steps may be fabricated into a single integrated circuit module.

[0162] In this manner, the present disclosure is not limited to any particular combination of hardware and software.

[0163] The above is merely an embodiment of the present disclosure, and does not limit the present disclosure. Those skilled in the art can make various modifications and variations to the present disclosure. Any modifications, equivalent replacements, improvements, etc. made within the principle of the present disclosure should be included within the scope of protection of the present disclosure.

Claims

1. 1. A method for transmitting information, comprising: transmitting first fallback request information to a third node or a second node, the first fallback request information including at least one of a fallback cause, functional module information of the first fallback, falling back to a legacy mode, and a first fallback start time; Methods of information transmission.

2. After sending the first fallback request information to the third node or the second node, the method further comprises: receiving first fallback confirmation information transmitted by the third node or the second node, the first fallback confirmation information including at least one of instruction information on whether to agree to the first fallback request information, a second fallback start time, functional module information of the second fallback, and falling back to a legacy mode; The method of claim 1.

3. After receiving the first fallback confirmation information sent by the third node or the second node, the method further comprises: determining to use a function module corresponding to the second fallback function module information when the first fallback confirmation information includes a second fallback function module information; determining to use a function module corresponding to the function module information of the first fallback when the first fallback confirmation information does not include function module information of the second fallback; and falling back to a legacy mode. The method of claim 2.

4. The method further comprises: If the first fallback confirmation information includes a second fallback start time, after the second fallback start time, communicating with the second node using the functional module, or adopting a legacy mode to communicate with the second node or a third node; and if the first fallback confirmation information does not include a second fallback start time, after the first fallback start time, communicating with the second node using the functional module, or adopting a legacy mode to communicate with the second node or a third node. The method of claim 2.

5. The functional module information includes: The name of the functional module; an index of said functional module; version information of the functional module; including at least one of the functions implemented by the functional modules; The method according to any one of claims 2 to 4.

6. 1. A method for transmitting information, comprising: Sending first fallback instruction information to the first node, the first fallback instruction information including at least one of functional module information of a third fallback, falling back to a legacy mode, and a third fallback start time; Methods of information transmission.

7. After sending the first fallback indication information to the first node, the method further comprises: receiving second fallback confirmation information transmitted by the first node, the second fallback confirmation information including at least one of a fourth fallback start time, functional module information of a fourth fallback, and instruction information to fall back to a legacy mode; The method according to claim 6.

8. The fourth fallback function module information is obtained from the third fallback function module information. The method of claim 7.

9. The method further comprises: The third fallback function module information includes at least one function module information, where the at least one function module information is: The name of the functional module; an index of said functional module; version information of the functional module; including at least one of the functions implemented by the functional modules; The method according to claim 6.

10. After receiving the second fallback confirmation information sent by the first node, the method further comprises: determining to use a function module corresponding to the fourth fallback function module information when the second fallback confirmation information includes a fourth fallback function module information; determining to use a function module corresponding to the function module information of a third fallback when the second fallback confirmation information does not include the function module information of a fourth fallback; and falling back to a legacy mode. The method of claim 7.

11. The method further comprises: If the second fallback confirmation information includes a fourth fallback start time, after the fourth fallback start time, the method includes at least one of the steps of: communicating with the second node using the functional module or adopting a legacy mode to communicate with the second node; and if the second fallback confirmation information does not include a fourth fallback start time, communicating with the second node using the functional module or adopting a legacy mode to communicate with the second node after the third fallback start time. The method of claim 10.

12. The method further comprises: transmitting function module information required by the first node in the second fallback confirmation information or in a first function module request information subsequent to the second fallback confirmation information; The method of claim 7.

13. The third node or the second node transmits response information to the functional module information required by the first node, where the response information comprises: Functional module information required for the first node; including at least one of a fallback start time of the functional module information required for the first node; The method of claim 12.

14. The step of transmitting the first fallback indication information to the first node includes: transmitting the first fallback indication information to a first node via control information in a control channel. The method according to claim 6.

15. The method further comprises: indicating whether the current control information is the control information that triggers the first fallback indication information according to a format of the control information; transmitting the first fallback indication information in control information in the control channel. The method of claim 14.

16. The method further comprises the step of: transmitting, by the second node, indication information for indicating whether the control information includes control information of the first fallback indication information. The method of claim 15.

17. An information transmission device, a first sending module configured to send first fallback request information to a third node or a second node, the first fallback request information including at least one of a fallback cause, functional module information of the first fallback, falling back to a legacy mode, and a first fallback start time; Information transmission device.

18. An information transmission device, a second sending module configured to send first fallback indication information to the first node, the first fallback indication information including at least one of functional module information of a third fallback, falling back to a legacy mode, and a third fallback start time; Information transmission device.

19. A computer readable storage medium having stored thereon a computer program, the computer program being configured, when executed, to perform the method according to any one of claims 1 to 5 or any one of claims 6 to 16. A computer-readable storage medium.

20. An electronic device comprising a memory and a processor, wherein a computer program is stored in the memory, and wherein the processor is configured to execute the computer program to perform the method according to any one of claims 1 to 5 or the method according to any one of claims 6 to 16. electronic equipment.

Images