Information transmission method and communication apparatus

Abstract

Provided in the present application are an information transmission method and a communication apparatus. In the method, on the basis of configuration information of a downlink non-anchor carrier, a network device can enable a terminal to determine a frequency point determination mode for the downlink anchor carrier, such that a frequency point of the downlink non-anchor carrier can be obtained on the basis of a correct frequency point determination mode, thereby implementing communication on the downlink non-anchor carrier, and thus ensuring communication reliability.

Description

Information transmission methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202510404336.2, filed on March 28, 2025, entitled "Information Transmission Method and Communication Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more specifically, to an information transmission method and a communication device. Background Technology

[0003] The Internet of Things (IoT) aims to create an intelligent network system that enables various physical devices and objects to communicate and collaborate with each other, achieving ubiquitous connectivity. Non-terrestrial networks (NTNs), based on non-terrestrial infrastructure such as satellites, drones, and high-altitude platforms, offer advantages over terrestrial networks, including wider coverage, higher reliability, and greater throughput. NTNs allow sensors and devices located in remote areas (such as at sea, in forests, and in mountainous regions) to overcome geographical limitations and connect to the network; IoT devices have become the primary target audience for NTN services.

[0004] However, when IoT devices are applied to NTN with multiple carriers, how to effectively determine the serving carrier is an urgent problem to be solved. Summary of the Invention

[0005] This application provides an information transmission method and a communication device that can ensure communication reliability.

[0006] In a first aspect, an information transmission method is provided, which can be executed by a first communication device, wherein the first communication device can be a terminal or a module (such as a logic circuit, a chip, or a chip system) that can be configured in (or used in) the terminal.

[0007] The method includes: a first communication device receiving configuration information for configuring a first carrier, the first carrier being a downlink non-anchor carrier; and the first communication device determining a frequency point determination method for the first carrier based on the configuration information.

[0008] According to the solution provided in the embodiments of this application, the first communication device can determine the frequency point determination method of the downlink anchor carrier through the configuration information of the downlink non-anchor carrier, so that the first communication device can obtain the frequency point of the downlink non-anchor carrier based on the correct frequency point determination method, realize communication on the downlink non-anchor carrier, and ensure communication reliability.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, the configuration information includes first information, which is used to indicate the deployment method of the first carrier. If the deployment method of the first carrier is an independent deployment method, the frequency point determination method of the first carrier is the frequency point determination method corresponding to the independent deployment method; or, if the deployment method of the first carrier is a non-independent deployment method, the frequency point determination method of the first carrier is the frequency point determination method corresponding to the non-independent deployment method.

[0010] According to the above scheme, the first communication device can determine the frequency point of the first carrier by using the first information in the configuration information to indicate the deployment mode of the downlink non-anchor carrier and determine the frequency point determination method corresponding to the deployment mode of the first carrier.

[0011] In one alternative implementation, the first information is used to indicate whether the first carrier is deployed in an independent deployment mode or a non-independent deployment mode.

[0012] In another optional implementation, the first information is used to indicate whether the deployment mode of the first carrier is an independent deployment mode, an in-band deployment mode, a guard band deployment mode, an in-band deployment mode using a first radio access technology (RAT) system, or an in-band deployment mode using a second RAT system.

[0013] In this embodiment, when the first carrier is deployed in an in-band mode, the first information can specifically indicate which RAT system's frequency band the first carrier is deployed in, enabling the first communication device to achieve rate matching, resource reservation, etc., based on the characteristics of the RAT system, thereby avoiding interference caused by different signals being sent to the same resource and further improving communication reliability.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first communication device determining the frequency point determination method of the first carrier based on whether the configuration information includes second information. Wherein, if the configuration information includes second information, the frequency point determination method of the first carrier is the first frequency point determination method. Alternatively, if the configuration information does not include second information, the frequency point determination method of the first carrier is the second frequency point determination method.

[0015] According to the above scheme, by predefining a default deployment method / frequency confirmation method, or by predefining whether the deployment method / frequency confirmation method of the downlink non-anchor carrier and the anchor carrier is the same or different, when the downlink non-anchor carrier adopts the default method, no signaling indication is required, which can reduce signaling overhead. When the downlink anchor carrier adopts a non-default method, the terminal can be notified through the second information in the configuration information so that the terminal can adopt the correct frequency point determination method to determine the frequency point of the first carrier and realize communication on the downlink non-anchor carrier, thus ensuring communication reliability.

[0016] In optional implementation a, the second information is used to indicate that the frequency point determination method of the first carrier is the first frequency point determination method.

[0017] In optional implementation b, the second information is used to indicate that the deployment mode of the first carrier is an independent deployment mode, and the first frequency point determination mode is the frequency point determination mode corresponding to the independent deployment mode.

[0018] In optional implementation c, the second information is used to indicate that the deployment mode of the first carrier is a non-independent deployment mode, and the first frequency point determination method is the frequency point determination method corresponding to the non-independent deployment mode.

[0019] In optional implementation d, the second information is used to indicate that the deployment method of the first carrier is the same as the deployment method of the anchor carrier, or the second information is used to indicate that the frequency point determination method of the first carrier is the same as the frequency point determination method of the anchor carrier, and the frequency point determination method of the anchor carrier is the first frequency point determination method.

[0020] In optional implementation e, the second information is used to indicate that the deployment method of the first carrier is different from the deployment method of the anchor carrier, or the second information is used to indicate that the frequency point determination method of the first carrier is different from the frequency point determination method of the anchor carrier, and the frequency point determination method of the anchor carrier is the second frequency point determination method.

[0021] In conjunction with the first aspect, in some implementations of the first aspect, the configuration information is specifically used to configure the switching from the second carrier to the first carrier, the second information is used to indicate that the deployment method of the first carrier is different from the deployment method of the second carrier, or the second information is used to indicate that the frequency point determination method of the first carrier is different from the frequency point determination method of the second carrier, and the frequency point determination method of the second carrier is the second frequency point determination method.

[0022] According to the above scheme, the frequency point determination method of the predefined carrier to be switched to (i.e., the first carrier) can be the same as the frequency point determination method of the current carrier (the second carrier) by default. If the configuration information does not include the second information, it can be assumed that the frequency point determination method of the first carrier is the same as that of the second carrier. If the first carrier and the second carrier do not have the same default frequency point determination method, the configuration information includes the second information to notify the terminal that the frequency point determination methods of the first carrier and the second carrier are different. When the downlink non-anchor carrier uses the default method, no signaling indication is required, which can reduce signaling overhead. When the downlink anchor carrier uses a non-default method, the terminal can be notified through the second information in the configuration information so that the terminal can use the correct frequency point determination method to determine the frequency point of the first carrier and realize communication on the downlink non-anchor carrier, thus ensuring communication reliability.

[0023] In conjunction with the first aspect, in some implementations of the first aspect, the frequency point determination method of the first carrier is the frequency point determination method corresponding to the independent deployment method, and the frequency point F of the first carrier is... DL Satisfy: F DL =F DL_low +0.1(N DL -N Offs-DL )+0.0025*(2M DL );

[0024] or,

[0025] The frequency point determination method for the first carrier is the frequency point determination method corresponding to the non-independent deployment method, and the frequency point F of the first carrier is... DL Satisfy: F DL =F DL_low +0.1(N DL -N Offs-DL )+0.0025*(2M DL +1);

[0026] Among them, F DL_low N is the lowest frequency in the downlink operating band. DL It is the downlink absolute radio frequency channel number ARFCN, N Offs-DL It is the downlink ARFCN offset, M DL It is the offset of the narrowband channel number relative to the downlink ARFCN channel number.

[0027] Secondly, an information transmission method is provided, which can be executed by a second communication device, wherein the second communication device can be a network device or a module (such as a logic circuit, chip, or chip system) configurable to (or usable in) a network device.

[0028] The method includes: a second communication device determining configuration information based on a frequency point determination method for a first carrier, the configuration information being used to configure the first carrier, the first carrier being a downlink non-anchor carrier; and the second communication device transmitting the configuration information.

[0029] According to the above scheme, the second communication device can determine the configuration information of the downlink non-anchor carrier based on the frequency point determination method of the first carrier, so that the first communication device can determine the frequency point determination method of the downlink non-anchor carrier based on the configuration information, thereby obtaining the frequency point of the downlink non-anchor carrier based on the correct frequency point determination method, realizing communication between the second communication device and the first communication device on the downlink non-anchor carrier, and ensuring communication reliability.

[0030] In conjunction with the second aspect, in some implementations of the second aspect, the configuration information includes first information, which indicates the deployment method of the first carrier. If the deployment method of the first carrier is an independent deployment method, the frequency point determination method of the first carrier is the frequency point determination method corresponding to the independent deployment method. Alternatively, if the deployment method of the first carrier is a non-independent deployment method, the frequency point determination method of the first carrier is the frequency point determination method corresponding to the non-independent deployment method.

[0031] In one alternative implementation, the first information is used to indicate whether the first carrier is deployed in an independent deployment mode or a non-independent deployment mode.

[0032] In another optional implementation, the first information is used to indicate whether the deployment mode of the first carrier is an independent deployment mode, an in-band deployment mode, a guard band deployment mode, an in-band deployment mode using a first radio access technology (RAT) system, or an in-band deployment mode using a second RAT system.

[0033] In conjunction with the second aspect, in some implementations of the second aspect, if the frequency point determination method of the first carrier is a first frequency point determination method, the configuration information includes the second information. Alternatively, if the frequency point determination method of the first carrier is a second frequency point determination method, the configuration information does not include the second information.

[0034] In optional implementation a, the second information is used to indicate that the frequency point determination method of the first carrier is the first frequency point determination method.

[0035] In optional implementation b, the second information is used to indicate that the deployment mode of the first carrier is an independent deployment mode, and the first frequency point determination mode is the frequency point determination mode corresponding to the independent deployment mode.

[0036] In optional implementation c, the second information is used to indicate that the deployment mode of the first carrier is a non-independent deployment mode, and the first frequency point determination method is the frequency point determination method corresponding to the non-independent deployment mode.

[0037] In optional implementation d, the second information is used to indicate that the deployment method of the first carrier is the same as the deployment method of the anchor carrier, or the second information is used to indicate that the frequency point determination method of the first carrier is the same as the frequency point determination method of the anchor carrier, and the frequency point determination method of the anchor carrier is the first frequency point determination method.

[0038] In optional implementation e, the second information is used to indicate that the deployment method of the first carrier is different from the deployment method of the anchor carrier, or the second information is used to indicate that the frequency point determination method of the first carrier is different from the frequency point determination method of the anchor carrier, and the frequency point determination method of the anchor carrier is the second frequency point determination method.

[0039] In conjunction with the second aspect, in some implementations of the second aspect, the configuration information is specifically used to configure the switching from the second carrier to the first carrier. The second information is used to indicate that the deployment method of the first carrier is different from the deployment method of the second carrier, or that the frequency point determination method of the first carrier is different from the frequency point determination method of the second carrier, and the frequency point determination method of the second carrier is the second frequency point determination method.

[0040] In one optional implementation, the first carrier is deployed in an independent manner, and the frequency point F of the first carrier is... DL Satisfy: F DL =F DL_low +0.1(N DL -N Offs-DL )+0.0025*(2M DL );

[0041] In another optional implementation, the first carrier is deployed in a non-standalone manner, and the frequency F of the first carrier... DL Satisfy: F DL =F DL_low +0.1(N DL -N Offs-DL )+0.0025*(2M DL +1);

[0042] Among them, F DL_low N is the lowest frequency in the downlink operating band. DL It is the downlink absolute radio frequency channel number ARFCN, N Offs-DL It is the downlink ARFCN offset, M DL It is the offset of the narrowband channel number relative to the downlink ARFCN.

[0043] Thirdly, a communication device is provided. In one design, the device may include modules corresponding to the methods / operations / steps / actions described in the first aspect or any embodiment of the first aspect. These modules may be hardware circuits, software, or a combination of hardware circuits and software. In one design, the device includes: a transceiver unit for receiving configuration information, the configuration information being used to configure a first carrier, wherein the first carrier is a downlink non-anchor carrier; and a processing unit for determining the frequency point determination method of the first carrier based on the configuration information.

[0044] Fourthly, a communication device is provided. In one design, the device may include modules corresponding to the methods / operations / steps / actions described in the second aspect or any of the embodiments of the second aspect. These modules may be hardware circuits, software, or a combination of hardware circuits and software. In one design, the device includes: a processing unit configured to determine configuration information based on a frequency point determination method of the first carrier, the configuration information being used to configure the first carrier, wherein the first carrier is a downlink non-anchor carrier; and a transceiver unit configured to transmit the configuration information.

[0045] Fifthly, a communication device is provided, including a processor. The processor can implement the methods of the first to second aspects and any possible implementations thereof. Optionally, the communication device further includes a memory, and the processor is coupled to the memory and can be used to execute instructions in the memory to implement the methods of the first to second aspects and any possible implementations thereof. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface. In the embodiments of this application, the communication interface may be a transceiver, a pin, a circuit, a bus, a module, or other types of communication interface, and is not limited thereto.

[0046] In one implementation, the communication device is a communication equipment (such as a terminal device or access network equipment). When the communication device is a communication equipment, the communication interface can be a transceiver, or an input / output interface.

[0047] In another implementation, the communication device is a chip configured within a communication device. When the communication device is a chip configured within a communication device, the communication interface can be an input / output interface.

[0048] Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0049] A sixth aspect provides a processor, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the methods described in the first to second aspects and any possible implementation thereof.

[0050] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0051] In a seventh aspect, a computer program product is provided, comprising: a computer program (also referred to as code or instructions) that, when run, causes a computer to perform the methods described in the first to second aspects and any possible implementation thereof.

[0052] Eighthly, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when executed on a computer, causes the computer to perform the methods described in the first to second aspects and any possible implementation thereof.

[0053] Ninthly, a communication system is provided, including at least one first communication device and at least one second communication device as described above.

[0054] It should be understood that the beneficial effects of the features corresponding to the first aspect in the second to ninth aspects can be referred to the relevant description of the first aspect above, and will not be repeated here. Attached Figure Description

[0055] Figures 1 to 3 are schematic diagrams of communication system architecture applicable to embodiments of this application;

[0056] Figure 4 is a schematic flowchart of an information transmission method provided in an embodiment of this application;

[0057] Figure 5 is a schematic block diagram of an example of a communication device provided in an embodiment of this application;

[0058] Figure 6 is a schematic structural diagram of another example of the communication device provided in the embodiments of this application. Detailed Implementation

[0059] To facilitate understanding of the embodiments of this application, the following description is provided first:

[0060] In this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information for the purpose of instructing A, it can be understood that the instruction information carries A, directly instructs A, or indirectly instructs A.

[0061] In this application, " / " can indicate that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" can be used to describe three relationships between the related objects. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0062] In this application, "at least one" means one or more, and "more than one" means two or more, such as three, four, or more. Similar expressions (such as at least one, at least one, etc.) are used in the same way. "At least one of the following," "one or more of the following," or similar expressions refer to any combination of these items, which may include only a single item or a combination of multiple items. For example, at least one of a, b, or c can mean: a, or b, or c; a and b; or a and c; or b and c; or a, b, and c. Where a, b, and c can be single or multiple.

[0063] In this application, for the convenience of describing the technical solutions of the embodiments of this application, the terms "first" and "second" may be used to distinguish them. The terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0064] In this application, the words "exemplary," "example," or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary," "example," or "for example" should not be construed as being more preferred or advantageous than other embodiments or designs. The use of the words "exemplary," "example," or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0065] In this application, "sending information / data" only indicates the direction of information / data transmission, including direct transmission via the device's communication interface (such as an air interface, or simply air interface). "Sending" can also be understood as the "output" of a module interface. "Sending" can include indirect transmission by the processing unit through the communication interface, meaning that after the processing unit outputs information / data through the module interface, it is transmitted to the device's communication interface and then sent out. "Receiving information / data" only indicates the direction of information / data transmission, including direct reception via the communication interface. "Receiving" can also be understood as the "input" of a module interface. "Receiving information / data" can include indirect reception by the processing unit through the communication interface, meaning that after the communication interface receives information / data, it is transmitted to the processing unit's module interface and then input to the processing unit. "Sending information / data to… (such as a terminal)" can be understood as the destination of the information being the terminal. It can include sending information / data directly or indirectly to the terminal. "Receiving information / data from… (such as a terminal)" can be understood as the source of the information being the terminal, and can include receiving information / data directly or indirectly from the terminal. Information / data may undergo necessary processing, such as format changes, between the source and destination, but the destination can understand the valid information / data from the source. Similar statements in this application can be understood in a similar way, and will not be repeated here.

[0066] The tables in this application embodiment are merely examples. The values ​​of the information in each table are only examples and can be configured to other values; this application is not limited thereto. The tables do not limit the scope of protection of this application. For example, appropriate modifications and adjustments can be made based on the tables described above, such as splitting, merging, etc. Furthermore, the parameter names shown in the headings of each table can also use other names understandable to the communication device, and the values ​​or representations of the parameters can also be other values ​​or representations understandable to the communication device. Moreover, in the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

[0067] The technical solutions of this application embodiment can be applied to various communication systems, such as: fourth generation (4G) th The fifth-generation (4G) communication system, the fifth-generation (5G) communication system, the satellite communication system, and the solutions provided in this application can also be applied to future communication systems or other communication systems. This application does not limit the scope of these applications.

[0068] Figure 1 illustrates a possible, non-limiting system diagram. As shown in Figure 1, the communication system 10 includes a radio access network (RAN) 100, a core network (CN) 200, and a data network (DN) 300. RAN 100 includes at least one RAN node (110a and 110b in Figure 1, collectively referred to as 110) and at least one terminal (120a-120j in Figure 1, collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1). Terminal 120 is wirelessly connected to RAN node 110. Access network node (or RAN node) 110 is wirelessly or wired connected to core network 200. The core network equipment in core network 200 and access network node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

[0069] RAN 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as 4G, 5G mobile communication systems, or future evolution systems. RAN 100 can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. RAN 100 can also be a communication system that integrates two or more of the above systems.

[0070] Access network node 110, sometimes also referred to as access network equipment, RAN entity, or access node, constitutes part of the communication system and is used to help terminals achieve wireless access. Multiple access network nodes 110 in communication system 10 can be of the same type or different types. In some scenarios, the roles of access network node 110 and terminal 120 are relative. For example, network element 120i in Figure 1 can be a helicopter or drone, which can be configured as a mobile base station. For terminals 120j accessing RAN 100 through network element 120i, network element 120i is a base station; but for base station 110a, network element 120i is a terminal. Access network node 110 and terminal 120 are sometimes both referred to as communication devices. For example, network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.

[0071] In one possible scenario, the access network node can be a base station, such as an evolved NodeB (eNodeB), a next-generation NodeB (gNB), or a base station in a future mobile communication system. The access network node can be a macro base station (as shown in Figure 1, 110a), a micro base station or indoor station (as shown in Figure 1, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Alternatively, the access network node can be an access point (AP), a transmission reception point (TRP), etc. Optionally, the access network node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the access network node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The access network node in this application can also be a logical node, logical module, or software capable of implementing all or part of the access network node functions.

[0072] In another possible scenario, multiple access network nodes collaborate to assist the terminal in achieving wireless access, with each access network node performing a portion of the base station's functions. For example, access network nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0073] A terminal can also be called a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used for communication in various scenarios. These scenarios include, but are not limited to, at least one of the following: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communications (mMTC), device-to-device (D2D) communication, V2X, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearables, smart transportation, sensing terminals, terminals integrating communication and sensing, or smart cities, etc. Terminals can be mobile phones (as shown in Figure 1, 120a, 120j, and 120e), tablets, computers with wireless transceiver capabilities (as shown in Figure 1, 120g), customer-premises equipment (CPE), point-of-sale (POS) machines, wearable devices, vehicles (as shown in Figure 1, 120b), drones, helicopters, airplanes (as shown in Figure 1, 120i), ships, robots, robotic arms, sensors, detectors, or smart home devices (as shown in Figure 1, 120h), etc.

[0074] Figure 2 illustrates another possible, non-limiting system diagram. The system architecture shown in Figure 2 is one possible architecture for an NTN network. As shown in Figure 2, the terminal communicates with the terrestrial base station through the User-Universal Terrestrial Radio Access Network (Uu) interface. The satellite enables transparent payload transmission between the terminal and the terrestrial base station. The satellite and the NTN gateway can be considered as remote radio units (RRUs) of the terrestrial base station, achieving transparent signal forwarding. That is, the satellite only supports functions such as radio frequency filtering, frequency conversion, and amplification, while the signal waveform remains unchanged. The satellite forwarding is transparent to the terminal. The terrestrial base station and the core network (CN) can communicate through the next-generation (NG) interface, exchanging non-access stratum (NAS) signaling of the core network and the terminal's service data via the NG interface. The core network can also transmit service data with the data network (DN).

[0075] Figure 3 illustrates another possible, non-limiting system diagram. As shown in Figure 3, the satellite possesses some or all of the functions of an access network device and can be referred to as a satellite base station. It can provide wireless access services and schedule wireless resources for terminals accessing the network through the satellite base station. The satellite base station and the terminal communicate via the Uu interface. Specifically, the satellite base station and the CN can communicate via the NG interface, and the satellite base station and the core network can exchange NAS signaling and terminal service data via the NG interface. The satellite radio interface (SRI) is the feeder link between the NTN gateway and the satellite. In Figure 3, the SRI interface can be used as part of the NG interface to realize communication interaction between the satellite and the core network.

[0076] In current narrow-band (NB-IoT) designs, in-band, guard-band, and standalone deployments are supported. Specifically, NB-IoT can coexist with systems using various radio access technologies (RATs), such as Long Term Evolution (LTE) and 5G NR systems. Taking NB-IoT coexistence with NR systems as an example, in-band deployment means the NB-IoT carrier band is located within the NR band, sharing spectrum resources with the NR system. Guard-band deployment means the NB-IoT carrier band is deployed within a guard band at the edge of the NR band, not occupying effective NR band resources. Standalone deployment means the NB-IoT carrier band is deployed independently of both the NR and LTE bands, not occupying frequency domain resources of the NR / LTE network.

[0077] In an NB-IoT system, the carriers used in a cell can include anchor carriers and non-anchor carriers. Anchor carriers are the fundamental carriers in the NB-IoT system, used to carry cell signal synchronization, system information, and control information. Non-anchor carriers are mainly used for data transmission, improving spectral efficiency and system capacity. Anchor carriers and non-anchor carriers can be deployed in any of the following ways: in-band deployment, guard band deployment, or standalone deployment. In-band deployment and guard band deployment are also known as non-standalone deployment. Combinations of anchor carrier and non-anchor carrier deployments are shown in Table 1.

[0078] Table 1

[0079] For terrestrial communication networks, regardless of whether the carrier is anchored or non-anchored, and regardless of the deployment method, the method for determining the downlink carrier frequency is the same, i.e., the downlink carrier frequency F. DL Satisfy: F DL =F DL_low +0.1(N DL -N Offs-DL )+0.0025*(2M DL +1) (1)

[0080] Among them, F DL_low N is the lowest frequency in the downlink operating band. DL It is the downlink absolute radio frequency channel number (ARFCN), N Offs-DL It is the downlink ARFCN offset, M DLThis is the offset of the narrowband channel number relative to the downlink ARFCN channel number. The parameter F... DL_low N DL N Offs-DL The value of parameter N can be determined based on the predefined correspondence in the protocol. DL M DL It is indicated by the network device through signaling.

[0081] In terrestrial communication networks, network equipment configures / switches a terminal to a downlink carrier. The terminal does not need to know whether the carrier is an anchor carrier or a non-anchor carrier, or the deployment method of the carrier. The terminal only needs to determine the frequency of the downlink carrier based on the frequency point determination method of Equation (1) to realize communication with the network equipment on the downlink carrier.

[0082] Currently, research is being conducted on implementing IoT technology in NTN scenarios. Unlike terrestrial communication networks, in NTN scenarios, the frequency point determination method for IoT downlink carriers in standalone deployment and non-standalone deployment methods needs to be designed separately.

[0083] For example, the frequency point F of the downlink carrier in the stand-alone deployment mode DL Satisfy: F DL =F DL_low +0.1(N DL -N Offs-DL )+0.0025*(2M DL (2)

[0084] The downlink carrier frequency F in non-standalone deployment modes (i.e., in-band deployment and guard band deployment) DL Satisfy: F DL =F DL_low +0.1(N DL -N Offs-DL )+0.0025*(2M DL +1) (3)

[0085] For details on the parameters in the two equations above, please refer to the previous introduction of the parameters in equation (1), which will not be repeated here.

[0086] It should be understood that the frequency point determination methods involved in the embodiments of this application are illustrated above in a relational manner. For example, Equation (2) represents the frequency point determination method corresponding to the independent deployment method, and Equation (3) represents the frequency point determination method corresponding to the non-independent deployment method. However, the embodiments of this application do not limit the specific form of the frequency point determination method. For example, the frequency point determination method can be a correspondence table of each parameter, an index table, etc., that satisfies the above relational form. The embodiments of this application use Equations (2) and (3) as examples to introduce the solutions provided by the embodiments of this application.

[0087] The terminal can determine the deployment method of the anchor carrier based on existing signaling. Therefore, the terminal can obtain the frequency point of the anchor carrier by adopting the frequency point determination method corresponding to the deployment method of the anchor carrier. However, for some non-anchor carriers, the terminal cannot determine which frequency point determination method to use to determine the frequency point of the non-anchor carrier, and a corresponding mechanism needs to be designed. This application proposes that the network device can use the configuration information of the downlink non-anchor carrier to enable the terminal to determine the frequency point determination method of the downlink anchor carrier, thereby obtaining the frequency point of the downlink non-anchor carrier based on the correct frequency point determination method, realizing communication on the downlink non-anchor carrier, and ensuring communication reliability.

[0088] The technical solutions provided in the embodiments of this application will be described below with reference to the accompanying drawings. It should be understood that the information transmission method provided in this application is shown from the perspective of interaction between a terminal and a network device in the embodiments of this application, but this application does not limit the executing entity of the method. The terminal can be replaced by a module (such as a chip, chip system, processor, logic circuit, or software) configured in (or used for) the terminal, and the network device can be replaced by a module (such as a chip, chip system, processor, logic circuit, or software) configured in (or used for) the network device. When the executing entity is a module in the terminal or a module in the network device, receiving / transmitting can be understood as input / output, that is, the module communicates with other modules or components in the device. Furthermore, the operation performed by a single executing entity can also be divided into operations performed by multiple executing entities, which can be logically and / or physically separated. For example, the operation performed by the network device can be divided into operations performed by at least one of CU, DU, RU, etc.

[0089] Figure 4 is a schematic flowchart of an information transmission method provided in an embodiment of this application. The method includes, but is not limited to, the following steps:

[0090] S401, the network device sends configuration information to the terminal. This configuration information is used to configure the first carrier, which is a downlink non-anchor carrier.

[0091] Accordingly, the terminal receives configuration information from the network device. Based on this configuration information, the terminal can determine the frequency point determination method for the first carrier.

[0092] S402, the terminal determines the frequency point determination method of the first carrier based on the configuration information.

[0093] The network device can determine the configuration information of the first carrier based on the frequency point determination method of the first carrier and send it to the terminal. After receiving the configuration information, the terminal can not only determine whether to receive downlink signals on the first carrier, but also determine the frequency point determination method of the first carrier based on the configuration information.

[0094] Optionally, the configuration information may also include information related to the time-domain resources of the first carrier and / or information related to power control. For example, the information related to the time-domain resources may be used to configure the set of downlink subframes for downlink transmission on the first carrier. As another example, the information related to power control may be used to configure the power offset of the reference signal on the first carrier.

[0095] The specific implementation methods of this configuration information may include, but are not limited to, the following:

[0096] In implementation method 1, the configuration information includes first information, which is used to indicate the deployment method of the first carrier, or the first information is used to indicate the frequency point determination method of the first carrier.

[0097] Example 1-1: This first information is used to indicate the deployment method of the first carrier. Based on the deployment method of the first carrier, the terminal determines the frequency point determination method of the first carrier to be the frequency point determination method corresponding to that deployment method. If the deployment method of the first carrier is an independent deployment method, the frequency point determination method of the first carrier is the frequency point determination method corresponding to the independent deployment method. If the deployment method of the first carrier is a non-independent deployment method, the frequency point determination method of the first carrier is the frequency point determination method corresponding to the non-independent deployment method.

[0098] For example, the frequency point determination method corresponding to the independent deployment mode can be predefined by the protocol. For instance, the frequency point determination method corresponding to the independent deployment mode predefined by the protocol satisfies the relationship (2) mentioned above, and the frequency point determination method corresponding to the non-independent deployment mode satisfies the relationship (3) mentioned above. If the terminal determines that the deployment mode of the first carrier is an independent deployment mode based on the first information, the terminal can determine the frequency point of the first carrier according to the relationship (2). If the terminal determines that the deployment mode of the first carrier is a non-independent deployment mode based on the first information, the terminal can determine the frequency point of the first carrier according to the relationship (3). This allows the terminal to use the correct frequency point determination method to determine the frequency point of the first carrier, realize communication on the downlink non-anchor carrier, and ensure communication reliability.

[0099] The following describes the specific implementation method of the deployment of the first carrier indicated by the first information.

[0100] In one alternative approach, the first information may specifically indicate whether the first carrier is deployed in a standalone or non-standalone manner. For example, the configuration information may be radio resource control (RRC) signaling, and the first information may be an information element (IE) in the RRC signaling.

[0101] For example, the first information can adopt a selection (CHOICE) type configuration method. The first information selects a deployment method—either a standalone deployment method or a non-standalone deployment method—which becomes the deployment method for the first carrier. For instance, the first information can be denoted as operationModeInfo, which can be specifically represented as follows:

[0102] operationModeInfo CHOICE{

[0103] standalone Standalone-NB

[0104] non-standalone Non-Standalone-NB}

[0105] The first information (operationModeInfo) can be selected from either standalone or non-standalone. If standalone is selected, it indicates that the first carrier is deployed independently, and the Standalone-NB can configure specific information related to this independent deployment mode. If non-standalone is selected, it indicates that the first carrier is deployed in a non-standalone manner, i.e., when the first carrier is deployed in an in-band or guard band configuration, non-standalone can be selected. The Non-Standalone-NB can configure information related to this non-standalone deployment mode.

[0106] For example, the first information can be configured using an enumeration type. This enumeration type configuration enumerates one deployment mode between independent and non-independent deployment modes, and this deployment mode is the deployment mode for the first carrier. For instance, the first information can be denoted as operationModeInfo, which can be specifically represented as follows:

[0107] operationModeInfo ENUMERATED{standalone,non-standalone}

[0108] The first information (operationModeInfo) enumerates either standalone or non-standalone. If the first information enumerates standalone, it means that the first carrier is deployed independently; if the first information selects non-standalone, it means that the first carrier is deployed in a non-standalone manner.

[0109] For example, the first information can be configured using a Boolean value. For instance, the first information can be represented as `standalone_operationmode`, which can be specifically represented as follows:

[0110] standalone_operationmode Boolean

[0111] In this configuration, the Boolean type uses a single bit or byte to represent true (TRUE) or false (FALSE). For example, when a Boolean value is represented by a single bit, a bit of 1 indicates true, meaning the first carrier is deployed in standalone mode (standalone_operationmode) and a bit of 0 indicates false, meaning the first carrier is deployed in a non-standalone mode (in-band or guard band deployment). Similarly, when a Boolean value is represented by a single byte, a byte of 0xFF (all 8 bits are 1) indicates true, meaning the first carrier is deployed in standalone mode (standalone_operationmode) and a byte of 0x00 (all 8 bits are 0) indicates false, meaning the first carrier is deployed in a non-standalone mode.

[0112] In another alternative approach, the first information may indicate whether the first carrier is deployed as an independent deployment, an in-band deployment, or a guard band deployment.

[0113] For example, the first information can be configured using a selection (CHOICE) type. The first information selects one deployment mode from standalone, in-band, or guardband deployment modes, and this deployment mode is the deployment mode for the first carrier. For instance, the first information can be denoted as operationModeInfo, which can be specifically represented as follows:

[0114] If the first information option is "inband", the Inband-NB can be configured with specific information regarding the in-band deployment method. If the first information option is "guardband", the Guardband-NB can be configured with specific information regarding the in-band deployment method.

[0115] For example, the first information can be configured using an enumeration type. The first information enumerates one deployment mode from standalone, in-band, or guardband deployment modes, and this deployment mode is the deployment mode for the first carrier. For instance, the first information can be denoted as operationModeInfo, which can be specifically represented as follows:

[0116] operationModeInfo ENUMERATED{standalone,inband,guardband}

[0117] For example, the first information can configure the deployment mode of the first carrier by combining selection type with other types, where other types can be enumeration or Boolean values. For instance, the first information can select a deployment mode from independent deployment mode and non-independent deployment mode. When non-independent deployment mode is selected, the relevant information for non-independent deployment mode configures whether the first carrier is deployed in-band or in the guard band.

[0118] For example, the first information can be denoted as operationModeInfo, and operationModeInfo can be specifically represented as follows:

[0119] operationModeInfo CHOICE{

[0120] standalone Standalone-NB

[0121] non-standalone Non-Standalone-NB}

[0122] The Non-Standalone-NB configuration specifically addresses the non-standalone deployment mode. Non-Standalone-NB can include an enumerated type `non-Standalone_operationmode`, enumerating one deployment mode between in-band and guard band deployment. For example, Non-Standalone-NB is represented as follows:

[0123] Non-Standalone-NB SEQUENCE{

[0124] non-Standalone_operationmode ENUMERATED{inband,guardband}

[0125] , ...}

[0126] The “…” indicates that the Non-Standalone-NB can be configured with other related information, but this application is not limited to this, and it is also possible not to configure other related information, which will not be elaborated on below.

[0127] Alternatively, Non-Standalone-NB can include the boolean type inband_operationmode, and Non-Standalone-NB can be represented as follows:

[0128] Non-Standalone-NB SEQUENCE{

[0129] inband_operationmode Boolean

[0130] , ...}

[0131] If `inband_operationmode` is true, the first carrier is deployed in-band; if `inband_operationmode` is false, the first carrier is deployed in guard band. Alternatively, the Non-Standalone-NB can configure a boolean value for `guardband_operationmode`. If `guardband_operationmode` is true, the first carrier is deployed in guard band; if `guardband_operationmode` is false, the first carrier is deployed in-band.

[0132] In another alternative approach, the first information indicates that the deployment mode of the first carrier is an independent deployment mode, an in-band deployment mode of the first RAT, an in-band deployment mode of the second RAT, or a guard band deployment mode. For example, the in-band deployment mode can specifically be an in-band deployment mode of NR or LTE, that is, the first RAT and the second RAT can be NR and LTE respectively, but this application is not limited to this, and can also be other RATs or future RATs.

[0133] For example, the first information can be configured using a selection method. The first information can be deployed in one of the following modes: standalone, inband LTE, inband NR, or guardband. This deployment mode is the deployment mode for the first carrier. The first information can be denoted as operationModeInfo, which can be specifically represented as follows:

[0134] For example, the first information can be configured using an enumeration type. The first information can be configured to choose from standalone, inband LTE, inband NR, or guardband deployment modes. The first information can be denoted as operationModeInfo, which can be specifically represented as follows:

[0135] operationModeInfo ENUMERATED{standalone,inbandLTE,inbandNR,guardband}

[0136] For example, the first information can configure the deployment mode of the first carrier by combining a selection type with other types, where the other types can be enumerated or Boolean values. For instance, the first information can select a deployment mode from standalone deployment, in-band deployment, and guard band deployment. When in-band deployment is selected, the relevant information for in-band deployment configures whether the first carrier is deployed in NR in-band or LTE band. For example, the first information can be denoted as operationModeInfo, which can be specifically represented as follows:

[0137] Specifically, Inband-NB can be configured with information related to the in-band deployment mode, while Inband-NB can be configured with information related to the non-standalone deployment mode. Inband-NB can include an enumerated type inband_operationmode, enumerating one deployment mode between LTE in-band deployment mode and NR in-band deployment mode. For example, Inband-NB can be represented as follows:

[0138] Inband-NB SEQUENCE{

[0139] inband_operationmode ENUMERATED{inbandLTE, inbandNR}

[0140] ,…}

[0141] Alternatively, Inband-NB can include Boolean type inbandLTE or inbandNR. For example, Inband-NB can be represented as follows:

[0142] Inband-NB SEQUENCE{

[0143] inbandLTE_operationmode Boolean, or, inbandNR_operationmode Boolean,

[0144] ,…}

[0145] In this optional implementation, when the first carrier is deployed in an in-band configuration, the network device can specify the frequency band of the RAT (Range Attribution-Based Access) in which the first carrier is deployed through configuration information. This allows the terminal to perform at least one of the following based on the characteristics of the RAT: rate matching or resource reservation. For example, if the first carrier is deployed in an LTE band, the terminal can perform rate matching and / or resource reservation based on the cell reference signal (CRS). If the first carrier is deployed in an NR band, the terminal can perform rate matching and / or resource reservation based on the reference signal, channel, etc., according to the configuration. This allows the terminal not only to determine the frequency of the first carrier based on its deployment method, but also to determine the rate matching method and / or resource reservation method based on the deployment method, further improving the reliability of communication on the first carrier.

[0146] It should be understood that in the examples of the embodiments of this application, the names of each IE are merely examples listed for better illustration of the scheme. In specific implementation, each IE may use other names, and the embodiments of this application do not limit the names of each IE.

[0147] The above describes a specific implementation method for the deployment of the first carrier indicated by the first information. In another example, the first information can indicate the frequency point determination method of the first carrier. This will be described below.

[0148] In Example 1-2, this first information is used to indicate the frequency point determination method for the first carrier. The terminal determines the frequency point determination method for the first carrier based on the first information.

[0149] For example, multiple frequency point determination methods can be predefined by the protocol. The network device can indicate one of the multiple frequency point determination methods through the first information, and the terminal determines the frequency point of the first carrier according to the frequency point determination method indicated by the first information.

[0150] The following describes the specific implementation method of determining the frequency point of the first carrier wave, which is indicated by the first information.

[0151] For example, if the protocol predefines two frequency point determination methods that satisfy the relationships (2) and (3) mentioned above, and their respective identifiers, the first information can indicate the frequency point determination method by indicating the identifier of the frequency point determination method predefined in the protocol. The identifiers of the two frequency point determination methods in relationships (2) and (3) are 0 and 1, respectively. The first information includes 1 bit. If this 1 bit is 0, the terminal uses the frequency point determination method with identifier 0 to determine the frequency point of the first carrier. If this 1 bit is 1, the terminal uses the frequency point determination method with identifier 1 to determine the frequency point of the first carrier.

[0152] For example, the protocol predefines a frequency point determination method that satisfies relation (2) above as frequency point determination method 1 (such as freqformula_mode1), and a frequency point determination method that satisfies relation (3) as frequency point determination method 2 (freqformula_mode2). The first information can be the IE in RRC signaling, and the first information can be configured using a selection type, enumeration type, or boolean value type configuration method to determine the frequency point.

[0153] The first information can be configured using a selection-type configuration method to determine the frequency point. The first information can choose between frequency point determination method 1 and frequency point determination method 2, and this frequency point determination method is the frequency point determination method for the first carrier. For example, the first information can be denoted as freqformulaModeInfo, which can be represented as follows:

[0154] freqformulaModeInfo CHOICE{

[0155] freqformula_mode1 Freqformula_mode1,

[0156] freqformula_mode2 Freqformula_mode2}

[0157] Specifically, if the first information selects frequency point determination method 1, Freqformula_mode1 is used to configure the relevant information for frequency point determination method 1; if the first information selects frequency point determination method 2, Freqformula_mode2 is used to configure the relevant information for frequency point determination method 1. The aforementioned relevant information can configure one or more parameters used to determine the frequency point, such as configuring downlink ARFCN (i.e., N...). DL Alternatively, the offset M can be configured. DL This application does not limit this to such matters.

[0158] The first information can be configured using an enumeration-based configuration method to determine the frequency point. The first information can enumerate one frequency point determination method from frequency point determination method 1 and frequency point determination method 2, and this frequency point determination method is the frequency point determination method for the first carrier. For example, the first information can be denoted as freqformulaModeInfo, which can be represented as follows:

[0159] freqformulaModeInfo ENUMERATED{freqformula_mode1,freqformula_mode2}

[0160] The first information can be configured using a boolean value. In one example, the first information can be denoted as freqformula_mode1_enable, which can be represented as follows:

[0161] freqformula_mode1_enable Boolean

[0162] If the Boolean value is true, it indicates that the frequency point determination method for the first carrier is frequency point determination method 1; if the Boolean value is false, it indicates that the frequency point determination method for the first carrier is frequency point determination method 2. Alternatively, in another example, the first information can be denoted as freqformula_mode2_enable. If the Boolean value is true, it indicates that the frequency point determination method for the first carrier is frequency point determination method 2; if the Boolean value is false, it indicates that the frequency point determination method for the first carrier is frequency point determination method 1. This application does not limit this specific implementation.

[0163] The above describes how network devices can use the first information in their configuration information to indicate the deployment method or frequency point determination method of the first carrier. This allows the terminal to determine the frequency point determination method of the first carrier from among various downlink carrier frequency point determination methods based on the first information. This enables the terminal to use the correct frequency point determination method to determine the frequency point of the first carrier, achieving communication on that downlink non-anchor carrier and ensuring communication reliability.

[0164] This application also provides another implementation method, in which the network device can determine the frequency point determination method of the first carrier by whether the configuration information includes second information. Implementation method 2 will be described below.

[0165] In implementation method 2, if the configuration information includes the second information, the frequency point determination method for the first carrier is the first frequency point determination method. If the configuration information does not include the second information, the frequency point determination method for the first carrier is the second frequency point determination method. The second information can be an optional element (IE) in the configuration information. The network device can determine whether the configuration information includes or excludes the second information based on the frequency point determination method for the first carrier.

[0166] It should be understood that if the configuration information does not include the second information, the configuration information may include other information used to configure the first carrier, such as information related to time-domain resources and / or power control as described above. This application does not limit this. After receiving the configuration information, the terminal determines whether the configuration information includes the second information. If the second information is not included, the terminal can determine that the frequency point determination method for the first carrier is the first frequency point determination method. If the second information is included, the terminal can determine that the frequency point determination method for the first carrier is the second frequency point determination method.

[0167] The following is an exemplary description of the specific implementation of the second information.

[0168] Example 2-1: The second information is used to indicate that the first carrier is deployed in a standalone mode, and the first frequency point determination method is the frequency point determination method corresponding to the standalone deployment mode. For example, the second information can be denoted as `standalone_operationmode`, which can be represented as follows:

[0169] standalone_operationmode ENUMERATED{enabled} OPTIONAL

[0170] In this configuration, OPTIONAL indicates that standalone_operationmode is optional. If standalone_operationmode is included in the configuration information, it means that the standalone deployment mode is enabled, the first carrier is deployed in standalone mode, and the frequency point determination method for the first carrier is the same as that for standalone deployment. If standalone_operationmode is not included in the configuration information, it means that the standalone deployment mode is not enabled, the first carrier is deployed in non-standalone mode, and the frequency point determination method for the first carrier is the same as that for non-standalone deployment.

[0171] In Example 2-1, it can be understood that the deployment mode of the downlink non-anchor carrier predefined by the protocol is a non-independent deployment mode by default. If the configuration information does not include the second information, then the deployment mode of the first carrier can be considered as the non-independent deployment mode predefined by the protocol. If the configuration information includes the second information, then the deployment mode of the first carrier is an independent deployment mode.

[0172] Example 2-2: The second information is used to indicate that the first carrier is deployed in a non-standalone mode, and the first frequency point determination method is the frequency point determination method corresponding to the non-standalone deployment mode. For example, the second information can be denoted as non-standalone_operationmode, which can be represented as follows:

[0173] non-standalone_operationmode ENUMERATED{enabled} OPTIONAL

[0174] In this configuration, OPTIONAL indicates that non-standalone_operationmode is optional. If the configuration information includes non-standalone_operationmode, it means that the non-standalone deployment mode is enabled, the first carrier is deployed in the non-standalone mode, and the frequency point determination method for the first carrier is the same as that for the non-standalone deployment mode. If the configuration information does not include non-standalone_operationmode, it means that the non-standalone deployment mode is not enabled, the first carrier is deployed in the standalone mode, and the frequency point determination method for the first carrier is the same as that for the standalone deployment mode.

[0175] In Example 2-2, it can be understood that the deployment mode of the downlink non-anchor carrier, predefined by the protocol, defaults to an independent deployment mode. If the configuration information does not include the second information, the deployment mode of the first carrier can be considered as the protocol-predefined independent deployment mode. If the configuration information includes the second information, the deployment mode of the first carrier is a non-independent deployment mode. After determining the deployment mode of the first carrier, the terminal can determine the frequency point determination method of the first carrier as the frequency point determination method corresponding to that deployment mode.

[0176] Example 2-3: The frequency point determination method for the anchor carrier is the first frequency point determination method. The second information indicates that the deployment method of the first carrier is the same as the deployment method of the anchor carrier, or that the frequency point determination method of the first carrier is the same as the frequency point determination method of the anchor carrier. If the configuration information includes the second information (i.e., the deployment method / frequency point determination method of the anchor carrier and the non-anchor carrier is the same), the frequency point determination method of the first carrier is the first frequency point determination method. If the configuration information does not include the second information (i.e., the deployment method / frequency point determination method of the anchor carrier and the non-anchor carrier is different), the frequency point determination method of the first carrier is the second frequency point determination method.

[0177] For example, the second information can be denoted as sameWithAnchor, which can be represented as follows:

[0178] sameWithAnchor ENUMERATED{enabled} OPTIONAL

[0179] In this context, OPTIONAL indicates that sameWithAnchor is optional in Internet Explorer.

[0180] For example, the second information indicates that the deployment method of the first carrier is the same as that of the anchor carrier. If the configuration information includes the second information, the terminal can determine that the deployment method of the first carrier is the same as that of the anchor carrier. If the anchor carrier is deployed independently, then the first carrier is also deployed independently, and the terminal can determine the frequency of the first carrier according to the frequency point determination method corresponding to the independent deployment method. If the anchor carrier is deployed in a non-independent manner, then the first carrier is also deployed in a non-independent manner, and the terminal can determine the frequency of the first carrier according to the frequency point determination method corresponding to the non-independent deployment method. If the configuration information does not include the second information, the terminal can determine that the deployment method of the first carrier is different from that of the anchor carrier. It should be understood that the difference here means that they are not both independent deployment methods or not both non-independent deployment methods. In-band deployment and guard band deployment can be considered to belong to non-independent deployment methods. If the anchor carrier is deployed independently and the non-anchor carrier is deployed in a non-independent manner, such as in-band deployment or guard band deployment, the terminal determines the frequency of the first carrier according to the frequency point determination method corresponding to the non-independent deployment method. If the anchor carrier is deployed in a non-independent manner, then the first carrier is deployed in an independent manner. The terminal determines the frequency of the first carrier according to the frequency determination method corresponding to the non-independent deployment method.

[0181] In other words, the deployment method of the downlink non-anchor carrier can be predefined by the protocol to be different from the default deployment method of the anchor carrier (i.e., independent deployment method and non-independent deployment method, respectively). If the configuration information does not include the second information, it can be assumed that the deployment method of the first carrier is different from the deployment method of the anchor carrier. If the deployment methods of the anchor carrier and the non-anchor carrier are not different by default, then the configuration information includes the second information, and the terminal is notified through the second information that the deployment methods of the first carrier and the anchor carrier are the same.

[0182] For example, the second information indicates that the frequency point determination method of the first carrier is the same as that of the anchor carrier. If the configuration information includes the second information, the terminal can determine that the frequency point determination method of the first carrier is the same as that of the anchor carrier. If the frequency point determination method of the anchor carrier is the first frequency point determination method, then the terminal determines the frequency point of the first carrier according to the first frequency point determination method. If the configuration information does not include the second information, the terminal can determine that the frequency point determination method of the first carrier is different from that of the anchor carrier. If the frequency point determination method of the anchor carrier is the first frequency point determination method, then the terminal can determine that the frequency point determination method of the first carrier is the second frequency point determination method, and then the terminal determines the frequency point of the first carrier according to the second frequency point determination method. The first frequency point determination method can be a frequency point determination method that satisfies the previous relation (2), and the second frequency point determination method can be a frequency point determination method that satisfies the previous relation (3). Alternatively, the first frequency point determination method can be a frequency point determination method that satisfies the previous relation (3), and the second frequency point determination method can be a frequency point determination method that satisfies the previous relation (2). This application embodiment does not limit this.

[0183] In other words, the frequency determination method for the downlink non-anchor carrier can be predefined by the protocol and differ from the default frequency determination method for the anchor carrier. If the configuration information does not include the second information, it can be assumed that the frequency determination method for the first carrier is different from that for the anchor carrier. If the frequency determination methods for the anchor carrier and non-anchor carrier are not different by default, then the configuration information includes the second information, which notifies the terminal that the frequency determination methods for the first carrier and the anchor carrier are different.

[0184] Example 2-4: The frequency point determination method for the anchor carrier is the second frequency point determination method. The second information indicates that the deployment method of the first carrier is different from the deployment method of the anchor carrier, or that the frequency point determination method of the first carrier is different from the frequency point determination method of the anchor carrier. If the configuration information includes this second information (i.e., the deployment method / frequency point determination method of the anchor carrier is different from that of the non-anchor carrier), the frequency point determination method of the first carrier is the first frequency point determination method. If the configuration information does not include the second information (i.e., the deployment method / frequency point determination method of the anchor carrier is the same as that of the non-anchor carrier), the frequency point determination method of the first carrier is the second frequency point determination method.

[0185] For example, the second information can be denoted as differentWithAnchor, which can be represented as follows:

[0186] differentWithAnchor ENUMERATED{enabled} OPTIONAL

[0187] In this context, OPTIONAL indicates that differentWithAnchor is optional.

[0188] For example, the second information indicates that the deployment method of the first carrier is different from that of the anchor carrier. If the configuration information includes the second information, the terminal can determine that the deployment method of the first carrier is different from that of the anchor carrier. For example, if the anchor carrier is deployed independently, then the deployment method of the first carrier is non-independent, and the terminal can determine the frequency of the first carrier according to the frequency point determination method corresponding to the non-independent deployment method. If the anchor carrier is deployed non-independently, then the deployment method of the first carrier is independent, and the terminal can determine the frequency of the first carrier according to the frequency point determination method corresponding to the independent deployment method. If the configuration information does not include the second information, the terminal can determine that the deployment method of the first carrier is the same as that of the anchor carrier. For example, if the anchor carrier is deployed independently, then the deployment method of the non-anchor carrier is also independent, and the terminal can determine the frequency of the first carrier according to the frequency point determination method corresponding to the independent deployment method. If the anchor carrier is deployed non-independently, then the deployment method of the first carrier is also non-independent, and the terminal can determine the frequency of the first carrier according to the frequency point determination method corresponding to the non-independent deployment method.

[0189] In other words, the deployment method of the downlink non-anchor carrier can be predefined by the protocol and is the same as the deployment method of the anchor carrier by default. If the configuration information does not include the second information, it can be assumed that the deployment method of the first carrier is the same as the deployment method of the anchor carrier. If the deployment methods of the anchor carrier and the non-anchor carrier are not the same by default, the configuration information includes the second information, which notifies the terminal that the deployment methods of the first carrier and the anchor carrier are different (i.e., independent deployment method and non-independent deployment method, respectively).

[0190] For example, the second information is used to indicate that the frequency point determination method of the first carrier is different from that of the anchor carrier. If the configuration information includes the second information, the terminal can determine that the frequency point determination method of the first carrier is different from that of the anchor carrier. For example, if the frequency point determination method of the anchor carrier is the second frequency point determination method, the terminal determines the frequency point of the first carrier according to the first frequency point determination method. If the configuration information does not include the second information, the terminal can determine that the frequency point determination method of the first carrier is the same as that of the anchor carrier. For example, if the frequency point determination method of the anchor carrier is the second frequency point determination method, the terminal can determine the frequency point of the first carrier according to the second frequency point determination method. The first frequency point determination method can be a frequency point determination method that satisfies the relationship (2) above, and the second frequency point determination method can be a frequency point determination method that satisfies the relationship (3) above, or the first frequency point determination method can be a frequency point determination method that satisfies the relationship (3) above, and the second frequency point determination method can be a frequency point determination method that satisfies the relationship (2) above. This application embodiment does not limit this.

[0191] In other words, the frequency determination method for the downlink non-anchor carrier can be predefined by the protocol and is the same as the frequency determination method for the anchor carrier by default. If the configuration information does not include the second information, it can be assumed that the frequency determination method for the first carrier is the same as the frequency determination method for the anchor carrier. If the frequency determination methods for the anchor carrier and the non-anchor carrier are not the same by default, then the configuration information includes the second information, which notifies the terminal that the frequency determination methods for the first carrier and the anchor carrier are different.

[0192] Optionally, the configuration information may be downlink carrier configuration information. For example, in the examples above, the configuration information may be downlink carrier common configuration information. For instance, the configuration information may be denoted as DL-CarrierConfigCommon, but this application is not limited to this; the configuration information may also have other names, such as carrier common configuration information, etc.

[0193] Example 2-5 shows that this configuration information is specifically used to configure a switch from the second carrier to the first carrier. The second information indicates that the deployment method of the first carrier is different from that of the second carrier, or that the frequency point determination method of the first carrier is different from that of the second carrier. The frequency point determination method of the second carrier is the second frequency point determination method.

[0194] In Examples 2-5, the configuration information may specifically be configuration information used to configure the terminal to switch from the second carrier to the first carrier. The terminal can determine the frequency point determination method of the first carrier based on whether the configuration information includes the second information. For example, the second information can be denoted as differentWithCurrentDLCarrier, which can be represented as follows:

[0195] differentWithCurrentDLCarrier ENUMERATED{enabled} OPTIONAL

[0196] In this context, OPTIONAL indicates that differentWithCurrentDLCarrier is optional.

[0197] For example, the second information is used to indicate that the deployment method of the first carrier is different from that of the second carrier. It should be understood that this difference means that the deployment methods of the first and second carriers are not both independent deployment methods, or neither is a non-independent deployment method. For instance, if the second carrier is deployed in-band and the first carrier is deployed in the guard band, or the second carrier is deployed in the guard band and the first carrier is deployed in-band, or both the first and second carriers are deployed independently, then both the first and second carriers are non-independent deployment methods, and the network device determines that the configuration information does not include the second information. After receiving the configuration information, the terminal determines that the configuration information does not include the second information, and therefore determines that the deployment methods of the first and second carriers are the same. If the second carrier is deployed independently, then the first carrier is also deployed independently, and the terminal determines the frequency of the first carrier according to the frequency point determination method corresponding to the independent deployment method. If the second carrier is deployed non-independently, then the first carrier is also deployed non-independently, and the terminal determines the frequency of the first carrier according to the frequency point determination method corresponding to the non-independent deployment method. If one of the first and second carriers is deployed independently and the other is deployed non-independently, the network device determines that the deployment methods of the first and second carriers are different. The configuration information includes second information. Based on the configuration information including the second information, the terminal determines that the deployment methods of the first and second carriers are different. If the second carrier is deployed independently, then the first carrier is deployed non-independently. The terminal determines the frequency of the first carrier based on the frequency point determination method corresponding to the non-independent deployment method. Similarly, if the second carrier is deployed non-independently, the terminal determines the frequency of the first carrier based on the frequency point determination method corresponding to the independent deployment method.

[0198] In other words, the deployment method of the carrier to be switched to (i.e., the first carrier) can be predefined by the protocol to be the same as the deployment method of the current carrier (i.e., the second carrier) by default. If the configuration information does not include the second information, it can be assumed that the deployment method of the first carrier is the same as that of the second carrier. If the first carrier and the second carrier are not the same by default, then the configuration information includes the second information, and the terminal is notified of the difference in deployment methods between the first carrier and the second carrier through the second information.

[0199] For example, the second information indicates that the frequency point determination method for the first carrier is different from that for the second carrier. If the configuration information does not include the second information, then the frequency point determination method for the first carrier is the same as that for the second carrier, and the terminal determines the frequency point determination method for the first carrier based on the frequency point determination method for the second carrier. If the configuration information includes the second information, then the frequency point determination method for the first carrier is different from that for the second carrier. If the frequency point determination method for the second carrier is the same as that for the first carrier, the terminal determines the frequency point for the first carrier based on the second frequency point determination method; otherwise, if the frequency point determination method for the second carrier is the same as that for the second carrier, the terminal determines the frequency point for the first carrier based on the first frequency point determination method.

[0200] In other words, the frequency point determination method for the carrier to be switched to (i.e., the first carrier) can be predefined by the protocol and is the same as the frequency point determination method for the current carrier (the second carrier) by default. If the configuration information does not include the second information, it can be assumed that the frequency point determination method for the first carrier is the same as that for the second carrier. If the first carrier and the second carrier do not have the same default frequency point determination method, then the configuration information includes the second information, which notifies the terminal that the frequency point determination methods for the first carrier and the second carrier are different.

[0201] For example, in Examples 2-5, the configuration information can be downlink carrier-specific configuration information. For instance, the configuration information can be denoted as DL-CarrierConfigDedicated, but this application is not limited to this; the configuration information can also have other names, such as carrier-specific configuration information, etc.

[0202] In this second implementation, by predefining a default deployment method / frequency confirmation method, or by predefining whether the deployment method / frequency confirmation method of the downlink non-anchor carrier and the anchor carrier is the same or different, when the downlink non-anchor carrier uses the default method, no signaling indication is required, which can reduce signaling overhead. When the downlink anchor carrier uses a non-default method, the terminal can be notified through the second information in the configuration information so that the terminal can use the correct frequency point determination method to determine the frequency point of the first carrier and realize communication on the downlink non-anchor carrier, thus ensuring communication reliability.

[0203] After receiving the configuration information in S401, the terminal can determine the frequency point determination method of the first carrier in S402 based on the configuration information, and thus determine the frequency point of the first carrier based on the frequency point determination method of the first carrier.

[0204] For example, if the first carrier is deployed in an independent manner, the frequency point of the first carrier satisfies the aforementioned relation (2). If the first carrier is deployed in a non-independent manner, the frequency point of the first carrier satisfies the aforementioned relation (3). However, this application is not limited to this, and other frequency point determination methods can be defined according to specific implementation methods.

[0205] According to the solution provided in the embodiments of this application, the network device can enable the terminal to determine the frequency point determination method of the downlink anchor carrier through the configuration information of the downlink non-anchor carrier, thereby obtaining the frequency point of the downlink non-anchor carrier based on the correct frequency point determination method, realizing communication on the downlink non-anchor carrier, and ensuring communication reliability.

[0206] It is understood that, in order to achieve the functions in the above embodiments, the base station and terminal include hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0207] Figures 5 and 6 are schematic diagrams of possible communication devices provided in the embodiments of this application. These communication devices can be used to implement the functions of the terminal or network device in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device can be one of the terminals 120a-120j shown in Figure 1, or it can be the network device 110a or 110b shown in Figure 1, or it can be a module (such as a chip or chip system) applied to the terminal or network device.

[0208] The communication device 500 includes a transceiver unit 520, which can be used to receive or send information. The communication device 500 may also include a processing unit 510, which can be used to process instructions or data to achieve corresponding operations.

[0209] It should be understood that when the communication device 500 is a chip configured in (or used in) a communication device, the transceiver unit 520 in the communication device 500 can be the input / output interface or circuit of the chip, and the processing unit 510 in the communication device 500 can be the processor in the chip.

[0210] Optionally, the communication device 500 may further include a storage unit 530, which can be used to store instructions or data. The processing unit 510 can execute the instructions or data stored in the storage unit to enable the communication device to perform corresponding operations.

[0211] The communication device 500 can be used to implement the functions of a terminal or network device in the method embodiment shown in FIG4 above.

[0212] When the communication device 500 is used to implement the functions of the terminal in the method embodiment shown in FIG4: the transceiver unit 520 is used to receive configuration information, the configuration information being used to configure a first carrier, the first carrier being a downlink non-anchor carrier. The processing unit 510 is used to determine the frequency point determination method of the first carrier according to the configuration information.

[0213] When the communication device 500 is used to implement the functions of the network device in the method embodiment shown in FIG4: the processing unit 510 is used to determine configuration information according to the frequency point determination method of the first carrier, the configuration information being used to configure the first carrier, the first carrier being a downlink non-anchor carrier. The transceiver unit 520 is used to send the configuration information.

[0214] For a more detailed description of the processing unit 510 and the transceiver unit 520, please refer to the relevant description in the method embodiment shown in Figure 4.

[0215] It should be understood that the transceiver unit 520 in the communication device 500 can be implemented through a communication interface (such as a transceiver, transceiver circuit, input / output interface, or pins, etc.). When the communication interface is a transceiver, the transceiver can consist of a receiver and / or a transmitter. The processing unit 510 in the communication device 500 can be implemented through at least one processor, or it can be implemented through at least one logic circuit. Optionally, the communication device 500 also includes a storage unit, which can be implemented using a memory.

[0216] As shown in Figure 6, the communication device 600 includes a processor 610 and an interface circuit 620. The processor 610 and the interface circuit 620 are coupled to each other. It is understood that the interface circuit 620 can be a transceiver or an input / output interface. Optionally, the communication device 600 may also include a memory 630 for storing instructions executed by the processor 610, or storing input data required by the processor 610 to execute instructions, or storing data generated after the processor 610 executes instructions.

[0217] In one implementation, the memory 630 may be integrated into the processor 610 or independent of the processor 610.

[0218] When the communication device 600 is used to implement the method shown in FIG4, the processor 610 is used to implement the function of the processing unit 510, and the interface circuit 620 is used to implement the function of the transceiver unit 520.

[0219] When the aforementioned communication device is a chip applied to a terminal device, the terminal device chip can implement the functions of the second communication device in the above method embodiments. The terminal device chip receives information from other modules (such as an RF module or antenna) in the terminal device, the information being sent to the terminal device by the network device; or, the terminal device chip sends information to other modules (such as an RF module or antenna) in the terminal device, the information being sent to the network device by the terminal device.

[0220] When the aforementioned communication device is a module applied to a network device, the network device module can implement the functions of the first communication device in the above method embodiments. The network device module receives information from other modules (such as radio frequency modules or antennas) in the network device, which is information sent from the terminal device to the network device; or, the network device module sends information to other modules (such as radio frequency modules or antennas) in the network device, which is information sent from the network device to the terminal device. Here, the network device module can be the baseband chip of the network device, or it can be a DU or other modules. The DU here can be a DU under an open radio access network (O-RAN) architecture.

[0221] It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), microprocessor units (MPUs), microcontroller units (MCUs), graphics processing units (GPUs), artificial intelligence processors (AI processors), neural processing units (NPUs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0222] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in an access network device or a terminal device. The processor and storage medium can also exist as discrete components in the access network device or terminal device.

[0223] According to the method provided in the application embodiments, this application embodiment also provides a computer program product, which includes: computer program code, which, when executed by one or more processors, causes a device including the processor to perform the method shown in FIG4.

[0224] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. This computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed, in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, network equipment, user equipment, or other programmable device.

[0225] According to the method provided in the embodiments of this application, the embodiments of this application also provide a computer-readable storage medium that stores the above-mentioned computer program or instructions. When the computer program or instructions are run by one or more processors, the apparatus including the processor performs the method shown in FIG4.

[0226] As described above, computer programs or instructions can be stored in or transferred from one computer-readable storage medium to another. For example, the computer programs or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium can be a volatile or non-volatile storage medium, or it can include both volatile and non-volatile types of storage media.

[0227] According to the method provided in the embodiments of this application, this application also provides a communication system, including one or more of the aforementioned terminals. The system may further include one or more of the aforementioned network devices.

[0228] In the various embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus described above is merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0229] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this solution according to actual needs.

[0230] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0231] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An information transmission method, characterized in that, include: Receive configuration information, the configuration information being used to configure a first carrier, the first carrier being a downlink non-anchor carrier; Based on the configuration information, the frequency point determination method for the first carrier is determined.

2. The method according to claim 1, characterized in that, The configuration information includes first information, which indicates the deployment method of the first carrier. If the first carrier is deployed in an independent manner, the frequency point determination method for the first carrier is the same as that for the independent deployment method; or, The deployment method of the first carrier is a non-independent deployment method, and the frequency point determination method of the first carrier is the frequency point determination method corresponding to the non-independent deployment method.

3. The method according to claim 2, characterized in that, The first information is used to indicate whether the deployment mode of the first carrier is a standalone deployment mode or a non-standalone deployment mode; or, The first information is used to indicate whether the deployment mode of the first carrier is an independent deployment mode, an in-band deployment mode, a guard band deployment mode, an in-band deployment mode using a first radio access technology (RAT) system, or an in-band deployment mode using a second RAT system.

4. The method according to claim 1, characterized in that, The step of determining the frequency point determination method of the first carrier based on the configuration information includes: Based on whether the configuration information includes the second information, the frequency point determination method for the first carrier is determined. Wherein, if the configuration information includes second information, the frequency point determination method for the first carrier is the first frequency point determination method; or, If the configuration information does not include the second information, the frequency point determination method for the first carrier is the second frequency point determination method.

5. The method according to claim 4, characterized in that, The second information is used to indicate that the frequency point determination method for the first carrier is the first frequency point determination method; or, The second information is used to indicate that the deployment mode of the first carrier is an independent deployment mode, and the first frequency point determination method is the frequency point determination method corresponding to the independent deployment mode; or, The second information is used to indicate that the deployment mode of the first carrier is a non-independent deployment mode, and the first frequency point determination method is the frequency point determination method corresponding to the non-independent deployment mode; or, The second information is used to indicate that the deployment method of the first carrier is the same as the deployment method of the anchor carrier, or the second information is used to indicate that the frequency point determination method of the first carrier is the same as the frequency point determination method of the anchor carrier, wherein the frequency point determination method of the anchor carrier is the first frequency point determination method; or, The second information is used to indicate that the deployment method of the first carrier is different from the deployment method of the anchor carrier, or the second information is used to indicate that the frequency point determination method of the first carrier is different from the frequency point determination method of the anchor carrier, wherein the frequency point determination method of the anchor carrier is the second frequency point determination method.

6. The method according to claim 4, characterized in that, The configuration information is specifically used to configure the switching from the second carrier to the first carrier. The second information is used to indicate that the deployment method of the first carrier is different from the deployment method of the second carrier, or the second information is used to indicate that the frequency point determination method of the first carrier is different from the frequency point determination method of the second carrier, wherein the frequency point determination method of the second carrier is the second frequency point determination method.

7. The method according to any one of claims 1 to 6, characterized in that, The frequency point determination method for the first carrier is the frequency point determination method corresponding to the independent deployment method, where the frequency point F of the first carrier is... DL satisfy: F DL =F DL_low +0.1(N DL -N Offs-DL )+0.0025*(2M DL ); or, The frequency point determination method for the first carrier is the frequency point determination method corresponding to the non-independent deployment method, and the frequency point F of the first carrier is... DL satisfy: F DL =F DL_low +0.1(N DL -N Offs-DL )+0.0025*(2M DL +1); Among them, F DL_low N is the lowest frequency in the downlink operating band. DL It is the downlink absolute radio frequency channel number ARFCN, N Offs-DL It is the downlink ARFCN offset, M DL It is the offset of the narrowband channel number relative to the downlink ARFCN channel number.

8. An information transmission method, characterized in that, include: Based on the frequency point determination method of the first carrier, the configuration information is determined. The configuration information is used to configure the first carrier, which is a downlink non-anchor carrier. Send the configuration information.

9. The method according to claim 8, characterized in that, The configuration information includes first information, which indicates the deployment method of the first carrier. If the first carrier is deployed in an independent manner, the frequency point determination method for the first carrier is the same as that for the independent deployment method; or, The deployment method of the first carrier is a non-independent deployment method, and the frequency point determination method of the first carrier is the frequency point determination method corresponding to the non-independent deployment method.

10. The method according to claim 9, characterized in that, The first information is used to indicate whether the deployment mode of the first carrier is a standalone deployment mode or a non-standalone deployment mode; or, The first information is used to indicate whether the deployment mode of the first carrier is an independent deployment mode, an in-band deployment mode, a guard band deployment mode, an in-band deployment mode using a first radio access technology (RAT) system, or an in-band deployment mode using a second RAT system.

11. The method according to claim 8, characterized in that, If the frequency point determination method for the first carrier is the first frequency point determination method, the configuration information includes the second information; or, If the frequency point determination method of the first carrier is the second frequency point determination method, the configuration information does not include the second information.

12. The method according to claim 11, characterized in that, The second information is used to indicate that the frequency point determination method for the first carrier is the first frequency point determination method; or, The second information is used to indicate that the first carrier is deployed in an independent mode, and the first frequency point determination method is the frequency point determination method corresponding to the independent deployment mode; or, The second information is used to indicate that the first carrier is deployed in a non-standalone mode, and the first frequency point determination method is the frequency point determination method corresponding to the non-standalone deployment mode; or, The second information is used to indicate that the deployment method of the first carrier is the same as the deployment method of the anchor carrier, or the frequency point determination method of the first carrier is the same as the frequency point determination method of the anchor carrier, wherein the frequency point determination method of the anchor carrier is the first frequency point determination method; or, The second information is used to indicate that the deployment method of the first carrier is different from the deployment method of the anchor carrier, or the frequency point determination method of the first carrier is different from the frequency point determination method of the anchor carrier, wherein the frequency point determination method of the anchor carrier is the second frequency point determination method.

13. The method according to claim 11, characterized in that, The configuration information is specifically used to configure the switching from the second carrier to the first carrier. The second information is used to indicate that the deployment method of the first carrier is different from the deployment method of the second carrier, or that the frequency point determination method of the first carrier is different from the frequency point determination method of the second carrier, and the frequency point determination method of the second carrier is the second frequency point determination method.

14. The method according to any one of claims 8 to 13, characterized in that, The first carrier is deployed in an independent manner, and the frequency point F of the first carrier is... DL satisfy: F DL =F DL_low +0.1(N DL -N Offs-DL )+0.0025*(2M DL ); or, The first carrier is deployed in a non-independent manner, and the frequency point F of the first carrier is... DL satisfy: F DL =F DL_low +0.1(N DL -N Offs-DL )+0.0025*(2M DL +1); Among them, F DL_low N is the lowest frequency in the downlink operating band. DL It is the downlink absolute radio frequency channel number ARFCN, N Offs-DL It is the downlink ARFCN offset, M DL It is the offset of the narrowband channel number relative to the downlink ARFCN.

15. A communication device, characterized in that, include: A transceiver unit is used to receive configuration information, which is used to configure a first carrier, wherein the first carrier is a downlink non-anchor carrier. The processing unit determines the frequency point determination method of the first carrier based on the configuration information.

16. A communication device, characterized in that, include: The processing unit is configured to determine configuration information based on the frequency point determination method of the first carrier, wherein the configuration information is used to configure the first carrier, and the first carrier is a downlink non-anchor carrier. The transceiver unit is used to send the configuration information.

17. A communication device, characterized in that, The device includes a processor coupled to a memory for storing a computer program, the processor executing the computer program stored in the memory to cause the communication device to perform the method as claimed in any one of claims 1 to 7; or to cause the communication device to perform the method as claimed in any one of claims 8 to 14.

18. A communication device, characterized in that, The device includes a processor and a communication interface, the processor being configured to execute a computer program to control the communication interface to perform input and / or output operations, such that the communication device implements the method as described in any one of claims 1 to 7, or implements the method as described in any one of claims 8 to 14.

19. The communication device according to claim 17 or 18, characterized in that, The communication device includes a memory for storing the computer program.

20. The communication device according to any one of claims 17 to 19, characterized in that, The communication device is a chip.

21. A computer-readable storage medium, characterized in that, The device stores instructions that, when executed on the communication device, cause the communication device to perform the method as described in any one of claims 1 to 7, or the method as described in any one of claims 8 to 14.

22. A computer program product, characterized in that, The computer program product includes: a computer program that, when run on a communication device, causes the communication device to perform the method of any one of claims 1 to 7, or the method of any one of claims 8 to 14.

Images